Setting Up Inventory Values

Purpose: The Inventory section of the System Control file defines parameters that control:

• Physical Inventory processing

• SKU generation and presentation

• Inventory Transactions

For more information: For instructions and screen samples on how to create, change, delete, and copy a system control value, see System Control File Components.

Quick Reference of Inventory System Control Values

This table describes briefly each system control value for the Inventory application area and lists the control value, a short definition, other control values to which you should refer in this section, if necessary, and a column where you can indicate the value that you assigned for your company.

If you are working with multiple companies, make a copy of this table for each company on your system.

Company: ______________________________

System Control Value	Description	Your Value
Inventory Transaction Batch Security (A02)	Indicates if security will be required to perform Batch Inventory Transactions.	Yes/No:
Inventory Transaction History Retention Days (A24)	Defines the number of days that inventory transaction history will remain on the system before being purged.	Number:
Costing Method (A25)	Defines how the cost of an item is calculated.	Code:
Split SKU Inventory (A26)	Defines how the SKU field will display on screens and reports. See Split SKU Values (B32).	Yes/No:
Suggest Warehouse Placement (C44)
Suggest Location Placement (A27)	Indicates if the system should suggest locations to store product during Suggest Warehouse/Location Placement.	Yes/No:
Type of Location to Search First during Suggest Location Placement (C40)	Defines the type of location to search first during suggest location placement.	Code:
Type of Location to Search Second during Suggest Location Placement (C41)	Defines the type of location to search second during suggest location placement.	Code:
Type of Location to Search Third during Suggest Location Placement (C42)	Defines the type of location to search third (last) during suggest location placement.	Code:
Suggest Split Locations during Suggest Location Placement (C43)	Controls whether the system will suggest placing an item in a location already occupied by another item or will suggest only empty locations.	Yes/No:
Location Types (A28)	Defines the type of warehouse locations used in a warehouse.	Code:
Random Stock Location Usage (A29)	Defines which location types are used with the Suggest Warehouse Placement feature. See Location Types (A28) and Suggest Location Placement (A27).	Code:
Random Stock Location Assignment Sequence (A30)	Define the warehouse type that will be evaluated first when the Suggest Warehouse Placement feature is used. See Location Types (A28) and Suggest Location Placement (A27).	Code:
Location Capacity Method (A31)	Defines how the system determines the size/capacity of a location. See Location Types (A28) and Suggest Location Placement (A27).	Code:
Local Currency Code (A55)	Defines the base currency code used for conversions.	Code:
Inventory Sharing (A69)	Indicates if a company will fulfill orders from another company's inventory.	Yes/No:
Split SKU Values (B32):	Defines presentation of SKU fields if you are using split SKU format. See Split SKU Inventory (A26).
Split SKU Element Column Headings (A52, A53, A54)	Defines column heading for SKU element 1.	Code:
Split SKU Element Column Headings (A52, A53, A54)	Defines column heading for SKU element 2.	Code:
Split SKU Element Column Headings (A52, A53, A54)	Defines column heading for SKU element 3.	Code:
Position of SKU Element 1, 2, 3 in Order Entry/Maintenance (A42, A43, A44)	Defines the order in which each SKU element will appear in Order Entry and Order Maintenance.	Number:
Current OE/OM SKU Mapping Sequence (A14, A15, A16)	Displays the sequence in which a SKU must be entered for an item in Order Entry and Order Maintenance.	Code:
SKU Element Description 1 (G37)	Defines the long description to appear for SKU element 1.	Code:
SKU Element Description 2 (G38)	Defines the long description to appear for SKU element 2.	Code:
SKU Element Description 3 (G39)	Defines the long description to appear for SKU element 3.	Code:
SKU Element Defining Color (H21)	Defines which SKU element defines color when interfacing from CWDirect to other systems.	Number:
SKU Element Defining Size (H22)	Defines which SKU element defines size when interfacing from CWDirect to other systems.	Number:
SKU Element Defining Size 2 (H23)	Defines which SKU element defines size 2 when interfacing from CWDirect to other systems.	Number:
Short (4 char) Column Heading for SKU Element 1, 2, 3 in OE/OM (A45, A46, A47)	These system control values are not implemented; see Split SKU Element Column Headings (A52, A53, A54).	Code:
Default Item Unit of Measure (B33)	Defines the unit of measure that will default when creating an item.	Code:
Default Primary Location (C05)	Indicates if the primary location for an item should default during Inventory Transactions.	Yes/No:
Default Primary Location - Suspense Placement and PO Receipts (C08)	Indicates if the primary location for an item should default during PO Receipts or Suspense Placement.	Yes/No:
Physical Inventory Values (Screen 1) (C15):
Entry Method (A01)	Defines whether you will be using a ticket or worksheet entry format.	Code:
File Generation Output (A09)	Defines the form you use to record physical inventory counts. If using system generated worksheets or tickets, refer to Assign Batch Numbers (A07) and Batch Size (A08).	Code:
Upload Counts (A12)	Defines whether you will update inventory counts through data entry or using a store and forward device.	Yes/No:
Number of Outstanding Physicals (A05)	Defines the number of physical inventories that can be pending at one time. See Cycle Counting (A06).	Number:
Number of Counts Required per Physical (A13)	Defines the number of times you must enter counts before processing an update.	Number:
Freeze Item During Physical (A10)	Indicates if any other activity against an item location is allowed during physical inventory.	Yes/No:
Cycle Counting (A06)	Indicates if you will use cycle counting for physical inventory. See Number of Outstanding Physicals (A05).	Yes/No:
Assign Batch Numbers (A07)	Indicates if the system assigns batch numbers. See Batch Size (A08).	Yes/No:
Batch Size (A08)	Defines the number of item locations to include in each physical inventory batch. See Assign Batch Numbers (A07).	Number:
Batch Grouping (L64)	Defines whether Physical Inventory Generation uses location or item/location, along with batch size, to determine the number of batches in a physical inventory.	Code:
Print On Hand Quantity (A11)	Indicates if on-hand quantity for each item will print on physical inventory sheets or tickets.	Yes/No:
Units Variance (A20)	Defines the greatest number of units an item location count can vary from your on-hand quantity before being noted on the Physical Inventory Evaluation Report.	Quantity:
Cost Variance (A21)	Defines the greatest cost variance an item location count can show from your on-hand quantity before being noted on the Physical Inventory Evaluation Report.	Dollar Amount:
Percent Units Variance (A22)	Defines the greatest percentage an item location count can vary from your on-hand quantity before it is noted on the Physical Inventory Evaluation Report.	Percentage:
Percent Cost Variance (A23)	Defines the greatest cost percentage an item location count can vary from your on-hand quantity before it is noted on the Physical Inventory Evaluation Report.	Percentage:
Default Division for Inventory Transactions (C17)	Defines the division to be used when posting inventory transactions to the General Ledger interface.	Code:
Default Disposition Code (C18)	Defines the disposition code that will default when you create a return authorization.	Code:
Suggest Warehouse Placement (C44)	This system control value is not currently implemented.	Code:
Default SKU Generator Vendor Item (C61)	Indicates if the system should default the SKU into the Vendor/Item number field when generating SKUs and Vendor/ Item records.	Yes/No:
Fulfillment Production Percent (C86)	Defines the overhead percentage for fulfillment costs to be used in the calculation for profitability used on the Sales Profit Analysis Report for items that have a Long SKU/Class value that matches the SCV Production Category (C90) value.	Percentage:
G/A Production Percent (C87)	Defines the overhead percentage for general and administrative costs to be used in the calculation for profitability used on the Sales Profit Analysis Report for items that have a Long SKU/Class value that matches the SCV Production Category (C90) value.	Percentage:
Fulfillment Non-Assembly Percent (C88)	Defines the overhead percentage for fulfillment costs to be used in the calculation for profitability used on the Sales Profit Analysis Report for items that have a Long SKU/Class value that matches the SCV Non-Assembly Category value.	Percentage:
G/A Non-Assembly Percent (C89)	Defines the overhead percentage for general and administrative costs to be used in the calculation for profitability used on the Sales Profit Analysis Report for items that have a Long SKU/Class value that matches the SCV Non-Assembly Category (C91) value.	Percentage:
Production Category (C90)	Indicates the value that will be used in the Long SKU/Class field to identify an item as belonging to the Production Category.	Code:
Non-Assembly Category (C91)	Indicates the value that will be used in the Long SKU/Class field to identify an item as belonging to the Non-Assembly Category.	Code:
Allow Multiple Primary Item Locations (D12)	Indicates whether multiple primary locations are allowed for inventory items.	Code:
IS Report Net Projected Remaining Calculation Method (D34)	Defines how the Net projected remaining column of the Inventory Status and Projection Report is calculated.	Code:
Default Item Label Print Format (D36)	Defines whether item labels will print on 1-up or 4-up labels.	Code:
Display Item Description (D45)	Defines whether item descriptions display on inventory transaction screens.	Yes/No:
Auto Assign Item # (D46)	Indicates if the system will assign the item number during Item entry.	Yes/No:
Default Soldout Control Code (D72)	Defines a soldout control code to default when you create items and SKUs.	Code:
Default Soldout Control Code for Item to Item Transactions (D94)	Defines a soldout control code to default when you sell out an item because of an item to item transfer.	Code:
Markdown Cost Percentage for Liquidation (E20)	Defines the percentage of the item/SKU cost to use when processing a warehouse replenishment through the outlet transfer process, if the outlet does not specify a cost.	Percentage:
Markdown Cost General Ledger Number (E21)	Defines the general ledger number to use for posting the markdown for items included in a warehouse replenishment through the outlet transfer process.	Number:
RF LPN Label Print Program (E22)	Defines the program for printing bar-coded license plate number labels if you use radio frequency devices in your warehouse.	System Name:
RF Bin Label Print Program (E23)	Defines the program for printing bar-coded location labels if you use radio frequency devices in your warehouse.	System Name:
RF Item Label Print Program (E24)	Defines the program for printing bar-coded item/SKU labels if you use radio frequency devices in your warehouse.	System Name:
RF Return Label Print Program (E25)	Defines the program for printing bar-coded item labels for customer returns if you use radio frequency devices in your warehouse.	System Name:
RF Carton Label Print Program (E27)	Defines the program for printing carton labels if you dock purchase orders prior to processing them with the Purchase Order Receiving function.	System Name:
Item Number Label Type (E28)	Defines the type of item/SKU format to use on LPN labels if you use radio frequency devices in your warehouse.	Code:
Location Label Type (E32)	Defines whether you use a control code to confirm correct scanning of the location code with a radio frequency device.	Code:
Create Item Transaction History for Non-Inventory Items (E39)	Defines whether the system writes an issue (I) type transaction history record when non-inventory and drop ship items go through billing.	Yes/No:
Work Order Values (E41):
Use Work Order Processing (E37)	Defines whether you use work order processing for finished good items.	Yes/No:
First Location Type (E42)	Defines the type of location the system searches first to fill the component quantity needed on the finished good work order.	Code:
Second Location Type (E43)	Defines the type of location the system searches second to fill the component quantity needed on the finished good work order.	Code:
Third Location Type (E44)	Defines the type of location the system searches third to fill the component quantity needed on the finished good work order.	Code:
Sold Out Retention Method (E63)	Defines whether the system holds open the oldest (FIFO) or newest (LIFO) open order lines when you process auto soldouts if you elect to retain a quantity of the item from selling out.	Code:
Require Long SKU Division with Long SKU Department (E85)	Defines whether the Long SKU Division is a required field when creating or changing a Long SKU Department.	Yes/No:
Require Item Class in Work with Items (F06)	Defines whether the Item class field is a required field on the Create Item and Change Item screens in Work with Item/SKUs.	Yes/No:
Gift Wrap Default (F07)	Defines the default setting for the Gift wrap field when you create an item/offer or SKU/offer.	Yes/No:
Create Location/Item Location/Item Warehouse from PI Upload (F09)	Defines whether you create new Location, Item Location, and Item Warehouse as a result of running the physical inventory count upload if these records do not already exist in your company.	Yes/No:
SKU Purge Days (F11)	Defines the number of days to retain SKUs that are not contained on any existing order.	Number:
Require Sort Sequence Number in the SKU File (F23)	Defines whether the Sort sequence number field on the Create SKU and Change SKU screens in Work with Item/SKUs is a required field.	Yes/No:
Auto Assign Sort Sequence Number During SKU Generation (F24)	Defines whether the system automatically assigns a SKU sort sequence number to each SKU created in the SKU Generator.	Yes/No:
SKU Element for Auto Linking Coordinates (F39)	Defines the SKU element to use for automatic linking when creating item coordinates.	Number:
Default Company for RF Returns (F45)	Defines whether the company code defaults at the RF return pull and put screens.	Yes/No:
Retail PC Stock Transfer Shared Folder (F50)	Defines the shared folder where the system copies CamData Retail Point of Sale download files.	System Name:
Retail PC POS Sales Upload Shared Folder (F56)	Defines the shared folder where the system retrieves CamData Retail Point of Sale upload files.	System Name:
Warehouse Replenishment Label Program (F57)	Defines the program name the system uses to print warehouse replenishment labels.	System Name:
Display Frozen Primary Location Warning Message in Returns (F58)	Defines whether the system displays a warning message pop-up window when you perform a return against an item whose “primary primary” location is frozen due to a physical inventory.	Yes/No:
Auto-Generate Item Keywords from Description (F79)	Defines whether the system automatically generates item keywords from the item's description when you create an item.	Yes/No:
Allow Location Class Edit in Inventory Transaction (F86)	Defines whether the system validates the item's location class against the location's location class during inventory transaction processing.	Yes/No:
Send Average Cost Changes to PkMS (F92)	Defines whether changes to the average cost generates a PkMS Item Interface transaction.	Yes/No:
Warehouse Management System Interface (F96)	Defines whether the system will populate the PkMS or the WMS files with information from the Pick, Vendor and Comments files.	Code:
Retail Store Values (G00):
Use Retail Store File (G15)	Defines whether the system advances you to the Store screens when you are working with a warehouse that represents a retail store in Work with Warehouses.	Yes/No:
Store Promotion Pricing Lead Days (G16)	Defines the lead days the system uses to determine the store promotion pricing start date.	Number:
Store Promotion Pricing End Days (G17)	Defines the end days the system uses to determine the store promotion pricing end date.	Number:
Store Promotion Minimum/Maximum Lead Days (G18)	Defines the lead days the system uses to determine the store promotion minimum/maximum override start date.	Number:
Store Promotion Minimum/Maximum End Days (G19)	Defines the end days the system uses to determine the store promotion minimum/maximum override end date.	Number:
Exclude Restock Orders from Posting Shipped Units (G20)	This value is not currently implemented.	Yes/No:
Default Cancel Reason Code for Store Restock Orders (G21)	Defines the cancel reason code the system defaults to an order detail line that is automatically canceled on a restock order.	Number:
Location Class for Loose Pick Store Restock (G22)	Defines the location class the system uses to determine which items are eligible for the loose pick store restock process.	Code:
Default Order Type for Store Restock Orders (G23)	Defines the order type the system defaults to store restock orders.	Code:
Default Item Status for Exclusion on Store Restock Orders (G24)	Defines the item status the system uses to determine which items are excluded from being included on a store restock order.	Code:
Maximum Number of Lines to Include on Store Restock Order (I51)	Defines the number of order detail lines the system includes on a store restock order before creating a new order.	Number:
Include In-Transit Location On Hand for Retail Replenishment (J89)	Defines whether the system includes the quantity in the in-transit warehouse/location in the retail replenishment calculation.	Yes/No:
Exclude Pieces Per Case for Retail Store Restock (K82)	Defines whether the system considers the pieces per case value for an item when calculating the retail store restock quantity.	Yes/No:
Default Primary Location from an Item Warehouse (G06)	Defines whether a primary location will default for an item in the warehouse specified for an inventory/receipt transaction.	Yes/No:
Warehouse Replenishment Pick Worksheet Print Program (G25)	Defines the program to print the Replenishment Pick Worksheet for warehouse replenishment.	System Name:
Default Primary Warehouse in RF (G32)	Defines whether the item's primary warehouse defaults on RF screens.	Yes/No:
Item Number Cross Reference Program (G40)	Defines the program name the system uses to translate CWDirect item and SKU codes to another system's item and SKU codes.	System Name:
Require Entity in Item File (G44)	Defines whether the Entity field on the Create Item and Change Item screens in Work with Items is a required field.	Yes/No:
Display "No Primary Location" Message in Returns (G46)	Defines whether the system displays a warning message pop-up window when you perform a return against an item which has no primary location.	Yes/No:
UPC Validation Program (G62)	Defines the validation the system performs when you create a UPC code for an item.	Code:
Pending Putaway Due Date Days (G92)	Defines the number of days to add to the transaction date when calculating a pending putaway due date for inventory that is not associated with a purchase order.	Number:
Use Retail Integration (H26)	Defines whether you can use Retail Integration (external system to CWDirect).	Yes/No:
Create Supporting Files during Retail Item Upload (H27)	Defines whether the system will automatically create secondary file values during a Retail Item Upload.	Yes/No:
Use Retail Price Change Processing (H29)	Defines whether you can use retail price change processing.	Yes/No:
Allow Retail Price Change Updates on Open Lines (H30)	Defines whether the system updates open order lines with the current retail price.	Yes/No:
Retail Price Change Upload Approval Percent (H31)	Defines the retail price threshold the system uses to automatically approve retail price change upload records.	Percentage:
Price Override for Retail Price Change Lines (H32)	Defines the price override reason code the system defaults to open order lines the system updated with the current retail price.	Code:
Inventory Transaction Code for ’Sync’ Processing (I85)	Defines the inventory transaction code that signals a sync transaction when received through the generic inventory transaction upload.	Code:
Default SKU Generator L/S Style (J04)	Defines whether the SKU generator automatically creates a Long SKU style for each SKU created.	Yes/No:
Default Active Offers (J07)	Defines whether the system defaults the most recent active offers for the specified item to the selection screen in Update SKU Offers (MUSO) and Update SKU Offer Prices (MUSK).	Yes/No:
Item Creation Values (J08)	Defines which screens automatically display when you are Performing Initial Item Entry (MITM).
Auto Advance to SKU Create (B34)	Defines whether the system automatically advances to the Create SKU with Overrides screen when you create an item.	Yes/No:
Auto Advance to Vendor Item Create (E78)	Defines whether the system automatically advances to the Vendor Item Create screen when you create an item or SKU.	Yes/No:
Create Keywords at Item Entry (F78)	Defines whether the system automatically advances to the Work with Keywords for Item screen when you create an item.	Yes/No:
Auto Advance to SKU Generator (J06)	Defines whether the system automatically advances to the SKU Generator screen when you create a SKU’ed item.	Yes/No:
Auto Advance to Item Offer (J05)	Defines whether the system automatically advances to the Item Offer screen when you create an item.	Yes/No:
Track Cost Changes (J69)	Indicates whether to track cost changes for an item or SKU.	Yes/No:

Inventory Transaction Batch Security (A02)

Purpose: Use this screen to define whether a the system will check the secured feature, Inventory Transactions Batch Authority (A01), which allows you to perform the Inventory Transactions/Batch function.

MSR0052 CHANGE Change System Control Value 11/29/99 12:03:11 Description . : Inventory Transaction Batch Security Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . I/T Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to check the authority defined for the secured feature that allows you to create, change, process, and approve batch inventory transactions.

If you enter Y in this field, the system checks the secured feature, Inventory Transactions Batch Authority (A01), to determine the authority level. If the authority has been set to *ALLOW, all users will be able to perform Batch Inventory Transactions, unless otherwise specified at the user or user class level. If the authority level has been set to *EXCLUDE, all users will be prevented from performing Batch Inventory Transactions, unless otherwise specified at the user or user class level.

If you enter N, all users will have access to Batch Inventory Transactions. The authority level in the secure feature is not checked.

Authority levels are defined for users or user classes. See Working with User Records (WUSR) and Setting Up User Classes (WUCL).

Inventory Transaction History Retention Days (A24)

Purpose: Use this screen to define the number of days that inventory transaction history will remain on the system before being purged through the Purge Inventory Transaction History function.

MSR0054 CHANGE Change System Control Value 11/29/99 12:40:41 Description . : Inventory Transaction History Retention Days Number . . . . 3 Narrative . . . Application . : INV Applic group . I/T Sequence# . . . 1 F3=Exit F12=Cancel

Number field: Enter the number of days you wish to keep inventory transaction history on the system. For example, if you enter 3, the system will purge inventory transaction history after 3 days on the system.

You must run the Purge Inventory Transaction History function (MITH) for the information to be deleted. See Warehousing Display Inventory Transaction History (DITH) for more information.

Costing Method (A25)

Purpose: Use this screen to define how the cost of an item is calculated.

MSR0051 CHANGE Change System Control Value 2/12/98 15:40:05 Description . : Costing Method Code . . . . . AVERAGE STANDARD Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 3 F3=Exit F12=Cancel

Code field: Enter the code for the costing method you will use for inventory.

The inventory costing methods are:

• AVERAGE

• STANDARD

• FIFO

The costing method you select determines how you determine the cost of each item.

Average costing method: If you use the AVERAGE inventory costing method, the system calculates a new average cost automatically during Purchase Order Receiving, and updates the Cost field in the SKU file with the new, calculated average cost.

Average cost calculation:

 

(current on-hand x current average cost) + (quantity received x new purchase cost) / (quantity on-hand + quantity received) = new average cost

 

The new purchase cost represents the actual cost at which the item was purchased plus any overhead charges and additional item charges. See Warehousing Purchase Order Receiving Overview for more information.

For example:

current on-hand = 185

current average cost = 25.00

quantity received = 25

new purchase cost = 28.75 (25.00 + 15% for commission)

 

(185 x 25.00) + 25 x 28.75) / (185 + 25) = 25.45 (new average cost)

 

The system continues to change the cost of the item as the system factors the cost of the item at Receiving time. This field is updated only during Purchase Order Receipts.

Standard costing method: If you use the STANDARD inventory costing method, the Cost field in the SKU file must be updated manually; the system does not calculate or assign a cost to this field automatically.

Storing costs: The system always calculates and stores the average cost of an item for future reference, regardless of the default costing method you choose. Once you establish this control value, you can change it to the other costing method in order to generate special reports or perform special analyses.

FIFO costing: FIFO (first-in, first-out) costing allows you to use track the different costs assigned to each quantity of an item at the time you receive it into your warehouse. For example, if you receive 10 units of an item at $1.00, then 5 units of the item at $1.50, the system uses a cost of $1.00 for the first 5 units you sell, then uses a cost of $1.50 for the next 5.

Important: Unless you are first setting up a new company (that is, there has not been any inventory activity at all), you cannot change to or from FIFO costing at the Costing Method screen; instead, you must run a conversion program to convert to or from the different file requirements of FIFO costing. See Warehousing FIFO Costing Overview for more information on this conversion program and for an overview of how FIFO costing works.

Cost change audit: The costing method you use controls how the system updates the Cost Change Audit file if the Track Cost Changes (J69) system control value is set to Y. See Reviewing Item/SKU Cost History for more information.

Split SKU Inventory (A26)

Purpose: Use this screen to define how the SKU field will be displayed on screens and reports.

MSR0052 CHANGE Change System Control Value 11/29/99 10:52:26 Description . : Split SKU Inventory Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, the SKU will display as three discrete 4-position fields with user-defined labels such as CLR, SIZE, WDTH. This is referred to as a split SKU. If you enter Y in this field, you must complete the Split SKU Values (B32) system control value.

If you enter N, the SKU will display as a one 14-position field with the label SKU.

For more information: See Merchandising Introducing Split SKU Setup.

Suggest Warehouse Placement (C44)

Purpose: Use this screen to define the sequence the system uses to suggest locations to place stock.

Suggest Location Placement (A27)

Defines whether the system suggests locations to store stock during PO Receiving, Inventory Transactions, and Suspense Placement.

Yes/No field: Enter Y in this field if you want the system to suggest locations to store stock.

You can override the system's suggested location. Suggested location placement is used during PO Receiving, Inventory Transactions and Suspense Placement.

Suggest placement: During PO Receiving and Suspense Placement, the system displays the suggested location codes for the item, the number of units to be moved to each location, the location type and the capacity values of each location. You can accept the system's suggestions by pressing F8 to receive all items on the purchase order or by entering 8 next to the item you wish to receive. Otherwise, you can override the quantities or locations suggested.

When you use suggest warehouse placement, the system will not recommend the item's “primary primary” location but instead will use the values defined in the Suggest Warehouse Placement system control values to determine how to suggest locations. (The “primary primary” location is stored in the Primary loc (Primary location) field in the SKU file.)

The system evaluates the system control values for:

• Suggest Location Placement (A27): which enables this feature.

• Type of Location to Search First during Suggest Location Placement (C40): which defines the type of location to search first for item placement.

• Type of Location to Search Second during Suggest Location Placement (C41): which defines the type of location to search second for item placement

• Type of Location to Search Third during Suggest Location Placement (C42): which defines the type of location to search third (last) for item placement.

• Suggest Split Locations during Suggest Location Placement (C43): which controls whether the system will suggest placing an item in a location already occupied by another item or will suggest only empty locations.

• Location Capacity Method (A31): which defines, in units or cubic volume, how many units can fit into the location.

• Default Primary Location - Suspense Placement and PO Receipts (C08): which defines whether an item's primary location will default when receiving into Suspense Placement or PO Receipts.

If you enter Y in the Default Primary Location - Suspense Placement and PO Receipts (C08), the system will default the item's primary location in the Location field; however, you can still use Suggest Warehouse Placement, and override the default location.

Enter N inthis field if you do not want the system to suggest a location. If you enter N during receiving and suspense placement, you must enter a location to store the product.

For more information: See Suggest Warehouse/Location Placement.

Type of Location to Search First during Suggest Location Placement (C40)

Defines the type of location the system evaluates first when suggesting locations to place the item during PO Receiving, Inventory Transactions and Suspense Placement.

Code field: Enter the location type that should be evaluated first when suggesting locations to place the item.

Valid values are:

• *PRIMARY = Search primary locations first when suggesting locations to place the item.

• *SECONDARY = Search secondary locations first when suggesting locations to place the item.

• *BULK = Search bulk locations first when suggesting locations to place the item.

The Suggest Location Placement (A27) system control value controls whether the system suggests locations to store stock during PO Receiving, Inventory Transactions, and Suspense Placement.

For more information: See Suggest Warehouse/Location Placement.

Type of Location to Search Second during Suggest Location Placement (C41)

Defines the type of location the system evaluates second when suggesting locations to place the item during PO Receiving, Inventory Transactions and Suspense Placement.

Code field: Enter the location type that should be evaluated second when suggesting locations to place the item.

Valid values are:

• *PRIMARY = Search primary locations second when suggesting locations to place the item.

• *SECONDARY = Search secondary locations second when suggesting locations to place the item.

• *BULK = Search bulk locations second when suggesting locations to place the item.

The Suggest Location Placement (A27) system control value controls whether the system suggests locations to store stock during PO Receiving, Inventory Transactions, and Suspense Placement.

For more information: See Suggest Warehouse/Location Placement.

Type of Location to Search Third during Suggest Location Placement (C42)

Defines the type of location the system evaluates third (last) when suggesting locations to place the item during PO Receiving, Inventory Transactions and Suspense Placement.

Code field: Enter the location type that should be evaluated third (last) when suggesting locations to place the item.

Valid values are:

• *PRIMARY = Search primary locations third (last) when suggesting locations to place the item.

• *SECONDARY = Search secondary locations third (last) when suggesting locations to place the item.

• *BULK = Search bulk locations third (last) when suggesting locations to place the item.

The Suggest Location Placement (A27) system control value controls whether the system suggests locations to store stock during PO Receiving, Inventory Transactions, and Suspense Placement.

For more information: See Suggest Warehouse/Location Placement.

Suggest Split Locations during Suggest Location Placement (C43)

Controls whether the system will suggest placing an item in a location already occupied by another item or will suggest only empty locations.

Yes/No field: Enter Y in this field if more than one item can be inventoried in a location; otherwise, enter N.

If you enter N in this field, the system will look at empty locations only to place the item being received or transferred.

Location Types (A28)

Purpose: Use this screen to define the types of warehouse locations used in your warehouse.

MSR0051 CHANGE Change System Control Value 11/29/99 16:26:37 Description . : Location Types Code . . . . . ALL ALL PRIMARY PRI/SEC PRI/BULK Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the code that represents the warehouse location types you will be using. Valid types appear to the right of this field, which are:

• ALL (Primary, Secondary, and Bulk)

• PRIMARY

• PRI/SEC Primary and Secondary)

• PRI/BULK (Primary and Bulk )

The system checks the location type you enter on the Work with Locations Screen against the value you define for this system control value. You will receive an error message in Work with Locations if you enter a location type that is not defined for this control value.

Definition of location types: A primary location is the location in the system from which merchandise is picked to fulfill orders. This location carries the maximum and minimum quantities for the item, which are used by the Primary Replenishment program.

A secondary location is a location that may be used to pick inventory to fulfill orders or it may be used to replenish the primary location. The Suggest Warehouse Placement function uses the capacity values established for the secondary locations in the Location file to determine how much room is available in a location.

A bulk location is an overstock location where large quantities of the item are stored. Bulk locations can be used to pick inventory and to replenish the primary and secondary locations. A bulk location may or may not exist in the same physical warehouse as the primary or secondary location. The Suggest Warehouse Placement function uses the capacity values established for the bulk locations in the Location file to determine how much room is available in a location.

Primary, secondary, and bulk locations can be defined as all pickable locations.

For more information: See Warehousing Creating and Maintaining Locations (WLOC).

Random Stock Location Usage (A29)

Purpose: Use this screen to define which location types are used with the Suggest Location Placement (A27).

MSR0051 CHANGE Change System Control Value 11/29/99 16:32:14 Description . : Random Stock Location Usage Code . . . . . ALL ALL PRIMARY SEC/BULK Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the code that indicates which location types can be suggested when the system is determining where to store product. Valid types are:

• ALL = All indicates that all locations (primary, secondary, and bulk) are evaluated for storing product. The control value, Random Stock Location Assignment Sequence (A30) must be defined to determine the order in which locations will be evaluated.

• PRIMARY = Primary indicates that only primary locations are evaluated for storing product. The system will not suggest storing product in a bulk or secondary location.

• SEC/BULK = Sec/bulk indicates that secondary and/or bulk locations are evaluated for storing product; the system will not suggest storing product in a primary location.

For more information: See Creating and Maintaining Locations (WLOC).

Random Stock Location Assignment Sequence (A30)

Purpose: Use this screen to define the warehouse location type that will be evaluated first when the Suggest Location Placement (A27) feature is used.

MSR0051 CHANGE Change System Control Value 11/29/99 16:34:13 Description . : Random Stock Location Assignment Sequence Code . . . . . SECONDARY SECONDARY BULK Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the code that represents the warehouse location type that will be evaluated first when the Suggest Warehouse Placement feature is used. Valid options are:

• SECONDARY

• BULK

The system automatically checks the Primary location first (if the control value, Random Stock Location Usage (A29) is set to ALL), then checks the secondary or bulk location depending on what you define for this value.

Location Capacity Method (A31)

Purpose: Use this screen to define how the system determines the size/capacity of a location.

MSR0051 CHANGE Change System Control Value 11/29/99 16:36:07 Description . : Location Capacity Method Code . . . . . UNITS UNITS VOLUME Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 5 F3=Exit F12=Cancel

Code field: Valid codes appear to the right of this field:

• UNITS = Units indicates that the capacity will be determined by indicating a specified number of units that can fit into the location.

• VOLUME = Volume indicates that the total cubic volume of the item will be compared against the maximum cubic volume of the location to determine capacity.

Leave this field blank if you want to define an unlimited capacity for all locations.

If you want to calculate capacity for some locations, leave this field blank, and establish the number of units for a location when you are creating locations. See Creating Item Warehouse/Locations (MIWL).

When BULK location is designated as one of the warehouse types in the Random Stock Location Usage (A29) control value, cubic values for items and locations must be defined, even if UNITS is specified as the Location Capacity Method.

Before suggesting a location into which inventory can be received, the system will always check the weight capacity of the location, regardless of the Location Capacity Method. This is a check and balance to ensure that the system does not suggest a location that cannot physically support the weight of the inventory.

Local Currency Code (A55)

Purpose: Use this screen to define the base currency code used for conversions.

MSR0051 CHANGE Change System Control Value 11/29/99 10:57:15 Description . : Local Currency Code Code . . . . . USA CAN ITY JPN RUB USA ZLT Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 3 F3=Exit F12=Cancel

Code field: Enter the code for the base currency from which you perform conversions. Currency codes defined in the Currency file display to the right of your entry. You must enter a valid currency code.

Purchase order entry and receipts: For example, if the local currency code is defined as U.S. dollars and you enter a purchase order for a German vendor, the system will convert the currency from the dollar to the Deutsche Mark in Purchase Order Entry, and perform a reverse conversion (Deutsche Mark to U.S. dollars) for Purchase Order Receipts from this vendor.

Alternate currency pricing: If you use alternate currency pricing (the Use Alternate Currency Pricing (H89) system control value is set to Y), the system uses the currency code defined in the Local Currency Code system control value as the local currency; any other currency code is considered an alternate (foreign) currency.

See Accounts Payable Working with Currency (WCUR).

You can leave this field blank if you have no requirement for currency conversion.

Inventory Sharing (A69)

Purpose: Use this screen to define whether a company will fulfill orders from another company's inventory.

MSR0052 CHANGE Change System Control Value 11/29/99 10:32:26 Description . : Inventory Sharing Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you wish to use inventory sharing, which allows inventory to be shared across multiple companies. For example, one company might maintain the actual inventory in its warehouse, and other companies point to the warehouse in this company for inventory fulfillment.

When this field is set to Y, the Sharing warehouse and Shared cmp/whs (Shared company and warehouse) fields appear on the Create, Change, or Display Warehouse screens.

You can use this feature only to share inventory with warehouses in other companies; you cannot share inventory with other warehouses within the same company.

Company and warehouse records must be established for each company using this system to fulfill orders.

Entering N in this field indicates that this company maintains its own on-hand inventory.

Setup for Inventory Sharing

Setup for sharing the inventory in a company with one or more other companies is described in the table below.

Setup	Example
System control value: Set this system control value to Y in all companies to participate in inventory sharing, including both the company where you actually maintain the inventory and the company(ies) to share the inventory.	Set this system control value to Y in company 1 (shared company, where you actually maintain the inventory) and company 2 (sharing company).
Shared warehouse: In the warehouse in the shared company, set the Sharing warehouse field to Y. Do not set the Shared cmp/whs (Shared company and warehouse) in the sharing company.	Warehouse 10 is the actual warehouse in company 1. Set the Sharing warehouse flag in warehouse 10 of company 1.
Sharing warehouse(s): In the sharing company(ies): Set the Shared cmp/whs (Shared company and warehouse) fields for the virtual warehouse which corresponds to the actual warehouse. Leave the Sharing warehouse field set to N. Note: You should use the same warehouse number for the warehouse in the shared company and the virtual warehouse(s) in the sharing company(ies).	Warehouse 10 of company 2 is a virtual warehouse. In warehouse 10 of company 2, set the Shared cmp/whs (Shared company and warehouse) to 1 and 10.
Locations: Create the same location(s) in the actual warehouse in the shared company and the virtual warehouse in the sharing company.	Create location A010101 in warehouse 10 of company 1 and warehouse 10 of company 2.
Items: Create the same item(s) in the shared company and in the sharing company, with consistent item warehouse and item location records across the companies.	Item AB100 has a default warehouse of 10 and primary location of A010101 in both company 1 and company 2.

Reserving Inventory Across Companies

Each sharing company points to the shared company when determining available quantity, on-hand quantity, and reserved quantity. For example, if 20 units of the item are reserved on orders in company 1, and 15 units are reserved on orders in company 2, the total reserved quantity displayed in both companies is 35 (20 + 15). Information on availability is displayed in the sharing company using inventory inquiries such as Inquiring into Item Availability (DIAV) and Using Inventory Inquiry (DINI).

In order entry: When you enter an order for a shared item in a sharing company, the system reserves the item in the shared company.

Backorders: If a shared item is backordered, the backorder quantity increases in both the shared and the sharing companies. When you process an inventory transaction that increases the on-hand quantity, such as receiving a purchase order, the system allocates the units across the backorders using the hierarchy specified by the Use Inventory Sharing Backorder Evaluation (I80) system control value. You can use this system control value to reserve all backorders in the shared company first, and then in sharing companies; or you can reserve backorders strictly on the basis of backorder priority and entered date and time, regardless of the company where you took the order.

Inventory transactions: If you process an inventory transaction in a sharing company, the information is updated in the shared company. For example, if you process a return in company 2, but you actually maintain inventory in company 1, the system updates the inventory information in company 1.

If you use Working with Inventory Transactions in Batch Mode (WITB) or Working with Inventory Transactions in Immediate Mode (WITI), the system accepts and processes the transaction you enter, but does not display the results on the screen. Similarly, all inventory transaction history (see is available for review in the shared company where you actually maintain the inventory; history is not tracked in the sharing company.

Troubleshooting: Please note the following when working with inventory sharing:

• general ledger postings:

• changes in inventory valuation: General ledger postings related to inventory valuation are made in the shared company where you actually maintain the inventory.

• cost of goods sold: In order to have cost of goods sold tracked correctly, you need to have both the Default Warehouse (A04) in both the shared and the sharing companies set to the shared warehouse.

• creating locations consistently: If you create and use a location in the sharing (virtual) warehouse that does not exist in the shared warehouse where you actually maintain inventory, the system ignores any transactions related to this location, and does not create an inventory transaction error.

Split SKU Values (B32)

Purpose: Use this screen to define the presentation of the SKU fields in the Inventory, and Order Entry/Order Maintenance functions if you are using a split SKU format.

If you entered Y to Split SKU Inventory (A26), you must complete this screen.

MSR0406 ENTER Edit Split SKU Values 8/26/99 14:00:45 EZK Mail Order SKU Column OE/OM Headings Mapping Split SKU Element 1 Column Heading COL 1 Split SKU Element 2 Column Heading SIZE 2 Split SKU Element 3 Column Heading WDTH 3 Application Code . . INV Application Group. . ALL Current OE/OM SKU Mapping Sequence: COL SIZE WDTH Sku Element 1 Description . . . Size Sku Element 2 Description . . . Color Sku Element 3 Description . . . Style   SKU Element defining COLOR . 1 SKU Element defining SIZE . . 2 SKU Element defining SIZE 2 . 3 F3=Exit F12=Cancel

For more information: See Merchandising Introducing Split SKU Setup for more information on using split SKUs.

Split SKU Element Column Headings (A52, A53, A54)

Enter the headings that you want to appear over SKU elements 1, 2, and 3. These column headings are used throughout the system for a split SKU. This is also the sequence in which the data will be presented on all screens and reports throughout the system except Order Entry. The SKU Column Heading represents the text that appears above the user input field for a particular SKU element.

This format allows you to define up to three 4-character descriptions for a base item. A SKU further defines an item in terms of color, size, width, etc. This screen allows you to define the field names of the SKUs that will be used throughout the system, specify the order in which the SKU elements will appear in all functions except Order Entry and Order Maintenance, and specify the order in which the SKU elements will appear in Order Entry and Order Maintenance.

See Position of SKU Element 1, 2, 3 in Order Entry/Maintenance (A42, A43, A44) for more information on the order in which each of the SKU elements will appear in the Order Entry and Order Maintenance functions.

Split SKU Element Column 1 Heading (A34)

The description you define for Split SKU Element 1 Column Heading will become your primary element if you are using the SKU generator, and is used throughout the Inventory functions.

The primary SKU element designation is used when defining a SKU Group, in which a unique set of sizes, colors, widths, etc. is defined as constants for the group. A SKU group allows you to create a matrix of variables for an item (colors, sizes, widths, etc.), of which a primary and secondary element can be defined. The primary element designation is used for reports to subtotal by whatever value is defined as the primary element.

Position of SKU Element 1, 2, 3 in Order Entry/Maintenance (A42, A43, A44)

The sequence defined in the OE/OM Mapping fields represents the order in which each of the SKU elements will appear in the Order Entry and Order Maintenance functions. In the OE/OM Mapping column, each of the user input fields represents the first, second, and third SKU fields in the Order Entry and Order Maintenance functions. The number entered in each field represents the SKU element used.

For example, if Split SKU Element 1 is color and the SKU Column Heading is COLR, and Split SKU Element 2 is size and the SKU Column Heading is SIZE, and the Split SKU Element 3 is width and the SKU Column Heading is WDTH, and you enter a 3 in the first OE/OM Mapping field, a 1 in the second, and a 2 in the third, the SKU fields in Order Entry and Order Maintenance will be presented in this sequence: SIZ COL WDTH.

The following settings are valid for these system control values.

SCV A42	SCV A43	SCV A44	Results
1	2	3	SKU element 1 displays first, SKU element 2 displays next, and SKU element 3 displays last.
2	1	3	SKU element 2 displays first, SKU element 1 displays next, and SKU element 3 displays last.
3	1	2	SKU element 3 displays first, SKU element 1 displays next, and SKU element 2 displays last.

Current OE/OM SKU Mapping Sequence (A14, A15, A16)

The Current OE/OM SKU Mapping Sequence illustrates the sequence in which the SKU must be entered for an item in Order Entry and Order Maintenance.

Note: You cannot enter any values in these fields, even if you select the system control values individually; they are used only for display purposes on the Edit Split SKU Values screen.

SKU Element Description 1 (G37)

Enter the description of the first SKU element as it appears on the internet storefront. You can use this description to establish the relationship between the field as it appears on the storefront and the SKU element in CWDirect. This is a 10-position, alphanumeric field.

It is not necessary to complete this field if you define SKU elements on the web storefront itself, or if you use a full (non-split) SKU.

SKU Element Description 2 (G38)

Enter the description of the second SKU element as it appears on the internet storefront. You can use this description to establish the relationship between the field as it appears on the storefront and the SKU element in CWDirect. This is a 10-position, alphanumeric field.

It is not necessary to complete this field if you define SKU elements on the web storefront itself, or if you use a full (non-split) SKU.

SKU Element Description 3 (G39)

Enter the description of the third SKU element as it appears on the internet storefront. You can use this description to establish the relationship between the field as it appears on the storefront and the SKU element in CWDirect. This is a 10-position, alphanumeric field.

It is not necessary to complete this field if you define SKU elements on the web storefront itself, or if you use a full (non-split) SKU.

Important: You cannot edit the above three fields independently; you can edit them only on the Edit Split SKU Values screen.

SKU Element Defining Color (H21)

Use this field to specify which SKU element defines color when interfacing from CWDirect to other systems. If you use the CWCollaborate Interface to process drop ship purchase orders, you may want to use this system control value for informational and data retrieval purposes, since the CWCollaborate application does not separate split SKU information from base item information.

Number field: Enter 1, 2, or 3 to specify which SKU element you want to use to define color when interfacing to other systems.

SKU Element Defining Size (H22)

Use this field to specify which SKU element defines size when interfacing from CWDirect to other systems.

If you use the CWCollaborate Interface to process drop ship purchase orders, you may want to use this system control value for informational and data retrieval purposes, since the CWCollaborate application does not separate split SKU information from base item information.

Number field: Enter 1, 2, or 3 to specify which SKU element you want to use to define size when interfacing to other systems.

SKU Element Defining Size 2 (H23)

Use this screen to specify which SKU element defines size 2 when interfacing from CWDirect to other systems.

If you use the CWCollaborate Interface to process drop ship purchase orders, you may want to use this system control value for informational and data retrieval purposes, since the CWCollaborate application does not separate split SKU information from base item information.

Number field: Enter 1, 2, or 3 to specify which SKU element you want to use to define size 2 when interfacing to other systems.

Short (4 char) Column Heading for SKU Element 1, 2, 3 in OE/OM (A45, A46, A47)

These system control values are not implemented. See Split SKU Element Column Headings (A52, A53, A54) for more information.

Default Item Unit of Measure (B33)

Purpose: Use this screen to define the unit of measure that will default on the Create Item screen when creating an item.

MSR0051 CHANGE Change System Control Value 11/29/99 10:58:58 Description . : Default Item Unit of Measure Code . . . . . EA Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 3 F3=Exit F12=Cancel

Code field: Enter a valid unit of measure code. This value is used in the Create Item function. Although your entry is not validated against the Unit of Measure file, make sure the code you enter is defined in the Unit of Measure file. See Merchandising Working with Units of Measure (WUOM).

If you leave this field blank, no value will default in the Unit of Measure field in the Item file.

Note: For each drop ship item you will process through the CWCollaborate Interface, you should specify a unit of measure for the item. This unit of measure must match the unit of measure you specify for the item in the Vendor Item file. See Merchandising Working with Vendor Items (WVNI).

Default Primary Location (C05)

Purpose: Use this screen to indicate if the primary location for an item will default when performing Inventory Transactions.

MSR0052 CHANGE Change System Control Value 11/29/99 10:42:50 Description . : Inventory Transactions -- Primary Locations Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, the primary location for an item will default to the Location field when performing Inventory Transactions, if a primary location has been defined for the item in the Item/SKU file, and the warehouse specified is the item's primary warehouse. This field can be overridden in Inventory Transactions. See Warehousing Working with Inventory Transactions in Immediate Mode (WITI).

If you enter N, no value will default, and you must complete the Location field when performing an Inventory Transaction.

Related system control value: If the Default Primary Location from an Item Warehouse (G06) system control value is set to Y, the system will override the setting in the Default Primary Location system control value, and will default the first primary location, in alphanumeric order, for an item in the warehouse specified for an inventory transaction.

The description of the Default Primary Location system control value may be Inventory Transactions - Primary Locations in your company.

Default Primary Location - Suspense Placement and PO Receipts (C08)

Purpose: Use this screen to indicate if the primary location for an item will default when updating receiving inventory using Suspense Placement or PO Receipts.

MSR0052 CHANGE Change System Control Value 11/29/99 10:44:20 Description . : Default primary location. Suspense placement and po receipts Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, the primary location for an item will default to the Location field when receiving inventory using Suspense Placement or PO Receipts, if a primary location has been defined for the item in the Item/SKU file, and the warehouse specified is the item's primary warehouse. This field can be overridden in Inventory Transactions. See Merchandising Working with Existing Items (MITM).

If you enter N, no value will default, and you must complete the Location field when receiving inventory.

Related system control value: If the Default Primary Location from an Item Warehouse (G06) control value is set to Y, the system will override the setting in the Default Primary Location system control value, and will default the first primary location, in alphanumeric order, for an item in the warehouse specified for an inventory transaction.

Physical Inventory Values (Screen 1) (C15)

Purpose: Use this screen to define the values required to perform a physical inventory.

PIR0001 CHANGE Physical Inventory Values (1 of 2) 11/05/99 10:47:03 KAL Co. Entry Method . . . . SHEET (TICKETS, SHEET) File Generation Output AISLE (TICKETS,SHEET,LOCATION,AISLE,NONE) Upload Counts . . . . . . . . . . . . . . . . N (Y,N) Number of Outstanding Physicals . . . . 1 Number of Counts Required Per Physical . . . 1 (1,2) Cycle Counting . . . . . . . . . . . . . . . Y (Y,N) Freeze Item During Physical . . . . . . . . . Y (Y,N) Assign Batch Numbers . . . . . . . . . . . . N (Y,N) Batch Size . . . . . . . . . . . . . . 50 Print On Hand Quantity . . . . . . . . . . . Y (Y,N) + F3=Exit F12=Cancel

Entry Method (A01)

Enter the code that defines whether you use a ticket or worksheet entry format when entering counts into the system. Valid options are:

• TICKETS

• SHEET

• blank

To produce physical inventory tickets, enter TICKETS in this field and in the File Generation Output (A09) field; in this case, the entry format requires that you specify only the ticket number and the count.

To print worksheets, enter SHEET in this field. The order in which item locations appear on the sheets is controlled by the File Generation Output (A09) field.

You could also set this field to SHEET if you are uploading counts (the File Generation Output (A09) field would be set to blank or NONE); this setting would allow you to upload the first count and enter subsequent counts using sheets. In this case, the Upload Counts (A12) field should be set to Y.

To upload counts once without any subsequent entry, leave this field blank. You should then set the File Generation Output (A09) field to NONE or blank and the Upload Counts (A12) field to Y.

File Generation Output (A09)

Enter the code for the form you want to produce to record physical inventory counts. Valid options are:

• TICKETS

• SHEET

• LOCATION

• AISLE

• NONE

• blank

If you enter TICKETS, the system prints a ticket for each item location. You can choose the number of items and/or locations for which tickets should be printed. The Entry Method (A01) system control value should also be set to TICKETS.

If you enter SHEET, the system prints a worksheet by location code. The Entry Method (A01) system control value must also be set to SHEET.

If you enter LOCATION, the system prints a worksheet by location code. The Entry Method (A01) system control value must be set to SHEET.

If you enter AISLE, the system prints a worksheet by zone/aisle. The Entry Method (A01) system control value must be set to SHEET.

If you enter NONE or leave this field blank, you should set the Upload Counts (A12) system control value to Y. If the Entry Method (A01) field is blank, this combination of settings is valid for uploading counts. If the Entry Method (A01) is SHEETS, this combination of settings is valid for uploading counts also, but permits entering a second or subsequent count. You might use these settings if you are using your own tickets or worksheets, an outside counting service, or if you use an RF (radio frequency) or store-and-forward device to record and send inventory counts.

Upload Counts (A12)

Enter Y in this field if you are updating the system with inventory counts using an RF or store-and-forward device. If you are using this feature, use the Work with Physical Inventory Upload option to accept inventory counts. You cannot use this menu option if this system control value is not set to Y. See Warehousing Working with the Physical Inventory Upload.

In addition, the Clear LPN file before generate field on the Generate Physical Inventory Screen (Generating a Physical Inventory (MGPI)) only displays if this system control value is set to Y.

Enter N or leave this field blank if you will be entering counts manually into the system.

The valid settings for these three fields are summarized in the table:

Entry Method	File Generation Output	Upload Counts	Result
blank	NONE or blank	Y	upload counts
TICKETS	TICKETS	N or blank	tickets
SHEET	NONE or blank	Y	upload count one then enter counts with sheets
SHEET	SHEET, LOCATION or AISLE	N or blank	see Assign Batch Numbers (A07) table

Number of Outstanding Physicals (A05)

Enter the number of physical inventories that can be pending at one time. This is a check-and-balance in the system to ensure that you do not generate too many physicals without completing one.

This feature is typically used in cycle counting. If physical inventories are not updated in a timely manner, other operations, such as pick slip generation, will be affected.

If you leave this field blank, it implies that only one physical inventory can be pending at one time.

Number of Counts Required per Physical (A13)

Enter the number of physical counts that must be entered before you can update the system with the actual inventory counts. Valid options are:

• 1 or blank

• 2

If you enter 1 or leave this field blank, you can enter one, two, or three counts before you perform an update. The on-hand quantity for each item location is always updated with the last count entered.

If you enter 2, the system requires that you enter at least two counts. However, if you are using sheets, you do not need to enter each item location on the second or final count. The on-hand quantity for an item location is always updated with the last count entered.

Freeze Item During Physical (A10)

Enter Y or leave this field blank to freeze item locations that are being counted during a physical inventory procedure (the Physical freeze field is set to Y). Freezing item locations prevents transactions that affect the on-hand balance from being performed. These transactions include: purchase order receiving, inventory adjustments, pick slip generation, confirmation, and billing. While an item is “frozen” during a physical inventory, the item will still be reserved for orders you take.

Setting this field to Y will greatly reduce your chances of having inventory errors or incorrect updates as a result of a physical inventory.

Enter N to avoid freezing item locations during a physical inventory (the Physical freeze field is set to N). If you set this field to N, there will not be any records on the On Hand Not Changed Report that is produced when you process a physical inventory update, since this report includes only item locations which remain frozen.

Cycle Counting (A06)

This field defines whether you will use the cycle counting feature for physical inventory. Cycle counting allows you to count a portion of your inventory. You must assign cycle count codes to items in the Item file in order to count inventory by cycle. See Merchandising Working with Existing Items (MITM).

If you enter Y in this field, you will be able to select cycle count as an option when performing a physical inventory.

If you enter N or leave this field blank, the cycle count fields do not appear on the Generate Physical Inventory Selection screen.

Assign Batch Numbers (A07)

This field defines whether the system assigns a batch number automatically when creating the physical inventory tickets or worksheets.

If you enter Y in this field, the system assigns a batch number to groups of tickets or worksheets. The system groups tickets or worksheets according to the Batch Size (A08) and Batch Grouping (L64) you define.

Assigning batch numbers allows you to generate Physical Inventory reports by specific batch, and update the system with physical inventory counts by batch. This may make your count entry process easier, since you can have more than one person entering counts at one time with less chance of mistakenly overwriting each others' entries. However, if you assign batch numbers, you cannot produce a variance report that includes all item locations in a warehouse.

Enter N or leave this field blank to not assign batch numbers. In this situation, the entire physical inventory is assigned to batch #1.

The table below explains the information that prints on the Physical Inventory Batch Work Sheet, based on the settings of the File Generation Output (A09) and Assign Batch Numbers (A07) system control values.

Generation output?	Assign batch numbers?	Batch Inventory Worksheets Results
SHEET	Y	Item locations appear in alphanumeric sequence by location code, then item code, then by the Sort sequence number for the SKU. Page breaks by location type and batch quantity (specified in the Batch Size (A08) system control value). Batches may be split across sheets. If a batch splits across sheets because of different location types, the sheets within the batch appear in location type sequence (PRIMARY, SECONDARY, BULK, then TEMPORARY).
SHEET	N	Item locations appear in location type sequence (PRIMARY, SECONDARY, BULK, then TEMPORARY), then alphanumeric sequence by location code, then alphanumeric sequence by item code, then by the Sort sequence number for the SKU. Page breaks by size of batch sheet and location type, but not by location code.
LOCATION	Y	Item locations appear in alphanumeric sequence by location code, then item code, then by the Sort sequence number for the SKU. Page breaks by location and batch quantity. Batches are not split across sheets. A blank sheet appears between each batch sheet.
LOCATION	N	Item locations appear in location type sequence (PRIMARY, SECONDARY, BULK, then TEMPORARY), then alphanumeric sequence by location code, then alphanumeric sequence by item code, then by the Sort sequence number for the SKU. Page breaks by size of batch sheet and location code.
AISLE	Y	Item locations appear in zone/aisle sequence, then alphanumeric sequence by item code, then by the Sort sequence number for the SKU. Page breaks by size of batch sheet and zone/aisle.
AISLE	N	Item locations appear in location type sequence (PRIMARY, SECONDARY, BULK, then TEMPORARY), then alphanumeric sequence by location code, then alphanumeric sequence by item code, then by the Sort sequence number for the SKU. Page breaks by size of batch sheet and location code.

Batch Size (A08)

Enter the number of item locations or the number of locations (based on the setting defined in the Batch Grouping (L64) system control value) to include in each physical inventory batch. The number you enter can be up to five positions.

This system control value assumes that you are using worksheets to perform and enter your physical counts.

• This field controls the number of item locations or locations in a batch, not the number of LPNs. Since you can have any number of LPNs within an item location, your batch sheets may be of a variable number of LPNs.

• You must complete this value if you entered Y in the Assign Batch Numbers (A07) system control value.

• If you leave this field blank, the batch size defaults to 1.

• Enter a small number in this system control value if you wish multiple people to work on the physical inventory count. You can assign a different person to each batch generated.

Batch Grouping (L64)

Indicate whether Physical Inventory Generation uses location or item/location, along with the Batch Size (A08), to determine the number of batches in a physical inventory.

• ITEM/LOC (default if not defined) = The system uses item/location and batch size to determine the number of batches in a physical inventory. A location could appear in more than one batch.

• LOCATION = The system uses location and batch size to determine the number of batches in a physical inventory. A location would not appear in more than one batch.

You must complete this value if you selected the Assign Batch Numbers (A07) system control value.

When Assign Batch Numbers (A07) is selected, the setting of the File Generation Output (A09) system control value determines when the system starts a new batch.

File Generation Output (A09)	Batch Grouping (L64)	System starts a new batch when:
SHEETS	ITEM/LOC	• The warehouse changes. • The number of item/locations is greater than the batch size.
SHEETS	LOCATION	• The warehouse changes. • The number of locations is greater than the batch size.
LOCATION	ITEM/LOC	• The zone changes. • The number of item/locations is greater than the batch size.
LOCATION	LOCATION	• The zone changes. • The number of locations is greater than the batch size.
AISLE	ITEM/LOC	• The aisle changes. • The number of item/locations is greater than the batch size.
AISLE	LOCATION	• The aisle changes. • The number of locations is greater than the batch size.
TICKETS	ITEM/LOC	The number of item/locations is greater than the batch size.
TICKETS	LOCATION	The number of locations is greater than the batch size.
NONE	N/A	If File Generation Output (A09) is set to NONE, the system does not assign batch numbers. In this situation, the entire physical inventory is assigned to batch 1.

For more information: See Using Physical Inventory Batches for an example of when the system starts a new batch, based on the setting of this system control value.

Print On Hand Quantity (A11)

If you enter Y in this field, the on-hand quantity for each item prints on system-generated, physical inventory worksheets or tickets.

Enter N or leave this field blank to suppress the printing of the on-hand quantity.

The advantage of suppressing the printing of the on-hand quantity is so that your warehouse workers may take an accurate count that is not influenced by the system count.

If you enter Y in this field and you use LPNs, you will notice that the total on-hand quantity for the item location that appears under LPN 0 represents the total on-hand not currently assigned to LPNs. For example, if the item location includes 65 units, including 60 that are assigned to 10-unit LPNs, a quantity of 5 will appear next to LPN 0, while a quantity of 10 will appear next to each of the LPNs.

When you complete this screen: When you complete this screen you can advance to screen 2 of the Physical Inventory values.

Physical Inventory Values (Screen 2)

Purpose: Use this screen to define variance thresholds to print on the Physical Evaluation Variance Report by Unit Variance.

The system will identify an exception for any item that meets any one condition defined on this screen. For example, if you specify 5 in the Units Variance (A20) field and $100.00 in the Cost Variance (A21) field, the system will note the item on the variance report if it is 5 units off; it does not have to meet the criteria for cost variance.

These values are defaults only. You can override any or all of them at the time you generate the report.

PIR0001 CHANGE Physical Inventory Values (2 of 2) 8/27/99 13:33:36 KAL Co. Variance Report Setup Units Variance . . . . . . . . . 100 Cost Variance . . . . . . . 100.50 Percent Units Variance . . . . . 2.00 Percent Cost Variance . . . . . . 5.00 F3=Exit F12=Cancel

Variance Report Setup:

Units Variance (A20)

Enter the quantity over or under which an exception will appear on the Physical Inventory Evaluation report. This is a 7-position, numeric field.

For example, if this value is set to 5 units, and the on-hand count is 100, but the physical count is 110, an exception will be noted, because the variance is greater than 5 units. This value is used to catch deviations, potential inventory shrinkage, or the need for a recount.

Cost Variance (A21)

Enter the dollar amount over which or under which an exception will appear on the Physical Inventory Evaluation report. This field is 12 positions with a 2-place decimal.

For example, if this dollar value is set to $25.00, and the on-hand value of an item is calculated at $100.00, but the on-hand value of the counted quantity is $70.00, an exception will be noted, because the variance is greater than 25 dollars. This dollar value is used to catch deviations, potential inventory shrinkage, or the need for a recount.

Percent Units Variance (A22)

Enter the percentage over which or under which an exception will appear on the Physical Inventory Evaluation report. This field is 6 positions with a 2-place decimal.

For example, if this value is set at 5%, and the on-hand count is 100, but the physical count is 110, an exception will be noted, because the percentage of variance is greater than 5%. This value is used to catch deviations, potential inventory shrinkage, or the need for a recount.

Percent Cost Variance (A23)

Enter the dollar percentage over which or under which an exception will appear on the Physical Inventory Evaluation report. This field is 6 positions with a 2-place decimal.

For example, if this dollar percentage is set to 5%, and the on-hand value of the item is calculated at 100.00, but the on-hand value of the counted quantity is $75.00, an exception will be noted, because the variance is greater than 5%. This dollar percentage is used to catch deviations, potential inventory shrinkage, or the need for a recount.

Default Division for Inventory Transactions (C17)

Purpose: Use this screen to define the division to use when posting inventory transactions to the general ledger.

No posting to the general ledger will take place for warehouse, item or inventory transactions unless you have defined the default division in this field.

MSR0051 CHANGE Change System Control Value 11/29/99 12:04:54 Description . : Default Division for Inventory Transactions Code . . . . . CA CA 01 1A 1B 11 2 2A 2B 3 4 Narrative . . . Application . : INV Applic group . I/T Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the division to use when posting inventory transactions to the General Ledger.

All inventory transaction codes associated with G/L numbers will post to the General Ledger transaction file as long as you have defined the default division in this field. The system uses the General Ledger number in the transaction code, the division you define for this system control value, the entity defined in the division, and the company code to post the transaction.

Override for warehouse: If the warehouse affected by the inventory transaction has a Division specified, the system uses this division, rather than the default specified with this system control value, to post inventory transactions. See the description of the Division under Creating and Maintaining Warehouses (WWHS) for more information.

Divisions are defined using the Working with Divisions (WDIV) menu option.

Default Disposition Code (C18)

Purpose: Use this screen to define the disposition code that will default when creating a return authorization.

MSR0051 CHANGE Change System Control Value 11/29/99 10:46:56 Description . : Default Disposition Code Code . . . . . RF AB QA RF ST 03 1 11 17 4 99 Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the code that defaults to the Disposition field when you create a return authorization record for a returned item through the Return Authorization option or the Returns function of Order Maintenance.

The disposition code defines how the returned item will be handled: whether it affect inventory levels; to which warehouse will the item be returned; to which location in the warehouse will the returned item be placed.

You can override this default when creating a return authorization through the Return Authorization option or the Returns option in Order Maintenance.

Additionally, all items on the order will be received into the warehouse and location defined for the default disposition code if the disposition code affects inventory.

This value is validated against the Return Disposition file. See Customer Service Establishing Return Disposition Values (WRDV).

Suggest Warehouse Placement (C44)

Purpose: This system control value is not currently implemented.

For more information: See:

• Suggest Warehouse/Location Placement for more information on having the system determine where merchandise should be placed when merchandise is being received into inventory, when merchandise is being transferred from suspense to inventory, and when you are placing items in locations independent of the Purchase Order Receipts and Place Suspended Stock functions.

• Let Down Replenishment for more information on the automatic restocking of primary locations initiated by the system when you generate pick slips.

• Replenish Primary Locations Overview for more information on how the Replenish Primary Locations function, initiated through Working with Replenishment Control (MSRP), is used to determine whether inventory should be moved from secondary or bulk locations to the primary picking locations.

• Replenish Warehouses Overview for more information on the Replenish Warehouses function, which is used to move inventory from one warehouse to another to replenish the target warehouse.

• Suggest Warehouse Placement (MSLO) for more information on the Suggest Location for Item function, which is used to search for available warehouse space to determine where you should place an item.

Default SKU Generator Vendor Item (C61)

Purpose: Use this screen to indicate whether the system should duplicate the SKU portion of the item number (the code for the item's color, size, width, etc.) into the Vendor/Item number field when using the SKU Generator and creating Vendor/Item records.

MSR0052 OPEN Change System Control Value 7/14/94 9:35:13 Description . : Default SKU Generator Vendor Item? Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . S/G Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, the system will default the SKU portion of the item to each Vendor/Item record when the SKU Generator creates the individual SKU records.

Typically, you would set this field to Y if the Vendor/Item SKU elements (for color, size, width, etc.) are the same as your own SKU codes. This reduces data entry because you do not need to reenter the vendor item number for each SKU.

The Vendor/Item code is the code under which the vendor sells an item. For example, the vendor may sell black shoes as item #9300 BLK 9.5 MED. This code indicates that the shoe itself is item number 9300, and the particular style of shoe (black, size 9.5, medium width) is represented by the code BLK 9.5 MED. If you advertise (and sell) the item under the a different item number (such as AB10000, but the same color and size), you may set this field to Y. When you add the item to your inventory and run the SKU Generator to create individual SKU records based on certain style elements (such as color, size, and width), the system will create a SKU record for each combination of styles and duplicate this information for each Vendor/Item record.

If you set this field to N and you specify to create Vendor/Item records, the system will leave the SKU field for each Vendor/Item record blank. You must enter this information manually for each SKU record; otherwise, the system issues a message:

Error: Vendor Item Duplicate

 

For more information:

• Merchandising Using the SKU Generator (ESKG)

• Merchandising Working with Vendor Items (WVNI)

Fulfillment Production Percent (C86)

Purpose: Use this screen to define the overhead percentage for fulfillment costs used in the calculation for profitability on the Sales Profit Analysis report.

MSR0057 OPEN Change System Control Value 1/04/95 12:24:20 Description . : Fullfillment Production percent Percentage . . 10.00 Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 100 F3=Exit F12=Cancel

Percentage field: The percentage you enter here is used in the calculation for profitability on the Sales Profit Analysis report. This percentage is used only for items that are assigned to the same long SKU class as in the Production Category (C90) system control value.

Long SKU classes are defined using the Working with Long SKU Classes (WLSC) menu option.

G/A Production Percent (C87)

Purpose: Use this screen to define the overhead percentage for general and administrative costs used in the calculation for profitability on the Sales Profit Analysis report.

MSR0057 OPEN Change System Control Value 1/04/95 12:24:20 Description . : G/A Production percent Percentage . . 10.00 Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 100 F3=Exit F12=Cancel

Percentage field: The percentage you enter here is used in the calculation for profitability on the Sales Profit Analysis report. This percentage is used only for items that are assigned to the same long SKU class as in the Production Category (C90) system control value.

Long SKU classes are defined using the Working with Long SKU Classes (WLSC) menu option.

Fulfillment Non-Assembly Percent (C88)

Purpose: Use this screen to define the overhead percentage for fulfillment costs used in the calculation for profitability on the Sales Profit Analysis report.

MSR0057 OPEN Change System Control Value 1/04/95 12:24:20 Description . : Fulfillment Non-Assembly percent Percentage . . 5.00 Narrative . . . _ Application . : INV Applic group . ALL Sequence# . . . 100 F3=Exit F12=Cancel

Percentage field: The percentage you enter here is used in the calculation for profitability on the Sales Profit Analysis report. This percentage is used only for items that are assigned to the same long SKU class as in the Non-Assembly Category (C91) system control value.

Long SKU classes are defined using the Working with Long SKU Classes (WLSC) menu option.

G/A Non-Assembly Percent (C89)

Purpose: Use this screen to define the overhead percentage for general and administrative costs used in the calculation for profitability on the Sales Profit Analysis report.

MSR0057 OPEN Change System Control Value 1/04/95 12:24:20 Description . : G/A Non-Assembly percent Percentage . . 5.00 Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 100 F3=Exit F12=Cancel

Percentage field: The percentage you enter here is used in the calculation for profitability on the Sales Profit Analysis report. This percentage is used only for items that are assigned to the same long SKU class as in the Non-Assembly Category (C91) system control value.

Long SKU classes are defined using the Working with Long SKU Classes (WLSC) menu option.

Production Category (C90)

Purpose: Use this screen to define the value that will be used in the Long SKU class field to identify an item as a production item.

MSR0057 OPEN Change System Control Value 1/04/95 12:24:20 Description . : Production Category Number . . . . 4444 Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 100 F3=Exit F12=Cancel

Number field: The value you enter here you may also enter in the Long SKU class field in the Item record to identify an item as a production item.

When you run the Sales Profit Analysis report, the system will determine which items are production items. Next, the system will use the overhead percentages for fulfillment costs and general and administrative costs (defined in the Fulfillment Production Percent (C86) and G/A Production Percent (C87) system control values) to calculate the profitability of production items.

Long SKU classes are defined using the Working with Long SKU Classes (WLSC) menu option.

Non-Assembly Category (C91)

Purpose: Use this screen to define the value that will be used in the Long SKU class field to identify an item as a non-assembly item.

MSR0057 OPEN Change System Control Value 1/04/95 12:24:20 Description . : Non-Assembly Category Number . . . . Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 100 F3=Exit F12=Cancel

Number field: The value you enter here you may also enter in the Long SKU class field in the Item record to identify an item as a non-assembly item.

When you run the Sales Profit Analysis report, the system will determine which items are non-assembly items. Next, the system will use the overhead percentages for fulfillment costs and general and administrative costs (defined in the Fulfillment Non-Assembly Percent (C88) and G/A Non-Assembly Percent (C89) fields in the System Control file) to calculate the profitability of non-assembly items.

Long SKU classes are defined using the Working with Long SKU Classes (WLSC) menu option.

Allow Multiple Primary Item Locations (D12)

Purpose: Use this screen to indicate whether multiple primary locations are allowed for inventory items.

MSR0051 OPEN Change System Control Value 1/04/95 12:24:20 Description . : Allow Multiple Primary Item Locations Code . . . . . NOT ALLOW CONFIRM ALLOW Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 100 F3=Exit F12=Cancel

Code field: The value you enter here controls whether you may define multiple primary locations any time you create an item/location record, such as during an Inventory Transaction or Location Transfer. This enables you to control the number of locations in which an item is inventoried or to place the item in as many locations as you want. Valid options are:

• NOT ALLOW

• CONFIRM

• ALLOW

If you set this value to NOT ALLOW, the system issues a warning message and prevents you from assigning the item to additional locations.

If you set this value to CONFIRM, the system displays a pop-up window that indicates that a primary location exists for the item. You can either continue and create another location for the item or cancel this action.

If you set this value to ALLOW, the system lets you create an additional location for an item automatically without sending a warning or confirmation.

Each time you attempt to create a new location for the item, the system checks for a value in the Location field in the SKU record. The system issues a warning message that a primary location already exists for the item if you set this value to CONFIRM or NOT ALLOW, regardless of the type of location specified for the item (primary, secondary, bulk).

Note: This value also affects how the Update Primary Primary Location for Item During Receiving (I35) system control value determines whether to update an item’s “primary primary” location when receiving a purchase order or placing suspended stock. See that system control value for more information.

IS Report Net Projected Remaining Calculation Method (D34)

Purpose: Use this screen to define how the Net projected remaining column on the Inventory Status and Projection Report should be calculated.

MSR0051 CHANGE Change System Control Value 5/06/99 17:31:28 Description . : IS Report Net Projected Remaining calculation method Code . . . . . GROSS GROSS NET Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 999 F3=Exit F12=Cancel

Code field: Enter NET in this field to have the Net projected remaining column on the Inventory Status & Projection Report (ISRP) calculated as:

 

Net projected life - Net units = Net projected remaining

 

Enter GROSS in this field to have the Net projected remaining column on the report calculated as:

 

Net projected life - Quantity ordered + Quantity returned/exchanged = Net projected remaining

 

Note: If this system control value is blank, the net projected remaining quantity will not be calculated, and the suggested quantity will be inaccurate.

Default Item Label Print Format (D36)

Purpose: Use this screen to define whether item labels print 1-up or 4-up.

MSR0051 OPEN Change System Control Value 8/04/95 10:47:57 Description . : Default Item Label Print Format Code . . . . . 1UP 4UP Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the code that represents the label type to use. Valid options are:

• 1UP: 1up labels print in a single row.

• 4UP: 4up labels print four to a row.

You can print item labels for miscellaneous stock movement associated with purchase order receiving, replenishment, etc. See Warehousing Creating Item Labels (PILB).

Display Item Description (D45)

Purpose: Use this screen to define whether item descriptions display on an inventory transaction screen.

MSR0052 OPEN Change System Control Value 9/19/95 12:27:40 Description . : Display Item Description on I/T Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: If you enter Y or leave this field blank, the system displays the item description on the Work with Inventory Transactions screen. Displaying the item description is useful in confirming that you have entered the correct item number for the inventory transaction.

If you enter N, the item description does not display on the Work with Inventory Transactions screen. See Warehousing Working with Inventory Transactions in Immediate Mode (WITI) for more information about inventory transactions.

Auto Assign Item # (D46)

Purpose: Use this screen to define whether the system assigns item numbers during item entry.

MSR0052 OPEN Change System Control Value 9/27/95 11:23:33 Description . : Auto Assign Item # Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . Sequence# . . . F3=Exit F12=Cancel

Yes/No field: This value controls whether the system assigns the item code automatically during Item entry (which you can override) or you enter your own item codes.

Enter Y in this field to have the system assign the next sequential item number each time you enter a new item in the Item file. The system takes the next available item number from the Item # field in the Number Assignment file. This is a numeric, 9 position (maximum) field. See Setting Up the Number Assignment File (WNUM) for more information about this number assignment.

During Item entry (when you press F6), the system loads the next item number (left-justified) to the Item field and places the cursor at the Desc (Description) field. You may override the system- assigned item number; however, this number will not be reused.

Enter N to use your own item codes during Item entry. During Item entry (when you press F6), the system places the cursor at the Item field.

Default Soldout Control Code (D72)

Purpose: Use this screen to define a soldout control code to default when you create items or SKUs.

MSR0051 CHANGE Change System Control Value 4/11/96 11:25:24 Description . : Default Soldout Control Code Code . . . . . Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter a soldout control code that you want to default into the Soldout Control field when you create items and SKUs in Work with Items, or when you create SKUs with the Generate SKUs function. You can override the default code when you are creating items and SKUs.

Leave this field blank if you do not want a soldout control code to default when you are creating items and SKUs.

The soldout control is a 2-position, alphanumeric code, defined in and validated against the Soldout Control file, that controls the circumstances under which you treat an item as soldout.

Although you define the code itself, each soldout control code can have only one of the three statuses:

1: sellout immediately

2: sellout when on-hand plus on-order quantity is exhausted

3: sellout when on-hand quantity is exhausted

For more information:

• on creating items and SKUs, see Merchandising Performing Initial Item Entry (MITM) and Working with SKU Elements (WSK1, WSK2, WSK3).

• on working with Soldout Controls, see Customer Service Working with Soldout Controls (WSLD).

Default Soldout Control Code for Item to Item Transactions (D94)

Purpose: Use this screen to define a soldout control code for the system to assign to items you sell out as a result of an item to item transfer.

MSR0051 CHANGE Change System Control Value 7/11/96 15:34:25 Description . : Default S/O Control Code for Item to Item Transactions Code . . . . . GB EX GB IN SO Narrative . . . Default S/O Control Code for Item to Item Transactions Application . : INV Applic group . I/T Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the soldout control code you want the system to default when you process an item to item transfer (item transaction code = G) in Work with Inventory Transactions.

You use item to item transfers when you want to transfer inventory from one item code to another. You might want to do this for a slow-selling or reduced inventory item that you now want to offer as part of a grab bag. The soldout control code you define here appears in a pop-up window when you process an item to item transfer. You can accept the default or enter a different code. If the transfer eliminates the entire on-hand inventory of the source item, the system will assign this soldout control code to the item.

Soldout control codes are defined in and validated against the Soldout Control Code file; valid codes appear to the right of the field.

Leave this field blank if you do not want to a soldout control code to default for item to item transfers.

For more information:

• See Warehousing Working with Inventory Transactions in Batch Mode (WITB) for more information on processing inventory transactions.

• See Customer Service Working with Soldout Controls (WSLD) for more information on working with soldout control codes.

Markdown Cost Percentage for Liquidation (E20)

Purpose: Use this screen to define the percentage of the item/SKU cost to use for items included in a warehouse replenishment using the outlet transfer process, if no cost is specified by the outlet.

MSR0057 CHANGE Change System Control Value 1/14/97 10:01:20 Description . : Markdown cost percentage for liquidation Percentage . . 80.00 Narrative . . . Application . : FUL Applic group . STK Sequence# . . . 1 F3=Exit F12=Cancel

Percentage field: Enter the percentage of the item/SKU cost to use when you process a warehouse replenishment using the outlet transfer process. For outlet transfers, the system bases the replenishment details on the contents of the Autostock Replenishment Work file, which contains replenishment requests from your outlet stores (each considered a warehouse in CWDirect). Outlet transfers differ from the standard warehouse replenishment process, which assumes that you maintain inventory information for each warehouse within CWDirect, and in which the system evaluates the replenishment requirements of the 'To' warehouse and the item availability of the 'From' warehouse for you.

If an outlet has requested an item for replenishment but has not specified a markdown cost, the system calculates the markdown cost as the percentage you specify here times the item/SKU cost in the SKU file. For example, if you specify a percentage of 80% (80.00) in this system control value, and the cost in the SKU file is $10.00, the system calculates the markdown cost of the item as $8.00. The system uses this cost for posting the change in inventory value to the General Ledger Interface file.

See the description of the Markdown Cost General Ledger Number (E21) for information on how the system updates the General Ledger Interface file for outlet transfers.

Leave this field blank if you do not process outlet transfers, or if the markdown cost will always be specified in the Autostock Replenishment Work file.

The cost that appears in the Inventory Transaction History file is the cost from the item/SKU record.

See Warehousing Work with Warehouse Replenishment (MWRP) for information on warehouse replenishment and outlet transfers.

Markdown Cost General Ledger Number (E21)

Purpose: Use this screen to define the general ledger number to use for posting item markdowns when you process an outlet transfer.

MSR0054 CHANGE Change System Control Value 1/14/97 10:16:52 Description . : Markdown cost general ledger number Number . . . . 55 Narrative . . . Application . : FUL Applic group . STK Sequence# . . . 1 F3=Exit F12=Cancel

Number field: Use this field to define the general ledger number to use when posting item markdowns when you process an outlet transfer.

When you transfer an item through the outlet transfer process (see the description of the Markdown Cost Percentage for Liquidation (E20) system control value), the system uses the account number you define here to post the difference between the markdown cost of the item and the cost that appears in the SKU file. For example, if the cost in the SKU file is $10.00, but you process the outlet transfer at $8.00, the system posts these transactions to reflect changes in inventory valuation to the General Ledger Interface file:

• $8.00 debit to the general ledger number defined for the 'To' warehouse

• $2.00 debit to the general ledger number defined in this system control value

• $10.00 credit to the general ledger number defined for the 'From' warehouse

Leave this field blank if you do not process outlet transfers, or do not process them at a markdown.

See Warehousing Work with Warehouse Replenishment (MWRP) for information on outlet transfers and warehouse replenishment.

RF LPN Label Print Program (E22)

Purpose: Use this screen to define the program for the system to use when printing bar-coded license plate number (LPN) labels for radio frequency warehouse management.

MSR0053 CHANGE Change System Control Value 10/21/96 15:51:00 Description . : RF LPN Label Print Program System name . . RFR0070 Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 100 F3=Exit F12=Cancel

System name field: Enter the name of the program that produces bar-coded LPN labels for use in managing your inventory through radio frequency devices.

If you use radio frequency in your warehouse, the system assigns an LPN to each case when you receive a purchase order. You then use a radio frequency gun to scan the label information, so that you can register each movement of the case throughout the warehouse. You can also print LPN labels through the RF menus. See Warehousing Radio Frequency Overview for an overview of radio frequency, setup information, and complete documentation of the radio frequency menus.

In addition to defining the LPN label print program here, you should define the program in the Report Control file. See Working with Report Controls (WRPT) of the System Operations guide for information on working with report controls.

The LPN label typically contains information such as:

• LPN number (which actually consists of the 3-position company code concatenated with the 6-position LPN number itself)

• company name

• date and time printed

• item and SKU descriptions

• LPN unit quantity

• item/SKU codes

• location where case should be placed at receipt

• the item's primary location

The base print program is RFR0070.

Leave this field blank if you do not use radio frequency in your warehouse.

RF Bin Label Print Program (E23)

Purpose: Use this screen to define the program for the system to use when printing bar-coded location labels for radio frequency warehouse management.

MSR0053 CHANGE Change System Control Value 10/21/96 15:51:00 Description . : RF Bin Label Print Program System name . . RFR0072 Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 100 F3=Exit F12=Cancel

System name field: Enter the name of the program that produces bar-coded location labels so that you can scan the location code through a radio frequency device.

In addition to defining the bin label print program here, you should define the program in the Report Control file. See System Operations Working with Report Controls (WRPT) for information on working with report controls.

The base print program is RFR0072.

See Warehousing Radio Frequency Overview for more information on radio frequency.

Leave this field blank if you do not use radio frequency in your warehouse.

RF Item Label Print Program (E24)

Purpose: Use this screen to define the program for the system to use when printing bar-coded item labels for radio frequency warehouse management.

MSR0053 CHANGE Change System Control Value 10/21/96 15:51:00 Description . : RF Item Label Print Program System name . . RFR0071 Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 100 F3=Exit F12=Cancel

System name field: Enter the name of the program that produces bar-coded item labels so that you can scan the item/SKU code through a radio frequency device.

In addition to defining the item label print program here, you should define the program in the Report Control file. See System Operations Working with Report Controls (WRPT) for information on working with report controls.

The base print program is RFR0071.

For more information: See Warehousing Radio Frequency Overview for more information on radio frequency.

Leave this field blank if you do not use radio frequency in your warehouse.

RF Return Label Print Program (E25)

Purpose: Use this screen to define the program for the system to use when printing bar-coded customer return labels for radio frequency warehouse management.

MSR0053 CHANGE Change System Control Value 10/21/96 15:51:00 Description . : RF Return Label Print Program System name . . RFR0073 Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 100 F3=Exit F12=Cancel

System name field: Enter the name of the program that produces bar-coded return labels so that you can scan the item/SKU code through a radio frequency device.

In addition to defining the return label print program here, you should define the program in the Report Control file.

The base print program is RFR0073.

The return label may contain information such as item/SKU, primary location, and date and time the return was processed.

For more information:

• See Warehousing Radio Frequency Overview for more information on radio frequency.

• See System Operations Working with Report Controls (WRPT) for information on working with report controls.

Leave this field blank if you do not use radio frequency in your warehouse.

RF Carton Label Print Program (E27)

Purpose: Use this screen to define the program for the system to use when printing carton labels when you dock a purchase order.

MSR0053 CHANGE Change System Control Value 10/21/96 15:51:00 Description . : RF Carton Label Print Program System name . . RFR0080 Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 100 F3=Exit F12=Cancel

System name field: Enter the name of the program that produces carton labels when you dock a purchase order.

Docking is an optional step before formally receiving a purchase order. If you dock a purchase order, you record the fact that you have received a shipment against the purchase order, not the actual contents of the shipment. You can dock a purchase order once or several times. See Warehousing Docking Purchase Orders (MDPO) for more information on docking.

In addition to defining the return label print program here, you should define the program in the Report Control file. See System Operations Working with Report Controls (WRPT) for information on working with report controls.

The carton label typically includes the purchase order number, the date, and a sequential number (i.e., 1 of 5, 2 of 5, etc.).

The base print program is RFR0080.

Note: This print program requires a radio frequency printer.

Item Number Label Type (E28)

Purpose: Use this screen to define how the system validates the item/SKU code you scan through LPN labels.

MSR0051 CHANGE Change System Control Value 2/24/97 11:26:32 Description . : Item Number Label Type Code . . . . . ITEMNUMBER ITEMNUMBER REF NUM SHORT SKU ITEM-S-K-U ZERO ITEM Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the code representing the format of the item/SKU field for bar-coded item codes on RF labels. This code tells the system how to interpret item codes that you scan through an RF gun.

Valid values are:

• ITEMNUMBER (or blank): The regular item and SKU codes appear on the label. This is the default value.

• REF NUM: The value in the Ref # field defined for the Item/SKU appears on the label. This is a 15-position, numeric field. This value is not currently implemented.

• SHORT SKU: The 7-position, numeric Short SKU field defined in the SKU file appears on the label. This is a system-assigned value.

• ITEM-S-K-U: The Item and SKU codes with embedded hyphens appear on the label. If you have this field set to ITEM-S-K-U, the item/SKU fields that appear on the RF menus will have an extra two positions. For example, if this field is not set to ITEM-S-K-U, the item/SKU fields appear on the RF screens as:

It:

SKU:

 

However, if this field is set to ITEM-S-K-U, the item/SKU fields appear on the RF screens as:

It:

SKU:

 

Note the additional two-position field that appears after the Item field. These positions are actually part of the SKU field, and allow you to enter the first embedded hyphen and the next character.

If you set this field to ITEM-S-K-U, the SKU field will appear as an unbroken 14-position (full SKU) field, even if you have the Split SKU Inventory (A26) system control value set to Y.

ZERO ITEM: The item code on the label is preceded by leading zeroes. The system strips off all zeroes but one when you scan the item; for example, if the item code on the label reads 00001234, the system reads the item code as 01234, and validates this code against the Item file.

If you have the Item Number Label Type (E28) system control value set to ZERO ITEM, the system will strip a check digit off the end of the item label if:

• the item code is made up of numeric characters, and

• the item code is scanned in, not entered or keyed in.

The check digit is the 12th digit in the item code, and appears on the far right of the item label. The system uses this character to calculate a further validation against the item code, in which the system performs a modulus check.

The system performs this check:

1. Add together every other digit, starting with the first position.

Example: If the item number were 01234567890 with a check digit of 5, the system adds together 0 +2 + 4 + 6 + 8 + 0 = 20. (Note: The first position would normally be a zero.)

2. Multiply the result by three.

Example: 20 * 3 = 60.

3. Add together every other digit, starting with the second position.

Example: 1 + 3 + 5 + 7 + 9 = 25.

4. Add the two resulting totals together.

Example: 60 + 25 = 85.

5. Subtract this total from the next highest multiple of 10 to determine the check digit.

Example: 90 - 85 = 5. The check digit is 5.

See Warehousing Radio Frequency Overview for more information on radio frequency.

Leave this field blank if you do not use radio frequency in your warehouse.

Location Label Type (E32)

Purpose: Use this screen to define how the system validates the location code on bar-coded labels when you use radio frequency devices.

MSR0051 CHANGE Change System Control Value 10/22/96 8:59:26 Description . : Location Label Type Code . . . . . REGULAR W/CTL CHAR Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the code that identifies how the system will validate the location code on bar-coded labels that you scan with a radio frequency gun.

Valid values are:

• REGULAR (or blank): The system validates the location code against the Location file. The location code is a 7-position, alphanumeric code. This is the default value.

• W/CTL CHAR: In addition to validating the location code against the Location file, the system assumes that the last character on the location code is a control character. It uses this character to calculate a further validation against the location code, in which the system performs a modulus check. In this modulus check, the system adds the values assigned to each character in the location code. The system divides the total of these values by 43, and then compares the remainder by the value of the control character.

If you have this field set to W/CTL CHAR, the location code field will appear with an extra, eighth position on the RF menu screens. For example:

Frm: 2

 

If this field is set to REGULAR or blank, the location code field appears as seven positions only. For example:

Frm: 2

 

Character values: This table provides the value assigned to each character for use in a modulus check against the location code.

0 = 0	B = 11	M = 22	X = 33
1 = 1	C = 12	N = 23	Y = 34
2 = 2	D = 13	O = 24	Z = 35
3 = 3	E = 14	P = 25	- = 36
4 = 4	F = 15	Q = 26	. = 37
5 = 5	G = 16	R = 27	' ' (space) = 38
6 = 6	H = 17	S = 28	R = 39
7 = 7	I = 18	T = 29	/ = 40
8 = 8	J = 19	U = 30	+ = 41
9 = 9	K = 20	V = 31	% = 42
A = 10	L = 21	W = 32

Example:

The location code you enter is BULK01, with a control character of /. The system adds the values of each character in the location code: B = 11 U = 30 L = 21 K = 20 0 = 0 1 = 1 83 The system then divides the result by 43:   83/43 = 1; Remainder = 40   The control character of / has a value of 40. The location passes the modulus check.

When a location code passes the modulus check, the system ignores the control character and treats the location code as a regular, 7-position code.

The modulus check calculation is invisible to the user.

See Warehousing Radio Frequency Overview for more information on using radio frequency devices in your warehouse.

Create Item Transaction History for Non-Inventory Items (E39)

Purpose: Use this screen to define whether the system writes an issue (I) type transaction history record when non-inventory and drop ship items go through billing.

MSR0052 CHANGE Change System Control Value 12/03/96 11:31:28 Description . : Create Item Trans Hist for non - Inv items Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . I/T Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to write an issue (I) type transaction history record for non-inventory and drop ship items when they go through billing. You can view the non-inventory transactions in the Item Transaction History file.

Enter N or leave this field blank if you do not want the system to write an issue (I) type transaction history record for non-inventory and drop ship items when they go through billing.

You can review inventory transaction history records by selecting Display Inventory Transaction History (DITH) from a menu. Issue type transactions used for non-inventory items differ from other issue type transactions in these ways:

• The Old on hand and New on hand fields remain blank since inventory is not affected.

• The code NONINVISSU (non-inventory issue) displays in the ID field for the transaction.

• The Location field remains blank since a location has not been defined for this item.

• A message displays for the transaction:

 

* Non-Inventory/Drop Ship Issue. Press Enter to Display Additional Details.*

 

See Warehousing Display Inventory Transaction History (DITH) for more information.

Sample screen: A sample of the second Inventory Transaction History screen is displayed below.

INR0055 DISPLAY Inventory Transaction History 2/16/98 16:39:41 The Mail Order Company Warehouse . . . . . : 0 Item/SKU . . . . . . : B1016 BINDERS Date/Time/Seq# . . . : 12/05/96 11:54:16 1 Cde Location Quantity Old O/H New O/H Id# I 1 NONINVISSU Batch# . . . . . . . : 0 Transaction# . . . . . : 0 Order# . . . . . . : 985 Invoice# . . . . . . . : 120 Purchase order# . . : 0 Vendor Charge Back No. : Reason . . . . . . . . . : 0 License Plate Number : 0 User . . . . . . : HERB_J G/L account # . . . : 0 Cost . . . . . . : 20.0000 F3=Exit F12=Cancel

Work Order Values (E41)

Purpose: Use this screen to define the sequence the system uses to search location types for the component quantity needed to make up a finished good work order.

MSR0840 ENTER Edit Work Order Values 1/31/97 9:16:13 The Karen Mail Order Company Use Work Order Processing : (Y/N) Sequence to suggest location types *PRIMARY,*SECONDARY,*BULK: First . . . . . . Second . . . . . . Third . . . . . . F3=Exit F12=Cancel

Use Work Order Processing (E37)

Enter Y in this field to use work order processing for finished good items. The system uses the Protected quantity field in the Item Warehouse file to reserve the quantity of component items needed to make up the finished good work order. The quantity in the Protected quantity field is increased for each component item when you create a work order and is decreased when you process the work order.

Enter N or leave this field blank if you do not want to use work order processing for finished goods. A message displays at the bottom of a menu screen if you try to enter the Work with Work Orders function and this system control value is set to N:

 

SCV: E37 must be set to 'Y' to perform Work Order Processing.

 

First Location Type (E42)

Enter in *PRIMARY, *SECONDARY or *BULK to define the type of location the system searches first to fill the component quantity needed on the finished good work order. The system searches for one location type that can fill the entire quantity needed. If one location type does not hold the entire quantity, the system will then break up the quantity between more than one location type.

Second Location Type (E43)

Enter in *PRIMARY, *SECONDARY or *BULK to define the type of location the system searches second to fill the component quantity needed on the finished good work order. The system searches for one location type that can fill the entire quantity needed. If one location type does not hold the entire quantity, the system will then break up the quantity between more than one location type.

Third Location Type (E44)

Enter in *PRIMARY, *SECONDARY or *BULK to define the type of location the system searches third to fill the component quantity needed on the finished good work order. The system searches for one location type that can fill the entire quantity needed. If one location type does not hold the entire quantity, the system will then break up the quantity between more than one location type.

See Warehousing Finished Good Work Order Processing (WWOR) for more information on work orders.

Sold Out Retention Method (E63)

Purpose: Use this screen to define the order in which the system evaluates orders for retention when you process auto soldouts.

MSR0051 CHANGE Change System Control Value 4/23/97 12:19:32 Description . : Sold Out Retention Method Code . . . . . FIFO FIFO LIFO Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter FIFO (first in, first out) in this field to have the system begin evaluating the oldest orders for an item for retention first when you process auto soldouts. The system evaluates orders only if you select an item retention quantity.

Enter LIFO (last in, first out) in this field to have the system begin evaluating the newest orders for an item for retention first when you process auto soldouts. The system evaluates orders only if you select an item retention quantity.

Leave this field blank if you do not intend to retain items from selling out when you process auto soldouts. You will not be able to advance to the Enter Quantity to Retain screen when you process auto soldouts.

Retaining items from selling out: When you process auto soldouts, you may prefer to retain a number of open orders for an item if, for example, you expect to receive that number of returns from customers. You use the Enter Quantities to Retain screen, available by pressing F7 at the Process Auto Soldouts screen, to specify the items you want to retain and the quantities of each. You must first specify the method for the system to use when it selects the orders to hold open.

If you set this system control value to FIFO, each order is evaluated in turn, starting with the oldest order for the item. The system selects an order line for retention only if it can retain the entire backordered quantity of the item. For example, if you set a retention quantity of 3, and the first order line the system evaluates has a backordered quantity of 5, the system skips this order line and evaluates the next. The order line with the quantity of 5 is sold out. The system continues to evaluate all open order lines until it has retained the entire quantity you specified, or until there are no more order lines with backorder quantities less than or equal to the remaining retention amount.

If you set this system control value to LIFO, each order is evaluated, except that the newest orders are evaluated first.

See Customer Service Working with Soldout Controls (WSLD) for more information on processing auto soldouts.

Require Long SKU Division with Long SKU Department (E85)

Purpose: Use this screen to define whether the long SKU division is a required field when you create or change a long SKU department.

MSR0052 CHANGE Change System Control Value 8/05/97 16:48:02 Description . : Require L/S Division with L/S Department? Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 10 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the L/S division field to be required when you create or change a long SKU department.

The L/S division field is a 3-position, alphanumeric field. It is not validated against any CWDirect file. You might use this field for sorting or grouping purposes on reports.

This field is available through the Work with Long SKU Departments (fast path = WLSD) menu option only.

Enter N in this field or leave it blank if you do not want the long SKU division to be a mandatory field when you work with a long SKU department.

See Merchandising Working with Long SKU Classes (WLSC) for more information on working with long SKU departments.

Note: This system control value is part of the Item Values (I91) umbrella system control value, which displays values related to retail point of sale.

Require Item Class in Work with Items (F06)

Purpose: Use this screen to define whether the Item class field is a required field on the Create Item and Change Item screens in Work with Item/SKUs.

MSR0052 CHANGE Change System Control Value 10/23/97 14:39:13 Description . : Require Item Class in Work With Items. Yes/No . . . . (Y,N) Narrative . . . Application . : ALL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the Item class field to be a required field on the Create Item and Change Item screens in Work with Item/SKUs. See Merchandising Performing Initial Item Entry (MITM).

If you are using the CWDirect/CWStore integration, requiring entry of item class may be required if it is part of your retail hierarchy in CWStore, depending on settings defined within theCWIntegrate cw_store site.

An error message displays if you create or change an item and the Item class field is blank: Item class required.

Enter N or leave this field blank if you do not want the Item class field to be a required field on the Create Item and Change Item screens in Work with Item/SKUs.

Item classes are defined in and validated against the Item Class file. See Merchandising Working with Item Classes (WICL).

Gift Wrap Default (F07)

Purpose: Use this screen to define the default setting for the Gift wrap field when you create an item/offer or SKU/offer.

MSR0052 CHANGE Change System Control Value 11/20/97 11:30:40 Description . : Gift Wrap Default Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the Gift wrap field to default to Y when you create an item/offer or SKU/offer through:

• Work with Item/SKUs (fast path = MITM)

• Create Item/SKU Offer (fast path = MISO)

• Update SKU Offers (fast path = MUSO)

The field will default to Y when you use these menu options; however, you can override this value. See Merchandising Assigning Items/SKUs to Offers and Creating Item/SKU Offers (MISO) for more information on these menu options.

The setting you enter here does not default when you use any other menu options to create item/offers or SKU/offers.

Set this field to N or leave it blank if you want the Gift wrap field to default to N in the Work with Item/SKUs, Create Item/SKU Offer, and Update SKU Offers menu options.

Create Location/Item Location/Item Warehouse from PI Upload (F09)

Purpose: Use this screen to define whether to create Location, Item Location, and Item Warehouse records as a result of the physical inventory count upload if these records do not already exist.

MSR0052 CHANGE Change System Control Value 12/23/97 16:47:34 Description . : Create Location/Item Location/Item Warehouse from PI Upload. Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . P/I Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to create Location, Item Location, and Item Warehouse records if they do not already exist in your warehouse.

About physical inventory upload: When you are running a physical inventory, you have the option of entering counts interactively through CWDirect, or uploading a file containing count information. This second option might be your choice if you use an external service, such as RGIS, to count inventory. You use the Uploading Physical Counts (MPIU) menu option to do so.

Why create new records? When you upload physical inventory count information, it is possible that you might not have a record of a particular item in a certain location in your warehouse; you might not even have a record of that location in your warehouse at all. However, the upload file might indicate that you have a quantity of that item on-hand in that location. In this case, you have the option of creating the appropriate Location, Item Location, and Item Warehouse records.

Why do you need defaults? When the physical inventory upload process creates these new records, you do not have an opportunity to indicate the settings to use for any of the required fields. For this reason, you can use the Default Options file to store default settings for the system to use when creating the records. Once the records are created, you can change the records from the defaulted values when necessary.

Set this field to N or leave it blank if you do not want to create new records as a result of the physical inventory upload. When you upload counts that contain locations that do not exist in your warehouse, they will be flagged as errors.

For more information:

• See Physical Inventory Overview for complete information on the system control values that affect whether you can create records through the physical inventory upload and a complete overview of the process.

• See Working with Default Options (WDFT) for more information on working with the Default Options file and on the process you use to create the defaults.

SKU Purge Days (F11)

Purpose: Use this screen to define the number of days to retain SKUs that are not contained on any existing order.

MSR0054 CHANGE Change System Control Value 3/04/98 16:43:05 Description . : SKU Purge Days Number . . . . Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Number field: Enter the number of days you wish to retain SKUs that are not contained on any existing order.

The system uses this number when you purge item/SKUs in Purge SKUs (fast path = MPSK). The system uses the SKU Purge Days system control value to determine how long an item/SKU must have been inactive (an order has not been entered for the item/SKU) to be eligible for purging. For example, if you define 365 as the SKU purge days, an item/SKU will be eligible for purging if the last order date on the SKU record is older than one year. See System Operations Purging SKUs (MPSK) for more information on purging item/SKUs.

Require Sort Sequence Number in the SKU File (F23)

Purpose: Use this screen to define whether the Sort sequence number field on the Create SKU and Change SKU screens in Work with Item/SKUs is a required field.

MSR0052 CHANGE Change System Control Value 3/12/98 17:08:44 Description . : Require Sort Seq# in the SKU File Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . ITM Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the Sort sequence number field on the Create SKU 1 of 2 (With Overrides) Screen and Change SKU screens in Work with Item/SKUs to be a required field.

An error message displays if you do not enter a sort sequence number: Sort Sequence # is required.

Enter N or leave this field blank if you do not want the Sort sequence number field on the Create SKU and Change SKU screens to be a required field.

Note: The SKU sequence number is used to determine the order in which the SKUs sort. See SKU Sort Sequence Numbers for an overview.

Auto Assign Sort Sequence Number During SKU Generation (F24)

Purpose: Use this screen to define whether the system automatically assigns a SKU sort sequence number to each SKU created in the SKU Generator.

MSR0052 CHANGE Change System Control Value 3/13/98 8:16:37 Description . : Auto Assign Sort Seq# during SKU Generation Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . ITM Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to automatically assign a SKU sort sequence number to each SKU created in the SKU Generator. See Merchandising Using the SKU Generator (ESKG).

The SKU sort sequence number is used to determine the order in which the SKUs sort. See SKU Sort Sequence Numbers for an overview.

If the Auto Assign Sort Sequence Number During SKU Generation (F24) system control value is set to Y, the system uses the sort collating sequence number defined in Working with SKU Elements (WSK1, WSK2, WSK3) to determine the SKU sort sequence number to assign to each SKU. The system assigns a SKU sort sequence number to each SKU in increments of 10.

Example: You are generating SKUs for a skirt in colors black and navy, styles petite and regular and sizes small and medium.

In Work with SKU Elements, the sort collating sequence numbers are defined as:

SKU Element 1

black = sort sequence number is blank

navy = sort sequence number is blank

SKU Element 2

petite = sort sequence number is 1

regular = sort sequence number is 12

SKU Element 3

small = sort sequence number is 2

medium = sort sequence number is 5

1. To assign the sort sequence number, the system first retrieves the sort sequence number defined in Work with SKU Element 1. In the example, the colors black and navy are not assigned a sort sequence number. Since they are not assigned a sort number, the system sorts the elements defined in SKU element 1 alphanumerically.

2. The system then retrieves the sort sequence number defined in Work with SKU Element 2. In the example, petite is assigned a sort sequence number of 1 and regular is assigned a sort sequence number of 12. The system sorts petite styles before regular styles.

3. The system then retrieves the sort sequence number defined in Work with SKU Element 3. In the example, small is assigned a sort sequence number of 2 and medium is assigned a sort sequence number of 5. The system sorts small sizes before medium sizes.

4. In the SKU Generator, the system assigns a SKU sort sequence number to each SKU based on the sort collating sequence numbers defined for each SKU element:

Item/SKU	Element 1/ Sequence #	Element 2/ Sequence #	Element 3/ Sequence #	SKU Sort Sequence Number
skirt	black (blank)	petite (1)	small (2)	10.000
skirt	black (blank)	petite (1)	medium (5)	20.000
skirt	black (blank)	regular (12)	small (2)	30.000
skirt	black (blank)	regular (12)	medium (5)	40.000
skirt	navy (blank)	petite (1)	small (2)	50.000
skirt	navy (blank)	petite (1)	medium (5)	60.000
skirt	navy (blank)	regular (12)	small (2)	70.000
skirt	navy (blank)	regular (12)	medium (5)	80.000

Enter N or leave this field blank if you do not want the system to automatically assign a SKU sort sequence number to each SKU created in the SKU Generator.

You can assign a SKU sort sequence number to each SKU of an item in the following ways.

• Enter a SKU sort sequence number in the Sort sequence number field on the Create SKU 1 of 2 (With Overrides) Screen or the Change SKU Screen.

• Select an item that contains SKUs at the Resequence SKU Collating Sequence Number Screen and press Enter to have the system automatically assign a sort sequence number to each SKU. See Assigning SKU Sort Sequence Numbers Based on SKU Element.

• Enter a SKU sort sequence number in the Sort sequence number field on the Work with SKU Generator Screen in Using the SKU Generator (ESKG).

SKU Element for Auto Linking Coordinates (F39)

Purpose: Use this screen to enter the number that represents the SKU element for the system to use when automatically creating linked item coordinate records for an item.

MSR0054 CHANGE Change System Control Value 5/11/98 7:03:02 Description . : SKU Element for Auto Linking Coordinates Number . . . . 1 1 2 3 Narrative . . . Application . : INV Applic group . ITM Sequence# . . . 99 F3=Exit F12=Cancel

Number field: Enter the number that represents the SKU element for the system to use when automatically creating linked item coordinate records for an item. You advance to the Work with Item Coordinates screen by entering 22 next to an item at the Work with Items screen (fast path - MITM).

• Item Coordinates: Item coordinates are related items that may be presented together in an offer and which you might sell or upsell together because they of this relationship. For example, if a customer orders a navy blazer, you might suggest purchase of a matching navy skirt or pants. The item coordinates defined for an item are available in order entry by entering 14 next to the item.

• SKU element for auto linking: When you are setting up item coordinates for an item, the system creates item coordinate records only for SKUs that match the selected SKU element of the primary item. For example, if you sell a blazer in navy, white and black, and you are planning to upsell a matching skirt that comes in navy, black, and purple as an item coordinate, the system automatically creates the item coordinate records for the navy and black SKUs only. In this case, you would SKU element 1, color, was selected for auto linking.

Example:

Item AB100 (blazer) sold in colors NAVY, WHIT and BLCK, sizes SMLL, MEDM, LRGE Item BB100 (skirt) sold in colors NAVY, BLCK, and PURP, sizes 6, 8, 10, 12, 14 SKU element 1 (color) specified as SKU element to use for auto linking Result: System automatically creates item coordinate records for item BB100 in these SKUs: • NAVY 6, 8, 10, 12, 14 • BLCK 6, 8, 10, 12, 14

You also have the option of creating item coordinate records for a specific SKU value only. For example, you could indicate that you want to create item coordinates only for SKUs whose first SKU element, color, is set to NAVY.

Important: The item coordinates are associated with the base item, not the individual SKUs. In the example, the item coordinate SKUs for the skirt would be associated with all SKUs of the blazer, including white SKUs of the blazer. However, you can control which SKUs display in order entry through the SKU Element for Order Entry Filtering (F40) system control value.

Manual linking: In addition to auto linking, you can also create item coordinates for a primary item to any SKU’d or non-SKU’d item.

Example:

Additional item coordinates for item AB100: Item CB100 (blouse) available in WHIT and PINK, sizes 6, 8, 10, 12, 14 Item DB100 (scarf), a non-SKU’d item

Since the items and SKUs do not match the selected SKU element of the primary item, you would create the item coordinate records manually. In this way, you are not restricted to the item coordinates the system creates automatically.

Non-split (full) SKU: The examples are based on a split SKU of three four-position fields. If you use the full SKU of 14 positions, you will not have the opportunity to specify an element for auto linking. However, the system will auto link the primary item to all matching SKUs of the item coordinate, regardless of your entry in this system control value.

Example:

Item BR1000 is available in SILVER, MULTI and GOLD. Item PE1000 is available in SILVER, GOLD and GLDPLATE. Result: Regardless of how this system control value is set, the system will auto link the GOLD and SILVER SKUs of item PE1000 only.

The Split SKU Inventory (A26) system control value controls whether you use a split SKU or a full SKU.

Selecting coordinates in order entry: When you enter an item in order entry that is associated with one or more item coordinates, a message displays informing you that item coordinates exist. If you enter 14 next to the primary item, you advance to a pop-up window which displays the item coordinates. From this window, you can advance to a subsequent window where you can review SKUs or details for an item coordinate and/or add it to the current order.

If this field is blank: This field will not ordinarily be blank, as it is a required field. However, if this field is blank, the system uses the SKU element specified in the Split SKU Element Column 1 Heading (A34) system control value. If this system control value is also blank, the system uses SKU element one.

Creating item coordinates through the upload: When you use the retail integration item upload to assign coordinates to an item, the auto-linking of coordinates does not apply unless you leave the ICN Coordinate SKU field blank and define an offer in the IUP Offer for Item Coord field. See Working with Retail Integration Item Upload (RIIU), specifically Fields for 09 Item Coordinate Record Type for more information.

For more information:

• Merchandising Entering Additional Item Information for information on setting up item coordinates for an item

• Order Entry Working with Items on the Order for information on working with item coordinates in order entry.

Default Company for RF Returns (F45)

Purpose: Use this screen to define whether the current company code defaults on the Return Pull and Put screens in RF.

MSR0052 CHANGE Change System Control Value 4/30/98 11:10:58 Description . : Default Company for RF Returns. Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field to have the code representing your current company default when you process a return pull or put transaction in RF. The cursor will be positioned in the Item field (It) when you advance to either screen.

Enter N in this field or leave it blank if you do not want the company code to default. The cursor will be positioned in the Company field when you advance to either screen.

Radio frequency (RF) technology enables you to enter inventory information on your system by scanning a bar-coded label with a hand-held device. See Warehousing Radio Frequency Overview for more information.

Retail PC Stock Transfer Shared Folder (F50)

Purpose: Use this screen to define the shared folder where the system copies CamData Retail Point of Sale download files.

MSR0053 CHANGE Change System Control Value 6/17/98 11:35:18 Description . : Retail PC Stock Transfer Shared folder System name . . Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

System name field: Enter the name of the shared folder where the system copies CamData Retail Point of Sale download files.

You can download Retail Stock Adjustments files in Download Retail Stock Adjustments (fast path = MDSA). See Warehousing Working with the Retail Point of Sale Interface for more information on the Retail Point of Sale Interface.

Leave this field blank if you do not want to download CamData Retail Point of Sale download files from the iSeries to a PC.

Retail PC POS Sales Upload Shared Folder (F56)

Purpose: Use this screen to define shared folder where the system retrieves CamData Retail Point of Sale upload files.

MSR0053 CHANGE Change System Control Value 10/13/00 8:09:40 Description . : Retail PC POS Sales Upload Shared Folder System name . . Narrative . . . Application . : INV Applic group . UNQ Sequence# . . . 99 F3=Exit F12=Cancel

System name field: Enter the name of the shared folder where the system retrieves CamData Retail Point of Sale upload files.

You can use the Load Cam Data Retail Interface Orders Screen (LPOS) to populate the Phone Orders (PHORDS) File with the information uploaded from Cam Data's POS system for the selected retail store.

The system:

• checks the folder name defined in this system control value to determine the folder where the files should be copied from.

• submits a batch job (CAMDTA_LD).

• maps all of the fields defined in the Point of Sale Receipt (POSSccss.TXT) file to the CWDirect Phone Order file. See Sample Phone Order File Record for more information on how the system maps the Point of Sale Receipt (POSSccss.TXT) fields to the Phone Order fields defined in the Phone Order file.

Leave this field blank if you do not want to retrieve CamData Retail Point of Sale upload files from a shared folder.

Warehouse Replenishment Label Program (F57)

Purpose: Use this screen to define the program name the system uses to print warehouse replenishment labels.

MSR0053 CHANGE Change System Control Value 9/14/98 8:41:31 Description . : Warehouse Replenishment Label Program System name . . Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 1 F3=Exit F12=Cancel

System name field: Enter the program name the system uses to print a warehouse replenishment label for each unit of each item in the replenishment request.

The system prints warehouse replenishment labels when you process a warehouse replenishment in Replenish Warehouses (fast path = MWRP).

The labels print in the same sequence as the warehouse replenishment pick worksheet and contain this information:

• barcode of item and SKU

• item number

• SKU code

• Offer price (The offer price defined for the offer in the Current Offer (A33) system control value. For items containing SKUs, the system uses the SKU offer price; if a SKU offer price has not been defined, the system uses the item offer price. If an offer price has not been defined, the system does not print an offer price.)

See Warehousing Work with Warehouse Replenishment (MWRP) for more information.

Leave this field blank if you do not want the system to print warehouse replenishment labels when you process a warehouse replenishment.

Display Frozen Primary Location Warning Message in Returns (F58)

Purpose: Use this screen to define whether the system displays a warning message pop-up window when you perform a return against an item whose “primary primary” location is frozen due to a physical inventory.

MSR0052 CHANGE Change System Control Value 6/19/98 15:12:08 Description . : Display Frozen Primary Location Warning Message in Returns Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . RTN Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to display a warning message pop-up window when you perform a return against an item whose “primary primary” location (the location defined in the SKU file) is frozen due to a physical inventory (the Physical freeze field in the Item Location file is set to Y). (The “primary primary” location is stored in the Primary loc (Primary location) field in the SKU file.)

This is helpful if you return items to a temporary location before moving them to their primary location.

The system displays the warning message pop-up window when you perform a return:

• in order entry. See Order Entry Posting a Return or Exchange Through Order Entry for more information.

• in order maintenance. See Customer Service Work with Order Screen for more information.

• in Work with Return Authorizations (fast path = WRTA). See Customer Service Working with Return Authorizations: Streamlined Process for more information.

Sample warning message window: This window displays when you perform a return against an item whose “primary primary” location is frozen due to a physical inventory.

Informational message only Item's Primary Location is frozen due to inventory counting. F12=Cancel

Enter N or leave this field blank if you do not want the system to display a warning message pop-up window when you perform a return against an item whose “primary primary” location is frozen due to a physical inventory.

Auto-Generate Item Keywords from Description (F79)

Purpose: Use this screen to define whether the system automatically generates item keywords for an item you are creating using words defined in the item's description.

MSR0052 CHANGE Change System Control Value 2/16/05 10:05:46 Description . : Auto-Generate Item Keywords from Description Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . ITM Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to automatically generate item keywords for an item you are creating using the words defined in the item's description.

When you press Enter on the Create Item screen in Work with Item/SKUs, the system displays a message indicating the item keywords were created: Creating item keywords...please wait

The system creates an item keyword for each word in the item description, except for any words defined in Work with Keyword Exclusions.

Example: You create an item CM8745Y whose item description is “101 chicken recipes for the family.” The words “for” and “the” are defined as keyword exclusions. If the Auto-Generate Keywords at Item Creation system control value is set to Y, the system will automatically create an item keyword for the words “101,” “chicken,” “recipes,” and “family,”

Related system control values: If the Create Keywords at Item Entry (F78) system control value is also set to Y, the system advances you to the First Work with Keywords for Item Screen where you can review the keywords the system automatically generated and also create or delete a keyword. For example, in the example above, you could delete the keyword “101” and add the keyword “cookbook” as keywords for the item CM8745Y.

If the Create Keywords at Item Entry (F78) system control value is set to N, the system does not advance you to the First Work with Keywords for Item Screen. You can review the keywords the system created for a specific item by entering 23 next toan item in Work with Item/SKUs, or you can review keywords for all items in Working with Item Keywords.

Retail integration (external system to CWDirect) item upload: If the Auto-Generate Item Keywords from Description (F79) system control value is set to Y, the system automatically creates keywords for items uploaded using the Working with Retail Integration Item Upload (RIIU).

Enter N or leave this field blank if you do not want the system to automatically generate item keywords for an item using the words defined in the item's description.

Allow Location Class Edit in Inventory Transaction (F86)

Purpose: Use this screen to define whether the system validates the item's location class against the location's location class during inventory transaction processing.

MSR0052 CHANGE Change System Control Value 10/06/98 10:23:24 Description . : Allow Location Class Edit in Inventory Transaction Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . I/T Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y or leave this field blank if you want the system to validate the location class defined for the item against the location class defined for the location during inventory transaction processing.

An error message displays if the item's location class does not match the location's location class:

Item is not compatible with location.

 

The system validates the item's location class against the location's location class when you perform these inventory transactions:

• Adjustment (A) transaction

• Item to Item Transfer (G) transaction

• Makeup Set (M) transaction

• On Hand (O) transaction

• Negative Adjustment (S) transaction

• Transfer (T) transaction

• Return to Vendor (V) transaction

You can perform inventory transactions in these functions:

• Work with Inventory Transactions Immediate (fast path = WITI)

• Work with Inventory Transactions Batch (fast path = WITB)

• Work Order Processing (fast path = WWOR)

SKU location class: If you assign SKUs to a location class at the SKU Location Class/Picks Screen, CWDirect does not validate the SKU’s location class against the location’s location class during inventory transaction processing. Even if the location class assigned to the SKU matches the location class assigned to the location, you receive an error message: Item is not compatible with location. It is recommended that you set this system control value to N if you wish to assign location classes to SKUs.

For more information: See Warehousing Working with Inventory Transactions in Batch Mode (WITB) for more information on inventory transaction processing.

Enter N if you do not want the system to validate the location class defined for the item against the location class defined for the location during inventory transaction processing.

Send Average Cost Changes to PkMS (F92)

Purpose: Use this screen to define whether changes to the average cost generate a PkMS Item Interface transaction.

MSR0052 CHANGE Change System Control Value 4/24/00 11:59:25 Description . : Send Average Cost Changes to PkMS Yes/No . . . . N (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to generate a transaction which passes the information to PkMS when average cost is changed.

If set to N, then no changes are sent through the PkMS Item Interface when you update average cost.

Warehouse Management System Interface (F96)

Purpose: Use this screen to define whether the system will populate the PkMS or the WMS files with information for the Pick, Vendor and Comments files.

MSR0051 CHANGE Change System Control Value 4/24/00 12:01:10 Description . : Warehouse Management Interface (PkMS/WMS) Code . . . . . PKMS WMS PKMS Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code fields: Enter PkMS in this field to have the system pass information from the Pick, Vendor and Comments files to the PkMS files.

Enter WMS in this field to have the system pass information from the Pick, Vendor, and Comments files to the WMS files.

Retail Store Values (G00)

Purpose: Use this screen to define retail store information for retail store promotions and retail store restock.

You can use retail store promotions to define a sale for specific items in selected stores. See Warehousing Working with Store Promotions (WSPR).

You can use retail store restock to create retail store restock orders for selected stores, generate pick slips for the restock orders, and update inventory in the stores. See Warehousing Working with Retail Store Restock (WRSR).

MSR1094 ENTER Edit Retail Store Values 5/20/99 10:10:58 KAL Co. Use Retail Store file . . . . . Y (Y/N) Store Promotions Promotion pricing lead days . . . . . . . . . . . . Promotion pricing end days . . . . . . . . . . . . Promotion Min/Max lead days . . . . . . . . . . . . Promotion Min/Max end days . . . . . . . . . . . . Store Restock Default Order type for Restock orders . . . . . . . . Default Cancel reason for Restock orders . . . . . . Item Status for Restock Order exclusion . . . . . . . Location Class for 'Loose pick' Restock orders . . . Exclude Restock Orders from Posting shipped units . . (Y/N) Max Number of Lines to Include on Store Restock Order Include in-transit loc on hand quantity . . . . . . . . (Y/N) F3=Exit F12=Cancel

Use Retail Store File (G15)

This value defines whether the system advances you to the Create Store, Change Store, and Display Store screens when you are working with a warehouse that represents a retail store in Work with Warehouses.

Enter Y in this field if you wish the system to advance you to the Create Store, Change Store, and Display Store screens when you are working with a warehouse that represents a retail store in Work with Warehouses.

You can set up a warehouse to represent a retail store by entering Y in the Retail outlet field for the warehouse.

If you enter Y in this field, the system also displays additional fields, Protect minimum/maximum, Original retail price, Current Retail price, and Protect Price, on the Create Item Warehouse, Change Item Warehouse, and Display Item Warehouse screens so that you can define additional retail store information.

Enter N or leave this field blank if you do not want the system to advance you to the Create Store, Change Store, and Display Store screens when you are working with a warehouse that represents a retail store in Work with Warehouses.

The system does not advance you to the Store screens regardless of the value defined in the Retail outlet field. Also, the Protect minimum/maximum, Original retail price, Current retail price, and Protect price fields do not display on the Item Warehouse screens.

Store Promotion Pricing Lead Days (G16)

This value defines the number of days the system uses to calculate a pricing start date for a store promotion.

You can use the promotion pricing start date to determine when the prices of items in the promotion should be changed to the promotion price.

To determine the promotion pricing start date, the system subtracts the number defined in the Store Promotion Pricing Lead Days system control value from the promotion start date, using this calculation:

 

promotion start date - promotion pricing lead days = promotion pricing start date

Example:

promotion start date = 6/13 promotion pricing lead days = 2 6/13 - 2 = 6/11 (6/11 is the pricing start date; this is the date the store changes the item's price so that the items are sold at the promotion price).

The system automatically calculates the store promotion pricing start date when you create a store promotion and define a store promotion start date. See Warehousing Working with Store Promotions (WSPR).

Store Promotion Pricing End Days (G17)

This value defines the number of days the system uses to calculate a pricing end date for a store promotion.

You can use the promotion pricing end date to determine when you should stop pricing items using the price defined in the store promotion and go back to pricing the items with their regular store price.

To determine the promotion pricing end date, the system subtracts the number defined in the Store Promotion Pricing End Days system control value from the promotion end date, using this calculation:

 

promotion end date - promotion pricing end days = promotion pricing end date

Example:

promotion end date = 6/19 promotion pricing end days = 4 6/19 - 4 = 6/15 (6/15 is the pricing end date; this is the date you stop pricing items for the store promotion and start pricing the items with the regular store price)

The system automatically calculates the store promotion pricing end date when you create a store promotion and define a store promotion end date. See Warehousing Working with Store Promotions (WSPR).

Store Promotion Minimum/Maximum Lead Days (G18)

This value defines the number of days the system uses to calculate a minimum/maximum override start date for a store promotion.

You can use the promotion minimum/maximum override start date to determine when the amount of stock in the store should be changed for the store promotion.

When the current date falls between the minimum/maximum override start date and the minimum/maximum override end date, the system looks at the minimum quantity and the maximum quantity defined for the rank associated with the store, to determine how much inventory the store needs to restock the store for the promotion.

To determine the store promotion minimum/maximum override start date, the system subtracts the number defined in the Store Promotion Minimum/Maximum Lead Days system control value from the promotion start date, using this calculation:

 

promotion start date - promotion minimum/maximum lead days = promotion minimum/maximum start date

Example:

promotion start date = 6/13 promotion minimum/maximum lead days = 5 6/13 - 5 = 6/8 (6/8 is the minimum/maximum start date; this is the date the store changes the minimum quantity and maximum quantity in the store for the specified items so that the items are available for the promotion).

The system automatically calculates the store promotion minimum/maximum start date when you create a store promotion and define a store promotion start date. See Warehousing Working with Store Promotions (WSPR).

Store Promotion Minimum/Maximum End Days (G19)

This value defines the number of days the system uses to calculate a minimum/maximum override end date for a store promotion.

You can use the promotion minimum/maximum override end date to determine when you should stop updating an item's minimum quantity and maximum quantity so that the item can be reduced to its normal amount of inventory.

When the current date falls between the minimum/maximum override start date and the minimum/maximum override end date, the system looks at the minimum quantity and the maximum quantity defined for the rank associated with the store, to determine how much inventory the store needs to restock the store for the promotion.

To determine the store promotion minimum/maximum override end date, the system subtracts the number defined in the Store Promotion Minimum/Maximum End Days system control value from the promotion end date, using this calculation:

 

promotion end date - promotion minimum/maximum end days = promotion minimum/maximum end date

Example:

promotion end date = 6/19 promotion minimum/maximum end days = 2 6/19 - 2 = 6/17 (6/17 is the minimum/maximum end date; this is the date the store changes the minimum quantity and maximum quantity in the store for the specified items back to the items regular inventory amount so that the store is not overstocked).

The system automatically calculates the store promotion minimum/maximum end date when you create a store promotion and define a store promotion end date. See Warehousing Working with Store Promotions (WSPR).

Exclude Restock Orders from Posting Shipped Units (G20)

This value is not currently implemented.

Default Cancel Reason Code for Store Restock Orders (G21)

This value defines the cancel reason code the system defaults to a restock order detail line that is automatically canceled during Billing.

A restock order line is automatically canceled during Billing if a full or partial quantity of the item is on backorder and the Automatic cancel backorder field for the sold to customer is set to Y. When the automatic cancel backorder field for the sold to customer is set to Y, the system automatically updates the Cancel backorder field on the restock order to Y. The Cancel backorder field indicates that you wish to automatically cancel any order quantity that is on backorder.

The system also defaults this cancel reason code to store add on request items that are excluded from store restock orders (the Exclude store restock field for the item is set to Y). The system adds the store add on request item to the restock order, but then automatically cancels the line, using the default cancel reason code.

Leave this field blank if you do not want to default a cancel reason code to restock order lines that contain a full or partial backorder quantity.

The system leaves any order detail line that contains a backorder quantity in an open status until the backorder quantity can be fulfilled.

Location Class for Loose Pick Store Restock (G22)

This value defines the location class the system uses to determine the items that can be included in a loose pick store restock.

Enter a location class in this field if you wish to define items that are eligible for loose pick store restock. You can define a loose pick store restock for a store by entering L (loose pick) in the Store restock type field for the store.

If the Restock type field for a store is set to L, the system only restocks items that:

• are set up with the location class that is defined in the Location Class for Loose Pick Store Restock system control value.

• contain an on hand quantity that is equal or less than zero.

• that are set up with a maximum quantity that is not equal to zero.

If the location class defined for the item is different than the location class defined in the Location Class for Loose Pick Store Restock system control value, the system never selects this item for restock.

If an item has not been defined with a location class, the system restocks the item using F (full restock type) criteria. See Warehousing Working with Retail Store Restock (WRSR).

Leave this field blank if you do not want to restock stores using the loose pick store restock criteria.

If you do not use loose pick store restock, you must define full restock or out of stock only as the type of restock to use to restock the store. See Warehousing Working with Retail Store Restock (WRSR).

Default Order Type for Store Restock Orders (G23)

This value defines the order type the system defaults to store restock orders.

When you perform a store restock, the system creates a restock order for each store in need of restock. If an order type code has been defined in the Default Order Type for Store Restock Orders system control value, the system defaults this order type to the Order type field on the Order Header screen for the restock order.

Leave this field blank if you do not want the system to default an order type to store restock orders.

If an order type code has not been defined in the Default Order Type for Store Restock Orders system control value, the system does not default an order type to the Order type field on the Order Header screen for the restock order. Any restock order that does not contain an order type, is placed in an error status and must be corrected in batch order entry.

Default Item Status for Exclusion on Store Restock Orders (G24)

This value defines the item status the system uses to determine if an item is excluded from store restock orders.

Enter an item status in this field if you wish the system to exclude any items assigned this item status from store restock orders.

Leave this field blank if you do not want the system to exclude any items from store restock orders.

You can also exclude an item/SKU from a store restock order by entering Y in the Exclude store restock field for the item/SKU. See Merchandising Performing Initial Item Entry (MITM).

Maximum Number of Lines to Include on Store Restock Order (I51)

This value defines the number of order detail lines the system includes on a store restock order before creating a new order. When you perform a store restock, the system creates a separate order detail line for each item eligible for restock.

Example: The Maximum Number of Lines to Include on Store Restock Orders is 5 and the following items are eligible for restock.

Restock Item	Results
ABC	The system creates order 123 and includes item ABC on order line 1.
ABD	The system adds item ABD to order 123 on order line 2.
ABE	The system adds item ABE to order 123 on order line 3.
ABF	The system adds item ABF to order 123 on order line 4.
ABG	The system adds item ABG to order 123 on order line 5.
ABH	The system creates order 124 and includes item ABH on order line 1.
ABI	The system adds item ABI to order 124 on order line 2.

You may wish to lower the number of order lines on a store restock order if you use the Generic Invoice Download API to download invoice information to another system, such as a retail store, for store replenishment. This way, you can keep the Invoice Download XML Message (CWINVOICEOUT) generated from becoming too big.

Leave this field blank if you wish the system to include 999 order lines on a restock order before creating a new order.

Include In-Transit Location On Hand for Retail Replenishment (J89)

Defines whether the system includes the quantity in the in-transit warehouse/location for the retail store in the retail replenishment calculation used to determine how much inventory to move to the retail store. You may wish to include the store in-transit on hand quantity in the retail replenishment calculation to ensure that the retail store is not over-replenished.

Enter Y in this field if you want the system to include the in-transit quantity in the retail replenishment calculation. Example: If the calculated retail replenishment quantity is 45, but 20 units are already in-transit to the retail store, the system will create the retail replenishment for 25 units so that the item in the store is not over-replenished; when the total units are received into the store, the store will have 45 units on-hand (20 in-transit + 25 in retail replenishment = 45).

Enter N or leave this field blank if you do not want the system to include the in-transit quantity in the retail replenishment calculation. Example: If the calculated retail replenishment quantity is 45, but 20 units are already in-transit to the retail store, the system will create the retail replenishment for 45 units; when the total units are received into the store, the store will have 65 units on-hand (20 in-transit + 45 in retail replenishment = 65).

Defining an In-Transit Warehouse/Location

You can specify the in-transit warehouse and location for a retail store at the Create Store Screen. Specifying an in-transit warehouse and location for a retail store allows you to track inventory on a store restock order when it is in-transit between your retail store restock warehouse and the retail store. When you confirm shipment of a retail store restock order for the store, the system transfers the inventory from the Restock from warehouse to the in-transit warehouse. When the store receives the shipment, you can transfer the inventory from the in-transit warehouse to the warehouse representing the retail store, either through a menu option such as Working with Inventory Transactions in Batch Mode (WITB) or through the Generic Inventory Transaction Upload.

If an in-transit warehouse/location is not defined: If an in-transit warehouse/location is not defined for the retail store warehouse, the system does not evaluate the Include In-Transit Location On Hand for Retail Replenishment (J89) system control value; once a pick slip is confirmed for a retail stock order, the system transfers the inventory to the auto restock location for the retail store warehouse.

In-transit warehouse/location setup: In order to include the quantity in the in-transit warehouse/location in the retail replenishment calculation, you must:

• Set up the in-transit warehouse/location as a separate warehouse from the retail store warehouse (the In-trans whs (In-transit warehouse) field defined for the retail store warehouse at the Create Store Screen must contain a warehouse code that is different from the retail store warehouse code).

• Define a separate in-transit location for each retail store so that the location can be used to distinguish the on hand quantity for each retail store.

Note: If the in-transit warehouse is the same warehouse code as the retail store warehouse, the system always includes the in-transit quantity as part of the overall retail warehouse on hand inventory, regardless of the setting of the Include In-Transit Location On Hand for Retail Replenishment (J89) system control value. You must configure CWDirect to have a location in the retail store where the system records received inventory and another in-transit location within the same warehouse. If there are not two distinct locations, you will not be able to differentiate in-transit versus not in-transit inventory.

The table below explains how the system determines the quantity to replenish, based on the setting of the Include In-Transit Location On Hand for Retail Replenishment (J89) system control value and how the in-transit location is set up.

SCV J89	In-Transit Location Setup	Results
Y	The system uses a single in-transit warehouse for all retail stores, but uses a separate in-transit location in the warehouse for each retail store	The system includes the in-transit quantity in the retail replenishment calculation. See Example: Include In-Transit Quantity, Separate In-Transit Location per Store for an example.
Y	The system uses a separate in-transit warehouse and location for each retail store
Y	The system uses a single in-transit warehouse and location for all retail stores	The system includes the in-transit quantity in the retail replenishment calculation. However, because you are using only one in-transit location to distribute inventory to multiple retail stores, the system cannot determine which quantity in the in-transit location is supposed to move to each store and instead considers the full quantity in the in-transit location as being in-transit to each store. If the total quantity in the in-transit location is greater than the minimum required for the retail store, the system does not generate a store replenishment for the store. See Example: Include In-Transit Quantity, Single In-Transit Location for All Stores for an example.
N	The system uses a single in-transit warehouse for all retail stores, but uses a separate in-transit location in the warehouse for each retail store	The system does not include the in-transit quantity in the retail replenishment calculation. See Example: Exclude In-Transit Quantity for an example.
N	The system uses a separate in-transit warehouse and location for each retail store
N	The system uses a single in-transit warehouse and location for all retail stores
N	The system uses a special in-transit location in the retail store warehouse itself to represent the quantity that is in-transit to the store	Regardless of the setting of the Include In-Transit Location On Hand for Retail Replenishment (J89) system control value, the system includes the quantity in the in-transit location in the retail replenishment calculation. See Example: In-Transit Location within Store for an example.
Y

For more information:

• See In-Transit Warehouse/Location Setup Options for more information on how to set up an in-transit warehouse and location.

• See Understanding Store Restock for more information on retail store replenishment.

Example: Include In-Transit Quantity, Separate In-Transit Location per Store

In this example, you set up your in-transit warehouse/location as one of the following:

1. The system uses a single in-transit warehouse for all retail stores, but uses a separate in-transit location in the warehouse for each retail store, or

2. The system uses a separate in-transit warehouse and location for each retail store.

The following warehouses are defined for item AB101.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		1000
In-Transit Setup 1: single in-transit warehouse, separate in-transit location for each store:
100 - In-Transit Warehouse	B010101 - Boston location	0
	C010101 - Nashua location	0
In-Transit Setup 2: separate in-transit warehouse and location for each store:
100 - Boston In-Transit Warehouse	B010101 - Boston location	0
200 - Nashua In-Transit Warehouse	C010101 - Nashua location	0
Retail Stores:
123 - Boston Retail Store Warehouse	1230101 - Restock location min qty = 10, max qty = 50	10
203 - Nashua Retail Store Warehouse	2030101 - Restock location min qty = 10, max qty = 50	8

When you process the retail store replenishment using the Working with Retail Store Restock (WRSR) menu option, the system moves 82 units from the Retail Store Restock Warehouse:

• 40 units from the Retail Store Restock Warehouse to the In-Transit Warehouse - location B010101 to move to the Boston Retail Store.

• 42 units from the Retail Store Restock Warehouse to the In-Transit Warehouse - location C010101 to move to the Nashua Retail Store.

Meanwhile, the Boston Retail Store had sales for the last 10 units and the Nashua Retail Store had sales for 1 unit.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		1000 - 82 = 918
In-Transit Setup 1: single in-transit warehouse, separate in-transit location for each store:
100 - In-Transit Warehouse	B010101 - Boston location	40 (in-transit to Boston store)
	C010101 - Nashua location	42 (in-transit to Nashua store)
In-Transit Setup 2: separate in-transit warehouse and location for each store:
100 - Boston In-Transit Warehouse	B010101 - Boston location	40 (in-transit to Boston store)
200 - Nashua In-Transit Warehouse	C010101 - Nashua location	42 (in-transit to Nashua store)
Retail Stores:
123 - Boston Retail Store Warehouse	1230101 - Restock location min qty = 10, max qty = 50	0 (10 sold)
203 - Nashua Retail Store Warehouse	2030101 - Restock location min qty = 10, max qty = 50	7 (1 sold)

Due to the last minute sales before the in-transit inventory was received into the retail stores, you process a retail store replenishment again. Because the Include In-Transit Location On Hand for Retail Replenishment (J89) system control value is set to Y, the system takes into consideration the inventory in the In-Transit Warehouse:

• Adds 10 units to the retail replenishment to move from the Retail Store Restock Warehouse to the In-Transit Warehouse - location B010101 to the Boston Retail Store, for a total of 50 units.

• Adds 1 unit to the retail replenishment to move from the Retail Store Restock Warehouse to the In-Transit Warehouse - location C010101 to move to the Nashua Retail Store, for a total of 43 units.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		918 - 11 = 907
In-Transit Setup 1: single in-transit warehouse, separate in-transit location for each store:
100 - In-Transit Warehouse	B010101 - Boston location	40 + 10 = 50 units in-transit to Boston store
	C010101 - Nashua location	42 + 1 = 43 units in-transit to Nashua store
In-Transit Setup 2: separate in-transit warehouse and location for each store:
100 - Boston In-Transit Warehouse	B010101 - Boston location	40 + 10 = 50 units in-transit to Boston store
200 - Nashua In-Transit Warehouse	C010101 - Nashua location	42 + 1 = 43 units in-transit to Nashua store
Retail Stores:
123 - Boston Retail Store Warehouse	1230101 - Restock location min qty = 10, max qty = 50	0
203 - Nashua Retail Store Warehouse	2030101 - Restock location min qty = 10, max qty = 50	7

The retail stores receive the store restock orders, transferring the inventory from the In-Transit Warehouse into the retail stores.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		910
In-Transit Setup 1: single in-transit warehouse, separate in-transit location for each store:
100 - In-Transit Warehouse	B010101 - Boston location	0
	C010101 - Nashua location	0
In-Transit Setup 2: separate in-transit warehouse and location for each store:
100 - Boston In-Transit Warehouse	B010101 - Boston location	0
200 - Nashua In-Transit Warehouse	C010101 - Nashua location	0
Retail Stores:
123 - Boston Retail Store Warehouse	1230101 - Restock location min qty = 10, max qty = 50	50 (moved from the Boston location in the In-Transit Warehouse)
203 - Nashua Retail Store Warehouse	2030101 - Restock location min qty = 10, max qty = 50	50 (7 + 43 moved from the Nashua location in the In-Transit Warehouse)

Example: Include In-Transit Quantity, Single In-Transit Location for All Stores

In this example, the system uses a single in-transit warehouse and location for all retail stores.

The following warehouses are defined for item AB101.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		1000
In-Transit Warehouse:
100 - In-Transit Warehouse	MAIN - in-transit location for all retail stores	0
Retail Stores:
123 - Boston Retail Store Warehouse	1230101 - Restock location min qty = 10, max qty = 50	10
203 - Nashua Retail Store Warehouse	2030101 - Restock location min qty = 10, max qty = 50	8

When you process the retail store replenishment using the Working with Retail Store Restock (WRSR) menu option, the system moves 82 units from the Retail Store Restock Warehouse:

• 40 units from the Retail Store Restock Warehouse to the In-Transit Warehouse to move to the Boston Retail Store.

• 42 units from the Retail Store Restock Warehouse to the In-Transit Warehouse to move to the Nashua Retail Store.

Meanwhile, the Boston Retail Store had sales for the last 10 units and the Nashua Retail Store had sales for 1 unit.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		1000 - 82 = 918
In-Transit Warehouse:
100 - In-Transit Warehouse	MAIN - in-transit location for all retail stores	82 (40 in-transit to Boston store and 42 in-transit to Nashua store)
Retail Stores:
123 - Boston Retail Store Warehouse	1230101 - Restock location min qty = 10, max qty = 50	0 (10 sold)
203 - Nashua Retail Store Warehouse	2030101 - Restock location min qty = 10, max qty = 50	7 (1 sold)

Due to the last minute sales before the in-transit inventory was received into the retail stores, you process a retail store replenishment again. However, because you are using only one in-transit location to distribute inventory to multiple retail stores, the system cannot determine which quantity in the in-transit location is supposed to move to each store and instead considers the full 82 units as being in-transit to each store. Because 82 units is more than is needed for each store, the system does not generate a new store replenishment for either store.

The retail stores receive the store restock orders, transferring the inventory from the In-Transit Warehouse into the retail stores.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		918
In-Transit Warehouse:
100 - In-Transit Warehouse	MAIN - in-transit location for all retail stores	0
Retail Stores:
123 - Boston Retail Store Warehouse	1230101 - Restock location min qty = 10, max qty = 50	40 (moved from the In-Transit Warehouse)
203 - Nashua Retail Store Warehouse	2030101 - Restock location min qty = 10, max qty = 50	49 (7 + 42 moved from the In-Transit Warehouse)

Example: Exclude In-Transit Quantity

In this example, you set up your in-transit warehouse/location as one of the following:

1. The system uses a single in-transit warehouse for all retail stores, but uses a separate in-transit location in this warehouse for each retail store, or

2. The system uses a separate in-transit warehouse and location for each retail store, or

3. The system uses a single in-transit warehouse and location for all retail stores.

The following warehouses are defined for item AB101

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		1000
In-Transit Setup 1: single in-transit warehouse, separate in-transit location for each store:
100 - In-Transit Warehouse	B010101 - Boston location	0
	C010101 - Nashua location	0
In-Transit Setup 2: separate in-transit warehouse and location for each store:
100 - Boston In-Transit Warehouse	B010101 - Boston location	0
200 - Nashua In-Transit Warehouse	C010101 - Nashua location	0
In-Transit Setup 3: single in-transit warehouse and location for all stores:
100 - In-Transit Warehouse	MAIN - in-transit location for all retail stores	0
Retail Stores:
123 - Boston Retail Store Warehouse	1230101 - Restock location min qty = 10, max qty = 50	10
203 - Nashua Retail Store Warehouse	2030101 - Restock location min qty = 10, max qty = 50	8

When you process the retail store replenishment using the Working with Retail Store Restock (WRSR) menu option, the system moves 82 units from the Retail Store Restock Warehouse:

• 40 units from the Retail Store Restock Warehouse to the In-Transit Warehouse - location B010101 (or the MAIN location for in-transit setup 3) to move to the Boston Retail Store.

• 42 units from the Retail Store Restock Warehouse to the In-Transit Warehouse - location C010101 (or the MAIN location for in-transit setup 3) to move to the Nashua Retail Store.

Meanwhile, the Boston Retail Store had sales for the last 10 units and the Nashua Retail Store had sales for 1 unit.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		1000 - 82 = 918
In-Transit Setup 1: single in-transit warehouse, separate in-transit location for each store:
100 - In-Transit Warehouse	B010101 - Boston location	40 (in-transit to Boston store)
	C010101 - Nashua location	42 (in-transit to Nashua store)
In-Transit Setup 2: separate in-transit warehouse and location for each store:
100 - Boston In-Transit Warehouse	B010101 - Boston location	40 (in-transit to Boston store)
200 - Nashua In-Transit Warehouse	C010101 - Nashua location	42 (in-transit to Nashua store)
In-Transit Setup 3: single in-transit warehouse and location for all stores:
100 - In-Transit Warehouse	MAIN - in-transit location for all retail stores	82 (40 in-transit to Boston store and 42 in-transit to Nashua store)
Retail Stores:
123 - Boston Retail Store Warehouse	1230101 - Restock location min qty = 10, max qty = 50	0 (10 sold)
203 - Nashua Retail Store Warehouse	2030101 - Restock location min qty = 10, max qty = 50	7 (1 sold)

Due to the last minute sales before the in-transit inventory was received into the retail stores, you process a retail store replenishment again. Because the Include In-Transit Location On Hand for Retail Replenishment (J89) system control value is set to N, the system does not take into consideration the inventory in the In-Transit Warehouse:

• Adds 50 units to the retail replenishment to move from the Retail Store Restock Warehouse to the In-Transit Warehouse - location B010101 (or the MAIN location for in-transit setup 3) to the Boston Retail Store, for a total of 90 units.

• Adds 43 units to the retail replenishment to move from the Retail Store Restock Warehouse to the In-Transit Warehouse - location C010101 (or the MAIN location for in-transit setup 3) to move to the Nashua Retail Store, for a total of 85 units.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		918 - 93 = 825
In-Transit Setup 1: single in-transit warehouse, separate in-transit location for each store:
100 - In-Transit Warehouse	B010101 - Boston location	40 + 50 = 90 units in-transit to Boston store
	C010101 - Nashua location	42 + 43 = 85 units in-transit to Nashua store
In-Transit Setup 2: separate in-transit warehouse and location for each store:
100 - Boston In-Transit Warehouse	B010101 - Boston location	40 + 50 = 90 units in-transit to Boston store
200 - Nashua In-Transit Warehouse	C010101 - Nashua location	42 + 43 = 85 units in-transit to Nashua store
In-Transit Setup 3: single in-transit warehouse and location for all stores:
100 - In-Transit Warehouse	MAIN - in-transit location for all retail stores	175 (90 in-transit to Boston store and 85 in-transit to Nashua store)
Retail Stores:
123 - Boston Retail Store Warehouse	1230101 - Restock location min qty = 10, max qty = 50	0
203 - Nashua Retail Store Warehouse	2030101 - Restock location min qty = 10, max qty = 50	7

The retail stores receive the store restock orders, transferring the inventory from the In-Transit Warehouse into the retail stores.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		825
In-Transit Setup 1: single in-transit warehouse, separate in-transit location for each store:
100 - In-Transit Warehouse	B010101 - Boston location	0
	C010101 - Nashua location	0
In-Transit Setup 2: separate in-transit warehouse and location for each store:
100 - Boston In-Transit Warehouse	B010101 - Boston location	0
200 - Nashua In-Transit Warehouse	C010101 - Nashua location	0
In-Transit Setup 3: single in-transit warehouse and location for all stores:
100 - In-Transit Warehouse	MAIN - in-transit location for all retail stores	0
Retail Stores:
123 - Boston Retail Store Warehouse	1230101 - Restock location min qty = 10, max qty = 50	90 (moved from the in-transit Warehouse)
203 - Nashua Retail Store Warehouse	2030101 - Restock location min qty = 10, max qty = 50	92 (7 + 85 moved from the in-transit warehouse)

Example: In-Transit Location within Store

In this example, the system uses a special in-transit location in the retail store warehouse itself to represent the quantity that is in-transit to the store.

When you use a special in-transit location in the retail store warehouse, the system always includes the in-transit quantity in the retail store replenishment calculation, regardless of the setting of the Include In-Transit Location On Hand for Retail Replenishment (J89) system control value.

The following warehouses are defined for item AB101.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		1000
Retail Stores with in-transit location within store:
123 - Boston Retail Store Warehouse	INTRANS - Boston in-transit location	0
	1230101 - Restock location min qty = 10, max qty = 50	10
203 - Nashua Retail Store Warehouse	INTRANS - Nashua in-transit location	0
	2030101 - Restock location min qty = 10, max qty = 50	8

When you process the retail store replenishment using the Working with Retail Store Restock (WRSR) menu option, the system moves 82 units from the Retail Store Restock Warehouse:

• 40 units from the Retail Store Restock Warehouse to the Boston in-transit location to move to the Boston Retail Store.

• 42 units from the Retail Store Restock Warehouse to the Nashua in-transit location to move to the Nashua Retail Store.

Meanwhile, the Boston Retail Store had sales for the last 10 units and the Nashua Retail Store had sales for 1 unit.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		1000 - 82 = 918
Retail Stores with in-transit location within store:
123 - Boston Retail Store Warehouse	INTRANS - Boston in-transit location	40
	1230101 - Restock location min qty = 10, max qty = 50	0 (10 sold)
203 - Nashua Retail Store Warehouse	INTRANS - Nashua in-transit location	42
	2030101 - Restock location min qty = 10, max qty = 50	7 (1 sold)

Due to the last minute sales before the in-transit inventory was received into the retail stores, you process a retail store replenishment again. However, because you are using a special in-transit location in the retail store warehouse itself, the system considers the in-transit quantity as part of the retail store quantity and does not generate a new store replenishment for either store.

The retail stores receive the store restock orders, transferring the inventory from the in-transit location into the retail stores.

Warehouse	Location	On Hand Qty
554 - Retail Store Restock Warehouse		918
Retail Stores with in-transit location within store:
123 - Boston Retail Store Warehouse	INTRANS - Boston in-transit location	0
	1230101 - Restock location min qty = 10, max qty = 50	40 (moved from the Boston in-transit location)
203 - Nashua Retail Store Warehouse	INTRANS - Nashua in-transit location	0
	2030101 - Restock location min qty = 10, max qty = 50	49 (7 + 42 moved from the Nashua in-transit location)

Exclude Pieces Per Case for Retail Store Restock (K82)

Defines whether the system considers the pieces per case value for an item in the retail replenishment calculation used to determine how much inventory to move to the retail store.

Enter Y in this field if you want the system to exclude the pieces per case value for an item in the retail replenishment calculation used to determine how much inventory to move to the retail store.

Enter N or leave this field blank if you want the system to include the pieces per case value for an item in the retail replenishment calculation used to determine how much inventory to move to the retail store.

Store restock replenishment quantity: When restocking an item, the system uses the highest minimum and maximum quantities for an item in the item warehouse or any active store promotions for the store’s rank, that it finds. The system can combine the minimum and maximum quantities from different sources. For example, it might use the highest minimum quantity from the item warehouse, and the highest maximum quantity from an active promotion.

• If the Exclude Pieces Per Case for Retail Store Restock (K82) system control value is set to Y, the system does not consider the pieces per case specified for an item when determining the restock quantity. The system uses the restock quantity from the above calculation as the restock order quantity. Example: If the pieces/case is 20 and the calculated restock quantity is 45, the system creates a restock quantity of 45.

• If the Exclude Pieces Per Case for Retail Store Restock (K82) system control value is set to N, the system considers the pieces per case specified for an item when determining the restock quantity:

• If a pieces/case metric has not been specified for the item, the system uses the restock quantity from the above calculation as the restock order quantity. Example: If the pieces/case is 20 and the calculated restock quantity is 45, the system creates a restock quantity of 45.

• If a pieces/case metric has been specified for the item, then the restock quantity is the multiple of the pieces/case metric that is closest to the calculated restock quantity. Example: If the pieces/case is 20 and the calculated restock quantity is 45, the system creates a restock quantity of 40 (20 * 2). If the pieces/case is 20 and the calculated restock quantity is 55, the system creates a restock quantity of 60 (20 *3). You specify the pieces/case through Performing Initial Item Entry (MITM).

Default Primary Location from an Item Warehouse (G06)

Purpose: Use this screen to indicate if a primary location for an item will default for a specified warehouse when performing inventory/receipt transactions.

MSR0052 CHANGE Change System Control Value 11/30/99 9:56:43 Description . : Default Primary Location from an Item Warehouse Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . W/M Sequence# . . . 50 F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, a primary location for an item in the warehouse specified for an inventory or receipt transaction will default to the Location field. If more than one primary location has been defined for the item in the specified warehouse, the system will default the first, in alphanumeric order.

Enter N if you do not want the system to default the first alphanumeric primary location for an item in the warehouse you specify in an inventory or receipt transaction.

Related system control values: This system control value will override the Default Primary Location (C05) system control value, which specifies that in inventory transactions, the system will default the primary location for an item from the Item/SKU file, if the warehouse specified is the item's primary warehouse (as defined in the Item/SKU file).

This system control value will also override the Default Primary Location - Suspense Placement and PO Receipts (C08) system control value, which specifies that in receipt transactions, the system will default the primary location for an item from the Item/SKU file, if the warehouse specified is the item's primary warehouse (as defined in the Item/SKU file).

Example: You have defined these values for Item X:

Item/SKU file
Item X	Primary warehouse: 100 Primary location: A999999 (primary primary; the “primary primary” location is stored in the Primary loc (Primary location) field in the SKU file.)
Item/Warehouse File
Item X	Warehouse: 100 Primary location: A111111 Primary location: A999999
You are performing an inventory transaction for Item X in Warehouse 100, and the Default Primary Location (C05) system control value is set to Y. If the Default Primary Location from an Item Warehouse (G06) system control value is set to N, the system will default location A999999 (Item X's primary primary location from the Item/SKU file). If the Default Primary Location from an Item Warehouse (G06) system control value is set to Y, the system will default location A111111 (the first alphanumeric item/warehouse location for Item X in Warehouse 100).

Item locations are defined in and validated against the Item Location file. See Warehousing Creating and Maintaining Item Warehouses.

Warehouse Replenishment Pick Worksheet Print Program (G25)

Purpose: Use this screen to define the program for the system to use when printing the Replenishment Pick Worksheet for warehouse replenishment.

MSR0053 CHANGE Change System Control Value 10/05/99 9:06:14 Description . : Warehouse Replenishment Pick Worksheet Print Program System name . . FLR0335 Narrative . . . Application . : INV Applic group . UNQ Sequence# . . . 8 F3=Exit F12=Cancel

System name field: Enter the program name for the system to use to generate the Replenishment Pick Worksheet for warehouse replenishment. The default program is FLR0335.

The Replenishment Pick Worksheet is generated automatically when you create a warehouse replenishment request using the standard process. You can also generate the worksheet by pressing F7 at the Work with Warehouse Replenishment Detail screen for both standard process and outlet transfer replenishment requests. You can display this screen by entering 5 next to a replenishment request at the Work with Warehouse Replenishment screen in Replenish Warehouses (fast path = MWRP).

If you leave this field blank, no replenishment pick worksheet will print.

For more information:

• Warehousing Replenish Warehouses Overview for an overview of both standard process and outlet transfer replenishment

• Warehousing Creating a Warehouse Replenishment Request for information on generating the Replenishment Pick Worksheet automatically when generating a standard process replenishment request, and a sample worksheet

• Warehousing Processing, Confirming and Unallocating Replenishment Requests for information on the Work with Warehouse Replenishment Detail screen.

Item Number Cross Reference Program (G40)

Purpose: Use this screen to define the program name the system uses to translate CWDirect item and SKU codes to another system's item and SKU codes.

MSR0053 CHANGE Change System Control Value 8/10/99 13:06:46 Description . : Item Number Cross Reference Program System name . . Narrative . . . Application . : INV Applic group . ITM Sequence# . . . 130 F3=Exit F12=Cancel

System name field: Enter the program name you wish the system to use to translate CWDirect item and SKU codes to another system's item and SKU codes.

You may want to translate CWDirect item and SKU codes to another system's item and SKU codes if you send and receive information with a retail store system, such as RA DOS. See Warehousing Working with the RA DOS Download Interface.

Leave this field blank if you do not want to translate CWDirect item and SKU codes to another system's item and SKU codes.

Require Entity in Item File (G44)

Purpose: Use this screen to define whether the Entity field on the Create Item and Change Items screens in Work with Items is a required field.

MSR0052 CHANGE Change System Control Value 10/05/99 10:09:05 Description . : Require Entity in Item File Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . ITM Sequence# . . . 25 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the Entity field on the Create Item Screen and Change Item screen in Work with Items to be a required field.

An error message displays if you do not enter an entity code:

 

Entity required.

 

An error message displays if the code you enter is not a valid entity code:

 

Entity not found.

 

Enter N or leave this field blank if you do not want the Entity field on the Create Item and Change Item screens to be a required field.

The Entity field in the Item file is informational only. An order is associated with an entity through the source code on the order header; for the purposes of accounting, tracking order history, determining vendor response codes, and overriding system control values at the entity level, this source code entity will override any entity assigned to an item on the order. See Setting Up Order Entry Values and Setting Up Customer Service Values for information on the system control values that determine how you use entity for these purposes.

Display "No Primary Location" Message in Returns (G46)

Purpose: Use this screen to define whether the system displays a warning message pop-up window when you perform a return against an item which does not have a primary location.

MSR0052 CHANGE Change System Control Value 9/29/99 14:50:49 Description . : Display "No Primary Location" Message in Returns Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . RTN Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to display a warning message pop-up window when you perform a return against an item which does not have a primary location defined in the SKU file.

This is helpful if you perform returns against items that have been liquidated and sold through an outlet.

The system displays the warning message pop-up window when you perform a return:

• in order entry. See Order Entry Posting a Return or Exchange Through Order Entry.

• in order maintenance. See Customer Service Returning and Exchanging Items.

• in Work with Return Authorizations (fast path = WRTA). See Customer Service Working with Return Authorizations: Standard Process for more information.

This window displays regardless of whether the return disposition code you enter for the return specifies that items should be returned to their primary locations.

Sample warning message window: This window displays when you perform a return against an item which does not have a primary location.

Primary Location for Item does not exist. F12=Cancel

Enter N or leave this field blank if you do not want the system to display a warning message pop-up window when you perform a return against an item which does not have a primary location defined in the SKU file.

UPC Validation Program (G62)

Purpose: Use this screen to define the validation the system performs when you create a UPC code for an item/SKU.

MSR0053 CHANGE Change System Control Value 10/26/99 8:25:12 Description . : UPC Validation Program System name . . Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 210 F3=Exit F12=Cancel

System name field: Enter the program name you wish the system to use to validate the UPC codes you create for an item/SKU.

The base program name is INR1620. The base program only validates that UPC codes created for the UPC type UA contain 12 digits.

You can create a UPC code for an item/SKU on the Work with UPC screen in Work with Item/SKUs. See Merchandising Entering Additional Item Information.

The types of UPC codes you can create are:

• E13: EAN-13

• E8: EAN-8

• UA: UPC-A

• UE: UPC-E

You can use the UPC codes you create for an item/SKU to enter or scan the item during pick/pack verification. See Fulfillment Working with Pick/Pack Verification (WPPV).

Leave this field blank if you do not want the system to validate the UPC codes you create for an item/SKU.

Default Primary Warehouse in RF (G32)

Purpose: Use this screen to define whether an item/SKU's primary warehouse, as identified in the SKU file, should default on several RF screens, including each "put" screen.

MSR0052 CHANGE Change System Control Value 12/06/99 9:25:49 Description . : Default Primary Warehouse in RF Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . RF Sequence# . . . 120 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have an item/SKU's primary warehouse, as identified in the SKU file, default on RF (Radio Frequency) screens.

The primary warehouse will default on these screens:

• Receiving Put Stock screen

• Replenishment Put Stock screen

• LPN Transfer Put Stock screen

• Item Transfer Pull Stock screen

• Item Transfer Put Stock screen

• Item Inquiry screen

• Item Return Put Stock screen

Set this field to N or leave it blank to have the warehouse identified in the Default Warehouse (A04) system control value, default on the RF screens mentioned, or if you do not use the RF interface. See Setting Up Fulfillment Values.

About RF: Each of the screens mentioned is available through the RF (radio frequency) menus, which you can use to manage your inventory with a radio frequency device. Although you can advance to the RF menus from a standard CWDirect screen, the RF menus are designed for use on an RF gun, where you can either enter or scan in information. Normally, you will have warehouse staff who advance directly to the RF menus when they sign on, as they will always be using the RF guns. See Warehousing Radio Frequency Overview.

Defining the primary warehouse: You define an item/SKU's primary warehouse on the Create/Change SKU (Base Information) screen for non-SKUed item, or the Create/Change SKU 1 of 2 (With Overrides) screen for SKUed items. See Merchandising Performing Initial Item Entry (MITM).

Pending Putaway Due Date Days (G92)

Purpose: Use this screen to define the number of days to add to the transaction date when calculating a pending putaway due date for inventory that is not associated with a purchase order.

MSR0054 CHANGE Change System Control Value 2/14/00 9:57:31 Description . : Pending Putaway Due Date Days Number . . . . Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Number field: Enter the number you wish the system to add to the inventory transaction date when calculating a pending putaway due date for inventory that is not associated with a purchase order.

The pending putaway due date is the date stock in the pending putaway or pending transfer warehouse is expected to be received in the “final destination” warehouse.

Pending warehouses are warehouses where you can place inventory that is on its way to its final destination, for example, a staging area. You can use the Display Pending Putaway Details Screen (Purchase Order View) to review inventory information for items that have been placed in a pending warehouse.

The system creates a pending putaway due date when you place inventory into a pending warehouse. A separate due date is created for each transaction that places inventory in a pending putaway warehouse.

Determining the pending putaway due date:

• If the inventory is associated with a purchase order, the purchase order due date is used.

• If the inventory is not associated with a purchase order, for example when you perform an inventory transfer, the system adds the number defined in the Pending Putaway Due Date Days system control value to the date the inventory transaction was performed: date of inventory transaction + number defined in SCV G92 = pending putaway due date days

Example: You perform an inventory adjustment for item A123 in the pending putaway warehouse on 6/20. The number defined in the Pending Putaway Due Date Days system control value is 6.

6/20 + 6 = 6/26 (pending putaway due date)

Inventory Transaction	Pending putaway due date
PO receipt	due date defined on purchase order
Transfer	date transfer was performed + the number defined in SCV G92

Leave this field set to zero if you want the system to use the date when the inventory transaction was performed as the pending putaway due date, or if you do not place inventory into a pending warehouse.

For more information: See Pending Putaway Overview.

Use Retail Integration (H26)

Purpose: Use this screen to determine whether you want CWDirect to change certain file structures to support integrating merchandise information from an external system into CWDirect.

MSR0052 CHANGE Change System Control Value 10/23/00 9:34:57 Description . : Use Retail Integration Functionality? Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . R/I Sequence# . . . 141 F3=Exit F12=Cancel

Yes/No field: If you set this field to Y, you indicate that you want to integrate and maintain merchandise information from an external system into CWDirect through an item upload or through creating and adding retail information within CWDirect, using the long SKU values listed below. When you use this integration, you can upload item information interactively or in a batch to create, change or delete specific item/SKU information.

Long SKU Values: When this system control value is set to Y, the following long SKU values for a base item are required:

• L/S department (if you wish to require long SKU department only, enter Y in the Require L/S Department (I92) system control value)

• L/S class (if you wish to require long SKU class only, enter Y in the Require L/S Class (I93) system control value)

• L/S style (if you wish to require long SKU style at the SKU level only, enter Y in the Require L/S Style (I94) system control value)

• L/S vendor

Retail classes: Retail classes are long SKU classes that are linked to a long SKU department. When this system control value is set to Y, the system:

• defines long SKU classes (retail classes) in the Retail Class file instead of the Long SKU Class file. See the Work with Retail Class Screen.

• does not allow you to enter the Working with Long SKU Classes (WLSC) menu option since the system reads the Retail Class file instead of the Long SKU Class file.

• requires a value in the L/S Class field (retail class) that is linked to the department in the L/S Dept field when you create or maintain items in Work with Items/SKUs (MITM). When you prompt (press F4) on the L/S Class field, only retail classes display for the long SKU department specified.

• a SKU’s long SKU class (retail class) is linked to the base item’s long SKU department; therefore, when you create SKUs in the SKU Generator (ESKG) and you want to override the base item’s retail class, you must enter a retail class (L/S Class field) that corresponds to the base item’s long SKU department. See the Work with SKU Generator Screen.

Set this field to N or leave it blank if you do not use Retail Integration (external system to CWDirect), or if you wish to use Retail Integration without requiring long SKU values for a base item or linking a long SKU class (retail class) to a long SKU department.

For more information:

• Retail Integration (External System into CWDirect) Overview and Setup

• retail item upload: Working with Retail Integration Item Upload (RIIU) and Retail Integration Job Control (RIJC)

Create Supporting Files during Retail Item Upload (H27)

Purpose: Use this screen to define whether you can create new supporting file values with the information you pass to CWDirect through the Retail Integration (external system to CWDirect) Item Upload.

MSR0052 CHANGE Change System Control Value 11/10/00 11:25:59 Description . : Create Supporting Files during Retail item Upload. Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . R/I Sequence# . . . 140 F3=Exit F12=Cancel

Yes/No field: If you set this field to Y, the system automatically creates values in the following secondary files:

• SKU Element 1

• SKU Element 2

• SKU Element 3

• Item Warehouse

• Item Location

• Item Class

• Item Status

• Buyer

• L/S Department

• L/S Division

• L/S Class

• Retail Class

• Item Category

• Prep Code

Example: If you want to create a new retail class for an item, you can pass new or existing values for long SKU class and long SKU department and the system will first create these values (if new) and then link them together to create a retail class.

No other supporting files are eligible to be created through the retail item upload.

Description? If the supporting file requires a description for a new record, the system uses the supporting file code as the description. For example, if the retail item upload includes a buyer code of HEB, the buyer description is also set to HEB when the system creates the new buyer.

Set this field to N or leave it blank if you do not want to create supporting file values during the Retail Integration (external system to CWDirect) Item Upload. In this case, if you try to pass new secondary file values in the item upload, the record are placed in error status displaying an invalid value message, and you need to create the value(s) manually before reprocessing the item upload record. You must use already existing values or valid combination of these values.

For more information:

• retail item upload overview and setup: Merchandising Retail Integration (External System into CWDirect) Overview and Setup

• retail item upload: Merchandising Working with Retail Integration Item Upload (RIIU)

Use Retail Price Change Processing (H29)

Purpose: Use this screen to define whether you use retail price change processing.

MSR0052 CHANGE Change System Control Value 11/29/00 14:22:42 Description . : Use Retail Price Change Processing Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . R/I Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you wish to use retail price change processing.

You may wish to upload retail price changes into CWDirect if you want to keep merchandise information in CWDirect in sync with merchandise information at your retail store. You can carry the same merchandise and offer your customers the same merchandise pricing in your retail store, catalog, and online channels.

If you use retail price change processing, you can:

• create or work with retail price change upload records in Working with Retail Price Change Upload (WRPU). Use this menu option to upload retail price changes into the RI Price Change file.

• create or work with retail price change records in Working with Retail Price Changes (WRPC). Use this menu option to update retail price change records to the RI Price Change History Detail file. The retail price change history record indicates the date the retail price was created, the retail price, and the date the retail price is effective.

• track retail price change history for an item/SKU at the Retail Price Change History Summary Screen.

• update the price for an item/SKU with the most recent retail price in all active offers.

• update open order lines with the most recent retail price if the Allow Retail Price Change Updates on Open Lines (H30) system control value is set to Y.

Enter N or leave this field blank if you do not want to use retail price change processing.

If this system control value is not selected, you cannot:

• create retail price change upload records in Working with Retail Price Change Upload (WRPU). A message displays when you try to create or modify a retail price change upload record or submit the Retail Price Change Upload Process:

 

SCV H29 (Use Retail Price Change Processing) must be set to ’Y’.

 

• create retail price change records in Working with Retail Price Changes (WRPC). The above message displays when you try to modify a retail price change record or submit the Retail Price Change Update Process.

• update the price of an item/SKU with the most recent retail price in all active offers.

• track retail price change history for an item/SKU at the Retail Price Change History Summary Screen.

For more information:

• retail integration (external system to CWDirect) overview and setup: Merchandising Retail Integration (External System into CWDirect) Overview and Setup.

• retail price change upload: Merchandising Working with Retail Price Change Upload (WRPU).

• retail price change: Merchandising Working with Retail Price Changes (WRPC).

• retail price change history: Merchandising Reviewing Retail Price Change History.

Allow Retail Price Change Updates on Open Lines (H30)

Purpose: Use this screen to define whether the system updates order lines with the most recent retail price.

MSR0052 CHANGE Change System Control Value 11/29/00 14:27:06 Description . : Allow Retail Price Change Updates on Open Lines Yes/No . . . . (Y,N) Narrative . . . Application . : INV Applic group . R/I Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to update order lines with the most recent retail price.

The system updates order lines with the most recent retail price that are:

• backordered

• reserved

• printed (Note: the customer receives an invoice for the retail price instead of the price given at the time of order entry)

• suspended

• contain errors

The system does not update these order lines, unless the price override reason code defined for the line matches the code defined in the Price Override for Retail Price Change Lines (H32) system control value:

• shipped

• canceled

• soldout

• manually overridden by an operator with a new price

Price override reason: In order to update order lines with the most recent retail price, you must enter a price override reason code in the Price Override for Retail Price Change Lines (H32) system control value.

Retail Price Change Update Processing

For each order detail line updated with the most recent retail price, the system:

• defaults the code defined in the Price Override for Retail Price Change Lines (H32) system control value to the Price override reason field.

• does not update order detail lines that already have a price override reason defined, unless the reason code matches the code defined in the Price Override for Retail Price Change Lines (H32) system control value. If the reason code does not match the code in the Price Override for Retail Price Change Lines system control value, the system assumes the price was already overridden for a reason.

• creates an order transaction history record for each order detail line whose price was updated to the new retail price:

 

Retail Price Overridden on Ln 999.

 

• creates an order transaction history record indicating the system defaulted the price override reason code defined in the Price Override for Retail Price Change Lines (H32) system control value to each order detail line whose price was updated to the new retail price:

 

User price override - Order line 999.

 

• submits the order detail lines to the ORDER ASYNC to process file updates, such as demand if the Update Demand for Order Maintenance Transactions (C72) system control value is set to Y. The system also creates a refund if the original price charged on the order reduced because of the retail price change. See ORDER ASYNC Updates for a list of files the system updates when the system updates order lines with the most recent retail price.

 

Example: A customer orders 2 pairs of socks and receives a promotional price for one pair.

Order lines Before Retail Price Change Update
Order line	Item	Price	Price override reason
1	SOCK54	12.00
2	SOCK54	8.00	P (promotional price)

The retail price updates to 15.00.

Order lines After Retail Price Change Update
Order line	Item	Price	Price override reason
1	SOCK54	15.00	R (retail price change)
2	SOCK54	8.00	P (promotional price)

The system only updates order line 1 with the retail price change because order line 2 already contains a price override reason. The system creates an order transaction history record for order line 1 indicating the price was updated with the retail price change and the retail price override reason code defaulted to the order line.

ORDER ASYNC Updates

This table shows the files the ORDER ASYNC updates when order detail lines are updated with the most recent retail price.

File	Updates
Customer Bill To (CSCBIL)	On order $
Customer Ship To Order History (CSHORH)	$ orders LTD
Customer Sold To Order History (CSTOOH)	$ orders LTD
Customer Sold To Entity (OECSEP)	$ orders LTD
Customer Ship To Entity (OECHEP)	$ orders LTD
Customer Sold To Item Class Entity (OEICEP)	$ orders LTD
Order Control Summary	$ orders
Item/SKU/Offer (FCISOF)	dollars ordered
Offer/Drop/Period (FCODRP)	dollars ordered
Offer/Drop/Period/Day (FCODPD)	dollars ordered
Order Type/User History (ORDUHS)	$ value
Order Type/User (OEOTYU)	$ value TD, $ value LTD
Order Billing History (OEBHST)	$ order total
Price Override Reason (OEPROR)	# overrides, total discount
SKU Price History (SKUPHT)	$ orders
SKU/Offer Page (INSKOP)	dollars ordered WTD, dollars ordered CTD
Source Period (FCSCPR)	dollars ordered
Source Code (MSSRC)	$ ordered

Note: Entity-level updates take place only if the Track Customer History at Entity Level (F89) system control value is set to Y.

Enter N or leave this field blank if you do not want the system to update order lines with the most recent retail price.

Note: When you change the value defined for this system control value, you should make sure that the Retail Price Change Update Process is not running since this can affect which order lines are updated with the most recent retail price.

Retail Price Change Upload Approval Percent (H31)

Purpose: Use this field to define the retail price threshold the system uses to automatically approve retail price change upload records.

MSR0057 CHANGE Change System Control Value 11/29/00 14:31:31 Description . : Retail Price Change Upload Approval % Percentage . . 5.00 Narrative . . . Application . : INV Applic group . R/I Sequence# . . . 99 F3=Exit F12=Cancel

Percentage field: Enter the percentage threshold you wish the system to use to automatically approve retail price change upload records. The percentage threshold is an absolute value; a positive or negative percentage can cause the retail price change upload record to automatically be approved.

The system:

• compares the retail price defined for the retail price change record to the most recent retail price that exists in CWDirect.

• calculates the percentage difference between the most recent retail price in CWDirect and the retail price defined for the retail price change record using this calculation:

 

(most recent retail price - retail price defined for retail price change record) / most recent retail price = the percentage difference between the two prices

 

• the system compares the percentage difference between the two prices to the percentage defined in the Retail Price Change Upload Approval Percentage system control value.

• the system approves the retail price change record if the percentage difference is less than or equal to the percentage defined in the system control value. The retail price change record is placed in an R (ready to process) status.

• the system does not approve the retail price change record if the percentage difference is greater than the percentage defined in the system control value. The retail price change record is placed in an H (held) status. You can approve and release the retail price change record from hold at the Work with Retail Price Change Screen.

Example: Here is an example of how the system determines whether a retail price change record should be placed on hold.

percentage in Retail Price Change Upload Approval % system control value	5.00
most recent retail price	200.00
retail price defined for retail price change upload record	180.00

 

(200.00 - 180.00) / 200.00 = 0.1 x 100 = 10.00

 

In this example, since 10.00 is greater than the 5.00 defined in the Retail Price Change Upload Approval % system control value, the system places the retail price change record in an H (held) status.

Enter 1% if you want almost all of your retail price change upload records to go on hold.

Leave this field blank if you want all retail price change upload records to automatically be approved if they pass validation.

Price Override for Retail Price Change Lines (H32)

Purpose: Use this screen to define the price override reason code the system defaults to open order lines updated with the most recent retail price.

MSR0051 CHANGE Change System Control Value 11/29/00 14:35:04 Description . : Price Override for Retail Price Change Lines Code . . . . . A B C E F G P W Narrative . . . Application . : INV Applic group . R/I Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the price override reason code the system defaults to open order lines updated with the most recent retail price.

The system updates order lines with the most recent retail price during Retail Price Change Update Processing if the Allow Retail Price Change Updates on Open Lines (H30) system control value is set to Y and you define a price override reason code in this system control value.

Price override reasons are defined in and validated against the Price Override Reason file; see Customer Service Establishing Price Override Reason Codes (WPOR).

Leave this field blank if you do not want the system to update order lines with the most recent retail price.

Inventory Transaction Code for ’Sync’ Processing (I85)

Purpose: Use this screen to indicate the inventory transaction code that signals a sync transaction when received through the generic inventory transaction upload.

MSR0051 CHANGE Change System Control Value 8/09/04 9:26:21 Description . : Inventory Transaction Code for 'Sync' Processing. Code . . . . . S * G L Q S Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the user-defined inventory transaction code that signals a sync transaction, rather than an adjustment, when passed as the transaction_code in the Inventory Transaction Upload XML Message (inCreateInvXaction). This screen displays all user-defined inventory transaction codes.

Note: Your entry here cannot be a system-defined transaction code.

About sync transactions: The Generic Inventory Transaction Upload processes a sync transaction by comparing the current on-hand quantity of the item/SKU in this location with the transaction_quantity passed in the Inventory Transaction Upload XML message. If the transaction_quantity passed in the message is greater than the current on-hand quantity, the resulting transaction adjusts the inventory upward by the difference; if the transaction_quantity is lower than the current on-hand quantity, the resulting transaction adjusts the inventory downward by the difference. If the transaction_quantity is the same as the current on-hand quantity, the system does not process an inventory transaction.

If the transaction_code passed in the Inventory Transaction Upload XML message is a user-defined code that does not match this system control value, the resulting transaction adjusts the on-hand inventory by the transaction_quantity.

Examples: The following table describes the results of a sync transaction and an adjustment transaction when the current on-hand quantity is 100:

transaction_ quantity =	Sync Transaction (inventory transaction code matches system control value)	Adjustment Transaction (other user-defined inventory transaction code)
25	25 is lower than the current on-hand quantity of 100. The sync transaction subtracts 75 from the current on-hand quantity in order to reset it to 25.	The transaction adds 25 to the current on-hand quantity, resulting in a new on-hand quantity of 125.
125	125 is higher than the current on-hand quantity of 100. The sync transaction adds 25 to the current on-hand quantity in order to reset it to 125.	The transaction adds 125 to the current on-hand quantity, resulting in a new on-hand quantity of 225.
100	100 is the current on-hand quantity. The system does not process an inventory transaction.	The transaction adds 100 to the current on-hand quantity, resulting in a new on-hand quantity of 200.
-50	You cannot process a sync transaction for a negative quantity; this creates an inventory transaction error.	The transaction subtracts 50 from the current on-hand quantity, resulting in a new on-hand quantity of 50.

Why use sync transactions? Processing sync transactions provides a way to keep inventory levels in sync with a remote system, such as CWStore. If you use the Point of Sale Integration with CWStore, you can receive periodic sync transactions from each store location that is represented by a warehouse in CWDirect so that you can review inventory levels in these store locations.

For more information: See:

• Generic Inventory Transaction Upload

• Work with Inventory Transaction Codes (WITC)

• Working with Inventory Transaction Errors (WITE)

Leave this field blank if you do not need to process sync transactions through the Generic Inventory Transaction Upload.

Default SKU Generator L/S Style (J04)

Purpose: Use this screen to define whether the SKU generator automatically creates a Long SKU style for each SKU created.

MSR0052 CHANGE Change System Control Value 2/16/05 11:04:13 Description . : Default SKU Generator Long SKU Style Yes/No . . . . N (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y inthis field if you want the SKU generator to automatically create a Long SKU style for each SKU created.

• If a long SKU style code is defined for the base item, the system creates a long SKU style code for each SKU using the base long SKU style code + SKU code.

• If a long SKU style code is not defined for the base item, the system creates a long SKU style code for each SKU using the item code + SKU code.

Example:

Item	Base L/S Style	SKU code	SKU L/S Style
AB101	LSAB101	RED WMNS SMLL	LSAB101REDWMNSSMLL
BC202	N/A	RED WMNS SMLL	BC202REDWMNSSMLL

Note: The Long SKU style field is 20 positions. If the generated long SKU style code is greater than 20 positions, the system will truncate the value to 20 positions.

This system control value only creates a long SKU style code for a SKU when you are using the SKU Generator (ESKG) menu option; this system control value does not default any value to the Long SKU style field when you are using the Work with Items (MITM) menu option.

Require unique long SKU style? If the Require L/S Style (I94) system control value is set to Y, the system will require a unique long SKU style code for each SKU.

Long SKU style defaults: The table below explains how the Long SKU style field is updated, based on system control value settings and whether a long SKU style code exists for the base item.

SCV J04	SCV I94	Item L/S style	Results
N	N	blank	The Long SKU style field is not populated with a default value for the SKUs created. The Long SKU style field is optional and the system does not require a unique value.
N	N	populated	The item long SKU style code defaults to the Long SKU style field for each SKU created. The Long SKU style field is optional and the system does not require a unique value.
N	Y	blank	The Long SKU style field is not populated with a default value for the SKUs created. The Long SKU style field is required and must be populated with a unique value.
N	Y	populated	The Long SKU style field is not populated with a default value for the SKUs created. The Long SKU style field is required and must be populated with a unique value.
Y	N	blank	The item code + SKU code defaults to the Long SKU style field for each SKU created. The Long SKU style field is optional and the system does not require a unique value.
Y	N	populated	The item long SKU style code + SKU code defaults to the Long SKU sty.le field for each SKU created. The Long SKU style field is optional and the system does not require a unique value.
Y	Y	blank	The item code + SKU code defaults to the Long SKU style field for each SKU created. The Long SKU style field is required and must be populated with a unique value.
Y	Y	populated	The item long SKU style code + SKU code defaults to the Long SKU sty.le field for each SKU created. The Long SKU style field is required and must be populated with a unique value.

Enter N or leave this field blank if you do not want the SKU generator to automatically create a Long SKU style for each SKU, based on the SKU code.

For more information: See Using the SKU Generator (ESKG) for more information on the SKU Generator.

Default Active Offers (J07)

Purpose: Use this screen to define whether the system defaults the most recent active offers for the specified item to the selection screen in Update SKU Offers (MUSO) and Update SKU Offer Prices (MUSK).

MSR0052 CHANGE Change System Control Value 2/22/05 8:35:07 Description . : Default Active Offers Yes/No . . . . N (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to default the most recent active offers for the specified item to the following screens:

• Update Item or SKU Offer(s) Screen in the Updating Item/SKU Offers (MUSO) menu option.

• Update SKU/Offer Screen in the Updating SKU Offer Prices (MUSK) menu option.

What is an active offer? Active offers are offers whose date range includes today’s date. The most recent active offers are those offers whose date range includes today’s date and whose Start date is closest to today’s date.

• If the offer’s Start date is later than today’s date, the offer is considered a future offer.

• If the offer’s End date is earlier than today’s date, the offer is considered an inactive, or expired, offer.

 

Example: The following offers are assigned to an item. Today’s date is 2/22/05.

Offer	Start Date	End Date	Results
O01	1/01/04	12/31/04	This offer has expired. The system will not default this offer to the selection screen in Update SKU Offers (MUSO) and Update SKU Offer Prices (MUSK).
O02	2/01/04	12/31/05	This offer is active. The system will default this offer to the selection screen in Update SKU Offers (MUSO) and Update SKU Offer Prices (MUSK). This offer is the third most recent active offer, based on the offer’s Start date.
O03	2/01/05	12/31/05	This offer is active. The system will default this offer to the selection screen in Update SKU Offers (MUSO) and Update SKU Offer Prices (MUSK). This offer is the second most recent active offer, based on the offer’s Start date.
O04	2/22/05	12/31/09	This offer is active. The system will default this offer to the selection screen in Update SKU Offers (MUSO) and Update SKU Offer Prices (MUSK). This offer is the most recent active offer because the Start date is closest to today’s date.
O05	1/01/06	12/31/06	This offer is a future offer. The system will not default this offer to the selection screen in Update SKU Offers (MUSO) and Update SKU Offer Prices (MUSK).

Updating Item/SKU Offers (MUSO) processing: If the Default Active Offers (J07) system control value is set to Y and you do not manually enter an offer in the Offer fields, the system defaults the 20 most recent active offers to the Offer fields for the entered item. The offers default to the Offer fields in descending Start date sequence.

• If you enter an item without a SKU code, the system defaults the 20 most recent active offers defined for the item.

• If you enter an item and SKU code, the system defaults the 20 most recent active offers defined for the SKU. The system will not default any item offers, even if no SKU offers exist.

Note:

• If the item is not assigned to 20 active offers, the system defaults the available active offers assigned to the item. For example, if the item is assigned to 25 offers, but only 8 offers are active, the system defaults the 8 active offers.

• If the item is assigned to more than 20 active offers, the system evaluates the offer’s Start date to determine the 20 most recent active offers to default.

• If active offers do not exist for the item, the Offer fields remain blank and you must manually enter offers in the Offer fields.

• If you update the Item and/or SKU field, the system will not update the defaulted offers.

• You can manually change a defaulted offer to another offer, even if the offer is a future offer or expired offer.

See Updating Item/SKU Offers (MUSO) for more information on updating item/SKU offers.

Updating SKU Offer Prices (MUSK) processing: If the Default Active Offers (J07) system control value is set to Y and you do not manually enter an offer in the Offer fields, the system defaults the 10 most recent active offers to the Offer field for the entered SKUed item. The offers default to the Offer fields in descending Start date sequence.

Note: The system does not default any offers until you enter a SKUed item, effective date, quantity, and price, and press Enter.

You must enter a SKUed item on the Update SKU/Offer Screen; however, you cannot enter a SKU code. Because of this, the system always defaults the 10 most recent item offers to the Offer fields.

• If the item is not assigned to 10 active item offers, the system defaults the available active offers assigned to the item. For example, if the item is assigned to 25 item offers, but only 8 item offers are active, the system defaults the 8 active item offers.

• If the item is assigned to more than 20 active item offers, the system evaluates the offer’s Start date to determine the 20 most recent active item offers to default.

• If active offers do not exist for the item, the Offer fields remain blank and you must manually enter offers in the Offer fields.

• If you update the Item and/or SKU field, the system will not update the defaulted offers.

• You can manually change a defaulted offer to another offer, even if the offer is a future offer or expired offer.

See Updating SKU Offer Prices (MUSK) for more information on updating SKU offer prices.

Enter N or leave this field blank if you do not want the system to default the most recent active offers for the specified item to the selection screen in Update SKU Offers (MUSO) and Update SKU Offer Prices (MUSK).

Item Creation Values (J08)

Purpose: Use this screen to define which screens automatically display when you are Performing Initial Item Entry (MITM).

MSR1469 ENTER Edit Item/SKU Creation Values 2/16/05 9:08:22 KAB Co Auto Advance to SKU Create . . . . . . . . . . . . N (Y/N) Auto Advance to Vendor Item Create . . . . . . . . N (Y/N) Auto Advance to Item Keywords. . . . . . . . . . . N (Y/N) Auto Advance to SKU Generator . . . . . . . . . . N (Y/N) Auto Advance to Item Offer . . . . . . . . . . . . Y (Y/N) F3=Exit F12=Cancel

Overview: The create item screen flow varies, depending on whether you are creating a non-SKU’ed item or SKU’ed item.

Additionally, the Item Creation Values (J08) umbrella system control value contains system control values that control which screens automatically display when you are creating an item.

Creating non-SKUed items screen flow: Enter N at the SKUs field on the Create Item Screen to create a non-SKUed item. The system automatically advances you through the following screens to create a non-SKUed item.

1. Create Item Screen

2. Create Item (Base Information) Screen

3. Create Vendor Item Screen (only if the Auto Advance to Vendor Item Create (E78) system control value is set to Y)

4. First Work with Keywords for Item Screen (only if the Create Keywords at Item Entry (F78) system control value is set to Y)

5. Create Item Offer Screen (only if the Auto Advance to Item Offer (J05) system control value is set to Y)

Once you have completed creating the item, the system returns you to the Create Item Screen where you can create another item.

Creating SKUed items screen flow: Enter Y at the SKUs field on the Create Item Screen to create a SKUed item. The system automatically advances you through the following screens to create a SKUed item.

1. Create Item Screen

2. First Work with Keywords for Item Screen (only if the Create Keywords at Item Entry (F78) system control value is set to Y)

3. Create Item Offer Screen (only if the Auto Advance to Item Offer (J05) system control value is set to Y)

4. Depending on whether you are using the SKU Generator:

• Create SKU 1 of 2 (With Overrides) Screen (only if the Auto Advance to SKU Create (B34) system control value is set to Y and the Auto Advance to SKU Generator (J06) system control value is set to N)

• SKU Generator Screen (Entering SKU Information) (only if the Auto Advance to SKU Generator (J06) system control value is set to Y)

5. Depending on whether you are using the SKU Generator:

• Create SKU 2 of 2 (With Overrides) Screen (only if the Auto Advance to SKU Create (B34) system control value is set to Y and the Auto Advance to SKU Generator (J06) system control value is set to N)

• Work with SKU Generator Screen (only if the Auto Advance to SKU Generator (J06) system control value is set to Y)

6. Depending on whether you are using the SKU Generator:

• Create Vendor Item Screen (only if the Auto Advance to SKU Create (B34) system control value is set to Y, the Auto Advance to Vendor Item Create (E78) system control value is set to Yselected and the Auto Advance to SKU Generator (J06) system control value is set to N)

• Enter SKU Base Information Pop-Up Window (only if the Auto Advance to SKU Generator (J06) system control value is set to Y)

Once you have completed creating the item and SKU, the system returns you to the:

• Create SKU 1 of 2 (With Overrides) Screen if you are not using the SKU Generator, where you can create another SKU.

• Create Item Screen if you are using the SKU Generator, where you can create another item.

 

Auto Advance to SKU Create (B34)

Defines whether the system automatically advances to the Create SKU 1 of 2 (With Overrides) Screen when you are Performing Initial Item Entry (MITM) for an item that has SKUs.

Yes/No field: Enter Y in this field if you want the system to automatically advance to the Create SKU 1 of 2 (With Overrides) Screen when you create an item that has SKUs using the Work with Items (MITM) menu option.

See Creating Items Screen Flow for more information on which screens automatically display when you create an item/SKU.

Note: If the Auto Advance to SKU Generator (J06) system control value is also set to Y, the system advances you to the SKU Generator Screen (Entering SKU Information) instead of the Create SKU 1 of 2 (With Overrides) Screen.

If you enter N, the Create SKU with Overrides screen won't display, but you can access it from the Work with SKUs Screen. You can also create SKUs automatically Using the SKU Generator (ESKG).

Auto Advance to Vendor Item Create (E78)

Defines whether the system automatically advances to the Create Vendor Item Screen when you are Performing Initial Item Entry (MITM).

Yes/no field: Enter Y in this field if you want the system to automatically advance to the Create Vendor Item Screen when you create an item or SKU in Work with Item/SKUs. See Merchandising Performing Initial Item Entry (MITM).

When you create a non-SKUed item, the system advances to the Create Vendor Item Screen when you press Enter on the Create Item (Base Information) screen.

When you create a SKUed item, the system advances to the Create Vendor Item Screen when you press Enter on the Create SKU (with Overrides) screen.

Enter N or leave this field blank if you do not want the system to automatically advance to the Create Vendor Item Screen when you create an item or SKU in Work with Item/SKUs.

Create Keywords at Item Entry (F78)

Defines whether the system automatically advances to the First Work with Keywords for Item Screen when you are Performing Initial Item Entry (MITM).

Yes/No field: Enter Y in this field if you want the system to advance you to the First Work with Keywords for Item Screen when you create an item.

The First Work with Keywords for Item Screen allows you to create keywords for the item you are creating.

For example, if you sell books and the item number is a code, AN8975H, and the description of the item is the title of the book, “The Outer Ring,” you may want to use the author's name as a keyword, Newbold, Alex.

You could further define the item by creating a keyword for the type of book it is, for example, “science fiction.” This way you can scan for items (books) that have been written by the author or scan for items (books) by book category.

Related system control value: You advance to the Work with Keywords for Item screen in ADD mode or CHANGE mode based on the setting of the Auto-Generate Item Keywords from Description (F79) system control value.

If the Auto-Generate Item Keywords from Description (F79) system control value is also set to Y, the system automatically generates item keywords for the item you are creating using the words defined in the item's description. The system advances you to the Work with Keywords for Item screen in CHANGE mode where you can review the auto-generated keywords, delete keywords, or create more keywords.

If the Auto-Generate Item Keywords from Description (F79) system control value is set to N or blank, the system advances you to the Work with Item Keywords for Item screen in ADD mode where you can create keywords for the item.

Once you finish working with the item keywords, the system returns you to the next screen in the existing sequence for item entry, based on the values defined for the Auto Advance to SKU Create (B34) and Auto Advance to Vendor Item Create (E78) system control values.

See Merchandising Working with Item Keywords for more information on item keywords.

Enter N or leave this field blank if you do not want the system to advance to the Work with Keywords for Item screen when you create an item.

Auto Advance to SKU Generator (J06)

Defines whether the system automatically advances to the SKU Generator Screen (Entering SKU Information) when you are Performing Initial Item Entry (MITM) for an item that has SKUs.

Yes/No field: Enter Y in this field if you want the system to automatically advance to the SKU Generator Screen (Entering SKU Information) when you create an item that has SKUs using the Work with Items (MITM) menu option. The SKU Generator screen allows you to create multiple SKUs for an item at one time.

See Creating Items Screen Flow for more information on which screens automatically display when you create an item/SKU.

Enter N or leave this field blank if you do not want the system to automatically advance to the SKU Generator Screen (Entering SKU Information) when you create an item that has SKUs.

You can enter Y in the Auto Advance to SKU Create (B34) system control value if you want the system to automatically advance to the Create SKU 1 of 2 (With Overrides) Screen when you create an item that has SKUs. The Create SKU 1 of 2 (With Overrides) screen allows you to create a single SKU for an item.

However, if the Auto Advance to SKU Generator (J06) system control value and Auto Advance to SKU Create (B34) system control value are both set to N, the system does not automatically advance you to any SKU screen when you initially create an item.

• You can advance to the Create SKU 1 of 2 (With Overrides) Screen from the Work with SKUs Screen.

• You can advance to the SKU Generator Screen (Entering SKU Information) from the Generate SKUs (ESKG) menu option; see Using the SKU Generator (ESKG).

Auto Advance to Item Offer (J05)

Defines whether the system automatically advances to the Create Item Offer Screen when you are Performing Initial Item Entry (MITM).

Yes/No field: Enter Y in this field if you want the system to automatically advance to the Create Item Offer Screen when you create an item.

See Creating Items Screen Flow for more information on which screens automatically display when you create an item/SKU.

Enter N or leave this field blank if you do not want the system to automatically advance to the Create Item Offer Screen when you create an item. You can advance to the Create Item Offer screen by pressing F6 at the Work with Item Offers Screen.

Track Cost Changes (J69)

Purpose: Use this screen to indicate whether to track changes to an item or SKU’s cost in the Cost Change Audit file.

MSR0052 CHANGE Change System Control Value 5/22/07 17:04:21 Description . : Track Cost Changes Yes/No . . . . Y (Y,N) Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 999 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to write a record to the Cost Change Audit file when you change an item or SKU’s cost, or change the cost for a FIFO cost layer if you use FIFO costing.

You can review cost change history in item maintenance. See Reviewing Item/SKU Cost History for more information.

Enter N or leave this field blank if you do not want the system to record cost changes in the Cost Change Audit file.