My Oracle Support Banner

E1: 42: Inventory Commitment Preference Basic and Advanced Profiles (P40306/P4210/P42101/R42520/R42565/R42530/R40211Z/R42997/P4071/P4072) (Doc ID 1641298.1)

Last updated on FEBRUARY 03, 2019

Applies to:

JD Edwards EnterpriseOne Sales Order Management - Version XE and later
JD Edwards EnterpriseOne Sales Order Processing - Version XE and later
Information in this document applies to any platform.

Purpose

Overview

The Inventory Commitment preference enables a single Sales Order line to be automatically committed from a different branch than the header branch, or be committed across several branches. This will increase the chances that an order will be completely filled, and gives users greater flexibility to commit from locations that make sense in their business.

Businesses using the Inter-branch process usually enter Sales Orders in a Branch/Plant that is a sales office and may not carry any inventory. They use Inventory Commitment Preferences during the Sales Order Entry process to resolve the sourcing Branch/Plant. The intention is to ship the order from the sourced Branch/Plant. This is a common business model where many sales Branch/Plants source their orders from one or more distribution centers. The sourcing may take place from multiple Branch/Plants, based on the preference setup and availability at the sourced Branch/Plants.

Use the Sequence Number field to tell the system which Branch/Plant you want to try to pull inventory from first, second, and so on. When the Route Code, Mode of Transportation, and Carrier Number fields are populated, these values will be used to populate the Sales Order Detail (F4211) records.  If using a Carrier (33) or Mode of Transport (34) Transportation preference for these values, the information populated in the Inventory Commitment preference will be ignored.

Scope

 

Details

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
Purpose
Scope
Details
 Availability Checking is Required
 Affect of Partial Shipments and Backorders Settings
 Grade and Potency
 Percent to Fill
 Future Committed Orders
 Substitute Items
 Other Quantity 1 and 2
 Basic Preference Setup (Menu G4231)
 Preference Definition
 Preference Hierarchy
 Example:  Sales Order Entry (P4210/P42101), Menu G4211
 Advanced Preference Schedule (P4070) Sequencing
 Advanced Preference Setup (Menus G4222 and G40311) 
 Preference Hierarchy (P40073/Menu G4222)
 Advanced Preference Definition (P4071/Menu G40311)
 Advanced Preference Detail (P4072/Menu G40311)
 Additional Information
 Frequently Asked Questions
 Question 1: With the inventory commitment advanced preference setup, but no item branch record setup for the header branch for a specific item, Sales Order Entry (P4210 and P42101) issues the error Item Branch Record Does Not Exist (0294). Is an item branch record required on the header branch if the branch plant is a sales office and does not stock inventory?
 Question 2: When a new order type (S1) is setup with BB line type and the inventory commitment preference, a Status Flow Not Setup (0425) Error is returned and the preference item branch record is not retrieved. When the SO order type is used with the BB line type the error does not occur.
 Question 3: Does the Inventory Commitment Preference work with W Line type orders where a Work Order is created to manufacture the item?
 Question 4: Does the Inventory Commitment preference have the ability on a multiple item order to evaluate all the lines on the order against each preference branch to see if any one branch can fill every order line so that only one transportation shipment is sent for the order?
 Question 5: Can the inventory commitment preference be applied on an existing committed order?
 Question 6: Why doesn't the preference branch get selected when the Sales Order Entry (P4210) version has the a branch plant populated in Defaults Tab Option #12 (Default Branch Plant)?
References

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