My Oracle Support Banner

E1: 47: EDI Receiving Advice Edit/Create (R47071) Doesn’t Populate the Correct Account on the Journal Entry (F0911) for the Last Line of the PO Receipt (Doc ID 3017942.1)

Last updated on JANUARY 02, 2025

Applies to:

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

Symptoms


EDI Receiving Advice Edit/Create - Purchasing (R47071) doesn’t populate the correct G/L account on the last line of the PO Receipt OV Document in the Journal Entries (F0911) it creates .

Steps to Reproduce:

Note: Data referenced below is from JD Edwards Demo Data. No actual customer, employee and personal data is revealed. 
  1. Use Purchase Order Entry (P4310) to create a Purchase Order as follows:
    1. Line 1.000 uses Account 30.6350
    2. Line 2.000 uses Account 30.6350
    3. Line 3.000 uses Account 30.1469
  2. Use Inbound EDI Receiving Advice Revisions (P47070) to populate EDI 861 Receiving Advice Interface tables.
    1. In this test we populate the Account Number field but if you leave the field blank, the EDI Receipt (R47071) program should retrieve in from the PO Detail without having to specify it in the EDI table (F47072)
    2. Add the Required Header Information
  3. Run the EDI Receiving Advice Edit/Create - Purchasing (R47071). The job is processed without errors.
  4. Check PO Receipts Inquiry (P43214). Account on third line was changed to 30.6350, but it should be 30.1469.
  5. Check Journal Entries. Last line is 30.6350 but should be 30.1469.

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
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.