Importing Item-Related Supporting Data (SDUP)
Purpose: Use the Submit Supporting Data Upload option to import supporting data related to items and order maintenance.
In this chapter:
• Submit Supporting Data Upload Screen (SDUP)
• Supporting Data Upload Table
• Understanding Supporting Data Upload Errors
Periodic function: You can also submit the upload through the UPLSDTA periodic function.
Submit Supporting Data Upload Screen (SDUP)
Purpose: Use this screen to create new records in supporting tables based on the records that are currently in the Supporting Data Upload table for your company. You can use this screen to create records in the following tables:
• Long SKU Division
• Long SKU Department
• Long SKU Class
• Item Class
• SKU Elements 1, 2, and 3
• Item Status
• Retail Class
• Return Reason
• Exchange Reason
How to display this screen: Enter SDUP in the Fast path field at the top of any menu, or select Submit Supporting Data Upload from a menu.
When you select Submit at this screen, the system submits the SUPPUPLOAD job.
Job processing:
• The job evaluates each record in the Supporting Data Upload table that is associated with your current company.
• If the job can create the record in the specified table without error, it creates the record and deletes the Supporting Data Upload record.
• If the Supporting Data Upload record is in error for any reason, the job leaves the record in the table and updates it with a description of the error.
• Since the job selects records in your company, records that do not have a valid company number remain in the table.
The contents of this table are described below.
Company field: The company field is required for all record types. The company number is numeric, three positions, and is validated against the Company table.
Additional fields ignored: If the record includes information in additional fields not listed below, the system ignores the information. For example, if the Misc1 field is populated for a record type that does not require this information, the contents of the field are discarded.
When you select Submit at the Submit Supporting Data Upload Screen (SDUP), the system process all error-free records whose Company field matches the submitting company, and ignores any records in the table whose Company does not match or that have already been flagged with an error reason.
Type |
Updates |
Additional Fields Used to Create Records |
EXR |
Exchange Reason: Establishing Exchange Reason Codes (WEXR) |
Code = Numeric, 3 positions. The exchange reason code. Description = Alphanumeric, 30 positions. Each of the above fields is required. You can use Establishing Exchange Reason Codes (WEXR) to enter additional information. See that menu option for more information. |
ICL |
Item Class: Working with Item Classes (WICL) |
Code = Alphanumeric, 3 positions. The item class code. Description = Alphanumeric, 30 positions. Each of the above fields is required. Note: You can use Working with Item Classes (WICL) to enter additional information for an item class. See that menu option for more information. |
IST |
Item Status: Working with Item Status (WIST) |
Code = Alphanumeric, 1 position. The item status code. Description = Alphanumeric, 30 positions. Each of the above fields is required. Note: You can use Working with Item Status (WIST) to enter order entry messages and a return disposition code. See that menu option for more information. |
LDV |
Long SKU Division: Creating and Maintaining Long SKU Divisions (WLDV) |
Code = Alphanumeric, 3 positions. The long SKU division code. Description = Alphanumeric, 30 positions. Each of the above fields is required. |
LSC |
Long SKU Class: Working with Long SKU Classes (WLSC) |
Code = Numeric, 4 positions. The long SKU class code. Description = Alphanumeric, 30 positions. Each of the above fields is required. You cannot upload or work with long SKU classes if the Use Retail Integration (H26) system control value is selected. |
LSD |
Long SKU Department: Working with Long SKU Departments (WLSD) |
Code = Numeric, 4 positions. The long SKU department code. Description = Alphanumeric, 30 positions. Each of the above fields is required. Misc1 = Long SKU division. Alphanumeric, 3 positions. Required if the Require Long SKU Division with Long SKU Department (E85) system control value is selected; otherwise, optional. Must be a valid long SKU division. |
Retail Class: Working with Long SKU Departments (WLSD) |
Code = Numeric, 4 positions. The retail class code. Description = Alphanumeric, 30 positions. Misc1 = The long SKU department to which the retail class is being assigned. Numeric, 4 positions. Must be a valid long SKU department. Each of the above fields is required. Note: • You can assign a retail class to a long SKU department only if the Use Retail Integration (H26) system control value is selected. • You cannot create a retail class without assigning it to a specific long SKU department. • You can assign the same retail class to more than one long SKU department; however, you cannot assign a retail class to more than one long SKU department at a time. Since the Misc1 field is not a key field for the Supporting Data Upload table, creating a second RTC record for the same retail class would be a duplicate record. |
|
RTR |
Return Reason: Establishing Return Reason Codes (WRTR) |
Code = Numeric, 3 positions. The return reason code. Description = Alphanumeric, 30 positions. Each of the above fields is required. You can use Establishing Return Reason Codes (WRTR) to enter additional information. See that menu option for more information. |
SEO |
SKU Element 1: Working with SKU Elements (WSK1, WSK2, WSK3) |
Code = Alphanumeric, 4 positions. The SKU element. Description = Alphanumeric, 10 positions. Misc1 = Sort sequence number. Numeric, 5 positions. All fields except Misc1 are required. |
SET |
SKU Element 3: Working with SKU Elements (WSK1, WSK2, WSK3) |
Code = Alphanumeric, 4 positions. The SKU element. Description = Alphanumeric, 10 positions. Misc1 = Sort sequence number. Numeric, 5 positions. All fields except Misc1 are required. |
SEW |
SKU Element 2: Working with SKU Elements (WSK1, WSK2, WSK3) |
Code = Alphanumeric, 4 positions. The SKU element. Description = Alphanumeric, 10 positions. Misc1 = Sort sequence number. Numeric, 5 positions. All fields except Misc1 are required. |
Understanding Supporting Data Upload Errors
When you run the upload, the job clears any Supporting Data Upload records if it was able to create a new record in the related target table. It updates each remaining record with a description of the error that prevented the update of the target table.
The information in the Supporting Data Upload table (MSSDUP) is not displayed on any screen.
Error |
Notes |
All record types See the Supporting Data Upload Table for a summary of the requirements of each record type. |
|
Missing Code |
No code was specified for the Supporting Data Upload record. |
Record already exists |
The record already exists in the related table. Note: See the RTC record type above for additional considerations related to retail class uploads. |
Missing Description |
No description was specified for the Supporting Data Upload record. |
Exchange Reason |
|
Exchange reason cannot exceed 999 |
The exchange reason is a three-position numeric code. See Establishing Exchange Reason Codes (WEXR) for background. |
Exchange Reason must be numeric |
|
ICL (item class) |
|
Item Class code cannot exceed 3 characters |
The item class code is a three-position alphanumeric field. See Working with Item Classes (WICL) for background. |
IST (item status) |
|
Item Status code cannot exceed 1 character |
The item status code is a one-position alphanumeric field. See Working with Item Status (WIST) for background. |
LSC (long SKU class) |
|
Long SKU Class not allowed when SCV H26 is set to Yes |
You cannot upload a long SKU class if the Use Retail Integration (H26) system control value is not selected. |
Long SKU Class cannot exceed 9999 |
The long SKU class is a four-position numeric code. |
Long SKU Class must be numeric |
|
Long SKU Class is zero |
|
LSD (long SKU department) |
|
Long SKU Division code cannot exceed 3 characters |
The long SKU division code specified in the Misc1 field exceeds three positions. |
Long SKU Division code is required |
No long SKU division code was specified in the Misc1 field, and the Require Long SKU Division with Long SKU Department (E85) system control value is selected. |
Long SKU Department cannot exceed 9999 |
The long SKU department code cannot exceed four positions. |
Long SKU Division code does not exist |
The long SKU division code specified in the Misc1 field is not valid. Note: This error occurs even if the Require Long SKU Division with Long SKU Department (E85) system control value is unselected. |
Long SKU Department must be numeric |
The long SKU department specified cannot include non-numeric characters. |
RTC (retail class) You can assign a retail class to a long SKU department if the Use Retail Integration (H26) system control value is selected. Also, you can assign the same retail class code to multiple long SKU departments, but not through the same supporting table upload process. See Working with Long SKU Departments (WLSD) for background. |
|
Retail Class valid only when SCV H26 is set to Yes |
The Use Retail Integration (H26) system control value is not selected. |
Long SKU Department code does not exist |
The long SKU department code specified in the Misc1 field is not valid. |
Long SKU Department must be numeric |
The long SKU department code specified in the Misc1 field is not numeric, or no long SKU department was specified. |
Long SKU Class cannot exceed 9999 |
The retail class is a four-position numeric code. |
Long SKU Class must be numeric |
The retail class is a four-position numeric code. |
RTR (return reason) |
|
Return reason cannot exceed 999 |
The return reason is a three-position numeric code. See Establishing Return Reason Codes (WRTR) for background. |
Return reason must be numeric |
|
SEO, SEW, SET (SKU element 1, 2, or 3) See Working with SKU Elements (WSK1, WSK2, WSK3) for background on the SKU element fields. |
|
SKU Element code cannot exceed 4 characters |
The first, second, and third SKU elements are each four-position alphanumeric fields. |
Sort sequence must be numeric |
The first, second, and third SKU sort sequence numbers are each five-position numeric fields. |
Description exceeds 10 characters |
The first, second, and third SKU descriptions are each ten-position alphanumeric fields. |
| Importing Item/SKU and Set Data | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Importing Set Components (WCUP) |
SDUP OROMS 17.0 2018 OTN