Setting Up Fulfillment Values

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

• Fulfillment and replenishment processing

• Cart/Bin picking

• Cubing

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 Fulfillment System Control Values

This table describes briefly each system control value for the Fulfillment 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
Include Print Quantity in Available Calculations (A65)	Indicates whether the system includes print quantity in primary replenishment calculations.	Yes/No:
Replenish from Location Type (A66)	Defines the types of locations for primary location replenishment.	Code:
Perform Cubing? (B36)	Indicates if you want to perform Cubing. See Maximum Weight of a Carton (B46), Maximum Cube Value for a Carton (B45).	Yes/No:
Pick Processing Days (B37)	Number of days from the time a pick slip is generated that the order is shipped.	Quantity:
Edit Cart/Bin Values Screen(B38)	Indicates if you are using the Cart/Bin Picking feature. See Cube of Bin (B44), Cube of Cart (B42), Maximum Number of Single Line Picks (B39), Maximum Number of Multi Line Picks (B40), Maximum Number of Zones (B41).	Yes/No:
Sort Picks by Pick Sequence (E89)	Indicates that the system considers the pick sequence number when sorting picks in a batch.	Yes/No:
Maximum Number of Single Line Picks (B39)	Defines the maximum number of single line pick slips in a batch.	Quantity:
Maximum Number of Multi Line Picks (B40)	Defines the maximum number of multi-line pick slips in a batch. See Cube of Bin (B44).	Quantity:
Maximum Number of Zones (B41)	Defines the maximum number of zones allowed on a multi-line pick slip.	Quantity:
Cube of Cart (B42)	Defines the cubic volume of a cart.	Quantity:
Cube of Bin (B44)	Defines the cubic value of the smallest bin in a cart.	Quantity:
Minimum Number of Picks in a Cart (B47)	Defines the minimum number of pick slips in a cart.	Quantity:
Maximum Cube Value for a Carton (B45)	Defines the maximum cubic value of a carton.	Quantity:
Maximum Weight of a Carton (B46)	Defines the maximum weight a carton can hold.	Weight:
Consolidated Invoice (B49)	Controls whether to consolidate invoices for shipments made for the same order on the same day.	Yes/No:
Edit Warehouse/Reservation Values Screen(B50):	Defines values for immediate and batch reservation.
FIFO Flag (A03)	Defines whether the system holds inventory for orders on a first-in/first-out basis. See Immediate Reservation (A64).	Yes/No:
Default Warehouse (A04)	Defines the warehouse code that defaults on many screens.	Number:
Immediate Reservation (A64)	Defines whether the system reserves inventory for orders as they are entered in order entry.	Yes/No:
Ship Complete from 1 Warehouse (B16)	Indicates whether the system reserves inventory only from the primary warehouse.	Yes/No:
Split Line Over Multiple Warehouses (B19)	Indicates whether the system fulfills orders from more than one warehouse.	Yes/No:
Evaluate Warehouses in Warehouse List Only (J47)	Defines whether reservation and backorder processing evaluates warehouses in the selected warehouse list only.	Yes/No:
Reservation Lead Days (B27)	Defines the number of days after which the system identifies an order as a “future order.”	Number:
Reevaluate Reservation Logic at Final Accept (M01)	Defines whether the system reevaluates item reservation on a ship to order during the final order accept, and if possible, re-reserve items so that the items ship from a single warehouse in the warehouse list.	Yes/No:
Pick/Pack Verification Entry Format (B59)	Defines the default format for the Pick/Pack Verification screen.	Code:
P/P Scan by Unit Default (B60)	Indicates if you use a scanner during Pick/Pack Verification.	Yes/No:
Default Restock Location (B62)	Defines the default location when performing warehouse replenishment.	Code:
Use PC Manifesting (B80)	Indicates if you are using a PC manifesting system. See PC Manifest Tool (B81), Data Queue Name (B77), Data Queue Library (B78), Void Request Wait Time (B79).	Yes/No:
Data Queue Name (B77)	Defines the data queue that allows communication between the iSeries and the PC.	Code:
Data Queue Library (B78)	Defines the library for the data queue.	Code:
Void Request Wait Time (B79)	Defines the number of seconds the iSeries waits in reply to request that a pick slip has been voided.	Number:
PC Manifest Tool (B81)	Defines the code for the controlling PC in the warehouse.	Code:
Send Void Requests (E45)	Determine whether CWDirect should try to communicate with the PC manifest station when voiding a pick slip.	Yes/No:
Interactive Processing (E56)	Determine whether upload records are processed as soon as they are received from the PC manifest station or in a batch mode.	Code:
Wait Time if Automatic (E57)	Defines the number of seconds the PC Interactive Manifest dataqueue should wait before searching for new records to process.	Number:
Let Down Replenishment (C36)	Defines if you are using Let Down Replenishment.	Code:
Pick Printing Program (C37)	Defines the name of the program that prints pick slips.	System Name:
Batch Pull Sheet Printing Program (C38)	Define the name of the program that prints batch pull sheets.	System Name:
Cart/Bin Batch Pull Sheet Printing Program (C39)	Defines the name of the program that prints cart/bin batch pull sheets.	System Name:
Perform Best Way Shipping (C47)	Controls whether to the Best Way Shipping feature at pick slip generation, in which the system selects the least expensive shipping method, using the shipping rate tables.	Yes/No:
Check Location Quantities During Pick Generation (C54)	Indicates if the system allocates inventory from specific warehouse locations or exclusively from the primary location.	Yes/No:
Print Batch Pull Sheet Item Summary (C59)	Determines if the Batch Pull Sheet Item Summary prints when pick slips are printed.	Yes/No:
Pick Sort Program Name (C65)	Defines the name of the program that sorts the pick slips.	System Name:
Declared Value Type (C66)	Indicates whether the system evaluates the declared value of shipments at cost or retail.	Code:
Spiegel Vendor Number (C75)	Defines the Spiegel Vendor Number that is stored in the Spiegel invoice.	Number:
Print Amounts on Drop Ship Picks (C81)	Indicates whether the price, the extended price, merchandise total, freight, handling, and additional charges print on drop ship pick slips.	Yes/No:
Allow Only Single Line on Drop Ship Picks (C82)	Indicates whether drop ship picks are limited to printing one detail line (item) per pick slip.	Yes/No:
Spiegel Batch Size (D05)	Defines the maximum number of CWDirect invoices per Spiegel invoice batch.	Number:
Spiegel Account Number (D06)	Identifies the Customer Bill To account number used when creating open A/R records for Spiegel.	Number:
Prorate Freight Charges (D39)	Indicates whether you charge a proportional amount of freight when you bill partial shipments, or charge all freight on the first shipment.	Yes/No:
Number of Pick Control Labels (D47)	Defines the number of label records to download to the PC manifest station for tracking.	Number:
Use Pick Label Tracking in Manifest Interface? (D48)	Indicates if you are tracking multiple labels for pick slips through PC manifesting.	Yes/No:
Sort Pick Slips by Gift Flag (D53)	Indicates whether you are sorting gift pick slips separately from non-gift pick slips.	Yes/No:
Sort Picks by Foreign/Domestic Flag (D54)	Indicates whether you are sorting foreign pick slips separately from domestic pick slips.	Yes/No:
Generate Coordinate Groups at Pick Gen for Ship Complete Orders (E10)	Defines whether the system assigns coordinate groups to items on a ship complete order during pick slip generation.	Yes/No:
Use Coordinate Groups Within Sets Only (E11)	Defines if the system checks whether items that are assigned the same coordinate group code are part of a set before determining if a pick slip can be generated.	Yes/No:
Invoice Consolidation Method (E29)	Defines whether invoices are consolidated for all ship to customers on the order or only within the same ship to customer.	Code:
Break Single Line Picks by Zone (E33)	Defines whether single-line picks break into separate cart/bin pullsheets based on location zone.	Yes/No:
Print One Drop Ship Invoice per Ship Alone Item (E38)	Defines whether the system prints out a separate drop ship invoice for each ship alone item on an order.	Yes/No:
Replenishment Report Program Name (E47)	Defines the name of the program that prints the Replenishment Detail report.	System Name:
Create Manifest Download Extended Records (E77)	Defines whether the system creates item weight records in the Manifest Download Extended file when you use PC manifesting to confirm shipments.	Yes/No:
Pick Units to Initiate Extra Labels (E91)	Defines whether pick generation prints two extra pick control labels for a pick slip.	Number:
Drop Ship Pick Print Program (E92)	Defines the name of the print program the system uses when drop ship pick slips are printed.	System Name:
Add Printed Drop Ship Lines as Backordered on Pick (E93)	Defines whether the system displays drop ship items as backordered on the regular pick slip even after a drop ship pick slip or purchase order has been generated for the drop ship item.	Yes/No:
Use Async Start Date for Billing Transactions (E95)	Defines whether the system use the Async start date as the billing date for billing transactions.	Yes/No:
Withhold Picks due to Item Allocation Error (F04)	Defines whether the system prints a pick slip for an order when items on the order create stock allocation errors.	Yes/No:
Print Drop Ship Invoice at time of Purchase Order Receiving (F10)	Defines whether the system prints a drop ship invoice when the drop ship purchase order is received.	Yes/No:
Replenishment Label Program Name (F20)	Defines the print program used to generate Replenishment Transfer Labels during Primary Location Replenishment.	System Name:
Pick Label Print Program (F28)	Defines the print program name the system uses to format pick control labels printed through Print Additional Pick Labels.	System Name:
Price Ticket Print Program (F46)	Defines the print program name the system uses to print price tickets in hanging and label format.	System Name:
Batch Item Pull Label Printing Program (F63)	Defines the print program name the system uses to print batch item pull labels during pick slip generation.	System Name:
Include Bulk Locations in Primary Primary Availability (F87)	Defines whether the system includes the quantity in bulk locations in the available pick quantity for the primary primary location.	Yes/No:
Include Secondary Locations in Primary Primary Availability (F88)	Defines whether the system includes the quantity in secondary locations in the available pick quantity for the primary primary location.	Yes/No:
Hold Invoices for Multi-Recipient Orders (G07)	Defines whether the system holds invoices for a multi-recipient order until all of the pick slips for the order have been confirmed.	Yes/No:
Cancel Reason Code for Retail Fulfillment Confirmation (G11)	Defines the cancel reason code to use when cancelling order lines you have fulfilled through shipment from a retail store.	Number:
Load Location into Pick Sequence (G34)	Defines whether to load the location codes for a pick slip to the Picking sequence array field in the Pick Sort GH file, for use in sorting pick slips.	Yes/No:
Consolidated Replenishment Report Program Name (G49)	Allows you to print replenishment reports for multiple replenishment requests generated on the same day.	System Name:
Pickable Setting for Analyzing Replenishment Locations (G63)	Defines whether to consider pickable, nonpickable, or either type of location in your 'From' warehouse when determining whether you can fulfill a warehouse replenishment request.	Code:
Type of Location to Search First in Warehouse Replenishment (G64)	Defines the type of location to search first when selecting the location in your 'From' warehouse from which to fulfill a warehouse replenishment request.	Code:
Type of Location to Search Second in Warehouse Replenishment (G65)	Defines the type of location to search second when selecting the location in your 'From' warehouse from which to fulfill a warehouse replenishment request.	Code:
Type of Location to Search Third in Warehouse Replenishment (G66)	Defines the type of location to search third when selecting the location in your 'From' warehouse from which to fulfill a warehouse replenishment request.	Code:
Use Carousel Interface (G55)	Defines whether the system sends pick control information to the Carousel system during pick slip generation.	Yes/No:
Drop Ship Integration Values Screen (H20)	Indicates whether you are using CWCollaborate or Locate Supplier Direct Fulfillment integration, and defines required values.
Drop Ship Lead Days (H36)	The number of days added to the date passed to CWCollaborate or Locate to calculate the Expected ship date stored in CWDirect for a drop ship purchase order line.	Number:
Communication Protocol (H37)	The file transfer protocol you use to transmit information to CWCollaborate.	MQ/FTP:
Retailer ID (H15)	Identifies the retailer within the CWCollaborate database and serves as the primary key in most of the files.	Code:
FTP ID - Vendor Download (H16)	Identifies the FTP script used to send vendor information to CWCollaborate.	Code:
FTP ID - PO Download - New (H17)	Identifies the FTP script used to send new purchase orders to CWCollaborate.	Code:
FTP ID - PO Download Changes (H35)	Identifies the FTP script used to send changed PO address information to CWCollaborate.	Code:
FTP ID - PO Cost Changes (H78)	Identifies the FTP script used to send PO cost changes to CWCollaborate.	Code:
FTP ID - Returns Download - New (H56)	Identifies the FTP script used to receive purchase order updates from CWCollaborate.	Code:
FTP ID - PO Cost Changes (H78)	Identifies the FTP script used to send cancellation requests to CWCollaborate.	Code:
FTP ID - Returns Download - New (H56)	Identifies the FTP script used to send new return information to CWCollaborate.	Code:
FTP ID - Return Updates (H58)	Identifies the FTP script used to receive return information from CWCollaborate.	Code:
FTP ID - Deleted RAs (H57)	Identifies the FTP script used to send deleted RA information to CWCollaborate.	Code:
FTP ID - AP Invoice Upload (H77)	Identifies the FTP script used to receive A/P invoice information from CWCollaborate.	Code:
System Cd (K50)	Specifies the system code identifying your company in Locate for integration with the Supplier Direct Fulfillment module.	Code:
Default Loc (K51)	Specifies the location code identifying your default warehouse in Locate for integration with the Supplier Direct Fulfillment module.	Code:
Refund Freight Default for Inbound Returns (H59)	Identifies whether freight should be refunded when processing returns from an outside system.	Yes/No:
Refund Additional Charge Default for Inbound Returns (H60)	Identifies whether additional charges should be refunded when processing returns from an outside system.	Yes/No:
Refund Handling Default for Inbound Returns (H61)	Identifies whether handling should be refunded when processing returns from an outside system.	Yes/No:
Refund Duty Default for Inbound Returns (H62)	Identifies whether duty should be refunded when processing returns from an outside system.	Yes/No:
Default Return Reason Code for Inbound Returns (H63)	Defines the default return reason code used when processing returns from an outside system.	Code:
Default Additional Charge Code for Inbound Returns (H64)	Defines the additional charge code used when adding return postage to an order for a return received from CWCollaborate.	Code:
Default Return Disposition Code for Inbound Returns (H65)	Defines the return disposition code used when processing returns from an outside system.	Code:
Generate Invoice Number at Pick Gen (H80)	Defines whether to assign pending invoice numbers when you generate pick slips.	Yes/No:
Prefix of Identcode (I28)	Specifies the prefix to assign pick slip identcodes for shipments in Germany.	Number:
Use Alternate Zone Reservation Logic (I52)	Specifies whether you want to use standard or alternate zone reservation logic for items that you do not currently have in inventory.	Yes/No:
Order Control Summary Shipment Update Method (I55)	Defines how the system updates the # Orders shipped field in the Order Control Summary file.	Code:
Minimum Item Price Eligible for Retail Pick Ticket (I76)	Defines the unit selling price threshold for items eligible for retail fulfillment.	Dollar amount:
Generate Price Tickets During Pick Slip Generation (I77)	Indicates if the system generates price tickets during pick slip generation for retail store orders.	Code:
Use Inventory Sharing Backorder Evaluation (I80)	Indicates whether to reserve backorders across all sharing companies using the same hierarchy, or to reserve within the shared company (where you actually maintain the inventory) first.	Yes/No:
Confirm Reprint of Pick Tickets from WMS (J32)	Defines whether the system reprints and immediately bills a pick slip when a partial warehouse backorder is received from a warehouse management system.	Yes/No:
QuickPick Zone Identifier (J41)	Defines whether the system performs QuickPick Zone processing. The value you enter in this field represents the zone the system treats as the QuickPick zone during pick slip allocation and let down replenishment.	Code:
Replenish from Primary during Let Down Replenishment (J42)	Defines whether the system includes primary locations in the type of locations from which you can replenish stock when performing let down replenishment.	Yes/No:
Rounding for Casepacks from Bulk in Let Down Replenishment (J43)	Defines whether the system is required to move stock from bulk locations in case packs during let down replenishment, and whether to round up or round down to a case pack, based on the quantity required by let down replenishment and the Maximum quantity defined for the item/location.	Code:
Include HDL Warehouse Value on Order Detail (J54)	Defines whether the system automatically assigns an HDL to an order line, based on the warehouse list associated with the SCF of the order ship to.	Yes/No:
Use Wave Picking (J87)	Defines whether the system generates pick slips using wave picking functionality.	Yes/No:
Pick Wave Label Print Program (J88)	Defines the print program the system uses to print pick wave labels.	System name:
Consolidated Credit Invoice (K06)	Defines whether to consolidate credit invoices created on the same day.	Yes/No:
UPS Identifier and Account Number (K57)	Defines the customer identifier and UPS account number to use as the first eight positions of the UPS tracking number. The system prints this information on the pick slip if your unique pick print program supports it.	Code:
Deadline for Special Shipper Override (L43)	The date to use when determining whether to override the ship via on a pick slip based on a special shipper override in pick slip generation.	Date:

Include Print Quantity in Available Calculations (A65)

Purpose: Use this screen to define whether you want to include the print quantity in primary replenishment calculations.

MSR0052 CHANGE Change System Control Value 11/12/99 12:36:33 Description . : Include 'Printed Quantity' in 'Available' calculations? Yes/No . . . . Y (Y,N) Narrative . . . Application . : FUL Applic group . STK Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want to include print quantity in available calculations for primary location replenishment. The print quantity is the number of units on pick slips that have not been confirmed.

There are two calculations in which printed quantity is used if you set this value to Y:

1. To determine if a location requires replenishment. (A location requires replenishment if the available quantity is less than or equal to the minimum quantity in the Item/Location file.)

 

Available quantity = On-hand + pending quantity - print quantity.

 

2. To determine the amount of stock available to be pulled from a location.

 

Available stock = On-hand + (Batch Inventory Transfer negative pending quantity) - print quantity.

 

Setting this parameter depends on when you replenish locations. If you replenish locations before you pick product, but after you generate pick slips, you probably do not want to include the printed quantity; there may not be enough room to store the product in the location. If you replenish locations after you pick product, you may want to include the print quantity to ensure that you have filled the locations to their capacity.

For more information: See Warehousing Replenish Primary Locations Overview.

Replenish from Location Type (A66)

Purpose: Use this screen to define the types of locations from which you want to replenish stock when performing primary location replenishment.

If the Let Down Replenishment (C36) system control value is set to RPT/EXEC, the system replenishes locations automatically to the quantity required for the current pick slip run during Pick Slip Generation, using the location type defined in the Replenish From Location Type system control value.

MSR0051 CHANGE Change System Control Value 11/12/99 12:39:37 Description . : Replenish from 'Location Type'. Code . . . . . BULK BULK SECONDARY SEC/BULK Narrative . . . Application . : FUL Applic group . STK Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the code for the location type. Valid codes are:

• BULK: If you enter BULK, the system attempts to replenish from bulk locations only.

• SECONDARY: If you enter SECONDARY, the system attempts to replenish from secondary locations only.

• SEC/BULK: If you enter SEC/BULK, the system attempts to replenish from both secondary and bulk locations. Locations are selected sequentially by location code.

Leave this field blank if you are not performing primary location replenishment.

For more information: See Warehousing Replenish Primary Locations Overview.

Perform Cubing? (B36)

Purpose: Use this screen to indicate whether you want to perform cubing during Pick Slip Generation.

MSR0052 CHANGE Change System Control Value 11/12/99 11:23:39 Description . : Use Cubing? Yes/No . . . . Y (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to perform cubing during Pick Slip Generation.

Cubing is the process whereby the system checks the cubing value of the items to be included on a pick slip, the cubic value of a carton, and determines how many items can be shipped in a single carton. If more than one carton is needed, cubing reevaluates each carton in relation to the overall cubic value of the items on the pick slip to ensure that the system uses the minimum amount of cartons and packs them in the most efficient way, maximizing the carton space to include the most items as possible.

If you enter N, the system does not consider the dimension of the item when determining the number of pick slips to be created.

For more information: See Fulfillment Introducing Pick Slip Generation.

Pick Processing Days (B37)

Purpose: Use this screen to define the number of days from the time a pick slip is generated that it takes the order to be shipped out of the warehouse.

MSR0055 CHANGE Change System Control Value 11/12/99 11:27:53 Description . : Pick Processing Days Quantity . . . 5 Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Quantity field: Enter the number of days (up to 7 positions, numeric) it takes your company, on average, to pick, pack, and ship an order. This is your internal lead time. This number is used to determine when a pick slip should be generated.

How the system determines when to produce the pick slip:

During Pick Slip Generation, the system checks the arrival date for each line on an order and uses this calculation to determine when to print the pick slip:

 

Arrival Date - (Pick Processing Days + Transfer Lead Days + Lead Days) Today's Date.

 

The system generates pick slips if this system-calculated date is less than or equal to today's date; otherwise, the system holds the printing of the pick slips until the date is within the allotted time frame. The system considers this information:

Pick Processing Days

Transfer Lead Days: This value is defined in the Warehouse Drop Point record. It represents the number of days it takes to ship the order from the drop point. This may be a centralized warehouse (in which you must ship from warehouse to another) or a drop point (which is a place where another shipper picks up the package and delivers it to its destination to save shipping charges).

Lead Days: This value represents the number of days it takes a shipper to deliver the order to its destination. The SCF represents the first 3 positions of the postal code to which you are shipping.

For more information: See Fulfillment Introducing Pick Slip Generation.

Edit Cart/Bin Values Screen(B38)

Purpose: Use this screen to define if you use the cart/bin picking feature to sort your pick slips.

If you use Cart/Bin Picking, you must complete all fields on this screen, except Minimum Number of Picks in a Cart (B47), which is an optional value.

MSR0475 ENTER Edit Cart/Bin Values 12/03/97 14:31:25 The KAL Mail Order Company Use Cart/Bin Picking . . . . (Y/N) Sort Picks by Pick Sequence (Y/N) Cart Description Setup Cube of Bin . . . . . . . . . . . . Cube of Cart . . . . . . . . . Minimum Number of Picks in a Cart . Single Line Orders Setup Maximum Number of Single Line Picks Multi Line Orders Setup Maximum Number of Multi Line Picks . Maximum Number of Zones . . . . . . . F3=Exit F12=Cancel

Use Cart/Bin Picking? (B38)

Enter Y in this field to indicate that you wish to use the cart bin picking feature to generate pick slips and pull sheets during the Pick Slip Generation Batch function. Cart/Bin Picking is a way to maximize the picking of inventory by generating a batch pick slip list for a single picker to handle in a single run.

Wave picking: If you enter Y in both the Use Cart/Bin Picking? (B38) system control value and the Use Wave Picking (J87) system control value, the system generates pick slips using cart/bin processing and not wave picking processing.

Enter N or leave this field blank if you do not wish to use cart/bin picking. Pull sheets and pick slips are still generated, but items are not grouped into batches. If you enter N, you do not need to complete the other fields.

Note: If this system control value is set to N, the system does not write order transaction history messages at pick slip generation. See Display Order History Screen for more information.

Sort Picks by Pick Sequence (E89)

Enter Y in this field to sort picks in a batch by the pick sequence number defined in the Pick sequence number field in Work with Locations (fast path = WLOC).

The system sorts by zone, then pick sequence number and considers this when breaking a batch:

• single and multiple line picks

• gift picks

• foreign and domestic picks

• batch capacity (number of picks in a batch or cube)

The system sorts picks in order of picking sequence within via priority but mixes across pick sequences.

Example: Two separate picks contain these items:

Pick Slip A:

Item	Zone	Pick Sequence #
item A	zone C	0000009
item B	zone C	0000004
item C	zone C	0000005
item D	zone B	0000004

Pick Slip B:

Item	Zone	Pick Sequence #
item A	zone C	0000009
item Q	zone C	0000008
item C	zone C	0000005

In this situation, the system sorts the items in this order:

Pick Slip B:

zone C	0000005
zone C	0000008
zone C	0000009

Pick Slip A:

zone B	0000004
zone C	0000004
zone C	0000005
zone C	0000009

You can review batches sorted by pick sequence number in the Pick Sort GH file (FLPSGH). The system loads the first 25 picking sequences on the pick slip only.

If the Load Location into Pick Sequence (G34) field is also set to Y, then the location code(s) for each item on the pick slip is loaded into the Picking sequence array field of the Pick Sort GH file, rather than the pick sequence number.

Enter N or leave this field blank if you do not want the system to consider pick sequence number when sorting picks in a batch. See Maximum Number of Zones (B41).

Cart Description Setup:

If you entered Y in this field to use cart/bin picking, complete these fields, which describe the cart size you are using.

Cube of Bin (B44)

Enter the cubic volume of the smallest bin within a cart. This value should correspond in the type of measurement to the value defined for Cube of Cart (B42) field. This 7-position, numeric field applies to multi-line pick slips.

Cube of Cart (B42)

Enter the total cubic volume of the cart. This value should correspond in the type of measurement to the value defined for Cube of Bin (B44) field. This is a 7 position, numeric field.

All cubing dimensions for evaluating cubic value of items, carts, and batches should be rendered in the same unit of measure throughout the system, whether you use inches, feet, or a point rating.

Minimum Number of Picks in a Cart (B47)

Enter the minimum number of picks that can be contained in a cart.

This value ensures that the number of picks in a cart/batch matches or exceeds the minimum size you determine. If the number of picks to be batched is less than the quantity you enter here, the picks are added to the current batch instead of creating a new batch that would be less than the minimum size.

For example, if you define the minimum number of picks as 20, each batch must contain at least 20 picks slips. If the next batch to be created contains only 15 picks, the 15 pick slips are added to the batch, rather than creating a new batch of 15 pick slips, because it is less than the required minimum of 20.

Single Line Orders Setup:

Maximum Number of Single Line Picks (B39)

Enter the maximum number of single line pick slips to include in a single batch. This value sets a break point for a batch and is usually dependent upon the number of bins in a cart. This is a 7-position, numeric field.

The system considers these factors in determining when to create a new batch of pick slips:

• When the number of single line picks to be included in a batch equals the maximum number defined, a new batch is created.

• When the total cubic value of the items in a batch is greater than the cubic volume of the cart, a new batch is created even if the maximum number of picks has not been reached.

The system also checks the setting of the Break Single Line Picks by Zone (E33) system control value.

Multi Line Orders Setup:

Maximum Number of Multi Line Picks (B40)

Enter the maximum number of multi-line pick slips to be included in each batch. A multi-line pick is a pick slip that contains two or more line items. This value sets a break point for the batches and is usually dependent upon the number of bins in your packing cart. This is a 7 position, numeric field.

Maximum Number of Zones (B41)

Enter the maximum number of zones (up to six) allowed on a multi-line pick slip before another batch is generated. Multiple line pick slips can contain items located in more than one zone.

Pick slips that have items in the same zones (up to the number of zones specified) are included in the same batch. Separate batches are created for pick slips that have items located in more zones than the number you specify in the Maximum Number of Zones field.

For example, a pick slip with items to be picked in zones A, B, and D are not included in the same batch as a pick slip with items to be picked in zones A, B, and R. However, a pick slip with items to be picked in zones A, B, and D are included in the same batch as a pick slip with items to be picked in zones A and D.

The system considers these factors in determining when to create a new batch of pick slips:

1. Multi line picks are generated by zone combination; all picks must be within the zone combination, which is normally the first position of the location code. When the zone combination changes, a new batch is generated. Even if the quantity of multi-line picks for a batch is 30, if only 18 picks match the zone combination, the batch contains only 18 picks.

2. When the number of multi-line picks to be included in a batch is equal to the maximum number defined, a new batch is generated.

3. The system determines the number of bins needed for a multi-line pick slip/order based on the total cubic volume of the items and the cubic volume of a bin. If the system determines that there are not enough bins in the cart to accommodate the batch, a new cart/batch is created.

For more information: See Fulfillment Introducing Pick Slip Generation.

Maximum Cube Value for a Carton (B45)

Purpose: Use this screen to define the maximum cubic value of a carton. Complete this system control value if you set Perform Cubing? (B36) to Y.

MSR0055 CHANGE Change System Control Value 11/12/99 11:48:43 Description . : Maximum Cube Value for a Carton Quantity . . . 100 Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Quantity field: Enter the maximum cubic value of a carton. This is a 7-position numeric field. This value is used during Pick Slip Generation, if the system control value Perform Cubing? (B36) has been set to Y, to determine the number of items that can ship in one carton.

This value can represent an actual cubic value of a standard carton size, or it can represent a relational value between an item and a box. For example, if you establish that the cubic value of a carton is 100%, you can define your items as percentages of 100. An item could have a cubic value of 20, meaning that it takes up 20% of the space within a carton.

The value you enter in the Quantity field should correspond to the cubic measure you have established for cartons, items, and batches.

For more information: See Fulfillment Introducing Pick Slip Generation.

Maximum Weight of a Carton (B46)

Purpose: Use this screen to define the maximum weight a carton can hold. Complete this system control value if you set Perform Cubing? (B36) to Y.

MSR0259 CHANGE Change System Control Value 11/12/99 11:50:41 Description . : Maximum Weight of a Carton. Weight . . . . 100.000 Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Weight field: Enter the maximum weight a carton can hold. This is an 8-position field with a 3-place decimal. This value is used during Pick Slip Generation, if the system control value Perform Cubing? (B36) has been set to Y, to determine the total number of items, based on the total weight, that can ship in one carton.

The value you enter in the Weight field should correspond to the weight measurement you have established for items.

For more information: See Fulfillment Introducing Pick Slip Generation.

Consolidated Invoice (B49)

Purpose: Use this screen to indicate whether to consolidate invoices for shipments on the same order on the same date.

MSR0052 CHANGE Change System Control Value 5/28/98 15:57:10 Description . : Consolidated Invoice Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you wish to consolidate order shipments that occur on the same date onto a single invoice.

System control values that affect whether invoice consolidation takes place:

• The Invoice Consolidation Method (E29) system control value defines whether the system consolidates invoices across all ship-to addresses on the order, or only within the same ship-to address.

• Setting the Capture Addresses for Invoice (J24) system control value to Y prevents invoice consolidation when you change the billing or shipping address between shipments.

• Setting the Update Invoice File with System Date During Billing (D51) system control value to Y prevents invoice consolidation.

• If the Generate Invoice Number at Pick Gen (H80) system control value is set to Y, any invoice numbers assigned at pick slip generation are not consolidated.

Other factors that prevent invoice consolidation:

• Invoice consolidation does not apply to express-billed orders.

• Processing deposits (using Processing Auto Deposits (SDEP)) between shipments prevents invoices from consolidating if the first invoice included a deposited payment method.

Note: If you use the Generic Invoice Download API and the retail store restock option to generate purchase orders in CWStore, you should not turn on the consolidate invoice option. Consolidating invoices would result in sending confusing purchase order information to CWStore.

Additional related system control values:

• The Consolidated Credit Invoice (K06) system control value controls the consolidation of credit invoices.

• If the E-mail Shipment/Return Confirmation Notification Immediately (K07) system control value is set to Y, then it is possible for the customer to receive multiple shipment confirmation emails on the same date, with each subsequent confirmation listing the newly-shipped item(s) plus each item shipped previously that day.

Enter N if you do not want to consolidate invoices. All pick slips produce separate invoices, regardless of when they ship (bill).

Note: After changing the setting of this system control value, end the background jobs and then restart them to make your change take effect.

For more information: See the Invoice Consolidation Method (E29) system control value for a discussion of invoice consolidation and examples.

Edit Warehouse/Reservation Values Screen(B50)

Purpose: Use this screen to define the parameters that control immediate and batch reservation.

MSR0428 ENTER Edit Warehouse/Reservation Values 11/12/99 12:32:44 EZK Mail Order Immediate reservation . . . Y (Y,N) FIFO flag . . . . . . . . . Y (Y,N) Default warehouse . . . . . 2 Ship complete from 1 whse . N (Y,N) Split line over multi whse . Y (Y,N) Evaluate Warehouse List only (Y,N) Reservation lead days . . . 1 Reservation at Final Accept. (Y,N) Application area . . . . . . FUL Application group . . . . . RSV F3=Exit F12=Cancel

Immediate Reservation (A64)

If you enter Y in this field, inventory is reserved for all orders (open and held) as each line item is entered in Order Entry.

There are only two exceptions. Inventory is not reserved for:

• Orders for customers with a Y in the Bypass Reservation field in the customer's record.

• Items in which the order quantity is greater than the SKU reserve limit in the Item file.

If you enter N, inventory is reserved for orders by running a batch program after the orders have been entered and processed.

FIFO Flag (A03)

If you enter Y in this field, inventory is held for orders on a first-in/first-out basis, regardless of whether the order is eligible for reservation. This field must be set to Y if Immediate Reservation (A64) is set to Y.

If you enter N, inventory are not held for orders that are not eligible for reservation.

For example, if you are using Batch Reservation and a customer's order is being held from reservation because of a balance due, inventory are not held for that order, but rather are allocated to the next eligible “pickable” order.

Note: If this field is set to N, the system subtracts the SKU open quantity from the On hand quantity for each warehouse in calculating the Available quantity. For example, if you have 10 units of an item on-hand in warehouse 1 and warehouse 2, and you enter an order for a quantity of 2, the system displays an available quantity of 8 in both warehouse 1 and warehouse 2.

Default Warehouse (A04)

Enter the code for the warehouse (up to 3 positions, numeric) that default in Work with Items when you create an item or SKU and in the pop-up window when using the SKU generator.

Warehouse codes are defined in and validated against the Warehouse file. See Warehousing Creating and Maintaining Warehouses (WWHS).

Note: If you are in a multiple warehouse environment, you may want to leave this field blank.

Ship Complete from 1 Warehouse (B16)

Defines whether the system attempts to fulfill an order from the warehouse closest to the shipping destination using Warehouse Ranking in the warehouse list associated with the SCF of the order ship to.

Enter Y in this field if you want the system to attempt to fulfill an order from the warehouse closest to the shipping destination, using warehouse ranking for the selected warehouse list. See Warehouse Ranking for an explanation of the logic the system uses to determine the warehouse rank of each warehouse in the selected warehouse list.

Enter N or leave this field blank if you want the system to look to first reserve inventory in the item’s primary warehouse, as defined in the Item file. If a warehouse list is defined for the order ship to address, the system uses the warehouse list to reserve inventory only if the item’s primary location does not have enough inventory to fulfill the order. In addition, if the system uses the warehouse list to reserve inventory, the system does not perform Warehouse Ranking, but instead reserves inventory using the hierarchy assigned to the warehouses in the warehouse list.

Related system control values: The system looks at the setting of the Ship Complete from 1 Warehouse (B16), Split Line Over Multiple Warehouses (B19), and Evaluate Warehouses in Warehouse List Only (J47) system control values during the following processes:

• Warehouse Reservation Processing

• Warehouse Backorder Processing

• Evaluating Backorders for Reservation

• Unreserving Inventory using Warehouse Lists

Split Line Over Multiple Warehouses (B19)

Defines whether the system attempts to allocate the entire order line, even if it means the item is reserved across multiple warehouses.

Enter Y in this field if you want the system to attempt to allocate the entire order line, even if it means the item is reserved across multiple warehouses.

Enter N or leave this field blank if you want the system to attempt to allocate the entire order line; however, if the item cannot be fully reserved from one warehouse, the system allocates what it can in the one warehouse and then backorders the remaining unfulfilled quantity.

Related system control values: The system looks at the setting of the Ship Complete from 1 Warehouse (B16), Split Line Over Multiple Warehouses (B19), and Evaluate Warehouses in Warehouse List Only (J47) system control values during the following processes:

• Warehouse Reservation Processing

• Warehouse Backorder Processing

• Evaluating Backorders for Reservation

• Unreserving Inventory using Warehouse Lists

Evaluate Warehouses in Warehouse List Only (J47)

Defines whether reservation and backorder processing only reserves and backorders in warehouses defined in the selected warehouse list.

Warehouse lists are used to more efficiently allocate an order in the warehouse closest to the shipping destination. Each list contains the warehouses the system uses fulfill an order, and the sequence in which the warehouse is considered. A warehouse list is usually created for each region to which you ship. See Working with Warehouse Lists (WWHL) for more information on warehouse lists.

Enter Y in this field if you want the system to only evaluate the warehouses in the selected warehouse list during reservation and backorder processing.

In addition:

• When using Immediate Reservation, the system limits the quantity available to the quantity of the item that is available to sell in the eligible warehouse(s) in order to represent the true availability of the item based on where the item may actually ship. See Displaying Item Availability for Eligible Warehouses.

• When the system sells out an item with a soldout control code of either 2 or 3, the system limits the soldout calculation to the eligible warehouses instead of all allocatable warehouses. See Soldout Calculation for Eligible Warehouses.

• When calculating the expected ship date, the system limits the PO Layering records to those that can fulfill the order line so that the expected ship date represents the expected ship date of the item based on the open purchase orders for the warehouses that are eligible to ship the backordered item. See Expected Ship Date Calculation.

If an item warehouse record does not exist for any of the warehouses in the selected warehouse list or a warehouse list is not associated with the SCF of the order ship to address:

• reservation processing reserves inventory from the item’s primary warehouse.

• backorder processing backorders inventory against the item’s primary warehouse.

Enter N or leave this field blank if you want the system to evaluate the item’s primary warehouse and the warehouses in the selected warehouse list during reservation and backorder processing.

The setting of the Ship Complete from 1 Warehouse (B16) system control value determines the order in which the system evaluates the item’s primary warehouse and the warehouses in the selected warehouse list.

Related system control values: The system looks at the setting of the Ship Complete from 1 Warehouse (B16), Split Line Over Multiple Warehouses (B19), and Evaluate Warehouses in Warehouse List Only (J47) system control values during the following processes:

• Warehouse Reservation Processing

• Warehouse Backorder Processing

• Evaluating Backorders for Reservation

• Unreserving Inventory using Warehouse Lists

Reservation Lead Days (B27)

Enter the number of days (up to 3 positions, numeric) after which an order (or order line) should be considered a future order and are not reserved.

Calculating a future order:

If the arrival date minus the reservation lead days is greater than today's date, the order is considered a future order, because it is not yet time to reserve the merchandise.

 

Arrival date = 12/20; Today's date = 12/5; reservation lead days = 5; 12/20 - 5 = 12/15; order is a future order.

 

The quantity on future order in the Item/SKU file increases, and the quantity open does not increase. Each night the system evaluates if the order should be put in an open status through periodic processing.

Reevaluate Reservation Logic at Final Accept (M01)

Defines whether the system reevaluates item reservation on a ship to order during the final order accept, and if possible, re-reserve items so that the items ship from a single warehouse in the warehouse list.

• Enter Y in this field if you want the system to reevaluate item reservation on a ship to order during the final order accept.

• Enter N or leave this field blank if you do not want the system to reevaluate item reservation during the final order accept.

Note: If you enter Y in this system control value, you must also enter Y in the Ship Complete from 1 Warehouse (B16) system control value so that the system first tries to reserve inventory using the selected warehouse list for the order.

Processing details: When the Reevaluate Reservation Logic at Final Accept (M01) system control value and Ship Complete from 1 Warehouse (B16) system control values are set to Y the system uses the following logic.

1. Reserve the entire order line quantity in one warehouse in the warehouse list, using Warehouse Ranking.

2. If the entire order line quantity cannot be reserved in one warehouse in the warehouse list, then look at the settings of the Split Line Over Multiple Warehouses (B19) and Evaluate Warehouses in Warehouse List Only (J47) system control values to determine the warehouse(s) to reserve against.

3. During the final order accept, reevaluate the reserved items on the order to see if all of the items can ship from one warehouse in the warehouse list, evaluating the warehouses in warehouse list priority sequence.

• If all of the reserved items on the order can ship from one warehouse in the warehouse list, re-reserve the items on the order in that warehouse. Any items on backorder retain the warehouse currently assigned.

• If all of the reserved items on the order cannot ship from one warehouse in the warehouse list, retain the current warehouse assigned to each item.

Items on backorder: Items that are fully on backorder are not included in the reevaluation that happens during the final order accept; see Warehouse Backorder Processing for more information on the warehouse the system backorders against based on the setting of certain system control values and see Evaluating Backorders for Reservation for more information on how the system determines which backordered items receive stock first.

Items that are partially reserved: If an order line contains an item that is partially reserved and partially on backorder, the system includes the reserved quantity of the item in the reevaluation that happens during the final order accept.

Set items: When the Reevaluate Reservation Logic at Final Accept (M01) system control value is set to Y, the system also ensures that at least one component item ships from the warehouse in which the main set item appears on the pick slip.

Example: You enter the following order lines on an order shipping to zip code 01129. SCF 011 is associated with warehouse list 6, which contains warehouses 601, 602, and 603. The default warehouse is 207.

Item	Order Qty	Item Warehouses	Avail Qty	Results
AB10	1	206 (primary whs) 601 (1st whs in list) 602 (2nd whs in list) 603 (3rd whs in list)	6 1 10 25	The system reserves 1 unit in warehouse 601 since that is the first warehouse in the warehouse list that can fulfill the order quantity.
BO10	1	206 (primary whs) 601 (1st whs in list) 602 (2nd whs in list) 603 (3rd whs in list)	0 0 0 0	The system backorders 1 unit in warehouse 206.
CD10	2	206 (primary whs) 601 (1st whs in list) 602 (2nd whs in list) 603 (3rd whs in list)	6 1 10 25	The system reserves 2 units in warehouse 602 since that is the first warehouse in the list that can fulfill the order quantity.
EF10	3	206 (primary whs) 601 (1st whs in list) 602 (2nd whs in list) 603 (3rd whs in list)	6 1 2 5	The system reserves 3 units in warehouse 603 since that is the first warehouse in the list that can fulfill the order quantity.
GH10	4	206 (primary whs) 601 (1st whs in list) 602 (2nd whs in list) 603 (3rd whs in list)	6 1 1 1	The system backorders 4 units in warehouse 206.
SETM	1	206 (primary whs)	0	Master set item The system assigns warehouse 206 to the master set item.
SET1	1	206 (primary whs) 601 (1st whs in list) 602 (2nd whs in list) 603 (3rd whs in list)	10 1 2 1	Set Component 1 The system reserves 1 unit in warehouse 601 since that is the first warehouse in the list that can fulfill the order quantity.
SET2	2	206 (primary whs) 601 (1st whs in list) 602 (2nd whs in list) 603 (3rd whs in list)	20 1 2 3	Set Component 2 The system reserves 2 units in warehouse 602 since that is the first warehouse in the list that can fulfill the order quantity.
SET3	3	206 (primary whs) 601 (1st whs in list) 602 (2nd whs in list) 603 (3rd whs in list)	16 1 2 3	Set Component 3 The system reserves 3 units in warehouse 603 since that is the first warehouse in the list that can fulfill the order quantity.
During the final order accept, the system reevaluates the items on the order to see if all of the reserved items can ship from one warehouse in the warehouse list. In this example, warehouse 603 in the warehouse list can ship all of the items. The system: • re-reserves the 1 unit of AB10 from warehouse 601 to warehouse 603 • re-reserves the 2 units of CD10 from warehouse 602 to warehouse 603 • re-reserves the master set item from warehouse 601 to warehouse 603 • re-reserves the 1 unit of SET1 from warehouse 601 to warehouse 603 • re-reserves the 2 units of SET2 from warehouse 602 to warehouse 603

For more information: See:

• Warehouse Reservation Hierarchy for more information on the hierarchy the system uses to determine the warehouse to assign to an order line.

• Warehouse List Hierarchy for more information on the hierarchy the system uses to determine which warehouse list to select for an order.

• Warehouse Ranking for more information on how the system selects a warehouse in the warehouse list to reserve against, based on the warehouse selected for previous items on the order.

• Warehouse Reservation Processing for more information on the processing the system performs, based on the setting of the System Control Values Related to Warehouse List Processing.

• Warehouse Backorder Processing for more information on the warehouse the system backorders against based on setting of certain system control values.

Pick/Pack Verification Entry Format (B59)

Purpose: Use this screen to define the default format you want to use during Pick/Pack Verification.

MSR0051 CHANGE Change System Control Value 10/22/99 8:55:25 Description . : Pick Pack Verification Entry Format Code . . . . . LONG SHORT UPC Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the code that defines the default format for the Pick/Pack Verification screen. Pick/Pack Verification allows you to verify items being packed using a scanning device, which scans the pick number and the item number.

• LONG entry format: The LONG format requires you to enter or scan the pick number and the item code/SKU.

• SHORT entry format: The SHORT format requires you to enter or scan the pick number and the 7-character short SKU (which represents the system-assigned numeric SKU).

• UPC entry format: The UPC format requires you to enter or scan the pick number and the UPC code defined for the item. You can define a UPC code for an item in Work with Item/SKUs. See Merchandising Entering Additional Item Information.

If you do not enter a value, the short SKU format automatically appears on the Pick/Pack Verification screen.

For more information: See Fulfillment Working with Pick/Pack Verification (WPPV).

P/P Scan by Unit Default (B60)

Purpose: Use this screen to define if you use a scanner during Pick/Pack Verification.

MSR0052 CHANGE Change System Control Value 11/12/99 12:09:47 Description . : P/P Scan by Unit default Yes/No . . . . N (Y,N) Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you are using a scanning device to enter the number of items packed during Pick/Pack Verification. The number 1 automatically defaults to the Quantity packed field if this value is set to Y.

Otherwise, enter N if you are not using a scanning device; you need to enter a quantity manually in the Quantity packed field.

For more information: See Fulfillment Working with Pick/Pack Verification (WPPV).

Default Restock Location (B62)

Purpose: This system control value is not currently used.

Edit PC Manifesting Values Screen

Purpose: Use this screen to indicate if you use PC manifesting to confirm shipments.

CommercialWare provides the standard data for each field, which you can change if necessary. Each field on this screen is required.

MSR0489 ENTER Edit PC Manifest Values 3/14/97 13:05:38 Mail Order Company Use PC Manifesting? . . . . . : Y (Y/N) PC Manifest Tool . . . . . . . : TRACERI Interactive Processing . . . . : M M=Manual, A=Automatic Wait time if automatic . . . . : 120 Communication Data Queue Setup Data Queue Name . . . . . . . : PCMANDATAQ Data Queue Library . . . . . . : CWM20DDTA Send Void Requests . . . . . . : N (Y/N) Void Request Wait Time . . . . : 10 (Seconds) F3=Exit F12=Cancel

Use PC Manifesting (B80)

Enter Y in this field if you are using PC manifesting. See PC Manifest Socket Interface for an overview.

Note: You can still use manual confirmation if needed if you are using PC manifesting.

Enter N if you are manually confirming each pick slip using the Confirmation function.

PC Manifest Tool (B81)

Enter the code that identifies the type of PC manifest system you are using. You should set this field to TracerI (Tracer Interactive) if you are using PC manifesting.

When you use PC manifesting, records are not downloaded to the PC manifest station. When the pick slip is scanned at the station, the station communicates with the iSeries interactively and the information from the pick slip is added to the upload file (which resides only on the iSeries) and is deleted from the download file (which resides only on the iSeries).

If you are using PC manifesting, the Use Pick Label Tracking in Manifest Interface? (D48) must be set to Y.

If you use PC manifesting, the PCINTASYNC background job processes the information received from the PC manifest station. See System Operations Working with the PCINTASYNC Job.

This is a 10-position, alphanumeric field.

Interactive Processing (E56)

If you are using PC manifesting, enter the code to identify whether each record in the Upload New file is automatically processed by PCINTASYNC as it is received and then sent to BILL_ASYNC or whether the information in the Upload New file is processed in a batch mode.

Valid options are A (automatic) or M (manual). If you set this field to M, you must run Submit Interactive PC Manifest (SPCI) to process the records in the Upload New file.

Wait Time if Automatic (E57)

If you are using PC manifesting and have Interactive Processing (E56) set to A, enter the number of seconds the PCINTASYNC job should wait before checking to see if there are any new records to be processed. See System Operations Working with the PCINTASYNC Job.

This is a 5-position, numeric field.

Data Queue Name (B77)

Enter the code for the data queue through which the set of commands are transmitted that allows communication between the iSeries and the PC.

Data Queue Library (B78)

Enter the name of the library where the data queue resides.

Send Void Requests (E45)

Enter Y in this field if you want to communicate with the PC manifest system when voiding pick slips on the iSeries. Enter N if you do not want to communicate with the PC manifest system.

If you are using PC manifesting, set Send Void Requests (E45) to N.

Void Request Wait Time (B79)

Enter the number of seconds that the iSeries waits (once a request to void and reprint a pick slip has been sent to the server PC) to receive a reply that the pick has been voided and reprinted. Once the number of seconds has been reached, a pop-up window appears with a system warning that the iSeries was not able to communicate with the PC. You are then required to either void the pick slip or cancel the void option.

This is a 5-position, numeric field.

Let Down Replenishment (C36)

Purpose: Use this screen to determine whether to use let down replenishment.

MSR0051 CHANGE Change System Control Value 11/12/99 11:53:15 Description . : Let Down Replenishment Code . . . . . REPORT *NONE REPORT RPT/EXEC Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Code field: Enter the code that defines the type of stock replenishment to use during Pick Slip Generation. Valid values are:

REPORT: The system creates the Replenish Control record and its details; however, item transfers are not processed immediately. You can use the Working with Replenishment Control (MSRP) menu option to print Replenishment Detail reports for each replenishment request, or print consolidated replenishment reports for several replenishments generated on the same day. You can then confirm and process the item transfers after reviewing the reports.

RPT/EXEC: The system creates the Replenish Control record and its details; furthermore, item transfers are processed automatically and the system generates the Replenishment Detail by 'From' Location Report.

*NONE: The system does not perform Let Down Replenishment. If there is not enough stock to allocate, the system prints the Item Stock Allocation Error report.

If you leave this field blank, the value defaults to *NONE.

The system looks at the setting of the Replenish from Location Type (A66) and Replenish from Primary during Let Down Replenishment (J42) system control values to determine the item locations where the system pulls stock from to fulfill the replenishment request.

For more information: See:

• Let Down Replenishment

• Replenish Primary Locations Overview

• Working with Replenishment Control (MSRP)

Pick Printing Program (C37)

Purpose: Use this screen to define the name of the program that prints pick slips.

MSR0053 CHANGE Change System Control Value 9/18/97 11:14:14 Description . : Pick Printing Program System name . . Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

System name: Enter the name of the program the system uses to print pick slips. The standard pick printing program name is FLR0439.

Other base print programs:

• For prefix description: If you have the Validate Prefix (I27) system control value set to Y, the base pick slip print program is FLR01104.

• For FormtasticTM: Use printing program FLR1108 to print a pick slip that render the bar code information as text rather than as a machine-readable graphic, Rendering the bar code as text may be a requirement of a forms design tool, such as Formtastic Fusion5TM from Quadrant Software, which needs to read the bar code information and render it in machine-readable form on the final pick slip output. This print program also differs from the standard printing program that it produces an SCS spool file rather than an IPDS spool file.

• For identcode: The base program that supports printing the identcode is FLR1106; see Prefix of Identcode (I28) for more information.

• For SmartLabel returns processing: The base program that supports printing the SmartLabel is FLR1116. See Using SmartLabel Returns Processing for more information.

• For FedEx SmartPost label on pick: The base program that supports printing the FedEx SmartPost label on the pick slip is FLR1198. See Printing SmartPost Pick Slips for more information.

You can print a pick slip through Work with Pick Slip Generation (fast path = WPSG). See Fulfillment Working with Pick Slip Generation (WPSG).

Printing extra labels: The system prints two extra pick control labels for a pick slip if the number of units on a pick slip is equal to or greater than the value defined in the Pick Units to Initiate Extra Labels (E91) system control value.

Leave this field blank only if you do not want to print pick slips.

Batch Pull Sheet Printing Program (C38)

Purpose: Use this screen to define the name of the program that is used to print batch pull sheets.

MSR0053 CHANGE Change System Control Value 11/12/99 11:57:14 Description . : Batch Pull Sheet Printing Program System name . . FLR0397 Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 2 F3=Exit F12=Cancel

System name field: Enter the name of the program that is used to print batch pull sheets. This is a 10 position, alphanumeric field. Complete this field if you are not using Cart/Bin picking.

If you are using the Cart/Bin picking feature, leave this field blank; otherwise, the system ignores your entry. See the Cart/Bin Batch Pull Sheet Printing Program (C39) control value.

This value is set by CommercialWare and should not be changed, unless you are using a batch pull sheet printing program written by your company.

For more information: See Fulfillment Introducing Pick Slip Generation.

Cart/Bin Batch Pull Sheet Printing Program (C39)

Purpose: Use this screen to define the name of the program that is used to print batch pull sheets for cart/bin picking.

MSR0053 OPEN Change System Control Value 4/28/94 13:20:50 Description . : Cart/Bin Batch Pull Sheet Printing Program System name . . FLR0393 Narrative . . . _______________________________________________________ _______________________________________________________ Application . : FUL Applic group . ALL Sequence# . . . 3         F3=Exit F12=Cancel

System name field: Enter the name of the program that is used to print batch pull sheets if you are performing Cart/Bin Picking. This program formats the batch pull sheets by printing the items grouped by batch. This is a 10-position, alphanumeric field. This value is set by CommercialWare and should not be changed, unless you are using a batch pull sheet printing program written by your company.

If you are not using the Cart/Bin picking feature (based on the setting of Use Cart/Bin Picking? (B38)), leave this field blank.

For more information: See Introducing Pick Slip Generation.

Perform Best Way Shipping (C47)

Purpose: Use this screen to indicate whether you use best way shipping at pick slip generation.

MSR0052 OPEN Change System Control Value 4/28/94 14:03:26 Description . : Perform Best Way Shipping Yes/No . . . . Y (Y,N) Narrative . . . ________________________________________________________ ________________________________________________________ Application . : FUL Applic group . PCK Sequence# . . . 100 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you are using the best way shipping feature at pick slip generation. This feature enables the system to select the least expensive shipping method from a user-selected list, using the shipping rate tables. Best way shipping compares the shipper specified for the shipment to the “best way” shippers flagged with a Type of P and determines, based on the appropriate rate table, the least expensive shipping method for the order. See Fulfillment Working with Shipping Rates (WSHR) for more information on using best way shipping at pick slip generation.

Note: This system control value does not affect the use of best way shipping in order entry. See Working with Best Way Shippers for more information.

Enter N if you are not using best way shipping at pick slip generation.

Check Location Quantities During Pick Generation (C54)

Purpose: Use this screen to indicate whether the Pick Generation program allocates inventory from specific pickable locations in the warehouse.

MSR0052 OPEN Change System Control Value 5/24/94 16:52:10 Description . : Check Location Quantities During Pick Generation Yes/No . . . . Y (Y,N) Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 300 F3=Exit F12=Cancel

Yes/no field: If you enter Y in this field, the system allocates inventory from the first pickable location with enough stock to satisfy the quantity printed on the pick. If there is not enough stock, the system allocates inventory across multiple pickable locations, beginning with primary, secondary, then bulk locations.

Reserving against a non-allocatable warehouse: In order to receive pick slips against a non-allocatable warehouse, this system control value must be set to Y. You can reserve inventory against a non-allocatable warehouse if the Reserve from Non-Allocatable Warehouse (J25) system control value is set to Y.

If you enter N, the system allocates the entire quantity printed (and reserved) on the picks from the item's primary location, defined in the Item/SKU record. Even if the primary location does not contain this quantity, the system determined that this quantity is available in the warehouse. You must perform Primary Location Replenishment Processing immediately after running the Pick Generation program to create the necessary replenishments from bulk locations to the primary locations to satisfy the quantities printed on the pick slips.

If you are using Let Down Replenishment to generate and/or immediately process replenishments during pick slip generation, you must set the Check Location Quantities During Pick Slip Generation system control value to Y.

For more information: See:

• Replenish Primary Locations Overview

• Let Down Replenishment

Print Batch Pull Sheet Item Summary (C59)

Purpose: Use this screen to define whether to print the Batch Pull Sheet Item Summary report when printing pick slips.

MSR0052 OPEN Change System Control Value 3/27/95 11:50:49 Description . : Print Batch Pull Sheet Item Summary Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . Sequence# . . . F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to print the Batch Pull Sheet Item Summary report automatically when printing pick slips. This report lists the items, picking locations, total quantity to pick, and item descriptions for each item printed on the pick slips.

This is a convenient way of picking the total quantity required of a single item from a location without first sorting through all pick slips including this item.

Enter N if you do not wish to print this report when printing pick slips.

Sample Batch Pull Sheet Item Summary Report:

CommercialWare Mozart Rel 1.1 Batch Pull Sheet Item Summary LEE_H FLR0377 3/27/95 12:12:06 Page 1   Warehouse 1 Billing Batch # 1233   Item# Location Qty to Pick Description ------------------------ -------- ----------- ------------------------------------ BELT A010101 73 LEATHER BELT   SHIRT 14 BLU PP AABULK 4 LONG SLEEVE BUTTON DOWN SHIRT   F7202 S A020104 16 SCOOPNECK POINTELLE COTTON KNIT   F4003 B000010 10 VERSAILLES FLORAL SCARF F3905 006010 25 ETCHED BRASS HOOP

For more information: See Fulfillment Introducing Pick Slip Generation.

Pick Sort Program Name (C65)

Purpose: Use this screen to identify the program that sorts data on the pick slips.

MSR0053 OPEN Change System Control Value 3/27/95 12:00:12 Description . : Pick Sort Program Name System name . . Narrative . . . Application . : FUL Applic group . Sequence# . . . F3=Exit F12=Cancel

System name field: Enter the name of the program used to sort information on pick slips.

The System name field is a 10-position optional field.

Base pick sort program: The base pick sort program is FLR0395; however, you may use a different program if you require a unique sort.

No sort pick sort program: If you use the program FLR0557, the system does not perform any sort at all. This option may be useful to you if you use an external product or service to produce your pick slips, because you do not expend system resources on sorting and consequently improve performance. If you do use this sort program, the system does not produce an Item Stock Allocation Error report or picking pullsheets, and does not perform cart/bin picking, regardless of your other system control value settings.

Wave picking pick sort program: The base pick sort program for wave picking is FLR0395; this program allows you to sort pick slips in wave, lane, bin number sequence. The system performs wave picking during pick slip generation if the Use Wave Picking (J87) system control value is set to Y; see Using Wave Picking for an overview of the wave picking process.

For more information: See Introducing Pick Slip Generation.

Declared Value Type (C66)

Purpose: Use this screen to define how to calculate the declared value for a shipment.

MSR0051 OPEN Change System Control Value 3/27/95 12:12:47 Description . : Declared Value Type Code . . . . . COST RETAIL Narrative . . . Application . : FUL Applic group . Sequence# . . . F3=Exit F12=Cancel

Code field: The value you enter here controls how declared value is calculated for items being shipped. The declared value identifies the value of the items being shipped in case the shipper loses the package and must reimburse you for the lost items.

Valid values are: COST or RETAIL.

Enter COST to calculate declared value based on the price at which you purchased the item from your vendor.

Enter RETAIL to calculate declared value based on the price at which the item was sold.

For example, your cost to purchase an item may be $17.00 (COST); whereas, the price at which you sell the item is $35.00 (RETAIL).

The business reason for this system control value is that some shippers charge an extra fee for packages with a declared value over a specific dollar amount (for example, any package over $100.). Your past experiences with a shipper (shipper reliability) may influence how you set this value. If the shipper is unreliable, for example, you may set this value to RETAIL so that you can recoup the full value of the package. If the shipper is reliable, however, you may set this value to COST so that you can avoid extra shipping charges.

Spiegel Vendor Number (C75)

Purpose: Use this screen to define a code to identify Spiegel to the Spiegel Interface program.

MSR0054 OPEN Change System Control Value 9/08/94 14:59:17 Description . : Spiegel Vendor Number Number . . . . 903 Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 100 F3=Exit F12=Cancel

Number field: Enter the vendor number you have defined for Spiegel. The Spiegel Interface uses this value when creating the Held Orders by Pay Type report, which lists the Spiegel orders for the specified pay type that are on hold and require manual authorization.

Additionally, this value is used when producing the Spiegel Invoice file that contains orders with Spiegel charges. Spiegel is invoiced for these charges, and receives a commission, in turn, for these orders.

For more information: See Marketing Overview of the Spiegel Interface.

Print Amounts on Drop Ship Picks (C81)

Purpose: Use this screen to define whether prices print on drop ship pick slips.

MSR0052 OPEN Change System Control Value 3/27/95 14:03:20 Description . : Print Amounts on Drop Ship Picks Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . Sequence# . . . F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to print prices on drop ship pick slips; otherwise enter N to suppress prices.

A drop ship pick slip is a pick slip that is printed for an item that you sell, but do not stock. Instead, you send the drop ship pick slips to the vendor so that the vendor can ship the item directly to the customer (thus, fulfilling the order).

The business reason for suppressing this information is that you may not want the vendor to know the price at which you sell the item.

For more information: See Fulfillment Introducing Pick Slip Generation.

Allow Only Single Line on Drop Ship Picks (C82)

Purpose: Use this screen to define whether a single item or multiple items print on a drop ship pick slip.

MSR0052 OPEN Change System Control Value 3/27/95 14:13:52 Description . : Allow only single line on drop ship pick Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . Sequence# . . . F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to print only a single item per drop ship pick slip; otherwise, enter N to print multiple items on a drop ship pick slip.

If you are printing a single drop ship pick slip for each drop ship item, the drop ship items may be shipped in separate shipments to the customer. If printing multiple items on a drop ship pick slip, you can keep the drop ship items on an order together.

A drop ship pick slip prints for an item you sell but do not stock. You forward the drop ship pick slip to your vendor. Your vendor ships the item directly to the customer, thus fulfilling the order.

Drop ship sets: If this system control value is set to Y and you print a drop ship pick slip for a drop ship set, the system creates a separate drop ship pick slip for the set master item and each component item. See Defining Sets as Drop Ship for more information on drop ship set processing.

For more information: See Fulfillment Introducing Pick Slip Generation.

Spiegel Batch Size (D05)

Purpose: Use this screen to define the maximum number of CWDirect invoices that can be consolidated into one Spiegel invoice batch.

MSR0054 OPEN Change System Control Value 3/27/95 15:28:17 Description . : Spiegel Batch Size Number . . . . Narrative . . . Application . : FUL Applic group . Sequence# . . . F3=Exit F12=Cancel

Number field: Enter the maximum size of a batch of invoices sent to Spiegel. This value is used only if you are using the Spiegel interface; in this situation, you accept and fulfill orders for Spiegel, then charge Spiegel a commission for the order fulfillment.

The system consolidates a specific number of CWDirect invoices into a single batch. The system begins a new batch when the number of invoices reaches the value defined in this field.

This is a 7-position, numeric field. Entry to this field is required only if using the Spiegel interface.

For more information: See Marketing Overview of the Spiegel Interface.

Spiegel Account Number (D06)

Purpose: Use this screen to define the billing account number to which A/R purchases post for Spiegel orders.

MSR0054 OPEN Change System Control Value 3/27/95 15:35:31 Description . : Spiegel Account# Number . . . . Narrative . . . Application . : FUL Applic group . Sequence# . . . F3=Exit F12=Cancel

Number field: Enter the Bill To (account) number to which Spiegel orders paid on-account (A/R) post. All Spiegel orders (identified by a specific pay code) paid on-account use this Bill To account number so that all Spiegel orders are consolidated to a single account.

Bill To numbers are defined in and validated against the Bill To Account file.

This is a 7-position numeric field. Entry is required only if using the Spiegel interface.

For more information: See Marketing Overview of the Spiegel Interface.

Prorate Freight Charges (D39)

Purpose: Use this screen to define whether to charge the customer for all freight charges on an order with the first shipment, or to charge a proportional amount of freight for partial shipments on an order.

MSR0052 CHANGE Change System Control Value 7/19/96 9:11:22 Description . : Prorate Freight Charges Yes/No . . . . N (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to charge a proportional amount of freight for partial shipments.

A customer places an order for two items at a price of $10.00 each. Total freight on the order is $4.00. One of the items is on hand, the other is backordered. When you ship and bill the first item, the system charges $2.00 freight. The system charges the remaining $2.00 when you ship and bill the backordered item.

You can prorate freight only for order level freight methods, listed in this table.

Order Level Freight Methods
Description	Code
Freight by dollar chart/offer	$O
Freight by dollar chart/source	$S
Freight by source code percentage	PS
Freight by ship via percentage	PV
Freight by recipient	R
Flat rate by ship-to	F
Actual freight	A
Freight by order weight	OW
Freight by offer price	OP

The system uses the Freight method you define for the source code on an order.

Dollar chart freight methods: Before deciding whether to prorate freight, it is useful to consider certain scenarios that can result if you use dollar chart freight methods. Prorating freight is always calculated by percentage, even when the freight method on the order uses a dollar chart. For example, a freight method is using the following dollar chart:

Merchandise Total	Freight
$0.01 - $24.99	$4.00
$25.00 - $49.99	$6.00
$50.00 - $74.99	$8.00
$75.00 - $100.00	$10.00

An order’s merchandise total is $100.00, so the total freight charge on the order is $10.00. However, the merchandise total for the first shipment is just $20.00. The system prorates freight by percentage, so the first invoice has a freight charge of $2.00 (20% of $10.00) rather than applying the $4.00 from the dollar chart.

If you subsequently process a return for that first $20.00 shipment, the system does not credit the $2.00 freight from the first invoice; the merchandise total is now $80.00, which still merits a $10.00 freight charge based on the dollar chart.

See below for more examples of how refunding works with prorated freight.

Cancellations with dollar-chart freight methods: When the order uses a dollar chart, processing a cancellation against a partially shipped order can result in a discrepancy between the total freight that is billed and the resulting order balance.

Example: Assume an order uses the example dollar chart provided above, and the same scenario where the order’s merchandise total is $100.00 with a total freight charge on the order is $10.00; again, the merchandise total for the first shipment is $20.00, resulting in a $2.00 freight charge billed for the first shipment. However, if the customer orders the remaining $80.00 in merchandise, the final freight for the order is $4.00, even though this amount of freight was never billed. If the order was prepaid, the refund amount would reflect the freight charge of $4.00 rather than the $2.00 that was billed; the customer would not receive the additional $2.00 in the refund. However, the $2.00 discrepancy can cause inconsistency in general ledger postings and reporting.

Refunds on freight: If this system control value is set to Y, and you are using an order-level freight calculation, freight refunds may be prorated, depending on your freight calculation method. You should test your individual method to determine whether freight refunds is prorated.

Example: Freight method is $S (Dollar chart by source). Prorate Freight Charges is set to Y. A customer orders two units of an item. Freight for the order is $5.00. The customer returns one unit. Freight charges of $2.50 is refunded on the return.

Example: Freight method is F (Flat rate by order). Prorate Freight Charges is set to Y. A customer orders two units of an item. Freight for the order is $5.00. The customer returns one unit. No freight charges is refunded on the return. The customer subsequently returns the second unit of the item. The full freight charge of $5.00 is refunded on the second return.

Freight exempt items: There is no freight charge on a pick slip, even if there are non-freight exempt items on the order, under these conditions:

• this system control value is set to N

• the Use Item Freight Exemption File (E73) system control value is set to Y

• the pick slip includes only freight exempt items

• the order uses one of the freight methods listed in Working with Freight Exempt Items (WFEI)

This system control value also controls whether any service charge by ship via on an order is prorated. See Fulfillment Working with Ship Via Codes (WVIA) for more information on defining a service charge by ship via.

Note: If you override the freight amount in order entry or order maintenance, the freight is not prorated.

Enter N if you want to charge the entire freight amount with the first shipment on an order.

Number of Pick Control Labels (D47)

Purpose: Use this screen to define the number of label records to create for each pick slip record you download to your PC manifesting station. You can use the pick control label number to track a pick slip that has been split into multiple cartons. The system uses this value only if you entered Y for the Use PC Manifesting (B80) and Use Pick Label Tracking in Manifest Interface? (D48) system control values. In order to use pick label tracking, you must enter a number greater than or equal to 1 in the Number field of this system control value.

This screen defines the number of label records to create. The pick slip printing program you use defines the number of labels that actually print. See Pick Printing Program (C37).

MSR0054 CHANGE Change System Control Value 12/11/95 14:30:01 Description . : # of Pick Control Labels Number . . . . 3 Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Number field: Enter the number of label records to create for each pick slip. If you are using pick label tracking or PC manifesting, the value in this field must be greater than or equal to one. The system creates only one label record for drop ship pick slips.

The system prints two extra pick control labels for a pick slip if the number of units on a pick slip is equal to or greater than the value defined in the Pick Units to Initiate Extra Labels (E91) system control value.

For more information: See Fulfillment Introducing Pick Slip Generation.

Use Pick Label Tracking in Manifest Interface? (D48)

Purpose: Use this screen to indicate if you are downloading multiple pick slip label records to a PC manifesting station. This might be useful if you often split pick slips into multiple cartons for shipping. See Number of Pick Control Labels (D47) for information on defining the number of label records to create. You must create at least 1 label in order to use pick label tracking.

MSR0052 CHANGE Change System Control Value 12/08/95 16:56:49 Description . : Use Pick Label Tracking in Manifest Interface? Yes/No . . . . Y (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field, the PC manifest download file accepts more than one label per pick slip. If you enter N, the download file does not accept multiple labels for pick slips.

If you do not use PC manifesting, you should enter N in this field. See Manually Confirming Shipments (MCON).

If you use PC manifesting, you should set this field to Y. See PC Manifest Socket Interface.

When the first label for a pick slip is wanded at the PC manifest station and the label record is sent through the manifest upload, the system:

• deletes the pick label record

• bills all merchandise, handling, and other charges for the pick slip through the billing ASYNC (The exception is when you are using actual freight; in this case, additional freight charges are billed on subsequent label records.)

• deletes the pick control header record

See PC Manifest Socket Interface for an overview.

Periodically, you must purge unused label records from your system. See System Operations Purging Unused Pick Control Label Records (PLBS).

Conditions for use of pick label: In addition to entering Y at this screen, these conditions must be met to use pick label tracking:

• You must be using PC manifesting as defined in the System Control file (see Use PC Manifesting (B80))

• You must enter a value greater than or equal to 1 at the Number of Pick Control Labels (D47) screen.

• You must be using a PC manifesting system that supports multiple label tracking.

Sort Pick Slips by Gift Flag (D53)

Purpose: Use this screen to specify whether the system separates gift orders from non-gift orders when sorting pick slips.

MSR0052 CHANGE Change System Control Value 2/07/96 11:13:51 Description . : Sort Picks by Gift Flag Yes/No . . . . Y (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 101 F3=Exit F12=Cancel

Yes/No field: If you enter Y in this field or leave it blank, the system sorts pick slips based on whether their orders are flagged as gifts (the Gift field in Order Entry is set to Y). If you enter N in this field, the system does not separate gift and non-gift pick slips.

For more information: pick slip sorting process, see Fulfillment Introducing Pick Slip Generation.

Sort Picks by Foreign/Domestic Flag (D54)

Purpose: Use this screen to specify whether the system separates foreign from domestic addresses when sorting pick slips.

MSR0052 CHANGE Change System Control Value 2/07/96 14:11:34 Description . : Sort picks by Foreign/Domestic Flag Yes/No . . . . Y (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 102 F3=Exit F12=Cancel

Yes/no field: If you enter Y in this field or leave it blank, the system sorts pick slips based on whether you are shipping the order to the default country defined in the System Control file. If you enter N in this field, the system does not separate foreign and domestic pick slips.

For more information: pick slip sorting process, see Fulfillment Introducing Pick Slip Generation.

Generate Coordinate Groups at Pick Gen for Ship Complete Orders (E10)

Purpose: Use this screen to define whether the system assigns coordinate groups to items on a ship-complete order during pick slip generation.

MSR0052 CHANGE Change System Control Value 10/25/96 10:57:21 Description . : Generate Coordinate Groups at Pick Gen for Ship Complete Ord Yes/No . . . . N (Y,N) Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 100 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to add a coordinate group code to items on a ship-complete order that share the same arrival date (the Ship complete flag on the Order Properties screen is set to Y), based upon each item's arrival date. The system overrides any coordinate groups you assigned to items before you generated pick slips and assigns a new coordinate group based upon arrival date; each item with the same arrival date receives the same coordinate group code.

Enter N or leave this field blank to run pick slip generation as usual. The system does not assign coordinate groups at pick slip generation. Coordinate groups that you assigned earlier is used.

See the examples of how the system assigns coordinate groups to an order's items during pick slip generation.

The system does not assign coordinate groups to these items:

• ship alone items

• continuity items

• drop ship items

• subscription items

Assigning Coordinate Groups To Set Items

The system looks to see whether items that are assigned the same coordinate group code are part of a set before determining if a pick slip can be generated when the Use Coordinate Groups Within Sets Only (E11) system control value is set to Y.

The system looks to see whether items that are assigned the same coordinate group code are part of a set. Each item within a set is then checked for item availability. A set is treated separately from any other item or set that is assigned the same coordinate group code. For example, if an item that is on backorder shares the same coordinate group code as a set, the set item can ship without waiting for the item on backorder.

Example: Examples of how the system assigns coordinate groups to an order's items during pick slip generation.

For these examples:

• today's date is 11/01/97

• there are 10 reservation lead days

Items with different arrival dates: An order contains:

• 1 regular item in-stock with an arrival date of 11/01/97

• 1 regular item on backorder with an arrival date of 11/01/97

• 1 regular item in-stock with an arrival date of 11/10/97

• 1 regular item on backorder with an arrival date of 11/10/97

• 1 regular item in a future ship status and an arrival date of 11/30/97

• 1 regular item in a future ship status and an arrival date of 11/30/97

Order Line	Item Type	Status	Arrival Date	System-assigned C/G #	Result
1	regular	in-stock	11/01/97	1	Lines 1 and 2 ship when line 2 is in-stock.
2	regular	on backorder	11/01/97	1
3	regular	in-stock	11/10/97	2	Lines 3 and 4 ship on 11/15/96 when line 4 is in-stock.
4	regular	on backorder	11/10/97	2
5	regular	future ship	11/30/97	3	Lines 5 and 6 ship together on 11/30/96.
6	regular	future ship	11/30/97	3
The system uses this calculation to determine whether to reserve an item with a future ship status:   Arrival date - Reservation lead days = Date   The system does not reserve an item with a future ship status if the date determined by this calculation is greater than today's date. For example, today's date is 11/01/97 and the order's arrival date is 12/11/97. There are 10 reservation lead days.   12/11/97 - 10 = 12/01/97   The system does not reserve this order's items since the calculated date is greater than today's date. See Order Entry Working with Items on the Order.

The system assigns coordinate groups to this order's items during pick slip generation based on this logic:

• line 1 is assigned coordinate group code # 1 because it is a regular item.

• line 2 is assigned coordinate group code # 1 because it is a regular item. Since lines 1 and 2 have the same arrival date, they are assigned the same coordinate group code. Since line 2 is on backorder, line 1 cannot ship until line 2 is in-stock.

• line 3 is assigned coordinate group code # 2 because it is a regular item with a different arrival date than lines 1 and 2.

• line 4 is assigned coordinate group code # 2 because it is a regular item. Since lines 3 and 4 have the same arrival date, they are assigned the same coordinate group code. Since line 4 is on backorder, line 3 cannot ship until line 4 is in-stock.

• line 5 is assigned coordinate group code # 3 because it is a regular item with a different arrival date than lines 1, 2, 3 and 4.

• line 6 is assigned coordinate group code # 3 because it is a regular item with the same arrival date as line 5.

Coordinate group exception items: An order contains:

• 1 regular item on backorder with an arrival date of 11/01/97

• 1 regular item in-stock with an arrival date of 11/30/97

• 1 drop ship item in-stock with an arrival date of 11/01/97

• 1 ship alone item in-stock with an arrival date of 11/30/97

• 1 subscription item in-stock with an arrival date of 11/01/97

Order Line	Item Type	Status	Arrival Date	System Assigned C/G #	Result
1	regular	on backorder	11/01/97	1	Line 1 ships by itself on 11/01/97.
2	regular	future ship	11/30/97	2	Line 2 ships by itself on 11/30/97.
3	drop ship	in-stock	11/01/97		Line 3 ships by itself on 11/01/97.
4	ship alone	in-stock	11/30/97		Line 4 ships by itself on 11/01/97.
5	subscription	in-stock	11/01/97		Line 5 ships by itself on 11/01/97.

The system assigns coordinate groups to this order's items during pick slip generation based on this logic:

• line 1 is assigned coordinate group code # 1 because it is a regular item.

• line 2 is assigned coordinate group code # 2 because it is a regular item with a different arrival date than line 1.

• line 3 is not assigned a coordinate group code because it is a drop ship item. Drop ship items are always excluded from the coordinate group routine.

• line 4 is not assigned a coordinate group code because it is a ship alone item. Ship alone items are always excluded from the coordinate group routine. Lines 2 and 4 do not ship together, but they may arrive together since they both have the same arrival date.

• line 5 is not assigned a coordinate group code because it is a subscription item. Subscription items are always excluded from the coordinate group routine. Lines 1, 3 and 5 do not ship together, but they may arrive together since they all have the same arrival date.

Use Coordinate Groups Within Sets Only (E11)

Purpose: Use this screen to define if the system checks whether items that are assigned the same coordinate group code are part of a set before determining if a pick slip can be generated.

MSR0052 CHANGE Change System Control Value 10/25/96 14:03:12 Description . : Use coordinate groups within sets only Yes/No . . . . N (Y,N) Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 100 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to check whether items that are assigned the same coordinate group code are part of a set. Each item within a set is then checked for item availability. A set is treated separately from any other item or set that is assigned the same coordinate group code. For example, if an item that is on backorder shares the same coordinate group code as a set, the set item can ship without waiting for the item on backorder.

Enter N or leave this field blank if you want the system to ship items on an order based on their assigned coordinate group code only. For example, if a set has the same coordinate group code as another item that is on backorder, the set must wait until the item on backorder is in-stock.

Example: An example of how the system ships items that are assigned the same coordinate group code. For this example, Use Coordinate Groups within Sets Only is set to Y.

This order includes:

• 1 set with in-stock components and an arrival date of 11/01/96

• 1 set with a component on backorder and an arrival date of 11/01/96

• 1 set with in-stock components and an arrival date of 11/30/96

Order Line	Item Type	Status	Arrival Date	System-Assigned C/G #	Result
1	set # 1 master	in-stock	11/01/96	1	A pick slip prints for this set and it ship by itself on 11/01/96.
2	set component	in-stock	11/01/96	1
3	set component	in-stock	11/01/96	1
4	set # 2 master	in-stock	11/01/96	1	A pick slip does not print. Set 2 ships when the component on backorder is in-stock.
5	set component	on backorder	11/01/96	1
6	set component	in-stock	11/01/96	1
7	set # 3 master	future ship	11/30/96	2	This set ships by itself on 11/30/96.
8	set component	future ship	11/30/96	2
9	set component	future ship	11/30/96	2

The system ships items that are assigned the same coordinate group code when the Use Coordinate Groups within Sets Only system control value is set to Y, based on this logic:

• set 1 is assigned coordinate group code # 1 because it is a set item that has 1 defined as its coordinate group code in the Set Detail file. A pick slip does print for this set since all of the component items are in-stock. Even though sets 1 and 2 are assigned the same coordinate group code, set 1 ships by itself because Use Coordinate Groups within Sets Only system control value is set to Y.

• set 2 is also assigned coordinate group code # 1 because it is a set item that has 1 defined as its coordinate group code in the Set Detail file. A pick slip does not print for this set since one of the component items in this set is on backorder. Even though sets 1 and 2 are assigned the same coordinate group code, set 2 ships by itself when it is in-stock because Use Coordinate Groups within Sets Only system control value is set to Y.

• set 3 is assigned coordinate group code # 2 because it is a set item that has 2 defined as its coordinate group code in the Set Detail file. A pick slip does not print for this set since it has a future ship status that is greater than the allowed reservation lead days calculation. See Order Entry Working with Items on the Order.

 

Example: Another example of how the system ships items that are assigned the same coordinate group code. For this example, Use Coordinate Groups within Sets Only system control value is set to N.

This order includes:

• 1 set with in-stock components and an arrival date of 11/01/96

• 1 set with a component on backorder and an arrival date of 11/01/96

• 1 set with in-stock components and an arrival date of 11/30/96

Order Line	Item Type	Status	Arrival Date	System-Assigned C/G #	Result
1	set # 1 master	in-stock	11/01/96	1	Sets 1 and 2 are treated as regular items and not as sets. Lines 1, 2, 3, 4 and 6 ship when line 5 is in-stock.
2	set component	in-stock	11/01/96	1
3	set component	in-stock	11/01/96	1
4	set # 2 master	in-stock	11/01/96	1
5	set component	on backorder	11/01/96	1
6	set component	in-stock	11/01/96	1
7	set # 3 master	future ship	11/30/96	2	Lines 7, 8 and 9 ship on 11/30/96.
8	set component	future ship	11/30/96	2
9	set component	future ship	11/30/96	2

The system ships items that are assigned the same coordinate group code when Use Coordinate Groups within Sets Only system control value is set to N, based on this logic:

• lines 1, 2 and 3 are assigned coordinate group code # 1 because they make-up a set item that has 1 defined as its coordinate group code in the Set Detail file. A pick slip does not print for lines 1, 2 and 3 since line 5 is assigned the same coordinate group code, and is on backorder. Lines 1, 2 and 3 ship when line 5 is in-stock because Use Coordinate Groups within Sets Only system control value is set to N.

• lines 4, 5 and 6 are assigned coordinate group code # 1 because they make-up a set item that has 1 defined as its coordinate group code in the Set Detail file. A pick slip does not print for lines 4, 5 and 6 since line 5 is on backorder. Lines 1, 2, 3, 4 and 6 ship when line 5 is in-stock because Use Coordinate Groups within Sets Only system control value is set to N.

• lines 7, 8 and 9 are assigned coordinate group code # 2 because they make-up a set item that has 2 defined as its coordinate group code in the Set Detail file. A pick slip does not print for lines 7, 8 and 9 since they are in a future ship status that is greater than the allowed reservation lead days calculation. See Generate Coordinate Groups at Pick Gen for Ship Complete Orders (E10).

The Use Coordinate Groups within Sets Only system control value works independently of the Generate Coordinate Groups at Pick Gen for Ship Complete Orders (E10) system control value. In order for the system to assign coordinate groups to an order's items based on arrival date only, Use Coordinate Groups within Sets Only system control value should be set to N.

For more information: See Merchandising Introducing Sets, for information about sets, and Fulfillment Reviewing Other Reservation Conditions, for information about coordinate groups.

Invoice Consolidation Method (E29)

Purpose: Use this screen to define whether invoices are consolidated for all ship-to addresses on an order, or only within the same ship-to address.

MSR0051 CHANGE Change System Control Value 3/12/98 11:40:16 Description . : Invoice Consolidation Method Code . . . . . ORDER ORDER SHIP Narrative . . . Application . : FUL Applic group : ALL Sequence# . . : 99 F3=Exit F12=Cancel

Code field: Set this field to ORDER to have the system consolidate shipments (or returns) on the same system date for all order ship-to addresses onto the same invoice.

Set this field to ORDER SHIP to have the system consolidate shipments (or returns) on the same system date onto the same invoice only if the shipments (or returns) are for the same order ship-to address.

The system uses the setting of this field:

• shipment invoices: only if the Consolidated Invoice (B49) system control value is set to Y.

• credit invoices: only if the Consolidated Credit Invoice (K06) system control value is set to Y.

Note: The settings of the Consolidated Invoice (B49) and of the Consolidated Credit Invoice (K06) system control value are independent. Based on your business requirements, you can consolidate shipment invoices only; consolidate credit invoices only; consolidate both shipment and credit invoices; or consolidate neither shipment and credit invoices.

Capture addresses? The Capture Addresses for Invoice (J24) system control value controls whether invoices consolidate if:

• the Consolidated Invoice (B49) system control value (or the Consolidated Credit Invoice (K06) system control value) is set to Y, and

• there are multiple shipments (or returns) for an order on the same system date, and

• the shipping or billing address changes between shipments (or returns). For example, you have just confirmed shipment of a pick slip for an order. Before you generate an additional pick slip for the same order, the customer calls and changes the billing or shipping address. If you confirm shipment of both pick slips on the same system date, the change in billing or shipping address prevents the shipments from consolidating into the same Invoice Header or Invoice Ship To as they otherwise would:

• If the Invoice Consolidation Method is set to ORDER SHIP, and the billing or shipping address changes for an order ship-to between billing pick slips, the system creates a separate Invoice Header number and Invoice Ship To record for each shipment.

• If the Invoice Consolidation Method is set to ORDER, and the billing or shipping address changes for an order ship-to between billing pick slips, the system creates a separate Invoice Header number for the pick slip that has a different shipping or billing address for a single ship-to; however, it does use the same Invoice Header number and a separate Invoice Ship To number when it bills a subsequent ship-to. Each Invoice Ship To is listed separately at the Display Invoices Screen in order inquiry. See example 4, below, for more information.

Invoice Consolidation Examples

In the following examples, an order includes two ship-to addresses. There are two separate pick slips for the first ship-to address and a pick slip for the second ship-to address. All three pick slips ship and bill on the same system date. These examples illustrate the effects of the three related system control values.

Note: Consolidated credit examples: Consolidation of credit invoices uses the same logic as consolidation of regular (debit) invoices based on the setting of the Consolidated Credit Invoice (K06) system control value and the other system control values discussed in the following examples.

Example 1: Consolidated invoice is set to N. In this situation, each pick slip produces a separate Invoice Header, each with a single Invoice Ship To record. This example assumes that the Capture Addresses for Invoice (J24) system control value is not a factor (it is set to N, or there is no change to shipping or billing addresses between shipments).

Example 2: Consolidated invoice is set to Y and Invoice consolidation method is ORDER SHIP. In this situation, the pick slips for the first order ship-to address are consolidated into a single invoice and Invoice Ship To record. The pick slip for the second order ship-to address creates a separate Invoice Header and Invoice Ship To.

Example 3: Consolidated invoice is set to Y and Invoice consolidation method is ORDER. In this situation, all three pick slips are consolidated into a single Invoice Header number. There are two separate Invoice Ship To records, one for each order ship-to address. This example also assumes that the Capture Addresses for Invoice (J24) system control value is not a factor (it is set to N, or there is no change to shipping or billing addresses between shipments).

Example 4: Consolidated invoice is set to Y, Invoice consolidation method is ORDER, and Capture addresses for invoice is set to Y. In this situation, there is a different billing or shipping address on the second pick slip for the first order ship-to address, and the shipments bill in the following order:

1. first shipment for ship-to 1

2. second shipment for ship-to 1 (after address change)

3. shipment for ship-to address 2

The result is that the separate shipping addresses for the first order ship-to are not consolidated onto the same invoice; instead, the second shipping address for the first ship-to is consolidated onto the same Invoice Header number as the second ship-to, but there is a separate Invoice Ship To for each.

The change of address for the first order ship-to prevents the two invoices for that ship-to from consolidating; however, since the invoice consolidation method is ORDER, the shipment for the second order ship-to is consolidated with the previous invoice number for the order.

Example 5: Consolidated invoice is set to Y, Invoice consolidation method is ORDER SHIP, and Capture addresses for invoice is set to Y. In this situation, if there is a different billing or shipping address on the second pick slip for the first order ship-to address, the different addresses prevent any invoice consolidation. Each separate pick slip produces a separate Invoice Header number and Invoice Ship To.

Break Single Line Picks by Zone (E33)

Purpose: Use this screen to define whether to break single line pick slips into separate cart/bin batches based on the warehouse zone.

MSR0052 CHANGE Change System Control Value 11/06/96 14:14:13 Description . : Break Single Line Picks By Zone Yes/No . . . . Y (Y,N) Narrative . . . Application . : ALL Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to create a separate cart/bin batch for pick slips that contain only one item line, if you are picking the items out of a separate zone in your warehouse. For example, the system would not put two single-line pick slips in the same cart/bin batch if you needed to pick one out of location A010101 (zone A) and the other out of B010101 (zone B).

Enter N or leave this field blank if you want the system to include single-line picks in the same cart/bin batch regardless of warehouse zone. All picks need to be within the same zone, which is normally indicated by the first position of the location code. When the zone changes, a new batch is generated. Even if the quantity of single line picks for a batch is 50, if only 20 picks can be generated for zone A, the batch contains only 20 picks.

For more information: See Fulfillment Introducing Pick Slip Generation.

Print One Drop Ship Invoice per Ship Alone Item (E38)

Purpose: Use this field to define whether the system prints a separate drop ship invoice for each ship alone item on an order.

MSR0052 CHANGE Change System Control Value 3/21/97 11:01:17 Description . : Print one drop ship invoice per ship alone item Yes/No . . . . (Y,N) Narrative . . . _________________________________________________________ _________________________________________________________ Application . : FUL Applic group . ALL Sequence# . . . 999 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to print a separate drop ship invoice for each ship alone item on an order.

Example: An example of how the system prints separate invoices for each ship alone item.

PO Line #	Item	Order Quantity	Invoice #	Explanation
1	Item A	1	1	Since items A and C are not ship alone items, they appear on the same invoice.
2	Ship alone item B	2	2 and 3	Since item B is a ship alone item, a separate invoice prints for each one ordered.
3	Item C	2	1	Item C appears on the same invoice as item A.

Enter N or leave this field blank to print one drop ship invoice that contains all items on an order, including ship alone items.

For more information:

• See Fulfillment Selecting Vendors for Drop Ship Processing (MDSP) for more information on printing drop ship purchase orders.

• See Merchandising Printing and Faxing Purchase Orders (MPRP) for more information on printing or faxing purchase orders.

Replenishment Report Program Name (E47)

Purpose: Use this screen to define the name of the program that prints the Replenishment Detail Report.

MSR0053 CHANGE Change System Control Value 12/10/96 15:39:09 Description . : Replenishment Report Program Name System name . . FLR0049 Narrative . . . Application . : FUL Applic group . STK Sequence# . . . 1 F3=Exit F12=Cancel

System name: Enter the name of the program that prints the Replenishment Detail report. The standard replenishment report program name is FLR0049.

The Replenishment Detail report can be used as a worksheet to assist you in confirming the item quantities that are replenished.

The system prints the Replenishment Detail report when you perform Primary Location Replenishment and Let Down Replenishment.

For more information: See:

• Replenish Primary Locations Overview

• Let Down Replenishment

• Replenishment Detail by 'From' Location Report

• Replenishment Detail Report by Item

• Replenishment Detail Report by 'To' Location

Create Manifest Download Extended Records (E77)

Purpose: Use this screen to define whether the system creates item weight records in the Download Extended Manifest file (FLMNDE) when you use a PC Manifest system to confirm shipments.

MSR0052 CHANGE Change System Control Value 7/24/97 8:56:26 Description . : Create Manifest Download Extended Records Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 1 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to create item weight records in the Download Extended Manifest file (FLMNDE) when you use a PC manifest system to confirm shipments. The system uses the value defined in the Ship weight field for each item in Work with Item/SKUs.

Item weight records are created in the Download Extended Manifest file as part of pick generation. The records are deleted when the corresponding download record is deleted through shipment confirmation. You can also delete and create item weight records when you void and reprint a pick slip; see Reprinting and Voiding Pick Slips (WVRP).

In order to pass item weight records to a PC manifest station, you must set these system control values correctly.

• Use PC Manifesting (B80) must be set to Y

• PC Manifest Tool (B81) must be set to TRACERI

• Use Pick Label Tracking in Manifest Interface? (D48) must be set to Y

Enter N or leave this field blank is you do not want the system to create item weight records in the Manifest Download Extended file when you use a PC manifest system to confirm shipments.

Pick Units to Initiate Extra Labels (E91)

Purpose: Use this screen to define whether pick generation prints two extra pick control labels for a pick slip.

MSR0054 CHANGE Change System Control Value 9/18/97 10:36:11 Description . : Pick Units to initiate extra labels. Number . . . . Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 99 F3=Exit F12=Cancel

Number: Enter a number in this field to define the total number of units needed on a pick slip before the system prints two extra pick control labels for a pick slip.

If the total number of units to ship on a pick slip is equal to or greater than this value, the system prints two extra pick control labels. If the total number of units to ship on a pick slip is less than this value, no extra pick control labels print.

Enter a zero or leave this field blank if you do not want the system to print two extra pick control labels for a pick slip.

For more information: See Fulfillment Introducing Pick Slip Generation.

Drop Ship Pick Print Program (E92)

Purpose: Use this screen to define the name of the print program the system uses when drop ship pick slips are printed.

MSR0053 CHANGE Change System Control Value 9/18/97 10:45:46 Description . : Drop Ship Pick Print Program. System name . . Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 99 F3=Exit F12=Cancel

System name: Enter the program name the system uses when drop ship pick slips are printed.

You can print a drop ship pick slip by pressing Enter in the Select Vendors for Drop Ship Picks function (fast path = MDSP). See Fulfillment Selecting Vendors for Drop Ship Processing (MDSP).

Leave this field blank if you do not want the system to print a special form for drop ship pick slips. When you print a drop ship pick slip, the system uses the program value defined in the Pick Printing Program (C37) system control value. The standard pick printing program name is FLR0439.

For more information: See Fulfillment Introducing Pick Slip Generation.

Add Printed Drop Ship Lines as Backordered on Pick (E93)

Purpose: Use this screen to define whether the system displays drop ship items as backordered on the regular pick slip even after a drop ship pick slip or purchase order has been generated for the drop ship item.

MSR0052 CHANGE Change System Control Value 4/27/07 9:43:51 Description . : Add printed D/S Lines as B/O on pick. Yes/No . . . . (Y,N) Narrative . . . When set to 'Y', drop ship items will print on the pick as a Backorder item even after the drop ship pick is created. Application . : FUL Applic group . PCK Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to display drop ship items as backordered on the regular pick slip even after a drop ship pick slip or purchase order has been generated for the drop ship item.

Regardless of the setting of this system control value, the system displays drop ship items as backordered on the regular pick slip if a drop ship pick slip or purchase order has not yet been generated for the drop ship item.

Enter N or leave this field blank if you do not want the system to display drop ship items as backordered on the regular pick slip if a drop ship pick slip or purchase order has already been generated for the drop ship item.

For more information: See:

• Selecting Vendors for Drop Ship Processing (MDSP) for more information on generating a drop ship pick slip or purchase order for a drop ship item.

• Introducing Pick Slip Generation for more information on generating regular pick slips.

Use Async Start Date for Billing Transactions (E95)

Purpose: Use this screen to define whether the system uses the Async start date as the billing date for billing transactions.

MSR0052 CHANGE Change System Control Value 9/19/97 15:24:34 Description . : Use Async Start Date for Billing Transactions Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the option of using the Async start date as the billing date for billing transactions or a different date, such as the Billing Header Data queue record date.

The system uses the Control ASYNC job (See System Operations Working with the CNTL_ASYNC Job) to start and end each of the background ASYNC jobs. Enter 7 next to the CNTL_ASYNC job to start the ASYNC jobs. The Override Async Start Date pop-up window displays:

Override Async Start Date Job date . . . . 91997 F3=Exit

Enter the date you want the system to use for billing transactions in the Job date field. The Controlling Async start date defaults in this field. You can override this date and enter a different date.

The fields updated with the date you enter here are:

• invoice date (all related files except the Invoice Header file)

• inventory transaction date

• general ledger interface date

Enter N or leave this field blank if you want the system to use the system date as the billing date. No pop-up window opens when you start the async jobs.

Withhold Picks due to Item Allocation Error (F04)

Purpose: Use this screen to define whether the system prints a pick slip for an order when an item on the order creates a stock allocation error.

MSR0052 CHANGE Change System Control Value 10/28/97 9:46:53 Description . : Withhold picks due to Item allocation error. Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 100 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you do not want the system to print a pick slip when an item on the order creates a stock allocation error.

The system does not print a pick slip for any item on the order that:

• prints on the same pick slip as the item that contains the item stock allocation error.

• contains the same coordinate group as the item that contains the item stock allocation error.

A pick prints for the items once the allocation error associated with the item on the order has been resolved. Printing one pick slip for an order is helpful if you want to reduce shipping costs.

Example: An example of how the system generates a pick slip when the Withhold Picks Due to Item Allocation Error system control value is set to Y.

Withhold Picks Due to Item Allocation Error = Y
Order Line	Item Type	Status	Coordinate Group Number	Result
1	regular item resulting in allocation error	in-stock		The system does not print a pick slip for the item which created an allocation error. The item displays on the Item Stock Allocation Error report.
2	ship alone item	in-stock		The system prints a separate pick slip for the ship alone item.
3	regular item	in-stock	1	The system does not print a pick slip for the 2 regular items that are coordinate grouped.
4	regular item	in-stock	1

Enter N or leave this field blank if you want the system to print a pick slip for an order when an item on the order creates a stock allocation error.

The system prints a pick slip for items on the order that did not create item stock allocation errors. A separate pick slip prints for items on the order that created item stock allocation errors once the errors have been resolved.

Example: An example of how the system generates a pick slip when the Withhold Picks Due to Item Allocation Errors system control value is set to N.

Withhold Picks Due to Item Allocation Error = N
Order Line	Item Type	Status	Coordinate Group Number	Result
1	regular item resulting in allocation error	in-stock		The system does not print a pick slip for the item which created an allocation error. The item displays on the Item Stock Allocation Error report.
2	ship alone item	in-stock		The system prints a separate pick slip for the ship alone item.
3	regular item	in-stock	1	The system prints a pick slip for the 2 regular items that are coordinate grouped.
4	regular item	in-stock	1

For more information: See Fulfillment Introducing Pick Slip Generation.

Print Drop Ship Invoice at time of Purchase Order Receiving (F10)

Purpose: Use this screen to define whether the system prints a drop ship invoice when a drop ship purchase order is received.

MSR0052 CHANGE Change System Control Value 2/10/98 9:04:39 Description . : Print Drop Ship Invoice at time of PO Receiving Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to print a drop ship invoice when a drop ship purchase order is received. (fast path = PORC).

The drop ship invoice contains this information:

• the customer's name and address

• the item(s) ordered (all lines print on the invoice even if the purchase order was partially received)

• the price the customer is being charged for each item

• any special handling information and charges (based on the selections made from a custom special handling format)

In order to print a drop ship invoice when you receive a drop ship purchase order, the Drop ship pick field in Work with Vendors (fast path = WVEN) must be set to N. This means that you send a purchase order instead of a drop ship pick slip to the vendor for drop ship items. The drop ship items are then sent to the customer directly from the vendor.

If you print drop ship invoices, you can forward the invoice and the drop ship purchase order to the vendor. The vendor can insert the invoice into the box when shipping the order to the customer.

The system also prints a drop ship invoice when you print a drop ship purchase order in Select Vendors for Drop Ship Picks (fast path = MDSP) if the Print Drop Ship Invoice with PO (C85) system control value is set to Y.

Enter N or leave this field blank if you do not want the system to print a drop ship invoice when a drop ship purchase order is received.

For more information:

• See Warehousing Selecting Purchase Orders for Receipt (PORC)

• See Merchandising Working with Vendors (WVEN)

• See Fulfillment Selecting Vendors for Drop Ship Processing (MDSP)

Replenishment Label Program Name (F20)

Purpose: Use this screen to define the print program used to generate Replenishment Transfer Labels during Primary Location Replenishment.

MSR0053 CHANGE Change System Control Value 4/27/07 13:49:12 Description . : Replenishment Label Program Name System name . . Narrative . . . Replenishment Label Program Name Application . : FUL Applic group . STK Sequence# . . . 1 F3=Exit F12=Cancel

System name: Enter the print program used to generate Replenishment Transfer Labels.

The base print program name is FLR0382.

The system produces replenishment transfer labels when you perform Primary Location Replenishment to help you manage the replenishment transfer process.

Leave this field blank if you do not want to generate replenishment transfer labels during Primary Location Replenishment.

For more information: See:

• Replenish Primary Locations Overview for an overview of the replenish primary locations process.

• Working with Replenishment Control (MSRP) for more information on generating a primary location replenishment.

• Replenishment Transfer Labels to review a sample replenishment transfer label.

Pick Label Print Program (F28)

Purpose: Use this screen to define the print program name the system uses to format pick control labels printed through the Printing Additional Pick Labels (PAPL) menu option.

MSR0053 CHANGE Change System Control Value 3/26/98 10:59:57 Description . : Pick Label Print Program System name . . Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 99 F3=Exit F12=Cancel

System name field: Enter the print program name in this field you want the system to use to format pick control labels printed through Print Additional Pick Labels.

The base pick label print program name is FLR0683.

When you print extra pick control labels, the system updates the Labels field in the Pick Control Header file and creates a PC Manifest Download record in the PC Manifest Download New file (FLMNDL).

You can review the additional pick control labels through Displaying PC Manifest Batches (DPCM).

See Fulfillment Printing Additional Pick Labels (PAPL) for more information on printing additional pick labels.

You can purge unused pick control label records from your system in Purge Unused Pick Control Label Records. See System Operations Purging Unused Pick Control Label Records (PLBS).

Price Ticket Print Program (F46)

Purpose: Use this screen to define the print program the system uses to print price tickets in hanging or label format.

MSR0053 CHANGE Change System Control Value 5/18/98 15:12:14 Description . : Price Ticket Print Program System name . . Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 99 F3=Exit F12=Cancel

System name field: Enter the print program you want the system to use to print price tickets in hanging or label format.

• Price tickets in hanging format are used for items that are stored in a hanging location, such as a suit.

• Price tickets in label format are used for items that are stored on a flat surface, such as shoes.

The base print program, FLR0715, prints price tickets in a format suitable for a Monarch printer. Print program FLR1128 prints price tickets in a format suitable for a Zebra printer.

Note: If you wish to print price tickets on a different printer, you need to verify that the printer prints the correct number of labels.

When is a price ticket generated? The system automatically generates price tickets for items on a retail store order. The system considers an order a retail store order if:

• The Mailorder/retail field for the order type on the order is set to R (retail), and

• The sold to customer on the order represents a retail store (the Warehouse field for the customer contains a warehouse code whose Retail outlet field is set to Y).

However, you can manually create a price ticket for any item at the Create Price Ticket Screen or Create Price Tickets for Order Screen.

When is the price ticket printed? The Generate Price Tickets During Pick Slip Generation (I77) system control value controls when price tickets are printed.

• H = The system prints price tickets in hanging format during pick slip generation for retail store orders.

• L = The system prints price tickets in label format during pick slip generation for retail store orders.

• N or blank = The system does not print price tickets during pick slip generation for retail store orders; instead, the system creates a record in the Price Ticket Work file for each price ticket. You must use the Work with Price Tickets Screen to print the price tickets. At this time, you can select which price ticket format (hanging or label) to print.

The system does not print price tickets if a print program has not been defined:

• An error message displays at the Work with Price Tickets Screen if you select to print price tickets (F21 in Work with Price Tickets) and a print program has not been defined: Price Ticket Print Program SCV (F46) is blank.

• Price tickets do not print during pick slip generation if a price ticket is not defined. Instead, the system creates a record in the Price Ticket Work file for each price ticket.

Leave this field blank if you do not want to print price tickets.

For more information: See:

• Working with Price Tickets (WPTW) for an overview

• Generate Price Tickets During Pick Slip Generation (I77) to print price tickets during pick slip generation

• Hanging Price Ticket for a sample price ticket in hanging format

• Label Price Ticket for a sample price ticket in label format

Batch Item Pull Label Printing Program (F63)

Purpose: Use this screen to define the print program name the system uses to print batch item pull labels during pick slip generation.

MSR0053 CHANGE Change System Control Value 9/16/98 13:28:05 Description . : Batch Item Pull Label Printing Program System name . . Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 99 F3=Exit F12=Cancel

System name: Enter the print program name you wish the system to use to print batch item pull labels during pick slip generation.

When you generate pick slips, the system:

• prints a Batch Item Pull Label for each location/item in the pick slip batch so pickers can attach the label to the picking cart

• sorts the batch item pull labels in location/item sequence within a billing batch

Once the batch pull item labels are attached to the picking cart, the packers can pick from the cart to fulfill each order.

The base batch item pull label print program is FLR0747.

For more information: See Fulfillment Introducing Pick Slip Generation.

Include Bulk Locations in Primary Primary Availability (F87)

Purpose: Use this screen to define whether the system includes the quantity in bulk locations in the available pick quantity for the primary primary location.

MSR0052 CHANGE Change System Control Value 11/05/98 13:45:09 Description . : Include Bulk Locations in Primary, Primary Availability Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter N or leave this field blank if you do not want the system to include the quantity in bulk locations in the available pick quantity for the primary primary location. See the first example for more information on how the system allocates inventory to fulfill the pick quantity.

Let down replenishment: Enter N or leave this field blank if you are using Let Down Replenishment (C36).

Enter Y in this field if you want the system to include the quantity in bulk locations in the available pick quantity for the primary primary location.

In order for the system to include the quantity available in bulk locations in the available pick quantity for the primary primary location:

• the Check Location Quantities During Pick Generation (C54) system control value must be set to Y.

• the bulk location must be non-pickable.

• stock must be available in the primary primary location.

If a bulk location is frozen, the system still includes the quantity in the available pick quantity for the primary primary location; however, if the location is frozen due to a physical inventory, the system does not include the quantity in the available pick quantity for the primary primary location.

When the Check Location Quantities During Pick Generation (C54) system control value is set to Y, the system allocates inventory from the first pickable location with enough stock to satisfy the quantity printed on the pick. If there is not enough stock, the system allocates inventory across multiple pickable locations, beginning with primary, secondary, then bulk locations.

Example: You generate a pick slip for item ABC for a quantity of 75.

The Check Location Quantities During Pick Generation (C54) system control value is set to Y.

Pick slip quantity for item ABC = 75
Location	Quantity	Pickable?	Result
Primary Primary A010101	50	yes	The system allocates 50 units from the primary primary location.
Primary A020202	25	yes	The system allocates 25 units from the primary location.
Secondary A030303	25	no	The system does not allocate inventory from the secondary location.
Bulk A040404	50	no	The system does not allocate inventory from the bulk location.

In this situation, the system allocates 50 units from the primary primary location. Since 50 units from the primary primary location does not fulfill the quantity needed to fulfill the pick slip, the system allocates 50 units from the primary location:

 

50 (units available from primary primary location) + 25 (units available from primary location) = 75 (quantity needed to fulfill the pick slip)

 

If you also have the Include Bulk Locations in Primary Primary Availability system control value set to Y, the system includes the quantity available in the bulk locations in the primary primary location availability. If there is not enough stock in the primary primary location, the system then allocates inventory across multiple pickable locations beginning with primary then secondary locations.

Example: You generate a pick slip for item ABC for a quantity of 75.

The Check Location Quantities During Pick Generation (C54) system control value is set to Y.

The Include Bulk Locations in Primary Primary Availability system control value is set to Y.

Pick slip quantity for item ABC = 75
Location	Quantity	Pickable?	Result
Primary Primary A010101	50	yes	The system allocates 50 units from the primary primary location.
Primary A020202	25	yes	The system does not allocate inventory from this primary location.
Secondary A030303	25	no	The system does not allocate inventory from the secondary location.
Bulk A040404	50	no	The system allocates 25 units from the bulk location.
Bulk A040444	25	no	The system does not allocate inventory form this bulk location.

In this situation, the system includes 25 units in the bulk location A040404 in the quantity available in the primary primary location:

 

50 (units in primary primary location) + 25 (units in bulk location A040404) = 75 (available inventory from primary primary location)

 

In order for the system to pick 75 units from the primary primary location, you must run primary replenishment to transfer the units in the bulk location to the primary primary location.

The system includes the quantity in secondary locations in the available pick quantity for the primary primary location if the Include Secondary Locations in Primary Primary Availability (F88) system control value is set to Y.

Example: You generate a pick slip for item ABC for a quantity of 175.

The Check Location Quantities During Pick Generation (C54) system control value is set to Y.

The Include Bulk Locations in Primary Primary Availability system control value is set to Y.

The Include Secondary Locations in Primary Primary Availability (F88) system control value is set to Y.

Pick slip quantity for item ABC = 175
Location	Quantity	Pickable?	Result
Primary Primary A010101	50	yes	The system allocates 50 units from the primary primary location.
Primary A020202	50	yes	The system allocates 25 units from the primary location.
Secondary A030303	25	no	The system allocates 25 units from the secondary location.
Secondary A030333	25	no	The system allocates 25 units from the secondary location.
Bulk A040444	25	no	The system allocates 25 units from the bulk location.
Bulk A040444	25	no	The system allocates 25 units from the bulk location.

In this situation, the system includes 25 units in the secondary location A030303, 25 units in the secondary location A030333, 25 units in the bulk location A040404 and 25 units in the bulk location A040444 in the quantity available in the primary primary location:

 

50 (units in primary primary location) + 25 (units in secondary location A030303) + 25 (units in secondary location A030333) + 25 (units in bulk location A040404) + 25 (units in bulk location A040444) = 150 (available inventory from primary primary location)

 

Since there is still not enough quantity in the primary primary location to fulfill the pick (175), the system allocates inventory in the primary location to fulfill the pick slip. In this case, the system allocates 25 units from the primary primary location:

 

150 (units available from primary primary location) + 25 (units available from primary location) = 175 (quantity needed to fulfill pick slip)

 

When both the Include Bulk Locations in Primary Primary Availability and Include Secondary Locations in Primary Primary Availability (F88) system control values are set to Y, the system allocates inventory from bulk locations before allocating inventory from secondary locations.

Stock allocation errors: The Withhold Picks due to Item Allocation Error (F04) system control value controls whether the system prints a pick slip for an order when an item on the order creates a stock allocation error.

If this system control value is set to Y, the system does not print a pick slip when an item on the order creates a stock allocation error. A pick slip does not print for any item on the order that prints on the same pick slip as the item that contains the item stock allocation error.

If this system control value is set to N or blank, the system prints a pick slip for items on the order that did not create item stock allocation errors.

For more information: See Fulfillment Introducing Pick Slip Generation.

Include Secondary Locations in Primary Primary Availability (F88)

Purpose: Use this screen to define whether the system includes the quantity in secondary locations in the available pick quantity for the primary primary location.

MSR0052 CHANGE Change System Control Value 11/06/98 16:02:08 Description . : Include Secondary Locations in Primary, Primary Availability Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter N or leave this field blank if you do not want the system to include the quantity in secondary locations in the available pick quantity for the primary primary location. See the first example for more information on how the system allocates inventory to fulfill the pick quantity.

Let down replenishment: Enter N or leave this field blank if you are using Let Down Replenishment (C36).

Enter Y in this field if you want the system to include the quantity in secondary locations in the available pick quantity for the primary primary location.

In order for the system to include the quantity available in secondary locations in the available pick quantity for the primary primary location:

• the Check Location Quantities During Pick Generation (C54) system control value must be set to Y.

• the bulk location must be non-pickable.

• stock must be available in the primary primary location.

If a secondary location is frozen, the system still includes the quantity in the available pick quantity for the primary primary location; however, if the location is frozen due to a physical inventory, the system does not include the quantity in the available pick quantity for the primary primary location.

When the Check Location Quantities During Pick Generation (C54) system control value is set to Y, the system allocates inventory from the first pickable location with enough stock to satisfy the quantity printed on the pick. If there is not enough stock, the system allocates inventory across multiple pickable locations, beginning with primary, secondary, then bulk locations.

Example: You generate a pick slip for item ABC for a quantity of 75.

The Check Location Quantities During Pick Generation (C54) system control value is set to Y.

Pick slip quantity for item ABC = 75
Location	Quantity	Pickable?	Result
Primary Primary A010101	50	yes	The system allocates 50 units from the primary primary location.
Primary A020202	25	yes	The system allocates 25 units from the primary location.
Secondary A030303	25	no	The system does not allocate inventory from the secondary location.
Bulk A040404	50	no	The system does not allocate inventory from the bulk location.

In this situation, the system allocates 50 units from the primary primary location. Since 50 units from the primary primary location does not fulfill the quantity needed to fulfill the pick slip, the system allocates 25 units from the primary location:

 

50 (units available from primary primary location) + 25 (units available from primary location) = 75 (quantity needed to fulfill the pick slip)

 

If you also have the Include Secondary Locations in Primary Primary Availability system control value set to Y, the system includes the quantity available in the secondary locations in the primary primary location availability. If there is not enough stock in the primary primary location, the system then allocates inventory across multiple pickable locations beginning with primary then bulk locations.

Example: You generate a pick slip for item ABC for a quantity of 75.

The Check Location Quantities During Pick Generation (C54) system control value is set to Y.

The Include Secondary Locations in Primary Primary Availability system control value is set to Y.

Pick slip quantity for item ABC = 75
Location	Quantity	Pickable?	Result
Primary Primary A010101	50	yes	The system allocates 50 units from the primary primary location.
Primary A020202	25	yes	The system allocates 25 units from the primary location.
Secondary A030303	50	no	The system allocates 25 units from the secondary location.
Secondary A030333	25	no	The system allocates 25 units from the secondary location.
Bulk A040404	25	no	The system does not allocate inventory from the bulk location.

In this situation, the system includes 25 units in the secondary location A030303 in the quantity available in the primary primary location:

 

50 (units in primary primary location) + 25 (units in secondary location A030303) + 25 (units in secondary location A030333) = 100 (available inventory from primary primary location)

 

In order for the system to pick 75 units from the primary primary location, you must run primary replenishment to transfer the units in the secondary location to the primary primary location. See Warehousing Replenish Primary Locations Overview.

The system includes the quantity in bulk locations in the available pick quantity for the primary primary location if the Include Bulk Locations in Primary Primary Availability (F87) system control value is set to Y.

Example: You generate a pick slip for item ABC for a quantity of 175.

The Check Location Quantities During Pick Generation (C54) system control value is set to Y.

The Include Secondary Locations in Primary Primary Availability system control value is set to Y.

The Include Bulk Locations in Primary Primary Availability (F87) system control value is set to Y.

Pick slip quantity for item ABC = 175
Location	Quantity	Pickable?	Result
Primary Primary A010101	50	yes	The system allocates 50 units from the primary primary location.
Primary A020202	50	yes	The system allocates 25 units from the primary location.
Secondary A030303	25	no	The system allocates 25 units from the secondary location.
Secondary A030333	25	no	The system allocates 25 units from the secondary location.
Bulk A040404	25	no	The system allocates 25 units from the bulk location.
Bulk A040444	25	no	The system allocates 25 units from the bulk location.

In this situation, the system includes 25 units in the secondary location A030303, 25 units in the secondary location A030333, 25 units in the bulk location A040404 and 25 units in the bulk location A040444 in the quantity available in the primary primary location:

 

50 (units in primary primary location) + 25 (units in secondary location A030303) + 25 (units in secondary location A030333) + 25 (units in bulk location A040404) + 25 (units in bulk location A040444) = 150 (available inventory from primary primary location)

 

Since there is still not enough quantity in the primary primary location to fulfill the pick (175), the system allocates inventory in the primary location to fulfill the pick slip. In this case, the system allocates 25 units from the primary location:

 

150 (units available from primary primary location) + 25 (units available from primary location) = 175 (quantity needed to fulfill pick slip)

 

When both the Include Bulk Locations in Primary Primary Availability (F87) and Include Secondary Locations in Primary Primary Availability system control values are set to Y, the system allocates inventory from bulk locations before allocating inventory from secondary locations.

Stock allocation errors: The Withhold Picks due to Item Allocation Error (F04) system control value controls whether the system prints a pick slip for an order when an item on the order creates a stock allocation error.

If this system control value is set to Y, the system does not print a pick slip when an item on the order creates a stock allocation error. A pick slip does not print for any item on the order that prints on the same pick slip as the item that contains the item stock allocation error.

If this system control value is set to N or blank, the system prints a pick slip for items on the order that did not create item stock allocation errors.

For more information: See Fulfillment Introducing Pick Slip Generation.

Hold Invoices for Multi-Recipient Orders (G07)

Purpose: Use this screen to define whether the system holds invoices for multi-recipient orders until all of the pick slips for the order have been confirmed.

MSR0052 CHANGE Change System Control Value 4/12/99 8:02:34 Description . : Hold invoices for multi-recipient orders Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you wish the system to hold invoices for a multi-recipient order until all of the pick slips for the order have been confirmed.

When this system control value is set to Y, the system determines if the pick slip being confirmed is the last pick slip that needs to be confirmed for the multi-recipient order.

If the pick slip is the last pick slip that needs to be confirmed for the order, the system:

• submits all of the pick slips associated with the multi-recipient order to the Billing Async

• places the order in an X (closed) status

• creates an invoice for all of the pick slips associated with the multi-recipient order

If the pick slip is not the last pick slip that needs to be confirmed for the order, the system:

• places the pick slip in a B (billing pending) status until all of the pick slips for the order have been confirmed

• keeps the order in an open status

• does not create an invoice

• writes an order transaction history message indicating that the pick slip has been confirmed

 

Example: A multi-recipient order produces 3 pick slips.

• Pick slip 1 is confirmed on 4/15

• Pick slip 2 is confirmed on 5/09

• Pick slip 3 is confirmed on 5/01

When pick slip 1 is confirmed on April 15th, the system does not submit the pick slip to billing and does not create an invoice since the other pick slips related to the order have not yet been confirmed. The system puts the pick slip that has been confirmed in a B (billing pending) status. The order remains in an open status.

When pick slip 3 in confirmed on May 1st, the system does not submit the pick slip to billing and does not create an invoice since one pick slip related to the order has not yet been confirmed. The system puts the pick slip that has been confirmed in a B (billing pending) status. The order remains in an open status.

When pick slip 2 is confirmed on May 9th, the system submits each pick slip related to the multi-recipient order to the Billing Async, closes the order, and creates an invoice for the pick slips. You can review invoices in order inquiry.

Generating shipment or return notification emails: If the E-mail Shipment/Return Confirmation Notification Immediately (K07) system control value is set to Y, the billing async job generates separate shipment and return notification emails, regardless of the setting of the Hold Invoices for Multi-Recipient Orders system control value. In order to consolidate these email notifications, you need to set the E-mail Shipment/Return Confirmation Notification Immediately (K07) system control value to N and use the Sending Internet Order Ship Confirmation (ESCF) menu option instead.

Enter N or leave this field blank if you do not want the system to hold invoices for a multi-recipient order until all of the pick slips for the order have been confirmed.

When this system control value is set to N or blank, the system submits each pick slip to the Billing Async as each pick slip is confirmed.

Cancel Reason Code for Retail Fulfillment Confirmation (G11)

Purpose: Use this screen to indicate the cancel reason code to use when canceling order lines you have fulfilled by shipping from a retail outlet.

MSR0054 CHANGE Change System Control Value 5/24/99 10:05:16 Description . : Cancel Reason code for Retail Fulfillment confirmation Number . . . . 12 01 02 03 04 05 06 07 10 11 12 13 ... Narrative . . . Application . : FUL Applic group . UNQ Sequence# . . . 10 F3=Exit F12=Cancel

Number field: Enter the cancel reason code to use when you confirm shipment of an item from a retail outlet and cancel the held order line for the item. The cancel reason code is a 2-position, numeric field.

Leave this field blank if you do not use retail fulfillment.

About retail fulfillment: You can use retail fulfillment to ship backordered items from a retail store that has the item in stock. The menu options you use to identify, allocate, and confirm items for retail fulfillment are:

• Submitting the Retail Fulfillment Selection (SFUL): Identifies backordered items that are available in retail stores.

• Working with Retail Fulfillment Selection (RFUL): Allows you to identify the quantity of each item to ship from retail stores and put the order lines on hold, as you are not attempting to fulfill them from your warehouse. You can also sell out items that you cannot fulfill at all.

• Confirming Retail Fulfillment Selection (CFUL): Confirm shipments from retail stores, or remove the hold from order detail lines that you attempt to ship from your warehouse.

When you confirm a shipment from the retail store, the system cancels the order line using the cancel reason code you define here, and writes an order transaction history message. The system does not allow you to confirm a retain shipment if you have not defined a cancel reason here.

For more information:

• retail fulfillment: Fulfillment Retail Fulfillment Overview

• cancel reason codes: Customer Service Establishing Cancel Reason Codes (WCNR)

Load Location into Pick Sequence (G34)

Purpose: Use this screen to indicate whether to load the location code(s) for each pick slip into the Picking sequence array fields of the Pick Sort GH file when you generate pick slips, so that you can use this information for your pick sort program.

MSR0052 CHANGE Change System Control Value 10/19/99 14:17:07 Description . : Load Location into Pick Sequence Yes/No . . . . Y (Y,N) Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 1 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field to have the location code(s) for each item on a pick slip loaded into the Picking sequence array field of the Pick Sort GH file (FLPSGH). You might choose to load the location codes if this information is required by your pick sort program.

Conditions: To load the location codes into the Picking sequence array field, you should also make sure that:

• the Sort Picks by Pick Sequence (E89) system control value is set to Y

• the Check Location Quantities During Pick Generation (C54) system control value is set to Y

• the program defined in the Pick Sort Program Name (C65) system control value supports it (Note: the base sort program, FLR0395, supports the use of this system control value)

Set this field to N or leave it blank if you do not want to load the location code for each item on the pick slip into the Picking sequence array field in the Pick Sort GH file:

• Sort Picks by Pick Sequence (E89) system control value = Y: The Pick sequence number for the location of each item on the pick slip is loaded into the Picking sequence array field instead for use by your pick sort program.

• Sort Picks by Pick Sequence (E89) system control value = N or is blank: The Picking sequence array field in the Pick Sort GH file is not populated during pick slip generation.

Consolidated Replenishment Report Program Name (G49)

Purpose: Use this screen to determine whether you can print the consolidated replenishment detail reports for replenishment control requests created by multiple pick slip generations in a single day.

MSR0053 CHANGE Change System Control Value 8/24/99 9:16:20 Description . : Consolidated Replenishment Report Program name System name . . INR1603 Narrative . . . Application . : FUL Applic group . STK Sequence# . . . 99 F3=Exit F12=Cancel

System name: Enter the consolidated replenishment report program name you want the system to use to print consolidated replenishment reports from Working with Replenishment Control (MSRP).

The base Consolidated Replenishment Report print program is INR1603.

About replenishment reports: When the system creates replenishment requests as a result of pick slip generation (Let-Down replenishment), a separate Replenishment Detail Report is generated for each pick slip generation batch. To print consolidated reports for all replenishment batches performed in a single day, enter Y in the Consolidated report? field for each replenishment batch at Work with Replenish Control and then F21 to print consolidated reports. The system prints these reports:

• Consolidated Replenishment Report by From Location

• Consolidated Replenishment Report by Item/SKU

• Consolidated Replenishment Report By To Location

Related system control values: To print consolidated replenishment reports, three related system control values should contain these settings:

• Let Down Replenishment (C36) must be set to REPORT.

• Check Location Quantities During Pick Generation (C54) must be set to Y.

• Replenish from Location Type (A66) should be set to the type of location you wish to replenish from.

For more information: See Warehousing Replenish Primary Locations Overview.

Use Carousel Interface (G55)

Purpose: Use this screen to define whether the system downloads pick control information to the Carousel system during pick slip generation.

MSR0052 CHANGE Change System Control Value 1/06/00 11:46:15 Description . : Use Carousel Interface Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 150 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to download pick control information to the Carousel system during pick slip generation.

During pick slip generation, the system populates the Carousel Pick Interface Download Detail file with pick control detail information. The file is populated after the Pick Sort GH records are created, but before pick slips are printed. Once all of the carousel pick interface download detail records for a pick control number are created, the system creates a carousel pick interface download header.

Carousel Pick Interface Download files: The system populates the Carousel Pick Interface Download files with pick control detail information for any pick control detail including a location defined as a carousel location. You can define a location as a carousel location by entering C (carousel location) in the Hang/flat field.

The system places the pick control header associated with the pick control detail in an L (waiting for carousel) status. The waiting for carousel status indicates to the system that detail lines associated with this pick control are being printed and picked from a carousel area. The pick control header remains in an L status until the associated pick control detail information is sent back to CWDirect from the Carousel system. Pick generation does not print a pick slip for this pick control number.

Carousel Pick Interface Upload files: Information uploaded from the Carousel system is placed in the Carousel Pick Interface Upload Header file and the Carousel Pick Interface Upload Detail file. The CAROUSEL Async monitors the Carousel Pick Interface Upload files for any carousel pick interface upload information to process.

Enter N or leave this field blank if you do not want the system to send pick control information to the Carousel system during pick slip generation.

For more information: See Warehousing WMS Background Jobs (WPBJ).

Pickable Setting for Analyzing Replenishment Locations (G63)

Purpose: Use this screen to define whether to consider pickable, nonpickable, or either type of location in your main warehouse when determining whether you can fulfill a warehouse replenishment request.

MSR0051 CHANGE Change System Control Value 10/04/99 15:29:29 Description . : Pickable setting for analyzing replenishment locations. Code . . . . . BOTH PICKABLE NONPCKABLE BOTH Narrative . . . Application . : FUL Applic group . STK Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the code that indicates which types of locations to consider when determining whether to allocate stock toward fulfillment of a warehouse replenishment request. Valid values are:

• PICKABLE or blank = Consider only pickable locations

• NONPCKABLE = Consider only nonpickable locations

• BOTH = Consider both pickable and nonpickable locations

Pickable flag: The system checks a location's Pickable flag in determining whether to allocate stock toward a replenishment request. This flag also controls whether you can pick stock from the location for pick slips.

Example: The system is creating a replenishment request for warehouse 25 (the 'To' warehouse) from warehouse 10 (the 'From' warehouse). The item that is required is AB100. This item is stored in location A010101 (pickable) and BULK (nonpickable) in warehouse 10. If this system control value is set to:

• PICKABLE or blank: the system considers only location A010101 when determining whether to allocate stock for the replenishment request

• NONPCKABLE: the system considers only location BULK when determining whether to allocate stock for the replenishment request

• BOTH: the system considers both A010101 and BULK when determining whether to allocate stock for the replenishment request

About warehouse replenishment: You can use the Replenish Warehouses menu option to replenish items to one or more secondary warehouses or outlets. Typically, you replenish from your main warehouse, although you can process replenishments from any warehouse in your company.

There are two types of warehouse replenishment:

• Standard process, in which the system evaluates the replenishment requirement of the 'To' warehouse and allocates stock in the 'From' warehouse based on this inventory information. This process assumes that you maintain inventory information in CWDirect for each warehouse requiring replenishment.

• Outlet transfer process, in which the system allocates stock for a replenishment request based on purchase order information in a file you can upload or populate outside of CWDirect. This process assumes that each 'To' warehouse you are replenishing represents a retail outlet, and that you do not maintain current inventory information for these outlets.

This system control value is used to control both types of warehouse replenishment.

Other system control values: This system control value works in combination with these values in determining whether and where to allocate stock for replenishment requests:

• Type of Location to Search First in Warehouse Replenishment (G64)

• Type of Location to Search Second in Warehouse Replenishment (G65)

• Type of Location to Search Third in Warehouse Replenishment (G66)

For more information: See Warehousing Replenish Warehouses Overview for a description of the processing and setup involved in warehouse replenishment.

Type of Location to Search First in Warehouse Replenishment (G64)

Purpose: Use this screen to indicate the type of location to consider first when determining where to allocate stock for fulfillment of a warehouse replenishment request.

MSR0051 CHANGE Change System Control Value 10/04/99 16:34:48 Description . : Type of location to search first in replenishment. Code . . . . . *PRIMARY *SECONDARY *BULK Narrative . . . Application . : FUL Applic group . STK Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the type of location to search first in determining whether to allocate stock toward a warehouse replenishment request. Valid values are:

• *PRIMARY = search primary locations (type = P) first when determining whether to allocate stock for an item in a replenishment request

• *SECONDARY = search secondary locations (type = S) first when determining whether to allocate stock for an item in a replenishment request

• *BULK = search bulk locations (type = B) first when determining whether to allocate stock for an item in a replenishment request

The system uses this value when evaluation locations within the 'From' warehouse if the item is stored in multiple locations. For example, the system is creating a replenishment request for warehouse 25 (the 'To' warehouse) from warehouse 10 (the 'From' warehouse). The item that is required is AB100. This item is stored in location A010101 (primary), S010101 (secondary) and BULK (bulk) in warehouse 10. This system control value determines which of these locations the system checks first in attempting to allocate stock for the replenishment request.

The system does not attempt to allocate stock from temporary locations (type = T) for warehouse replenishment requests.

Other system control values: This value works with these additional system control values in determining whether to allocate stock toward a replenishment request:

• Pickable Setting for Analyzing Replenishment Locations (G63)

• Type of Location to Search Second in Warehouse Replenishment (G65)

• Type of Location to Search Third in Warehouse Replenishment (G66)

It is not necessary to specify all three of the Type of location to search... system control values if you want to allocate stock for replenishment only from one or two types of locations. For example, if you want to use only bulk locations, you can set the Type of location to search first in replenishment field to *BULK, and leave the Type of Location to Search Second in Warehouse Replenishment (G65) and Type of Location to Search Third in Warehouse Replenishment (G66) fields blank. Similarly, if you want to search only PRIMARY and BULK locations, you might set the Type of location to search first in replenishment field to *PRIMARY, set the Type of Location to Search Second in Warehouse Replenishment (G65) to *BULK, and leave the Type of Location to Search Third in Warehouse Replenishment (G66) blank.

Important: If all three of the Type of location to search... system control values are blank, the system never generates a warehouse replenishment request.

Standard vs. outlet transfer: This system control value is used to control both standard and outlet transfer warehouse replenishment.

About warehouse replenishment: See Warehousing Replenish Warehouses Overview for a description of the processing and setup involved in warehouse replenishment.

Type of Location to Search Second in Warehouse Replenishment (G65)

Purpose: Use this screen to indicate the type of location to consider second when determining where to allocate stock toward fulfillment of a warehouse replenishment request.

MSR0051 CHANGE Change System Control Value 10/04/99 16:56:29 Description . : Type of location to search second in replenishment. Code . . . . . *PRIMARY *PRIMARY *SECONDARY *BULK Narrative . . . Application . : FUL Applic group . STK Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the type of location to search second in determining whether to allocate stock toward a warehouse replenishment request. Valid values are:

• *PRIMARY = search primary locations (type = P) second when determining whether to allocate stock for an item in a replenishment request

• *SECONDARY = search secondary locations (type = S) second when determining whether to allocate stock for an item in a replenishment request

• *BULK = search bulk locations (type = B) second when determining whether to allocate stock for an item in a replenishment request

When processing a warehouse replenishment request, the system checks the location type defined here if it is unable to allocate stock for an item in the location type defined in the Type of Location to Search First in Warehouse Replenishment (G64) system control value.

Other system control values: This value works with these additional system control values in determining whether to allocate stock toward a replenishment request:

• Pickable Setting for Analyzing Replenishment Locations (G63)

• Type of Location to Search First in Warehouse Replenishment (G64)

• Type of Location to Search Third in Warehouse Replenishment (G66)

Important: If all three of the Type of location to search... system control values are blank, the system never generates a warehouse replenishment request.

Type of Location to Search Third in Warehouse Replenishment (G66)

Purpose: Use this screen to indicate the type of location to consider third when determining where to allocate stock toward fulfillment of a warehouse replenishment request.

MSR0051 CHANGE Change System Control Value 10/04/99 17:10:17 Description . : Type of location to search third in replenishment. Code . . . . . *PRIMARY *SECONDARY *BULK Narrative . . . Application . : FUL Applic group . STK Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the type of location to search third in determining whether to allocate stock toward a warehouse replenishment request. Valid values are:

• *PRIMARY = search primary locations (type = P) third when determining whether to allocate stock for an item in a replenishment request

• *SECONDARY = search secondary locations (type = S) third when determining whether to allocate stock for an item in a replenishment request

• *BULK = search bulk locations (type = B) third when determining whether to allocate stock for an item in a replenishment request

When processing a warehouse replenishment request, the system checks the location type defined here if it is unable to allocate stock in the location types defined in the Type of Location to Search First in Warehouse Replenishment (G64) and the Type of Location to Search Second in Warehouse Replenishment (G65) system control values.

Other system control values: This value works with these additional system control values in determining whether to allocate stock toward a replenishment request:

• Pickable Setting for Analyzing Replenishment Locations (G63)

• Type of Location to Search First in Warehouse Replenishment (G64)

• Type of Location to Search Second in Warehouse Replenishment (G65)

Important: If all three of the Type of location to search... system control values are blank, the system never generates a warehouse replenishment request.

Drop Ship Integration Values Screen (H20)

Purpose: Use this screen to indicate whether you use the CWCollaborate Interface or the Locate Supplier Direct Fulfillment Interface to process drop ship orders, and to define the values used to pass information.

About CWCollaborate and Locate: Both CWCollaborate and Locate’s Supplier Direct Fulfillment module provide internet-based, collaborative environments for retailers and vendors to share and process information related to drop ship orders. If you use CWCollaborate or Locate to process drop ship orders for a vendor, your system generates a drop ship purchase order and automatically transmit the purchase order information to the integrated system, where your vendor can access it through a browser window. You must purchase the CWCollaborate application or Locate’s Supplier Direct Fulfillment module.

For more information: See CWCollaborate Interface or Locate Supplier Direct Fulfillment Interface.

System control values and settings at this screen:

• both CWCollaborate and Locate integrations: Use CWCollaborate/Locate (H13)

• CWCollaborate integration:

• Retailer ID (H15)

• Drop Ship Lead Days (H36)

• Communication Protocol (H37)

• FTP ID - Vendor Download (H16)

• FTP ID - PO Download - New (H17)

• FTP ID - PO Download Changes (H35)

• FTP ID - PO Cost Changes (H78)

• FTP ID - PO Updates (H19)

• FTP ID - Cancellation Requests (H18)

• FTP ID - Returns Download - New (H56)

• FTP ID - Return Updates (H58)

• FTP ID - Deleted RAs (H57)

• FTP ID - AP Invoice Upload (H77)

• Locate integration:

• Locate IFS Folder

• System Cd (K50)

• Default Loc (K51)

• .

MSR1253 ENTER Drop Ship Integration Values 1/23/14 11:12:25 EZK Mail Order Use CWCollaborate/Locate . . . . . . Y (Y,N) Retailer ID . . . . . . . . . EGOLF Drop ship lead days . . . . . 14 Communication protocol . . . . FTP (FTP, MQ) FTP ID-Vendor Download . . . . CS1 SEND VENDORS TO CDC FTP ID-PO Download-New . . . . CS2 SEND PURCHASE ORDERS TO CDC FTP ID-PO Download-Changes . . CS5 OUTBOUND PO CHANGES FTP ID-PO Cost Changes . . . . CS0 SEND PO COST CHANGES TO CDC FTP ID-PO Updates . . . . . . CS4 RECEIVE UPDATES FROM CDC FTP ID-Cancel Requests . . . . CS3 SEND CANCEL REQUESTS TO CDC FTP ID-Returns Download-New . CS6 SEND RETURN AUTHS TO CDC FTP ID-Return Updates . . . . CS8 RECEIVE RA UPDATES FROM CDC FTP ID-Deleted RAs . . . . . . CS7 SEND RA CANCELS TO CDC FTP ID-AP Invoice Upload . . . CS9 RECEIVE AP UPDATES FROM CDC Locate IFS Folder System Cd Default Loc /CWJava/Locate/ 27 2 F3=Exit F12=Cancel

Use CWCollaborate/Locate (H13)

Enter Y in this field if you are using CWCollaborate or Locate to process drop ship orders.

This value determines whether:

• You can assign a Drop ship output setting of C (collaborative) or L (Locate drop ship) to a vendor

• The CDC async job in WMS Background Jobs (WPBJ) processes drop ship transactions for your company. Your company must also be flagged as Active.

• You can upload vendors with Drop ship output settings of C (collaborative) or L (Locate drop ship) through Working with Vendor Upload (LVUP).

The CDC background job becomes active only if at least one company in your environment has this system control value set to Y. See Warehousing WMS Background Jobs (WPBJ).

Enter N or leave this field blank if you are not using CWCollaborate or Locate to process drop ship orders.

Retailer ID (H15)

Enter the code you use to identify the retailer within the CWCollaborate data base. This value serves as a key to most of the CWCollaborate files. The Retailer ID is first defined in CWCollaborate, and then entered in this field in CWDirect. This value should not be changed once data has been sent to CWCollaborate.

This is a 10-position, alphanumeric field.

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

Drop Ship Lead Days (H36)

Enter the number of days you want to add to the date passed to CWCollaborate or Locate to calculate the Expected ship date stored in CWDirect for a drop ship purchase order line. If you enter a value in this field, the date passed to CWCollaborate or Locate is: Purchase order creation date + vendor lead days (the Lead days specified for the vendor item). The expected ship date stored in CWDirect is the same.

For more information: See:

• Assign Drop Ship Expected Ship Date (I59) for a list of screens, reports and notices that indicate the expected ship date

• Calculating an Expected Ship Date for CWCollaborate Items or Backorder Card Processing for Locate Items for a discussion of how the expected ship date is calculated

Communication Protocol (H37)

Enter the file transport mechanism you use to transmit information to CWCollaborate. Valid values are FTP or MQ.

File transport mechanisms: CWDirect passes information to CWCollaborate via one of two mechanisms:

• FTP

• IBM WebSphere® MQ¹ Message Queues

Note: CWDirect uses the file transport setting specified for your first CWDirect company in numeric sequence that uses CWCollaborate. For example, if you are using companies 100 and 200 and both use CWCollaborate, the system uses the file transport setting defined for company 100.

If you use FTP as a file transport mechanism, you must define FTP scripts and enter their codes in the appropriate fields of this umbrella system control value. See the FTP ID descriptions below, and Fulfillment Working with FTP Application (WFTP).

If you use WebSphere MQ Messaging, you must install WebSphere MQ on your CWCollaborate application server as well as on your iSeries system; you should configure WebSphere MQ on your CWCollaborate application server before configuring it on your iSeries system. See Fulfillment Working with CWCollaborate Message Queues (WCDC).

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

FTP ID - Vendor Download (H16)

Enter the FTP code which identifies the FTP script used to send vendor information to CWCollaborate. FTP codes are defined using the Working with FTP Application (WFTP) menu option.

A typical FTP script for vendor download would be similar to the following:

*************** Beginning of data *************************************************************************************** 0001.00 administrator money 0002.00 locsite trim 0 0003.00 put cwm95qdta/flcsvd cdc\transfer\oms\rdc\inbox\vendor 0004.00 quit ****************** End of data *************************************************

Note: The command locsite trim 0 addresses the problem of trailing blank truncation in the final field when sending flat files. Since the final field of the Vendor download file is a variable-length field, this command is needed to ensure successful file translation from the flat file format to the XML format required by CWCollaborate.

For more information on FTP scripts, refer to the IBM TCP/IP Configuration Manual.

This is a 3-position, alphanumeric field.

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

FTP ID - PO Download - New (H17)

Enter the FTP code which identifies the FTP script used to send purchase order information to CWCollaborate. FTP codes are defined using the Working with FTP Application (WFTP) menu option.

A typical FTP script for PO download would be similar to the following:

*************** Beginning of data ***************************************************************************************** 0001.00 administrator money 0002.00 append cwm95qdta/flcspo cdc\transfer\oms\rdc\inbox\newpo 0003.00 quit ****************** End of data **************************************************

For more information on FTP scripts, refer to the IBM TCP/IP Configuration Manual.

This is a 3-position, alphanumeric field.

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

FTP ID - PO Download Changes (H35)

Enter the FTP code which identifies the FTP script used to send outbound PO address changes to CWCollaborate. FTP codes are defined using the Working with FTP Application (WFTP) menu option.

A typical FTP script for outbound PO changes would be similar to the following:

*************** Beginning of data ***************************************************************************************** 0001.00 administrator money 0002.00 append qtemp/flcspo cdc\transfer\oms\rdc\inbox\poaddrchg 0003.00 quit ****************** End of data ***************************************************

For more information on FTP scripts, refer to the IBM TCP/IP Configuration Manual.

This is a 3-position, alphanumeric field.

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

FTP ID - PO Cost Changes (H78)

Enter the FTP code which identifies the FTP script used to send PO cost changes to CWCollaborate. FTP codes are defined using the Working with FTP Application (WFTP) menu option.

A typical FTP script for PO cost changes transfer would be similar to the following:

*************** Beginning of data ***************************************************************************************** 0001.00 administrator money 0002.00 append cwm95qdta/flcscc cdc\transfer\oms\rdc\inbox\pocostchg 0003.00 quit ****************** End of data ***************************************************

For more information on FTP scripts, refer to the IBM TCP/IP Configuration Manual.

This is a 3-position, alphanumeric field.

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

FTP ID - PO Updates (H19)

Enter the FTP code which identifies the FTP script used to receive purchase order updates from CWCollaborate. FTP codes are defined using the Working with FTP Application (WFTP) menu option.

A typical FTP script for PO updates transfer would be similar to the following:

*************** Beginning of data ***************************************************************************************** 0001.00 administrator money 0002.00 rename cdc\transfer\oms\rdc\outbox\poupdt cdc\transfer\oms\rdc\outbox\newpoupdt 0003.00 get cdc\transfer\oms\rdc\outbox\newpoupdt cwm95qdta/FLCSFS (replace 0004.00 delete cdc\transfer\oms\rdc\outbox\newpoupdt 0005.00 quit ****************** End of data ***************************************************

For more information on FTP scripts, refer to the IBM TCP/IP Configuration Manual.

This is a 3-position, alphanumeric field.

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

FTP ID - Cancellation Requests (H18)

Enter the FTP code which identifies the FTP script used to send cancellation requests to CWCollaborate. FTP codes are defined using the Working with FTP Application (WFTP) menu option.

A typical FTP script for cancellation request transfer would be similar to the following:

*************** Beginning of data *************************************************************************************** 0001.00 administrator money 0002.00 append cwm95qdta/flcscn cdc\transfer\oms\rdc\inbox\canreq 0003.00 quit ****************** End of data *************************************************

For more information on FTP scripts, refer to the IBM TCP/IP Configuration Manual.

This is a 3-position, alphanumeric field.

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

FTP ID - Returns Download - New (H56)

Enter the FTP code which identifies the FTP script used to send new return or return authorization information to CWCollaborate. FTP codes are defined using the Working with FTP Application (WFTP) menu option.

A typical FTP script for new returns transfer would be similar to the following:

*************** Beginning of data *************************************************************************************** 0001.00 administrator money 0002.00 append cwm95qdta/flcsra cdc\transfer\oms\rdc\inbox\newra 0003.00 quit ****************** End of data *************************************************

For more information on FTP scripts, refer to the IBM TCP/IP Configuration Manual.

This is a 3-position, alphanumeric field.

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

FTP ID - Return Updates (H58)

Enter the FTP code which identifies the FTP script used to receive return information updates from CWCollaborate. FTP codes are defined using the Working with FTP Application (WFTP) menu option.

A typical FTP script for return updates transfer would be similar to the following:

*************** Beginning of data *************************************************************************************** 0001.00 administrator money 0002.00 get cdc\transfer\oms\rdc\outbox\return cwm95qdta/flrart (replace 0003.00 delete cdc\transfer\oms\rdc\outbox\return 0004.00 quit ****************** End of data *************************************************

For more information on FTP scripts, refer to the IBM TCP/IP Configuration Manual.

This is a 3-position, alphanumeric field.

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

FTP ID - Deleted RAs (H57)

Enter the FTP code which identifies the FTP script used to send information about deleted return authorizations to CWCollaborate. FTP codes are defined using the Working with FTP Application (WFTP) menu option.

A typical FTP script for deleted RAs transfer would be similar to the following:

*************** Beginning of data *************************************************************************************** 0001.00 administrator money 0002.00 append cwm95qdta/flcsrc cdc\transfer\oms\rdc\inbox\canra 0003.00 quit ****************** End of data *************************************************

For more information on FTP scripts, refer to the IBM TCP/IP Configuration Manual.

This is a 3-position, alphanumeric field.

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

FTP ID - AP Invoice Upload (H77)

Enter the FTP code which identifies the FTP script used to receive information about updated A/P invoice records from CWCollaborate. FTP codes are defined using the Working with FTP Application (WFTP) menu option.

A typical FTP script for invoice records transfer would be similar to the following:

*************** Beginning of data *************************************************************************************** 0001.00 administrator money 0002.00 get cdc\transfer\oms\rdc\outbox\invoice qtemp/apinup (replace 0003.00 delete cdc\transfer\oms\rdc\outbox\invoice 0004.00 quit ****************** End of data ************************************************

For more information on FTP scripts, refer to the IBM TCP/IP Configuration Manual.

See Working with A/P Invoice Upload Errors (WAPU) for more information on uploading A/P invoices from CWCollaborate.

This is a 3-position, alphanumeric field.

This value is not used by the integration with Locate’s Supplier Direct Fulfillment module.

Locate IFS Folder

The folder path on the Integrated File System where you have installed the interface programs and the cw.properties File, used for integration with Locate’s Supplier Direct Fulfillment module and with Locate’s Order Broker module. If you are logging messages related to the Supplier Direct Fulfillment module or the Order Broker module, the log folder containing the log files is under the Locate IFS folder.

Note: This is not a system control value; instead, your entry for this path updates a data area (CDCDTAARA) and applies to each company in the CWDirect environment.

MICROS recommends an IFS folder path of /CWJava/Locate/. If you require multiple instances of the interface to support different CWDirect environments, such as production and test, then you can create subfolders within the Locate folder.

Typical folder hierarchy is:

• /CWJava/Locate/: Interface programs

• config: cw.properties File

• logs: Log file

Used for the integration with Locate’s Supplier Direct Fulfillment module and with Locate’s Order Broker module.

This path is also available through the Order Broker Values (K15) screen.

Important: The complete IFS folder path plus the name of each required .jar file cannot exceed a length of 1000 positions. In order to prevent a possible issue resulting from a path and .jar file name exceeding the maximum length, use an IFS path that is as short as possible.

This value is not used by the integration with CWCollaborate.

System Cd (K50)

Code field: Use this field to specify the system code identifying your company in Locate for integration with the Supplier Direct Fulfillment module. The system code must be the same as your CWDirect company number, and must be a valid system code for your organization in Locate.

This system code is passed as the requesting_system_cd in all request messages to the Supplier Direct Fulfillment module. For example, if your CWDirect company number is 2, you can set this field to 2 (not 002; omit padding zeroes unless that is how you created the system code in Locate).

Also used for Order Broker integration: This system control value is also used in the integration with Locate’s Order Broker module, and is also available at the Order Broker Values (K15) screen.

Leave this field blank if you do not integrate with Locate.

This value is not used by the integration with CWCollaborate.

Default Loc (K51)

Code field: Use this field to specify the location code identifying your default warehouse in Locate for integration with the Supplier Direct Fulfillment module.

The location code is passed as the requesting_location_cd in the CreateDSOrder message to the Supplier Direct Fulfillment module. This message creates the drop ship purchase order in Locate.

The location code must match an existing location code in Locate for the System Cd (K50).

Also used for Order Broker integration: This system control value is also used in the integration with Locate’s Order Broker module, and is also available at the Order Broker Values (K15) screen.

Leave this field blank if you do not integrate with Locate.

This value is not used by the integration with CWCollaborate.

Refund Freight Default for Inbound Returns (H59)

Purpose: Use this screen to define whether to refund freight charges when processing returns initiated from an outside system such as the CWCollaborate drop ship processing system or a third-party warehouse management system.

MSR0052 CHANGE Change System Control Value 11/06/96 14:14:13 Description . : Refund Freight Default for Inbound Returns Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 999 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to refund freight charges for a return initiated from an outside system when you have not created a return authorization for the merchandise. If a return authorization exists for the merchandise in CWDirect, the system uses the value specified in the Refund freight field of the return authorization to determine whether to refund freight for the merchandise when the return is credited.

Prorating freight refunds: If system control value Prorate Freight Charges (D39) is set to Y, and you are using an order-level freight calculation, freight refunds may be prorated, depending on your freight calculation method. You should test your individual method to determine whether freight refunds are prorated.

System control value Prorate Freight Charges (D39) does not apply to line-level freight calculations.

Example: Freight method is $S (Dollar chart by source), an order-level method. System control values Refund Freight for Inbound Returns and Prorate Freight Charges are both set to Y. A customer orders two units of a drop ship item processed through CWCollaborate. Freight for the order is $5.00. The customer returns one unit to the vendor without calling for a return authorization. Freight charges of $2.50 are refunded on the return.

Example: Freight method is F (Flat rate by order), an order-level method. System control values Refund Freight for Inbound Returns and Prorate Freight Charges are both set to Y. A customer orders two units of a drop ship item processed through CWCollaborate. Freight for the order is $5.00. The customer returns one unit to the vendor without calling for a return authorization. No freight charges are refunded on the return. The customer subsequently returns the second unit of the item. The full freight charge of $5.00 is refunded on the return.

Example: Freight method is OP (Freight by Offer Price), an order-level freight method. System control value Refund Freight Default for Inbound Returns is set to Y.A customer orders two drop ship items processed through CWCollaborate; the offer price for one item is $20.00 and the other is $10.00. The freight charge for up to $25.00 in merchandise is $4.95, and the charge for $25.01 to $50.00 is $5.95. The customer returns the $10.00 item, reducing the total subject to freight from $30.00 to $20.00. The return includes a freight refund of $1.00 ($5.95 - $4.95).

Example: Freight method is I (Freight by Item), a line-level method. System control value Refund Freight Default for Inbound Returns is set to Y.A customer orders two drop ship items processed through CWCollaborate. Freight for the order is $5.00, $3.00 for the first item and $2.00 for the second. The customer returns the first item to the vendor without calling for a return authorization. The return includes freight refund of $3.00.

Enter N or leave this field blank if you do not want to refund freight charges for a return initiated from an outside system when there is no return authorization for the merchandise.

For more information:

• Freight methods: See Marketing Working with Source Codes (WSRC).

• CWCollaborate drop ship processing: See CWCollaborate Interface.

Refund Additional Charge Default for Inbound Returns (H60)

Purpose: Use this screen to define whether to refund additional charges when processing returns initiated from an outside system such as the CWCollaborate drop ship processing system or a third-party warehouse management system.

MSR0052 CHANGE Change System Control Value 11/06/96 14:14:13 Description . : Refund Additional Charge Default for Inbound Returns Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 999 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to refund additional charges for a return initiated from an outside system when you have not created a return authorization for the merchandise. If a return authorization exists for the merchandise in CWDirect, the system uses the value specified in the Refund add'l chgs (Refund additional charges) field of the return authorization to determine whether to refund additional charges for the order when the return is credited. If there were negative additional charges on the order, refunding them results in adding positive additional charges, or decreasing the net amount of the refund.

Enter N or leave this field blank if you do not want to refund additional charges for a return initiated from an outside system when there is no return authorization for the merchandise.

For more information:

• Additional charges: See Customer Service Establishing Additional Charge Codes (WADC).

• CWCollaborate drop ship processing: See CWCollaborate Interface.

Refund Handling Default for Inbound Returns (H61)

Purpose: Use this screen to define whether to refund handling charges when processing returns initiated from an outside system such as the CWCollaborate drop ship processing system or a third-party warehouse management system.

MSR0052 CHANGE Change System Control Value 11/06/96 14:14:13 Description . : Refund Handling Default for Inbound Returns Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 999 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to refund handling charges for a return initiated from an outside system when you have not created a return authorization for the merchandise. If a return authorization exists for the merchandise in CWDirect, the system uses the value specified in the Refund handling field of the return authorization to determine whether to refund handling charges for the order when the return is credited.

Enter N or leave this field blank if you do not want to refund handling charges for a return initiated from an outside system when there is no return authorization for the merchandise.

For more information:

• Handling charges: See Work with Special Handling Screen in chapter 6 of Order Entry.

• CWCollaborate drop ship processing: See CWCollaborate Interface.

Refund Duty Default for Inbound Returns (H62)

Purpose: Use this screen to define whether to refund duty when processing returns initiated from an outside system such as the CWCollaborate drop ship processing system or a third-party warehouse management system.

MSR0052 CHANGE Change System Control Value 11/06/96 14:14:13 Description . : Refund Duty Default for Inbound Returns Yes/No . . . . (Y,N) Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 999 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to refund duty for a return initiated from an outside system when you have not created a return authorization for the merchandise. If a return authorization exists for the merchandise in CWDirect, the system uses the value specified in the Refund duty field of the return authorization to determine whether to refund duty for the order when the return is credited.

Enter N or leave this field blank if you do not want to refund duty for a return initiated from an outside system when there is no return authorization for the merchandise.

For more information:

• Duty: See Customer Service Setting Up the Country File (WCTY).

• CWCollaborate drop ship processing: See CWCollaborate Interface.

Default Return Reason Code for Inbound Returns (H63)

Purpose: Use this screen to identify the return reason code that the system uses when processing returns initiated from an outside system if a valid return reason code is not passed to CWDirect. Outside systems for which you would use this system control value may include the CWCollaborate drop ship processing system or a third-party warehouse management system.

MSR0054 CHANGE Change System Control Value 1/24/02 9:58:32 Description . : Default Return Reason Code for Inbound Returns Number . . . . 001 111 345 555 666 777 888 Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 999 F3=Exit F12=Cancel

Number field: Enter a valid return reason code in this field to specify the return reason code the system uses for a return initiated from an outside system when a valid return reason code is not passed from the outside system and you have not created a return authorization for the merchandise. If a return authorization exists for the merchandise in CWDirect, the system uses the value specified in the Return reason field of the return authorization to assign a return reason when the return is received.

If you do not enter a return reason code in this field, and the system needs a return reason for a return initiated from an outside system, the system uses the first return reason code, sorted numerically, in the return reason code file.

Example:

• You have defined return reason codes 001, 002, 005, 888 and 999 in CWDirect.

• A return from an outside system is uploaded to CWDirect, and there is no return authorization for the return.

• The return from the outside system does not pass any of the defined reason codes.

• You have entered 005 in the Number field of this system control value.

CWDirect assigns reason 005 to the return when it is received.

Example:

• You have defined return reason codes 001, 002, 005, 888 and 999 in CWDirect.

• A return from an outside system is uploaded to CWDirect, and there is no return authorization for the return.

• The return from the outside system does not pass any of the defined reason codes.

• You have not entered any code in the Number field of this system control value.

CWDirect assigns reason 001 to the return when it is received.

For more information:

• Return reason codes: See Customer Service Establishing Return Reason Codes (WRTR).

• CWCollaborate : See CWCollaborate Interface.

Default Additional Charge Code for Inbound Returns (H64)

Purpose: Use this screen to specify whether the system refunds return postage for a return, and to identify the additional charge code that the system uses when adding return postage to a return received from CWCollaborate.

MSR0054 CHANGE Change System Control Value 1/24/02 9:58:32 Description . : Default Additional Charge Code for Inbound Returns Code . . . . BR C CK CS CU D DB D EM EN F ... Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 999 F3=Exit F12=Cancel

Code field: Enter a valid additional charge code in this field to specify the additional charge code used to add return postage, as a negative additional charge, to an order. If you enter a valid additional charge code for this system control value, return postage is added to the order even if the associated line has already been returned.

If you do not enter a valid additional charge code in this field, return postage is not added to an order even if passed to CWDirect from CWCollaborate. However, the return postage passed from CWCollaborate is logged in the Drop Ship Transaction file (FLCSVD) regardless of whether you enter a code in this system control value.

About return postage: If you use the CWCollaborate interface to process drop ship orders, you may allow some vendors to enter return postage for returns, whether the return is initiated from the vendor or pre-authorized in CWDirect and returned against the return authorization. If you enter a valid additional charge code in this system control value, CWDirect adds the return postage passed from the vendor as a negative additional charge on the order, and increases the total of the return by the return postage amount.

Example: Your CWCollaborate vendor has authority to enter return postage and create returns without a return authorization from CWDirect. A customer sends merchandise back to the vendor without first calling for a return authorization. The vendor creates a return and enters return postage of $2.98. CWCollaborate sends the return to CWDirect. If you have entered an additional charge code for the Default Additional Charge Code for Inbound Returns system control value, CWDirect adds an additional charge of -$2.98 to the order, and increases the total of the return by $2.98. If you have not entered an additional charge code for this system control value, CWDirect does not add a negative additional charge to the order or increase the customer’s refund, but does log the amount in the Drop Ship Transaction file.

Example: Your CWCollaborate vendor has authority to enter return postage. A customer has called to inform you she is returning merchandise. You have decided to send an immediate refund to the customer, without waiting to receive the merchandise, so you have processed a complete return (entered, received, and credited) for the merchandise. The return is still sent to the vendor via the CWCollaborate interface, and when the vendor receives the merchandise he adds return postage of $2.98 to the return. When the vendor’s return information is passed to CWDirect, the customer’s order is updated with a negative additional charge of -$2.98 if you have entered an additional charge code for the Default Additional Charge Code system control value. The system creates another invoice for the customer’s order to refund the return postage. If you have not entered an additional charge code for this system control value, CWDirect does not add a negative additional charge to the order or increase the customer’s refund, but does log the amount in the Drop Ship Transaction file.

For more information:

• Additional charge codes: See Customer Service Establishing Additional Charge Codes (WADC)

• CWCollaborate : See CWCollaborate Interface.

Default Return Disposition Code for Inbound Returns (H65)

Purpose: Use this screen to identify the return disposition code that the system uses when processing returns initiated from an outside system such as the CWCollaborate drop ship processing system or a third-party warehouse management system.

MSR0051 CHANGE Change System Control Value 1/24/02 14:50:50 Description . : Default Return Disposition Code for Inbound Returns Code . . . . . 1N IN RB RP RW TT 1N 1Y 3R 4A 4B 50 Narrative . . . Application . : C/S Applic group . REF Sequence# . . . 999 F3=Exit F12=Cancel

Code field: Enter a valid return disposition code in this field to specify the return disposition code the system uses for a return initiated from an outside system when you have not created a return authorization for the merchandise. If a return authorization exists for the merchandise in CWDirect, the system uses the value specified in the Disposition code field of the return authorization to assign a return disposition code when the return is received.

If you do not enter a return disposition code in this field, and the system needs one to process a return created without a return authorization, the system uses the first return disposition code, sorted alphanumerically, in the return disposition code file.

Example:

• You have defined return disposition codes 1N, 2R, 30, 40, and AA in CWDirect.

• A return from an outside system is uploaded to CWDirect, and there is no return authorization for the return.

• You have entered 40 in the Code field of this system control value.

CWDirect assigns disposition code 40 to the return when it is received.

Example:

• You have defined return reason codes 1N, 2R, 30, 40 and AA in CWDirect.

• A return from an outside system is uploaded to CWDirect, and there is no return authorization for the return.

• You have not entered any code in the Code field of this system control value.

CWDirect assigns reason 1N to the return when it is received.

About return disposition codes: The return disposition code identifies how a returned item is handled by the system, in terms of whether the return updates inventory and the warehouse and location to which the item is returned. If the disposition code is set up to affect inventory and return to the primary location, the system checks for a primary location in the Item record. If one is available, the system returns the item automatically to this warehouse location. If one is not available or if the disposition code is not set up to receive returns in the primary location, the system creates a receive the return in the warehouse and location defined in the Return Disposition record. If the item/location does not exist, the system creates a record in the Item/Location file automatically.

Affect inventory? When you accept a return for drop ship merchandise and assign the return a disposition code that affects inventory and returns the merchandise to a pickable location, the merchandise is available and reserved on the next order for which you have enough inventory to reserve the order line. The system does not create a drop ship purchase order for the reserved merchandise when you process drop ship orders through the Maintain Drop Ship Orders (MDSP) menu option; instead, the reserved order line is processed when you generate pick slips for the order.

User and user class authority to return disposition values: User and user class authority settings do not affect returns initiated from an outside system.

For more information:

• Return disposition codes: See Customer Service Establishing Return Disposition Values (WRDV).

• CWCollaborate : See CWCollaborate Interface.

Generate Invoice Number at Pick Gen (H80)

Purpose: Use this screen to indicate whether to assign pending invoice numbers to qualifying orders at pick slip generation.

MSR0052 CHANGE Change System Control Value 3/11/02 9:50:06 Description . : Generate invoice number at Pick Gen Yes/No . . . . Y (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want the system to assign a pending invoice number provided:

• the order does not use a permanent ship-to address (added by pressing F7)

• a bill-to customer with an identical name and address is associated with the sold-to customer

Note: An order ship-to, added by pressing F14, or a recipient customer, added by pressing F2, does not prevent the invoice number assignment.

The system uses the Pending invoice number field in the Pick Control Header file (FLPCTH).

Billing: When you bill the order, the system uses the pending invoice number to create the Invoice Header record. Also, the system uses the billing date as the Invoice print date, so that the invoice does not print when you choose to print Unprinted invoices in Printing Invoices (PINV).

Note: The invoice number prints on the pick slip only if your unique pick slip printing program supports it.

The system does not consolidate invoice numbers that were assigned at pick slip generation, regardless of the setting of the Consolidated Invoice (B49) system control value.

Void/reprint: When you void and reprint a pick slip that has a pending invoice number, the system assigns a new invoice number; the system does not evaluate the order or customer at this time to verify that the order still qualifies for pending invoice number assignment.

Enter N or leave this field blank if you do not want the system to assign pending invoice numbers at pick slip generation.

Prefix of Identcode (I28)

Purpose: Use this screen to identify the prefix to assign pick slip identcodes for shipments in Germany.

MSR0054 CHANGE Change System Control Value 7/09/03 13:56:19 Description . : Prefix of Identcode Number . . . . 83367 Narrative . . . Application . : FUL Applic group . PCK Sequence# . . . 999 F3=Exit F12=Cancel

Number field: Enter the prefix to use when assigning identcodes to pick slips. An identcode is a used to generate a bar code for parcel shipment in Germany, and is composed of the prefix that you specify here, concatenated with the six-position suffix, which is sequentially assigned by the system. The Identcode number assignment (A73) tracks the next available identcode suffix.

Example: The Prefix of Identcode system control value is set to 83367, and the next available number for the Identcode number assignment is 123. The identcode for the next pick slip is 83367000123.

Where is the identcode used? The system writes an order transaction history message, such as PICK 0010137 IDENTCODE 83367000022, for each identcode that prints on a pick slip. You can review these messages at the Display Order History Screen in order inquiry.

Note: The identcode prints on pick slips only if your pick slip printing program, specified through Pick Printing Program (C37), supports it. The base program that supports printing the identcode is FLR1106. If you use a pick printing program that does not support the identcode, the system does not write the order transaction history message or update the number assignment.

What if a pick slip has multiple pages? The system assigns a unique, sequential identcode suffix to each page of the pick slip. If the order generates multiple pick slips, each successive pick slip is also assigned a unique, sequential suffix.

Specifying the identcode suffix at pick slip generation: If you use this system control value to specify an identcode prefix, when you generate pick slips the system displays a pop-up window prompting for the next identcode suffix to use. The next available identcode, based on the Identcode number assignment, defaults, but you can override it.

Leave this system control value blank if you do not want to use the identcode for shipments in Germany. When you generate pick slips, the system does not prompt for the next identcode suffix, and does not write the order transaction history message.

For more information: See:

• generating pick slips and specifying the identcode suffix number: Generating Pick Slips for Reserved Stock

• creating or resetting the suffix number assignment: Setting Up the Number Assignment File (WNUM)

• reviewing the identcode in order inquiry: Display Order History Screen

Use Alternate Zone Reservation Logic (I52)

Purpose: Use this screen to indicate whether to use standard or alternate zone reservation rules for reserving and shipping weather-sensitive items, such as plant stock, if you do not currently have the items in inventory.

MSR0052 CHANGE Change System Control Value 12/19/03 13:44:10 Description . : Use Alternate Zone Reservation Logic Yes/No . . . . Y (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want to use alternate zone reservation rules. You might use these rules if:

• there is little likelihood that you will be able to fulfill a zone reservation order once the season starts if you do not currently have an available quantity or an open PO quantity for an item

• you should be able to fulfill a zone reservation order within the zone reservation dates as long as there is an open PO for the item

Under alternate rules, the system always presents the Select Order Line Option Window after the season Start date if there is no available quantity or open PO quantity for an item. You can use this window to sell out the order line, or to add the item as a future order line with the Next season open date as the order line’s Arrival date, meaning that the system would not attempt to reserve or ship the item until that date.

Also, if this value is set to Y, the system does not consider the Deferred cutoff date when determining whether to present the Select Order Line Option Window if there is no available quantity for an item but there is an open PO quantity. Instead, the system adds the order line as a zone reservation item with the current date as the Arrival date.

Enter N or leave this field blank if you do not want the system to use alternate zone reservation rules. The system uses the standard zone reservation rules, which treats items the same way if there is no available quantity, regardless of whether there is an open PO quantity or not. For example, the system does not display the Select Order Line Option Window after the season start date, and simply adds the item to the order as a zone reservation item using the current date as the Arrival date. Also, the system does present the Select Order Line Option Window if there is no available quantity for an item but there is an open PO quantity after the Deferred cutoff date.

Order Control Summary Shipment Update Method (I55)

Purpose: Use this screen to define how the system updates the # Orders shipped field in the Order Control Summary file.

MSR0051 CHANGE Change System Control Value 2/04/04 8:52:11 Description . : Order Control Summary Shipment Update Method Code . . . . . ORDERS INVOICES PICKS Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the code that represents how you wish the system to update the # Orders shipped field in the Order Control Summary file.

You can review the # Orders shipped field at the First Operations Control Summary Screen.

Valid codes are ORDERS, INVOICES, or PICKS.

Important: If you track orders that match the Fulfillment Order Type (J36) separately, you need to have the Order Control Summary Shipment Update Method system control value set to ORDERS in order for the shipment totals to be correct.

ORDERS Order Control Summary Shipment Update Method

When the Order Control Summary Shipment Update Method (I55) system control value is set to ORDERS or blank, the system updates the # Orders shipped field when the Billing Async updates the status of an order to closed.

The Orders shipped total includes:

• Shipped orders, including drop ship orders, confirmed; the system does not update the # Orders shipped until all of the units on the order are confirmed, soldout, or cancelled.

• A single order with multiple pick slips (for example, for ship alone items) updates the # Orders shipped by 1.

• An order that includes a pre-billable item does not update the # Orders shipped when the Pre Billed Amount Item (J72) bills.

• An order with multiple recipients updates the # Orders shipped by the number of recipients. For example, an order with 2 ship-to customers updates the total by 2.

• Orders which include only non-inventory items, gift certificate items, membership items, or virtual stored value card items; the system updates the total once the order is processed through billing.

• Express bill orders.

The Orders shipped total does not include:

• Orders which include only soldout items.

• Returns processed as negative quantities in order entry. Note: If the order also contains a regular item, the system includes the order in the Orders shipped total once all of the regular items on the order are confirmed.

INVOICES Order Control Summary Shipment Update Method

When the Order Control Summary Shipment Update Method (I55) system control value is set to INVOICES, the system updates the # Orders shipped field when the Billing Async creates an invoice for an order, excluding credit invoices.

The Orders shipped total includes:

• Invoices for an order, excluding credit invoices.

• A single order with multiple invoices updates the # Orders shipped by the number of invoices created. For example, an order with 2 invoices updates the total by 2.

• An order with multiple recipients updates the # Orders shipped by the number of invoices created for each ship to. For example, an order with 2 ship-to customers, each ship to producing 2 invoices, updates the total by 4.

• If you use Consolidated Invoice (B49), the system counts a consolidated invoice as one invoice, regardless of how many separate shipments are processed through billing.

• Express bill orders and drop ship orders since an invoice is still created.

• Orders which include only non-inventory items, gift certificate items, membership items or virtual stored value card items since an invoice is still created.

The Orders shipped total does not include:

• Orders which include only soldout items since an invoice is never created.

• Returns processed as negative quantities in order entry since the invoice created is a credit. Note: If the order also contains a regular item, the system includes the order in the Orders shipped total once an invoice is created for the regular item.

PICKS Order Control Summary Shipment Update Method

When the Order Control Summary Shipment Update Method (I55) system control value is set to PICKS, the system updates the # Orders shipped field when the Billing Async processes a pick control number for an order.

The Orders shipped total includes:

• Pick control numbers confirmed for an order.

• A single order with multiple pick control numbers updates the # Orders shipped by the number of pick control numbers confirmed through billing. For example, a pick was generated for a ship alone item and another pick was generated for all other items. The system generates a separate pick control number whenever an order is split into several pick slips; see Splitting an Order for more information on the reasons an order is split into several pick slips.

• An order with multiple recipients updates the # Orders shipped by the number of pick control numbers generated and confirmed for each ship to. For example, an order with 2 ship-to customers, each ship to has 2 pick control numbers confirmed, updates the total by 4.

• Orders which include only non-inventory items or drop ship items since a pick control number is still generated.

The Orders shipped total does not include:

• Pick labels that are scanned and sent to billing since they do not contain any detail lines.

• Express bill orders since a pick control number is not generated.

• Returns processed as negative quantities in order entry since a pick control number is not generated. Note: If the order also contains any regular item, the system includes the order in the Orders shipped total once the pick control number(s) associated with the regular item(s) is processed by billing.

• Orders which include only sold out items, gift certificate items, membership items, or virtual stored value card items since a pick control number is not generated.

For more information: See:

• Reviewing Operations Control Summary (FLSH) to review order and merchandising summary information for a selected date.

• Updates During Background Processing for more information on the updates the Billing Async performs.

Minimum Item Price Eligible for Retail Pick Ticket (I76)

Purpose: Use this screen to indicate the threshold unit selling price for generating retail fulfillment pick slips for items on orders.

MSR0056 CHANGE Change System Control Value 5/17/04 12:15:03 Description . : Minimum Item Price Eligible for Retail Pick Ticket Dollar amount . Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Dollar amount: Enter the highest unit selling price that should not generate a pick slip in retail fulfillment. Only order detail lines with unit prices higher than your entry are eligible for retail fulfillment. Order detail lines with unit prices equal to or less than your entry are not eligible for retail fulfillment. You might want to use this value to avoid the extra expense of retail fulfillment for order lines below a given value.

Example: Set this value to 4.99 to avoid generating retail pick slips for any order detail lines with unit selling prices of less than $5.00.

Which price? The system uses the actual selling price of a single unit of the item to determine whether to generate the retail pick, or the ODT price field in the Order Detail file. This price reflects discounting or repricing applied to the order line itself; however, it does not reflect an discounts applied to the order as negative additional charges.

Multiple units: The system compares the single unit price of the item with the setting for this system control value, not the extended price of the order line. For example, if you set this value to 3.00 and there are two units of the item priced at $2.50 each for an extended price of $5.00, the order line is still excluded based on the unit price being lower than the system control value.

Leave this value set to blank, or zero, if you do not want to exclude any items from retail fulfillment based on unit selling price, or if you do not use retail fulfillment.

For more information: See Retail Fulfillment Overview.

Generate Price Tickets During Pick Slip Generation (I77)

Purpose: Use this screen to indicate if the system generates price tickets during pick slip generation for retail store orders.

MSR0051 CHANGE Change System Control Value 5/18/04 15:37:53 Description . : Generate Price Tickets During Pick generation Code . . . . . H L N Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter a code to indicate if the system generates price tickets during pick slip generation for retail store orders.

Identifying retail store orders: The system considers an order a retail store order if:

• The Mailorder/retail field for the order type on the order is set to R (retail), and

• The sold to customer on the order represents a retail store (the Warehouse field for the customer contains a warehouse code whose Retail outlet field is set to Y).

Valid values are:

• H = The system prints price tickets in hanging format during pick slip generation for retail store orders. A Hanging price ticket is used for items that are stored in a hanging location, such as a suit.

• L = The system prints price tickets in label format during pick slip generation for retail store orders. A Label price ticket is used for items that are stored on a flat surface, such as shoes.

• N or blank = The system does not print price tickets during pick slip generation for retail store orders; instead, the system creates a record in the Price Ticket Work file for each price ticket. You must use the Work with Price Tickets Screen to print the price tickets. At this time, you can select which price ticket format (hanging or label) to print.

The system uses the print program defined in the Price Ticket Print Program (F46) system control value to print the price tickets. If a print program is not defined, the system does not print price tickets during pick slip generation and instead, creates records in the Price Ticket Work file. See Hanging Price Ticket and Label Price Ticket for sample price tickets in hanging format and label format.

Note: If this system control value is set to H or L, the system automatically generates the price tickets during pick slip generation and clears the Price Ticket Work file of any other price ticket records; price tickets printed during pick slip generation does not display on the Work with Price Tickets Screen and any other price tickets that existed in the work file no longer display.

Leave this field blank if you do not wish to generate price tickets for retail store order during pick slip generation. You can still create price tickets using the Working with Price Tickets (WPTW) menu option.

For more information: See Working with Price Tickets (WPTW) for an overview.

Use Inventory Sharing Backorder Evaluation (I80)

Purpose: Use this screen to indicate whether to reserve backorders strictly according to backorder priority and order age, or to reserve orders in the shared company (where you actually maintain the inventory) first.

MSR0052 CHANGE Change System Control Value 7/15/04 11:04:50 Description . : Use Inventory Sharing Backorder Evaluation? Yes/No . . . . N (Y,N) Narrative . . . Application . : FUL Applic group . RSV Sequence# . . . 999 F3=Exit F12=Cancel

Yes/no field: Enter Y in this field if you want to reserve backorders across all companies that share inventory based strictly on B/O priority and age, regardless of the company where the order was taken. When evaluating order detail lines across all sharing companies, the system checks the information in the Order Detail file, and uses the following hierarchy:

1. Select the order detail line with the highest B/O priority.

2. If there is more than one order detail line with this B/O priority, select the line with this priority and the earliest entered date and entered time.

The EBO_ASYNC background job performs backorder evaluation and reservation; see Working with the EBO_ASYNC Job.

About B/O priority: B/O priority is a one-position, numeric field. An order line with a priority of 9 should be reserved first, and an order line with a priority of zero should be reserved last.

The B/O priority defaults to the order detail line from the order header if a priority is specified on the order header. Similarly, the B/O priority defaults to the order header from the source code, if a priority is specified for the source code. You can override the B/O priority at any of these levels.

Entered date and time determined how? The earliest entered date and time are based on when the item was first added to the order, either in order entry or order maintenance, and so are not necessarily the same as the date and time that the order was first entered. The entered date and time are not updated when you update an existing order detail line.

Note: If you use inventory sharing and would like to use the hierarchy described above when reserving backorders, set this value to Y in the shared company (that is, the one where you actually maintain the inventory). Leave this value set to N in each company that shares the inventory.

Enter N or leave this field blank if you want to reserve backorders first within the shared company (that is, the one where you actually maintain the inventory), and then within sharing companies. The system uses the same logic as described above, except that it reserves all backorders first within the shared company, and then begins to evaluate additional sharing companies only after all backorders in the first company are reserved.

Note: The EBO_ASYNC background job reserves backordered order detail lines based on changes in inventory levels, such as receiving purchase orders. If this system control value is set to Y, the system writes a single EBO_ASYNC data queue record for the shared company (the company where you actually track the inventory) when reserving any backorders, regardless of how many backorders are being reserved and in which companies. If this system control value is set to N, the system writes a separate EBO_ASYNC data queue record for each company where it reserves a backorder. See the Display Evaluate B/O Data Queue Screen for more information on reviewing EBO_ASYNC data queue records.

For more information: See Inventory Sharing (A69).

Confirm Reprint of Pick Tickets from WMS (J32)

Purpose: Use this screen to define whether the system reprints and immediately bills a pick slip when a partial warehouse backorder is received from a warehouse management system.

MSR0052 CHANGE Change System Control Value 2/07/06 8:21:14 Description . : Confirm Reprint of Pick Tickets from WMS Yes/No . . . . (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 reprint and immediately bill a pick slip when a partial warehouse backorder is received from a warehouse management system.

Enter N or leave this field blank if you want the system to reprint and send a new pick slip to the warehouse management system when a partial warehouse backorder is received from a warehouse management system. The system does not bill the pick slip until a shipment confirmation is received from the warehouse management system.

Overview: When you receive shipment confirmations from a warehouse management system, CWDirect bills the customer on the order and creates an invoice.

However, if the warehouse management system cannot ship the number of units of the item requested on the pick slip, the WMS sends a shipment confirmation to CWDirect identifying a warehouse backorder.

A Partial warehouse backorder exists if some of the items on the pick slip are not available in the warehouse to pick and ship to the customer. In this situation, CWDirect voids and unreserves the units that are not available and looks at the Confirm Reprint of Pick Tickets from WMS (J32) system control value to determine how to process the new pick slip:

If the Confirm Reprint of Pick Tickets from WMS (J32) system control value is set to Y, CWDirect:

• Voids and unreserves the units that are not available.

• Reprints the pick slip.

• Does not send the pick slip to the warehouse management system. Instead, CWDirect immediately bills the customer and creates an invoice.

If the Confirm Reprint of Pick Tickets from WMS (J32) system control value is set to N, CWDirect:

• Voids and unreserves the units that are not available.

• Reprints the pick slip.

• Sends the pick slip to the warehouse management system. The warehouse management system sends a shipment confirmation back to CWDirect at a later time, indicating when to bill the customer and create an invoice.

Example: The following example explains the processing that occurs when a shipment confirmation including a partial warehouse backorder is received from the warehouse management system, based on the setting of the Confirm Reprint of Pick Tickets from WMS (J32) system control value.

SCV J32 is Y	SCV J32 is N
Original pick slip: The original pick slip sent to the WMS contains the following information:
Pickticket control number: 2509 Pickticket number: 5210 Order number: 8538 Total number of units: 3 Item: 20061 Original order quantity: 3 Original pickticket quantity: 3 Pickticket quantity: 3	Pickticket control number: 2506 Pickticket number: 5204 Order number: 8534 Total number of units: 3 Item: 20061 Original order quantity: 3 Original pickticket quantity: 3 Pickticket quantity: 3
Shipment confirmation: The shipment confirmation received from the WMS contains the following information:
• Pickticket control number: 2509 • Pickticket number: 5210 • Order number: 8538 • Pickticket line number: 1 • Item: 20061 • Pickticket quantity: 3 • Shipped quantity: 2	• Pickticket control number: 2506 • Pickticket number: 5204 • Order number: 8534 • Pickticket line number: 1 • Item: 20061 • Pickticket quantity: 3 • Shipped quantity: 2
PkMS Billing Async: When the PkMS Billing Async processes the shipment confirmation, the system:
Voids pick control number 5210 and reprints the pick slip for the shipped quantity, using the next available pick control number (5211). You can review the pick slips for the order on the Display Pick Tickets for Order screen.	Voids pick control number 5206 and reprints the pick slip for the shipped quantity, using the next available pick control number (5207). You can review the pick slips for the order on the Display Pick Tickets for Order screen.
Changes the printed quantity on the reprinted pick slip to match the shipped quantity (2) received from the warehouse management system. Unreserves the backordered quantity (1) on the order line.	Changes the printed quantity on the reprinted pick slip to match the shipped quantity (2) received from the warehouse management system. Unreserves the backordered quantity (1) on the order line.
Creates order transaction history messages: Order Line 1 unrsv'd w/BO qty of 1. Pick 5208 reprinted as pick 5209.	Creates order transaction history messages: Order Line 1 unrsv'd w/BO qty of 1. Pick 5204 reprinted as pick 5205.
Creates a record in the WMS Backordered Pick Work file. The record indicates the company where the pick slip was voided and the pick ticket number for the pick slip that was voided. Note: The system purges records in the WMS Backordered Pick Work file when you run the Purge WMS Inbound Files periodic process (program name PKR0207) to purge invoice records. See Number of Days to Purge WMS Inbound Files (H48) for more information.	Creates a record in the PkMS Pick Ticket Header file. The record indicates the old pick control number and the new pick control number. • Pickticket control number: 2506 • Pickticket number: 5205 • Order number: 8534 • Total number of units: 2
Creates records in the PkMS Invoice Header, PkMS Invoice Detail, PkMS Invoice Carton Header, and PkMS Invoice Carton Detail files for the new pick control number and the information provided in the voided pick control number.	Sends the new record in the PkMS Pick Ticket Header file to the WMS.
Bills and creates an invoice for the order using the new pick control number.	Does not bill the order until a shipment confirmation for the reprinted pick slip is received from the WMS.

Note: A Full warehouse backorder exists if none of the items on the pick slip are available in the warehouse to pick and ship to the customer. In this situation, CWDirect voids and unreserved the entire pick slip, regardless of the setting of the Confirm Reprint of Pick Tickets from WMS (J32) system control value.

For more information: See Receiving Shipment Confirmations from a Warehouse Management System.

QuickPick Zone Identifier (J41)

Purpose: Use this screen to define whether the system performs QuickPick Zone processing. The value you enter in this field represents the zone the system treats as the QuickPick zone during pick slip allocation and printing.

MSR0051 CHANGE Change System Control Value 3/27/06 9:22:02 Description . : QuickPick Zone Identifier Code . . . . . Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter a code in this field for the zone the system treats as the QuickPick Zone during pick slip allocation and printing. Entering a zone in this field indicates the system performs QuickPick Zone processing.

Leave this field blank if you do not want to use QuickPick Zone Processing.

Identifying the zone: The code you enter in this field must represent a valid zone for a location. This is the Zone field in the Location file, as displayed in the Zone field for a location record in Creating and Maintaining Locations (WLOC).

Typically, the Zone field displays as the first character of the Location field for a location record. However, the first character of the Location field does not have to represent the zone.

Note: The system does not validate that the code you enter in this field is a valid zone; however, if you enter a code that is not a valid zone, the system never performs QuickPick Zone processing.

The system considers all other zones that do not match the zone defined in the QuickPick Zone Identifier (J41) system control value as regular, or non-QuickPick, zones. For example, if zone A is defined as the QuickPick zone, zones B, C, D, etc. are considered regular, non-QuickPick, zones.

Quickpick zone setup for set and non-inventory items: In order for QuickPick zone processing to work correctly, you should perform the following setup for your set items and non-inventory items.

• Set items (Kit type S): In order to pick a set item from both inside and outside the QuickPick zone, you must create two “fake” item locations for the set header: one item location inside the QuickPick zone, and one item location outside the QuickPick zone. A primary primary location does not need to be setup. If the set item is only available inside the QuickPick zone, then create one “fake” item location for the set header inside the QuickPick zone; if the set item is only available outside the QuickPick zone, then create one “fake” item location for the set header outside the QuickPick zone.

• Non-inventory items: For each of your non-inventory items, create two “fake” item locations: one item location inside the QuickPick zone, and one item location outside the QuickPick zone. A primary primary location does not need to be setup.

QuickPick Zone Processing

When you generate a pick slip and a zone is defined in the QuickPick Zone Identifier (J41) system control value, the system performs the following steps.

1. The system tries to allocate all of the reserved items on the order from the QuickPick zone.

If the item has multiple item/locations in the QuickPick zone, the system allocates the inventory in the pickable location with enough inventory to fill the line, searching the locations in the following sequence:

• Allocate the inventory from the primary primary location.

• If the primary primary location does not have enough inventory to fill the line (or the primary primary location is not part of the QuickPick zone), allocate the inventory from the first pickable location in alphabetical sequence in the QuickPick zone that has enough inventory to fill the line. The system first searches all pickable primary locations and then searches pickable secondary and bulk locations.

• If no location in the QuickPick zone has enough inventory to fill the line, allocate the inventory across pickable locations in the QuickPick zone.

• If all pickable locations in the QuickPick zone do not have enough inventory to fill the line:

• If Let Down Replenishment is enabled, move stock from other locations to fill the required quantity.

• If Let Down Replenishment is not enabled or the system cannot allocate all of the reserved items on the order from the QuickPick zone, continue to the next step.

2. The system tries to allocate all of the reserved items on the order from non-QuickPick zones.

If the item has multiple item/locations in the non-QuickPick zones, the system allocates the inventory in the pickable location with enough inventory to fill the line, searching the locations in the following sequence:

• Allocate the inventory from the primary primary location.

• If the primary primary location does not have enough inventory to fill the line (or the primary primary location is part of the QuickPick zone), allocate the inventory from the first pickable location in alphabetical sequence in the non-QuickPick zones that has enough inventory to fill the line. The system first searches all pickable primary locations and then searches pickable secondary and bulk locations.

• If no location in the non-QuickPick zones has enough inventory to fill the line, allocate the inventory across pickable locations in the non-QuickPick zones.

• If all pickable locations in the non-QuickPick zones do not have enough inventory to fill the line:

• If Let Down Replenishment is enabled, move stock from other locations to fill the required quantity.

• If Let Down Replenishment is not enabled or the system cannot allocate all of the reserved items on the order from non-QuickPick zones, continue to the next step.

3. The system tries to allocate the reserved items on the order from a pickable item/location in any zone.

The system allocates the reserved item, regardless of whether the item/location is in the QuickPick zone or in a non-QuickPick zone.

If the item has multiple item/locations across all zones, the system allocates the inventory in the pickable location with enough inventory to fill the line, searching the locations in the following sequence:

• Allocate the inventory from the primary primary location.

• If the primary primary location does not have enough inventory to fill the line, allocate the inventory from the first pickable location in alphabetical sequence that has enough inventory to fill the line. The system first searches all pickable primary locations and then searches pickable secondary and bulk locations.

• If no location has enough inventory to fill the line, allocate the inventory across pickable locations, regardless of zone.

• If all pickable locations do not have enough inventory to fill the line:

• If Let Down Replenishment is enabled, move stock from other locations to fill the required quantity.

• If Let Down Replenishment is not enabled, print the item on the Item Stock Allocation Error Report, based on the setting of the Withhold Picks due to Item Allocation Error (F04) system control value.

Note: In order to perform QuickPick Zone processing, the Check Location Quantities During Pick Generation (C54) system control value must be set to Y.

Separating QuickPick Pick Slips from Regular Pick Slips

If FLR1150 or FLR1157 is defined in the Pick Printing Program (C37) system control value, the system creates a separate spool file for pick slips that contain items allocated from the QuickPick zone.

• Spool file QUICKZONE contains pick slips with all lines allocated from the QuickPick zone.

• Spool file REGULAR contains pick slips with all lines allocated from non-QuickPick zones.

• Spool file MIXED contains pick slips with lines allocated from both the QuickPick zone and non-QuickPick zones. Note: MIXED also displays if the pick slip is picking from more than 6 zones.

Regardless of QuickPick zone, the system creates a separate spool file for pick slips, based on warehouse/ship via priority combination.

See Sorting Pick Slips for more information on when the system creates separate spool files for pick slips and the sequence in which the system sorts pick slips within spool files.

Splitting an order into several pick slips: Allocating items based on QuickPick zone does not impact whether an order splits into several pick slips. See Splitting an Order for the reasons why an order may split into several pick slips.

For more information: See:

• QuickPick Example -- Printing Pick Slips by QuickPick Zone

• QuickPick Example -- Allocate from QuickPick Zone

• QuickPick Example -- Allocate from QuickPick Zone with Let Down Replenishment

• QuickPick Example -- Allocate from Non-QuickPIck Zone

• QuickPick Example -- Allocate from QuickPick and Non-QuickPick Zones (Mixed)

• QuickPick Example -- Allocate from QuickPick with Insufficient Inventory

Replenish from Primary during Let Down Replenishment (J42)

Purpose: Use this screen to define whether the system includes primary locations in the type of locations from which you can replenish stock when performing Let Down Replenishment.

MSR0052 CHANGE Change System Control Value 3/27/06 9:52:45 Description . : Replenish from Primary during Let Down Replenishment Yes/No . . . . (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 include primary locations in the type of locations from which you can replenish stock when performing Let Down Replenishment.

Let Down Replenishment is automatic restocking of primary locations initiated by the system when you generate pick slips. The system recommends, or recommends and immediately processes, a replenishment transfer, to insure that inventory quantities in primary locations is adequate for the pick slips you have generated. The Let Down Replenishment (C36) system control value determines whether the system initiates replenishment when you generate pick slips and whether the system completes the replenishment transfer, or recommends but does not complete the transfer.

During Let Down Replenishment, the system:

• Analyzes the inventory level in the primary location to determine if additional inventory is needed to fulfill the pick slip quantity.

• Analyzes the secondary and/or bulk locations to determine the quantity to transfer and the location from which to transfer, based on the setting defined in the Replenish from Location Type (A66) system control value.

• If the Replenish from Primary during Let Down Replenishment (J42) system control value is set to Y, and the secondary and/or bulk locations do not have enough stock required to fulfill the primary location, the system also analyzes the other primary locations to determine the quantity to transfer and the location from which to transfer.

Note: In order to replenish from primary locations, the Replenish from Location Type (A66) system control value must contain a value.

Let down replenishment -- Fill to max: The Let down replenishment -- Fill to max field defines whether the system stocks the locations during Let Down Replenishment just enough to allow picking or enough to fulfill all pick slips, plus refill the bin. If this field is set to Y, during Let Down Replenishment, the system calculates the quantity required to fulfill the pick slips and to refill the location back to its maximum quantity. However, if the Replenish from Primary during Let Down Replenishment (J42) system control value is set to Y and the system moves stock from a primary location, the system only moves the quantity required to cover the open pick slips.

Replenish primary locations: The Working with Replenishment Control (MSRP) menu option allows you to move inventory from secondary or bulk locations to the primary picking locations. The system does not look at the setting of the Replenish from Primary during Let Down Replenishment (J43) system control value when replenishing primary locations using the Work with Replenishment Control (MSRP) menu option.

Enter N or leave this field blank if you do not want the system to include primary locations in the type of locations from which you can replenish stock when performing Let Down Replenishment. The system replenishes stock only from secondary and/or bulk locations, based on the setting defined in the Replenish from Location Type (A66) system control value.

For more information: See:

• Let Down Replenishment for more information on the processing that occurs during Let Down Replenishment.

• Let Down Replenishment Example -- Replenish from Primary for an example of Let Down Replenishment including primary locations in the type of locations from which to replenish stock.

• Replenish Primary Locations Overview for an overview on replenishing primary locations by creating a replenishment request using Working with Replenishment Control (MSRP).

Rounding for Casepacks from Bulk in Let Down Replenishment (J43)

Purpose: Use this screen to define whether the system is required to move stock from bulk locations to primary locations in case packs during Let Down Replenishment, and whether to round up or round down to a case pack, based on the quantity required by Let Down Replenishment and the Maximum quantity defined for the item/location.

MSR0051 CHANGE Change System Control Value 3/27/06 10:33:25 Description . : Rounding for Casepacks from Bulk in Let Down Replenishment Code . . . . . ROUND UP ROUND DOWN Narrative . . . Application . : INV Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter a value in this field to indicate the system is required to move stock from bulk locations to primary locations in case packs during Let Down Replenishment.

Valid values are:

ROUND DOWN: The system moves stock from bulk locations in case packs during Let Down Replenishment and, if the replenishment quantity reaches the maximum quantity defined for the item location, the system moves case packs without going over the maximum quantity defined for the item location.

Example: Case packs contain a quantity of 12. Pick slips require 18 units. The quantity defined for the item location after the units for the pick slips have been removed is 30. The maximum quantity for the item location is 50. The Let down replenishment -- fill to max field for the pick slip generation template is set to Y. In this scenario, the system moves 3 case packs of 12 (36 units). 18 units are allocated to the pick slips. 18 units are moved to the item location, bringing the quantity to 48 (30 + 18 = 48; 2 units under the maximum quantity of 50).

ROUND UP: The system moves stock from bulk locations in case packs during Let Down Replenishment and, if the replenishment quantity reaches the maximum quantity defined for the item location, the system moves enough case packs to meet the maximum quantity defined for the item location, even if reaching the maximum means that the maximum quantity is exceeded.

Example: Case packs contain a quantity of 12. Pick slips require 18 units. The quantity defined for the item/location after the units for the pick slips have been removed is 30. The maximum quantity for the item/location is 50. The Let down replenishment -- fill to max field for the pick slip generation template is set to Y. In this scenario, the system moves 4 case packs of 12 (48 units). 18 units are allocated to the pick slips. 30 units are moved to the item/location, bringing the quantity to 60 (30 + 30 = 60; 10 units over the maximum quantity of 50).

Leave this field blank if you do not want to require the system to move stock from bulk locations to primary locations in case packs during Let Down Replenishment; instead, the system moves the number of units required by Let Down Replenishment.

Example: If case packs contain a quantity of 12, and Let Down Replenishment requires a quantity of 18, the system moves 18 units from bulk.

Pieces/case: The system uses the Pieces per case field in the Item file to determine the number of units in a case. If the Pieces per case field for an item is blank, the system assumes a quantity of 1 unit in a case and replenishes by unit instead of case pack during Let Down Replenishment.

Note: The Rounding for Casepacks from Bulk in Let Down Replenishment (J43) system control value only relates to moving stock in case packs from bulk locations. When replenishing from secondary or primary locations, the system only moves the quantity required by Let Down Replenishment, regardless of the setting of this system control value.

Replenish primary locations: The Working with Replenishment Control (MSRP) menu option allows you to move inventory from secondary or bulk locations to the primary picking locations. The system does not look at the setting of the Rounding for Casepacks from Bulk in Let Down Replenishment (J43) system control value when replenishing primary locations using the Work with Replenishment Control (MSRP) menu option.

Let down replenishment -- fill to max: The Let down replenishment -- fill to max field defined for a pick slip generation template defines whether the system stocks the locations during Let Down Replenishment just enough to allow picking or enough to fulfill all pick slips, plus refill the bin. Valid values for this field are:

Y = During Let Down Replenishment, the system calculates the quantity required to fulfill the pick slips and to refill the location back to its maximum quantity. If the Round for Casepacks from Bulk in Let Down Replenishment (J43) system control value is set to ROUND UP or ROUND DOWN, the system moves stock from bulk locations in case packs. In addition:

• If the Round for Casepacks from Bulk in Let Down Replenishment (J43) system control value is set to ROUND DOWN, the system moves case packs without going over the maximum quantity defined for the item location. See Let Down Replenishment Example -- Round Down for Case Packs and Fill to Max for an example.

• If the Round for Casepacks from Bulk in Let Down Replenishment (J43) system control value is set to ROUND UP, the system moves enough case packs to meet the maximum quantity defined for the item location, even if reaching the maximum means that the maximum quantity is exceeded. See Let Down Replenishment Example -- Round Up for CasePacks and Fill to Max for an example.

N (default) = During Let Down Replenishment, the system only moves enough stock to cover the open pick slips. If the Round for Casepacks from Bulk in Let Down Replenishment (J43) system control value is set to ROUND UP or ROUND DOWN, the system moves stock from bulk locations in case packs. In addition, the system moves enough case packs to meet the pick slip quantity, even if reaching the pick slip quantity means the maximum quantity for the primary location is exceeded. See Let Down Replenishment Example -- Round for CasePacks and Fill to Pick for an example.

For more information: See:

• Let Down Replenishment Example -- Round Down for Case Packs and Fill to Max

• Let Down Replenishment Example -- Round Up for CasePacks and Fill to Max

• Let Down Replenishment Example -- Round for CasePacks and Fill to Pick

Include HDL Warehouse Value on Order Detail (J54)

Purpose: Use this screen to define whether the system automatically assigns an HDL to an order line during reservation, based on the warehouse list associated with the SCF of the order ship to.

MSR0052 CHANGE Change System Control Value 11/03/06 12:03:33 Description . : Include HDL Warehouse value on Order Detail Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to automatically assign an HDL to an order line during reservation, based on the warehouse list associated with the SCF of the order ship to.

The system uses the Warehouse List Hierarchy to determine which HDL to assign to an order line.

• SCF/Item: The system assigns the HDL for the warehouse list defined at the SCF/item level first.

• SCF/Item class: If a warehouse list has not been defined at the SCF/item level, the system assigns the HDL for the warehouse list at the SCF/item class level.

• SCF: If a warehouse list has not been defined at the SCF/item class level, the system assigns the HDL for the warehouse list at the SCF level.

The systems assigns the HDL to the order line:

• regardless if the item quantity is reserved or is on backorder.

• even if the item is a dropship item.

• even if a warehouse override is defined for the order line or order (the reservation warehouse is not part of the warehouse list).

The system determines which HDL to assign to the order line when:

• you add the item to an order.

• during reservation processing (for example, the item quantity was initially on backorder).

• during manual reservation.

• when you process a return for the item on the order line.

For example, if the warehouse list associated with the order line has changed between initial order entry and reservation, the system updates the HDL on the order line to reflect the HDL in the new warehouse list.

The HDL code remains on the order line, even if:

• the item quantity is unreserved.

• the order line is cancelled.

What if more than one HDL exists in the warehouse list? If more than one HDL warehouse exists in the warehouse list, the system assigns the HDL with the highest priority to the order line.

When an order line is not assigned an HDL: The system does not assign an HDL to an order line when:

• the Include HDL Warehouse Value on Order Detail (J54) system control value is set to N, or

• a warehouse list is not associated with the SCF of the order ship to.

• an HDL warehouse is not included in the selected warehouse list for the order line.

Enter N or leave this field blank if you do not want the system to assign an HDL to an order line.

For more information: See HDL (Home Delivery Service) Processing.

Use Wave Picking (J87)

Purpose: Use this screen to define whether the system fulfills pick slips using wave picking functionality.

MSR0052 CHANGE Change System Control Value 3/19/08 10:14:38 Description . : Use Wave Picking Yes/No . . . . (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to fulfill pick slips using wave picking functionality.

Wave picking, or batch order picking, is the simultaneous picking of multiple customer orders, done to improve the efficiency of the overall picking operation. During pick slip generation, the system generates multiple waves (pick batches) in a single pick slip generation run. Orders are picked from various zones simultaneously, providing a fast method of picking. You can create a separate wave (pick batch) based on whether the pick slip contains an item that requires special handling, whether the order is an express-ship order, or whether the order is being shipped to an international address. You can further separate waves by whether the pick slip is a single-line pick slip or multi-line pick slip. In addition, for each type of wave, you can define the maximum number of pick slips that can be included in a single wave (pick batch) before the system generates a new wave.

For more information: See Using Wave Picking for an overview of the wave picking process and the required setup.

Cart/bin picking: If you enter Y in both the Use Wave Picking (J87) system control value and the Use Cart/Bin Picking? (B38) system control value, the system generates pick slips using cart/bin processing and not wave picking processing.

Enter N or leave this field blank if you do not want the system to fulfill pick slips using wave picking functionality.

Pick Wave Label Print Program (J88)

Purpose: Use this screen to define the print program the system uses to print pick wave labels.

MSR0053 CHANGE Change System Control Value 3/19/08 10:36:40 Description . : Pick Wave Label Print Program System name . . FLR1212 Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

System name: Enter the print program the system uses to print pick wave labels.

The system generates pick wave labels if you Use Wave Picking (J87). You can attach pick wave labels to items that you pick so that they can be sorted to the appropriate orders for shipment.

The base pick wave label print program is FLR1212.

Leave this field blank if you do not wish to print pick wave labels or you do not Use Wave Picking (J87).

For more information: See Using Wave Picking for an overview of the wave picking process and the required setup.

Consolidated Credit Invoice (K06)

Purpose: Use this screen to indicate whether to consolidate credit invoices for returns processed on the same date.

MSR0052 CHANGE Change System Control Value 9/22/08 15:39:07 Description . : Consolidated Credit Invoice Yes/No . . . . Y (Y,N) Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Yes/No field: Enter Y in this field if you want the system to consolidate credit invoices created for an order on the same date. Returns that you process against an order separately, but on the same date, are included on the same credit invoice.

Related system control values:

• The Invoice Consolidation Method (E29) system control value defines whether the system consolidates regular (debit) or credit invoices across all ship-to addresses on the order, or only within the same ship-to address.

• Setting the Capture Addresses for Invoice (J24) system control value to Y prevents regular or credit invoice consolidation when you change the billing or shipping address between processing shipments or returns.

• Setting the Update Invoice File with System Date During Billing (D51) system control value to Y prevents regular or credit invoice consolidation.

• The Consolidated Invoice (B49) system control value controls the consolidation of shipment invoices.

Note: If you consolidate credit invoices and the E-mail Shipment/Return Confirmation Notification Immediately (K07) system control value is set to Y, then it is possible for the customer to receive multiple return confirmation emails on the same date, with each subsequent confirmation listing the newly-returned item(s) plus each item returned previously that day.

Additional factor that prevents credit invoice consolidation: Credit invoices do not consolidate if you:

1. Create a credit invoice by processing the first refund on the order.

2. Before processing the next return:

• Refund the credit card used for a credit invoice using Processing Refunds (MREF).

• Submit deposits using Processing Auto Deposits (SDEP).

Enter N if you do not want to consolidate credit invoices. All returns produce separate credit invoices, regardless of when they bill.

Note: After changing the setting of this system control value, end the background jobs and then restart them to make your change take effect.

For more information: See the Invoice Consolidation Method (E29) system control value for a discussion of invoice consolidation for both credit and regular invoices and examples.

UPS Identifier and Account Number (K57)

Purpose: Use this screen to define the customer identifier and UPS account number to use as the first eight positions of the UPS tracking number. The system prints this information on the pick slip if your unique pick print program supports it.

MSR0051 CHANGE Change System Control Value 1/28/10 7:59:03 Description . : UPS Identifier and Account Number Code . . . . . Narrative . . . Application . : FUL Applic group . ALL Sequence# . . . 99 F3=Exit F12=Cancel

Code field: Enter the customer identifier and UPS account number to use as the first eight positions of the UPS tracking number.

The Pick Printing Program (C37) system control value defines the program the system uses to print pick slips. The system includes the UPS identifier and account number on the pick slip only if your unique print program supports it.

Additional information to print on your unique pick slip: The system prints the following information on the pick slip if your unique pick print program supports it.

• UPS service code and service icon: The UPS service code defines the type of shipment delivery, such as ground or next day air. The UPS service icon defines the package level of service. You can define the UPS service code and service icon for each pay type whose Type field is U (UPS). The system stores this information in the UPS Service Code XRef file. See the Create Ship Via (1 of 2) Screen.

• UPS routing code: The UPS routing code helps ensure the accurate routing and prompt delivery of a shipment. The code identifies the UPS delivery facility and is derived from the destination country and postal code. You can define the UPS routing code in the UPS Routing Code file. Note: It is your responsibility to populate this file with the UPS routing code information provided by UPS.

UPS tracking number: The UPS tracking number is an 18 character string consisting of the following elements. The system prints the UPS tracking number on the pick slip if your unique pick print program supports it.

• Identifier: The UPS customer identifier is a unique two-digit reference number assigned by UPS. The system pulls this information from the UPS Identifier and Account Number (K57) system control value.

• UPS account number: The UPS account number, or shipper name, is a unique six-digit reference number assigned by UPS to a shipper for billing purposes. The system pulls this information from the UPS Identifier and Account Number (K57) system control value.

• Service Code: The UPS service code is a two position code assigned by UPS to indicate the type of shipment delivery service, such as ground or next day air. The system pulls this information from the UPS service code field for the UPS pay type in the UPS Service Code XRef file. See the Create Ship Via (1 of 2) Screen for more information.

• Package ID: The package ID is a 7 position code to identify the delivery package for tracking purposes. This is the pick control number from the Pick Control Header file.

• Check Digit: The check digit is a 1 position code. The system uses a calculation based on the other elements of the tracking number to determine this value.

CWPickOut message: If your unique print program supports it, the system includes the UPS tracking number in the alternate_pick_nbr tag of the Pick Message from CWDirect (CWPickOut). Note: In order to update the alternate_pick_nbr tag with the UPS tracking number, the Use PkMS Interface Values (F31) system control value must be N.

Deadline for Special Shipper Override (L43)

Purpose: Use this screen to define the date that controls whether to override the ship via on a pick slip based on a Special shipper override in pick slip generation.

MSR0893 CHANGE Change System Control Value 4/15/11 11:38:40 Description . : Deadline for Special Shipper Override Date . . . . . 6/17/11 Narrative . . . Date used for special shipper override logic in Pick Generation. Application . : FUL Applic group . PCK Sequence# . . . 99 F3=Exit F12=Cancel

Date field: Enter the date to control whether to override the ship via on a pick slip based on the override records set up at the Special Shipper OVR by Day/Via/Zone Screen in pick slip generation. You can use this system control value to provide expedited shipping in the days preceding a holiday (for example, “free upgrade to two-day shipping from now until Christmas”).

Controls access to options in pick slip generation: If this system control value is currently set to a date in the future, the Special shipper override field and the Special Shipper OVR by Day/Via/Zone Screen are available in pick slip generation. Otherwise, the option is not displayed and the screen is not available.

Special shipper override evaluation: Pick slip generation overrides the ship via on a pick slip based on an override record if:

• the Drop point on the Pick Control Header matches the Drop point set up for the current ship via in Work with SCF Ship Via Values (WSHV).

• the Special shipper override at the Pick Slip Generation (1 of 2) Screen is set to Y, and

• there is a matching Special Shipper Override record for the pick slip generation job, for which:

• the number of days until the Deadline for Special Shipper Override (L43) is equal to the # of days prior to deadline.

Example:

• The Deadline for Special Shipper Override (L43) system control value is set to 12/23 • Today is 12/21 • There is a Special Shipper Override record with the # of days prior to deadline set to 2 (12/23-12/21) Note: The # of days prior to deadline must be an exact match to the deadline minus the current date. It is not a “greater than or equal to” or “less than or equal to” match.

• the current Ship via on the pick slip matches the Ship via on the Special Shipper Override record.

• the Ship zone for the related SCF Ship Via record matches the Shipping zone on the Special Shipper Override record.

Example:

• The Shipping zone for the override record is 3. • The Ship via currently on the pick slip is 2. • The pick slip is shipping to SCF 016. • The SCF Ship Via record for ship via 2 and SCF 016 has a Ship zone of 3.

If a pick slip qualifies for override based on the above conditions, the program sets the ship via on the pick slip to the Ship via override for the override record; also, it writes an Order Transaction History message, such as Special shipper override (03).

Note:

• No additional freight added: Any additional freight charges related to the Ship via override do not apply to the order.

• Updates pick slip only: The override applies to the pick slip only, and does not update the order ship-to or order detail.

• Override all orders to via takes precedence: If the Override all orders to via field for the pick slip generation template specifies a ship via, this ship via takes precedence over a special ship via. However, a special ship via override takes precedence over all other ship via overrides in pick slip generation.

• Shipping lead days not considered: The evaluation does not consider the Shipping lead days for the SCF Ship Via.

• Evaluation based on current ship via: The evaluation does not consider whether the current ship via on the pick slip is the result of any sort of override, such as a promotion.

• SCF Ship Via record required for current ship via: There must be a matching SCF Ship Via record for the SCF, ship zone, and the ship via that is currently on the pick slip before the override; however, there is no requirement that an SCF Ship Via record exist for the SCF on the pick slip and the Ship via override.

• Evaluation does not take place in void/reprint: If you use the void/reprint option in Reprinting and Voiding Pick Slips (WVRP), the ship via override remains on the pick slip. However, if you use the void option and reprint the pick slip afterward, pick slip generation again uses the evaluation process described above to determine whether to override the ship via.

• Evaluation does not take place for drop ships: The evaluation does not take place when you use Selecting Vendors for Drop Ship Processing (MDSP).

• Evaluation can take place during retail store restock: The evaluation does take place when you use the Working with Retail Store Restock (WRSR) option if you select a pick slip generation template that supports the special shipper override.

• No other logic affected: The evaluation does not affect any other processing that occurs during pick slip generation, such as selection, sorting, or splitting logic.

Leave this field blank if you are not using the special ship via override option at pick slip generation. The Select shipper override field and the Special Shipper OVR by Day/Via/Zone Screen are not available in pick slip generation.

For more information: See:

• Special Shipper OVR by Day/Via/Zone Screen

• Working with SCF/Ship Via Values (WSHV)

---

1. IBM WebSphere® is a registered trademark of IBM Corporation.