See Also

Oracles 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 Oracles 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 Oracles PeopleSoft Customer Connection website:
Resource Application maintenance information Business process diagrams Updates + Fixes Support, Documentation, Business Process Maps Navigation
Resource Interactive Services Repository Hardware and software requirements
Navigation Support, Documentation, Interactive Services Repository Implement, Optimize + Upgrade; Implementation Guide; Implementation Documentation and Software; Hardware and Software Requirements Implement, Optimize + Upgrade; Implementation Guide; Implementation Documentation and Software; Installation Guides and Notes Implement, Optimize + Upgrade; Implementation Guide; Implementation Documentation and Software; Pre-Built Integrations for PeopleSoft Enterprise and JD Edwards EnterpriseOne Applications Implement, Optimize + Upgrade; Implementation Guide; Supported Platforms Support, Documentation, Documentation Updates Support, Support Policy Support, Documentation, Documentation Updates, Category, Release Notes Support, Roadmaps + Schedules Support, Documentation, Documentation Updates, Category, Release Notes Support, Documentation, Documentation Updates, Category, Release Value Proposition Support, Documentation, Documentation Updates, Category, Statement of Direction Support, Troubleshooting Support, Documentation, Upgrade Documentation and Scripts

Installation guides

Integration information
Minimum technical requirements (MTRs) Documentation updates Implementation guides support policy Prerelease notes Product release roadmap Release notes Release value proposition Statement of direction Troubleshooting information Upgrade documentation
Typographical Conventions and Visual Cues
This section discusses: Typographical conventions. Visual cues. Country, region, and industry identifiers. Currency codes.
Typographical Conventions
This table contains the typographical conventions that are used in implementation guides:

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 Automatic audit trails Description 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.
Commitment Feature User-defined commitment distribution rules
Description 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 Flexible pricing methods for commitments. Description 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.
Payment Processing Feature Payment options.
Description 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.

15. Configurator (P3210) 16. Blanket Release (P43216)
17. Logs Entry (P4305) 18. Requisition Self Service (P43E10)
Specify which version the system uses with the Logs Entry program (P4305). Specify which version the system uses with the Requisition Self Service program (P43E10).

Currency

These processing options specify currency information. 1. Tolerance Specify a currency tolerance limit percentage to ensure that the currency amount does not fluctuate by an amount greater than the tolerance percentage as compared with the Currency Exchange Rates table (F0015). If you work with multiple currencies, create a separate version of this program for each currency. The amount that you specify is currency-specific. 2. Currency Code Enter a code to specify the currency in which to view as if amounts. This enables you to view domestic or foreign amounts in a currency other than the currency in which the amounts were originally entered. If you leave this processing option blank, the system displays as if amounts in the currency in which they were originally entered. Note. This works if currency amounts are stored in a temporary memory and are not written to a table. 3. As of Date Specify an as of date for the as if Currency Code processing option. The system uses this date to retrieve the exchange rate from the F0015 table. If you specify a currency for the Currency Code processing option and leave this processing option blank, the system uses the system date. Note. A valid exchange rate between the domestic or foreign currency and the as if currency must exist in the F0015 table, based on the as of date.

Approvals

These processing options specify approval-processing information. 1. Route Code Specify which code the system uses for approval processing. Blank: Do not perform approval processing. 1: Originators address. 2: Originators user profile. 3: Branch/plant route code. 4: Default locations route code. 2. Awaiting Approval Status 3. Approved Status 4. Reapprove Changed Lines Enter the next status for the system to use when the order enters the approval route. Enter the next status for the system to use when the order is automatically approved. Specify the type of modification for which approval processing is activated for a purchase order line that has been approved. Values are:

1: Activate approval processing when any fields for the purchase order line have been modified. 2: Activate approval processing only when certain critical fields, which are activated through the Approval Fields Constants program (P43080), have been modified. 3: Activate approval processing when the standard critical fields have been modified. 5. Approval Hold Code Specify a hold code that the system uses when placing the order on hold for the approval process. If you leave this processing option blank, the system does not place the order on hold.

Budgeting

These processing options specify budgeting information. 1. Budget Hold Code Specify the hold code that the system uses for budget holds. After you enter a hold code, the system activates the budget-checking process. Budget checking ensures that when a detail line exceeds the budget for an account, the system places the entire order on hold. 2. Budget Ledger Type Specify the ledger type that contains the budgets. If you specify a budget ledger type, the system retrieves only that budget ledger type. If you leave this processing option blank, the system retrieves all budget ledger types that were specified in the Ledger Type Master Setup program (P0025) and that are contained in the Ledger Type Master table (F0025). 3. Level of Detail Specify the value (3 through 9) for the level of detail that the system uses during the budget checking process. If you leave this processing option blank, the system uses a default value of 9. Note. You can use this processing option with the processing option for level of detail accumulation. 4. Budget Total Method Specify the method by which the system calculates the budget. Values are: Blank: The system uses the job cost budget calculation method 1: Job cost budget: (Original budget) + (period amounts for the current year) + (prior year postings) 2: Standard financial budget: (Sum of period amounts for the current year) 3: Standard financial spread: (Original budget) + (period amounts for the current year) 5. Period Accumulation Method Specify the time period to use when accumulating the budget. Values are: Blank: Use the total annual budget to accumulate the budget.
1: Accumulate the budget through the current period. 6. Tolerance Percentage 7. Hold Warning Specify the percentage by which the detail line amount can exceed the budget before the system places the order on budget hold. Specify whether the system displays a warning message about detail line amounts that exceed the budget. Values are: Blank: The system does not display a warning, but it does place the order on hold. 1: The system displays a warning and places the order on hold. 2: The system displays a warning, but it does not place the order on hold. 8. Budget Accumulation Level of Detail Specify whether the system uses the value for the Level of Detail processing option (located on the Budgeting tab) to accumulate budget amounts. Values are: Blank: The system uses the value for the Level of Detail processing option. 1: The system accumulates budget amounts starting from the level of detail that has been specified for the purchase order detail line up to the value for the Level of Detail processing option. 9. Exclude Subledger/Type Specify whether the system excludes the subledger and subledger type when validating the budget information. Values are: Blank: The system includes the subledger and subledger type. 1: The system excludes the subledger and subledger type. The system calculates the total of budgets for all subledgers for the detail line account to determine whether the line exceeds the budget. 10. Job Cost Account Sequence Specify the job cost account sequence that the system uses for budgeting. Values are: Blank: The system uses the standard account sequence (for example, cost center, object, and subsidiary). 1: The system uses the job cost sequence (for example, job, cost code, and cost type). 11. Include Taxes Specify whether to include taxes for taxable lines in budget calculations. Values are: Blank: Do not include taxes. 1: Include taxes.

Forms Used to Enter Subcontract Order Header Information
Enter origin information and Subcontract Processing (G43D11), Enter Subcontract delivery instructions for an order. Orders On the Work With Contract Detail form, click Add. Or on the Work With Contract Detail form, select an existing order and click Select. The Contract Header form appears if you have set the processing options to display header information prior to detail information. Enter dates for an order. Enter tax information for an order. Enter user-defined values for additional properties and category codes. See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Entering Purchase Orders," Entering Order Header Information. Specify the print message clauses that are associated with a subcontract order. Enter reference information for an order. The reference information is primarily for informational purposes. Enter delivery instructions for an order or enter reference information, such as a confirmation number, document number, job number for the order, or miscellaneous notes to be printed on the order. View supplier classification codes. See JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Entering Purchase Orders," Entering Additional Order Header Information.

Clauses

W4310K
Select Clauses from the Form menu on the Contract Header form. Select Additional Info from the Form menu on the Contract Header form.
Page Name Order Header - Additional Information II

Definition Name

W4310M
Navigation Usage View supplier classification Subcontract Processing (G43D11), Enter Subcontract codes. Orders See JD Edwards On the Work With Contract EnterpriseOne Procurement Detail form, click Add. Management 9.0 On the Contract Detail form, Implementation Guide, "Entering Purchase Orders," select Additional Info from Entering Additional Order the Form menu. Header Information.
Entering Origin Information and Delivery Instructions for an Order
Access the Contract Header form. To enter origin information and delivery instructions for an order: 1. Complete the Subcontractor, Job, and Ship To fields. 2. From the Form menu, select Additional Info to access the Order Header - Additional Information form. 3. On the Order Header - Additional Information form, complete the Delivery Instructions Line 1 field and click OK. 4. On the Order Header form, click OK. 5. On the Work With Order Details form, click Cancel.

Additional Selection Criteria W43041F
On the Work With Contract Detail form, select Added Selections from the Form menu. On the Work With Contract Detail form, select the detail line and then select Order Detail from the Row menu. On the Work With Contract Detail form, select an order and, from the Row menu, select Change Orders, then View All Chg Order. On the Work With Contract Detail form, select an order and select Order Summary from the Row menu.
Purchase Order Detail Inquiry

W430301C

Order Entry - Summary Order Information

W430114A

Review summary information for an order, including items, account numbers, order quantities, prices, and extended volumes and weights. You can also review the total tax and monetary amount for the entire order.

Page Name Order Recap

W4310C
Navigation On the Work With Contract Detail form, select an order and select Order Recap from the Row menu.
Usage Review a detailed summary of information about an order or change order. For example, you can review information about vouchers, retainage, or changes made to an order. Review the financial status information for an order.
Work With Financial Status Inquiry

W44200A

Subcontract Inquiries (G43D112), Financial Status Inquiry On the Work With Contract Detail form, select an order and select Financial Status from the Row menu.

Supplier Ledger Inquiry

W0411G
On the Work With Financial Status Inquiry form, select Supplier Ledger from the Form menu.
Review voucher information for an order. See JD Edwards EnterpriseOne Accounts Payable 9.0 Implementation Guide, "Processing Accounts Payable Vouchers," Understanding Voucher Processing.

Working with Budgets

This section provides overviews of budget checking, search scenarios for level of detail, budget totaling, and calculations of available budget to date for the fiscal year, and discusses how to: Set processing options for Trial Balance/Ledger Comparison (P09210A). Review the budget.
Understanding Budget Checking
You use budget checking to identify the detail line amounts that exceed the budget for a specific job, project, department, and so forth. Each time you enter or change a subcontract, the system checks the account number for each detail line and compares it to the available budget for the account. If the detail line amount exceeds the available budget amount, the system places the entire subcontract on hold. You can set a budgeting processing option in the Purchase Orders program (P4310) to provide a warning message that a detail line amount exceeds the available budget amount, but the system still places the order on hold. The system stops further processing of the order until you remove the budget hold. You must set up budget hold codes for each business unit. The system calculates available budget amounts by subtracting actual amounts (AA ledger) and committed amounts (PA ledger) from the budget amount that you specify for an account number. The system uses this budget calculation:

Understanding Calculations of Available Budget to Date for the Fiscal Year
Use the Period Accumulation Method processing option to specify how the system calculates the available budget. When you enter 1 for this processing option, the system reviews the fiscal date pattern for the company and determines the current general ledger period. The system then adds the sum of the period budget amounts from period one through the current period. The system uses this amount as the original budget for budget checking. Enter 1 for this processing option only when you enter 2 for the Budget Total Method processing option.
JD Edwards EnterpriseOne Procurement Management 9.0 Implementation Guide, "Processing Approvals," Working with Orders Awaiting Approval JD Edwards EnterpriseOne General Accounting 9.0 Implementation Guide, "Creating Budgets," Entering Annual Budgets
Form Used to Work with Budgets
Form Name Trial Balance / Ledger Comparison FormID

W09210AA

Navigation Subcontract Inquiries (G43D112), Budget Comparison

Usage Review the budget.

Setting Processing Options for Trial Balance / Ledger Comparison (P09210A)
1. Ledger Type 1 Specify the default ledger type 1. Options are in user-defined code (UDC) table 09/LT. If this processing option is left blank, the system uses BA. 2. Ledger Type 2 Specify the default ledger type 2. Options are in UDC 09/LT. If this processing option is left blank, the system uses AA. 3. Exit with Ledger Type Specify the ledger type for the called application to use when exiting to another application. Values are: Blank and 1: Use ledger type 1. 2: Use ledger type 2.
1. Suppress Zero Balances Specify whether to display posting accounts with zero balances. Values are: Blank: Display posting accounts with zero balances.
N: Display. Y: Do not display Note. This processing option applies only to posting accounts. Nonposting header accounts appear on the Trial Balance/Ledger Comparison form (P09210A) regardless of this processing option. 2. Calculation Method Specify the Calculation Method to use when calculating variances. Values are: Blank: Subtraction A: Addition M: Multiplication D: Division S: Subtraction 3. Additional Ledger Type 1 and 4. Additional Ledger Type 2 5. Subledger Specify an additional ledger type to use in calculating account balances for ledger type 1 and ledger type 2. Options are in UDC 09/LT. If this processing option is left blank, no additional ledger type is used. Specify the subledger that the system uses for calculating account balances. Enter * to display all transactions with subledgers. If this processing option is left blank, then the system selects transactions that have no subledgers. 6. Subledger Type Specify the subledger type to use for calculating account balances. Options are in UDC 00/ST. If this processing option is left blank, a blank subledger type is used. 7. Account Level Of Detail Specify the account level of detail to be used (39). If this processing option is left blank, the system uses an account level of 9.

Chapter 9

Progress Payments and Subcontract Vouchers
To make progress payments, you must first create a voucher in the JD Edwards EnterpriseOne Subcontract Management system. Vouchers contain the details of a payment and enable you to create a payment that is drawn against the commitments for a contract. You use vouchers to determine the amount and type of payment that you are processing. Before you can pay a subcontractor, you must create a voucher that: Indicates that the terms of a transaction are met. Specifies the amount to pay the subcontractor. Notifies JD Edwards EnterpriseOne Accounts Payable to cut a check. You can also create vouchers: To withhold a portion of the gross payment as retainage. Retainage is a percentage of a committed amount that is held until after the order is complete. For example, if you create a voucher for 100.00 with retainage of 10 percent, the actual payment is 90.00, with 10.00 held as retainage. You release retainage by entering a payment voucher for the amount that you want to release. See Chapter 9, "Processing Progress Payments," Processing Retainage, page 125. To make progress payments on a contract. For units if you are paying against a unit based order. In a unit-based order, you create payments based on the number of units completed. You should enter either the number of units for which you are paying or the gross payment. The system then calculates the other value based on the price per unit. Progress Payments is a version of the Voucher Match program (P4314). It includes specific information for the JD Edwards EnterpriseOne Subcontract Management system. The system provides a Work With Contracts form on which you can further specify which contracts you want to match. You can select whether to match contracts, receipts, retainage, or all three. You can also access the Subcontract Ledger Inquiry program (P0411) or the Subcontract Order Entry program (P4310). The processing options for P4314 include a Progress Payments tab on which you can specify how the system processes payments. From the Work With Contracts form, you can: Select contracts to pay. Select receipts to pay. Select retainage to release. Specify threshold tolerance. Review subcontract orders. Review the subcontract ledger. Pay using cumulative percentages or amounts. Access log functionality. Note. Set the Option Default processing option on the Progress Payments tab of P4314 to 1 to have the system match the quantity and amount when performing voucher match.
American Institute of Architects (AIA) Application for Payment
The AIA Application for Payment is similar to the American Institute of Architects (AIA) Document G702, titled Application and Certificate for Payment. It is a report that lists base contract and change order commitment amounts in addition to previous amounts that were billed and retained. Additionally, you can print and send the Waiver of Lien form when you send a subcontractor the AIA Application for Payment. The Waiver of Lien states that the subcontractor has been paid and that no outstanding liens are associated with the work on the contract. See Appendix A, "JD Edwards EnterpriseOne Subcontract Management Reports," R44440 - AIA Application for Payment, page 144.

These processing options enable you to enter the version for each application. If you leave any of these processing options blank, the system uses version ZJDE0001. 1. Order Entry (P4310) Specify the version that the system uses when you are using the Order Entry program. When you select a version, review the versions processing options to ensure that the version meets the needs. 2. AP Master Business Function (P0400047) Specify the versions that the system uses when you process accounts payable transactions. You can review versions for this program in the interactive versions list only. When you select a version, review the versions processing options to ensure that the version meets the needs. 3. GL Master Business Function (P0900049) Specify the version that the system uses when you are using the JD Edwards EnterpriseOne General Accounting system. You can review versions for this program in the interactive versions list only. When you select a version, review the versions processing options to ensure that the version meets the needs.
4. Open Receipts Inquiry (P43214)
Specify the version that the system uses when you are using the Open Receipts Inquiry program. When you select a version, review the versions processing options to ensure that the version meets the needs.
5. Stand Alone Landed Cost (P43214)
Specify the version that the system uses when you are using the Standalone Landed Cost program. When you select a version, review the versions processing options to ensure that the version meets the needs.
6. Freight Audit History (P4981) 7. Supplier Ledger Inquiry (P0411) 8. Purchase Order Logs (P4305) 9. Freight Distribution (P43147)
Specify which version of the Voucher Match program (P4314) the system uses for matching freight. Specify the version that the system uses when you use the Supplier Ledger Inquiry program. Specify the version that the system uses when you use the Logs Entry program (P4305). The system uses this version of the P4305 program if UDC 40/VF is activated for 04. Specify the version that the system uses when you use the Freight Distribution program (P43147).
1. Notify Amount Changes and 2. Notify Quantity Changes Specify the person who receives notification. Values are: Blank: Do not send any notification emails. 1: Purchase order originator. 2: Project manager. 3: Buyer. 4: Originator, buyer, and project manager.

Voucher Match with Retainage Job Expense Acct 900 Non-Billable 100 AP Retainage 100 AP Trade 900
Release Retainage Job Expense Acct 100 Non-Billable 100 AP Retainage 100 AP Trade 100
T account changes for nonbillable retainage example
The commitment is not affected because it was already relieved. To facilitate entry of the initial voucher, indicate that retention applies to the purchase order when entering the voucher. In the JD Edwards EnterpriseOne system, you use retainage functionality to automate the recording of retention to nonbillable accounts for transactions with an inventory interface of A and B only. The system uses financial automatic accounting instruction (AAI) PCNBRT for retainage processing during voucher match. To enable the retention functionality in the JD Edwards EnterpriseOne system, you must: 1. Select the Non-Billable Retainage option on the Line Type Constants Revisions form (W40205B). New journal ledger entries are created if this subcontract retention option is selected. 2. Perform two-way voucher match. The system supports multiple partial matches. Note. If you want to perform three-way voucher match, you must select the Expense At Voucher option on the Line Type Constants Revisions form (W40205B). 3. Ensure that the retainage amount is not zero. Before entering an order that includes retention, select the Display Retainage Indicator processing option on the Display tab of the Subcontract Order Entry program (P4310). When you enter an order that has retainage, select the Retainage Indicator check box on the order header form. This field notifies the A/P clerk during the voucher match process to double-check the invoice from the supplier to see if there was an amount retained on the invoice. The Retainage Indicator check box can be used with or without the Retainage Percentage field. Note. When you are using the Purchase Order Generator (P43032), Generate POs from Requisitions/Blanket Order Release (P43060), and Quote Order Release (P43360) programs to release blanket, requisition, and quote orders, the order that is generated contains the retainage indicator value. The value of the Retainage Indicator field is brought over from the source order irrespective of the processing option setting. Note. The system does not support retention in Purchase Order Workbench (P43101), sourcing, electronic data interchange (EDI), XPI, transfer orders, direct ship orders, re-cost voucher, and freight to match. You can display the Retainage Indicator field in the detail grid on the Voucher Match form by setting the Display Retainage Indicator processing option on the Display tab of the Voucher Match program (P4314). The system retrieves the retainage indicator setting from the order header. You also set the processing options on the Retainage tab of the P4314 program. When performing voucher match, you can relieve commitments to billable and nonbillable accounts. The setting of the Non-Billable Retainage option on the Line Type Constants Revisions form determines whether the system uses the new nonbillable automatic accounting instruction (AAI) for retainage. Select this option to specify that the system use the financial AAI nonbillable retainage (PCNBRT) for retainage processing during voucher match. If the Non-Billable Retainage option is not selected, then the system uses the previous functionality for expensing retainage. You select the Voucher Match Variance Account option in the Line Type Constants (P40205) program to indicate to which account the system books a variance. A variance that is generated during voucher match can be booked to a variance account or to the expense account for the order detail line. For three-way voucher match, select both the Non-Billable Retainage and Expense at Voucher options to use a nonbillable expense AAI.

You can release retainage and create a voucher at the same time. The Retainage Indicator field that appears on the form signals the accounts payable clerk to verify whether retainage occurred on the invoice and whether it should be applied to the voucher. The Retainage Indicator field is independent of the Retainage % field, and the system will not require a retainage percentage if the Retainage Indicator option is selected. Thus, the system does not perform any functionality based on the Retainage Indicator field. The commitment is relieved when you are posting a voucher with nonbillable retainage. The system retrieves the nonbillable received not vouchered (RNV) amount from the Purchase Order Detail Non-Billable table (F4317) and adds it to the billable RNV amount (input value from the General Ledger Post program (R09801) when you are posting a voucher with nonbillable retainage. Thus, the system processes voucher match with nonbillable retainage and nonbillable retainage release. During voucher match, the system calculates the billable and nonbillable general ledger amounts, both domestic and foreign amounts. The system uses the following calculations during voucher match: (Billable Amount) = (GL Amount) (1 (Retainage Percent)) (Non-Billable Amount) = (GL Amount) (Billable Amount) The retainage to release amount is computed based on the PO Detail (F4311) level and proportioned to the PO Non-Billable (F4317) level based on percentage. The system uses the following calculations during release retainage: (Released Amount) = (F4317.NonBillableAmount) (Released Percent) (Retained Amount) = (F4317.NonBillableAmount) (Relased Amount) The system also calculates the released percentage when releasing nonbillable retainage. This percentage is required for partial release and rounding issues. The system uses the following calculations for released percentage: (Released Percentage) (Domestic) = (F43121T.RETA) (F4311T.RETA) (Released Percentage) (Foreign) = (F43121T.REFA) (F4311T.REFA) The nonbillable amount is always equal to the retained amount unless you are using B, C, and V tax types. The nonbillable amount is the sum of one or more future billable amounts. When you close an order, the system does not provide a reminder or force payment of any retention. If you reverse a voucher, then the accounting entries are reversed as they were entered. The system performs the following transactions: Updates the Purchase Order Receiver File table (F43121). Reverses F4317 records to update the nonbillable amount. Reverses Purchase Order Receiver Non-Billable table (F43127) records. - Deletes F43127 records that have a match type 3 (reversed by voucher match application). - Updates F43127 records that have match types of 2 (created by voucher match application) and 3 (reversed by voucher match application). See Chapter 2, "Setting Up Subcontract Management," AAI Tables for the Financial System, page 11. See Chapter 9, "Processing Progress Payments," Setting Processing Options for Voucher Match (P4314), page 105.

as if processing as of processing
Auto Commit Transaction back-to-back process batch processing

Glossary

Abbreviation for Business Process Execution Language, a standard web services orchestration language, which enables you to assemble discrete services into an end-to-end process flow. Abbreviation for Business Process Execution Language Process Manager, a comprehensive infrastructure for creating, deploying, and managing BPEL business processes. Configurable settings in a text file that are used by a build program to generate ANT scripts. ANT is a software tool used for automating build processes. These scripts build published business services. An actor that is responsible for building, mastering, and packaging artifacts. Some build engineers are responsible for building application artifacts, and some are responsible for building foundation artifacts. A WIN32 executable that reads build configuration files and generates an ANT script for building published business services. An actor that determines if and why an EnterpriseOne business service needs to be developed. A named set of user-created, reusable business rules and logs that can be called through event rules. Business functions can run a transaction or a subset of a transaction (check inventory, issue work orders, and so on). Business functions also contain the application programming interfaces (APIs) that enable them to be called from a form, a database trigger, or a non-JD Edwards EnterpriseOne application. Business functions can be combined with other business functions, forms, event rules, and other components to make up an application. Business functions can be created through event rules or third-generation languages, such as C. Examples of business functions include Credit Check and Item Availability. See named event rule (NER). EnterpriseOne business logic written in Java. A business service is a collection of one or more artifacts. Unless specified otherwise, a business service implies both a published business service and business service. Source files, descriptors, and so on that are managed for business service development and are needed for the business service build process. A method that accesses resources provided by the business service framework. Configuration files include, but are not limited to, interop.ini, JDBj.ini, and jdelog.properties. A key and value data pair used during orchestration. Collectively refers to both the code and the key cross reference in the WSG/XPI based system. Utility services installed in a BPEL/ESB environment that are used to access JD Edwards EnterpriseOne orchestration cross-reference data. A framework needed by an integration developer to develop and manage business services. Otherwise known as JDeveloper. A collection of artifacts managed by EnterpriseOne LCM tools. Named and represented within EnterpriseOne LCM similarly to other EnterpriseOne objects like tables, views, forms, and so on.

media storage object message center messaging adapter messaging server
Middle-Tier BPEL/ESB Server Monitoring Application

named event rule (NER)

Encapsulated, reusable business logic created using event rules, rather that C programming. NERs are also called business function event rules. NERs can be reused in multiple places by multiple programs. This modularity lends itself to streamlining, reusability of code, and less work. In Brazil, a legal document that must accompany all commercial transactions for tax purposes and that must contain information required by tax regulations. In Brazil, a nota fiscal with invoice information. See also nota fiscal.
nota fiscal nota fiscal factura
Object Configuration Manager (OCM)
In JD Edwards EnterpriseOne, the object request broker and control center for the runtime environment. OCM keeps track of the runtime locations for business functions, data, and batch applications. When one of these objects is called, OCM directs access to it using defaults and overrides for a given environment and user. A repository of all versions, applications, and business functions reusable in building applications. Object Librarian provides check-out and check-in capabilities for developers, and it controls the creation, modification, and use of JD Edwards EnterpriseOne objects. Object Librarian supports multiple environments (such as production and development) and enables objects to be easily moved from one environment to another. A process that blends any modifications to the Object Librarian in a previous release into the Object Librarian in a new release. An interoperability model that enables you to use SQL statements to extract JD Edwards EnterpriseOne data for summarization and report generation. An interoperability model that enables you to set up an interface for JD Edwards EnterpriseOne to pass data to another software package, such as Microsoft Excel, for processing. JD Edwards EnterpriseOne objects are installed to workstations in packages from the deployment server. A package can be compared to a bill of material or kit that indicates the necessary objects for that workstation and where on the deployment server the installation program can find them. It is point-in-time snapshot of the central objects on the deployment server. A software application that facilitates the deployment of software changes and new applications to existing users. Additionally, in JD Edwards EnterpriseOne, a package build can be a compiled version of the software. When you upgrade your version of the ERP software, for example, you are said to take a package build. Consider the following context: Also, do not transfer business functions into the production path code until you are ready to deploy, because a global build of business functions done during a package build will automatically include the new functions. The process of creating a package build is often referred to, as it is in this example, simply as a package build.