Field

Description

Generate item out triggers

Indicates whether to create an outbound interface transaction trigger for each item and SKU created, updated, or deleted when you complete this screen. The system creates a trigger with a file type of SKU, indicating to generate an outbound item XML message for the item. See Generic Item Download API for more information on the outbound XML message. Valid values are:

Y = Create a trigger to create an outbound item XML message (CWItemOut) for each item and SKU created or updated.

N = Do not create the triggers for the outbound item XML message.

Important: If you set this field to N, then the system does not create any triggers for any items or SKU’s that you create, change, or delete at this screen.

This field defaults to the setting from the last time you used this menu option. If there is no stored setting, the default is Y. See Working with Default Options (WDFT) for information on how the system stores defaults.

Note: This field is displayed only if the Create Generic Item Download Trigger Records (I15) system control value is set to Y.

Alphanumeric, 1 position; required.

Date

The date you created the item upload record.

Numeric, 6 positions (MMDDYY format); optional.

Record Type

A code that defines the item/SKU information you want to add, change, or delete. Valid values are:

01 = Item/SKU

03 = Item Offer (including item alias)

04 = SKU Offer

05 = Item Price

06 = SKU Price

07 = Vendor Item

08 = Item UPC

09 = Item Coordinate

10 = SKU Cross Reference

11 = Vendor/Item Additional Charge

12 = Item Information

Fields in the item upload file are categorized by record type, and this code determines the group of item/SKU information fields that the item upload program evaluates to create or update an item/SKU.

Example: If you want to change a SKU’s price information, you enter an 06 (SKU Price) record type. Even if all the fields in the item upload record are populated for that SKU, only the information in the nine SKU price fields is evaluated.

Note: If you maintain values (a change Request Type) for different record types and you leave blank fields in the item upload record related to that record type, the system updates the associated files with blanks.

01 Item/SKU Record Type

When passing information to CWDirect, you must build upon values passed in this record type. For example, you cannot create a vendor item (07 record type) until you have first created the item/SKU (01 record type).

The system considers fields associated with this record type. Of these fields, the following are required when the Use Retail Integration (H26) system control value is set to Y:

• L/S style

• L/S vendor

• Item description

• L/S class

• L/S department

• L/S division (if the Require L/S Division with L/S Department (E85) system control value is set to Y, AND you are passing a new L/S Department value)

• Item class (if the Require Item Class in Work with Items (F06) system control value is set to Y)

See Fields for 01 Item/SKU Record Type.

Creating an item/SKU record is the only instance in which the item and SKU code fields are evaluated outside of the Key Type, and the only instance where the item identifier values for the key type are not required.

Example: When creating an item/SKU (an add Request Type for an 01 record type), you must pass an Item code unless you have the Auto Assign Item # (D46) system control value set to Y. If this system control value is set to N, the system displays an error message when using a key type other than IT: An Item/SKU was not found with the given surrogate key.

When you use the IT key type and do not enter an item code, a message displays: Missing Item/SKU for Key Type IT.

You must also pass a SKU code in the above situation (an add Request Type for an 01 record type) when the Allow SKUs field is set to Y.

Note: When you pass an add request for the 01 record type and leave various fields blank, the system tries to default values from the **DFLT ITEM or system control values. See Creating Default and Change Item/SKU Upload Values: **DFLT ITEM and **DFTCHG.

03 Item Offer Record Type

The system considers fields associated with this record type. The Offer for item offer field is required. In addition, if you are including item alias, the page and alias are required. See Fields for 03 Item Offer Record Type.

04 SKU Offer Record Type

The system considers 23 fields associated with this record type. The SKU offer for SKU offer field is required. See Fields for 04 SKU Offer Record Type.

If you use the RS Key Type to identify the item associated with the item upload record, you must also enter a value in the SKU field so that the system can identify the SKU for the offer record. If you use the LS key type and have other SKUs that use the same long SKU values, enter a SKU code in this field so that the system can identify the SKU for the offer.

05 Item Price Record Type

The system considers the fields associated with the item price record type. These fields are required:

• Offer for item price

• Effective date

• Quantity

• Price

See Fields for 05 Item Price Record Type. You cannot create an item price record until you have created an item offer record.

06 SKU Price Record Type

The system considers the fields associated with the SKU price record type. These fields are required:

• Offer for SKU price

• SKP effective date

• SKP quantity

• SKP price

See Fields for 06 SKU Price Record Type. You cannot create a SKU price record without first creating a SKU offer record.

If you use the RS Key Type to identify the CWDirect item associated with the item upload record, you must also enter a code in the SKU field so that the system can identify the SKU for the price record. If you use the LS key type and have other SKUs that use the same long SKU values, enter a SKU code in this field so that the system can identify the SKU for the price record.

07 Vendor Item Record Type

The system considers the fields associated with the vendor item record type. These fields are required:

• Vendor for vendor item record

• item code

• Description

See Fields for 07 Vendor Item Record Type. If the item for which you are creating a vendor item has SKUs, you must select a Key Type that can identify a SKU or enter a code in the SKU field for the item upload record.

08 UPC Record Type

The system considers the fields associated with the UPC record type. The UPC type and UPC code are required. See Fields for 08 Item UPC Record Type.

09 Item Coordinate Record Type

The system considers the fields associated with the item coordinate record type. The Item coordinate is always required, and the Coordinate SKU is required if the coordinate item has SKU’s. See Fields for 09 Item Coordinate Record Type.

10 SKU Cross Reference Record Type

The system considers the fields associated with the SKU cross reference record type. Both the SKU Xref # and the SKU Xref type are required. See Fields for 10 SKU Cross Reference Record Type.

11 Vendor Item Additional Charge Record Type

The system considers the fields associated with the vendor item, the purchase order additional charge code, and the percentage or amount of the charge. See Fields for 11 Vendor Item Additional Charge Record Type.

12 Item Information Record Type

The system considers the fields associated with the item information record type. See Fields for 12 Item Information Record Type.

Numeric, 2 positions; optional.

IUP Request Type

A code that defines whether you create, change or delete item/SKU information. Valid values are:

A: add record; however, if the system finds a record in the CWDirect database that matches the information in the RI Item Upload record, the system changes the Request type to C and updates the existing record.

C: change record; however, if the system cannot find a record in the CWDirect database that matches the information in the RI Item Upload record, the system changes the Request type to A and creates a new record.

D = Delete request to delete a record.

Add Request Type

You can pass numerous add requests for the same item/SKU with these record types:

• 03 (item offer)

• 04 (SKU offer)

• 05 (item price)

• 06 (SKU price)

• 07 (vendor item)

• 09 (item coordinate)

• 10 (SKU cross reference)

• 11 (vendor item additional charge)

• 12 (item information)

When adding an item/SKU (01 record type), the system tries to default values whenever you leave a record type 01 field blank. The system looks to the **DFLT item and system control values to default values whenever possible. See Creating Default and Change Item/SKU Upload Values: **DFLT ITEM and **DFTCHG.

Change Request Type

You can pass multiple change requests for all record types; however, the fields associated with the specified record type are overwritten with the most recent information you pass for that record type. Do not pass a change request trying to update only one or two fields.

Example: You want to change the effective date for a SKU price record (C request type, 06 record type). Assuming you enter identifier Key Type values and the system can find the SKU associated with the item upload record, if you enter the required fields for a SKU price record, updating the effective date but you leave the other fields that the system considers for the SKU price Record Type blank, the system updates the file with the values you entered in the required fields, and overwrites the rest of the data in the file with blanks.

Note: The system overwrites data from blank fields passed in change requests for every record type except the 01 item/SKU record type. With this record type, the system defaults values whenever possible, either from the **DFLT ITEM or from system control values. See Creating Default and Change Item/SKU Upload Values: **DFLT ITEM and **DFTCHG.

Delete Request Type

You can pass deletion requests for primary file values only. For example, you cannot delete the L/S Department value associated with an item from the Item file, but you can delete the item record itself. All deletions are subject to the system edits within CWDirect.

You can send a delete request for all record types. With a SKUed item, only the SKU record is deleted. If you delete the last remaining SKU for an item, the base item is also deleted.

Alphanumeric, 1 position; optional.

IUP Key Type

This code defines the field values the system evaluates in order to identify the CWDirect item or SKU associated with an item upload record. Valid values are:

IT = Item/SKU code

LS = Long SKU values

RS = Item retail style number

UP = Item/SKU UPC code

It is possible for more than one item to have the same identifier values. This can happen only with the long SKU values or the retail style numbers. The system requires that item/SKU and UPC codes are unique and does not allow you to create a duplicate code either through the item upload or manually in CWDirect. If duplicate long SKU values or retail style numbers exist, the system can not determine the CWDirect item associated with the item upload. The system places the record in an error status and displays an error message at the Work with Retail Item Upload Errors Screen screen: An Item/SKU was not found with the given surrogate key.

Note:

• If an item has SKUs, you cannot enter the item identifier values for the base item and make changes to all the SKUs. To make SKU level changes, you must pass identifier values that allow the system to identify the SKU and make changes or deletions individually.

• Using any key type besides IT (item/SKU) is not supported for type 10 (SKU cross reference) records.

IT Key Type

The Item and SKU fields identify the item and SKU associated with the item upload record. If you define IT as the key type, the Item field is required and optionally the SKU field if you want to change information for a specific SKU. If the item contains SKUs and you do not enter a SKU code, the system maintains the base item for an item-level Record Type. A message displays if you do not enter a code in the Item and SKU fields and the key type for the item upload record is RS.

LS Key Type

The long SKU fields identify the item and SKU associated with the item upload record. If you define LS as the key type, the L/S department, L/S class, L/S style, and L/S vendor fields are required and the L/S color, L/S size, L/S width, and SKU fields are optional.

The L/S fields at the SKU level override the L/S fields at the item level. Therefore, when you are trying to map to a SKUed item, you only need to enter the L/S fields necessary to uniquely identify the SKU. If however, multiple SKUs have the same long SKU values at the item and SKU levels, the system considers the SKU codes to try to identify the SKU associated with the item upload record.

Note: This key type is not supported for type 10 (SKU cross reference) records.

RS Key Type

The Retail style number field identifies the item associated with the item upload record. If you define RS as the key type, the Retail style # field is required and the SKU field is optional. A message displays if you do not enter a code in the Retail style # field and the key type for the item upload record is RS: Missing Retail Style # for Key Type RS.

If you are trying to identify a SKU using the RS key type, you must enter a SKU code.

Note: This key type is not supported for type 10 (SKU cross reference) records.

UP Key Type

The UPC code field identifies the item and SKU associated with the item upload record. If you define UP as the key type, the UPC code field is required. A message displays if you do not enter a code in the UPC code field and the key type for the item upload record is UP: Missing UPC/UPC Type for Key Type UP.

Since UPC codes are defined for SKUs if an item has SKUs, you cannot use UPC codes to map to a base item for an item-level Record Type.

Note: This key type is not supported for type 10 (SKU cross reference) records.

Alphanumeric, 2 positions; optional.

Key

The information that the system/translation program retrieved to identify the item or SKU associated with the item upload record. For each key type different information is passed to identify the item/SKU, therefore the information displayed here changes with the different key types.

Example: If you used the RS key type, the item’s retail style number displays here, if the system was able to find an item with a matching retail style number. If the system cannot find the item, this field displays the partial information you passed and an error message displays: An Item/SKU was not found with the given surrogate key.

If the system maps the record to an item/SKU within CWDirect, the item/SKU’s full information displays here.

Alphanumeric, 30 positions; display-only.

Sts (Status)

The status of the item upload record. Valid values are:

E = The item upload record contains errors.

P = The item upload record has been processed.

U or blank = The item upload record is ready to be processed.

D = The item upload record is deleted from the file when you submit the process.

When you pass records to the Retail Integration Item Upload file either directly or from the Copy Retail Item Upload Records file, the Upload Translation program creates unprocessed records that display on the Work with Retail Item Upload Screen with a blank Sts (Status) field. When you press F9 to process and edit the item upload records, the system updates all records with the appropriate status. Only records in E status remain visible at the Work with Retail Item Upload Screen so that you can correct them.

Alphanumeric, 1 position; optional.

Field

CWCreateItem Element

Description

Keys to the File: Fields Required for all Record Types

You must enter a value in these key fields. The values you enter for these keys determine:

• what information gets passed to CWDirect.

• whether the item upload program creates, changes, or deletes an item.

• how the item upload program identifies the CWDirect item associated with the item upload record.

Note: If you are passing records interactively and do not enter a value in all of these fields, the item upload program errors the record, places it in a fail status, and does not sent it to the item upload. The system sends a response to the retail system indicating the records failed.

See Basic errors and Item errors.

Company

company

A code that represents the company to which you wish to upload retail item/SKU information. Company codes are defined in and validated against the Company file.

Numeric, 3 positions; required.

Record Created Date

create_date

The date you create the item upload record.

Note: If you do not enter a value in this field using the batch process, when you enter 2 next to the item upload record at the Work with Retail Item Upload Screen, you advance to an E2 Key Screen and cannot correct any errors in the record.

Numeric, 7 positions (CYYMMDD format); required.

Record Created Time

create_time

The time you create the item upload record.

Note: If you do not enter a value in this field using the batch process, when you enter 2 next to the item upload record at the Work with Retail Item Upload Screen, you advance to an E2 Key Screen and cannot correct any errors in the record.

Numeric, 6 positions (HHMMSS format), required.

Record Type

record_type

A code that defines the item/SKU information you want to add, change, or delete. Valid values are:

01 = Item/SKU

03 = Item Offer

04 = SKU Offer

05 = Item Price

06 = SKU Price

07 = Vendor Item

08 = Item UPC

09 = Item Coordinate

10 = SKU Cross Reference

11 = Vendor Item Additional Charge

12 = Item Information

The record type determines what fields the system considers in the item upload record. For example, if you want to change a SKU’s price information, enter an 06 record type. Even if all the fields in the item upload record are populated for that SKU, the system only looks at information in the nine SKU price fields.

See the following for the fields and descriptions associated with each record type:

• Fields for 01 Item/SKU Record Type

• Fields for 03 Item Offer Record Type

• Fields for 04 SKU Offer Record Type

• Fields for 05 Item Price Record Type

• Fields for 06 SKU Price Record Type

• Fields for 07 Vendor Item Record Type

• Fields for 08 Item UPC Record Type

• Fields for 09 Item Coordinate Record Type

• Fields for 10 SKU Cross Reference Record Type

• Fields for 11 Vendor Item Additional Charge Record Type

• Fields for 12 Item Information Record Type

Note: When passing information to CWDirect, you must build upon values passed in this record type. For example, you cannot create a vendor item (07 record type) until you have first created the item/SKU (01 record type).

**DFLT ITEM and **DFTCHG

The **DFLT ITEM allows you to default values to blank fields in an add or change item upload record for an item/SKU record type. The **DFTCHG item determines if the system updates an existing item with the values defined in a change item upload record for an item/SKU record type. See Creating Default and Change Item/SKU Upload Values: **DFLT ITEM and **DFTCHG.

Alphanumeric, 2 positions; required.

Request Type

request_type

A code that defines whether the upload program creates, maintains, or deletes item/SKU information. Valid values are:

A: add record; however, if the system finds a record in the CWDirect database that matches the information in the RI Item Upload record, the system changes the Request type to C and updates the existing record.

C: change record; however, if the system cannot find a record in the CWDirect database that matches the information in the RI Item Upload record, the system changes the Request type to A and creates a new record.

D = Delete request to delete a record.

The request type you send depends on what records you have already passed. For example, you cannot create a vendor item unless the item already exists.

Add Request Type (A)

You can pass multiple add requests for the same item/SKU with these record types:

• 01 (item/SKU)

• 03 (item offer)

• 04 (SKU offer)

• 05 (item price)

• 06 (SKU price)

• 07 (vendor item)

• 10 (SKU cross reference)

• 11 (vendor item additional charge)

• 12 (item information)

If you pass blank values for an item/SKU (01 record type), the system defaults values based on the **DFLT ITEM and system control values; see Creating the **DFLT ITEM Item/SKU.

Change Request Type (C)

You can pass multiple change requests for all record types; however, the fields associated with the specified record type are overwritten with the most recent information you pass for that record type.

If you pass blank values for an item/SKU (01 record type), the system defaults values using the **DFLT ITEM and system control values. Also, if a value exists in **DFTCHG, the system does not update the existing item with the upload value; see Creating Default and Change Item/SKU Upload Values: **DFLT ITEM and **DFTCHG.

If you pass blank values for any other record type, the system updates the value for the existing item to blank.

Note: The system does not update any history records for transactions that occurred prior to the change date.

Delete Request Type (D)

You can send a delete request for all record types; however you can delete only primary file values for the Record Type you specify.

For a SKU’d item, the system only deletes the SKU record. If you delete the last remaining SKU for an item, the system also deletes the base item.

All deletions are subject to the system edits within CWDirect.

• You cannot delete a base item if Allow SKUs field is set to Y.

• You cannot delete item information for an item/SKU that has open orders or an on-hand quantity other than zero.

Alphanumeric, 1 position; required.

Sequence #

no associated element

The sequence number assigned to the item upload record when using the batch process. This field is not available when passing records interactively since records are received and processed one at a time.

Sequence numbers can be in a random order or sequentially assigned, but they must be unique for each day. If you duplicate a sequence number for the same date, the record does not get passed to the item upload file and does not display at the Work with Retail Item Upload Screen.

Numeric, 3 positions; required.

Key Type

key_type

A code that defines how the system identifies the CWDirect item/SKU associated with a change or delete item upload record. Valid values are:

IT = Item/SKU; the upload record contains the item code, and optionally SKU code, that matches a CWDirect item/SKU. If the item contains SKUs and you do not enter a SKU code, the system maintains the base item.

Note: This is the only key type that is valid for a type 10 (SKU cross reference) record.

LS = Long SKU values; the upload record contains the L/S department, L/S class, L/S style, L/S vendor, and optionally L/S color, L/S size, and L/S width, that matches a CWDirect item/SKU. The L/S fields at the SKU level override the L/S fields at the item level.

RS = Retail style number; the upload record contains the retail style number that matches a CWDirect item/SKU. If you are trying to identify a SKU using the RS key type, you must enter a SKU code.

UP = UPC code; the upload record contains the UPC code that matches a CWDirect item/SKU. Since UPC codes are defined at the SKU level, you cannot use UPC codes to map to a base item.

If duplicate long SKU values or retail style numbers exist, the system cannot determine the CWDirect item associated with the item upload and places the record in an error status with the error message: An Item/SKU was not found with the given surrogate key.

If you try to change or delete a SKU value and duplicate identifier values exist, the system cannot determine which SKU is associated with the item upload and displays an error message: SKU is required for this record type.

Alphanumeric, 2 positions; required.

CWDirect values

Item

item

A user-defined code that represents a unit of inventory.

The system automatically assigns an item number if you set the Auto Assign Item # (D46) system control value to Y; however, you can override this value.

For an add request for an 01 Record Type, you must pass an item code unless you have the Auto Assign Item # (D46) system control value set to Y.

Identifier Value

For the IT Key Type, the item code you enter must identically match an item in CWDirect for the system to identify the item associated with the add or delete item upload record.

Alphanumeric, 12 positions; required for 01 records.

SKU

sku

seo_code

set_code

sew_code

The unique attributes of an item, such as color, size, and style. The Split SKU Inventory (A26) system control value controls whether you use a full SKU or split SKU environment.

This field does not display distinct fields for split SKU elements; therefore, you must count positions and enter the SKU element in the respective place on the field if you have the Split SKU Inventory (A26) system control value set to Y. Spacing is as follows:

• SKU Element 1 = spaces 1-4

• SKU Element 2 = spaces 6-9

• SKU Element 3 = spaces 11-14

Item Identifier

For the IT, LS, and RS Key Types, the SKU code you enter must match a SKU in CWDirect. If you make a mistake on spacing for split SKUs or enter an invalid full SKU, the system cannot identify the correct SKU for add and delete requests and displays an error message: Invalid Item.

Alphanumeric, 14 positions; required if the Allow SKUs field is set to Y.

Status

status

A system-generated code that represents the record’s status in the Retail Item Upload file. Valid values are:

E = Error

P = Processed

U or blank = Unprocessed

D = Delete Pending

When you pass records to the Retail Integration Item Upload file the Upload Translation program creates unprocessed records that display on the Work with Retail Item Upload Screen with a blank Sts (Status) field. When you press F9 to process and edit the item upload records, the system updates all records with the appropriate status. Only records in E status remain visible at the Work with Retail Item Upload Screen so that you can correct them.

Alphanumeric, 1 position; optional.

Processed Date

no associated element

The date the item upload record was processed. This date is used to update the Created date and the Last change date in the Item file. This date is visible in as the Last chg date (Last change date) field in Creating and Maintaining Items.

Numeric, 7 positions (CYYMMDD format); optional.

Processed Time

no associated element

The time the item upload record was processed. This time is used to update the Created time and Maintained time in the Item file.

Numeric, 6 positions (HHMMSS format); optional.

Fields for 01 Item/SKU Record Type

See Basic errors, Item errors, and SKU errors.

Note: Fields not in the file:

• External info: This file does not contain the Ext info (External info) field; however, you can update this field on the Change Item Screen.

• Locate eligible: This file does not contain the Locate elig (Locate eligible) field. When creating a new item, the program does not use the setting from the **DFLT ITEM record; this field is always set to Y for a new item. However, when changing an existing item, the program does use the setting from the **DFTCHG item to determine whether to update this field. See Creating Default and Change Item/SKU Upload Values: **DFLT ITEM and **DFTCHG for background.

Allow SKUs

allow_skus

This field indicates whether the item is available in various styles, such as color, size, etc. Valid values are:

Y = This item has SKUs associated with it.

N = There are no SKUs associated with this item.

You must set this field to Y when you pass an 01, 04, 06 or 07 Record Type for upload records containing a SKU code.

The value in this field does not default from the **DFLT ITEM. If you do not enter a value in this field, the system sets the SKU field to N in the Item file.

Alphanumeric, 1 position; required for 01 Item/SKU record types.

Cub val

itm_cubing_value

The cubic volume of the item. This value controls the number of units of the item that can fit into a carton; see Performing Cubing.

Numeric, 7 positions with a 1-place decimal; optional.

Drop Ship

itm_drop_ship

Indicates whether you ship the item from your warehouse, or have your vendor ship it to the customer directly.

You can flag an item as drop ship at the item level and SKU level. The setting at the SKU level overrides the setting at the item level. If the setting at the SKU level is blank, the system uses the setting at the item level.

Valid values are:

Y = Drop ship item. When a customer orders the item, you order the item from your vendor and the vendor ships it directly to your customer. If the item is flagged as drop ship, any SKUs for the item can be flagged as drop ship or non-drop ship.

N (or blank) = Non-drop ship item. You ship the item from your warehouse. If the item is flagged as non-drop ship, any SKUs defined for the item must also be flagged as non-drop ship.

Alphanumeric, 1 position; optional.

Height

itm_height

The height measurement for an item. The Height, Length, and Width values determine the cubic volume of an item. This value can be entered in feet or centimeters, or any other measurement as long as it is consistent.

Numeric, 3 positions; optional.

Kit Type

itm_kit_type

Defines the type of kit or set functionality represented by this item.

Valid values:

C = Continuity program

S = Set

F = Finished goods

V = Variable set

Blank = none of the above

Note: You cannot link set component items to the set master item through the item upload; you must do this within CWDirect after you create the item/SKU records.

Alphanumeric, 1 position; optional.

Length

itm_length

The length measurement for an item. The Height, Length, and Width values determine the cubic volume of an item. This value can be entered in feet or centimeters, or any other measurement as long as it is consistent.

Numeric, 3 positions; optional.

Long SKU Style

itm_long_sku_style

A user-defined field representing the long SKU style defined for the item.

This field is required if the Use Retail Integration (H26) system control value is set to Y.

If the Require L/S Style (I94) system control value is set to Y, the system validates that the long SKU style is a unique value.

If you do not have authority to the Maintain Long SKU Values in MITM (B05) secured feature, you cannot enter or change this value.

Item Identifier

For the LS Key Type, the system uses the value in this field combined with the L/S department, L/S class, and L/S vendor values, and optionally the L/S color, L/S size, L/S width, and SKU code values to identify the CWDirect item/SKU associated with the item upload record.

Alphanumeric, 20 positions; required if SCV H26 or SCV I94 is set to Y.

Retail Style #

itm_retail_style

A user-defined code used to identify the item.

Item Identifier

For the RS key type, the system uses the value in this field to identify the base item in CWDirect associated with the item upload record. If you are trying to identify a SKU using the base item’s retail style number, you must enter the SKU’s code in the SKU field.

Alphanumeric, 20 positions; optional.

Long SKU Vendor

itm_long_sku_vendor

A user-defined field representing the long SKU vendor for the item/SKU.

This field is required if the Use Retail Integration (H26) system control value is set to Y. See Merchandising Chapter 88: Retail Integration (External System into CWDirect) Overview and Setup.

If you do not have authority to the Maintain Long SKU Values in MITM (B05) secured feature, you cannot enter or change this value.

Item Identifier

For the LS Key Type, the system uses the value in this field combined with the L/S department, L/S class, and L/S style values, and optionally, the L/S color, L/S size, L/S width and SKU code values to identify the CWDirect item/SKU associated with the item upload record.

Alphanumeric, 7 positions; required if the Use Retail Integration (H26) system control value is set to Y.

Standard Cost

itm_standard_cost

The standard cost of the item. This is the cost that appears in the Default cost field in the item file.

Numeric, 11 positions with a 4-place decimal; optional.

Non-Inventory

itm_non_inventory

This value indicates whether inventory levels are maintained for the item.

Y = This is a non-inventory item.

N (or blank) = This is a regular item that will be tracked.

Alphanumeric, 1 position; optional.

Pieces Per Case

itm_pieces_per_case

The system uses this value to determine the number of units that fit in a case when creating license plate numbers for radio frequency inventory management and suggesting location placement and when determining the restock quantity when you perform retail store restock.

Numeric, 5 positions; optional.

Selling Qty

itm_selling_quantity

The selling quantity defines the required order quantity (or multiple of) for this item. For example, an item may be stocked in single units, but must be sold in quantities of 6 (or 12, or 18, etc.).

Numeric, 5 positions; optional.

Selling Weight

itm_selling_weight

This value is used to calculate the freight charge on an item when the Freight method on the order is Freight by weight or Freight by order weight, as defined in the Source Code file.

Numeric, 7 positions with a 3-place decimal; optional.

Serial # Tracking

itm_serial_tracking

This value determines whether each unit of the item has a specific serial number that should be tracked.

Y = This item uses serial numbers.

N (or blank) = This item does not use serial numbers.

Alphanumeric, 1 position; optional.

Ship Alone

itm_ship_alone

The value in this field indicates how to ship this item.

Valid values are:

S = This item must ship by itself, and each unit prints on its own pick slip.

M = This item can be shipped with other items (that also have an M in the Ship alone field).

L = This item prints on the pick slip in Location Class sequence along with other items belonging to the same class.

U = This value represents a user-defined code for any special shipping requirements.

Alphanumeric, 1 position; optional.

Ship Weight

itm_ship_weight

The actual shipping weight of the item.

Numeric, 7 positions with a 3-place decimal; optional.

User Field 1

itm_user_field_1

An informational field you can use according to your organization's specific requirements.

Alphanumeric, 10 positions; optional.

User Field 2

itm_user_field_2

An informational field you can use according to your organization’s specific requirements.

Alphanumeric, 10 positions; optional.

User Field 3

itm_user_field_3

An informational field you can use according to your organization’s specific requirements.

Alphanumeric, 10 positions; optional.

User Field 4

itm_user_field_4

An informational field you can use according to your organization’s specific requirements.

Alphanumeric, 10 positions; optional.

Width

itm_width

The width measurement for an item. The Height, Length, and Width values determine the cubic volume of an item. This value can be entered in feet or centimeters, or any other measurement as long as it is consistent.

Numeric, 3 positions; optional.

Allow % discount?

itm_allow_discount

This value determines whether certain discounts can be applied to the item.

Y (or blank) = This item is discountable.

N = This item is not discountable.

Alphanumeric, 1 position; optional.

Oversize

itm_oversize_flag

This value determines whether this item is considered an oversized item.

Y = This is an oversized item.

N (or blank) = This is not an oversized item.

Alphanumeric, 1 position; optional.

Description (Item description)

itm_description

The description of the item. This value does not default from the **DFLT ITEM.

Alphanumeric, 40 positions; required.

Second Language Desc

itm_second_language_desc

The second language description for the item.

Alphanumeric, 40 positions; optional.

Exclude From Flex Pay

itm_exclude_from_flex_pay

This value determines whether this item is excluded from deferred and installment payment plans. Valid values are:

Y = Exclude this item from deferred and installment payment plans.

N (or blank) = Do not exclude this item from deferred and installment payment plans.

Alphanumeric, 1 position; optional.

Royalty

itm_royalty

This field indicates whether sales of the item require royalty payments to an author or owner, and is used for query and reporting purposes only. Valid values are:

Y = This is a royalty item.

N (default) = This is not a royalty item.

Alphanumeric, 1 position; required.

Membership

itm_membership

This value indicates that the item represents a membership program, which you can use to generate periodic orders to a customer. Valid values are:

Y = This is a membership item.

N (default) = This is not a membership item.

Alphanumeric, 1 position; optional.

Qty Threshold

itm_qty_threshold

You can use this field to indicate when to trigger an automatic download of item availability information to the E-Commerce Staging Library (G56); from there, the information is available to a web storefront if you use the E-Commerce Interface. This download allows you to display an item’s availability status to web customers if your web storefront supports it.

Note: Although this field displays a 9.0 length in the item upload file, you can only pass a 5-position value. If you pass more than 5 numbers, the edit program displays an error message: Quantity must be limited to 99999.

Numeric, 9 positions; optional.

SVC type

itm_svc_type

A code that indicates the item is a stored value card, and whether the stored value card is a physical or virtual card.

blank (default) = The item is not a stored value card.

P = The item is a physical stored value card.

E = The item is a physical stored value card and, as soon as the stored value card is processed through billing, the system sends an email notification to the recipient card holder on the order, notifying the customer that a stored value card has been purchased and is in the process of being delivered.

R = The item is a stored value card that is activated and fulfilled by a gift card fulfillment system. When you generate a pick slip for a remote fulfillment stored value card, the system sends a remote fulfillment request message to the gift card system; once the gift card system activates and ships the card, the gift card system sends a remote fulfillment confirmation back to CWDirect. See Stored Value Card Remote Fulfillment for an overview.

V = The item is a virtual (non-physical) stored value card.

If you enter a stored value card type, you cannot flag the item as a gift certificate.

See Creating a Stored Value Card Item for more information on setting up a stored value card item.

Alphanumeric, 1 position; optional.

Buyer

buy_buyer

The person who is authorized to make purchases for your company.

Buyer codes are defined in and validated against the Buyer file; see Chapter 17: Working with Buyers (WBUY).

Alphanumeric, 3 positions; optional.

CTN ID # (SKU) (Carton ID)

ctn_id_sku

The type of carton in which this item must be shipped.

Cartons are defined in and validated against the Carton file; see Chapter 11: Working with Cartons (WCTN).

Numeric, 2 positions; optional.

Inventory value G/L#

inventory_value_gl

The general ledger account number to use for inventory transactions.

If you do not pass an account number to the Item file, the system uses the Inventory value G/L # defined in the Warehouse file.

Numeric, 8 positions; optional.

Code (Hazard code)

haz_code

A user-defined code used to categorize an item as a hazardous material that requires special storage and/or handling. Validated against the Item Hazard file; see Chapter 3: Working with Hazardous Item Codes (WHAZ).

Numeric, 2 positions; optional.

Item Class

icl_item_class

A user-defined code that identifies a group of items.

This code is validated against the Item Class file; see Chapter 5: Working with Item Classes (WICL).

An item class code is required if the Require Item Class in Work with Items (F06) system control value is set to Y.

Alphanumeric, 3 positions; required if the Require Item Class in Work with Items system control value is set to Y.

Cycle

icc_cycle

A code that identifies a physical inventory cycle. Validated against the Item Cycle file; see Chapter 6: Working with Item Cycles (WICY).

Alphanumeric, 2 positions; optional.

SKU Group

isg_sku_group

A code that represents a group of common characteristics of a SKU item.

SKU Group codes are defined in and validated against the SKU Group file; see Chapter 41: Working with SKU Groups (WISG).

Numeric, 3 positions; optional.

STS (Status)

ist_item_status

A code that represents an item's status, such as obsolete, discontinued, etc. This information is used for inventory reporting purposes and to select items for physical inventory. See Chapter 7: Working with Item Status (WIST).

Alphanumeric, 1 position; optional.

Location Class

lcl_location_class

A code that represents a location type, such as caged area, carousel area, etc.

Validated against the location class file; see Warehousing Chapter 42: Creating and Maintaining Location Classes (WLCL).

Alphanumeric, 2 positions; optional.

Class (Long SKU class)

lsc_long_sku_class

A code you can use to group items into classes for reporting purposes.

This field is required if the Use Retail Integration (H26) system control value or Require L/S Class (I93) system control value is set to Y.

Long SKU classes are defined in and validated against either the Retail Class file or the Long SKU Class file.

Note: When the Use Retail Integration (H26) system control value is set to Y, the system validates this field against the Retail Class file instead of the Long SKU Class file.

Retail Classes

Long SKU classes that are linked to long SKU departments are called retail classes. If the Use Retail Integration (H26) system control value is set to Y, this field refers to a retail class. Retail classes are department specific. For example, Retail Class 10 may be Ties within Department 20 (Men’s Apparel), but within Department 30 (Women’s Apparel) Retail Class 10 may be Slacks. See the Work with Retail Class Screen.

If you pass a new retail class code to CWDirect and you set the Create Supporting Files during Retail Item Upload (H27) system control value to Y, the system reads the long SKU department code (whether new or existing) with the new retail class code and creates the retail class and description. If you do not pass a long SKU department code and a long SKU department code does not default from the **DFLT ITEM, the system displays an error message: Long SKU Department required.

If you have the Use Retail Integration (H26) system control value set to Y, but the Create Supporting Files during Retail Item Upload (H27) system control value is set to N, the system still requires a retail class and a long SKU department code, but you must use existing codes and combinations because the system does not create any supporting file values. See Item Upload Processing for a listing of primary and supporting files. If you enter an invalid combination of codes or do not enter a long SKU department code, the system displays an error message: Invalid Long SKU Class/Department combination for item.

If you leave this field blank and a retail class code does not default from the **DFLT ITEM, the system displays an error message: Item Long SKU Class required.

Long SKU Classes:

If the Use Retail Integration (H26) system control value is set to N, this field refers to long SKU classes. Long SKU classes have only one value to an organization. For example, Long SKU Class 15 may be Men’s Shoes, and remains Men’s Shoes regardless of the department. For more information see Chapter 8: Working with Long SKU Classes (WLSC).

Item Identifier

For the LS Key Type, the system uses the value in this field combined with the L/S department, L/S vendor, and L/S style values, and optionally, the L/S color, L/S size, L/S width and SKU code values to identify the CWDirect item/SKU associated with the item upload record.

If you do not have authority to the Maintain Long SKU Values in MITM (B05) secured feature, you cannot enter or change this value.

Numeric, 4 positions; required if SCV H26 or SCV I93 is set to Y and you are using an 01 record type or an LS key type.

Department

lsd_department

A code used to group items into departments for reporting purposes.

This field is required if the Use Retail Integration (H26) system control value or Require L/S Department (I92) system control value is set to Y.

Long SKU departments are defined in and validated against the Long SKU Department file; see Chapter 9: Working with Long SKU Departments (WLSD).

When using Retail Integration from an external system into CWDirect, long SKU classes are linked to long SKU departments and become retail classes. If you set the Create Supporting Files during Retail Item Upload (H27) system control value to Y, you can pass a new or existing long SKU department code with a new or existing retail class code and the system creates the long SKU department and the associated retail class. If you do not pass a long SKU department code and one does not default, the system displays an error message: Long SKU Department required.

If you have the Use Retail Integration (H26) system control value set to Y, but the Create Supporting Files during Retail Item Upload (H27) system control value is set to N, the system still requires a long SKU department code and a retail class code, but you must use existing codes and combinations because the system does not create any new supporting file values. See Item Upload Processing for a listing of primary and supporting files. If you enter an invalid combination of codes or do not enter a long SKU department code, the system displays an error message: Invalid Long SKU Class/Department combination for item.

If the Require Long SKU Division with Long SKU Department (E85) system control value is set to Y, you must enter a value in the L/S Division field or use a L/S department code that already has a L/S division code assigned to it.

Item Identifier

For the LS Key Type, the system uses the value in this field combined with the L/S class, L/S vendor, and L/S style values, and optionally, the L/S color, L/S size, L/S width and SKU code values to identify the CWDirect item/SKU associated with the item upload record.

If you do not have authority to the Maintain Long SKU Values in MITM (B05) secured feature, you cannot enter or change this value once passed to CWDirect.

Numeric, 4 positions; required if SCV H26 or SCV I92 is set to Y and you are using an 01 record type or an LS key type.

L/S Division

ldv_ls_division

A code that represents a long SKU division. L/S divisions are used in conjunction with L/S departments and L/S classes for reporting purposes and to create a company or entity hierarchy. Long SKU division codes are defined in and validated against the L/S Division file.

If the Require Long SKU Division with Long SKU Department (E85) system control value is set to Y, you must specify a long SKU division when the long SKU department is either new, or does not have a L/S division associated with it. If the long L/S department already exists and is already assigned a L/S division, you do not need to enter a L/S division code.

If the L/S division is new and you set the Create Supporting Files during Retail Item Upload (H27) system control value to Y, the system creates a new code in the L/S Division file. If this system control value is set to N and you pass a new code, the system tries to default a L/S division value from the **DFLT ITEM. If you have not defined a default value for L/S division, the system displays an error message: Invalid L/S Division.

Alphanumeric, 3 positions; required if BOTH the Require L/S Division with L/S Department (E85) system control value is set to Y AND you are passing a new L/S department value.

UOM (Unit of Measure)

uom_type_sku

A standard by which an item is sold. Typical units of measure include:

EA = each

IN = inches

C12 = case of 12

This value is validated against the Unit of Measure file (see Chapter 10: Working with Units of Measure (WUOM)) and defaults from the Default Item Unit of Measure (B33) system control value, if a value is specified.

Note: The system never defaults a value from the Unit of Measure field for the **DFLT ITEM even if you do not enter a value in this field and do not specify a value in the Unit of Measure (B33) system control value. See Creating Default and Change Item/SKU Upload Values: **DFLT ITEM and **DFTCHG.

Alphanumeric, 3 positions; optional.

Vendor #

vnd_vendor_nbr

A code that defines the vendor or supplier of an item.

Vendor codes are defined in and validated against the Vendor file; see Chapter 19: Working with Vendors (WVEN).

If the Use Data Warehouse (G94) system control value is set to Y, the system requires you to define a vendor number for an item/SKU.

Numeric, 7 positions; optional.

Ship Via Code

via_ship_via_code

A code that represents the carrier that must be used when shipping this item.

Numeric, 2 positions; optional.

Manufacturer Vendor

manufacturer_vendor

The vendor who manufactured the item.

Numeric, 7 positions; optional.

Entity Number

itm_ent_entity_number

A business unit within your company that is held accountable for sales performance; for example, mail order, retail, or e-commerce.

If the system control value Require Entity in Item File (G44) is set to Y, you must enter an entity code for each item you set up; entity codes for items and SKUs are defined at the item level. This value is informational only.

Numeric, 3 positions; optional.

Season

sea_season

Defines the season associated with this item, such as spring.

Season codes are defined in and validated against the Season file; see Marketing Chapter 3: Working with Season Codes (WSEA).

Alphanumeric, 3 positions; optional.

Collating Seq #

sku_collating_sequence

The sequence number used to determine the order in which SKUs sort. You can use the sort sequence to display SKUs in a different order, such as by size, rather than alphanumerically by SKU code.

This field is required if the Require Sort Sequence Number in the SKU File (F23) system control value is set to Y.

See SKU Sort Sequence Numbers for an overview.

Numeric, 5 positions; required if the Require Sort Sequence Number system control value is set to Y.

Compatibility

sku_compatibility

A user-defined code assigned to an item/SKU.

Alphanumeric, 3 positions; optional.

SKU Last purchase cost

sku_last_purchase_cost

The cost of the item from the most recent purchase order, including any discounts, surcharges, or additional charges.

Numeric, 11 positions with a 4-place decimal; optional.

Cub val (Cubing value)

sku_cubing_value_override

The cubic volume of the SKU, which overrides the cubic volume defined at the base item level.

Numeric, 7 positions with a 1-place decimal; optional.

SKU Description

sku_description

The description of the SKU element. If no value is passed, the SKU description is blank.

Alphanumeric, 40 positions; optional.

Subscription

sku_subscription

This value indicates whether the item is a subscription item.

Valid values are:

Y = Item is a subscription item

N = Item is not a subscription item

If you identify an item as a subscription item, you must:

• enter a Y in the Non-Inventory field to indicate that inventory levels are not maintained for the subscription item and that customer will be billed (the full price of the subscription) immediately through Express Billing.

• create a record for the subscription in the Item Subscriptions file to define the particulars of the subscription, such as the current issue number, length of subscription (number of intervals and number of days between issues).

See Chapter 12: Working with Item Subscriptions (WISB).

Alphanumeric, 1 position; optional.

Height Override

sku_height_override

The height measurement for a SKU. The Height, Length, and Width values are used to determine the cubic volume of an item/SKU. You can enter the height in feet or centimeters, or any other measurement as long as it is consistent.

Numeric, 3 positions; optional.

Length Override

sku_length_override

The length measurement for a SKU. The Height, Length, and Width values are used to determine the cubic volume of an item/SKU. You can enter this value in feet or centimeters, or any other measurement as long as it is consistent.

Numeric, 3 positions; optional.

List Price

sku_list_price

The system uses this price when you process item to item transfers (inventory transaction code = G).

Numeric, 7 positions with a 2-place decimal; optional (required if you process item to item transfers).

Long SKU Color

sku_long_sku_color

A code, typically used in a retail environment, that represents the color portion of the long SKU code. This value is used for reporting purposes.

Item Identifier

For the LS Key Type, the system uses the value in this field combined with the L/S department, L/S class, L/S vendor, and L/S style values, and optionally, the L/S size, L/S width and SKU code values to identify the CWDirect SKU associated with the item upload record.

If you do not have authority to the Maintain Long SKU Values in MITM (B05) secured feature, you cannot enter or change this value in CWDirect.

Numeric, 5 positions; optional.

Long SKU Size

sku_long_sku_size

A code, typically used in a retail environment, that represents the size portion of the long SKU code. This value is used for reporting purposes.

Item Identifier

For the LS Key Type, the system uses the value in this field combined with the L/S department, L/S class, L/S vendor, and L/S style values, and optionally, the L/S color, L/S width and SKU code values to identify the CWDirect SKU associated with the item upload record.

If you do not have authority to the Maintain Long SKU Values in MITM (B05) secured feature, you cannot enter or change this value in CWDirect.

Numeric, 5 positions; optional.

Long SKU Width

sku_long_sku_width

A code, typically used in a retail environment, that represents the width portion of the Long SKU code. This value is used for reporting purposes.

Item Identifier

For the LS Key Type, the system uses the value in this field combined with the L/S department, L/S class, L/S vendor, and L/S style values, and optionally, the L/S color, L/S size and SKU code values to identify the CWDirect SKU associated with the item upload record.

If you do not have authority to the Maintain Long SKU Values in MITM (B05) secured feature, you cannot enter or change this value in CWDirect.

Numeric, 5 positions; optional.

Lowest Price

sku_lowest_price

The lowest recommended sale price for the item/SKU; however, the item/SKU can be sold at a lower price.

Numeric, 7 positions with a 2-place decimal; optional.

Max Qty for Location

sku_max_for_location

The SKU's recommended maximum number of units to be stored in the primary pick location.

The primary pick location refers to the code that you pass in the Location field.

Numeric, 7 positions; optional.

Max Qty for Warehouse

sku_max_for_warehouse

The SKU's recommended maximum number of units for the warehouse specified in the Whs (Warehouse) field.

Numeric, 7 positions; optional.

Min Qty for Location

sku_min_for_location

The SKU's recommended minimum quantity to be stored in the primary pick location.

The primary pick location refers to the code that you pass in the Location field.

Numeric, 7 positions; optional.

Min Qty for Warehouse

sku_min_for_warehouse

The SKU's recommended minimum number of units for the warehouse specified in the Whs (Warehouse) field.

Numeric, 7 positions; optional.

SKU Gift Certificate

sku_gift_certificate

This value determines whether or not this SKU qualifies as a gift certificate.

Y = The SKU represents a gift certificate item.

N (or blank) = The SKU does not represent a gift certificate item.

See Customer Service Chapter 122: Working with Gift Certificates.

Alphanumeric, 1 position; optional.

Reserve Qty Limit

sku_reserve_qty_limit

If the order quantity exceeds this amount, the system does not reserve the item/SKU and displays a Backorder Reason.

Numeric, 7 positions; optional.

Restrict Orders

sku_restrict_orders

This value defines whether you can accept an order for this item/SKU in Order Entry and whether demand is captured.

Y = The operator cannot accept an order for this item/SKU.

N (or blank) = The operator can accept an order for this item/SKU.

Alphanumeric, 1 position; optional.

Retail Ref #

sku_retail_ref

This value represents the retail reference or alternate product number. You can use this value to cross-reference an item/SKU to an external system, such as through the Generic Inventory Transaction Upload or the Generic Order Interface (Order API).

Numeric, 15 positions; optional.

Selling Weight Override

sku_selling_weight_ovrrde

The system uses this value to calculate the freight charge on a SKU when the Freight method on the order is Freight by weight or Freight by order weight, as defined in the Source Code. This value overrides the selling weight, if any, defined at the base item level.

Numeric, 7 positions with a 3-place decimal; optional.

Short SKU

sku_short_sku

A unique number that the system assigns to all items and SKUs unless you pass a value for the item/SKU in the item upload.

Numeric, 7 positions; optional.

User field 1

sku_user_field_1

An informational field you can use according to your organization's specific requirements.

Alphanumeric, 10 positions; optional.

User field 2

sku_user_field_2

An informational field you can use according to your organization’s specific requirements.

Alphanumeric, 10 positions; optional.

User field 3

sku_user_field_3

An informational field you can use according to your organization’s specific requirements.

Alphanumeric, 10 positions; optional.

Weight Override

sku_weight_override

The actual shipping weight of the SKU. The system may use this value to calculate carton weights and to determine your shipping charges if you perform manual confirmation and use cubing.

Numeric, 7 positions with a 3-place decimal; optional.

Width Override

sku_width_override

The width measurement for an SKU. The Height, Length, and Width values are used to determine the cubic volume of an item/SKU. You can enter this value in feet or centimeters, or any other measurement as long as it is consistent.

Numeric, 3 positions; optional.

Sale Credit Flag

sku_sale_credit_flag

This field is not currently implemented. Valid values are Y and N.

Alphanumeric, 1 position; optional.

Harmonize Code

sku_harmonize_code

A code that prints on customs documents for international shipments.

Alphanumeric, 16 positions; optional.

Coord group (Coordinate group items?)

sku_coordinate_group

A code that may be assigned to item/SKUs to ensure that certain item/SKUs ship together when ordered together.

Numeric, 3 positions; optional.

Average Cost

sku_average_cost

The cost of a SKU, or of a non-SKU’d item.

General ledger update

If you change this cost and the Costing Method (A25) is set to AVERAGE, the system updates the General Ledger Interface file to reflect the change in inventory valuation. See * = Change Average or Standard Cost for an overview.

Tracking cost changes

If you change this cost, the Costing Method (A25) is set to AVERAGE, and the Track Cost Changes (J69) system control value is set to Y, the system tracks the cost change in the Cost Change Audit file. See Reviewing Item/SKU Cost History for more information on how the system tracks cost changes differently depending on your costing method, and how to review cost change history.

Numeric, 11 positions with a 4-place decimal; optional.

FIFO Cost

sku_fifo_cost

If you use FIFO costing, the system updates the weighted average FIFO cost for inquiry and reporting purposes (for example, the FIFO Activity Report lists this cost). The weighted average FIFO cost is stored in the FIFO cost field in the SKU file. See FIFO Costing Overview for background.

Tracking cost changes

If you change this cost, the Costing Method (A25) is set to FIFO, and the Track Cost Changes (J69) system control value is set to Y, the system tracks the cost change in the Cost Change Audit file. See Reviewing Item/SKU Cost History for more information on how the system tracks cost changes differently depending on your costing method, and how to review cost change history.

Numeric, 11 positions with a 4-place decimal; optional.

LIFO Cost

sku_lifo_cost

A method to determine the cost of an item. This field is not currently implemented.

Numeric, 11 positions with a 4-place decimal; optional.

Standard Cost

sku_standard_cost

A method to determine the cost of an item. When you use the standard costing method, the system does not calculate a new standard cost automatically.

General ledger update

If you change this cost and the Costing Method (A25) is set to STANDARD, the system updates the General Ledger Interface file to reflect the change in inventory valuation. See * = Change Average or Standard Cost for an overview.

Tracking cost changes

If you change this cost, the Costing Method (A25) is set to STANDARD, and the Track Cost Changes (J69) system control value is set to Y, the system tracks the cost change in the Cost Change Audit file. See Reviewing Item/SKU Cost History for more information on how the system tracks cost changes differently depending on your costing method, and how to review cost change history.

Numeric, 11 positions with a 4-place decimal; optional.

Second language description

sku_second_lang_desc

This field is not currently implemented.

Alphanumeric, 40 positions; optional.

VAT exempt flag

sku_vat_exempt_flag

Indicates if the item is exempt from VAT.

Y = The item is exempt from VAT.

N = The item is not exempt from VAT.

Alphanumeric, 1 position; optional.

Second Compatibility

sku_second_compat

This field is not currently implemented.

Alphanumeric, 3 positions; optional.

Hidden Tax Amount

sku_hidden_tax_amnt

The amount to include in the Hidden tax field for an item subject to VAT.

Numeric, 7 positions with a 2-place decimal; optional.

Hidden Tax Percent

sku_hidden_tax_percent

The percentage to use when calculating hidden tax for an item subject to VAT.

Numeric, 5 positions with a 2-place decimal; optional.

Suppress B/O Card

sku_suppress_bo_card

This field indicates whether to produce a backorder card for the SKU. Valid values are:

Y = Suppress normal backorder card generation for this item.

N or blank = Do not suppress normal backorder card generation.

If you leave this field blank, the system defaults the value from the Unconditional Suppression of Backorder Card (F19) system control value. The system does not default a value from the **DFLT ITEM even if this system control value is blank.

Alphanumeric, 1 position; optional.

Projected Returns

sku_projected_returns

The number of units you expect to receive in returns for the item.

Numeric, 7 positions; optional.

User Field 4

sku_user_field_4

An informational field you can use according to your organization's specific requirements.

Alphanumeric, 5 positions; optional.

User Field 5

sku_user_field_5

An informational field you can use according to your organization’s specific requirements.

Alphanumeric, 5 positions; optional.

Returnable

sku_returnable

This field indicates whether the item is eligible for return; informational only. Valid values are:

Y = The item is eligible for return

N (default) = This item is not eligible for return

Alphanumeric, 1 position; required.

Retail X-Ref #

sku_retail_x-ref

This value represents the UPC (Universal Product Code) or Retail Reference number for the SKU. This value is used for informational purposes. If you want the system to create or identify a SKU with an UPC code, you must enter values in the Fields for 08 Item UPC Record Type or a value in the UPC field.

Numeric, 10 positions; optional.

L/S Style

sku_ls_style

A user-defined field that represents the long SKU style defined for the SKU.

This field is required if the Require L/S Style (I94) system control value is set to Y; additionally, the system validates that the long SKU style is a unique value.

If you do not have authority to the Maintain Long SKU Values in MITM (B05) secured feature, you cannot enter or change this value in CWDirect.

Alphanumeric, 20 positions; optional.

L/S Vendor

sku_ls_vendor

A user-defined field that represents the long SKU vendor for the item/SKU.

If you do not have authority to the Maintain Long SKU Values in MITM (B05) secured feature, you cannot enter or change this value in CWDirectr.

Alphanumeric, 7 positions; optional.

Excl Store Restock

sku_excl_store_restock

This value indicates whether the item is eligible for retail store restock. Valid values are:

Y = The item is excluded from retail store restock.

N or blank = The item is available for retail store restock.

See Warehousing Chapter 108: Working with Retail Store Restock (WRSR).

Alphanumeric, 1 position; optional.

Original Retail Price

sku_original_retail_price

The original price of the item at the retail store.

Numeric, 7 positions with a 2-place decimal; optional.

GTIN

sku_gtin

This field is currently not implemented.

Numeric, 14 positions; optional.

Commodity Code

sku_commodity_code

This field is currently not implemented.

Numeric, 8 positions; optional.

ABC Code

abc_code

This code classifies an item/SKU based on sales volume.

Alphanumeric, 1 position; optional.

Carton ID #

ctn_id_sku_rec

The type of carton in which this item must ship.

Cartons are defined in and validated against the Carton file. See Chapter 11: Working with Cartons (WCTN).

Numeric, 2 positions; optional.

Freq Code (Frequency code)

frq_frequency_code

This code classifies the performance of a SKU based on the number of picks generated for the SKU over a month's time. Validated against the Frequency file; see Chapter 2: Working with Frequency Codes (WFRQ). This code is informational only.

Alphanumeric, 1 position; optional.

Whs (Warehouse)

whs_warehouse

A code that represents a warehouse where this item is stocked.

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

Numeric, 3 positions; required.

Location

loc_location

A code that represents an area within the warehouse that contains the item/SKU. Sometimes referred to as the “primary primary.” Validated against the Location file.

Alphanumeric, 7 positions; optional.

Soldout control code

slc_code

A code that represents how you determine when an item/SKU is soldout.

You can define a value in the Default Soldout Control Code (D72) system control value to default automatically when you create items and SKUs; however, you can override this value.

See Chapter 113: Working with Soldout Controls (WSLD).

Download to web storefront? If you change the soldout control setting for an item that has been downloaded to the web storefront, the system sends current availability information for the item. See E-Commerce Item Availability Processing for an overview.

Alphanumeric, 2 positions; optional.

UOM Type

uom_type_sku_rec

A standard by which an item/SKU is sold.

Validated against the Unit of Measure file (see Chapter 10: Working with Units of Measure (WUOM)) and can default from the Default Item Unit of Measure (B33) system control value.

Alphanumeric, 3 positions; optional.

Status

sku_ist_item_status

A code that represents a SKU's status, such as obsolete, discontinued, sold out, etc. This information is used for inventory reporting purposes only. The status defined at the SKU level overrides the status defined at the base item level. See Chapter 7: Working with Item Status (WIST).

Alphanumeric, 1 position; optional.

Category

sku_itc_category

A code assigned to the SKU to classify and group like item/SKUs for use in the Item Relationships function. Validated against the Item Category file; see Chapter 4: Working with Item Category Codes (WITG).

Alphanumeric, 4 positions; optional.

Prep Code

sku_prp_prep_code

A code used to indicate any special preparation or handling required for the SKU. This field is informational only.

Prep codes are defined in and validated against the Prep Code file. See Chapter 15: Working with Prep Codes (WPRC).

Alphanumeric, 2 positions; optional.

Country of Origin

sku_country_of_origin

A code representing the country where the SKU originated.

Country codes are defined in and validated against the Country file; see Customer Service Chapter 14: Setting Up the Country File (WCTY).

Alphanumeric, 3 positions; optional.

L/S Class

sku_lsc_ls_class

A code you can use to group items into classes for reporting purposes. Long SKU classes are defined in and validated against the Long SKU Class file; see Chapter 8: Working with Long SKU Classes (WLSC).

If the Use Retail Integration (H26) system control value is set to Y, long SKU classes are linked to long SKU departments and are called retail classes. Retail classes are department specific whereas regular long SKU classes are unique and remain constant across departments. For this reason, when the Use Retail Integration (H26) system control value is set to Y, you can only enter a retail class in this field that is assigned to the base item’s long SKU department. If you enter a long SKU class that is not linked to the base item’s long SKU department, the system does not let you proceed and displays an error message: L/S Class (xxxx) was not found in L/S Department (xx).

Retail classes are defined in and validated against the Retail Class file; see the Work with Retail Class Screen for more information.

If you do not have authority to the Maintain Long SKU Values in MITM (B05) secured feature, you cannot enter or change this value.

Numeric, 4 positions; optional.

Zone Reservation

sku_zrc_zone_reservation

A code assigned to weather-sensitive items/SKUs such as plant stock to insure that the items ship to different regions of the country within time windows suited to the regions.

See Fulfillment Chapter 53: Shipping Zone Reservation Overview.

Alphanumeric, 4 positions; optional.

Virtual card type

itm_virtual_card_type

Defines the associated virtual card type for this stored value card item in ValueCard. The card type in ValueCard identifies whether you can define an expiration date for a card when the card is activated.

When you generate a pick slip for an order containing a virtual stored value card, the system automatically assigns a stored value card number to the virtual card, using the next available number from the Virtual Card Number File (FLSVCA). When assigning a number to a virtual stored value card, the system first determines the virtual card type defined for the item.

• If a virtual card type is defined for the stored value card item, the system assigns the next available number in the Virtual Card Number file that matches the virtual card type associated with the item.

• If a virtual card type is not defined for the stored value card item, the system assigns the next available number in the Virtual Card Number file that has a blank card type.

• If a virtual card type is defined for the stored value card item and there are no available card numbers in the Virtual Card Number file for that card type, or a virtual card type is not defined for the stored value card item and there are no available card numbers in the Virtual Card Number file with a blank card type, then the system does not assign a card number to the stored value card item. If a number is not available to assign to the card, the entire order line containing the stored value card item is not billed and the order prints on the Stored Value Card Assignment Errors Report.

If you enter a card type in this field it must match the associated card type in ValueCard. Otherwise, you might send the customer the wrong virtual card number and expiration date. In addition, ValueCard requires that a stored value card is associated with the merchant that created it. Virtual card types must be unique for each merchant and the card type defined for a stored value card item must point to the correct card type in ValueCard for the correct merchant.

You can only enter a virtual card type if the SVC type field is set to V.

Available in XML version: 4.0 (11.5 of CWDirect).

Alphanumeric, 10 positions; optional.

SKU drop ship

sku_drop_ship

Indicates whether you ship the SKU from your warehouse, or have your vendor ship it to the customer directly.

You can flag an item as drop ship at the item level and SKU level. The setting at the SKU level overrides the setting at the item level. If the setting at the SKU level is blank, the system uses the setting at the item level.

Valid values are:

Y = Drop ship SKU. When a customer orders the SKU, you order the SKU from your vendor and the vendor ships it directly to your customer. You can only flag a SKU as drop ship if the Drop ship flag at the item level is Y.

N = Non-drop ship SKU. You ship the SKU from your warehouse. You can flag a SKU as non-drop ship if the Drop ship flag at the item level is Y, N or blank.

Blank = The drop ship setting has not been defined at the SKU level; instead, the system uses the drop ship setting at the item level to determine if the SKU is a drop ship item.

Available in XML version: 4.0 (11.5 of CWDirect).

Alphanumeric, 1 position; optional.

Fields for 03 Item Offer Record Type

The 03 Item Offer Record Type can include item offer information and item alias information.

To Create an Item Offer without an Item Alias

At minimum, you must define:

• Keys to the File: Fields Required for all Record Types

• Offer for Item Offer (the item offer cannot already exist)

• Leave the 03 Item Offer Record Type - Item Alias Fields blank.

The system creates the item offer and does not create an item alias for the item offer.

To Create an Item Offer and Item Alias

At minimum, you must define:

• Keys to the File: Fields Required for all Record Types

• Offer for Item Offer (the item offer cannot already exist)

• Page #

• Alias Item

The system creates the item offer and the specified item alias for the item offer.

To Create an Item Alias for an Existing Item Offer

At minimum, you must define:

• Keys to the File: Fields Required for all Record Types

• Offer for Item Offer (the item offer must already exist)

• Page #

• Alias Item (the page number and alias item combination cannot already exist)

The system creates the item alias for the specified item offer.

To Change an Item Offer without an Item

A minimum, you must define:

• Keys to the File: Fields Required for all Record Types

• Offer for Item Offer (the item offer must already exist)

• At least one Item Offer field in addition to the Offer for Item Offer

• Leave the 03 Item Offer Record Type - Item Alias Fields blank.

The system updates the item offer and does not update any item alias records defined for the item offer.

To Change an Item Offer and Item Alias

At minimum, you must define:

• Keys to the File: Fields Required for all Record Types

• Offer for Item Offer (the item offer must already exist)

• At least one Item Offer field in addition to the Offer for Item Offer

• Seq #

• Page #

• Alias Item (the page number and alias item combination must already exist)

• At least one item alias field in addition to the Seq #, Page #, and Alias Item

The system updates the item offer and the specified item alias for the item offer.

Note: If you wish to change an item alias for an item offer, you must include the full item offer information. If a change record for an 03 Item Offer Record Type includes item alias information and does not include item offer information for the specified item offer, the system updates the item alias, but also updates the fields for the item offer to blank. For example, if a change record for an 03 Item Offer Record Type includes the Keys to the File: Fields Required for all Record Types, Offer for Item Offer, Seq #, Page #, Alias Item, and Square Inch, the system updates the Square inch field for the specified item alias, but also updates the fields for the specified item offer to blank. If the Pickup/New field for the item offer was set to N (New) and you left this field blank in the item upload record, the system updates this field to blank.

To Delete an Item Offer

At minimum, you must define:

• Keys to the File: Fields Required for all Record Types (Note: The Request Type must be D)

• Offer for Item Offer (the item offer must already exist)

• Leave the 03 Item Offer Record Type - Item Alias Fields blank

The system deletes the item offer and also deletes any item alias records that are defined for the item offer.

To Delete an Item Alias without Deleting the Item Offer

At minimum, you must define:

• Keys to the File: Fields Required for all Record Types (Note: The Request Type must be D)

• Offer for Item Offer (the item offer must already exist)

• Seq #

• Page #

• Alias Item (the page number and alias item combination must already exist)

The system deletes the specified item alias for the item offer, but does not delete the item offer.

For more information: See:

• Item Offer errors

• 03 Item Offer Record Type - Item Alias Fields

• Item Alias errors

Offer for Item Offer

iup_offer_for_item_offer

The code for the offer (catalog) in which the item/SKU appears. Validated against the Offer file. See Marketing Chapter 2: Working with Offers (WOFR).

Alphanumeric, 3 positions; required (if other information is entered).

Cost

iof_cost

The cost to include the item in the offer.

Numeric, 7 positions with a 2-place decimal; optional.

Expected Return Pct

iof_expected_return_pct

The percentage of returns you expect to receive for the item/offer.

Numeric, 5 positions with a 2-place decimal; optional.

G/W Flag

iof_gift_wrap_flag

This value indicates whether this SKU is eligible for gift wrap. If the Gift Wrap Default (F07) system control value is set to Y, this field defaults to Y, although you can override it; otherwise, this field defaults to N.

Y (or blank) = The item/SKU can be gift wrapped.

N = In this offer, the item/SKU cannot be gift wrapped.

Alphanumeric, 1 position; optional.

G/W Price

iof_gift_wrap_price

The price for gift wrapping the item. The G/W field must be set to Y. The gift wrap price is charged for each unit of this SKU that is gift wrapped.

Numeric, 7 positions with a 2-place decimal; optional.

Page #

iof_page

The primary page number on which the item/SKU displays in the offer.

Numeric, 5 positions; optional.

Projected Units

iof_projected_units

The number of units of this item/SKU that you expect to sell in an offer.

Numeric, 7 positions; optional.

S/H Price

iof_sh_price

The price to charge for special handling.

Numeric, 7 positions with a 2-place decimal; optional.

S/H Flag

iof_special_handling

This value indicates whether this item is eligible for any type of special handling in this offer (such as, monogramming, hemming, etc.).

Y = This item is eligible for special handling.

N (default) = This item is not eligible for special handling.

If this field is set to Y and there is a default special handling code defined (see below), OR if you specify special handling for an item in order entry, you advance to the Work with Special Handling Screen or the Work with Custom Special Handling Screen; however, if the special handling code’s:

• Suppress S/H window field is set to Y: the system adds the special handling code and charge to the item without displaying the special handling screen.

• Bypass S/H field is set to Y: you do not advance automatically to the special handling screen unless you enter the special handling code when entering the item; however, you can still advance to the special handling screen by entering 8 next to the item.

See Special Handling Overview for more information.

Alphanumeric, 1 position; optional.

Square Inches

iof_square_inches

The square inches (not the percentage) that the item/SKU occupies on the catalog page or in the offer.

Numeric, 5 positions with a 2-place decimal; optional.

Freight

iof_freight

The freight amount to be charged for this item/SKU. The value in this field is multiplied by the quantity ordered to determine the freight charge for this item. Only used if Freight by item or Flat Rate by item has been established in Freight method field for the Source Code file.

Numeric, 6 positions with a 2-place decimal; optional.

Hidden Freight

iof_hidden_freight

This value is used only with item/SKU level freight methods, such as: Flat rate by item, flat rate by item quantity, flat rate by item source, and by item.

Hidden freight represents the portion of the item's catalog price that is used for freight.

Numeric, 6 positions with a 2-place decimal; optional.

Spread

iof_spread

Indicates the setting of Sale item flag for the item offer or SKU offer as follows:

Y = The item/SKU is flagged as a sale item in the item offer or SKU offer.

N (or blank) = The item/SKU is not flagged as a sale item in the item offer or SKU offer.

Note: Although this field is 3 positions, only the one position required to set the flag should be used.

Alphanumeric, 3 positions; optional.

Volume Discount Y/N

iof_volume_discount_yn

This value indicates whether this item is eligible for an end-of-order discount that applies when you accept the order during Order Entry.

Y = The item/SKU is eligible for the volume discount.

N (or blank) = The item/SKU is not eligible for the volume discount.

See Item Volume Discounting.

Alphanumeric, 1 position; optional.

Coupon Disc %

iof_coupon_disc

This value represents the amount that is subtracted from the price when the SKU is ordered from this offer.

Numeric, 7 positions with a 2-place decimal; optional.

Coupon Effective Date

iof_coupon_effective_date

The date the coupon is effective until (i.e., the date expires).

Numeric, 7 positions (CYYMMDD format); optional.

Feature/option

iof_feature_option

This value indicates whether the item is considered a featured or optional item in a depiction.

Valid values are:

F = Item is the featured item in the depiction

O = Item is an optional item in the depiction

Alphanumeric, 1 position; optional.

Pickup/new

iof_pickup_new

This value indicates whether the item has been carried over from a previous offer or is new to your product offerings.

Valid values are:

P = Item is a pickup item, previously sold in an offer

N = Item is a new addition to your offer

Alphanumeric, 1 position; optional.

Pop Up Message 1-4

iof_pop_up_message_1-4

For optional message lines.

Alphanumeric, 30 positions each; optional.

Warranty Item?

iof_warranty_item

This field defines whether the item in this offer is a warranty item.

Valid values are:

Y = The item in this offer is a warranty item. When an operator adds this item to an order in order entry or order maintenance, the system adds the item to the order at no charge.

N or blank = The item in this offer is not a warranty item.

Alphanumeric, 1 position; optional.

Require Add Reason

iof_required_add_reason

This field defines whether an Order addition reason code is required when the item in this offer is added to an order in order entry or order maintenance.

Valid values are:

Y = The item in this offer requires an add reason code when the item is added to an order in order entry or order maintenance.

N = The item is this offer does not require an add reason code when the item is added to an order in order entry or order maintenance.

Alphanumeric, 1 position; optional.

Curve Code

crv_code

A code that represents the item's expected selling pattern in this offer. Validated against the Projection Curve file. See Marketing Chapter 26: Working with Projection Curves (WCRV).

Numeric, 3 positions; optional.

Add’l chg code

add_addl_chg_code

The additional charge code associated with the type of special handling you are offering for the item.

The system validates that the additional charge code is defined as special handling, with a Type of standard or custom; the system handles each type in a different way. See Special Handling Overview for more information.

If you enter a special handling code here, you advance to the Work with Special Handling Screen or Work with Custom Special Handling Screen automatically in order entry; however, if the special handling code’s:

• Suppress S/H window field is set to Y: the system adds the special handling code and charge to the item without displaying the special handling screen.

• Bypass S/H field is set to Y: you do not advance automatically to the special handling screen unless you enter the special handling code when entering the item; however, you can still advance to the special handling screen by entering 8 next to the item.

See Special Handling Overview for more information.

Alphanumeric, 2 positions; optional.

Add-On Code

iof_aoc_add-on_code

This field is not currently implemented.

Alphanumeric, 3 positions; optional.

03 Item Offer Record Type - Item Alias Fields

The following fields are part of the Fields for 03 Item Offer Record Type, but are used to add, change, or delete an item alias for an offer. See Fields for 03 Item Offer Record Type for instructions on how to create, change, and delete item alias records for an item offer.

Available in XML version: 5.0 (version 12.5 of CWDirect).

Seq #

pla_seq_nbr

The sequence number assigned to the item alias record in the Page Letter Alias file.

A sequence number is required if you are changing or deleting an existing item alias record. For add records, the system automatically assigns a sequence number to the new item alias record.

Numeric, 3 positions; required to change or delete an item alias.

Page Letter

pla_page_letter

This field is not currently implemented.

Alphanumeric, 6 positions; optional.

Page #

pla_page

The number of the page where the alias appears in the catalog.

Numeric, 5 positions; required to create, change or delete an item alias.

Cost

pla_cost

The cost to include the alias on that page in the offer.

Numeric, 11 positions with a 4-place decimal; optional.

Square Inch

pla_square_inch

The number of square inches the alias occupies on the catalog page.

Numeric, 5 positions with a 2-place decimal; optional.

Alias Item

pla_alias

The alternate item code for an actual item. You can create multiple aliases for an item offer, but each alias must have a unique code.

Alphanumeric, 12 positions; required to create, change or delete an item alias.

Fields for 04 SKU Offer Record Type

See SKU Offer errors.

Offer for SKU Offer

iup_offer_for_sku_offer

The code for the offer (catalog) in which the item/SKU appears. Validated against the Offer file. See Marketing Chapter 2: Working with Offers (WOFR).

Alphanumeric, 3 positions; required (if other information is entered).

Cost

sko_cost

The cost to include the item in the offer.

Numeric, 7 positions with a 2-place decimal; optional.

Expected Return Pct

sko_expected_return_pct

The percentage of returns you expect to receive for the item/offer.

Numeric, 5 positions with a 2-place decimal; optional.

G/W Flag

sko_gift_wrap_flag

This value indicates whether this SKU is eligible for gift wrap. If the Gift Wrap Default (F07) system control value is set to Y, this field defaults to Y, although you can override it; otherwise, this field defaults to N.

Y (or blank) = The item/SKU can be gift wrapped.

N = In this offer, the item/SKU cannot be gift wrapped.

Alphanumeric, 1 position; optional.

Page #

sko_page

The primary page number on which the item/SKU appears in the offer.

Numeric, 5 positions; optional.

Projected Units

sko_projected_units

The number of units of this item/SKU that you expect to sell in an offer.

Numeric, 7 positions; optional.

S/H Price

sko_sh_price

The price to charge for special handling.

Numeric, 7 positions with a 2-place decimal; optional.

S/H Flag

sko_special_handling_flag

This value indicates whether this item is eligible for any type of special handling in this offer (such as, monogramming, hemming, etc.).

Y = This item is eligible for special handling.

N (default) = This item is not eligible for special handling.

If this field is set to Y and there is a default special handling code defined (see below), OR if you specify special handling for an item in order entry, you advance to the Work with Special Handling Screen or the Work with Custom Special Handling Screen; however, if the special handling code’s:

• Suppress S/H window field is set to Y: the system adds the special handling code and charge to the item without displaying the special handling screen.

• Bypass S/H field is set to Y: you do not advance automatically to the special handling screen unless you enter the special handling code when entering the item; however, you can still advance to the special handling screen by entering 8 next to the item.

See Special Handling Overview for more information.

Alphanumeric, 1 position; optional.

Square Inches

sko_square_inches

The square inches (not the percentage) that the item/SKU occupies on the catalog page or in the offer.

Numeric, 5 positions with a 2-place decimal; optional.

G/W Price

sko_gift_wrap_price

The price for gift wrapping the item. The G/W field must be set to Y. The gift wrap price is charged for each unit of this SKU that is gift wrapped.

Numeric, 7 positions with a 2-place decimal; optional.

Freight

sko_freight

The freight amount to be charged for this item/SKU. The value in this field is multiplied by the quantity ordered to determine the freight charge for this item. Only used if Freight by item or Flat Rate by item has been established in Freight method field for the Source Code file.

Numeric, 6 positions with a 2-place decimal; optional.

Hidden Freight

sko_hidden_freight

This value is used only with item/SKU level freight methods, such as: Flat rate by item, flat rate by item quantity, flat rate by item source, and by item.

Hidden freight represents the portion of the item's catalog price that is used for freight.

Numeric, 6 positions with a 2-place decimal; optional.

Coupon discount %

sko_coupon_discount

This value represents the amount that is subtracted from the price when the SKU is ordered from this offer.

Numeric, 7 positions with a 2-place decimal; optional.

Coupon Effective

sko_coupon_effective_date

The date the coupon is effective until (i.e., the date expires).

Numeric, 7 positions (CYYMMDD format); optional.

Volume disc?

sko_volume_discountable

This value indicates whether this item is eligible for an end-of-order discount that applies when you accept the order during Order Entry.

Y = The item/SKU is eligible for the volume discount.

N (or blank) = The item/SKU is not eligible for the volume discount.

See Item Volume Discounting.

Alphanumeric, 1 position; optional.

Spread

sko_spread

This field is not currently implemented.

Alphanumeric, 3 positions; optional.

Feature/Option

sko_feature_option

This value indicates whether the item is considered a featured or optional item in a depiction.

Valid values are:

F = Item is the featured item in the depiction

O = Item is an optional item in the depiction

Alphanumeric, 1 position; optional.

Pickup/New

sko_pickup_new

This value indicates whether the item has been carried over from a previous offer or is new to your product offerings.

Valid values are:

P = Item is a pickup item, previously sold in an offer

N = Item is a new addition to your offer

Alphanumeric, 1 position; optional.

Warranty Item?

sko_warranty_item

This field defines whether the item/SKU in this offer is a warranty item.

Valid values are:

Y = The item/SKU in this offer is a warranty item. When an operator adds this item/SKU to an order in order entry or order maintenance, the system adds the item to the order at no charge.

N or blank = The item/SKU in this offer is not a warranty item.

Alphanumeric, 1 position; optional.

Required Add Reason?

sko_required_add_reason

This field defines whether an Order addition reason code is required when the item in this offer is added to an order in order entry or order maintenance.

Valid values are:

Y = The item in this offer requires an add reason code when the item is added to an order in order entry or order maintenance.

N = The item is this offer does not require an add reason code when the item is added to an order in order entry or order maintenance.

Alphanumeric, 1 position; optional.

Curve Code

crv_code_sko_rec

A code that represents the item/SKU's expected selling pattern in this offer.

Numeric, 3 positions; optional.

Add’l chg

add_addl_chg_sko_rec

The additional charge code associated with the type of special handling you are offering for the item.

The system validates that the additional charge code is defined as special handling, with a Type of standard or custom; the system handles each type in a different way. See Special Handling Overview for more information.

If you enter a special handling code here, you advance to the Work with Special Handling Screen or Work with Custom Special Handling Screen automatically in order entry; however, if the special handling code’s:

• Suppress S/H window field is set to Y: the system adds the special handling code and charge to the item without displaying the special handling screen.

• Bypass S/H field is set to Y: you do not advance automatically to the special handling screen unless you enter the special handling code when entering the item; however, you can still advance to the special handling screen by entering 8 next to the item.

See Special Handling Overview for more information.

Alphanumeric, 2 positions; optional.

Add-On Code

sko_aoc_add-on_code

This field is not currently implemented.

Alphanumeric, 3 positions; optional.

Fields for 05 Item Price Record Type

See Item Price errors.

Offer for Item Price

iup_offer_for_item_price

The code for the offer (catalog) in which the item appears. Validated against the Offer file. See Marketing Chapter 2: Working with Offers (WOFR).

Alphanumeric, 3 positions; required.

Effective Date

iup_ipr_effective_date

The date the price or quantity break discount becomes valid.

Numeric, 7 positions (CYYMMDD format); required.

Qty

iup_ipr_qty

The amount of an item that the customer must order to receive the discounted (quantity break) price.

Numeric, 7 positions; required.

Associate Price

ipr_associate_price

The price at which the item is sold in this offer to associate customers.

Numeric, 7 positions with a 2-place decimal; optional.

Price

ipr_price

The price at which the item is sold in this offer, if no discounts are applied, and the order date is on or after the effective date.

Numeric, 7 positions with a 2-place decimal; required.

Price Column

ipr_price_column

The pricing column associated with the price entered. In the Customer file, you may assign a customer to a pricing column. This means that the customer is charged the column price, even if the customer does not order the number of units specified for the price break.

Alphanumeric, 2 positions; optional.

Tax Inclusive Associate Price

ipr_associate_tax_price

The price at which the item is sold in this offer to associate customers on orders subject to VAT.

Numeric, 7 positions with a 2-place decimal; optional.

Tax Incl Price

ipr_tax_price

The price at which the item sells in this offer on orders subject to VAT. When an order is subject to VAT, tax does not accumulate in the Tax bucket on the order; instead, the customer pays a tax-inclusive price for the items and VAT is included as a “hidden tax” on the order detail line.

Numeric, 7 positions with a 2-place decimal; optional.

No Charge?

ipr_no_charge

Valid values are:

Y

N (or blank)

Updates the No charge? field in the Item Price file. This field is not currently implemented.

Alphanumeric, 1 position; optional.

Fields for 06 SKU Price Record Type

See SKU Price errors.

Offer SKU Price

iup_offer_for_sku_price

The code for the offer (catalog) in which the SKU appears. Validated against the Offer file. See Marketing Chapter 2: Working with Offers (WOFR).

Alphanumeric, 3 positions; required.

Effective Date

iup_skp_effective_date

The date the price or quantity break discount becomes valid.

Numeric, 7 positions (CYYMMDD format); required.

SKU Price Qty

iup_skp_qty

The amount of a SKU that the customer must order to receive the discounted (quantity break) price.

Numeric, 7 positions; required.

Associate Price

skp_associate_price

The price at which the SKU sells in this offer to associate customers.

Numeric, 7 positions with a 2-place decimal; optional.

Price

skp_price

The price at which the SKU sells in this offer, if no discounts are applied, and the order date is on or after than the effective date.

Numeric, 7 positions with a 2-place decimal; required.

Price Column

skp_price_column

The pricing column associated with the price entered. In the Customer file, you may assign a customer to a pricing column. This means that the customer is charged the column price, even if the customer does not order the number of units specified for the price break.

Alphanumeric, 2 positions; optional.

Tax Inclusive Associate Price

skp_associate_tax_price

The price at which the SKU sells in this offer to associate customers on orders subject to VAT.

Numeric, 7 positions with a 2-place decimal; optional.

Tax Incl Price

skp_tax_price

The price at which the SKU sells in this offer on orders subject to VAT.

Numeric, 7 positions with a 2-place decimal; optional.

No Charge?

skp_no_charge

Valid values are:

Y

N (or blank)

Updates the No charge? field in the SKU Price file. This field is not currently implemented.

Alphanumeric, 1 position; optional.

Fields for 07 Vendor Item Record Type

See Vendor Item errors.

Note: This file currently does not contain the following fields; however, you can update these fields on the Change Vendor Item Screen.

• Freight G/L number

• Freight $ limit

• Handling G/L number

• Handling $ limit

• Other G/L number

• Other $ limit

Vendor Number

vnd_vendor_for_vit_rec

A code that defines the supplier of an item. This field is defined in and validated against the Vendor file. See Chapter 19: Working with Vendors (WVEN).

Numeric, 7 positions; required.

Item (Vendor item)

vit_item_code

The code you use to identify a vendor item. If an item has SKUs, you must define the vendor item code at the SKU level. If you are creating a vendor item for a SKU, you must specify a Key Type to identify the SKU in CWDirect. For example, if you enter the RS key type and enter the base item’s retail style number, you must also enter the SKU code of the SKU.

If you are entering a change request, you cannot change the vendor item; instead, you need to create a new record.

Alphanumeric, 20 positions; required.

Cubic Volume

vit_cubic_volume

The cubic volume of the item, as defined by the vendor; used for informational purposes only.

Numeric, 5 positions; optional.

Description

vit_description

The description of the item, as defined by the vendor.

Alphanumeric, 30 positions; required.

Lead Days

vit_lead_days

The number of days it takes a vendor to deliver this item when it is ordered through a purchase order.

Numeric, 3 positions; optional.

Message Line 1-3

vit_message_line_1-3

An informational message that you can use for reporting purposes. Up to 3 lines of messages are available for free-form text, such as special packing instructions.

Alphanumeric, 30 positions (each line); optional.

Min Qty

vit_minimum_qty

The minimum unit quantity of merchandise you are required to order from the vendor.

Numeric, 7 positions; optional.

Price

vit_price

This value represents the vendor's list price for this item.

Numeric,11 positions with a 4-place decimal; optional.

Ship Weight

vit_ship_weight

The shipping weight of the item, as defined by the vendor.

Numeric, 7 positions with a 3-place decimal; optional.

Vendor ord qty multiple

vit_vend_ord_qty_multiple

The number of units by which your order quantity must be divisible when you order this item from this vendor.

Numeric, 5 positions; optional.

Ship Via

pov_ship_via_code

A code that represents the carrier used when shipping this item to your company. If you pass a vendor item PO ship via code, it defaults on a vendor item purchase order line automatically, but you can override it. This field is validated against the PO Ship Via file.

Numeric, 2 positions; optional.

UOM Type (SKU)

uom_type_vit_rec

The vendor's Unit of measure for an item (e.g. C12 = case of 12, GRS = gross). The system validates this unit of measure against the Unit of Measure file.

Alphanumeric, 3 positions; optional.

Country of Origin

vit_country_of_origin

A code representing the country where the vendor item originated.

Country codes are defined in and validated against the Country file; see Customer Service Chapter 14: Setting Up the Country File (WCTY).

Alphanumeric, 3 positions; optional.

Fields for 08 Item UPC Record Type

See Item UPC errors.

UPC Type

iup_upc_type

The type of UPC code. The UPC type determines the type of validation the system performs against the UPC code.

Valid values are:

E13: EAN-13

E8: EAN-8

UA: UPC-A (the system validates that the code contains 12 digits if you defined INR1620 in the UPC Validation Program (G62) system control value)

UE: UPC-E

Alphanumeric, 3 positions; required.

UPC

iup_upc

A UPC code defined for the item/SKU.

A message displays if the UPC code is not a valid length for the UPC type: UPC Length is Invalid.

The program name you define in the UPC Validation Program (G62) system control value controls the validation the system performs against UPC codes you create.

The system displays a message if the UPC code has already been assigned to another item/SKU or for this item/SKU: UPC already assigned to ACB958.

Item Identifier

For the UP Key Type, the system uses the value in this field to identify the item associated with the item upload record. Optionally the system considers the value in the SKU field to identify the CWDirect SKU.

Numeric, 14 positions; required.

UPC Vendor Nbr

upc_vnd_vendor_nbr

A user-defined code that identifies the supplier of the item/SKU UPC. This field is defined in and validated against the Vendor file. See Chapter 19: Working with Vendors (WVEN).

Numeric, 7 positions; required.

Fields for 09 Item Coordinate Record Type

See Item Coordinate errors.

Coordinate Item

icn_coordinate_item

The related item you are coordinating to the primary item (identified in the Item field or the item element) for cross-selling purposes.

Item codes are defined in and validated against the Item file.

Note: If you specify a SKU (sku) for the primary item in an item coordinate request, the system ignores it; item coordinates are assigned to the base item only, not to individual SKU’s.

Available in XML version: 2.0 (version 9.0 of CWDirect).

Alphanumeric, 12 positions; required.

ICN Coordinate Item Type

icn_coordinate_type

A code representing a type of item coordinate, such as mandatory or optional.

If you do not specify a coordinate type in a change request, the system clears the existing coordinate type assignment.

Coordinate type codes are defined in and validated against the Item Coordinate Type file; see Working with Item Coordinate Types (WICT).

Available in XML version: 2.0 (version 9.0 of CWDirect).

Alphanumeric, 2 positions; optional.

Message

icn_coordinate_message

A persuasive or descriptive message to display on the item coordinate pop-up window in order entry.

If you do not specify a message in a change request, the system clears the existing message.

Available in XML version: 2.0 (version 9.0 of CWDirect).

Alphanumeric, 70 positions; optional.

ICN Coordinate SKU

icn_coordinate_SKU

The coordinate item's unique characteristics, such as its color or size.

To create a single SKU coordinate: Enter the SKU of the coordinate item that you wish to create. The system creates a SKU coordinate for the specified SKU only.

To create a SKU coordinate for each SKU: Leave this field blank for a coordinate item that is a SKUed item and define a valid offer for the primary item and coordinate item in the IUP Offer for item coordinate field; in this situation, the system creates a SKU coordinate for each SKU of the coordinate item.

If you do not specify an IUP Offer for item coordinate, this field is required for an item coordinate that is a SKUed item.

Available in XML version: 2.0 (version 9.0 of CWDirect).

Alphanumeric, one 14-position field (full SKU) or three 4-position fields (split SKU); required if the item coordinate has SKUs and an IUP Offer for item coordinate is not defined.

IUP Offer for Item Coord

iup_offer_for_item_coord

The offer associated with the primary and coordinate items. If the coordinate item is a SKUed item, this offer represents the offer at the item level and not the SKU level.

Offer codes are defined in and validated against the Offer file.

• If an offer is not defined, the offer is not valid, or the offer is valid but an item offer record does not exist for the primary and coordinate item, the system processes the item coordinate, ignoring the specified offer.

• If the offer is valid and an item offer record exists for the primary and coordinate item, the system processes the item coordinate using the specified offer.

Note: If the item coordinate record is placed in an error status, the system does not retain the offer specified; see Item Coordinate errors for a list of errors.

Available in XML version: 7.0 (version 17.0 of CWDirect).

Alphanumeric, 3 positions; optional.

Fields for 10 SKU Cross Reference Record Type

See SKU Cross Reference Errors.

Note:

• If the SKU Cross Reference number or SKU Cross reference type for a SKU Cross Reference record changes from its current value, the system considers the SKU Cross Reference record a new record and adds it to the item/SKU.

• The SKU Cross Reference number or SKU Cross reference type for a SKU Cross Reference record are case sensitive when determining if the record is an add or change. For example, RED and Red are considered unique values.

• You cannot create the same SKU Cross Reference number and SKU Cross reference type combination for more than one item/SKU. If the SKU Cross Reference number and SKU Cross reference type combination already exists for an item/SKU other than the item/SKU in the upload record, the system places the upload record in error: SKU Cross Reference Change not allowed.

Available in XML version: 3.0 (version 10.5 of CWDirect).

SKU Xref #

sku_xref_nbr

The cross reference number that identifies the item/SKU in an external system, such as a retail outlet.

Alphanumeric, 30 positions; required.

SKU Xref type

sku_xref_type

The type of SKU cross reference, indicating the source of the cross reference number and whether you can use it to enter an item/SKU in order entry. Defined in and validated against the SKU Cross Reference Type file; see Working with SKU Cross Reference Types (WSXT) for more information.

Alphanumeric, 4 positions; required.

Fields for 11 Vendor Item Additional Charge Record Type

See Vendor Additional Charge Errors.

Available in XML version: 6.0 (version 16.0 of CWDirect).

Charge code

vac_charge_code

The vendor additional charge code to create, update, or delete for the vendor item specified through the Vendor Number (vnd_vendor_for_vit_rec in the CWCreateItem message) and Item (Vendor item) (vit_item_code in the CWCreateItem message). The vendor item specified must be associated with the item identified through the IUP Key Type. The charge code is defined in and validated against the PO Additional Charge file; see Chapter 20: Working With PO Additional Charges (WPAC).

Alphanumeric, 2 positions; required.

VAC Percent

vac_percent

The dollar amount to add to a purchase order for each unit (in retailer’s unit of measure) of the vendor item.

Numeric, 12 positions; required if you do not specify a percent.

VAC Unit amount

vac_unit_amount

The percent of the total merchandise amount to add to a purchase order for total orders of the vendor item.

Numeric, 6 positions; required if you do not specify a unit amount.

Fields for 12 Item Information Record Type

Note: You can create and update item information for the Customer Service template only.

Available in XML version: 7.0 (version 17.0 of CWDirect).

IUP Item Cls for Itm Info

iup_item_cls_for_itm_info

The item class assigned to the item that has a Customer Service information template defined.

Item class codes are defined in and validated against the Item Class file; see Working with Item Classes (WICL).

If the item class code is not valid, or if the item class is valid but is not assigned to the item, the system does not create or update item information.

Alphanumeric, 3 positions; required.

IUP Template for Itm Info

iup_template_for_itm_info

The item information template to update.

Valid value is CS Customer Service template.

The template provides standard headings for each piece of information. For example, item/SKUs belonging to an item class "clothing" might have headings such as laundry instructions and fabric contents in the customer service template. For items belonging to an item class of "toys" you might have headings such as "recommended age group."

The template also defines the number of lines available for each subject (heading). For example, you can specify 2 lines of 50 characters each to define the fabric content and 3 lines of 50 characters each to explain the laundry instructions.

For more information about working with Item Class Templates, see Reviewing Item Class Templates.

Note: If the item information template is not CS, the system does not create or update item information.

Alphanumeric, 2 positions; required.

IUP ICT Seq# for Itm Info

iup_ict_seqNbr_for_itm_info

The item class template sequence number to update; this is the sequence number defined for the item class template heading whose item information you wish to define.

Must be set to 01.

Note: If the item class template sequence number is not 01, the system does not create or update item information.

Numeric, 3 positions; required.

IUP IIF Seq# for Itm Info

iup_iif_seqNbr_for_itm_info

The item information text sequence number assigned to the item information text.

Valid values are 01-999.

• If item information does not exist for the item information text sequence number, the system creates it.

• If item information exists for the item information text sequence number, the system updates it, overriding any text that currently exists.

Note: If the item information text sequence number is blank or invalid, the system does not create or update item information.

Numeric, 3 positions; required.

IUP IIF Item Info Line

iup_iif_item_info_line

The item information text to define for the item information text sequence number.

• If item information does not exist for the item information text sequence number, the system creates it.

• If item information exists for the item information text sequence number, the system updates it, overriding any text that currently exists.

Alphanumeric, 50 positions; required.