My Oracle Support Banner

EAR 9.2: The Correct Transactions Page (AR_CC_TRAN_ERROR) Is Updating the Incorrect Item Sequence When ChartField Accounting Changes Are Saved, Always Affecting Sequence 1 (Doc ID 2647298.1)

Last updated on MARCH 09, 2020

Applies to:

PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

The Revenue Estimate Correct Transactions page (AR_CC_TRAN_ERROR) is always incorrectly updating Item Sequence Number 1, on any saved Accounting ChartField changes for those transactions flagged with Budget Errors, regardless of the Item Sequence Number being updated.

As such, it does not matter if it is Item Sequence Number 5 the one in Budget Status Error, that the changes will be implemented on the Item Sequence Number 1.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as a Receivables User
    2.- Enable Commitment Control for the Accounts Receivable module
    3.- Define a proper Budget Definition for the desired ChartField combination
    4.- Create a new Budget Journal for that ChartField combination, and post the transaction
    5.- Create a new Pending Item Group, with a Debit Item on the affected Business Unit for Commitment Control, and balance the Group
    6.- Manually create the Accounting Entries of this Pending Item Group, and ensure that the User row contains the ChartField combination values defined at the Budget Journal
    7.- Set the Post Action of the Pending Item Group to Batch Standard
    8.- Launch AR Update for the affected Business Unit, and select the Pending Items option
    9.- Confirm that the amount of the new Item is on the Recognized Revenue of the Budget Details
    10.- Create a second Pending Item Group, re-using the same Item ID as before, and for a different amount
    11.- Manually create the Accounting Entries of this second Pending Item Group, and ensure that the User row contains the ChartField combination values defined at the Budget Journal except by one ChartField (Product ID, Fund Code, Project ID, any ChartField will do, as long as it is different than the combination on the Budget Journal. This is to trigger errors)
    12.- Set the Post Action of this second Pending Item Group to Batch Standard
    13.- Launch AR Update for the affected Business Unit, and select the Pending Items option
    14.- Check at the View/Update Item Details page, that both Item Sequences (1 and 2) have been properly posted against the Customer's Account
    15.- Navigate to the Revenue Estimate Review Transactions by Item page, and open the Item in question
    16.- Confirm that while Item Sequence 1 is having a Budget Status of VALID, the Item Sequence 2 is in ERROR
    17.- Navigate to the Revenue Estimate Correct Transactions page, and open the Item's Sequence 2 activity that is in Budget Error
    18.- On the ChartFields tab, proceed to update the ChartField value we entered incorrectly, to another value, still not the correct one (Again, this could be any ChartField: Product ID, Fund Code, Project ID, etc...)
    19.- Select the 'Correction Completed' flag, and save the changes
    20.- Go back to the View/Update Item Details component, on the Item Accounting Entries tab, and check the Item Sequence 1 Accounting Entries, to see that the ChartField value changed has impacted its rows, instead of Item Sequence 2 Accounting Entries, which remain the same as initially entered

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

Item Sequence Number 1 is always the one being updated regardless of which Item Sequence Number being the one in Budget Status Error. As such, the system changes the Accounting ChartField values on already posted, and successfully budget checked Item Sequences that will not be able to get corrected anymore. This is creating an out of sync problem between those ChartFields present in PS_ITEM_DST, and those already interfaced into General Ledger module.

The codeline delivered within the Revenue Estimate Correct Transactions page (AR_CC_TRAN_ERROR) should properly update the Item Sequence Number being updated, and that is flagged with Budget Check Errors, and not the initial sequence number transaction, which has a Budget Status of Valid.

NOTE: In the images/screenshots/examples mentioned and/or the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance).  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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