E1: 47: EDSP and Audit Fields Not Updated When Rejected Due To Errors

(Doc ID 2345927.1)

Last updated on JANUARY 05, 2018

Applies to:

JD Edwards EnterpriseOne EDI - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

EDI Inbound Purchase Order Change Edit/Create (R47131) and all EDI Inbound Processor UBEs

The Successfuly Processed (EDSP) field in the EDI tables (F47131 and F47132) only get updated by EDI Inbound Purchase Order Change Edit/Create (R47131) when a record has been successfully processed. Also other audit fields such as the User ID (USER) Program ID (PID), Date Updated (UPMJ), and Time Updated (UPMJ) in the EDI tables are not updated when the the records are not successfully processed.
 
When users review EDI Documents with the Inbound EDI P.O. Change Inquiry (P47130) program, the records that were rejected should be marked with a N in the Successfuly Processed (EDSP) field and the other audit fields such as the User ID (USER) Program ID (PID), Date Updated (UPMJ), and Time Updated (UPMJ) in the EDI tables should be updated when the the records are not successfully processed.


This causes a problem for users who have no way to be a way to tell the difference between a record that was in error and a record that has not yet been processed by reviewing the EDI documents with the Inbound EDI P.O. Change Inquiry (P47130) program.

While it is true that when a job is rejected with an error, the error message is sent to the work center, the work center messages are not visible to users from their user Id and they are unable to review work center errors reported under the user id for the nightly job scheduler.

The steps below are for EDI Inbound Purchase Order Change Edit/Create (R47131) but the same process can be used with all EDI Inbound Processor UBEs

  1. Use the Inbound EDI P.O. Change Inquiry (P47130) program to create a new EDI document to make changes to fields on an existing sales order.
  2. Make sure to populate a field with an invalid value that will cause an error when EDI Inbound Purchase Order Change Edit/Create (R47131) is run.
  3. Have someone with appropriate security to log in to the scheduler user ID and launch the EDI Inbound Purchase Order Change Edit/Create (R47131) application.
  4. From the scheduler user ID, check the work center and verify the error.
  5. Sign in under your regular user id and look at the EDI Document you created that was rejected using Inbound EDI P.O. Change Inquiry (P47130) program.
  6. Notice Successfuly Processed (EDSP) field is blank.
  7. Go to the Work Center. No error messages appear under your user ID.
  8. Using databrowser access the EDI 860 Inbound Detail (F47132) file and find teh EDI document number.
  9. Notice audit fields such as the User ID (USER) Program ID (PID), Date Updated (UPMJ), and Time Updated (UPMJ) have not been changed to identify the user, program, date and time of the failed run.

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