Working with Retail Integration Item Upload (RIIU)
Purpose: Use the Work with Retail Integration Item Upload menu option to process, review and correct batch item upload records passed to Order Management System from your retail master system through the RI Item Upload Table (RIIUPP).
About the RI Item Upload: This integration allows you to keep merchandise information at your merchandising system consistent with merchandise information in Order Management System. You can use the RI Item Upload Table (RIIUPP) to upload information about items and SKUs from the external system into Order Management System. The types of information you can upload include:
• items/SKUs
• item offers and SKU offers
• item prices and SKU prices
• vendor items
• item UPC’s
• item coordinates
See the Retail Integration (External System into Order Management System) Overview and Setup for an overview and the required setup.
Require long SKU information? The Use Retail Integration (H26) system control value determines whether Order Management System changes certain table structures so that it can read records you upload from your retail system. When this system control value is selected, the system:
• uses long SKU class codes from the Retail Class table instead of long SKU class codes from the Long SKU Class table. This allows you to create a hierarchy of retail class within long SKU department. You can link retail classes to a long SKU department in Working with Long SKU Departments (WLSD).
• requires a value in the Long SKU department, Long SKU class (retail class), Long SKU style, and Long SKU vendor fields when you create or maintain a base item.
If you wish to selectively require certain long SKU values, you can select one or more of the following system control values instead of selecting the Use Retail Integration (H26) system control value:
• Require L/S Department (I92)
• Require L/S Style (I94) (This system control value also validates that the long SKU style code is unique at both the item and SKU level.)
Create supporting tables? Order Management System creates supporting table values, such as buyer code, for items/SKUs created or updated through the item upload if they do not already exist in the Order Management System table. See Tables Updated by the RI Item Upload.
Scheduling the item upload process: You can also schedule this process to run periodically by setting up the UPRITEM Upload Retail Item File (Program name PFR0134, Parameter RIIUPP) periodic function and RIUPLD Retail Integration Item Upload periodic function (Program name PFR0084). See Scheduling Jobs for background.
Active procedure: The system creates the active procedure RI ITEM UPLOAD when you submit the process to prevent more than one RI Item Upload process from running at the same time.
In this chapter:
- RI Item Upload Translation Program
• Tables Updated by the RI Item Upload
• RI Item Upload Table (RIIUPP)
• Work with Retail Item Upload Screen
- Change Item Upload - Item/SKU Screens
- Change Item Upload - Item Offer Screens
- Change Item Upload - SKU Offer Screens
- Change Item Upload - Item Price Screen
- Change Item Upload - SKU Price Screen
- Change Item Upload - Vendor Item Screen
- Change Item Upload - Item UPC Screen
- Change Item Upload - Item Coordinate Screen
• Work with Retail Item Upload Errors Screen
• Record Deleted from RI Item Upload Report
You can create records in the RI Item Upload Table (RIIUPP) by:
• creating an RI Item Upload text file that contains the records you wish to upload and running the UPRITEM Upload Retail Item File (Program name PFR0134, Parameter RIIUPP) periodic function or using the Working with File Uploads (WUPL) menu option to upload the records in the text file to the RI Item Upload table. You can use the sample data provided to create records in the text file you wish to upload; see Sample Retail Integration Items Upload Data.
Note: When populating the RI Item Upload table:
- the information should be entered in all upper case values.
- If you wish to leave any field in the upload file blank, pass a space in an alphanumeric field and a 0 in a numeric so that the file can be processed without errors. Leaving a field with no space or 0 is interpreted as null in the database and causes errors.
• selecting Accept at the Copy Item to Company Window in Working with Existing Items (MITM).
Once you have passed item upload records from your retail master system to the RI Item Upload table, you process the table by selecting Process at the Work with Retail Item Upload Screen. If you are copying items, the system submits the process automatically.
What type of information gets passed to the RI Item Upload table? The type of information in each RI Item Upload record is indicated by its record type:
• 01 = Item/SKU
• 03 = Item Offer
• 04 = SKU Offer
• 05 = Item Price
• 06 = SKU Price
• 07 = Vendor Item
• 08 = Item UPC
• 09 = Item Coordinate
Based on the record type, the system reads information related to that type and ignores any other information defined for the record. For example, when you are creating an item, the system does not check whether there is information in the record related to SKU price or item UPC.
Request types: These codes indicate whether the system creates or maintains the related information in Order Management System. Request types are:
• A = Add record; however, if the system finds a record in the Order Management System 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 Order Management System database that matches the information in the RI Item Upload record, the system changes the Request type to A and creates a new record.
• Blank = The system compares the information in the RI Item Upload record to the existing records in the Order Management System database.
- If the system cannot match the RI Item Upload record to an existing record in the Order Management System database, the system considers the RI Item Upload record an add request.
- If the system can match the RI Item Upload record to an existing record in the Order Management System database, the system considers the RI Item Upload record a change request.
Key type: IT (item/SKU) indicates the system identifies the item and SKU associated with a record in the RI Item Upload Table (RIIUPP) using the Item and SKU passed in the record.
RI Item Upload Translation Program
The system calls the RI Item Upload translation program when you select Process File at the Work with Retail Item Upload Screen. The system also automatically calls this translation program when you select Accept at the Copy Item to Company Window in Working with Existing Items (MITM).
Scheduling the RI Item Upload process: You can also schedule the RI Item Upload Process to run periodically by setting up the RIUPLD function using the PFR0084 program. See Scheduling Jobs for background.
The RI Item Upload translation program:
1. |
Creates the active procedure RI ITEM UPLOAD. See Ending the RI Item Upload Process Before It Completes if you need to end the RI Item Upload program before it is finished. |
2. |
Processes records in the RI Item Upload Table (RIIUPP) in record type sequence: 1. Process 01 Item/SKU records. 2. Process 03 Item Offer records. 3. Process 04 SKU Offer records. 4. Process 05 Item Price records. 5. Process 06 SKU Price records. 6. Process 07 Vendor Item records. 7. Process 08 Item UPC records. 8. Process 09 Item Coordinate records. If there are any records in I (In Process) status, changes their status to U (Unprocesssed). Order Management System only selects records to process that are in a U or blank (Unprocessed) or E (Error) status. When Order Management System selects a record type to process, the system updates the status of all records with this record type to B (Batch Selected) in order to prevent other activity against this set of records. |
3. |
For the record type selected to process, Order Management System processes records in batches of 1000 records, based on: • Earliest date and time. • If there are both add records and change records, process the add records first. When Order Management System processes a batch of 1000 records, the system updates the status of the records in the batch to I (In Process). |
4. |
For each record in the selected batch, identifies the Item and SKU defined for the item upload record. |
5. |
Checks for duplicate records in the selected batch of records. |
6. |
The system places any RI item upload record that fails one or more of the above edits in an error (E) status in the RI Item Upload table and in the RI Item Upload Error table. These records in error also print on the Item Upload Error Report. See Work with Retail Item Upload Errors Screen. |
Once the RI Item Upload translation program identifies the item/SKU associated with the item upload record the system calls the RI Item Upload Edit Program. This edit program checks for invalid field values or combinations in the RI item upload record. If the record passes all validations, the edit program:
1. |
Checks the **DFLT ITEM Item/SKU to determine whether to default values to any blank fields in the RI item upload record. The system checks the **DFLT ITEM only for add and change item upload records for record type 01 (item/SKU information). See **DFLT ITEM Item/SKU. |
2. |
Checks the **DFTCHG Item/SKU to determine whether to update an existing item/SKU with the values in the RI item upload record. The system checks the **DFT CHG item only for change item upload records for record type 01 (item/SKU information). See **DFTCHG Item/SKU. Note: If the **DFT CHG item has a value, the system does not validate that field in the RI item upload record. |
3. |
Creates or maintains the item/SKU, based on the Request Type for the item upload record. If the Auto-Generate Item Keywords from Description (F79) system control value is selected, the system also creates keywords for items created through the RI Item Upload process for record type 01 Item/SKU. Note: The system creates new keywords for the item based on its current description; however, any existing keywords for the item will remain. |
4. |
Changes the status of the item upload records to P (Processed). |
5. |
If the Create Generic Item Download Trigger Records (I15) system control value is selected, the system submits the secondary job RISECU to create item download triggers and changes the status of the item upload records to S (Other Updates). |
6. |
Deletes the RI item upload record from the RI Item Upload Table (RIIUPP). |
7. |
If the RI item upload record fails any validation, the edit program: • Changes the status of the RI item upload record to E (Error) and does not delete the record from the RI Item Upload table. • Creates a record in the RI Item Upload Error table which displays the reason(s) why the record failed. |
8. |
Once RI item upload records are processed, the records are listed on: • Item Upload Error Report: indicates that RI item upload records failed one or more edits and remain in the RI Item Upload table. • Record Deleted from RI Item Upload Report: indicates that you deleted the RI item upload record(s) from the RI Item Upload table by selecting Delete for an item upload record at the Work with Retail Item Upload Screen. This means that the edit program did not create or maintain any item/SKU information. |
If a valid email is defined in the Email address field for the user that submitted the RI Item Upload Program, the system sends a Retail Item Upload email to the user’s email address when the job completes indicating whether all records were processed successfully or whether any records contain errors.
Sample successful email: A sample of the retail item upload email that is generated when all of the records processed successfully is displayed below.
Address information: |
From: To: Subject: |
OROMS@EXAMPLE.com Thomas Russell Retail Item Upload finished successfully |
System generated text: |
The Retail Item Upload has run successfully with no errors. |
|
Sample error email: A sample of the retail item upload email that is generated when one or more records contain errors is displayed below.
Address information: |
From: To: Subject: |
OROMS@EXAMPLE.com Thomas Russell Retail Item Upload finished with errors |
System generated text: |
The Retail Item Upload has run successfully but errors exist. Please review reports produced for more information. |
|
You can use the Item Upload Error Report to review the item upload records that failed one or more edits and remain in the RI Item Upload table.
Ending the RI Item Upload Process Before It Completes
If you need to end the RI Item Upload program before it is finished, for example you are processing a large number of RI item upload records, you can terminate the job by deleting the RI ITEM UPLOAD active procedure in the Purging Active Procedures (MACP) menu option.
When you delete the RI ITEM UPLOAD active procedure, the system:
1. Finishes processing the current batch of 1000 RI Item Upload records.
2. Terminates the RI Item Upload job.
3. If the Create Generic Item Download Trigger Records (I15) system control value is selected, the system submits the secondary job RISECU for the RI Item Upload records that finished processing. The system changes the status of these item upload records to S (Other Updates). Once the RISECU job ends, the system deletes these RI item upload records from the RI Item Upload Table (RIIUPP). Note: You can submit another RI Item Upload process while the RISECU job is running.
4. Updates the status of any remaining records in a B (Batch Selected) status to U (Unprocessed).
5. Leaves any remaining unprocessed records until the next time you run the RI Item Upload program.
Tables Updated by the RI Item Upload
For every RI item upload record that you pass to the RI Item Upload Table (RIIUPP), you can create, change or delete primary item and SKU values in these tables:
• Item
• SKU
• Vendor Item
• Item/Offer
• SKU/Offer
• Item Price
• SKU Price
• Item UPC
• Item Coordinate
Using the RI item upload, you can create values for secondary, supporting item/SKU tables. You can only create secondary table values; the system does not allow you to change already existing values. You can create values in these secondary item/SKU-related tables:
• SKU Element 1
• SKU Element 2
• SKU Element 3
• Item Warehouse
• Item Location
• Item Class
• Item Status
• Buyer
• L/S Department
• L/S Class
• L/S Division
• Retail Class
• Item Category
RI item upload processing will not create records in the more complex or Order Management System-specific secondary tables. You must manually create these values before passing them in a retail item upload request. For example, you cannot create ship vias, warehouses, locations, drop points, seasons, entities, vendors, sold out controls, and any other table not specifically mentioned above using the item upload.
The values you enter in the key type fields determine the fields in the RI item upload record for which you must enter a value. See:
• Keys to the table: fields that are required for all record types
• 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
**DFLT ITEM and **DFTCHG: You can create the following items for the system to consider when uploading RI item upload records for record type 01 (item/SKU information).
• **DFLT ITEM: create this item to define the values to default to add or change item upload records; see **DFLT ITEM Item/SKU.
• **DFTCHG: create this item to determine when the system updates an existing item/SKU with the values defined in a change item upload record; see **DFTCHG Item/SKU.
Note: You are not required to create the **DFLT ITEM item or **DFTCHG item, however it is recommended.
This table indicates the name of the field in the RI Item Upload table and a description of the field.
Populating the RI Item Upload table: Create an RI Item Upload text file that contains the records you wish to upload. Run the UPRITEM Upload Retail Item File (Program name PFR0134, Parameter RIIUPP) periodic function or use the Working with File Uploads (WUPL) menu option to upload the records in the text file to the RI Item Upload table. You can use the sample data provided to create records in the text file you wish to upload; see Sample Retail Integration Items Upload Data.
When populating the RI Item Upload table, the information should be entered in all upper case values.
Field |
Description |
Keys to the table: fields that are 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 Order Management System. • whether the RI item upload program creates or changes an item. • how the RI item upload program identifies the Order Management System item associated with the item upload record. See Basic errors and Item errors. |
|
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 table. Numeric, 3 positions; required. |
|
The date you create the RI item upload record. Note: If you leave this field blank and select Change for the RI item upload record at the Work with Retail Item Upload Screen, you advance to an E2 Key Screen and will not be able to correct any errors in the record. Numeric, 7 positions (CYYMMDD format); required. |
|
The time you create the item upload record. Note: If you leave this field blank and select Change for the RI item upload record at the Work with Retail Item Upload Screen, you advance to an E2 Key Screen and will not be able to correct any errors in the record. Numeric, 6 positions (HHMMSS format), required. |
|
A code that defines the item/SKU information you want to add or change. 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 Note: You must enter the leading 0 in this field. For example, you must pass 01 and not just 1. The record type determines which fields the system considers in the RI 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 RI 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 Note: When passing information to Order Management System, 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 Item/SKU allows you to default values to blank fields in an add or change RI item upload record for an item/SKU record type. The **DFTCHG Item/SKU determines if the system updates an existing item with the values defined in a change RI 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. |
A code that defines whether the upload program creates or maintains item/SKU information. Valid values are: • A = Add record; however, if the system finds a record in the Order Management System 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 Order Management System database that matches the information in the RI Item Upload record, the system changes the Request type to A and creates a new record. • Blank = The system compares the information in the RI Item Upload record to the existing records in the Order Management System database. - If the system cannot match the RI Item Upload record to an existing record in the Order Management System database, the system considers the RI Item Upload record an add request. - If the system can match the RI Item Upload record to an existing record in the Order Management System database, the system considers the RI Item Upload record a change request. |
|
|
Add Request Type (A) 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) • 08 (UPC record type) • 09 (item coordinate) You can pass multiple add requests for an existing item (record type 01) as long as you are creating a new SKU; see Record Type. 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 **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. Alphanumeric, 1 position; optional. |
A unique sequence number assigned to the RI item upload record. Sequence numbers can be in a random order or sequentially assigned, but they must be unique for each day. Numeric, 3 positions; required. |
|
A code that defines how the system identifies the Order Management System item/SKU associated with a change item upload record. IT (Item/SKU) is the only valid key type and indicates the upload record contains the item code, and optionally SKU code, that matches a Order Management System item/SKU. If the item contains SKUs and you do not enter a SKU code, the system maintains the base item. Note: If you pass an invalid key type for an 01 Item/SKU record type, the system automatically corrects it. Alphanumeric, 2 positions; required. |
|
Order Management System values |
|
A user-defined code that represents a unit of inventory. 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 selected. Note: The item code you enter must identically match an item in Order Management System for the system to identify the item associated with a change item upload record. Alphanumeric, 12 positions; required. |
|
The unique attributes of an item, such as color, size, and style. Does not include distinct fields for split SKU elements; therefore, you must count positions and enter the SKU element in the respective place on the field. Spacing is as follows: • SKU Element 1 = spaces 1-4 • SKU Element 2 = spaces 6-9 • SKU Element 3 = spaces 11-14 Alphanumeric, 14 positions; required if the Allow SKUs field is selected. |
|
Status |
A system-generated code that represents the record’s status in the RI Item Upload table. Valid values are: • U or blank = Unprocessed • B = Batch Selected • I = In Process • S = Other Updates • P = Processed • E = Error • D = Delete Pending When you initially upload records to the RI Item Upload table, the unprocessed records display on the Work with Retail Item Upload Screen with a blank Sts (Status) field. When you select Process File 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 |
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 table. This date is visible as the Last chg date (Last change date) field in Creating and Maintaining Items (MITM). Numeric, 7 positions (CYYMMDD format); optional. |
Processed Time |
The time the item upload record was processed. This time is used to update the Created time and Maintained time in the Item table. Numeric, 6 positions (HHMMSS format); optional. |
Fields for 01 Item/SKU record type See Basic errors, Item errors, and SKU errors. Note: This table currently does not contain the External info field; however, you can update this field on the Change Item screen. |
|
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. Enter Y in this field when you pass an 01 (Item/SKU), 04 (SKU Offer), 06 (SKU Price) or 07 (Vendor Item) Record Type for upload records containing a SKU code. Does not default from the **DFLT ITEM Item/SKU. If you leave this field blank, the system looks at the SKU field; if the SKU field contains a value, the system updates this flag to Y; if the SKU field does not contain a value, the system updates this flag to N. Alphanumeric, 1 position; optional. |
|
Cub val |
The cubic volume of the item. Controls the number of units of the item that can fit into a carton. Numeric, 7 positions with a 1-place decimal; optional. |
Indicates whether you ship the item from your warehouse, or have your vendor ship it to the customer directly. Valid values are: • Y = When a customer orders the item, you order the item from your vendor and the vendor ships it directly to your customer. • N = You ship the item from your warehouse. If you leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to N. Alphanumeric, 1 position; optional. |
|
Height |
The height measurement for an item. The Height, Length, and Width values determine the cubic volume of an item. Can be entered in feet or centimeters, or any other measurement as long as it is consistent. Numeric, 3 positions; optional. |
Defines the type of kit or set functionality represented by this item. Valid values: • 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 Order Management System after you create the item/SKU records. Alphanumeric, 1 position; optional. |
|
Length |
The length measurement for an item. The Height, Length, and Width values determine the cubic volume of an item. Can be entered in feet or centimeters, or any other measurement as long as it is consistent. Numeric, 3 positions; optional. |
A user-defined field representing the long SKU style defined for the item. If the Require L/S Style (I94) system control value is selected, the system requires a long SKU style when creating or updating a SKU and validates that the long SKU style code defined at the item level and SKU level are both unique values. Note: If the Use Retail Integration (H26) system control value is selected, the system ignores the setting of the Require L/S Style (I94) system control value. In this situation, the system requires a long SKU style when creating or updating an item, but it does not have to be unique. Alphanumeric, 20 positions; required if SCV H26 or SCV I94 is selected. |
|
A user-defined code used to identify the item. Alphanumeric, 20 positions; optional. |
|
A user-defined field representing the long SKU vendor for the item/SKU. Required if the Use Retail Integration (H26) system control value is selected. See Retail Integration (External System into Order Management System) Overview and Setup. Alphanumeric, 7 positions; required if the Use Retail Integration (H26) system control value is selected. |
|
Standard Cost |
The standard cost of the item. This is the cost that appears in the Default cost field in the Item table. Numeric, 11 positions with a 4-place decimal; optional. |
Indicates whether inventory levels are maintained for the item. • Y = This is a non-inventory item. • N = This is a regular item that will be tracked. If you leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to N. Alphanumeric, 1 position; optional. |
|
Pieces Per Case |
The system uses this value to determine the number of units that fit in a case when suggesting location placement. Numeric, 5 positions; optional. |
Selling Qty |
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 |
Used to calculate the freight charge on an item when the Freight method on the order is By Item or Flat Rt/Item. Numeric, 7 positions with a 3-place decimal; optional. |
Serial # Tracking |
This field is not implemented; enter N in this field. Alphanumeric, 1 postion; optional. |
Indicates how to ship this item. Valid value is: S = This item must ship by itself, and each unit prints on its own pick slip. Blank = This item can ship with other items. Alphanumeric, 1 position; optional. |
|
Ship Weight |
The actual shipping weight of the item. Numeric, 7 positions with a 3-place decimal; optional. |
User Field 1 |
An informational field you can use according to your organization's specific requirements. Alphanumeric, 10 positions; optional. |
User Field 2 |
An informational field you can use according to your organization’s specific requirements. Alphanumeric, 10 positions; optional. |
User Field 3 |
An informational field you can use according to your organization’s specific requirements. Alphanumeric, 10 positions; optional. |
User Field 4 |
An informational field you can use according to your organization’s specific requirements. Alphanumeric, 10 positions; optional. |
Width |
The width measurement for an item. The Height, Length, and Width values determine the cubic volume of an item. Can be entered in feet or centimeters, or any other measurement as long as it is consistent. Numeric, 3 positions; optional. |
Allow % discount? |
Determines whether certain discounts can be applied to the item. • Y = This item is discountable. • N = This item is not discountable. If you leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Oversize |
Determines whether this item is considered an oversized item. • Y = This is an oversized item. • N = This is not an oversized item. If you leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to N. Alphanumeric, 1 position; optional. |
The description of the item. Does not default from the **DFLT ITEM Item/SKU. Alphanumeric, 40 positions; required. |
|
Second Language Desc |
The second language description for the item. Alphanumeric, 40 positions; optional. |
Exclude From Flex Pay |
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 = Do not exclude this item from deferred and installment payment plans. If you leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Royalty |
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 = This is not a royalty item. If you leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Membership |
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 = This is not a membership item. If you leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to N. Alphanumeric, 1 position; optional. |
You can use this field to indicate when to trigger an automatic download of item availability information to an extract table; 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 has a 9.0 length in the RI Item Upload table, 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. |
|
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. • V = The item is a virtual (non-physical) stored value card. See Creating a Stored Value Card Item for more information on setting up a stored value card item. Alphanumeric, 1 position; optional. |
|
The person who is authorized to make purchases for your company. Buyer codes are defined in and validated against the Buyer table; see Working with Buyers (WBUY). Alphanumeric, 3 positions; optional. |
|
CTN ID # (SKU) (Carton ID) |
The type of carton in which this item must be shipped. Note: This field is not currently implemented. Numeric, 2 positions; optional. |
Inventory Value G/L # |
This field is not implemented. Numeric, 8 positions; optional. |
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 table; see Working with Hazardous Item Codes (WHAZ). Numeric, 2 positions; optional. |
|
A user-defined code that identifies a group of items. This code is validated against the Item Class table; see 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 selected. Alphanumeric, 3 positions; required if SCV F06 is selected. |
|
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 table; see Working with SKU Groups (WISG). Numeric, 3 positions; optional. |
|
A code that represents an item's status, such as obsolete, discontinued, etc. This information is used for inventory reporting purposes, to assign a future arrival date, or to prevent the Item Selection screen from listing the item. See Working with Item Status (WIST) for background. Alphanumeric, 1 position; optional. |
|
A code that represents a location type, such as caged area, etc. Validated against the location class table; see Creating and Maintaining Location Classes (WLCL). Alphanumeric, 2 positions; optional. |
|
A code to group items into classes for reporting purposes. Required if the Use Retail Integration (H26) or Require L/S Class (I93) system control value is selected. Long SKU Class If the Use Retail Integration (H26) system control value is unselected, the system validates this field against the Long SKU Class table. Long SKU classes have only one value to an organization. For example, Long SKU Class 15 may be Men’s Shoes, and will remain Men’s Shoes regardless of the department. For more information see Working with Long SKU Classes (WLSC). Retail Class If the Use Retail Integration (H26) system control value is selected, the system validates this field against the Retail Class table instead of the Long SKU Class table. Long SKU classes that are linked to long SKU departments are called retail classes. 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 Order Management System, 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 Item/SKU, the system displays an error message: Long SKU Department required. 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 Item/SKU, the system displays an error message: Item Long SKU Class required. Numeric, 4 positions; required if SCV H26 or SCV I93 is selected and you are using an 01 record type. |
|
A code used to group items into departments for reporting purposes. Required if the Use Retail Integration (H26) or Require L/S Department (I92) system control value is selected. Long SKU departments are defined in and validated against the Long SKU Department table; see Working with Long SKU Departments (WLSD). When using Retail Integration from an external system into Order Management System, long SKU classes are linked to long SKU departments and become retail classes. 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 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 selected, 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. If the system creates the long SKU department, the system will also create the long SKU division if it does not already exist. However, if the long SKU department does not need to be created, the system will not create the long SKU division if it does not already exist. Numeric, 4 positions; required if SCV H26 or SCV I92 is selected and you are using an 01 record type. |
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 table. If the Require Long SKU Division with Long SKU Department (E85) system control value is selected, 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, the system creates a new code in the L/S Division table, but only if the system is also creating the long SKU department. Alphanumeric, 3 positions; required if the Require L/S Division with L/S Department (E85) system control value is selected and you are passing a new L/S department value. |
|
A standard by which an item is sold. Typical units of measure include: • EA = each • IN = inches • C12 = case of 12 Validated against the Unit of Measure table (see Working with Units of Measure (WUOM)). If you leave this field blank, defaults from the Default Item Unit of Measure (B33) system control value. Alphanumeric, 3 positions; optional. |
|
A code that defines the vendor or supplier of an item. Vendor codes are defined in and validated against the Vendor table; see Working with Vendors (WVEN). Numeric, 7 positions; optional. |
|
A code that represents the carrier that must be used when shipping this item. Numeric, 2 positions; optional. |
|
The vendor who manufactured the item. Numeric, 7 positions; optional. |
|
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 selected, you must enter an entity code for each item you set up; entity codes for items and SKUs are defined at the item level. Informational only. Numeric, 3 positions; optional. |
|
Defines the season associated with this item, such as spring. Season codes are defined in and validated against the Season table; see Working with Season Codes (WSEA). Alphanumeric, 3 positions; optional. |
|
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. Required if the Require Sort Sequence Number in the SKU File (F23) system control value is selected. See SKU Sort Sequence Numbers for an overview. Numeric, 5 positions; required if the Require Sort Sequence Number system control value is selected. |
|
Compatibility |
A user-defined code assigned to an item/SKU. Alphanumeric, 3 positions; optional. |
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) |
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 |
The description of the SKU element. If no value is passed, the SKU description will be blank. Alphanumeric, 40 positions; optional. |
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 leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to N. If you identify an item as a subscription item, you must: • enter 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 table 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 Working with Item Subscriptions (WISB). Alphanumeric, 1 position; optional. |
|
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 |
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 |
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). |
A code, typically used in a retail environment, that represents the color portion of the long SKU code. Used for reporting purposes. Numeric, 5 positions; optional. |
|
A code, typically used in a retail environment, that represents the size portion of the long SKU code. Used for reporting purposes. Numeric, 5 positions; optional. |
|
A code, typically used in a retail environment, that represents the width portion of the Long SKU code. Used for reporting purposes. Numeric, 5 positions; optional. |
|
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 |
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 |
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 |
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 |
The SKU's recommended minimum number of units for the warehouse specified in the Whs (Warehouse) field. Numeric, 7 positions; optional. |
SKU Gift Certificate |
This field is not implemented; enter N for this field. Alphanumeric, 1 position; optional. |
Reserve Qty Limit |
If the order quantity exceeds this amount, the system will not reserve the item/SKU and will display the Backorder Reason. Numeric, 7 positions; optional. |
Restrict Orders |
Indicates 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 = The operator can accept an order for this item/SKU. If you leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Retail Ref # |
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 |
The system uses this value to calculate the freight charge on a SKU when the Freight method on the order is By Item or Flat Rt/Item. Overrides the selling weight, if any, defined at the base item level. Numeric, 7 positions with a 3-place decimal; optional. |
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. Note: • For add 01 (Item/SKU) records, leave this field blank to have the system assign a unique short SKU number to the item/SKU. The system does not default the short SKU defined for the **DFLT ITEM Item/SKU to a new item/SKU. • For change 01 (Item/SKU) records, create the **DFTCHG Item/SKU so that existing items/SKUs retain their assigned short SKU number; however, even if you pass a short SKU number for a change 01 record, the system retains the existing short SKU number that is assigned to the item/SKU. Numeric, 7 positions; optional. |
User field 1 |
An informational field you can use according to your organization's specific requirements. Alphanumeric, 10 positions; optional. |
User field 2 |
An informational field you can use according to your organization’s specific requirements. Alphanumeric, 10 positions; optional. |
User field 3 |
An informational field you can use according to your organization’s specific requirements. Alphanumeric, 10 positions; optional. |
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 |
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 |
Not implemented. Alphanumeric, 1 position; optional. |
Harmonize Code |
A code that prints on customs documents for international shipments. Alphanumeric, 16 positions; optional. |
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 |
The cost of an item. FIFO costing: The cost stored here in the SKU table is updated similarly to the average cost, but is used only for reporting and inquiry, not for the actual costing of inventory transactions such as billing. Numeric, 11 positions with a 4-place decimal; optional. |
FIFO Cost |
A method to determine the cost of an item. FIFO (first in, first out) costing allows you to track the cost of an item/SKU based on its cost at purchase order receipt, and apply this cost against each shipment of the item until the receipt quantity is exhausted. The system determines the cost by creating a FIFO costing layer when you receive a purchase order, and selecting the oldest eligible FIFO cost layer when you ship an order. Numeric, 11 positions with a 4-place decimal; optional. |
LIFO Cost |
A method to determine the cost of an item. Not currently implemented. Numeric, 11 positions with a 4-place decimal; optional. |
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. Numeric, 11 positions with a 4-place decimal; optional. |
Second language description |
Not currently implemented. Alphanumeric, 40 positions; optional. |
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. If you leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Second Compatibility |
A user-defined code assigned to the item. If the second compatibility code for the item matches the code defined in the Second Compatibility Code used to Trigger SKU Blocking (K84) system control value, the system sends item and order information to an external system to determine whether the item/SKU is allowed on an order. See this system control value for more information. Alphanumeric, 3 positions; optional. |
The amount to include in the Hidden tax field for an item subject to VAT. Numeric, 7 positions with a 2-place decimal; optional. |
|
The percentage to use when calculating hidden tax for an item subject to VAT. Numeric, 5 positions with a 2-place decimal; optional. |
|
Indicates whether to produce a backorder card for the SKU. Valid values are: • Y = Suppress normal backorder card generation for this item. • N = Do not suppress normal backorder card generation. If you leave this field blank, the system defaults this value from the **DFLT ITEM Item/SKU. If the **DFLT ITEM (or NA SKU for the **DFLT ITEM) does not exist, the system defaults this value from the Unconditional Suppression of Backorder Card (F19) system control value. If this system control value is blank, the system defaults this field to N. Alphanumeric, 1 position; optional. |
|
Projected Returns |
The number of units you expect to receive in returns for the item. Numeric, 7 positions; optional. |
User Field 4 |
An informational field you can use according to your organization's specific requirements. Alphanumeric, 5 positions; optional. |
User Field 5 |
An informational field you can use according to your organization’s specific requirements. Alphanumeric, 5 positions; optional. |
Returnable |
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 If you leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Retail X-Ref # |
Represents the UPC (Universal Product Code) or Retail Reference number for the SKU. Used for informational purposes. If you want the system to create an item UPC code, you must enter values in the Fields for 08 Item UPC record type. Numeric, 10 positions; optional. |
The long SKU style defined for the SKU. If the Require L/S Style (I94) system control value is selected, the system requires a long SKU style when creating or updating a SKU and validates that the long SKU style code defined at the item level and SKU level are both unique values. Note: If the Use Retail Integration (H26) system control value is selected, the system ignores the setting of the Require L/S Style (I94) system control value. In this situation, the system requires a long SKU style when creating or updating an item, but it does not have to be unique. Alphanumeric, 20 positions; optional. |
|
L/S Vendor |
A user-defined field that represents the long SKU vendor for the item/SKU. Alphanumeric, 7 positions; optional. |
Excl Store Restock |
This field is not implemented; enter N in this field. Alphanumeric, 1 position; optional. |
Original Retail Price |
The original price of the item at the retail store. Numeric, 7 positions with a 2-place decimal; optional. |
GTIN |
Not currently implemented. Numeric, 14 positions; optional. |
Commodity Code |
Not currently implemented. Numeric, 8 positions; optional. |
ABC Code |
This field is not implemented. Alphanumeric, 1 position; optional. |
Carton ID # |
The type of carton in which this item must ship. Note: This field is not currently implemented. Numeric, 2 positions; optional. |
Freq Code (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. Note: This field is not currently implemented. Alphanumeric, 1 position; optional. |
A code that represents a warehouse where this item is stocked. Warehouse codes are defined in and validated against the Warehouse table. See Creating and Maintaining Warehouses (WWHS). If the **DFLT ITEM Item/SKU does not exist and you do not define a valid warehouse, the system defaults the warehouse defined in the Default Warehouse (A04) system control value. Numeric, 3 positions; required. |
|
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 table. Alphanumeric, 7 positions; optional. |
|
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 Working with Soldout Controls (WSLD). Alphanumeric, 2 positions; optional. |
|
A standard by which an item/SKU is sold. Validated against the Unit of Measure table (see Working with Units of Measure (WUOM)). Defaults from the Default Item Unit of Measure (B33) system control value if you have not defined a default value in the **DFLT ITEM Item/SKU or the **DFLT ITEM does not exist. Alphanumeric, 3 positions; optional. |
|
SEO Code |
SKU element 1. Alphanumeric, 4 positions; optional. |
SEW Code |
SKU element 2. Alphanumeric, 4 positions; optional. |
SET Code |
SKU element 3. Alphanumeric, 4 positions; optional. |
A code that represents a SKU's status, such as obsolete, discontinued, sold out, etc. This information is used for inventory reporting purposes. The status defined at the SKU level overrides the status defined at the base item level. See Working with Item Status (WIST) for background. Alphanumeric, 1 position; optional. |
|
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 table; see Working with Item Category Codes (WITG). Alphanumeric, 4 positions; optional. |
|
Prep Code |
A code used to indicate any special preparation or handling required for the SKU. Informational only. Note: This field is not currently implemented. Alphanumeric, 2 positions; optional. |
A code representing the country where the SKU originated. Country codes are defined in and validated against the Country table; see Setting Up the Country Table (WCTY). Alphanumeric, 3 positions; optional. |
|
A code to group items into classes for reporting purposes. Long SKU classes are defined in and validated against the Long SKU Class table; see Working with Long SKU Classes (WLSC). If the Use Retail Integration (H26) system control value is selected, 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 selected, 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 will 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 table; see the Work with Retail Class Screen for more information. Numeric, 4 positions; optional. |
|
A code assigned to weather-sensitive items/SKUs such as plant stock to insure that the items will ship to different regions of the country within time windows suited to the regions. See Shipping Zone Reservation Overview. Alphanumeric, 4 positions; optional. |
|
OROB Eligible |
Indicates whether to include this item when: • sending item and inventory information from Order Management System to Order Broker through a stored procedure; however, this flag does not control whether to include the item through an API that uses an XML message, such as the Generic Item Download API or the Generic Inventory Download API. • sending backordered order lines to the Order Broker for fulfillment. See Order Broker Integration for an overview, and see Rules for Submitting Backorders to the Order Broker for more rules that govern eligibility for the Order Broker. Valid values: • Y = Include this item when you use a stored procedure to send item and inventory information to Order Broker; also, the item is eligible to be sent to the Order Broker for fulfillment, provided it meets the other Rules for Submitting Backorders to the Order Broker. • N = Do not include this item when you use the stored procedure to send item and inventory information to Order Broker; also, the item is not eligible to be sent to the Order Broker for fulfillment. If you leave this field blank, it defaults from the **DFLT ITEM Item/SKU. If the **DFLT ITEM Item/SKU does not exist, the system defaults this field to Y. Alphanumeric, 1 position; optional. |
ITM Image Link |
The URL to the location of the item image on the external image hosting application. No validation. See Item Image/Info Link Screen. Updates the ITM Image Link field in the Item table. Alphanumeric, 256 positions; optional. |
ITM Info Link |
The URL to the location of the item information on the external image hosting application. No validation. See Item Image/Info Link Screen. Updates the ITM Info Link field in the Item table. Alphanumeric, 256 positions; optional. |
SKU Image Link |
The URL to the location of the SKU image on the external image hosting application. No validation. See Item Image/Info Link Screen. Updates the SKU Image Link field in the SKU table. Alphanumeric, 256 positions; optional. |
SKU Info Link |
The URL to the location of the SKU information on the external image hosting application. No validation. See Item Image/Info Link Screen. Updates the SKU Info Link field in the SKU table. Alphanumeric, 256 positions; optional. |
ITM Tag Type |
This field is not implemented. Alphanumeric, 2 positions; optional. |
Fields for 03 Item Offer record type See Item Offer errors. |
|
The code for the offer (catalog) in which the item/SKU appears. Validated against the Offer table. See Working with Offers (WOFR). Alphanumeric, 3 positions; required (if other information is entered). |
|
Cost |
Not implemented. Numeric, 7 positions with a 2-place decimal; optional. |
Expected Return Pct |
Not implemented. Numeric, 5 positions with a 2-place decimal; optional. |
G/W Flag |
Indicates whether this SKU is eligible for gift wrap. Valid values: • Y = The item/SKU can be gift wrapped. • N = In this offer, the item/SKU cannot be gift wrapped. If you leave this field blank, the system defaults Y to this field if the Gift Wrap Default (F07) system control value is selected; otherwise, this field defaults to N. Alphanumeric, 1 position; optional. |
G/W Price |
The price for gift wrapping the item. The G/W field must be Y. The gift wrap price will be charged for each unit of this SKU that is gift wrapped. Numeric, 7 positions with a 2-place decimal; optional. |
Page # |
Not implemented. Numeric, 5 positions; optional. |
Projected Units |
Not implemented. Numeric, 7 positions; optional. |
S/H Price |
The price that will be charged for special handling. Numeric, 7 positions with a 2-place decimal; optional. |
S/H Flag |
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 = This item is not eligible for special handling. If you leave this field blank, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Square Inches |
Not implemented. Numeric, 5 positions with a 2-place decimal; optional. |
Freight |
The freight amount to be charged for this item/SKU. Multiplied by the quantity ordered to determine the freight charge for this item. Used only if the Freight method field for the Source Code table is set to By Item or Flat Rt/Item. Numeric, 6 positions with a 2-place decimal; optional. |
Hidden Freight |
Used only with item/SKU level freight methods, such as: Flat Rt/Item, Flat Rt/Qy, Flat Rt/Itm Src, 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 |
Not implemented. Alphanumeric, 3 positions; optional. |
Volume Discount Y/N |
Indicates whether this item is eligible for an end-of-order discount that will be applied when you accept the order during Order Entry. • Y = The item/SKU is eligible for the volume discount. • N = The item/SKU is not eligible for the volume discount. If you leave this field blank, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Coupon Disc % |
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 |
The date the coupon is effective until (i.e., the date expires). Numeric, 7 positions (CYYMMDD format); optional. |
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. |
|
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 |
For optional message lines. Alphanumeric, 30 positions each; optional. |
Warranty Item? |
Indicates 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 = The item in this offer is not a warranty item. If you leave this field blank, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Require Add Reason |
Indicates 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. If you leave this field blank, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Curve Code |
Not implemented. Numeric, 3 positions; optional. |
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. Alphanumeric, 2 positions; optional. |
|
Not currently implemented. Alphanumeric, 3 positions; optional. |
|
Fields for 04 SKU Offer record type See SKU Offer errors. |
|
The code for the offer (catalog) in which the item/SKU appears. Validated against the Offer table. See Working with Offers (WOFR). Alphanumeric, 3 positions; required (if other information is entered). |
|
Cost |
Not implemented. Numeric, 7 positions with a 2-place decimal; optional. |
Expected Return Pct |
Not implemented. Numeric, 5 positions with a 2-place decimal; optional. |
G/W Flag |
Indicates whether this SKU is eligible for gift wrap. Valid values: • Y = The item/SKU can be gift wrapped. • N = In this offer, the item/SKU cannot be gift wrapped. If you leave this field blank, the system defaults Y to this field if the Gift Wrap Default (F07) system control value is selected; otherwise, this field defaults to N. Alphanumeric, 1 position; optional. |
Page # |
Not implemented. Numeric, 5 positions; optional. |
Projected Units |
Not implemented. Numeric, 7 positions; optional. |
The price that will be charged for special handling. Numeric, 7 positions with a 2-place decimal; optional. |
|
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 = This item is not eligible for special handling. If you leave this field blank, the system defaults this field to N. Alphanumeric, 1 position; optional. |
|
Square Inches |
Not implemented. Numeric, 5 positions with a 2-place decimal; optional. |
G/W Price |
The price for gift wrapping the item. The G/W field must be Y. The gift wrap price will be charged for each unit of this SKU that is gift wrapped. Numeric, 7 positions with a 2-place decimal; optional. |
Freight |
The freight amount to be charged for this item/SKU. Multiplied by the quantity ordered to determine the freight charge for this item. Used only if the Freight method field for the Source Code table is set to By Item or Flat Rt/Item. Numeric, 6 positions with a 2-place decimal; optional. |
Hidden Freight |
Used only with item/SKU level freight methods, such as: Flat Rt/Item, Flat Rt/Qty, Flat Rt/Itm Src, 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 % |
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. |
The date the coupon is effective until (i.e., the date expires). Numeric, 7 positions (CYYMMDD format); optional. |
|
Volume disc? |
Indicates whether this item is eligible for an end-of-order discount that will be applied when you accept the order during Order Entry. • Y = The item/SKU is eligible for the volume discount. • N = The item/SKU is not eligible for the volume discount. If you leave this field blank, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Spread |
Not implemented. Alphanumeric, 3 positions; optional. |
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. |
|
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? |
Indicates 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 = The item/SKU in this offer is not a warranty item. If you leave this field blank, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Required Add Reason? |
Indicates 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. If you leave this field blank, the system defaults this field to N. Alphanumeric, 1 position; optional. |
Curve Code |
Not implemented. Numeric, 3 positions; optional. |
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. Alphanumeric, 2 positions; optional. |
|
Not currently implemented. Alphanumeric, 3 positions; optional. |
|
Fields for 05 Item Price record type See Item Price errors. |
|
The code for the offer (catalog) in which the item appears. Validated against the Offer table. See Working with Offers (WOFR). Alphanumeric, 3 positions; required. |
|
The date the price or quantity break discount becomes valid. Numeric, 7 positions (CYYMMDD format); required. |
|
The amount of an item that the customer must order to receive the discounted (quantity break) price. Numeric, 7 positions; required. |
|
Associate Price |
The price at which the item will be sold in this offer to associate customers. Numeric, 7 positions with a 2-place decimal; optional. |
The price at which the item will be sold in this offer, if no discounts are applied, and the order date is on or after the effective date. If the Tax Included in Price (E70) system control value is unselected, you must define a price; if this system control value is selected, you can define a price or tax inclusive price. Numeric, 7 positions with a 2-place decimal; required if SCV E70 is unselected. |
|
Price Column |
The pricing column associated with the price entered. In the Customer table, you may assign a customer to a pricing column. This means that the customer will be 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 |
The price at which the item will be sold in this offer to associate customers on orders subject to VAT. Numeric, 7 positions with a 2-place decimal; optional. |
Tax Incl Price |
The price at which the item will be sold 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. If the Tax Included in Price (E70) system control value is unselected, you must define a price; if this system control value is selected, you can define a price or tax inclusive price. Numeric, 7 positions with a 2-place decimal; optional. |
No Charge? |
Indicates whether this item/SKU is eligible for any type of special handling in this offer (such as, monogramming, hemming, etc.). • Y = The item/SKU is eligible for special handling. • N = The item/SKU is not eligible for special handling. Note: This field is not currently implemented. Alphanumeric, 1 position; optional. |
Fields for 06 SKU Price record type See SKU Price errors. |
|
The code for the offer (catalog) in which the SKU appears. Validated against the Offer table. See Working with Offers (WOFR). Alphanumeric, 3 positions; required. |
|
The date the price or quantity break discount becomes valid. Numeric, 7 positions (CYYMMDD format); required. |
|
The amount of a SKU that the customer must order to receive the discounted (quantity break) price. Numeric, 7 positions; required. |
|
Associate Price |
The price at which the SKU will be sold in this offer to associate customers. Numeric, 7 positions with a 2-place decimal; optional. |
The price at which the SKU will be sold in this offer, if no discounts are applied, and the order date is on or after than the effective date. If the Tax Included in Price (E70) system control value is unselected, you must define a price; if this system control value is selected, you can define a price or tax inclusive price. Numeric, 7 positions with a 2-place decimal; required if SCV E70 is unselected. |
|
Price Column |
The pricing column associated with the price entered. In the Customer table, you may assign a customer to a pricing column. This means that the customer will be 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 |
The price at which the SKU will be sold in this offer to associate customers on orders subject to VAT. Numeric, 7 positions with a 2-place decimal; optional. |
Tax Incl Price |
The price at which the SKU will be sold in this offer on orders subject to VAT. If the Tax Included in Price (E70) system control value is unselected, you must define a price; if this system control value is selected, you can define a price or tax inclusive price. Numeric, 7 positions with a 2-place decimal; optional. |
No Charge? |
Indicates whether this item/SKU is eligible for any type of special handling in this offer (such as, monogramming, hemming, etc.). • Y = The item/SKU is eligible for special handling. • N = The item/SKU is not eligible for special handling. Note: This field is not currently implemented. Alphanumeric, 1 position; optional. |
Fields for 07 Vendor Item record type See Vendor Item errors. |
|
A code that defines the supplier of an item. Defined in and validated against the Vendor table. See Working with Vendors (WVEN). Numeric, 7 positions; required. |
|
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 that will be able to identify the SKU in Order Management System. 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 |
The cubic volume of the item, as defined by the vendor; used for informational purposes only. Numeric, 5 positions; optional. |
The description of the item, as defined by the vendor. Alphanumeric, 30 positions; required. |
|
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 |
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 |
The minimum unit quantity of merchandise you are required to order from the vendor. Numeric, 7 positions; optional. |
Price |
Represents the vendor's list price for this item. Numeric,11 positions with a 4-place decimal; optional. |
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 |
The number of units by which your order quantity must be divisible when you order this item from this vendor. Numeric, 5 positions; optional. |
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. Validated against the PO Ship Via table. Numeric, 2 positions; optional. |
|
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 table. Alphanumeric, 3 positions; optional. |
|
A code representing the country where the vendor item originated. Country codes are defined in and validated against the Country table; see Setting Up the Country Table (WCTY). Alphanumeric, 3 positions; optional. |
|
Fields for 08 Item UPC record type See Item UPC errors. |
|
The type of UPC code. Informational only. Valid values are: • E13 = EAN-13, indicating a 13 position UPC code; however Order Management System does not validate the UPC length. • E8 = EAN-8, indicating an 8 position UPC code; however, Order Management System does not validate the UPC length. • UA = UPC-A, indicating a 12 position UPC code; however Order Management System does not validate the UPC length. • UE = UPC-E, indicating a 6 position UPC code; however Order Management System does not validate the UPC length. Alphanumeric, 3 positions; required. |
|
A UPC code defined for the item/SKU, including any leading zeros. Example: If the UPC code is 06012011, the UPC code passed should be 06012011 and not 6012011. Alphanumeric, 14 positions; required. |
|
A user-defined code that identifies the supplier of the item/SKU UPC. Defined in and validated against the Vendor table. See Working with Vendors (WVEN). Numeric, 7 positions; optional. |
|
The related item you are coordinating to the primary item (identified in the Item field) for cross-selling purposes. Item codes are defined in and validated against the Item table. Note: If you specify a SKU in an item coordinate request, the system ignores it; item coordinates are assigned to the base item only, not to individual SKUs. Alphanumeric, 12 positions; required. |
|
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 table; see Working with Item Coordinate Types (WICT). Alphanumeric, 2 positions; optional. |
|
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. Alphanumeric, 70 positions; optional. |
ICN Coordinate SKU |
The coordinate item's unique characteristics, such as its color or size. Required if the coordinate item has SKUs. Note: • If you define a SKU for the coordinate item that is not already defined for the primary item, the system creates a new Item Coordinate record for the primary item. • If you define a SKU for the coordinate item that is already defined for the primary item, the system updates the Coordinate type and Message values for the existing Item Coordinate record. Alphanumeric, three 4-position fields; required if the item has SKUs. |
Work with Retail Item Upload Screen
Purpose: Use this screen to process batch item upload records, then review and correct the records with errors.
All batch records that you pass to the RI Item Upload Table (RIIUPP) using the process described under RI Item Upload Process display on this screen with a blank status. You can process the batch by selecting Process File to submit the RI_UPLD job. Any records that are in error remain on this screen, and the system places the record(s) in error status (E).
How to display this screen: Enter RIIU in the Fast Path at the top of any menu or select Work with Retail item Upload from a menu.
Field |
Description |
Date |
The date you created the item upload record. Numeric, 6 positions; optional. |
Record type |
Indicates the item/SKU information you want to add, change, or delete. Valid values are: • Item/SKU • Item Offer • SKU Offer • Item Price • SKU Price • Vendor Item • Item UPC • Item Coordinate Fields in the RI Item Upload table 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. Note: Although the record type description is listed on this screen, each record type is identified by a numeric code in the table. For example, an Item/SKU is record type 01. |
|
Example: If you want to change a SKUs price information, you enter a SKU Price record type. Even if all the fields in the item upload record are populated for that SKU, the system will only pass information in the nine SKU price fields. Note: If you maintain values (a change Request Type) for different record types and you leave blank fields in the item upload record, the system updates the associated tables with blanks. Item/SKU Record Type (01) When passing information to Order Management System, you must build upon values passed in this record type. For example, you cannot create a vendor item record type until you have first created the item/SKU 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 selected: • L/S style • L/S vendor • Item description • L/S class • L/S department • L/S division (if the Require Long SKU Division with Long SKU Department (E85) system control value is selected, 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 selected) |
|
Creating an item/SKU record is the only instance where 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 do not have to be specified. 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 selected. If you do not enter an item code, a message indicates: 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 selected. |
|
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. Item Offer Record Type (03) The system considers fields associated with this record type. The Offer for item offer field is required. See Fields for 03 Item Offer record type. SKU Offer Record Type (04) The system considers fields associated with this record type. The SKU offer for SKU offer field is required. See Fields for 04 SKU Offer record type. |
|
Item Price Record Type (05) 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. |
|
SKU Price Record Type (06) 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. |
|
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 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 SKUs. See Fields for 09 Item Coordinate record type. Optional. |
Req type (Request Type) |
A code that defines whether you create or change item/SKU information. Valid values are: • Add = Add record; however, if the system finds a record in the Order Management System database that matches the information in the RI Item Upload record, the system updates the existing record. • Maintain = Change record; however, if the system cannot find a record in the Order Management System database that matches the information in the RI Item Upload record, the system creates a new record. • Blank = The system compares the information in the RI Item Upload record to the existing records in the Order Management System database. - If the system cannot match the RI Item Upload record to an existing record in the Order Management System database, the system considers the RI Item Upload record an add request. - If the system can match the RI Item Upload record to an existing record in the Order Management System database, the system considers the RI Item Upload record a change request. |
|
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) • 08 (UPC record type) • 09 (item coordinate) You can also pass multiple add requests for the same item (record type 01) as long as you are creating a new SKU for that base item. See the Record Type field description for more 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 table with the values you entered in the required fields, and overwrites the rest of the data in the table 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. Optional. |
Key type (IUP Key Type) |
Defines the field values the system evaluates in order to identify the Order Management System item or SKU associated with an item upload record. Valid value is Item/SKU. The Item and SKU fields identify the item and SKU associated with the item upload record. 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 indicates if you do not enter a code in the Item and SKU fields. Optional. |
Key |
The information that the system/translation program retrieved to identify the item or SKU associated with the item upload record. If the system maps the record to an item/SKU within Order Management System, the item/SKU’s full information is shown here. Alphanumeric, 30 positions; display-only. |
The status of the item upload record. Valid values are: • Unprocessed or blank = The item upload record is waiting to be processed. • Batch Selected = The item upload record contains the Record Type that is currently selected to process. • In Process = The item upload record is part of the batch of 1000 records that is currently being processed. • Other Updates = The item upload record is being processed by the secondary job RISECU that creates item download triggers and data warehouse triggers. • Deleted = The item upload record will be deleted from the table. • Error = The item upload record contains errors. • Processed = The item upload record has been processed. When you pass records to the RI Item Upload table, 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 select Process File to process and edit the item upload records, the system updates all records with the appropriate status. Only records in Error status remain visible at the Work with Retail Item Upload Screen so that you can correct them. Optional. |
Screen Option |
Procedure |
Select Process File to edit and process batch item upload records. See RI Item Upload Process for more information on how the system edits and populates the tables. The system submits the RI_UPLD job. Periodic function: You can also schedule this process to run periodically by setting up the RIUPLD function using the PFR0084 program. See Scheduling Jobs for background. |
|
Change an item upload record |
Select Change for an item upload record to advance to one of the Change Item Upload Screens. Note: You cannot change an item upload record if its status is B (Batch Selected), I (In Process), S (Other Updates) or P (Processed). |
Delete an item upload record |
Select Delete for an item upload record to delete it. When you process the batch (select Process File), the system deletes the item upload record from the RI Item Upload table. Note: You cannot delete an item upload record if its status is B (Batch Selected), I (In Process), S (Other Updates) or P (Processed). |
Display an item upload record |
Select Display for an item upload record to advance to one of the Display Item Upload Screens. |
Errors |
Select Errors for an item upload record to advance to the Work with Retail Item Upload Errors Screen. |
Delete all records that currently exist in the RI Item Upload Table (RIIUPP), across all companies |
Select Delete All. At the Are you sure you want to delete? window, select Delete to delete all records; otherwise, select Exit to cancel. |
Select Print Error Report to print the Item Upload Error Report. The system submits the RI_ERROR job. |
Purpose: Use these screens to correct batch item upload records with errors.
The system displays different information on the Change screens based on the information in the item upload record. For example, vendor item information is indicated for an item upload record containing vendor item information.
E2 Key screen: If you do not enter one of the keys to the table for the item upload record, you advance to an E2 Key Screen and are not able to advance to these screens to correct the errors.
Note: You cannot change an item upload record if its status is B (Batch Selected), I (In Process), S (Other Updates) or P (Processed).
The following types of change screens exist:
• Change Item Upload - Item/SKU Screens
• Change Item Upload - Item Offer Screens
• Change Item Upload - SKU Offer Screens
• Change Item Upload - Item Price Screen
• Change Item Upload - SKU Price Screen
• Change Item Upload - Vendor Item Screen
• Change Item Upload - Item UPC Screen
• Change Item Upload - Item Coordinate Screen
Change Item Upload - Item/SKU Screens
Purpose: Use these screens to work with item upload records containing item/SKU information (01 Item/SKU record type).
Default values:
• If you use the **DFLT ITEM Item/SKU to default values, the system does not default these values until you correct any errors.
• If you use the **DFTCHG Item/SKU to keep the existing values for an item/SKU and only update the fields defined in the item upload, the system defaults the retained values to the Change Item Upload - Item/SKU screens.
For field descriptions see Keys to the table: fields that are required for all record types and Fields for 01 Item/SKU record type.
Change Item Upload - Item Offer Screens
Purpose: Use these screens to work with item upload records containing item/offer information (03 record type).
For field descriptions see Keys to the table: fields that are required for all record types and Fields for 03 Item Offer record type.
Change Item Upload - SKU Offer Screens
Purpose: Use these screens to work with item upload records containing SKU/offer information (04 record type).
For field descriptions see Keys to the table: fields that are required for all record types and Fields for 04 SKU Offer record type.
Change Item Upload - Item Price Screen
Purpose: Use this screen to work with item upload records containing item/price information (05 record type).
For field descriptions see Keys to the table: fields that are required for all record types and Fields for 05 Item Price record type.
Change Item Upload - SKU Price Screen
Purpose: Use this screen to work with item upload records containing SKU/price information (06 record type).
For field descriptions see Keys to the table: fields that are required for all record types and Fields for 06 SKU Price record type.
Change Item Upload - Vendor Item Screen
Purpose: Use this screen to work with item upload records containing vendor/item information (07 record type).
For field descriptions see Keys to the table: fields that are required for all record types and Fields for 07 Vendor Item record type.
Change Item Upload - Item UPC Screen
Purpose: Use this screen to work with item upload records containing item/UPC information (08 record type).
For field descriptions see Keys to the table: fields that are required for all record types and Fields for 08 Item UPC record type.
Change Item Upload - Item Coordinate Screen
Purpose: Use this screen to work with item upload records containing item coordinate (09 record type).
For field descriptions see Keys to the table: fields that are required for all record types and Fields for 09 Item Coordinate record type.
To display: Select Display for an item upload record at the Work with Retail Item Upload Screen to advance to one of the Display Item Upload Screens. The Record Type of the item upload record determines the category of information that is indicated. See the Change Item Upload Screens for the different types of screens that display and see RI Item Upload Table (RIIUPP) for an explanation of the fields.
Work with Retail Item Upload Errors Screen
Purpose: Use this screen to review all errors associated with an item upload record, to review the values you passed for the keys to the table such as the created date, record type, request type, and key type, and to review the key information the translation program found for a Order Management System item associated with the item upload record.
Once you perform the RI Item Upload Process by selecting Process for the item upload batch at the Work with Retail Item Upload Screen, all item upload records that contain errors display in three places:
• the Retail Integration Item Upload Error table
• the Item Upload Error Report
• the Work with Retail Item Upload Screen
How to display this screen: Select Errors for an item upload record at theWork with Retail Item Upload Screen.
The top portion of the screen displays the key information you passed to the item upload table for the item upload record. See Work with Retail Item Upload Screen for descriptions of these fields.
Note: If you do not enter values for all the Keys to the table: fields that are required for all record types, you will receive an error message displaying which value(s) you are missing. However, you cannot change these values here. You must delete the item upload record, and re-send it with the required corrections.
The following table lists some of the most common errors the Retail Item Translation Program and the Retail Integration Edit Program find during RI Item Upload Process.
Types of errors include:
Error Code |
Error Message |
Problem |
|
See Keys to the table: fields that are required for all record types and Fields for 01 Item/SKU record type. |
||
IA |
Invalid Season for Item. |
The Season field contains an invalid value. |
IB |
SKU Group can only be entered for items which have SKUs. |
The SKU Group field must be blank if the item is not SKUed. |
IC |
Item Drop ship and Non-inventory are mutually exclusive. |
The Drop Ship field is selected and the item is a non-inventory item. |
ID |
Item Drop ship and Kit Type 'S' are mutually exclusive. |
The Drop Ship field is selected and the item is a set item. |
IE |
Entity required. |
The Entity Number field is required. |
IF |
Item Long SKU Style required. |
The Long SKU Style field is required for the item. |
IG |
Item Long SKU Vendor required. |
The Long SKU Vendor field is required for the item. |
IH |
Quantity must be limited to 99999. |
The Qty Threshold field must be less than or equal to 5 positions. |
GA |
Invalid Company |
The Company does not exist. |
GB |
Company required |
The Company is required. |
GC |
Item required. |
The Item is required because the system could not identify the item based on the information passed for the RI Item Upload record. |
GD |
Invalid Item |
You tried to add an 03-08 record type without first creating the item/SKU (01 record type). |
GE |
SKU is required for this record type. |
The SKU is required. |
GF |
Invalid record type for an item without skus. |
The Record Type is invalid for the item. |
GG |
Invalid SKU. |
The SKU is invalid. |
GH |
Invalid record type. |
The Record Type is invalid. |
GI |
Invalid request type. |
The Request Type is invalid. |
IN |
Change of Allow SKUs is not allowed. |
You cannot change the Allow SKUs field to N because SKUs exist. |
IO |
Invalid SVC code |
You entered an invalid value in the SVC type field. Valid values are: • blank (default) = The item is not a stored value card. • P = The stored value card item is a physical card. • E = The stored value card is a physical card and, as soon as the stored value card is processed through billing, the system sends an email notification to the ship to customer on the order, notifying the customer that a stored value card has been purchased and is in the process of being delivered. • V = The stored value card is a virtual (non-physical) card. |
IP |
Item L/S Style is Not Unique |
The Require L/S Style (I94) system control value is selected and the Long SKU Style defined at the item level is also assigned to another item or SKU. |
K1 |
Missing company |
The Company field requires a value. |
K2 |
Missing date |
The Record Created Date field requires a value. |
K3 |
Missing time |
The Record Created Time field requires a value. |
K4 |
Missing record type |
The Record Type field requires a value. |
KI |
Missing Item/SKU for Key Type IT. |
You must enter an Item if the Key type is IT. |
KT |
Invalid key type for record. |
The Key Type field is invalid. The key type must be IT. If you pass an invalid key type for an 01 Item/SKU record type, the system automatically corrects it. |
SC |
Multiple primary locations for this Item/SKU not allowed. |
The SKU already had a primary location and the Allow Multiple Primary Item Locations (D12) system control value is set to NOT ALLOW. |
SD |
SKU Long SKU Style required. |
The Require L/S Style (I94) system control value is selected and a L/S Style is not defined at the SKU level. |
SE |
SKU Long SKU Style is not unique. |
The Require L/S Style (I94) system control value is selected and the L/S Style defined at the SKU level is also assigned to another item or SKU. |
Q1 |
Error on Query |
The current batch of 1000 RI Item Upload records failed to process because someone was creating or updating item/SKU information in Order Management System at the same time the RI Item Upload process was processing a record for the same item/SKU information. For example, you would get this error if someone was creating an item at the same time the RI Item Upload process was trying to create this same item. In this situation, the system updates the status of all of the records in the batch to E (Error) with the reason Error on Query. |
10 |
Invalid Long SKU Department. |
The Department (L/S department) field contains an invalid value. |
11 |
Long SKU Department required. |
The Department (L/S department) field does not contain a value. |
12 |
Long SKU Division required. |
The L/S Division field does not contain a value. This field is required if the Require Long SKU Division with Long SKU Department (E85) system control value is selected and you are passing a new Department (L/S department) value. |
13 |
Invalid Long SKU Division. |
The L/S Division field contains an invalid value. |
14 |
Invalid UOM Type for item. |
The UOM (Unit of Measure) field for the item contains an invalid value. |
15 |
UOM - Item Required. |
The UOM (Unit of Measure) field for the item does not contain a value. |
16 |
Invalid Vendor for Item. |
The Vendor # field for the item contains an invalid value. |
17 |
Invalid Ship Via for Item |
The Ship Via Code field for the item contains an invalid value. |
18 |
Invalid Manufacturing Vendor for Item. |
The Manufacturer Vendor field for the item contains an invalid value. |
19 |
Invalid Entity for Item. |
The Entity Number field for the item contains an invalid value. |
1D |
Invalid Kit Type |
The Kit Type field must be S, F, or V. |
1G |
Invalid Ship Alone flag. |
The Ship Alone field must be S or blank. |
1J |
Item Description required. |
The Description (Item description) field is blank and requires a value. |
1N |
Invalid buyer for item. |
The Buyer field contains an invalid value. |
1Q |
Invalid Hazard Code |
The Code (Hazard code) field contains an invalid value. |
1R |
Invalid Item Class for item. |
The Item Class field contains an invalid value for the item. |
1S |
Item Class Required |
The Item Class field does not contain a value. |
1U |
Invalid Item SKU Group code for item. |
The SKU Group field contains an invalid value. |
1V |
Invalid Item Status for item. |
The STS (Status) field for the item contains an invalid value. |
1W |
Invalid Location Class |
The Location Class field contains an invalid value. |
1Y |
Invalid Long SKU Class for item. |
The Class (Long SKU class) field contains an invalid value. |
1Z |
Item Long SKU Class required. |
The Class (Long SKU class) field does not contain a value. |
20 |
SKU Crt - SKU Exists |
The SKU you are trying to create already exists. |
21 |
Subscription must be defined as non-inventory. |
The Subscription field must contain a Y or N. |
22 |
Must enter hidden tax amount OR hidden tax percent. |
You can enter a value in the Hidden Tax Amount field OR Hidden Tax Percent field, but not both. |
24 |
Sort Sequence # required for SKU. |
The Collating Seq # field must contain a value. |
25 |
SKU not eligible for zone reservation code. |
The Zone Reservation field must be blank for the SKU. |
26 |
Coordinate Group (999) cannot be assigned to a Set/Component item. |
You cannot enter a value in the Coord group (Coordinate group items?) field for a set item. |
2L |
Invalid Warehouse code. |
The Whs (Warehouse) field contains an invalid value. |
2M |
Warehouse is Required. |
The Whs (Warehouse) field does not contain a value. |
2N |
Invalid Location code. |
The Location field contains an invalid value. |
2O |
Invalid Sold Out Control code. |
The Soldout control code field contains an invalid value. |
2P |
Invalid UOM Type for SKU |
The UOM Type field for the SKU contains an invalid value. |
2Q |
Invalid Item Status for SKU |
The Status field contains an invalid value for the SKU. |
2R |
Invalid category for SKU. |
The Category field contains an invalid value for the SKU. |
2T |
Invalid Country of origin for SKU |
The Country of Origin field contains an invalid value for the SKU. |
2U |
Invalid Long Sku Class for SKU. |
The L/S Class field contains an invalid value for the SKU. |
2V |
Invalid Long SKU Class/Department combination for SKU. |
The L/S Class and Department (L/S department) combination is invalid for the SKU. |
2W |
Invalid Zone Reservation for SKU. |
The Zone Reservation field contains an invalid value. |
2X |
Invalid SKU Element 1 |
The SKU field contains an invalid value for SKU element 1. |
2Y |
Invalid SKU Element 2 |
The SKU field contains an invalid value for SKU element 2. |
2Z |
Invalid SKU Element 3 |
The SKU field contains an invalid value for SKU element 3. |
3A |
Invalid Offer for Item |
The Offer for Item Offer field contains an invalid value for the item. |
3B |
Offer is Required for item |
The Offer for Item Offer field does not contain a value for the item. |
3C |
Item Offer Create - Item/Offer Exists |
The Offer for Item Offer you are trying to create already exists. |
3D |
Invalid Item Offer |
The Offer for Item Offer field contains an invalid value. |
3H |
Invalid Feature/Option flag on Item Offer. |
The Feature/option field contains an invalid value for the item offer. |
3I |
Invalid Pickup/New flag on Item Offer. |
The Pickup/new field contains an invalid value for the item offer. |
3M |
Invalid Additional Charge code on item offer. |
The Add’l chg code field contains an invalid value for the item offer. |
3N |
Invalid Add-On code on item offer. |
The Add-On Code field contains an invalid value for the item offer. |
3P |
Spcl Hand price not allowed on item offer when not eligible. |
The S/H Price field does not contain a value for the item offer. |
3Q |
Spcl Hand code not allowed on item offer when not eligible. |
The S/H Flag field does not contain a value for the item offer. |
3R |
Invalid Coupon Expiration Date on Item Offer |
The Coupon Effective field contains an invalid date. The date must be in CYYMMDD format. |
4A |
Invalid Offer for SKU |
The Offer for SKU Offer field contains an invalid value for the SKU. |
4B |
Offer is required for SKU. |
The Offer for SKU Offer field does not contain a value for the SKU. |
4C |
SKU Offer Create - SKU/Offer Exists |
You cannot create the Offer for SKU Offer because it already exists. |
4D |
Invalid SKU Offer |
The Offer for SKU Offer you are trying to create is invalid. |
4H |
Invalid Feature/Option flag on SKU Offer. |
The Feature/Option field contains an invalid value for the SKU offer. |
4I |
Invalid Pickup/New flag on SKU Offer. |
The Pickup/New field contains an invalid value for the SKU offer. |
4M |
Invalid Additional Charge code on SKU offer. |
The additional charge code in the Add’l chg field is invalid for the SKU offer. |
4N |
Invalid Add-On code on SKU offer. |
The add-on code in the Add-On Code field is invalid for the SKU offer. |
4P |
Spcl Hand price not allowed on SKU offer when not eligible. |
The S/H Price field does not contain a value for the SKU offer. |
4Q |
Spcl Hand code not allowed on SKU offer when not eligible. |
The S/H Flag field does not contain a value for the SKU offer. |
4R |
Invalid Coupon Expiration Date on SKU Offer |
The Coupon Effective field contains an invalid date. The date must be in CYYMMDD format. |
5A |
Invalid Offer for Item Price |
The Offer for Item Price defined for the item price is invalid. |
5B |
Offer is required for item price. |
The Offer for Item Price field does not contain a value for the item price. |
5C |
Effective date is required for item price. |
The Effective Date field does not contain a value for the item price. |
5D |
Quantity is Required for Item Price |
The Qty field does not contain a value for the item price. |
5E |
Itm Price Crt - Item Price Exists |
You cannot create the item price because it already exists. |
5F |
Invalid item effective date or quantity. |
The Effective Date or Qty is not valid for the item price record. |
5G |
Price required on item price. |
The Price field does not contain a value for the item price. |
5H |
Invalid Effective Date on Item Price |
The Effective Date field contains an invalid date. The date must be in CYYMMDD format. |
5I |
Price cannot be negative on item price. |
The Price field contains a negative value for the item price. |
5J |
Invalid item offer for item price. |
The item offer price is invalid. |
6A |
Invalid Offer for SKU Price |
The Offer SKU Price is invalid for the SKU price. |
6B |
Offer is required for SKU price. |
The Offer SKU Price field does not contain a value for the SKU price. |
6C |
Effective date is required for SKU price. |
The Effective Date field does not contain a value for the SKU price. |
6D |
Quantity is required for SKU price. |
The SKU Price Qty field does not contain a value for the SKU price. |
6E |
SKU Price Crt - SKU Price Exists |
You cannot create the SKU price because it already exists. |
6F |
Invalid sku effective date or quantity. |
The Effective Date or SKU Price Qty is not valid for the SKU price record. |
6G |
Price required on Sku price. |
The Price field does not contain a value for the SKU price. |
6H |
Invalid Effective Date on SKU Price |
The Effective Date field contains an invalid date. The date must be in CYYMMDD format. |
6I |
Price cannot be negative on Sku price. |
The Price field contains a negative value for the SKU price. |
6J |
Invalid sku offer for sku price. |
The SKU offer is invalid for the SKU price. |
7A |
Invalid Vendor for Vendor Item. |
The Vendor Number field contains an invalid value for the vendor item. |
7B |
Vendor is required for vendor item. |
The Vendor Number field does not contain a value for the vendor item. |
7C |
Vendor Item code is required for vendor item. |
The Item (Vendor item) field does not contain a value for the vendor item. |
7D |
VIT Crt - VIT Exists |
You cannot create the vendor item because it already exists. |
7E |
Invalid vendor item. |
The Item (Vendor item) is invalid. |
7F |
Vendor Item Description required. |
The Description field is required for vendor item. |
7G |
Invalid PO Ship Via code on Vendor Item. |
The Ship Via field contains an invalid value for vendor item. |
7H |
Invalid UOM Type for Vendor Item. |
The UOM Type (SKU) field contains an invalid value for vendor item. |
7I |
Invalid country of origin for Vendor Item. |
The Country of Origin field contains an invalid value for vendor item. |
8A |
UPC type is required for Item UPC. |
The UPC Type field is required. |
8B |
UPC # is required for Item UPC. |
The UPC field is required. |
8C |
UPC Crt - UPC exists |
You cannot create the UPC because it already exists. |
8D |
Invalid Item UPC |
The UPC for the item is invalid. |
8E |
Invalid Vendor on Item UPC. |
The UPC Vendor Nbr defined for the UPC is invalid. |
8F |
UPC already assigned to xxxx. (where xxxx is item and sku) |
The UPC is already assigned to another item/SKU. |
8G |
UPC Length is Invalid |
The UPC length is invalid for the UPC Type. Not currently implemented. |
8H |
UPC type is invalid for Item UPC |
The UPC Type is invalid. |
9A |
Invalid Item Coordinate |
The Coordinate Item specified does not exist. |
9B |
Invalid Item Coordinate Type. |
The ICN Coordinate Item Type specified does not exist. |
9C |
Invalid Coordinate SKU. |
A SKU is specified for a non-SKUed item, or the SKU specified for a SKUed item does not exist. |
9D |
Item Coordinate is required. |
No Coordinate Item is specified. |
9E |
Can’t add Item Coordinate because Item Coordinate already ex |
The non-SKUed coordinate item specified for an Add request is already assigned to the item. |
9F |
Can’t add Coordinate SKU. Coordinate SKU already exists. |
The specified SKU of the coordinate item specified for an Add request is already assigned to the item. |
9G |
Coordinate SKU is required for SKU’ed item. |
There is no coordinate SKU specified for the coordinate item, and it is a SKU’d item. |
| Retail Integration Overview and Setup | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Item Upload Error Report |
RIIU OROMS 17.0 2018 OTN