My Oracle Support Banner

E1: 76A: Invoice Void Application P76A725 Fails to Retrieve Delivery Note data (Doc ID 2982912.1)

Last updated on OCTOBER 26, 2023

Applies to:

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

Symptoms

When trying to cancel a delivery note through the P76A725 application, no data is retrieved. Analysis of the business logic shows that the application is looking at the User Reserved field F4211.URRF. Following the changes made under BUGs 30250503 and 30297414 , the Shipment Note Legal Number data is now being recorded in the F76A4211 table and field SNLN. The P76A725 is set to retrieve data from the F4211.URRF field, not the current/correct table and field.

Steps To Duplicate: 

  1. Activate AR localization; use the P4210 application to raise a sales order.
  2. Configure the R42565 and R76A565 process to process a “Remito” (document type 091) – this involves setting the RG100 option in the R76A565.
  3. Run the invoice process over the order and confirm that the system populates the F76A4211 table, including the Shipment Note Legal Number in the SNLN field.
  4. Launch the P76A725 application and populate the Shipment Note number fields in the Header, and press Find. The system fails to locate the order that was created, because it is designed to look for the legal shipment number in the F4211.URRF field. Following a design change, this field is no longer populated – data is stored in the F76A4211 table, field SNLN.

 

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.