E1: 34A: Suppressing Un-wanted Field Values within Supplier.xml File Generated by Batch Program R34A1000 (Doc ID 2288848.1)

Last updated on JULY 21, 2017

Applies to:

JD Edwards EnterpriseOne Advanced Planning Agent - Version 9.1 to 9.1 [Release 9.1]
Information in this document applies to any platform.

Symptoms

By design within JDE E1, it is possible to define different StandardLeadTime, OrderMultiple, MinimumPeriodOrder and MaximumPeriodOrder for an Item across different Branch Plants with the Supplier information. This information is stored in F4102-Item Branch Table which is similar to MSC_SYSTEM_ITEMS on VCP side.

Information within Table F4102 is not Supplier specific data and hence shouldn't be populated within Supplier.xml generated by Batch Program R34A1000. When this information is passed on to ASCP, as ASCP does not support this functionality it picks up any one of the value defined across the Branch Plants for the Item/Supplier combination and applies it across all the Organizations (Branch Plant) in ASCP, which is incorrect. However, if the Supplier related fields are null, then ASCP will default to the values from MSC_SYSTEM_ITEMS.

Require a functionality to suppress un-wanted values associated with OrderMultiple, MinimumPeriodOrder and MaximumPeriodOffer fields being passed into Supplier.xml and updating the StandardLeadTime (aka Processing  Leadtime) with a valid value when Batch Program R34A1000 is 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