EAR 9.2: Delivered AR30006 Report (Aging by ChartField) Ignores The As Of Date Value If Run Control ID Has ChartFields Being Defined (Doc ID 2215863.1)

Last updated on DECEMBER 20, 2016

Applies to:

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

Symptoms

ISSUE:

An inconsistency has been detected when Users launch the Aging by ChartField (AR30006) delivered report when making use of the As Of Date feature:

     - If the Run Control ID defined is not having any ChartField values defined, (such as Account, Department ID, Fund Code, Operating Unit, etc...), the As Of Date value is being respected
     - If the Run Control ID defined is having any ChartField values defined, (such as Account, Department ID, Fund Code, Operating Unit, etc...), the As Of Date value is being ignored

As such, if the User wants to see the report results for one specific date, and the As Of Date is used, if there are ChartField values defined, the AR30006.sqr program will bypass that date value, and retrieve the Item information from today's date.

REPLICATION STEPS:

     1.- Log into the FSCM Online Application as User ID VP1
     2.- Navigate to: Accounts Receivable > Pending Items > Online Items > Group Entry
     3.- Create a brand new Pending Group for Business Unit US005, and Accounting Date of June 1st 2016, with a new Item for 1000 USD and Customer ID 1000
     4.- Set the new Pending Group into Batch Standard
     5.- Navigate to: Accounts Receivable > Receivables Update > Request Receivables Update
     6.- Launch AR Update to post the Item in question
     7.- Navigate to: Accounts Receivable > Payments > Online Payments > Regular Deposit
     8.- Create a brand new Deposit Group for Business Unit US005, for 1000 USD on Customer ID 1000, and referencing the previous Item ID created. Place the Accounting Date to July 31st 2016
     9.- Navigate to: Accounts Receivable > Payments > Apply Payments > Create Worksheet
     10.- Retrieve the new Deposit ID previously created, and build the worksheet, with the Item ID in question
     11.- Place the Payment Worksheet into Batch Standard
     12.- Navigate to: Accounts Receivable > Receivables Update > Request Receivables Update
     13.- Launch AR Update to post the Payment Worksheet in question
     14.- Navigate to: Accounts Receivable > Receivables Update > Unpost Groups > Payment Group
     15.- Open the Payment Worksheet Group recently posted, and in the Options tab state the below values:
           - Unpost Reason = WRGINV
           - Edit Accounting Date = Y
           - Accounting Date = October 3rd 2016
     16.- Save the changes, and place the un-post group into Batch Standard posting action
     17.- Navigate to: Accounts Receivable > Receivables Update > Request Receivables Update
     18.- Launch AR Update to un-post the Payment Worksheet Group in question
     19.- Navigate to: Accounts Receivable > Receivables Analysis > Aging > Aging by ChartField
     20.- Create a brand new Run Control ID with the below values:
           - Run Control ID = GCS
           - Language = English
           - As of Date = September 30th 2016
           - Business Unit = US005
           - Aging Set ID = SHARE
           - Aging ID = STD
           - Customer ID = Blank
           - Default Set ID = SHARE
           - Account = 120000
     21.- Continue by launching the AR30006 SQR process
     22.- Open the resulting AR30006 PDF report, to notice that the Item ID in question is being displayed, with an outstanding amount of 1000 USD, for an As Of Date of September 30th 2016, when that is incorrect

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

ACTUAL RESULT:

Because the As Of Date value is being ignored, Users are unable to review proper Customer Aging information at a particular significant date if ChartField values are being used to filter the information.

EXPECTED BEHAVIOR:

Whether only one single ChartField is being defined, or a combination of them, the Aging by ChartField report (AR30006) should be able to handle the request of the As Of Date, and present the Customer Aging information results for that particular specified date.

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms