The JD Edwards EnterpriseOne Apparel Management system facilitates the wholesale allocation and delivery of style items. You use allocation rules to facilitate the effective and efficient distribution of available style items to fill sales orders. You define allocation rules based on your business requirements.
Sales orders may contain a large number of detail order lines for style items that have a short period of time for initial delivery. One sales order line consists of a group of child style items.
Work order receipts for discrete item manufacturing are often spread among many sizes of child style items. You use allocation rules to determine which customer gets what items and in what sizes. If one size cannot be shipped, then you create exceptions or overrides in the allocation rules to determine when not to ship items and when to deliver items. All allocation rules are applicable to sales orders for style items only.
The system performs allocations based on the allocation rules defined by the user. You can also use allocation rules to create buffer stock to keep building inventory to fill large, high-priority sales orders.
You can generate allocation and delivery proposals for style items. Allocation proposals enable you to share the available stock among several sales orders in the case of product shortages. Delivery proposals ensure that the appropriate number of goods is shipped as needed.
You can manage allocation and delivery proposal processes simultaneously if you set constraints at the same time that you allocate stock. You can also split and run the processes separately. In this case, you first allocate the stock (hard commitment) and then manage delivery constraints.
Prerequisites
Before you complete the tasks in this topic, you must complete the following setup:
- Set the Specific Commitment (Days) field on the Branch/Plant Constants form to 999 to eliminate future commits.
- Deselect the Backorders Allowed option on the Branch/Plant Constants form to specify that backorders not be allowed for the branch/plant. Note. If backorders cannot be disabled at the branch/plant level, then you can bypass backorder processing
by setting the Activate Availability Checking processing option on the Commitment tab of the Sales Order Entry program (P4210) to blank. - Select the Other Quantity 1 SO option on the Item Availability Definition form in the Branch/Plant Constants to enable the system to deduct the other quantity 1 on the sales order from available quantity. Note. The Other Quantity 1 SO field stores the retained quantity during the allocations process. Important! Blanket sales orders use the Other Quantity 1 SO field. If you use blanket sales orders, then you may want set up the blanket sales order process to use the Other Quantity 2 SO field by setting the Commit to Quantity 1 or Quantity 2 processing option on the Commitment tab of the Sales Order Entry program (P4210).
- Set up a specific status for allocations in the order activity rules. For example, order status 529 (in allocations).
- Leave the Activate Availability Checking processing option on the Commitment tab of the Sales Order Entry program (P4210) blank to disable availability checking. Important! You must complete this setup in order to perform allocations.
- Verify the setup of the following UDC tables:
- Level Alias (41F/LA). The level alias codes define the SRP codes for sales category codes. The Top/Bottom UDC (41F/RC) uses UDC 41F/LA.
- Top/Bottom (41F/RC). The Item Category Code Alias 1 and Item Category Code Alias 2 processing options on the Satisfaction Rate tab and the Item Category Alias Top/Bottom, Item Category Alias Grouping Code 1, and Item Category Alias Grouping Code 2 processing options on the Top/Bottom Processing tab of the Generate Allocation and Delivery Proposals program (RCW06) use UDC 41F/RC. You use top and bottom management functionality to deliver items at the same time; for example, a jacket and pant that are sold together.
- Extract or Order Based (41F/SB). The Satisfaction Rate based on processing option on the Process tab of the Generate Allocation and Delivery Proposals program uses UDC 41F/SB.
- Processing Types (41F/TT) (treatment types). The Processing Type processing option on the Status tab of the Generate Allocation and Delivery Proposals program uses UDC 41F/TT.
- Reason Codes for Not Retained (41F/NR). The reason code identifies the reason a particular sales order line or style item was not retained.
Upon completion of this topic, you will be able to:
- Demonstrate size management in allocations for style items.
- Demonstrate top/bottom management in allocations for style items.