E1 Subcontract Mgmt Guide

(1)

Subcontract Management 9.0

Implementation Guide

(2)

Trademark Notice

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Subject to patent protection under one or more of the following U.S. patents: 5,781,908; 5,828,376; 5,950,010; 5,960,204; 5,987,497; 5,995,972; 5,987,497; and 6,223,345. Other patents pending.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are “commercial computer software” or “commercial technical data” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

Hazardous Applications Notice

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Third Party Content, Products, and Services Disclaimer

This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.

(3)

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

Open Source Disclosure

Oracle takes no responsibility for its use or distribution of any open source or shareware software or documentation and disclaims any and all liability or damages resulting from use of said software or documentation. The following open source software may be used in Oracle’s JD Edwards EnterpriseOne products and the following disclaimers are provided:

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED “AS IS’’ AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR

SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

(4)

(5)

General Preface

About This Documentation Preface ... ...xi

JD Edwards EnterpriseOne Application Prerequisites... . . . .xi

Application Fundamentals... . . . .xi

Documentation Updates and Downloading Documentation...xii

Obtaining Documentation Updates...xii

Downloading Documentation...xii

Additional Resources...xii

Typographical Conventions and Visual Cues...xiii

Typographical Conventions...xiv

Visual Cues...xiv

Country, Region, and Industry Identifiers... . . . .xv

Currency Codes...xvi

Comments and Suggestions...xvi

Common Fields Used in Implementation Guides...xvi

Preface JD Edwards EnterpriseOne Subcontract Management Preface... . . . .xix

JD Edwards EnterpriseOne Products...xix

JD Edwards EnterpriseOne Application Fundamentals...xix

Chapter 1 Getting Started with JD Edwards EnterpriseOne Subcontract Management... ...1

JD Edwards EnterpriseOne Subcontract Management Overview...1

JD Edwards EnterpriseOne Subcontract Management Integrations...5

JD Edwards EnterpriseOne Subcontract Management Implementation...6

Global Implementation Steps...7

JD Edwards EnterpriseOne Subcontract Management Implementation Steps...8

Chapter 2 Setting Up Subcontract Management... ...9

Understanding System Setup...9

(6)

Other System Setup... . . . .11

AAI Tables for the Financial System... . . . .11

Setting Up Projects or Jobs... . . . .14

Setting Up Commitments... . . . .15

Understanding Commitments... . . . .16

Understanding Commitment Tracking... . . . .16

Understanding Commitment Relief... . . . .17

Form Used to Set Up Commitments... . . . .17

Setting Up Commitment Tracking... . . . .17

Setting Up Commitment Relief... . . . .17

Converting Data to the Log Master Table... . . . .17

Understanding Converting Data to the Log Master Table... . . . .18

Converting Data to the Log Master Table... . . . .18

Chapter 3 Setting Up Suppliers... . .. .. .. .19

Understanding Supplier Setup... . . . .19

Entering Supplier Information for Subcontract Orders... . . . .19

Understanding Supplier Information for Subcontract Orders... . . . .20

Prerequisite... . . . .20

Forms Used to Enter Supplier Information for Subcontract Orders... . . . .20

Entering Supplier Details... . . . .20

Entering Supplier Additional Information... . . . .22

Entering a Temporary Address for a Supplier... . . . .23

Managing Subcontractors... . . . .24

Chapter 4 Creating Contracts... . . . .25

Understanding Contracts... . . . .25

Prerequisites... . . . .25

Understanding Subcontract Orders... . . . .26

Setting Processing Options for Enter Subcontract Orders (P4310)... . . . .29

Entering Subcontract Order Header Information... . . . .45

Understanding Subcontract Order Header Information... . . . .46

Forms Used to Enter Subcontract Order Header Information... . . . .48

Entering Origin Information and Delivery Instructions for an Order... . . . .49

Entering Dates for an Order... . . . .49

(7)

Entering Reference Information for an Order... . . . .50

Entering Subcontract Order Detail Information... . . . .50

Understanding Subcontract Order Detail Information... . . . .51

Forms Used to Enter Subcontract Order Detail Information... . . . .55

Entering Detail Lines by Account Number... . . . .56

Entering Tax Information for a Detail Line... . . . .58

Entering Discount Terms for a Detail Line... . . . .58

Entering Change Orders... . . . .59

Copying Change Orders... . . . .60

Duplicating an Order... . . . .60

Working with Orders on Hold... . . . .60

Understanding Order Holds... . . . .61

Forms Used to Work with Orders on Hold... . . . .62

Entering Order Holds... . . . .62

Chapter 5 Working with Commitments... . .. . .. ..65

Understanding Commitments... . . . .65

Verifying Commitment Integrity... . . . .67

Understanding the Commitment Integrity Report... . . . .67

Running the Commitment Integrity Report (R40910)... . . . .68

Setting Processing Options for the Commitment Integrity Report (R40910)... . . . .68

Reviewing Commitment Information for Subcontracts... . . . .69

Understanding Commitment Information for Subcontracts... . . . .69

Forms Used to Review Commitment Information for Subcontracts... . . . .70

Setting Processing Options for Commitment Inquiry (P40230A)... . . . .71

Reviewing Detailed Commitment Information... . . . .71

Processing Commitment Rollovers... . . . .72

Understanding the Encumbrance Rollover Program... . . . .73

Running the Encumbrance Rollover Program (R4317)... . . . .73

Setting Processing Options for Encumbrance Rollover (R4317)... . . . .73

Working with Commitment Audit Trails... . . . .75

Understanding Commitment Audit Trails... . . . .75

Understanding the Create Commitment Audit Trail Program... . . . .75

Understanding Corrections to Commitment Audit Trails... . . . .75

(8)

Running the Create Commitment Audit Trail Program (R00993)... . . . .76

Posting Committed Costs to Jobs... . . . .76

Understanding the Post Committed Cost to Job Program... . . . .77

Running the Post Committed Cost to Job Program (R00932)... . . . .77

Setting Processing Options for Post Committed Cost to Job (R00932)... . . . .77

Chapter 6 Working with Subcontract Logs... . . . .79

Understanding Subcontract Logs... . . . .79

Entering Subcontract Log Information... . . . .80

Understanding Subcontract Log Entry... . . . .80

Forms Used to Enter Subcontract Log Information... . . . .81

Setting Processing Options for Log Revisions (P4305)... . . . .81

Creating a Subcontract Log... . . . .81

Updating the Log Master... . . . .83

Understanding the Log Report/Update Program... . . . .83

Running the Log Report/Update Program (R43300)... . . . .83

Setting Processing Options for Log Report/Update (R43300)... . . . .83

Updating Unsatisfied, Expired Logs... . . . .84

Understanding the Logs (F4305) Report/Update Program... . . . .84

Running the Logs (F4305) Report/Update Program (R43540)... . . . .84

Setting Processing Options for Logs (F4305) Report/Update (R43540)... . . . .84

Chapter 7 Working with Order Information... . .. .. .. .87

Understanding Data Purging... . . . .87

Reviewing Order Information... . . . .87

Understanding Order Reviews... . . . .87

Forms Used to Review Order Information... . . . .88

Working with Budgets... . . . .89

Understanding Budget Checking... . . . .89

Understanding Search Scenarios for Level of Detail... . . . .90

Understanding Budget Totaling... . . . .91

Understanding Calculations of Available Budget to Date for the Fiscal Year... . . . .92

Form Used to Work with Budgets... . . . .92

(9)

Reviewing the Budget... . . . .94

Chapter 8 Processing Receipts... . .. . .. ..95

Understanding Receipt Processing... . . . .95

Chapter 9 Processing Progress Payments... . .. . .. ..97

Understanding Progress Payments... . . . .97

Creating Subcontract Vouchers... . . . .99

Understanding Subcontract Vouchers...100

Understanding Voucher Matching...103

Understanding Invoices Received in an Alternate Currency...104

Prerequisites...104

Forms Used to Create Subcontract Vouchers...105

Setting Processing Options for Voucher Match (P4314)...105

Setting Processing Options for A/P Standard Voucher Entry (P0411)...114

Setting Processing Options for Freight Distribution (P43147)...122

Selecting Records to Match to a Voucher...122

Selecting Order Detail Lines to Match to a Voucher...123

Selecting Order Detail Lines for Freight Vouchering...123

Processing Retainage...125

Understanding Retainage...125

Prerequisites...130

Forms Used to Process Retainage...130

Entering a Voucher with Retainage...130

Entering a Voucher to Release Retainage...130

Chapter 10 Processing Special Orders... ...133

Understanding Special Orders Processing...133

Chapter 11 Processing Approvals... ...135

(10)

Appendix A

JD Edwards EnterpriseOne Subcontract Management Reports... ...137

JD Edwards EnterpriseOne Subcontract Management Reports...137

JD Edwards EnterpriseOne Subcontract Management Reports: A to Z...138

JD Edwards EnterpriseOne Subcontract Management Selected Reports...140

R43050 - F4305 Logs Report...141

Processing Options for F4305 Logs Report (R43050)...141

R43535 - Order Revisions History Report...141

Processing Options for Order Revisions History Report (R43535)...142

R4401P – Print Subcontracts Report...142

Processing Options for Print Subcontracts Report (R4401P)...142

R44425 - Detailed Status Report by Supplier...143

Processing Options for Status Report by Supplier (R44425)...143

R44440 - AIA Application for Payment...144

Processing Options for AIA Application for Payment (R44440)...144

Glossary of JD Edwards EnterpriseOne Terms...147

(11)

JD Edwards EnterpriseOne implementation guides provide you with the information that you need to implement and use JD Edwards EnterpriseOne applications from Oracle.

This preface discusses:

• JD Edwards EnterpriseOne application prerequisites. • Application fundamentals.

• Documentation updates and downloading documentation. • Additional resources.

• Typographical conventions and visual cues. • Comments and suggestions.

• Common fields in implementation guides.

Note. Implementation guides document only elements, such as fields and check boxes, that require additional

explanation. If an element is not documented with the process or task in which it is used, then either it requires no additional explanation or it is documented with common fields for the section, chapter, implementation guide, or product line. Fields that are common to all JD Edwards EnterpriseOne applications are defined in this preface.

JD Edwards EnterpriseOne Application Prerequisites

To benefit fully from the information that is covered in these books, you should have a basic understanding of how to use JD Edwards EnterpriseOne applications.

You might also want to complete at least one introductory training course, if applicable.

You should be familiar with navigating the system and adding, updating, and deleting information by using JD Edwards EnterpriseOne menus, forms, or windows. You should also be comfortable using the World Wide Web and the Microsoft Windows or Windows NT graphical user interface.

These books do not review navigation and other basics. They present the information that you need to use the system and implement your JD Edwards EnterpriseOne applications most effectively.

Application Fundamentals

Each application implementation guide provides implementation and processing information for your JD Edwards EnterpriseOne applications.

For some applications, additional, essential information describing the setup and design of your system appears in a companion volume of documentation called the application fundamentals implementation guide. Most product lines have a version of the application fundamentals implementation guide. The preface of each implementation guide identifies the application fundamentals implementation guides that are associated with that implementation guide.

(12)

The application fundamentals implementation guide consists of important topics that apply to many or all JD Edwards EnterpriseOne applications. Whether you are implementing a single application, some combination of applications within the product line, or the entire product line, you should be familiar with the contents of the appropriate application fundamentals implementation guides. They provide the starting points for fundamental implementation tasks.

Documentation Updates and Downloading Documentation

This section discusses how to: • Obtain documentation updates. • Download documentation.

Obtaining Documentation Updates

You can find updates and additional documentation for this release, as well as previous releases, on Oracle’s PeopleSoft Customer Connection website. Through the Documentation section of Oracle’s PeopleSoft Customer Connection, you can download files to add to your Implementation Guides Library. You’ll find a variety of useful and timely materials, including updates to the full line of JD Edwards EnterpriseOne documentation that is delivered on your implementation guides CD-ROM.

Important! Before you upgrade, you must check Oracle’s PeopleSoft Customer Connection for updates to the

upgrade instructions. Oracle continually posts updates as the upgrade process is refined.

See Also

Oracle’s PeopleSoft Customer Connection, http://www.oracle.com/support/support_peoplesoft.html

Downloading Documentation

In addition to the complete line of documentation that is delivered on your implementation guide CD-ROM, Oracle makes JD Edwards EnterpriseOne documentation available to you via Oracle’s website. You can download PDF versions of JD Edwards EnterpriseOne documentation online via the Oracle Technology Network. Oracle makes these PDF files available online for each major release shortly after the software is shipped.

See Oracle Technology Network, http://www.oracle.com/technology/documentation/psftent.html

Additional Resources

The following resources are located on Oracle’s PeopleSoft Customer Connection website:

Resource Navigation

Application maintenance information Updates + Fixes

(13)

Resource Navigation

Interactive Services Repository Support, Documentation, Interactive Services Repository

Hardware and software requirements Implement, Optimize + Upgrade; Implementation Guide; Implementation Documentation and Software; Hardware and Software Requirements

Installation guides Implement, Optimize + Upgrade; Implementation Guide; Implementation Documentation and Software; Installation Guides and Notes

Integration information Implement, Optimize + Upgrade; Implementation Guide; Implementation Documentation and Software; Pre-Built Integrations for PeopleSoft Enterprise and JD Edwards EnterpriseOne Applications

Minimum technical requirements (MTRs) Implement, Optimize + Upgrade; Implementation Guide; Supported Platforms

Documentation updates Support, Documentation, Documentation Updates

Implementation guides support policy Support, Support Policy

Prerelease notes Support, Documentation, Documentation Updates,

Category, Release Notes

Product release roadmap Support, Roadmaps + Schedules

Release notes Support, Documentation, Documentation Updates,

Category, Release Notes

Release value proposition Support, Documentation, Documentation Updates, Category, Release Value Proposition

Statement of direction Support, Documentation, Documentation Updates, Category, Statement of Direction

Troubleshooting information Support, Troubleshooting

Upgrade documentation Support, Documentation, Upgrade Documentation and Scripts

Typographical Conventions and Visual Cues

This section discusses: • Typographical conventions. • Visual cues.

• Country, region, and industry identifiers. • Currency codes.

(14)

Typographical Conventions

This table contains the typographical conventions that are used in implementation guides:

Typographical Convention or Visual Cue Description

Bold Indicates PeopleCode function names, business function

names, event names, system function names, method names, language constructs, and PeopleCode reserved words that must be included literally in the function call.

Italics Indicates field values, emphasis, and JD Edwards

EnterpriseOne or other book-length publication titles. In PeopleCode syntax, italic items are placeholders for arguments that your program must supply.

We also use italics when we refer to words as words or letters as letters, as in the following: Enter the letter O.

KEY+KEY Indicates a key combination action. For example, a plus sign (+) between keys means that you must hold down the first key while you press the second key. For ALT+W, hold down the ALTkey while you press the W key.

Monospace font Indicates a PeopleCode program or other code example.

“ ” (quotation marks) Indicate chapter titles in cross-references and words that are used differently from their intended meanings.

. . . (ellipses) Indicate that the preceding item or series can be repeated any number of times in PeopleCode syntax.

{ } (curly braces) Indicate a choice between two options in PeopleCode syntax. Options are separated by a pipe ( | ).

[ ] (square brackets) Indicate optional items in PeopleCode syntax.

& (ampersand) When placed before a parameter in PeopleCode syntax, an ampersand indicates that the parameter is an already instantiated object.

Ampersands also precede all PeopleCode variables.

Visual Cues

(15)

Notes

Notes indicate information that you should pay particular attention to as you work with the JD Edwards EnterpriseOne system.

Note. Example of a note.

If the note is preceded by Important!, the note is crucial and includes information that concerns what you must do for the system to function properly.

Important! Example of an important note.

Warnings

Warnings indicate crucial configuration considerations. Pay close attention to warning messages.

Warning! Example of a warning.

Cross-References

Implementation guides provide cross-references either under the heading “See Also” or on a separate line preceded by the word See. Cross-references lead to other documentation that is pertinent to the immediately preceding documentation.

Country, Region, and Industry Identifiers

Information that applies only to a specific country, region, or industry is preceded by a standard identifier in parentheses. This identifier typically appears at the beginning of a section heading, but it may also appear at the beginning of a note or other text.

Example of a country-specific heading: “(FRA) Hiring an Employee”

Example of a region-specific heading: “(Latin America) Setting Up Depreciation”

Country Identifiers

Countries are identified with the International Organization for Standardization (ISO) country code.

Region Identifiers

Regions are identified by the region name. The following region identifiers may appear in implementation guides: • Asia Pacific • Europe • Latin America • North America Industry Identifiers

Industries are identified by the industry name or by an abbreviation for that industry. The following industry identifiers may appear in implementation guides:

(16)

• E&G (Education and Government)

Currency Codes

Monetary amounts are identified by the ISO currency code.

Comments and Suggestions

Your comments are important to us. We encourage you to tell us what you like, or what you would like to see changed about implementation guides and other Oracle reference and training materials. Please send your suggestions to your product line documentation manager at Oracle Corporation, 500 Oracle Parkway, Redwood Shores, CA 94065, U.S.A. Or email us at [email protected].

While we cannot guarantee to answer every email message, we will pay careful attention to your comments and suggestions.

Common Fields Used in Implementation Guides

Address Book Number Enter a unique number that identifies the master record for the entity. An address book number can be the identifier for a customer, supplier, company, employee, applicant, participant, tenant, location, and so on. Depending on the application, the field on the form might refer to the address book number as the customer number, supplier number, or company number, employee or applicant ID, participant number, and so on.

As If Currency Code Enter the three-character code to specify the currency that you want to use to view transaction amounts. This code enables you to view the transaction amounts as if they were entered in the specified currency rather than the foreign or domestic currency that was used when the transaction was originally entered.

Batch Number Displays a number that identifies a group of transactions to be processed by the system. On entry forms, you can assign the batch number or the system can assign it through the Next Numbers program (P0002).

Batch Date Enter the date in which a batch is created. If you leave this field blank, the system supplies the system date as the batch date.

Batch Status Displays a code from user-defined code (UDC) table 98/IC that indicates the posting status of a batch. Values are:

Blank: Batch is unposted and pending approval.

A: The batch is approved for posting, has no errors and is in balance, but

has not yet been posted.

D: The batch posted successfully.

(17)

P: The system is in the process of posting the batch. The batch is unavailable

until the posting process is complete. If errors occur during the post, the batch status changes to E.

U: The batch is temporarily unavailable because someone is working with

it, or the batch appears to be in use because a power failure occurred while the batch was open.

Branch/Plant Enter a code that identifies a separate entity as a warehouse location, job, project, work center, branch, or plant in which distribution and manufacturing activities occur. In some systems, this is called a business unit.

Business Unit Enter the alphanumeric code that identifies a separate entity within a business for which you want to track costs. In some systems, this is called a branch/plant.

Category Code Enter the code that represents a specific category code. Category codes are user-defined codes that you customize to handle the tracking and reporting requirements of your organization.

Company Enter a code that identifies a specific organization, fund, or other reporting entity. The company code must already exist in the F0010 table and must identify a reporting entity that has a complete balance sheet.

Currency Code Enter the three-character code that represents the currency of the transaction. JD Edwards EnterpriseOne provides currency codes that are recognized by the International Organization for Standardization (ISO). The system stores currency codes in the F0013 table.

Document Company Enter the company number associated with the document. This number, used in conjunction with the document number, document type, and general ledger date, uniquely identifies an original document.

If you assign next numbers by company and fiscal year, the system uses the document company to retrieve the correct next number for that company. If two or more original documents have the same document number and document type, you can use the document company to display the document that you want.

Document Number Displays a number that identifies the original document, which can be a voucher, invoice, journal entry, or time sheet, and so on. On entry forms, you can assign the original document number or the system can assign it through the Next Numbers program.

Document Type Enter the two-character UDC, from UDC table 00/DT, that identifies the origin and purpose of the transaction, such as a voucher, invoice, journal entry, or time sheet. JD Edwards EnterpriseOne reserves these prefixes for the document types indicated:

P: Accounts payable documents. R: Accounts receivable documents. T: Time and pay documents. I: Inventory documents. O: Purchase order documents. S: Sales order documents.

(18)

Effective Date Enter the date on which an address, item, transaction, or record becomes active. The meaning of this field differs, depending on the program. For example, the effective date can represent any of these dates:

• The date on which a change of address becomes effective. • The date on which a lease becomes effective.

• The date on which a price becomes effective.

• The date on which the currency exchange rate becomes effective. • The date on which a tax rate becomes effective.

Fiscal Period and Fiscal

Year Enter a number that identifies the general ledger period and year. For manyprograms, you can leave these fields blank to use the current fiscal period and year defined in the Company Names & Number program (P0010).

G/L Date (general ledger

date) Enter the date that identifies the financial period to which a transaction will beposted. The system compares the date that you enter on the transaction to the fiscal date pattern assigned to the company to retrieve the appropriate fiscal period number and year, as well as to perform date validations.

(19)

Management Preface

This preface discusses:

• JD Edwards EnterpriseOne products.

• JD Edwards EnterpriseOne application fundamentals.

JD Edwards EnterpriseOne Products

This implementation guide refers to these JD Edwards EnterpriseOne products from Oracle: • JD Edwards EnterpriseOne Job Cost.

• JD Edwards EnterpriseOne Work Orders. • JD Edwards EnterpriseOne Procurement. • JD Edwards EnterpriseOne Accounts Payable. • JD Edwards EnterpriseOne General Accounting. • JD Edwards EnterpriseOne Address Book.

• JD Edwards Project and Government Contract Accounting.

JD Edwards EnterpriseOne Application Fundamentals

Additional, essential information describing the setup and design of the system appears in a companion volume of documentation called JD Edwards EnterpriseOne Inventory Management 9.0 Implementation Guide. Customers must conform to the supported platforms for the release as detailed in the JD Edwards EnterpriseOne minimum technical requirements. In addition, JD Edwards EnterpriseOne may integrate, interface, or work in conjunction with other Oracle products. Refer to the cross-reference material in the Program Documentation at http://oracle.com/contracts/index.html for Program prerequisites and version cross-reference documents to assure compatibility of various Oracle products.

See Also

JD Edwards EnterpriseOne Inventory Management 9.0 Implementation Guide, "JD Edwards EnterpriseOne

(20)

(21)

Getting Started with JD Edwards EnterpriseOne

Subcontract Management

This chapter discusses:

• JD Edwards EnterpriseOne Subcontract Management overview. • JD Edwards EnterpriseOne Subcontract Management integrations. • JD Edwards EnterpriseOne Subcontract Management implementation.

JD Edwards EnterpriseOne Subcontract

Management Overview

You use the JD Edwards EnterpriseOne Subcontract Management system from Oracle to manage the day-to-day and long-term details of contracts, payments, and commitments that are associated with jobs. In addition, you can perform any of the following tasks with the JD Edwards EnterpriseOne Subcontract Management system: • Create and maintain contracts for the subcontractors on the jobs.

• Establish payment guidelines and make payments against the contracts.

• Track the costs you have paid against a job and the costs you are committed to in the future. • Make up-to-the-minute inquiries on contract information.

• Input change orders for contract commitments.

• Generate status reports for contracts and commitments. • Create base agreements for contracts.

When you create a new contract, you enter subcontractor information, the work to be done, contract commitments, dates, log items, and so on. After you enter a contract, you can change the base agreement details, enter commitment change orders, and track the completion of submittals and transmittals.

You can then enter and release progress payments, or hold progress payments. Progress payments are payments that you make to the subcontractors as they make progress against their jobs.

The JD Edwards EnterpriseOne Subcontract Management system has many features to help you manage contracts. The system helps you to manage contacts, commitments, and to process payments.

(22)

Contracts

You create contracts for the subcontractors on jobs. Contracts specify details such as the contractor information, work to be done, contract commitments, dates, log items, such as submittals and transmittals, and so on. A submittal is information a subcontractor must provide to you. A transmittal is information you must provide to a subcontractor. The JD Edwards EnterpriseOne Subcontract Management system offers you these features to make the work with contracts as efficient as possible:

Contract Features Description

Multiple contract types You can manage a variety of contract types, including: • Construction contracts

• Maintenance contracts • Professional service contracts • Fabrication contracts

• Encumbered cost contracts

Base agreement processing You can create base agreements. A base agreement enables you to set up various jobs so that you do not have to specify distribution commitments for each job individually. This will help you manage contracts in which you have various categories of jobs, but with jobs in each category having identical costs.

Contract reporting You can process a variety of reports regarding contracts. These reports can indicate:

• Payment status information by supplier, job, or contract. • Log information.

• Unit price information.

• Committed cost information, integrating data from the JD Edwards EnterpriseOne Job Cost and JD Edwards EnterpriseOne Subcontract Management systems.

Change order updating Change orders direct the system to change the amount of money committed to a contract. You can create and update change orders easily. Change orders can stand alone or be rolled into the original contract for payment.

(23)

Contract Features Description

Supplemental data tracking Many contracts require supplemental information in addition to the basic contract information. This information can be in the form of submittals, transmittals, and other user-defined log types. The JD Edwards EnterpriseOne Subcontract Management system provides these capabilities for managing supplemental data:

• You can track the completion and receipt of submittals and transmittals. • You can report on deficient submittal information that is associated with a

contract commitment.

• You can automatically update submittal status and transmittal status

• You can withhold progress payments against a contract on the basis of expired logs.

In addition, you can enter extended textual information regarding supplemental data and run reports about various log entries. You can also set up a model log entry for each contract type on the system, and then copy and revise those models in the actual contracts.

Contract inquiries You can review this contract information:

• Up-to-the-minute payment status details by amount, units, or unit cost. • Online log status details and update.

• Open order details on remaining commitments. • Online budget comparisons.

• Contract searches.

Commitments

A commitment is the money that you designate to pay against a contract. The JD Edwards EnterpriseOne Subcontract Management system provides you with these features to make the work with contract commitments as efficient as possible:

Commitment Feature Description

Automatic audit trails You can maintain an audit trail for committed costs. You can access JD Edwards EnterpriseOne Accounts Payable and JD Edwards EnterpriseOne General Accounting systems for an audit trail of progress payments.

(24)

Commitment Feature Description

User-defined commitment distribution rules You can set up the system for these commitment distribution purposes: • To distribute commitments among multiple jobs within a contract. • To establish user-defined cost types per contract type.

• To establish multiple account distributions per contract type. • To track change order.

Tax capabilities You can assess a number of taxes on progress payments, including: • Sales

• Use • Value added

The JD Edwards EnterpriseOne Subcontract Management system also creates journal entries for the JD Edwards EnterpriseOne General Accounting and JD Edwards EnterpriseOne Job Cost systems and updates tax files.

Payment Processing

You process payments against the contracts as the subcontractors make progress against their jobs. Payments are charged against the committed money for a contract. The JD Edwards EnterpriseOne Subcontract Management system offers many features you can use to process progress payments, including:

Payment Processing Feature Description

Flexible pricing methods for commitments. You can use these pricing methods for the contract commitments: • Lump sum, where the contract price is fixed.

• Unit price, where the contract price is based on the number of units completed.

(25)

Payment Processing Feature Description

Payment options. You can use these options when you process the progress payments: • Joint payment handling and alternate payees.

• Partial payments.

• Multiple concurrent payment runs.

• Payment release by due date, payment status, or job.

• Processing of back charges and extras in addition to the committed amount

Efficient progress payments. The JD Edwards EnterpriseOne Subcontract Management system helps you manage the progress payments by:

• Issuing a warning if there are log requirements that have not been met when you try to enter a progress payment voucher.

• Providing quick access to log status information. • Processing retainage amounts as percentage or flat rates.

• Handling retainage and discount information on the same pay request. • Performing both partial and full retainage releases.

• Providing an American Institute of Architects payment document that you can print and use for future progress payments.

JD Edwards EnterpriseOne Subcontract Management

Integrations

The JD Edwards EnterpriseOne Subcontract Management system integrates with these JD Edwards EnterpriseOne systems from Oracle:

• JD Edwards EnterpriseOne Job Cost

• JD Edwards EnterpriseOne Change Management • JD Edwards EnterpriseOne Work Orders

• JD Edwards EnterpriseOne Procurement • JD Edwards EnterpriseOne Accounts Payable • JD Edwards EnterpriseOne General Accounting • JD Edwards EnterpriseOne Address Book

JD Edwards EnterpriseOne Job Cost

The JD Edwards EnterpriseOne Subcontract Management system automatically updates committed units and amounts to accounts in the JD Edwards EnterpriseOne Job Cost system. You can manage the contract budgets and cost projections through the JD Edwards EnterpriseOne Job Cost system.

(26)

JD Edwards EnterpriseOne Change Management

You can access the JD Edwards EnterpriseOne Change Management system to review the details of a change request that is associated with a contract. You can also transfer the details of a change request to the JD Edwards EnterpriseOne Subcontract Management system. The contract number provides the link between a contract and its associated change requests.

JD Edwards EnterpriseOne Work Orders

You can link line item commitments on the Subcontract Entry form to a work order in the JD Edwards EnterpriseOne Work Orders system. Costs from the line item are automatically charged against the work order in the JD Edwards EnterpriseOne Job Cost system, the JD Edwards EnterpriseOne Subcontract Management system, and the JD Edwards EnterpriseOne General Accounting system.

JD Edwards EnterpriseOne Procurement

The JD Edwards EnterpriseOne Subcontract Management system shares a common database with the JD Edwards EnterpriseOne Procurement system. You can use these links to view the purchase orders and contract commitments that are related to a project from one inquiry form and through the same commitment ledger. Both systems also release commitments in the same manner through the JD Edwards EnterpriseOne Accounts Payable system.

JD Edwards EnterpriseOne Accounts Payable

The JD Edwards EnterpriseOne Accounts Payable system automatically updates the appropriate accounts payable records when you enter progress payments, release retainage, or make payments against a contract. Retainage is a percentage of the contract amount that is held until a specified date after the completion of the work. You can also complete other accounts payable tasks from the JD Edwards EnterpriseOne Subcontract Management system, such as designating joint or alternate payees.

JD Edwards EnterpriseOne General Accounting

The JD Edwards EnterpriseOne Subcontract Management system automatically updates the general ledger in the JD Edwards EnterpriseOne General Accounting system when you create payment vouchers for contracts. All audit trails for JD Edwards EnterpriseOne Subcontract Management vouchers and payments are maintained in the general accounting ledgers.

JD Edwards EnterpriseOne Address Book

The JD Edwards EnterpriseOne Subcontract Management system accesses the JD Edwards EnterpriseOne Address Book system for the addresses of suppliers, subcontractors, and business owners. You can use this information to print payments, reports, and so on. You can access JD Edwards EnterpriseOne Address Book from a JD Edwards EnterpriseOne Subcontract Management inquiry form to find specific subcontractors.

JD Edwards EnterpriseOne Subcontract Management

Implementation

This section provides an overview of the steps that are required to implement the JD Edwards EnterpriseOne Subcontract Management system.

In the planning phase of the implementation, take advantage of all sources of information, including the installation guides and troubleshooting information. A complete list of these resources appears in the preface in About This Documentation with information where to find the most current version of each.

(27)

When determining which electronic software updates (ESUs) to install for JD Edwards EnterpriseOne Subcontract Management, use the EnterpriseOne and World Change Assistant. EnterpriseOne and World Change Assistant, a Java-based tool, reduces the time required to search and download ESUs by 75 percent or more and enables you to install multiple ESUs at one time.

See JD Edwards EnterpriseOne Tools 8.98 Software Update Guide

For information about the Oracle Business Accelerator solution for implementation of JD Edwards EnterpriseOne Subcontract Management, review the documentation available.

See http://www.peoplesoft.com/corp/en/iou/implement/rapid_start/rapid_start_prtr_notes.jsp

Global Implementation Steps

This table lists the global implementation steps for JD Edwards EnterpriseOne Subcontract Management:

Step Reference

1. Set up global user-defined codes (UDCs). JD Edwards EnterpriseOne Tools 8.98 System

Administration Guide, “Working with User Defined Codes” 2. Set up fiscal date patterns, companies, and business

units.

JD Edwards EnterpriseOne Financial Management Application Fundamentals 9.0 Implementation Guide, "Setting Up Organizations"

3. Set up next numbers. JD Edwards EnterpriseOne Financial Management Application Fundamentals 9.0 Implementation Guide, "Setting Up Next Numbers"

4. Set up accounts. JD Edwards EnterpriseOne Financial Management Application Fundamentals 9.0 Implementation Guide, "Creating the Chart of Accounts"

5. Set up General Accounting constants. JD Edwards EnterpriseOne General Accounting 9.0 Implementation Guide, "Setting Up the General Accounting System," Setting Up Constants for General Accounting 6. Set up multicurrency processing, including currency

codes and exchange rates.

JD Edwards EnterpriseOne Multicurrency Processing 9.0 Implementation Guide, "Setting Up General Accounting for Multicurrency Processing"

7. Set up ledger type rules. JD Edwards EnterpriseOne General Accounting 9.0 Implementation Guide, "Setting Up the General Accounting System," Setting Up Ledger Types for General Accounting 8. Enter address book records. JD Edwards EnterpriseOne Address Book 9.0

Implementation Guide, "Entering Address Book Records" 9. Set up default location and printers. JD Edwards EnterpriseOne Tools 8.98 Development Tools:

Report Printing Administration Technologies Guide, “Working with Report Printing Administration” 10. Set up branch/plant constants. JD Edwards EnterpriseOne Inventory Management

9.0 Implementation Guide, "Setting Up the Inventory Management System," Defining Branch/Plant Constants

(28)

11. Set up manufacturing and distribution AAIs. JD Edwards EnterpriseOne Inventory Management 9.0 Implementation Guide, "Setting Up the Inventory Management System," Setting Up AAIs in Distribution Systems

12. Set up document types. JD Edwards EnterpriseOne Inventory Management 9.0 Implementation Guide, "Setting Up the Inventory Management System," Setting Up Document Type Information

13. Set up shop floor calendars. JD Edwards EnterpriseOne Shop Floor Management 9.0 Implementation Guide, "Setting Up Shop Floor Management," Understanding Shop Floor Calendar Setup

JD Edwards EnterpriseOne Subcontract Management

Implementation Steps

This table lists the application-specific implementation steps for the JD Edwards EnterpriseOne Subcontract Management system:

1. Set up the procurement system, projects or jobs, and

commitments. Chapter 2, "Setting Up Subcontract Management," page 9 2. Set up suppliers. Chapter 3, "Setting Up Suppliers," page 19

(29)

Setting Up Subcontract Management

This chapter provides an overview of system setup and discusses how to: • Set up projects or jobs.

• Set up commitments.

• Convert data to the Log Master table.

Understanding System Setup

Before you use the JD Edwards EnterpriseOne Subcontract Management system, you must define setup information. Much of the defining of setup information for the JD Edwards EnterpriseOne Subcontract Management system is performed within the JD Edwards EnterpriseOne Procurement system and other EnterpriseOne systems.

This information directs the system to accommodate specific business needs. For example, you must define the purchasing cycle through which the system processes each order type that you use (requisitions, blanket orders, purchase orders).

This section discusses:

• JD Edwards EnterpriseOne Procurement system setup. • Other system setup.

• AAI tables for the financial system.

JD Edwards EnterpriseOne Procurement System Setup

You set up this information for the JD Edwards EnterpriseOne Procurement system:

Order Line Types

You must define codes that determine how the system processes a detail line on an order. You can also enable additional functionality such as subcontract retention, expense at voucher match, and service units.

See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Defining Order Line Types.

Order Activity Rules

You must establish the sequence of steps in the purchasing cycle through which the system processes each order. See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Setting Up Order Activity Rules.

(30)

Constants

You must define constants for these types of default information:

• Branch/plant constants control daily transactions within a branch/plant.

• Item availability constants define how the system calculates the quantity of items available at a branch/plant. • System constants provide default information that applies throughout the system.

• Batch control constants determine whether an application requires management approval and batch control. See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Setting Up Procurement Constants.

Automatic Accounting Instructions

You must set up automatic accounting instructions (AAIs) to determine the general ledger accounts for which the system creates journal entries for purchasing transactions.

See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Setting Up AAIs.

Tolerance Rules

You can create tolerance rules to specify the number or percentage by which the quantity, unit cost, and extended amount can change on a detail line.

See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Creating Tolerance Rules.

Order Hold Information

You can set up information that the system uses to place orders on hold.

See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Setting Up Order Hold Information.

Landed Costs

You can set up landed costs to specify costs that exceed the purchase price of an item, such as delivery charges, broker fees, and so forth.

See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Setting Up Landed Costs.

Nonstock Items

You can set up information for items that you do not account for as part of the inventory.

See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Setting Up Nonstock Items.

Purchase Order Templates

You can set up templates for use during purchase order entry. Templates contain items that you frequently order from a supplier.

See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Setting Up Templates for Purchase Orders.

(31)

Model Logs

You can set up model logs for use during log creation. Model logs contain items that you frequently use in a log. See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Creating Model Logs.

Other System Setup

You set up this information in other systems, including the JD Edwards EnterpriseOne Inventory Management system and the JD Edwards EnterpriseOne General Accounting system:

Messages

You can predefine messages to attach to orders.

See JD Edwards EnterpriseOne Inventory Management 9.0 Implementation Guide, "Setting Up the Inventory Management System," Setting Up Messages.

See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Defining Print Messages.

Default Location and Printers

You can define default information for a specified user or workstation terminal, including a branch/plant, an approval route, and a printer output queue.

See JD Edwards EnterpriseOne Inventory Management 9.0 Implementation Guide, "Setting Up the Inventory Management System," Setting Up Default Location Information.

Next Numbers

You can use the next numbers facility to automatically assign the next available number to document types and address book numbers.

See JD Edwards EnterpriseOne Financial Management Application Fundamentals 9.0 Implementation Guide, "Setting Up Next Numbers".

Tax Processing

You must set up tax processing information for the system.

User-Defined Codes

You can set up user-defined codes (UDCs) to customize each system in the environment.

Item Cross-References

You can define item cross-reference numbers to link the internal item numbers to alternate item numbers, such as those maintained by the suppliers.

See JD Edwards EnterpriseOne Financial Management Application Fundamentals 9.0 Implementation Guide, "Setting Up Next Numbers".

AAI Tables for the Financial System

Eight categories of AAIs relate to the JD Edwards EnterpriseOne Subcontract Management system. Each of these categories has a unique prefix that defines the way it is used in the system.

(32)

• Freight distribution (PCFRTD)

Use this AAI to determine which account to use when you enter freight distribution. • Non-billable retainage (PCNBRT)

Use this AAI to determine which account to use for nonbillable retainage. • Retainage payables (PCRETN)

Use this AAI to determine which retention payable account to use when you create contracts that include retainage.

• Deferred VAT tax payables (PCVATP)

Use this AAI to determine the account for deferred value-added tax (VAT) payables. This AAI applies only when the VAT tax processing option is set and you use a tax type of C or V.

• Deferred VAT tax recoverables (PTVATD)

Use this AAI to determine the account for deferred VAT recoverables. This AAI applies only when the VAT tax processing option is on and you use a tax type of C or V.

• Default cost types (objects) (CD)

Use this AAI to specify the default cost type (object) for purchase order detail lines that are left blank. • Specific contract cost types (CT)

Use this AAI to determine the cost types (objects) that are allowed for contracts. • Range of contract cost types (CR)

Use this AAI to determine a range of valid cost types for contracts.

See JD Edwards EnterpriseOne Financial Management Application Fundamentals 9.0 Implementation Guide, "Setting Up Automatic Accounting Instructions".

AAIs for Freight Distribution (PCFRTD)

Use this AAI to determine which account to use when you enter freight distribution.

You must define the PCFRTD AAI before the Voucher Match program (P4314) can process freight distribution.

AAIs for Non-Billable Retainage (PCNBRT)

Use this AAI to determine which account to use for nonbillable retainage.

You must define the PCNBRT AAI before the Progress Payments program (P4314) can process vouchers with nonbillable retainage.

AAIs for Retainage Payables (PCRETN)

Use this AAI to determine which retention payable account to use when you are creating contracts that include retainage.

If you do not specify a company, the system uses the default company number (00000). You should set the default company account as the account most commonly used by companies on the system. Then you only need to set up distinct PCRETN AAIs for companies with different accounts.

Retainage records that are created on the Progress Payments form require the object account associated with the PCRETN AAI to hold retained balances. You must define the PCRETN AAI before the Progress Payments (P4314) program can create retainage vouchers.

(33)

AAIs for VAT Payables (PCVATP)

Use this AAI to determine the account for deferred VAT payables. If you do not set up this AAI, the general ledger post ignores the deferred VAT when both of these statements are true:

• The processing option for VAT with retainage is set. • You use a tax type of C or V.

If you do not specify a company, the system uses the default company number (00000). You should set the default company account as the account most commonly used by companies on the system. Then you need to set up distinct PCVATP AAIs only for companies with different accounts.

When you release retainage, this AAI reverses debits and credits with the PTVATD AAI.

AAIs for VAT Recoverables (PTVATD)

Use this AAI to determine the account for deferred VAT recoverables. If you do not set up this AAI, the general ledger post ignores the deferred VAT when both of these statements are true:

• The processing option for VAT tax with retainage is set. • You use a tax type of C or V.

You must follow these guidelines on the AAIs form when you set up the PTVATD AAIs: • You must specify a business unit and an object account.

• You can specify a company.

If you do not specify a company, the system uses the default company number (00000). You should set the default company account as the account most commonly used by companies on the system. Then you need to set up distinct PTVATD AAIs only for companies with different accounts.

When you release retainage, this AAI reverses debits and credits with the PCVATP AAI.

AAIs for Default Cost Types (CD)

Use this AAI to determine the default cost types (objects) for the contracts. You must follow these guidelines when you set up CD AAIs:

• The first two characters must be CD.

• The second two characters indicate the contract type, such as OS and OP. You must create a separate CD AAI for each contract type. You must also define the contract types in the UDC table for document types (00/DT). • Do not assign company, business unit, or subsidiary to the CD AAIs.

If you define a CD AAI for a contract type, the system automatically supplies the cost type associated with the CD AAI.

AAIs for Specific Contract Cost Types (CT)

Use this AAI to determine the allowable cost types (objects) for the contracts. You must follow these guidelines when you set up CT AAIs:

• The first two characters must be CT.

(34)

You must create a separate CT AAI for each contract type. You must also define the contract types in the UDC table for document types (00/DT).

• The last two characters must be a numeric value from 01 to 99.

This value uniquely identifies each valid cost type within the contract type. • Do not assign company, business unit, or subsidiary to the CT AAIs.

If you define more than one CT AAI for a contract type, the system does not supply a cost type. You must enter a cost type for each commitment. The system compares the cost type that you enter against the CT AAIs for the contract type to ensure that the cost type is valid.

AAIs for a Range of Contract Cost Types (CR)

Use this AAI to determine a range of valid cost types for the contracts. You must follow these guidelines when you set up CR AAIs:

• The first two characters must be CR.

• The second two characters indicate the contract type, such as OS and OP.

You must also define the contract types in the UDC table for document types (00/DT). If you use base agreements, you must set up a range of CR AAIs for the base agreement contract types. For example, if the base agreement contract type is defined as BC, you must set up a CRBCxx range of AAIs.

• The last two characters must be a numeric value from 01 to 99.

These values must always occur in sequential pairs that represent ranges. For example, CROP01 is associated with CROP02, CROS97 is associated with CROS98, and so on.

• Do not assign company, business unit, or subsidiary to the CR AAIs.

When you enter a cost type for the contracts, the system first compares it to the CT AAIs and then to the CR AAIs to ensure that the cost type is valid.

Setting Up Projects or Jobs

Before you use the JD Edwards EnterpriseOne Subcontract Management system, you should set up the project or job information in the JD Edwards EnterpriseOne Job Cost system. A project is composed of one or more jobs. When you set up a job, you include information regarding the work to be done. When you set up a project, you include the details of the overall project and the details of each job within the project. After you enter the project or job information, you can use the JD Edwards EnterpriseOne Subcontract Management system to create and maintain contracts for each of the subcontractors on jobs.

You can customize the project or job information to the business needs. Consider these examples: • You are contracted to build an office building. The office building is the project, and each floor is a

separate job.

• You are contracted to build the houses in a subdivision. The subdivision is the project, and each house is a separate job.

You must first create a job master record for each of the projects or jobs. If you set up a project, you must also set up each of the jobs within the project.

(35)

After you set up the projects or jobs, you must set up a cost code structure for each job. A cost code structure is a list of all of the accounts that apply to a job. You use the chart of accounts to track and manage all of the costs that are associated with a job.

For example, assume that you are contracted to construct an office building. You must first create a master record for the entire office building. You can then set up the jobs in the building. In this case, you set up each floor of the building as a separate job. After you set up the jobs, you set up the cost code structure for each job. For example, the cost code structure for the third-floor job might include accounts for plumbing, drywall, electrical, and so on.

You can also set up multiple jobs within a company at the same time.

Creating a Job Master Record

Before you use the JD Edwards EnterpriseOne Subcontract Management system, create a job master record for each of the projects or jobs. A job master record includes basic identifying information about the project or job.

Setting Up Jobs Within a Project

After you create a job master record for a project, you must set up the jobs within the project. For example, if the project is an office building, you might set up each floor of the building as a separate job.

Assume that you set up job number 6000 for the office-building project. You should set up the floor 1 job as job 6001, the floor 2 job as job 6002, the floor 3 job as job 6003, and so on.

Creating the Cost Code Structure

After you set up jobs, you must create a cost code structure for each job in the JD Edwards EnterpriseOne Job Cost system. A cost code structure is a list of all of the cost codes and cost types that apply to a job.

You use the cost code structure to track and manage all of the costs that are associated with a job. For example, the cost code structure for the floor 1 job might include accounts for plumbing, drywall, electrical, and so on.

See Also

JD Edwards EnterpriseOne Job Cost 9.0 Implementation Guide, "Setting Up Jobs," Setting Up Job Master

Records

JD Edwards EnterpriseOne Job Cost 9.0 Implementation Guide, "Setting Up Cost Code Structures," Creating

Cost Code Structures

JD Edwards EnterpriseOne Job Cost 9.0 Implementation Guide, "Entering Budgets and Scheduling Jobs,"

Entering Cost Code Schedules

Setting Up Commitments

This section provides overviews of commitments, commitment tracking, and commitment relief, and discusses how to:

• Set up commitment tracking. • Set up commitment relief.

(36)

See Also

Chapter 5, "Working with Commitments," page 65

Chapter 5, "Working with Commitments," Reviewing Commitment Information for Subcontracts, page 69

JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Using Receipt Processing,"

Reviewing Journal Entries for Receipt Transactions

JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Creating Vouchers,"

Reviewing and Posting Journal Entries for Voucher Transactions

JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Using Receipt Processing"

Understanding Commitments

A commitment is the recognition of a future obligation. Each time you enter a subcontract order detail line, you can have the system track the amount that you are obligated to pay and apply it to a job or project. You can monitor individual commitments for a job or project to verify the types of subcontracts being made. You can review the total commitment amount for a job or project to verify that it does not exceed the budget. When you create progress payments, you can have the system relieve commitments. To do this, the system subtracts the individual commitment amount from the total commitment amount for the job or project. You can also have the system:

• Create an audit trail in the P.O. Detail Ledger File - Flexible Version table (F43199). • Recalculate amounts in the account balance ledgers.

Understanding Commitment Tracking

You can set up commitment tracking to monitor subcontract obligations for a specific job or project. Each time you enter a subcontract detail line, the system recognizes the amount on the line as a commitment. You can review individual commitments and the total amount of outstanding commitments for a specific job or project. Commitment tracking applies only to purchases for nonstock items and services (subcontracts). You must charge each detail line to a general ledger account number. The business unit component of the general ledger account number represents the job or project for which you are tracking commitments.

For a detail line to be eligible for commitment tracking, it must be associated with an order type that is listed in UDC 40/CT and it must have a line type with an Inventory Interface code of A or B. These codes indicate that the line is charged directly to a general ledger account number.

See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up the Procurement System," Defining Order Line Types.

Each time you enter a subcontract detail line for which commitment tracking is applicable, the system records the amount in the purchase amount (PA) ledger and the purchase unit (PU) ledger.

The PA ledger contains committed subcontract amounts. The PU ledger contains committed subcontract units.

See Also

JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Setting Up Purchase Order

(37)

Understanding Commitment Relief

When you create progress payments, you can have the system relieve the corresponding commitment amount. To relieve a commitment, the system subtracts the individual commitment amount from the total commitment amount for the job or project.

You set up commitment relief to determine whether the system relieves commitments automatically. The system relieves commitments when you post vouchers generated from progress payments to the general ledger.

Important! When completing commitment relief, the Job Cost Projections processing option must be set to

No if you are in a nonjob cost environment.

Note. The default value in the Job Cost Projections processing option is Yes.

Form Used to Set Up Commitments

Form Name FormID Navigation Usage

Job Cost Constants W0026A Subcontract Setup/Rebuild (G43D411), Commitment Relief Constants

On the Work with Job Cost Constants form, click Add.

Set up commitment relief to determine whether the system relieves

commitments automatically.

Setting Up Commitment Tracking

You specify the order types for which the system is to track commitments in UDC 40/CT. For example, if you want the system to track commitments on orders and requisitions, you must specify these order types.

See JD Edwards EnterpriseOne Tools 8.98 System Administration Guide

Setting Up Commitment Relief

Access the Job Cost Constants form.

Commitment Relief Enter an option that specifies whether the system automatically relieves open commitments when you post accounts payable vouchers to the general ledger. These vouchers are related to noninventory purchase orders and contract progress payments.

Consider selecting this option to relieve commitments automatically when you post progress payment vouchers.

Converting Data to the Log Master Table

This section provides an overview of converting data to the Log Master table and discusses how to convert data to the Log Master table.

(38)

Understanding Converting Data to the Log Master Table

You can convert data from the JD Edwards World Subcontract Management system to the JD Edwards EnterpriseOne Subcontract Management system. To do so, you must run two conversion programs. You must first run the TC from F4303 to F4305 program (R894305) and then run the F4303 - F4305 Media Object Conversion program (R894305A). The system stores all the data that you convert in the Log Master table (F4305).

Oracle recommends that after you convert the data, you run all reports using data from the Log Master table (F4305).

Converting Data to the Log Master Table

To convert data to the log master table:

1. Enter BV in the Fast Path field.

2. Enter R894305 in the Batch Application field. 3. Locate and run a version.

4. Enter BV in the Fast Path field.

5. Enter R894305A in the Batch Application field. 6. Locate and run a version.