My Oracle Support Banner

E1: 34: Large Customer Forecast Records Exported for EDI Do Not Retain Customer Address Book Number in F47067 (R47062) (Doc ID 2592700.1)

Last updated on OCTOBER 17, 2019

Applies to:

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

Symptoms

The Outbound Extraction - Forecast or Planning Schedule Extraction (R47062) when used to extract large customer Forecast records from the Forecast File (F3460) does not populate the customer address book number in EDI Planning Schedule Detail Outbound (F47077) file.  The inbound R47061 process populates the customer number in the F3460, so the EDI process is inconsistent.  Also, the R47062 outbound process prints the customer number to the PDF report, so the fault can be easily missed. 

STEPS
-----------------------
1.  Enter a BF F3460 large customer forecast for a parent Item Branch manufactured item.  
2.  From G47251, create named version of R47062 set to create Transaction set (EDST) 830, Transaction Name (EDFT) DELFOR records, EDI Doc Type (EDCT) PS or FC.  
3.  Run R47062 and review header (F47066) and detail records (F47067) for created outbound records.  Date and quantity are as expected.  Customer Number (CITM) is not populated in the F47077 outbound record, even though the F3460 record does have the address book number populated.

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!


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