EAR 9.2: AR Update Process Abends at Step AR_PGG_SERV.MNTCNTL.MWC_MLA Due to Duplicate Insert Violation on Record PS_PG_PENDST_TAO4 After Patch 30473065
(Doc ID 2849695.1)
Last updated on APRIL 07, 2022
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The AR Update process has abended at Step AR_PGG_SERV.MNTCNTL.MWC_MLA, with a unique constrain violation on Record PS_PG_PENDST_TAO4. This is taking place after <Bug 30473065> - (ARUPDATE FAILS FOR MAINTENANCE WORKSHEET AT STEP AR_PGG_SERV.MNTCNTL.MWC_MLA), whose solution was delivered in FSCM 9.2 Image #35, got implemented.
This issue seems to take place in an environment with the below common criteria:
a) The AR Update is being launched for multiple Business Units at the same time, with Maintenance Transactions option selected
b) ChartField Inheritance on the AR/BI Group is enabled for some of the delivered ChartFields (Such as Fund Code)
c) IntraUnit Balancing Entries on the Default Ledger Group has been enabled on some ChartFields (Such as Fund Code)
d) Commitment Control has been enabled for the Billing and Receivables modules
e) At the Receivables Installation options level, the 'No Mult Pending Item Selection' check-box is selected
f) The Maintenance Group ID with the offending Item is present in Business Unit ABC, but another BU XYZ also has a Maintenance Group ID with the same value already processed
The code from the abending Step AR_PGG_SERV.MNTCNTL.MWC_MLA seems to be missing a join by Business Unit.
1.- Log into the FSCM Online Application as a Receivables User
2.- Create a new Regular Deposit under Business Unit US001, with a Payment transaction of 100 USD for Customer ID 12345
3.- Create a Payment Worksheet under Business Unit US001, and place the new Payment into an On Account Item
4.- Launch AR Update with the Payments option selected for Business Unit US001
5.- Confirm that Customer ID 12345 has a new credit Item in its Account
6.- Create a new Maintenance Group on Business Unit US003, and name the Group ID M001
7.- Launch AR Update with the Maintenance Transactions option selected for Business Unit US003
8.- Ensure that Maintenance Group ID M001 is properly processed, and posted
9.- Create a new Pending Item Group under Business Unit US001, define a new Item ID AAAA under Customer ID 12345 for an amount of 100 USD, and place it in Post Action Batch Standard
10.- Launch AR Update with the Pending Items option selected for Business Unit US001
11.- Confirm that Customer ID 12345 has a new Item ID AAAA in its Account
12.- Create a new Maintenance Group under Business Unit US001, name the Group ID M001, and balance off Item ID AAAA (100 USD) against Credit Item (-100 USD), and set Post Action as Batch Standard
13.- Ensure Business Unit US003 has other transactions in Batch Standard status ready for posting as well (Maintenance Groups may be best)
14.- Create a new Run Control ID for AR Update that will have Maintenance Transactions option selected, and will define Business Units US001 and US003
15.- Launch the AR Update process
16.- The AR Update program abends in Error Message due to missing join on delivered codeline from Step AR_PGG_SERV.MNTCNTL.MWC_MLA, because Group ID M001 exists under both Business Units US001 and US003
The abend on AR Update leaves many transactions locked, and in corrupted status, which cannot be further processed. Hence, delaying Maintenance Worksheet application on outstanding Items, Accounting missing, and further integration into General Ledger module.
The AR Update should be able to handle all Maintenance Worksheet scenarios, regardless if multiple Business Units are being processed at the same time, and complete in Success, generating the needed Accounting Entries, and correctly updating the involved Item transactions.
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