Availability Based Replenishment
Commonly referred to as “ABR” (Availability Based Replenishment)
The Availability Based Replenishment feature constrains downstream replenishment recommendations to the inventory available at the source location. Setting the OP_ENABLE_ABR global setting to true (default) enables this feature.
• When using the Trigger Point Order Policy, the recommended quantity is constrained and the Total Replenishment Need amount is visible on each record as the Amount Requested and the Unmet Requirement is visible on each record as the Replenishment Deficit. This is also true when using TP-TR.
• When using the Time Phased Order Policy for replenishment pairs, the recommendations are moved out until inventory is available at the source location.
• The Order Planning process does not search for a more optimal ordering plan when the percentage of ABR retries is exceeded based on the setting of the OP_ABR_RETRY_STOP_PERCENTAGE global setting and the OP_MAX_ABR_RETRIES global setting.
 |
When the Order Planning process stops early as a result of limit set by the two global settings, the Order Plan processing stopped early Review Type (336) is generated with the following message:
ABR processing for GAP exceeded retry stop percentage. Ordering solution may not be optimal
|
Planning at the source location always takes into account the unmet need whether in trigger point or time phased mode.
 |
• When ABR is not enabled in a connected model, it allows the source location inventory balance to go negative and results in backorders at the topmost procuring locations.
• ABR cannot be used with Alternate Transport Mode or with Disconnected. Disconnecting a replenishment source from its child disables ABR for the replenishment orders between the two.
• It is not recommended to enable the Order Plan Detail feature when ABR is disabled. Order detail detail requires actual inventory to be accurate. The Order Plan Details feature is enabled or disabled by the OP_WRITE_PART_DETAIL global setting.
When should you use the ABR feature?
• If you want an executable supply plan for replenishment locations.
• If replenishment recommendations must be executable (pickable) by the client’s host systems. This typically means the host system cannot allocate replenishment orders or handle replenishment backorders. The GS OP_MAX_CONSTRAINED_DAYS controls the time horizon until ABR is enforced. This value is usually determined by how far out into the future you would want executable replenishment orders. Unlimited supply is available beyond this. It is recommended that this global setting no longer be used because of its interference with many other features and the runtime reduction from using it is now minimal.
• If the you want to use Fairshare for replenishment allocation.
|
Availability Based Replenishment Example
Consider the following example:
Field location — needs to order 5 today (Jan 1st)
Warehouse — has no inventory today (Jan 1st) but will receive 5 pieces of inventory on Jan 5th
Using the Time Phased Order Policy:
• ABR On — Field creates order on Jan 5th for 5 because the Warehouse will not have 5 units until Jan 5th
• ABR Off — Field creates order on Jan 1st for 5 because the Field does not check if source has inventory
Using Trigger Point Order Policy:
• ABR On — Field creates order on Jan 1st for recommended quantity of 0, requesting 5 because no inventory is available but the Field wanted 5
• ABR Off — Field creates order on Jan 1st for 5 because the Field does not check if source has inventory