1. Apparel Management Implementation Guide
  2. Prerequisites

Prerequisites

Before you complete the tasks in this chapter, 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.

    See "Setting Up Branch/Plant Constants" in the JD Edwards EnterpriseOne Applications Sales Order Management Implementation Guide.

  • 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.

    See "Setting Up Item Availability" in the JD Edwards EnterpriseOne Applications Sales Order Management Implementation Guide.

    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).

    See "Setting Up Order Activity Rules" in the JD Edwards EnterpriseOne Applications Sales Order Management Implementation Guide.

  • 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.

    See "Setting Processing Options for Sales Order Entry (P4210)" in the JD Edwards EnterpriseOne Applications Sales Order Management Implementation Guide.

  • Verify the setup of the following user-defined codes (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 the 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 the 41F/RC UDC.

      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 the 41F/SB UDC.

    • Processing Types (41F/TT) (treatment types)

      The Processing Type processing option on the Status tab of the Generate Allocation and Delivery Proposals program uses the 41F/TT UDC.

    • Reason Codes for Not Retained (41F/NR)

      The reason code identifies the reason why the particular sales order line or style item has not been retained.