My Oracle Support Banner

E1: 31P: Create PO Ledger Detail (F43199) - Manufacturing - R31P993 Calculates Financial Commitments Incorrectly and Disregards IM Transactions Already Posted (Doc ID 2983850.1)

Last updated on OCTOBER 30, 2023

Applies to:

JD Edwards EnterpriseOne Engineer to Order - Version 9.2 and later
Information in this document applies to any platform.


R31P993 calculates financial commitments incorrectly and disregards WO Material Issued transactions already done and posted. It looks like R31P993 does not check whether the related amounts have been posted or not and it only uses the Planned Amounts from F3102. Instead, the calculation for rebuilding financial commitments should consider the difference between the Planned Amount (Alias: PLAT) and the Actual Amount (Alias: CLAT).

As per 9.2 ETO Implementation Guide:
"The system de-commits financial commitments when the issue transactions for project-related work orders are posted.

When you post material transactions to the general ledger by running the Post General Journal program (R09801), the system relieves the related financial commitments. When the work order number in the sub-ledger field in the Account Ledger table (F0911) identifies the work order as a project work order, the system relieves the financial commitment for the work order."

The issue can be reproduced at will with the following steps:

  1. P4101 / P41026 - Create one project specific parent item (Stk Ty = G, Ln Ty = S), one simple purchased component (Stk Ty = P, Ln Ty = S) and one project specific purchase component (Stk Ty = H, Ln Ty = SC).
  2. P4105 - project specific parent item is set with Sales/Inventory Cost Method 09 – Unit Cost blank.
  3. P4105 – Both purchased components use Sales/Inventory Cost Method 07 – standard costing; 07 Unit Cost of the purchase component # 1 = 50 USD and 07 Unit Cost of the project specific purchase component # 2 = 100 USD.
  4. R30812 / R30835 – Update simulated and frozen standard costs of the purchased components.
  5. P3002 / P3003 - Create BOM / Routing for the parent; both purchased components are set with QNTY = 1 in the BOM.
  6. P31P001 – Create an ETO Job Cost related Project; add a MFG task – shippable WO; Financial Plan and Financial Actuals tabs are blank for MFG task.
  7. P31P001 – Process MFG task; Financial Plan shows the Planned Material (150 USD = 50 + 100) and Planned Labor buckets populated.
  8. P512000A – Job Status Inquiry shows the Open Commit Amount bucket populated for the Material-A1 cost (150 USD).
  9. Databrowser – F4801; both OACM and RACM values = 150 for the shippable WO.
  10. Databrowser – F43199 – one record for ledger type PA is created against the shippable WO, Extended Price = 150 USD.
  11. F3102 – Current Amount and Planned Amount buckets are both populated for A1 Cost Type = 150 USD.
  12. R3482 – Run PRP to generate messages for the existing ETO project.
  13. P3411 – Process the PRP message to create an OP order for the project specific purchased component. For the project specific purchased items, from this point forward, the financial commitment is created and maintained within JDE Procurement system.
  14. P512000A – 2 different records for Open Commit Amounts are created in the Job Status Inquiry: one for 100 USD – Materials (OP order) and one for 50 USD for the Material-A1 bucket.
  15. P40230A – Commitment Inquiry shows the financial commitments for both the OP # generated during step 13 and WO for the shippable task.
  16. Databrowser – F4801; both OACM and RACM values were decreased to 50 USD for the shippable WO.
  17. Databrowser – F43199 – The ledger type PA created against the shippable WO now shows the Extended Price = 50 USD. 2 more records have been created for the corresponding OP # created for the project specific purchased component; the record having the ledger type (LT field) blank also shows the Amount Open = 100 USD.
  18. P31P001 – The shippable task shows the OP # attached in the View Related Orders form.
  19. P31P001 > P31113 – Perform Material issues only for the simple purchased component. Note that the OP for the project specific purchased component is not received yet. In the P31113 screen, make sure to set the Issue 1/0 field to 0 for the second WO parts detail line created against the project specific purchased component.
  20. R31802A – Run Mfg Accounting to create JEs for the IM transaction done for the first purchased component. Note the Batch #.
  21. F3102 – Planned Amount bucket shows 150 USD and Actual Amount bucket shows 50 USD for A1 Cost Type. This is correct. Since 50 USD are in the Actuals now, they are not committed anymore.
  22. P31P301 – Set the Cost Classification by Accounts and add the projects specific accounts for all cost types: material, labor etc.
  23. R31P301 – Rollup the Actual Costs to ETO Project.
  24. P31P001 – Actual values are updated correctly into the project – Financial Actuals shows the Actual Material = 50 USD.
  25. R09801 – Post the MFG Batch (batch Type 0) created by R31802A for IM transaction.
  26. R43199P – Purge existing financial commitments for the current Job Cost Unit.
  27. Databrowser – F43199 – all financial commitments for the related ETO Projects have been deleted.
  28. P512000A – It looks like the commitments are still in place. The related financial commitment for the Material-A1 buckets is now moved from the Open Commit Amount to Actual Amount.
    Total Actual Amount = 50 USD
    Total Open Commit Amount = 100 USD
  29. P40230A - However, checking the Commitment Inquiry, financial commitments are deleted. This is correct.
  30. R31P993 – Rebuild financial commitments for the ETO Project
  31. P512000A / P40230A – Project specific financial commitments are incorrect. Although the 50 USD for the WO purchased material were already issued and uploaded into the Project Actuals and the journal entries were created for the material issue transaction and the batch has been posted through R09801, the financial commitment still shows this value. In this situation, the Actual Amount bucket is updated with the value of 50 USD and the Open Commit Amount bucket is blank, but the Commitment Inquiry still displays the WO material as being committed, with the Total Open Amount = 50 USD. This is wrong! It looks like the R31P993 uses only the value of the Planned Amount from F3102 for the cost type A1. It should calculate the commitment as Planned Amount (Alias: PLAT) – Actual Amount (Alias: CLAT) and it should check whether the related amounts have been posted or not.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.