EAR 9.2: PSJob STATEMNT Does Not Create All Customer Statements Expected if Launched as a Scheduled Job Definition Due to PS_RUN_CNTL_AR.AS_OF_DATE Not Being Properly Updated With System Date
(Doc ID 2740142.1)
Last updated on DECEMBER 28, 2020
Applies to:PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The Accounts Receivable Customer Statement PSJob (STATEMNT) has been scheduled to run on a periodic basis for a Group of Customers, on predetermined Run Control IDs, where the Use System Date flag has been selected. As new Customers are added into the Statement Group in question throughout the month, their Correspondence Options configuration are dated with the needed Effective Date value.
However, it has been detected that such new Customers are not being included in the PSJob run, and hence, their Customer Statements are not being created.
The As Of Date is what is used in AR_STMTPP AE Program to determine the Effective Date for the Customer's Correspondence Options. However, the As Of Date value (Record Field PS_RUN_CNTL_AR.AS_OF_DATE) does not get updated to the 'System Date' until the next process AR_STMT1 (which calls AR_STMTS where the code actually resides AR_STMTS.INIT.UPRCSID.SQL).
1.- Log into the FSCM Online Applications as a Receivables User
2.- Created a new Customer ID with Effective Date May 31st 2020, with Correspondence Options defining Statement Group A
3.- Created a new Pending Item Group for the new customer, with today's date (May 31st 2020), and placed the Group in Batch Standard
4.- Ran AR Update, and successfully posted the new Item against the Customer's Account
5.- Create a new Run Control ID (Name it OSS) for the Create Customer Statements process (PSJob STATEMNT), using System Date (May 31st 2020), and defined Statement Group A
6.- Launched the PSJob STATEMNT to success
7.- Confirmed that a new Statement ID is created for the new Customer, containing the new Item
8.- Added a new Effective Date row for Correspondence Options for the new Customer with a date value of TOMORROW, and defined Statement Group B
9.- Amended the existing Run Control ID OSS for the Create Customer Statements process (PSJob STATEMNT), using System Date (May 31st 2020), and changed the Statement Group to B
10.- Launched the PSJob STATEMNT to success
11.- Confirmed that no new Statement ID is created this time
12.- Define a DAILY Recurrence with a Start Date of TOMORROW
13.- Linked the DAILY Recurrence against PSJob STATEMNT Definition
14.- Configure a Scheduled Job Definition for PSJob STATEMNT under Run Control ID OSS, and Recurrence DAILY starting June 1st 2020
15.- At this stage, wait until TOMORROW to re-take the test
16.- One day has past, and it is now June 1st 2020
17.- Check the Process Monitor page under PeopleTools, and confirm that the scheduled PSJob STATEMNT has been launched automatically at the time expected, and completed in Success
18.- Check if any new Customer Statement has been created for Statement Group B, but none has, even though the Customer's Effective Date is June 1st 2020
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.
Customer Statements are not including all expected Customer IDs, and their respective transactions. As such, the resulting reports are inaccurate.
The Customer Statement IDs, and their respective reports, should contain all eligible Customers, and their transactions. As such, the delivered codeline from PSJob STATEMNT and all its related sub-processes should properly update Record Field PS_RUN_CNTL_AR.AS_OF_DATE in order to set the current System Date as the new As Of Date.
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