My Oracle Support Banner

E1: 42: Shipment Status (P4947) Version Called from Sales Order Entry Powerform (P42101) Always Calls P4947 Version Corresponding to P42101 Version (Doc ID 2535346.1)

Last updated on NOVEMBER 30, 2019

Applies to:

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

Symptoms

Sales Order Entry (P4210) is hard coded to call the ZJDE0001 version of P4947 when a user selects the option to view Shipment Status.  Sales Order Entry Powerform (P42101) indicates NONE in the Event Rules for form interconnect for P4947.  As a result, when the user accesses the ZJDE0006 version of P42101 and then takes the Row Exit to Order, Shipment Status, the ZJDE0006 version of P4947 is called.  If a ZJDE0006 version of P4947 does not exist, warning messages are written to the JAS log indicating:

[WARN  ] USER ID- [xxxxxxx] POEngine.fetchF983051Record(): No F983051 record fetched for version | App Name : P4947_W4947A_ZJDE0006
[WARN  ] USER ID- [xxxxxxx] POEngine.loadPOData():Unable to fetch F983051 record | App Name : P4947_W4947A_ZJDE0006
[WARN  ] USER ID - [xxxxxxx] POEngine.loadPOData(): Unable to load PO Data | App Name : P4947_W4947A_ZJDE0006

Revise P42101 to be hard-coded to call the ZJDE0001 version of P4947 similar to the hard-coding of P4210.

A workaround is to create one version of P4947 for each P42101 version used to review Shipment Status.

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.