Building & Adding Items

These all go on the Item Induction Template.

Item & Supplier Updates

Edit on the front end for a single item, or use RMS Download for several.

UDAs

Location-Level Updates

These all go on the Manual Maintenance Form.

Seasons & Ticket Types

Hierarchy Changes

These run on a fixed schedule.

Item Tab — Required Columns

Location Tab (if ranging to new locations)

Save file as ODS and upload to V16

Updating in RMS v16

1. Go to Tasks → Foundation Data → Manage Item Lists. Paste the Item List number → Search.
2. In the Results box: Actions → Mass Change → Item/Locations.



Item List Search ×
▲ Search
Match All Any
Advanced Saved Search Default
Item List
Description
Type
Created Date
📅
Created By
Item
🔍
Item Description
Search Reset Save As...
▲ Results
Actions ▼
Create
Create From Existing
Edit
View
Export to Excel
Mass Change ▶
Create ▶
Reclassification
Item
Replenishment
VAT Rates
Item / Locations
User Defined Attributes
Seasons / Phases
Item Ticket
Up Charges
View ▼ | 📄 📋 ✏️ 👓 | 📊 ⏳ | ◪ Detach
Item List	Description	Type	Total Items	Created Date	Created By
22285450	Air Wick Oil 3 Items	Dynamic	3	4/24/26	boydz
Columns Hidden 2
Total ➖



3. Click the Green (+). Select the appropriate location type → OK. Add additional locations as needed.
4. Paste the Primary Supplier into the Primary Supplier Site field. Set Primary Country to USA.
5. Click Save and Close.

Updating in RMS v16

1. Go to Tasks → Items → Manage Items. Paste the Parent RIN into the item field → Search → click into the item RIN.



Item

Description

Transaction Level

Item Level

Status

Item Type

Department

Class

Subclass

Supplier Site

VPN

Search Reset Save...

▲ Results

Actions ▼ View ▼ | 📄 📖 ✏️ 👓 | 🔍 📊 | ◪ Detach ⇄ Wrap

Cost Change

Item	Description	Item Level	Department	Class	Subclass	Subclass Name
14910832	Orchard Valley Harvest Trail Mix Chocolate Raisin 8oz	Level 1	974	1100	1	PEGGED TRAIL MIXES




2. Click More Actions → Locations.



▲
Parent "14910832 | Orchard Valley Harvest Trail Mix Chocolate Raisin 8oz
Regular Item | Approved
Department974 | NUTS
Class1100 | TRAIL MIX
Subclass1 | PEGGED
Transaction LevelTransaction
Unit Retail4.10
Unit ELC3.9100
Markup %4.63
CurrencyUSD
SellableYes
OrderableYes
InventoriedYes
▲ Descriptions 🌐
* Description Orchard Valley Harvest Trail Mix Chocolate Raisin 8oz
* Short
Secondary
Number Type Oracle Retail Item Number
▶ Cost and Price
▲ Usage and Units
* Store Order Multiple Case Pack
* Standard UOM EA
UOM Conversion Factor
▶ Attributes
❓ | 📄 📋 ❌
Create Children
More Actions ▼
Suppliers
Retail by Zone
Locations
Item Up Charges
List Children
Simple Pack ▶
Transformation
Replenishment
Substitute Items
User Defined Attributes
Save Save and Close Cancel



3. Click More Actions → Mass Change → Location Attributes.



Actions ▼ View ▼ | ➕ ✏️ | 📊 📅 | ◪ Detach
Location Type	Location	Name	Status	Average Cost	Unit Cost	Unit Retail	Currency
			ALL
Store	2	NORF PACKAGE STORE	Active			4.10	USD
Store	5	NORF CCC	Active			4.10	USD
Store	7	HUNTINGTON HALL MM	Active			4.10	USD
Store	8	NORF V55 MM/GAS	Active			4.10	USD
Store	9	NORF CEP 76 MM/GAS	Active			4.10	USD
Store	10	NORF MAIN STORE	Active			4.10	USD
Store	13	NORF LT PARKING	Active			4.10	USD
❓
More Actions ▼
Location Attributes ▶
Location Traits
Mass Change ▶
Cancel



4. Click the Green (+). Select the appropriate location type: Store, Warehouse, Location List-Store, or Location List-Warehouse → OK. Add additional locations as needed.
5. Paste the Primary Supplier into the Primary Supplier Site field. Set Primary Country to USA.
6. Click Save and Close.

Purpose

This Standard Operating Procedure (SOP) describes the process for AGC mass UPC deletion.

Scope

This SOP is a mandatory document and shall be implemented by all employees when engaging in this project.

Training

The Manager of the Data Steward Team is responsible for ensuring that team members who follow this procedure understand the SOP's objectives and other inter-related activities. Ensure that team members sign that they have read and understand this SOP.

Precautions

Use this SOP in conjunction with other related item induction and item deletion procedures.

Responsibility

Data Steward Team members are responsible for the activities identified in this procedure.

Equipment / Systems

• Data Steward Inbox
• HUB: Merchandising / Support / ORUP
• Item Induction Template
• Microsoft Exchange Email
• RMSv16 & RMSv10
• TOAD / SQL — RMSv16 & RMSv10

This 832 UPC/EAN deletion process happens monthly. The email will usually come in on the first Monday of the first full week of the month. As phases of RMSv16 are being implemented, data is managed in both RMSv16 and RMSv10 — the deletion process takes at least 2 days to fully delete UPCs out of both systems (longer if there are issues with the UPCs or delays with data flowing/batches running).

The UPC deletion process is a nightly job in the RMS batches and runs in the After Batch, after all other phases have completed. The DST will flag UPCs for deletion in RMSv16 via the CFAS flag. This flag sends a message to RMSv10 to put the UPCs into "Delete Pending" status in RMSv10. The UPCs will purge via the Daily Purge job in the nightly batch, and then send a message back to RMSv16 to place the UPCs into "Delete Pending" status there as well. The UPCs then purge out of RMSv16 via the Daily Purge job in the nightly batch.

Notification & Submission

1. Notification of AGC Monthly UPC Deletes will come into the DST inbox. The original email will be from the TLE Admin User and will be forwarded to DST from either the EDI Business Team or START. Subject will be: "RETEK 832 UPC/EAN Deletion Report for (Date)."
2. The email will contain a list of UPCs to delete, and at the bottom will be a count of UPCs.

Creating Item Induction Template for Mass UPC Deletes

1. Download or open the Item Induction Template from the HUB. The most current template may be downloaded from:
   Item Induction Template
   internal-link
2. In the Action Field (Column A): select Add Item CFAS.
3. In the Parent Field (Column H): enter the UPCs from the Retek 832 UPC/EAN Deletion Report.
   ⚠

   Note: Copy the UPCs, and when pasting into the Parent field, select "Match Destination Formatting." A straight paste will lose the front-loading zero on the UPCs.
4. In the Buyer Field (Column DK): enter 260 (Buyer # for these departments).
5. Copy the Action Field of "Add Item CFAS" and Buyer Field of "260" down to match the amount of UPCs pasted into the template.



	Item Information
Action	Status	Item Type	Sellable	Orderable	Inventory	Item Family ID	Parent Item	Transaction Item	Buyer
Add Item CFAs	Approved	Regular Item	Yes	Yes	Yes		013051280376		260
Add Item CFAs	Approved	Regular Item	Yes	Yes	Yes		013051280482		260
Add Item CFAs	Approved	Regular Item	Yes	Yes	Yes		013051280499		260
Add Item CFAs	Approved	Regular Item	Yes	Yes	Yes		013051280529		260
Add Item CFAs	Approved	Regular Item	Yes	Yes	Yes		013051312053		260
Add Item CFAs	Approved	Regular Item	Yes	Yes	Yes		013051571641		260
Add Item CFAs	Approved	Regular Item	Yes	Yes	Yes		018100028497		260
Add Item CFAs	Approved	Regular Item	Yes	Yes	Yes		018100527877		260



6. Validate front-loading UPCs did not drop off.
7. If you have a Security Warning Banner stating macros have been disabled, select the Enable Content button.
8. Select the Populate Button in Rows 2 & 3 / Column C & D — the 4 tabs at the bottom of the template will explode out, and UPCs will populate the necessary tabs.
9. On the Item Tab, go all the way to the end and validate there are no errors upon populating the template. Errors, if any, will populate in columns DN & DO.
10. At the bottom of the template by the tabs, select the right arrow with the line to show the last several tabs so you see the Vw_Nexcfas tab.
11. On the Vw_Nexcfas tab, column G (Delete Flag) is populated with "N." Change this field to "Y" and copy down for all records on the template.

	A	B	C	D	E	F	G
1	Item	Plan-o-Gram Required	NRF Size Code	NRF Size Desc	Base Zone	Buyer	Delete Flag
2	013051280376	Y				260	Y
3	013051280482	Y				260	Y
4	013051280499	Y				260	Y
5	013051280529	Y				260	Y

12. Name the file (e.g., AGC-PRG Deletes_06May19 #1) and save the template as an .ODS file. It must be an .ODS file in order to induct it into RMSv16.
⚠
Note: If there are several thousand UPCs to delete, break this process up into multiple templates with no more than 800 UPCs. The maximum supported for deleting UPCs is not yet known — it may be higher, but large batches can be more cumbersome to troubleshoot if issues arise.

Inducting Mass Delete Item Induction Template

1. Log into RMSv16 internal-link and go to the Main Screen.
2. Select Items > Upload Items from File.
   If saved in Favorites, select the Star and then Upload Items from File. If not, select Tasks (Clipboard with Check Mark) → Items → Upload Items from File. The Upload Items from File screen will open.
3. From the Upload Items from File screen, populate the following fields:


Source and Destination
Template	Item Master	Source	AGC-PRG Deletes_06May19 #1.ods Update...
Process Description		Destination	RMS Tables
Upload Done


4. The file will process in the background. You'll receive a notification under the Bell Icon when the file has finished processing.
5. Select the Bell Icon; the Notifications box will open. Select the blue link, and the Data Loading Status screen will open.
6. From the Data Loading Status screen, check the Status of your Item Induction Delete File.
   ℹ

   You may need to scroll right to see the status field. Make note of your Process ID # — it will be important for a later step.
7. The record will show a Process ID # and the Status should say "Processed with errors," since not all fields are being populated but the file still processes.
8. If the Status says Processed w/ Errors, the View Issues button will be enabled — select it to check your errors. The most common error indicates that the template is expecting fields to be populated that are not; these fields are not needed for deleting UPCs.
9. For additional Delete Files, repeat the upload steps above until all Delete Files have been processed.
10. To validate the file updated correctly, log in to RMSv16 SQL Developer or TOAD and run the following query (entering the UPCs you submitted to be deleted):
SQL — Validate CFAS Flag (RMSv16)

SELECT *
FROM RMS.ITEM_MASTER_CFA_EXT
WHERE ITEM IN ('601350155138',
'601350155145',
'601350155152',
'601350155169',
'747941643698',
'747941643704',
'747941643711',
'747941621757');

11. The results you are looking for are the VARCHAR2_2 & VARCHAR2_3 fields populated with 'Y' and the Buyer #.




≡	ITEM	GROUP_ID	VARCHAR2_1	VARCHAR2_2	VARCHAR2_3	VARCHAR2_4
	601350155138	10009	Y	Y	940
	601350155145	10009	Y	Y	940
	601350155152	10009	Y	Y	940
	601350155169	10009	Y	Y	940
	747941339560	10009	Y	Y	940
	747941339577	10009	Y	Y	940
	747941339584	10009	Y	Y	940
	747941339591	10009	Y	Y	940
	747941621726	10009	Y	Y	940
	747941621733	10009	Y	Y	940
	747941621740	10009	Y	Y	940
	747941621757	10009	Y	Y	940
	747941643698	10009	Y	Y	940
	747941643704	10009	Y	Y	940
	747941643711	10009	Y	Y	940



12. You can also check on the frontend. From Favorites or the Task list, select Manage Items. Select the UPC to open the Item Screen with the item information.
13. On the bottom right, select More Actions and scroll down to Other Attributes.
14. Select Item Master CFAS — this opens the Item Master CFAS Screen. You should see the Delete Flag box checked.
15. From here, the process sends the delete file to RMSv10 and places the UPCs into Delete Pending status there.
16. The Daily Purge job is a nightly batch in RMSv10 that processes anything in Delete Pending. This is an overnight job — you will not see results until the following day.
17. To validate UPCs have been deleted, run the following query in RMSv10 (SQL Developer or TOAD) — no records should be returned:
SQL — Validate Deletion (RMSv10)

select distinct item, item_parent TRANSACTION, item_grandparent PARENT, item_desc, dept, class, subclass,
create_datetime, last_update_id, last_update_datetime
from rms.item_master
where item in ('601350155138',
'601350155145',
'601350155152',
'601350155169',
'747941643698',
'747941643704',
'747941643711');

18. Assuming the Daily Purge job runs with no issues, the UPCs will delete out of RMSv10 and send a file to RMSv16 to place the UPCs into Delete Pending there as well.
19. The Daily Purge job is also a nightly batch in RMSv16. This is again an overnight job — results will not appear until the following day.
20. To validate UPCs have been deleted, run the same query above in RMSv16 (SQL Developer or TOAD) — no records should be returned.
21. If records are returned, run the following queries in RMSv16:


SQL — Daily Purge Tables

select *
from rms.daily_purge;
-- If data is still in this table, the UPCs are slated to be deleted;
-- check whether the Daily Purge job ran the previous night.

select *
from rms.daily_purge_error_log;
-- If data is returned here, something has blocked or prevented the UPC from purging.

For AGC/PRG, it's very rare to have issues with UPCs deleting. The most common error is if the UPC is in the Ordsku table in the REF_ITEM field.

Table

select *
from rms.ordsku
where ref_item = '',

23

select *

24

from rms.ordsku

25

--where ref_item = '';

26

Data Grid

|◀ ◀ ▶ ▶| + - ▲ ✓ ✕

	ORDER_NO	ITEM	REF_ITEM	ORIGIN_COUNTRY_ID
▶	20364755	11365734	610764826176	USA
	20364762	2444	085000007167	USA
	20364796	8789250	030111420411	USA
	20364797	6873410	030111416735	USA
	20364802	12712854	846675011404	USA

Deleting Process ID's

Once all UPCs have deleted out of both systems, go back into RMSv16 and delete your Process IDs. This step is needed because AGC/PRG will re-use (or do a Price Change on) their UPCs — if the Process IDs are not deleted or cleared out of RMSv16, then when the new UPCs are inducted, it will error upon induction.

1. From the RMSv16 main screen, select Notifications (Bell Icon), and at the bottom select "See All."
2. The Notifications screen will open.
3. In the Search field above Description, enter your Process ID with a % (wildcard) sign in front — e.g., %3875833 — then hit Enter and your record should return.
4. Select the Description link; the Data Loading Status screen will open. Select the red X at the top.
5. A warning box will appear asking "Are you sure you want to delete this record?" Select Yes.
6. You'll be taken back to the Data Loading screen and the record should be gone — it should state "No Data to Display."
7. Select Save and Close at the bottom right; you'll be taken back to the Notifications screen.
8. Repeat this process for any other Process IDs you need to delete.

Benefits

• Better information out of RMS with UDA tracking and reporting ability.
• Adding _D to the end of the item description is a quick way to identify that the item is deleted.
• Adding (D) to the beginning of the VPN should prevent a supplier from shipping.
• Adding UDA ID 533 and UDA Value 2 flows into IKB and identifies the item as deleted.

The Process

Buyer determines the item is a corporate delete. The buying team can either:


1. Update the item on the front end in RMS v16:
   Add _D to the end of the item description.
   Add (D) in front of the VPN.
   Add UDA 533, Value 2.

Or:

2. Download the item from RMS v16 following the steps below and send it to the Data Steward Team to be uploaded (strongly recommended if you have multiple RINs).



Note on Parent/Child RINs: If an item has 1 Parent and 1 Child, both RINs need to be updated.
If an item has 1 Parent and many Children, only the Child RIN needs to be updated.

Step 1 — Create Your Item List

1. Create your item list in RMS v16, including both Parent & Child RINs if necessary.

Step 2 — Download the Item List from RMS

1. Click the Tasks button and choose "Items."

	ORACLE Merchandising
★ ✓ 🔔	Tasks ⚲ Search for a task Foundation Data ˃ Items ˃ • Cost ˃ Price ˃ Orders ˃

2. Choose "Download Items from RMS."

	ORACLE Merchandising
★ ✓ 🔔	< Items ▼ ⚲ Search for a task Create Item Manage Items Download Items from Staging Download Items from RMS Upload Items from Staging Upload Items from File Upload Items Step 2

3. Enter the Item List # and click Search. Item details will appear at the bottom of the screen.
4. Click the Download button.

ORACLE

Merchandising

👤 username ▾ ❓

Download Items from RMS ✕

▲ Search

Item 🔍 Item Description Department ▼ Class ▼

Advanced Saved Search Default ▼ Subclass ▼ VPN ▼ Item List ▼ Supplier Site ▼

Search Reset Save...

▲ Results

Actions ▾

View ▾

💾↑

📋↓

🔳 Detach

Download

Item	Item Description	Supplier Site	Department	Class	Subclass
10294178	FRAME 8X10 WALNUT_D	613705565	795	1101	1
10348111	BP ACACIA WOOD FRAME GREY...	613705565	795	1101	1
10348112	BP ACACIA WOOD FRAME GREY...	613705565	795	1101	1
10348622	BP PS FRAME METAL & WOOD L...	613705565	795	1101	1
10348646	BP BARNWOOD TEXTURED WO...	613705565	795	1101	2
10348650	BP BARNWOOD TEXTURED WO...	613705565	795	1101	2
10902669	5X7 RAISED DIAMOND GRAY_DIOI	1056936	795	1101	1
10908125	BP BARNWOOD TEXTURED WO...	613705565	795	1101	1
5. A box will pop up — choose "Item Master." A Process Description will auto-populate. Click OK.

Step 3 — Open the File in Excel

1. You'll see the option to Open the file — choose Open with Microsoft Excel.
2. The file that opens is the "Item Induction Base Template." Note the multiple tabs at the bottom of the spreadsheet.
3. Click the “Item Master” tab: This tab contains all Item Description information from RMS in columns X, Y, Z.
4. Buying team will need to add _D at the end of the item description in column X.



Status	Item Description	Secondary Description	Short Description
Approved	BP ACACIA WOOD FRAME GREY WASH WYATT 5x7_D	BP 5x7 Acacia Wood Frame Grey Wash Wyatt_D	BP ACACIA WOOD FRAME_D
Approved	5X7 RAISED DIAMOND GRAY_D	5X7 RAISED DIAMOND GRAY_D	5X7 RAISED DIAMOND GRAY_D
Approved	BP METAL CLAD FRAME 5x7 - OFF WHITE W/PEWTER_D	BP METAL CLAD FRAME 5x7 - OFF WHITE W/PEWTER_D	BP METAL CLAD FRAME_D
Approved	BP MIRROR ON MIRROR FRAME 4x6 - SILVER TEXTURE_D	BP MIRROR ON MIRROR FRAME 4x6 - SILVER TEXTURE_D	BP MIRROR ON MIRROR FRAME_D
Approved	FRAME 8X10 WALNUT_D	FRAME 8X10 WALNUT_D	FRAME 8X10 WALNUT_D



5. Click the “Item_Supplier” tab. This tab contains the VPN in column E.
   Buying team will need to add (D) in front of each VPN



Supplier	Primary	VPN
61370556	Yes	(D) 150334601
1056936	Yes	(D) 2267-57
61370556	Yes	(D) 18357-44A-14
61370556	Yes	(D) 11679-02M-27
61370556	Yes	(D) 11679-46-27



6. Click the “Item_LOV_UDAs” tab.This tab contains any UDAs currently attached to the items. Please leave these rows as-is
   User will go back to the Item Master tab and copy all RIN#s from column ‘B’ (only Child RINs live on POGs).
   Paste those RIN#s in Column B of the Item_LOV_UDAs tab.
   In Column A chose “Create” for any new RINs and add the Corporate Delete UDAs in columns C & D



Action	Item	UDA	UDA Value
	10348611	5463	15
	10348612	5463	15
	10348650	9632	2
	10902669	9632	2
	10908125	5463	15
	10908138	5463	15
Create	10348612	533	2
Create	10348622	533	2
Create	10348646	533	2
Create	10348650	533	2
Create	10902669	533	2
Create	10908125	533	2
Create	10908138	533	2
Create	10908139	533	2
Create	10908170	533	2
Create	10908175	533	2

Step 4 — Save & Send

1. Save the file to your personal drive with whatever name you choose. The file will automatically be in the correct ODS format (Open Document Spreadsheet).
2. Send the ODS file to the Data Steward Team for upload. Please note "Corporate Delete" in the subject line. You're done!
3. DST Uploads via Tasks>Items>Upload Items From File

What it is

A re-class moves an approved item from one department/class/subclass to another in RMS. Buying teams request them through the DST Inbox; DST checks that the item can safely move, keys the re-class in RMS v16 (and in RMS v10 where required), and the change is applied by the nightly batch. Most of the work is in the checks beforehand: forecasting, mandatory UDAs, open orders on the deals tables, pack components and financial (Lawson) moves are the usual reasons a re-class fails.

Process at a glance

1. Receive the request in the DST Inbox and check the re-class form is complete.
2. Run the pre-re-class checks: forecasting, mandatory UDAs, hierarchy changes, financial moves, and open or pack orders.
3. Key the re-class in RMS v16, and in v10 (single item or item list) where required.
4. Report the night's item count before leaving for the day.
5. After the batch, validate the results and fix any failures (open orders, pack components).
6. Reply to the original email with the canned response once validation is complete.

Definitions

About this Procedure

• Purpose: documents the steps needed to complete RMS item re-classes.
• Scope: mandatory for all DST members when creating or editing item re-classes for the buying groups.
• Training: DST makes sure team members understand this SOP. Buying teams are trained quarterly on submitting re-classes correctly.
• Responsibility: DST updates and maintains this procedure.
• Systems: the buying group's Item Re-class form, RMS v16 & RMS v10, Toad/SQL, and the DST role in v16 & v10.

Receiving a Re-class Request

1. Buying teams email the DST Inbox with the subject FINANCIAL RECLASS or RECLASS [1, 2, 3, …], depending on the type of re-class.
2. During open re-class cycles, check the inbox several times a day and move new emails to the Received folder. Leave them unread until you start working on them. The manager assigns re-classes based on workload.
3. Open the email and confirm the re-class form is filled out completely and correctly. The blank template is on the HUB under Code M → Support → ORUP → Templates.
4. If more than five items are going to the same dept/class/subclass, the buying group must supply an item list, one for v16 and a separate one for v10 (v16 item lists don't flow to v10). v16 items must be at the Parent level.
5. Keep a running total of items being processed each day and tell RAVE/RIB, so they can adjust and keep batches from running long (25k soft cap).

Re-class form columns

Pre-Re-class Checklist

Run these checks before keying anything. Each one catches a common cause of a failed re-class. Links go to the queries in the Re-class Query Index.

Forecasted Items

1. Run Q3 to see whether the destination department is forecastable, then Q4 (single item) or Q5 (item list) to see whether the items are on forecasting. The item's forecastability must match the destination.
2. Item must stay forecastable: the Forecasting Team sets up the new dept/class/subclass as forecastable. If the destination dept isn't forecastable, it must be added to a domain for the financial group (see the domain query in the query index).
3. Item doesn't need forecasting: ask the Forecasting Team to change its replenishment method to min/max. You can then re-class it without making the destination forecastable.

Merchandise Hierarchy Changes

Always check whether the destination dept/class/subclass was recently changed. Search the DST Inbox for an email tagged "FYI . . . Please Read" titled "Please Map New and Edit Dept, Class, and Subclasses". These stay in the inbox for 48 hours, then move to the Merchandise Hierarchy folder.

Keying a Re-class in RMS v16

One screen handles single items and item lists, and is also where you view and delete pending re-classes.

1. From Tasks, select Foundation Data → Items → Reclassifications.
2. The Reclassifications screen lists every pending re-class, with its details below.
3. Click the green +, or Actions → Add.
4. In the Add Reclassification window, fill in:
   • Description: the submitter's last name. If they sent more than one, add a number: DOE - #1, DOE - #2, and so on.
   • Reclass Date: defaults to tomorrow. Pick a later date if needed; the system holds the re-class until then.
   
5. Under Select Items to Reclassify, choose Item or Item List and enter the Parent-level item or the item list number (or search with the magnifier/LOV).
   ℹ

   For 2-level items, the items on your v16 item list won't match the v10 item list.
6. Under Select New Hierarchy, enter the Department, Class and Subclass the item is GOING TO.
7. Click OK, or OK and Add Another to key the next one (repeat steps 4–6).
8. A warning confirms the items will be reclassified the night before the reclassification effective date. Click OK. The job runs in Phase 4 of the nightly batch.
9. Record the new re-class number in the RC# column of the re-class form.

Viewing or Deleting Pending Re-classes

Re-classes can't be edited. To change one, delete it and key it again.

1. Open Tasks → Foundation Data → Items → Reclassifications. The grid shows re-classes that are still waiting to run (not ones already processed). Select a row to see its items in Detail.
2. To delete, highlight the re-class and click the red X (or Actions → Delete). Select Yes at the warning.
3. Click Save and Close to save the deletion.

Keying a Single-Item Re-class in RMS v10

1. From Retek Enterprise, double-click the Items folder, then open the Reclassification folder.
2. Select Reclassify one item.
3. Enter the item's RIN. The Reclassification Number fills in automatically; record it in the RC# column of the form.
4. Reclassification Description: buyer's last name and department, plus a number if there are several, e.g. DOE - Dept 123 #1.
5. Effective Date: defaults to tomorrow; choose another day if needed.
6. Enter the Department, Class and Subclass the item is GOING TO, then click OK.
7. A warning confirms the item(s) will be reclassified the night before the reclassification effective date (Phase 4 of the batch).

Keying an Item List Re-class in RMS v10

1. From Retek Enterprise, double-click the Items folder, then Item List.
2. Choose Use from the drop-down, enter the v10 item list number and click OK.
3. From the top menu select Options → Create Mass Item Change → Reclassification. The re-class form opens with Item List in place of Item.
4. Record the re-class number on the form.
5. Description: Buyer Last Name - Dept # - #1 (same format as single items).
6. Set the Effective Date (tomorrow by default), enter the Department, Class and Subclass the items are GOING TO, and click OK.

Re-classes Between Lawson (Financial) Departments

A re-class that moves an item into a different Lawson (financial) group is a financial move and needs extra approval and notice.

1. Confirm it's a financial move: run Q15 to list the departments on the item list (this also catches a mis-keyed item from another department), then Q16 to check whether those departments belong to different groups.
2. Get approval from the Vice President of Merchandising Support (the Director of Merchandise Planning and Analysis can also approve moves outside the financial group).
3. Notify the DMM of Planning and Replenishment. POCs are the Director of Merchandise Planning and Analysis and the Director of Merchandise Planning.
4. Key the re-class as normal (RMS v16, plus v10 if required).
5. The Merchandise Accounting Manager reviews financial moves in a monthly report and handles any follow-up.

Nightly Batch Communication to RAVE

1. Each evening, the last team member to leave runs the batch queries: Q18 (re-classes scheduled for tonight) and Q19 (details for specific re-class numbers). The SOP also lists Q20 for tonight's re-class numbers, which isn't in the query index.
2. Post the total number of items being re-classed that night in the Record Counts/Batch Count Teams chat. Keep it under the 25k soft cap.
3. The week after, run the v16 vs v10 hierarchy comparison to confirm both systems match.

Validating Re-classes & Resolving Errors

1. After the batch, check the results with Q13 (item list) or Q14 (single item). Export to Excel and filter one item list at a time. You can select several lists together if they're going to the same dept/class/subclass.
2. If a list shows more than one value for dept, class or subclass, some items didn't move. For very large lists, just check each filter drop-down for extra values.
3. For any failure, find the reason with Q11 (last batch only) or Q12 (older rejections, by user, date or item). The rejection reason tells you what to fix.
4. Fix the cause (usually open orders or pack components), then key the failed items again.
5. Once everything validates, reply to the original email with the canned response.

Unfiltered results: one item list with all its items.

Filtered to the old class/subclass: these two items did not re-class and must be done again.

Failed Because of Open Orders

1. An item usually fails because of an open PO on the deals tables, or because it's a component of a pack that's on order.
2. Run Q7 to find the item or item list on open orders, then check those PO numbers with Q8 (both deals tables) and Q9 (open appointments, which must be closed before the PO can be). Together they give you the POs that need closing.
3. Export the results to Excel with columns expanded, a gray header row, a filter and all borders. Include PO number, status and, optionally, item number.
4. Email the buying group asking them to cancel the POs and let DST know when done. For a few POs, paste a screenshot into the email; for more, attach the spreadsheet.
5. When they confirm, check the POs are closed (Q10 in the SOP, which isn't in the query index), then key the re-class again. If RMS still sees a PO as open, wait a few minutes and retry.

Failed Because of Pack Components on Order

1. If the item isn't on order itself but still fails for open orders, it's probably a component of a pack that is on order.
2. Run Q6 with the item number. It returns the POs the pack is on.
3. Ask the buying group to cancel those orders, then key the re-class for the component item(s) again.

1. Building the Item

1. Follow all normal DST item build standards.
2. Due to the nature of the items, they typically do not have associated GTINs, so price prompt items will always be built with a system generated GTIN

Dept	Class	Subclass	Parent Item Description	Transaction Item Description	Web Description	Supplier Color	Primary Ref Ind	Item Number Type	GTIN
23	1001	2	Askar Handicrafts	Askar Handicrafts	Askar Handicrafts		Yes	UCC12	Generate

3. After completing visual checks, run the template through the Template Checker.
   Most price prompt items are from Overseas — their checker may have issues, so always run it to catch errors.
4. Once ran through the template checker, populate the template
5. Save as .ods.
6. Upload to RMS v16: Tasks → Item → Upload Items from File
   Set Template to Item Master, Destination to RMS Tables, select your file → Upload.

Adding Locations

Once the items are built:

1. In RMS v16: Tasks → Items → Upload Items — Step 2
2. Select the .ods file, assign a process name → Upload.

Creating the Incident Ticket

1. Go to CA Service Desk Manager: internal-link
2. File → New Incident
3. Fill in the following fields:
     • Affected End User: Whoever submitted the item request
     • Incident Area: Oracle Retail → RMS → Other
     • Group: START Group
     • Summary: Add Item To Special Items Table - Price Prompt
     • Description: Please mark newly created item, [TRANSACTION RIN(s)], as price prompt at the location level, and then add it to the special items table
4. Save. You will receive an email confirmation with the incident number and buying group.

1. From the Item screen (Clipboard icon → Item → Manage Items), enter the item provided from the SMU or email.
2. In the results box, select the item, and the Item screen will open.


Item

Description

Transaction Level

▼

Item Level

▼

Status

▼

Item Type

▼

▲ Results

Actions ▼ View ▼

➕⭐ 📋 ✏️ 👓

📊↓ ⏳↓

📄 Detach ↪️ Wrap

Cost Change

Item	Description	Item Level	Department	Class	Subclass	Subclass Name	Status
14806261	Aroma 4-Cup Rice Cooker White	Level 2	826	1401	1	RICE/PRESR/STM ...	Approved



3. In the bottom right corner, select More Actions → Locations, and the Item/Loc screen will open.


▲ Transaction "14806261 | Aroma 4-Cup Rice Cooker White
Parent"14806260 | Aroma 4-Cup Rice Cooker
Department826 | SMALL ELECTRICS
Class1401 | COOKING APPLIANCES
Subclass1 | RICE/PRESR/STM COOKE
Transaction LevelTransaction
Unit Retail19.00
Unit ELC13.5000
Markup %28.95
CurrencyUSD
SellableYes
OrderableYes
InventoriedYes
---
▲ Descriptions
*Description Aroma 4-Cup Rice Cooker White
*Short
Secondary
Number Type Oracle Retail Item Number
▲ Cost and Price
▲ Usage and Units
*Store Order Multiple Case Pack
*Standard UOM EA
UOM Conversion Factor
Merchandise
Forecastable
On Replenishment
▲ Attributes
▲
✔ Suppliers
Retail by Zone
✔ Locations
Item Up Charges
✔ List Children
Simple Pack ▶
Transformation
✔ Replenishment
Substitute Items
✔ User Defined Attributes
▼


4. Enter the location in the Loc field.


Transaction "14806261 | Aroma 4-Cup Rice Cooker White

Actions ▼ View ▼

➕ ✏️

📊↓

📄 Detach

▼

ALL ▼

Location Type	Location	Name	Status	Average Cost	Unit Cost
Store	2	NORF PACKAGE STORE	Active	9.0000	13.5000
Store	7	HUNTINGTON HALL MM	Active	9.0000	13.5000
Store	8	NORF V55 MM/GAS	Active	9.0000	13.5000
Store	9	NORF CEP 76 MM/GAS	Active	9.0000	13.5000
Store	10	NORF MAIN STORE	Active	14.3623	13.5000
Store	15	NORF N LODGE STORE	Active	9.0000	13.5000
Store	16	LCREEK MAIN STORE	Active	13.5071	13.5000
Store	20	YORKTOWN MM/GAS	Active	9.0000	13.5000
Store	21	CHEATHAM ANNX MM/...	Active	9.0000	13.5000
Store	24	NSA HAMPTON ROADS ...	Active	9.0000	13.5000
Store	28	PORTS SCOTT CTR MAIN	Active	9.0000	13.5000
Store	29	NAVY EXCHANGE POR...	Active	9.0000	13.5000
Store	30	PORTS VA NMC MM	Active	9.0000	13.5000
Store	31	OCEANA PACKAGE ST...	Active	9.0000	13.5000
Store	32	OCEANA MM / UNIFORMS	Active	9.0000	13.5000
Store	34	OCEANA MAIN STORE	Active	13.5184	13.5000
Store	35	DAMNECK PACKAGE ST	Active	9.0000	13.5000
Store	37	DAMNECK MAIN STORE	Active	9.0000	13.5000
Store	43	LCREEK HOME GALLERY	Active	9.0000	13.5000
Store	50	NEWPORT MINI MART	Active	9.0000	13.5000



5. If you do not have the option to query by location, select the View drop down box and select Query by Example:


Transaction "14806261 | Aroma 4-Cup Rice Cooker White
Actions ▼
View ▼
➕ ✏️ 📊↓
📊↓
📄 Detach
Location Type	Location	Name	Status
Store		YOKO NEX DEPOT	Active
Currency Views ▶
Columns ▶
Detach
Sort ▶
Reorder Columns...
✔ Query by Example





6. Once the location record shows, select Actions -> Location Traits and the Item/Loc Trait screen will open


Transaction "14806261 | Aroma 4-Cup Rice Cooker White
▲ Apply Updates To
Store 461 | YOKO NEX DEPOT
Customer Order Attributes
Returnable
▼
Back Orderable
▼
Grocery Attributes
Launch Date
📅
Quantity/Key Options
Prohibited ▼
Manual Price Entry
▼
Deposit Code
▼


7. In the Quantity Key field – select drop down and select Required.


Transaction "14806261 | Aroma 4-Cup Rice Cooker White
▲ Apply Updates To
Store 461 | YOKO NEX DEPOT
Customer Order Attributes
Returnable
▼
Back Orderable
▼
Grocery Attributes
Launch Date
📅
Quantity/Key Options
Required ▼
Manual Price Entry
▼


8. Select Save and Close until you are back to the Item screen.
9. Repeat for additional items.

Serializing a Single Item

1. Look up the RIN at the Transaction Level in RMS v16.
2. Navigate to More Actions → Locations.
3. Scroll down and select More Actions → Location Attributes.
4. Click the Green Plus Sign (+). In the Add Locations box, use the dropdown to select All Stores → click OK.
5. Scroll to the bottom right, select the required UIN Type and UIN Label options from the dropdowns → click Save and Close.
6. Save and Close out of the item.

Serializing Multiple Items (Mass Change)

1. Create an Item List in RMS v16 (can be Parent + Transactions, or just Transactions).
2. Search for Item List in RMS v16.
3. Click Actions → Mass Change → Item/Locations.
4. Click the Green Plus Sign (+). Select All Stores → click OK.
5. For mass change, the Primary Supplier of the items must be entered in both the Primary Supplier and Primary Country fields.
6. Select the required UIN Type and UIN Label options → click Save and Close.

What it is

The Item Induction Checker is an Excel macro that pre-validates an Item Induction Template before it's submitted or uploaded to RMS. It checks every row on the main sheet and on the Location tab:

• formats and allowed drop-down values
• required fields for the selected Action
• relationships between fields (for example, Case Size must be a multiple of Inner Size)
• live RMS lookups: suppliers, GTINs, hierarchy, Diff IDs, UDAs and retail

Problems are highlighted on the sheet, so you can fix common errors before they turn into failed uploads.

• Header-driven: it finds columns by their header names in row 7, so inserted or reordered columns still work as long as the headers are unchanged.
• Data range: rows 8–1000 on the main sheet. The Location tab uses row 2 for its headers.
• Actions with specific rules: Create Item Family, Add Tran Item or GTIN, Add Item Supplier and Add Item Supp Country Dimension. General checks apply to every active row.

When a new supplier, UDA, brand or size is created in RMS, the checker's lookup tables need updating. See Updating Template Checker Tables.

Running the Checker

1. Fill out the Item Induction Template as normal, using the values for the Action on each row.
2. With the template's main sheet active, run the validation macro.
3. Read the completion message and the results in cells A2–A4.
4. Review every highlighted cell. Many also have a cell comment with the exact reason or the correct value.
5. Fix the data and run the checker again. Repeat until A3 reads Successful, No Errors were Found, then save.

Reading the Highlights

Swatches are approximate; text in highlighted cells is dark red unless noted.

Required Fields by Action

Supplier & Packaging

Descriptions & Brand

Color, UDA & E-Commerce Fields

Required UDAs by hierarchy

Department-Specific Rules

Perishable required:

Ecomm Warranty eligible:

Consignment/Concession required:

Dimensions required (Create Item Family): Package Type, Depth, Width, Height, Gross Weight and Presentation Method are only required for these depts:

GTIN / UPC & Sizes

Retail & Hierarchy

Allowed Drop-Down Values

Filled-in fields must match these values exactly. Blank fields are skipped unless another rule requires them.

Expired phases: a Phase ID can be on the allowed list and still be rejected once its season has ended ("Phase ID References an Already-Ended Season"). The comment gives the end date.

Countries: Source Country must be USA. Manufacture Country must be a valid three-letter code from the tool's built-in list of 246 codes.

Location Tab

Exceptions at a Glance

• Create Item Family: Supplier Color can be blank when NRF Color Code = 000; the six dimension/packaging fields can be blank when the dept doesn't require dimensions.
• Dept 884 + Class 1401 and Buyers 60, 90, 720, 960: exempt from the dimension/packaging fields.
• Add Item Supp Country Dimension: skips the Inner Size / Case Size / Ti / Hi rule and the NRF Color Description check.
• Add Item Supplier: VPN isn't required; any one of Family ID, Parent Item or Transaction Item is enough; skips the NRF Color Description check.
• Brand at start of description: skipped when the description contains "S/O"; apostrophes can be left out.
• GTIN: GENERATE (all caps) is accepted; duplicate GTINs are only compared within the same Action.
• Color Code 262S is never flagged as an existing color/size under the parent.
• Ecomm Warranty: only flagged when 1 - Yes is chosen for an ineligible dept.
• Perishable depts: Yes or No are both fine; only blank is an error.
• Location tab: only required when an Action on the main sheet needs it.
• Brand list: if it can't be opened, the brand-exists check is skipped instead of failing every brand.
• Phase expiration: only the seasons listed above are checked for expiry.

Fixing Errors: Recommended Order

1. Start with the A4 summary to see which categories are present.
2. Fix the orange required-field and format errors first.
3. Read the cell comments for errors that give a specific RMS value, UDA ID, phase end date or description detail.
4. On Add Tran Item or GTIN rows, fix hierarchy mismatches before looking into RMS duplicates on the same row.
5. Resolve RMS existence and Diff/Size conflicts before treating a row as ready.
6. Check duplicates across the whole sheet, not just the rows on screen.
7. Run the checker again until A3 reads Successful, No Errors were Found, then save.

Troubleshooting

• The checker validates the active worksheet, so start it from the template's main sheet.
• Headers must stay in row 7 with data in rows 8–1000. If an optional header is missing from the template, its check is skipped.
• If RMS can't be reached or an unexpected error happens, the tool shows a failure message instead of reporting success. Fix the connection and run it again.
• While it runs, Excel events and calculation are paused and then restored. Initial Retail, MSRP and Unit Cost are set to General number format.
• The brand list (X:\shared\folder\Brand2.xls) is opened read-only and hidden while the brand check runs.
• When new seasons are added, the phase expiry dates in the macro also need updating, or the new phases won't be checked for expiry.

What's New in Version 2.0

• Family ID consistency: rows with the same Family ID must share a Dept/Class/Subclass; Create Item Family rows must share a Size Group ID.
• NRF Color Code format: exactly three digits, 000–999.
• Dollar signs are flagged in Initial Retail, MSRP and Unit Cost.
• Parent Description limited to 100 characters.
• Prohibited characters (! @ & $ ™ ® © ?) checked in Parent, Transaction and Web descriptions.
• GTIN check digit validated with the GS1 calculation.
• Package-type duplicates now checked per Family ID + GTIN, covering Case, Each, Inner, Outer and Pallet.
• Add Item Supplier redundancy: flags rows that repeat the Create Item Family supplier.
• Add Tran Item or GTIN now requires Initial Retail, Supplier Site, Unit Cost and Buyer.
• Header-driven processing: columns can be inserted, removed or reordered safely.

Creating a New Web Brand Name

1. Forward the buying team's email (with the Web Brand template attachment) to the Senior MAs and wait for approval.
   ***Senior MAs will specify the case format for the Brand Description and UDA Value Description.
2. In RMS v16:
   Tasks → Foundation Data → Data Loading → Download
☰ ORACLE Merchandising
👤 username ▼ ❓
Download Data ×
Template Type
Items ▼
Template
Brands ▼
3. Click Download. Open the downloaded file in Microsoft Excel
Opening Brands - 12.28.18 10.35 AM.ods ×
You have chosen to open:
≡
Brands - 12.28.18 10.35 AM.ods
which is: OpenDocument Spreadsheet
from: internal-link
What should Firefox do with this file?
Open with
Microsoft Excel (default) ▼
Save File
Do this automaticallly for files like this from now on.
4. On the Brands tab:
   clear all data below headers (Row 1), then fill in:
     • Action (A): CREATE
     • Brand Name (B): Brand name in ALL CAPS
     • Brand Description (C): Brand name per Senior MA instruction
5. Repeat for each additional brand. Save as .ods file to:
   📁X:\shared\folder
   Save as "Brand UDA Updates *Date*
6. In RMS v16:
   Tasks → Foundation Data → Data Loading → Upload
   Set Template Type: Items, Template: Brands, browse to your .ods file → Upload File
7. If no notification received → brand created successfully. If notification received → error occurred, check issues and troubleshoot using the query below.

-- Check upload status (use lowercase RMS v16 User ID)
SELECT to_char(s.action_date, 'DD-Mon-YY HH:MI:SS') a_date,
       s.process_id, s.process_desc, s.status, s.user_id, s.file_path
FROM rms.svc_process_tracker s
WHERE user_id = 'yourusernamehere'
ORDER BY action_date DESC;