E1: 43: Repost Committed Costs (R00932) AFTER Purge Prior Year Balance (R09912) Corrupts Account Balance PA Ledgers (Doc ID 2545295.1)

Last updated on MAY 31, 2019

Applies to:

Symptoms

Repost Committed Costs (R00932)

After changing the Subledger on a J Line Type PO, and purging the PA Ledger records from the Account Balances Table (F0902), the Repost Committed Costs (R00932) program restores the wrong Subledger Account to the Account Balances (F0902) table.

This issue should never occur in the production (live) environment. This could only occur if:

• The user is allowed to change the subledger on a previously saved purchase order line.
  • This is a bad practice.
  • If the wrong subledger was entered on the line initially, the line should be canceled and added as a new line.
• After changing the subledger, the user is allowed to delete the active account in production, even though the account is actively being used for new purchase orders.
  • Users should be instructed to not run Purge Prior Year Balance (R09912) on active accounts currently being used for new purchase orders.

Steps to duplicate

1. Create a new account that has never been previously used.
2. Create Purchase Order for the Account for 100.00 and populate Subledger Type A and Subledger 4344 on the order. G/L Date is today’s date. Save the order.
3. Check Commitment Inquiry (P40230A). Amount Committed to Subledger 4344 is 100.00 and G/L Date is today (May 19, 2019)
4. Check the Account Balances (F0902) PA Ledger Record in Databrowser. Period 5 has 100.00 committed for Subledger 4344.
5. You reinquire on the purchase order and enter the PO Detail Revisions screen and change the Subledger from 4344 to 4345. You also change the G/L Date to May 17, 2019. Save the changes.
6. Check Commitment Inquiry (P40230A). May 19 has a +100.00 Commitment and -100.00 Decommitment to Subledger 4344. May 17 has a +100.00 commitment to Subleger 4345.
7. Check the Account Balances (F0902) PA Ledger Record in Databrowser. Period 5 has 0 committed for Subledger 4344. There is a new PA ledger record for Subledger 4345 with 100.00 committed.
8. Now run the Commitment Integrity Report (R40910). There are no Integrity Variances. The Subledger 4344 account has no open amounts and all zeros.
9. On a fat client run the Purge Prior Year Balance (R09912) Report locally
10. Purge the CURRENT Account Balances Table (F0902) PA Ledger records for the account 30.6350.ITALY which will encompass both Subledgers (4344 and 4345). Confirm the records were purged.
11. Now run the Commitment Integrity Report (R40910).
    1. Subledger 4344 has no variance
    2. Subledger 4345 has a 100.00 variance because there is no Account Balances (F0902) record.
12. Now run Repost Committed Costs (R00932).
13. The record that was created was for Subledger 4344 not 4345.
14. Now run the Commitment Integrity Report (R40910).
    1. Subledger 4344 has a variance of 100.00 between F43199 and F0902 because there is a F0902 record for 100.00 that should not be there.
    2. Subledger 4345 has a 100.00 variance because F43199 and F0902 there is no Account Balances (F0902) record.
15. The Subledger Populated on the PO Detail (F4311) Record was 4345, not 4344 which was put in the Account Balances (F0902) table.

Where the issue happens
This has only occurred after deleting the PA Account Ledger records in a test environment. A user would never be allowed to purge an active account ledger record in the production (live) environment when the account is being used for new purchase orders.

Changes

Cause

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