Title: Preference Profiles For
EnterpriseOne: Inventory Commitment
Preference
Abstract: Documents setup specific to the Inventory Commitment Preference profile.
Links to Individual Preference Setup Considerations
Purpose and General Setup
Payment Terms
Payment Terms By Branch/Plant
Pricing Unit Of Measure
Pricing Unit Of Measure (Branch or ECS)
Revenue Business Unit, Or Cost Center
Revenue Business Unit, Or Cost Center
(Branch)
End Use
Print Message
Product Allocation
Product allocation (Branch)
Grade and Potency
Delivery Date
Order Preparation Days
Line Of Business
User Defined Price Codes
Price Adjustment Schedule
Pricing Or Container Management
Next Order Status
Sales Commission
Customer Currency
Inventory Commitment Preference: P40306-F40306
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 Interbranch 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 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.
Programs Affected:
P4210
Sales Order Entry
R42520
Pick Slip
R42522
Pick Control - Picks through the Subsystem
R42565
Invoices - Invoices through the Subsystem
R42530
Bill of Lading
R40211Z
Batch Sales Order Edit/Creation
R42997
Batch Inventory Commitment - Commitment through the Subsystem
Additional Information: Sales Order Entry (P4210) processing option #2 on the
Preference tab controls the use of the Inventory Commitment preference. Processing
option #1 on the Preference tab does not affect the Inventory Commitment preference,
nor do you need a version of Preference Selection for this preference.
When an order is entered, the first commitment preference branch that is actually used is
defaulted into the detail line.
If a branch is manually entered in the DETAIL branch field that is different from the
header branch, the branch entered will be used and the Inventory Commitment preference
will not change it. Therefore, no Inventory Commitment preference will affect this
order.
NOTE: The Inventory Commitment preference does not function with kits or
configured items.
Availability Checking
The Inventory Commitment preference works in conjunction with normal availability
checking, except that all branches defined in the preference profile are now checked. As
the availability of each branch is checked, if any one branch can fill the entire order, the
order will be shipped from that branch.
Backorder = N, Partial Ship = Y - Ship available and cancel remainder. After all
branches have been checked, any remaining quantity will be canceled.
Backorder = N, Partial Ship = N - Cancel if not enough available. After all branches
have been checked, cancel order quantity.
Backorder = Y, Partial Ship = Y - Ship available and backorder remainder. After all
branches have been checked, any remaining quantity will be backordered to the first
commitment preference branch USED.
Backorder = Y, Partial Ship = N - Backorder the entire line if there is not enough
available. After all branches have been checked, backorder the order quantity to the first
commitment preference branch.
Grade and Potency
The availability checking works together with the Grade and Potency fields. The
availability routine will not use any grades/potencies that are not within the range. In
addition, the “days before expire” in the Grade and Potency preference profile will
determine if the expiration date is within the customer’s allowable days. The availability
will then truly be the quantity of the grades/potencies they allow and within an acceptable
expiration period.
% To Fill
The Percent to Fill in the Inventory Commitment preference is used to designate the
percentage of an order quantity that must be filled in order to ship the available quantity
from that branch.
If the Percent to Fill is zero, the system performs normal processing.
100% to fill – the entire quantity must be shippable from only one branch. This prevents
shipping from multiple branches, but still searches a list of branches. If no branch can fill
the entire order, the order is backordered or partially shipped from the first preference
branch that it can satisfy.
1% to 99% - if the branch can fill the percentage, ship the available and carry the
remainder to the next branch and its percentage is checked. Each branch is still checked
to see if the entire quantity can be shipped.
Example: Order quantity of 500 each
Preference
Available
% to fill
HOU
ATL
100
400
50%
80%
Minimum Order Quantity Result
Available
250
No, skip branch
400
Yes, ship 400
SF
96
95%
95
Yes, ship 96,
backorder 4 to ATL
(95% of remaining 100)
The Inventory Commitment preference will use the Sequence Number field to determine
the order to check for filling quantities.
Future Commit
EnterpriseOne Inventory Commitments Preference functionality, which handles sourcing,
was not designed to handle orders that are in the future based on the Header Branch/Plant
(sales office) commitment days. The reason for this was that since the order is in the
future, the future availability is not known and cannot be predicted, and since the
sourcing logic is based on Availability, sourcing cannot be done for future orders.
When the Order Date is in the future, based on the Header Branch/Plant’s commitment
days, the sales order line gets future committed to the Header Branch/Plant and no
sourcing is done. This is the original design because, as pointed out earlier, future
availability is not known and cannot be predicted. Sales Order Entry Edit Line does not
allow Inventory Commitment Preferences to be called if the date is in the future.
However, a simple solution to ensure that sourcing is always done is to make the Header
Branch/Plant’s commitment days equal to 999. If the Header Branch/Plant’s commitment
days are set to 999, which is the maximum allowed, the order date will fall within the
Header Branch/Plant’s commitment days and sourcing will always be done. If the Header
Branch/Plant does not carry any inventory, there is no reason to have the commitment
days anything less than 999. Since the Branch/Plant never carries inventory, it will never
have any availability, not even future availability, hence no commitments will ever be
done in this Branch/Plant.
When a Sales Order is not in the future based on the Header Branch/Plant, sourcing is
done. This works correctly when the sales Branch/Plant is always sourcing from a single
shipping Branch/Plant. However, commitments are not correct if sourcing is done from
multiple Branch/Plants and if the Order Date is in the future based on any of the Detail
Branch/Plants sourced. In the case where souring from Multiple Branch/Plants and if the
order is not in the future according to the first sourced Branch/Plant, the sourced quantity
is correctly soft committed to the first sourced Branch/Plant. However, in the case of
subsequent sourced Branch/Plants, if the first Branch/Plant was soft committed, all other
sourced Branch/Plants are soft committed too, irrespective of whether the order date is
within or beyond their respective commitment days. So, even if the order is in the future
for a particular sourced Branch/Plant, then it will still get soft committed to that
Branch/Plant.
Back to Top