E1: 42: How to Recover from Premature Invoice Print (R42565) and Sales Update (R42800) (Doc ID 3024902.1)

Last updated on OCTOBER 08, 2024

Applies to:

Goal

HOW DOES THE CUSTOMER RECOVER FROM THE FOLLOWING INCIDENT?

Client has a process where they automatically invoice clients on the 5th of the month for a service received the prior month and run sales update immediately after invoicing. The job runs on the JDE Scheduler. The following process occurred in May 2024:

1. The job did not automatically run on May 5th which fell on Sunday.
2. On Monday, May 6, a user noticed the job did not run and ran the job manually from Batch Versions.
3. The May 6 job produced a Sales Update (R42800) report of 673 pages.
   1. All report lines had an Invoice Date of 4/30/2024.
   2. Execution Detail showed 3,707 Sales Detail (F4211) records were processed.
4. On Wednesday, May 8, the JDE Scheduler job that was supposed to run on May 5 was run.
5. The May 8 job produced a Sales Update (R42800) report of 197 pages.
   1. All the report lines had an Invoice Date of 5/31/2024.
   2. Execution Detail showed 1,210 Sales Detail (F4211) records were processed.
   3. These records were for May invoices and were produced too early.
   4. Recognizing that these invoices should not have been produced, the client deleted the RI batch.
      • The batch was not posted.
      • All the AR Ledger (F03B11) records were deleted.
      • All the Journal Entries (F0911) records were deleted.
   5. The Sales Detail (F4211) records were NOT purged to History (F4211)
      • All the records were at Status 620/999.
      • All the items included in the batch were non-stock items so the Item Ledger (F4111) was not affected.
   6. The client wants to rerun Invoice Print (R42565) and Sales Update (R42800) but they will need to change the statuses back to prior to Invoice Print.

Solution

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