My Oracle Support Banner

E1: 17: R17714 not Considering Customer Master Backorder not Allowed Flag (Doc ID 2240104.1)

Last updated on FEBRUARY 05, 2019

Applies to:

JD Edwards EnterpriseOne Service Management - Version 9.1 and later
Information in this document applies to any platform.


 R17714 WO Print should consider customer master backorder not allowed flag.

Some of the final customers do not accept backorders F03012) neither partial shipments (flag APTS ticked in F03012).
The stocked items and estimated quantities and component branch plants are added in F3111, using P90CD015. Separately, logistics is adding manually the secondary locations which is hard committing the quantity.
When running R17714 it is automatically allocating parts/stocked items into secondary locations and then R17714 is hard - committing this quantity in F3111 with comm flag = H.

Now the question that we have is that R17714, when allocating quantities to secondary locations, in the case where available quantity in stock is lower than requested quantity in part-list F3111. It looks like R17714 is not looking to customer master where customer can be defined as not allowing back orders, not allowing partial deliveries.

R17714 should look at customer master to know that customer does not allow backorders/partial shipments, as it is properly done using sales orders and sales allocation batch.





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

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