NEXCOM

Data Steward Team Guide

Supply Chain Systems · Internal Use Only

Document Decision Guide

Use the tables below to identify the correct form or process for any DST action. When in doubt, refer to the relevant SOP linked in the sidebar.

Building & Adding Items

If you need to…Use this
Build an itemItem Induction Form
Add a supplierItem Induction Form
Add a transactionItem Induction Form
Add a GTINItem Induction Form or manually via Front-End
Add dimensionsItem Induction Form or manually via Front-End
Delete a GTINItem Induction Form
Add UDAsItem Induction Form
Create a consignment itemItem Induction Form — change Column C
Create a drop ship itemItem Induction Form — change Column BH

Supplier-Level Updates

If you need to…Use this
Update Primary Supplier at Supplier LevelManually or via RMS Download
Update Drop Ship Flag (Direct Ship in v16)Manually or via RMS Download
Update VPNManually or via RMS Download
Update Supplier Color (Diff 1 in v16)Manually or via RMS Download
Update Consignment RateManually or via RMS Download
Update Default UOPManually or via RMS Download
Update Inner and Pack — Cross docked itemSend to DST
Update Inner and Pack — Warehouse itemSend to ROADS
Update Ti/HiManually or via RMS Download
Update Rounding LevelManually or via RMS Download
Edit DimensionsManually or RMS Download

Hierarchy & Location

If you need to…Use this
Move item to a different Dept/Class/SubclassRe-class form (first full week of every month); certain changes require Management approval
Create, add, or edit a Dept/Class/SubclassMerchandise Hierarchy Form (twice a year); certain changes require Management approval
Add a location to a RINItem Induction Form — Location Tab only
Update Primary Supplier at Location LevelManual Maintenance Form
Update Quantity KeyContact START/DST
Update Location StatusManual Maintenance Form
Update Store Order Multiple at Location LevelManual Maintenance Form

UDAs, Seasons & Descriptions

If you need to…Use this
Update UDAs (List of Values only)RMS Download
Delete UDAs (List of Values only)RMS Download
Update, Add, or Delete Seasons/PhasesManually or Mass Change via Item List
Update, Add, or Delete Ticket TypeManually or Mass Change via Item List
Update BrandManually via Front-End or RMS Download
Update Suggested Retail (MSRP)Manually via Front-End or RMS Download
Update CommentsManually via Front-End or RMS Download
Update Description, Short, or SecondaryManually via Front-End or RMS Download

Email Responses

Canned / template email responses used by the Data Steward Team. Each subheader below is a scenario; the text beneath it is the ready-to-send response — click the copy icon to copy it exactly as written.

Action Required

25
ACTION REQUIRED for Add Web Loc(s):
Email Response
Upon initial review of the submitted Item Induction Location form, please review the following field(s):

Items are missing the following Web requirements:
- Missing BOPIP UDAs

Please submit an update to Add the BOPIP UDAs along with your request to Add Web locs.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION REQUIRED for Update Primary Supplier: — Suppliers not attached to items
Email Response
Upon initial review of the submitted Manual Maintenance Location form, please review the following:

Please check/validate suppliers are attached to the item(s).

Please submit an Add Supplier Item Induction form along with your manual maintenance form.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION REQUIRED for Update Primary Supplier: — Incorrect Supplier entered on form
Email Response
Upon initial review of the submitted Manual Maintenance Location form, please review the following:

Please check/validate supplier # is correct on your form as this supplier is not attached to the item(s).
-You have supplier #698140691 on your manual maintenance form but your form is indicating DeCA which is supplier #835949082

Please submit an Add Supplier Item Induction form (if necessary) along with your manual maintenance form or update your manual maintenance form and resubmit.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION REQUIRED CHECKER NOT BEING USED: — Doesn't show template ran though checker
Email Response
Good morning and are you having checker issues?  Your template was not ran through the checker prior to submitting this template.

Please run your template through the checker and save that copy or advise if you’re having issues.  If you’re having issues with the checker, please provide the error you are receiving.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION RQUIRED:
Email Response
Upon initial review of the submitted Item Induction form, please review the following field(s):

**List invalid fields**

Please review, correct and re-submit.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION RQUIRED for Building a New Brand Request:
Email Response
Upon initial review of your Brand Request Form,  please review the following field(s):

- Web Brand (column C) – please check and validate Spelling is correct.
- You have FAUDI SPADA on the form but the website shows it as FEVDI SPADA
- Web Brand/UDA Display (column D) – please check that this is populated correctly – see the notes for this field below:
- This column needs to show the Vendors brand standard and how the Brand should be displayed on MNE.com's search bar results and copy - i.e. it be all CAPS, Proper, miXed and also should include any necessary characters like accents, etc
- You have this in All Caps FEUDI SPADA – is that correct or should it be proper case?

Please review, make any necessary corrections and re-submit.  If you attached an item induction template to build items, please confirm that is still accurate and correct (in case changes were needed for the Brand) and reattach with your Brand Request form as well.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION RQUIRED for Location Tab (duplicate IFID records):
Email Response
Upon initial review of the submitted Item Induction form, please review the following field(s):

- Please review your Location Tab.  You have duplicate records - for each Item Family ID, you have it listed multiple times – this will cause the system to throw errors.  You only need the item Family ID once for each unique Location record.
- Highlighted in red & bolded the records you should have on your template.

Please review, correct and re-submit.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION RQUIRED for Add Trans (Diff/Size Issues):
Email Response
***View in HTML***

Upon initial review of the submitted Item Induction form, please review the following field(s):

- Please review your size code you are trying to utilize – you cannot change your size code, it must match the size code of the Parent item you are trying to attach this Tran to
- Your induction template is requesting size code 006S be used but the Parent # 19745338 you are trying to attach it to is built with a size code of 036S.  This will error on us when we induct it into RMS.
- It looks like you requested size 25 be added to 006S but it may have needed to be added to 036S.

Please review, correct and re-submit.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION RQUIRED for Add Trans (Diff/NRF Issues):
Email Response
***View in HTML***

Upon initial review of the submitted Item Induction form, please review the following field(s):

- Please review your NRF color code you are trying to utilize – you cannot reuse a color code if it’s already been used for that size code
- Please review the highlighted records – we show this color code already being used for this Parent(s).  Please update your color code to one that is not being utilized and resubmit.
- We have attached a report that shows what is currently being used for those Parents

Please review, correct and re-submit.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION RQUIRED for Brands, Item Desc, & Loc Tab:
Email Response
***View in HTML***

Upon initial review of the submitted Item Induction form, please review the following field(s):

We see you ran your template through the checker, did you not receive any errors?

- 5 ERROR: Qty  Brands has an incorrect value. Please fix and rerun script.
- (Must be in the validation file. – Did not see Hawaiian King Chocolate built in our system or anything with Hawaiian King.  If you need this built please submit on the Web Brand form that is on the HUB and DST will build it for you.

- Once the Brand is built or you have the correct Brand, please review your item descriptions again and make sure they are consistent.  You have Hawaiian Brand Chocolate for the first 3 records and then Hawaiian King (without the chocolate for the last 2 records.  You need to use the brand correctly for all Item Descriptions
- Location Tab: there is no data on this tab.  Please populate or not locations will be attached to your items.

Please review, correct and re-submit.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION RQUIRED for cost higher than retail:
Email Response
***View in HTML***

Upon initial review of the submitted Item Induction form, please review the following field(s):

WARNING: Qty 1 Costs are higher than Retail (Col AG and BN). Please validate. Is this correct?  You have a cost of $740 and a retail of $6.99.  This would impact your financials for markups/markdowns, etc.

Please review, correct and re-submit.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION RQUIRED for Dimension Field(s):
Email Response
Upon initial review of the submitted Item Induction form, please review the following field(s):

Please review your Gross Weight field (column CA).  This needs to be a number with no other data included.  You have several that have the UOM included in the field.  This will error upon induction.

Please review, correct and re-submit.

If you have any questions, please let us know.

Thank you,
Data Steward Team
Missing Web Requirements for Adding Loc(s):
Email Response
***View in HTML***

Upon initial review of Item Induction template to Add Loc(s), we noticed you have Web loc(s) (781 and/or 9870) on your Location Tab.  Please keep in mind, if you are adding 781, you MUST add 9870; and items MUST have all Web Requirements attached before we can process your request.

Items are missing the following Web requirements:
- Missing BOPIP UDAs
- Brand
- VPNs if vendor provided
Here is the link to the HUB that provides the Web Requirement Instructions and have attached a soft copy as well.

Please review your items and submit a download form to add any missing Web requirements and resubmit all template to DST for processing.

If you have any questions, please let us know.

Thank you,
Data Steward Team

Or

Upon initial review of Item Induction template to Add Loc(s), we noticed you have Web loc 9870 on your Location Tab.  Why are you adding the Web Warehouse loc?  You don’t have 781 attached to this item.  Pease keep in mind, if you are adding any web loc(s) you must add both 781 and 9870, and you MUST have all Web Requirements attached before we can process your request.

NOTE:  If you just need loc 182 to resolve the pricing issue, then please resubmit without the 9870 loc so we may process.

Items are missing the following Web requirements:
- Missing BOPIP UDAs
- Brand
- VPNs if vendor provided
- Web UDA’s (
- MSRP’s (unless on the exempt list from Web Team)
Here is the link to the HUB that provides the Web Requirement Instructions and have attached a soft copy as well.

https://intranet.nexad.nexweb.us/M/MS/ORUP%20Training%20Materials/Web%20Requirements%20for%20New%20Items%20-%2003Mar23.docx

Please review your items and submit a download form to add any missing Web requirements and resubmit all template to DST for processing.

If you have any questions, please let us know.

Thank you,
Data Steward Team
UPLOAD w/ Errors:
Email Response
Your Item Induction form received the following error(s) during the upload process with the following error(s):

Once reviewed, please correct and re-submit on the proper form.

If you have any questions, please let us know.

Thank you,
Data Steward Team
UPLOAD w/ Errors for mis-matched size group ids w/in a grouping:
Email Response
Your Item Induction form received the following error(s) during the upload process with the following error(s):

You have a mis-matched size group id for 1 of your Item Groupings.  Nots sure if they should have been grouped together or not; but you cannot have different size groups for any given Item Grouping.  We have attached your original template and have highlighted the Item Grouping and then in red showed where the size group id is different.  These 4 items did not build.

Action:  If these items should be part of this grouping then please resubmit (on a clean item induction template) the 4 items as an Add Trans utilizing the correct size group id/values.  If this is truly a unique and different item, then submit (on a clean induction template) a Create Item Family action for these 4 items.

All other items have built successfully and we have attached the BI Item report for those items.

Once reviewed, please correct and re-submit on the proper form.

If you have any questions, please let us know.
UPLOAD w/ Errors for a duplicate color code w/in a grouping:
Email Response
***View in HTML***

Your Item Induction form received the following error(s) during the upload process with the following error(s):

- This child/grandchild item already exists for item 20236711 – You duplicated a color code for the same Parent (020 – Gray).  You cannot use the same color/side combination within a single item grouping.
- We’ve attached your original induction template highlighting the item that error out and bolded in Red the fields that need to be corrected

Action: Please submit a new clean item induction template to add the missing item using the “Add Trans” Action on the Item Induction sheet and change your NRF color code to something different and use a different color name.  You cannot use Gray as you have used it for another transaction within that same grouping.  There needs to be some differentiator.  For example is a Heather Gray, Light Gray, etc.

All other items have built successfully and we have attached the BI Item report for those items.

Once reviewed, please correct and re-submit on the proper form.

If you have any questions, please let us know.

Thank you!
Data Steward Team
UPLOAD w/ Errors for invalid UDA Id value:
Email Response
Dafne,

Your Item Induction form received the following error(s) during the upload process with the following error(s):

Invalid UDA id.  Please be aware your items have been built and approved but UDA's have not been attached.  If you need the UDA(s) attached to these items, please submit a request to add these UDA's to your items.

Once reviewed, please correct and re-submit on the proper form.

If you have any questions, please let us know.
UPLOAD w/ Errors for Hierarchy not matching Parent:
Email Response
Betsy,

Your Item Induction form received the following error(s) during the upload process with the following error(s):

Please review the record highlighted in yellow and your hierarchy.  Your requested hierarchy does match the Parent hierarchy in the system.  We have attached a report that shows you the hierarchy for the Parent # you have provided.

Once reviewed, please submit a new, clean item induction template with that single record on it for processing.

If you have any questions, please let us know.

Thank you,
Data Steward Team
UPLOAD w/ Errors for Missing Sheet/Input:
Example / reference data
ItemItem DescriptionSupplier SiteCountry of SourcingWorksheetRowColumnIssue TypeIssue Description
Item_MasterErrorMissing sheet in the input file.
ErrorInvalid template. Check the sheets and/or columns in the spreadsheet used.
Email Response
***View in HTML***

Your Item Induction form received the following error(s) during the upload process with the following error(s):

Did you by chance delete any columns or try and change anything?  Please remember this template or data is very finicky so something was deleted that is causing this to error out.  Please redownload the form and make your updates again and resubmit for processing.

If you have any questions, please let us know.

Thank you,
Data Steward Team
UPLOAD w/ Errors for Updating Dimensions when no Dimensions attached:
Email Response
***View in HTML***

Your Item Induction form received the following error(s) during the upload process with the following error(s):

Error: This dimension object does not exists for the item-supplier-country of sourcing relationship.  It looks like you were trying to update dimensions for items that did not have any dimensions attached to them.

NOTE:  If you are trying to Add new dimensions to item(s) then please either submit them via an item induction template or you may update them manually on the front end (if you have completed Item Maintenance training).  Also attaching the link to our DST Document Guide that tells you how to which form(s) or use or if you can do them on the front end by Action.

https://intranet.nexad.nexweb.us/M/MS/ORUP%20Training%20Materials/DST%20Document%20Guide.xlsx

If there were multiple updates submitted, the others had no errors.

Once reviewed, please correct and re-submit on the proper form.

If you have any questions, please let us know.

Thank you,
Data Steward Team
Action Required for Case Packs w/ Whs SOH:
Email Response
Upon initial review of the submitted Item Induction form, please review/update the following.

You're requesting to change case packs but it appears one or all of them have SOH in warehouse.  ROADS handles all case pack requests for items warehouse.  Please fill out the attached form and submit to the ROADS Team

https://intranet.nexad.nexweb.us/M/MS
File Name: Case Pack Request Form

Please review, correct and re-submit.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION RQUIRED for Pack GTIN(s) that Exist in RMS:
Example / reference data
GTINPACK_NODEPTCLASSSUBCLASSITEM_DESCCREATE_DATETIME
0721400394171725433060315012Eucerin Body Asst 12pc8/08/24
0721400394241725432960315014Aquaphor Body Asst PDQ8/08/24
Email Response
***View in HTML***

Upon initial review of the submitted Pack Induction form, please review the following field(s):

Your GTINs exists in RMS already. If the all the information is the same for the packs, then you'll find your pack item information below.  If they are not correct, you will need to submit a Delete request to delete the GTIN(s) so you may rebuild the new packs.

Please review, correct and re-submit.

If you have any questions, please let us know.

Thank you,
Data Steward Team
ACTION RQUIRED for GTIN Delete (template format/submission):
Email Response
***View in HTML***

Upon initial review of the submitted Item Induction form, please review the following field(s) for your delete request:

Please make sure you are paying attention to the field(s) you are populating.  Your data is in the incorrect field, see the procedure to note that your delete request must go in the PARENT Field as this is the only field the system is looking at when processing these deletes.

Here is the link to the instructions on the HUB and have attached a soft copy as well.
https://intranet.nexad.nexweb.us/M/MS/ORUP%20Training%20Materials/Delete%20Item%20via%20Induction.docx
How to Submit a Delete GTIN Induction Form to DST
*Note: This is to delete GTINs out of RMS and downstream systems.

For Buying Teams:
You must provide a reason for all Delete requests in the body of the email.  DST has been tasked to track all deletes as there are downstream ramifications when we process any delete requests.  NOTE: Please Do Not put the reason in the Subject Line
Reminder/Notes:
- If the Transaction Item the GTIN is currently attached to has multiple GTINs, please make sure the GTIN being deleted is NOT flagged as primary.  If it is, you must change the primary flag to another GTIN.  This is a hard stop for RMS as the purge job will error and will delay your request as it will be sent back to you for updating.
- If your Delete should only be happening in a single system (i.e. RMSv16 Only or RMSv10 Only).  You MUST notate that in your email or the delete will automatically be processed for both systems.
- If you are requesting to delete at Parent or Trans level, please be aware the items MUST meet the purge criteria in order to delete – no transactions of any kind for 2 years àIf there are any transactions out there it is a hard stop.
- If you will be building new items with these GTINs, please DO NOT attach the new Item Induction to the Delete request email.  It must be submitted to DST separately after the delete has processed.
To delete a GTIN through the Custom Item Induction template, please follow these steps:
Email Response
- Select Action = ‘Add Item CFAS’ (Column A)
- Enter GTIN(s) or Parent/Trans to be deleted in the Parent Item (Column H) - this should be whatever level you are trying to delete (i.e. GTIN, Trans, or Parent).
- Enter Buyer Number in the Buyer (Column DK)
DO NOT POPULATE ANY OTHER FIELDS:
Email Response
- Submit and E-mail to the DST (as an Excel Macro-Enabled Workbook) with DELETE GTIN (or ITEM) Request in the Subject Line

If you have any questions, please let us know.

Thank you,
Data Steward Team

Successful

17
Add Loc(s):
Email Response
NOTE: Please make sure there are no spaces after your item #(s) as it will cause issues with locs adding.

Your Item Induction form to Add Loc(s) has been successfully uploaded .  Your item/loc should be available to use within one hour, but could take up to two hours.  If you do not see your item/locs in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
Add Loc(s)/Update Status:
Email Response
Your Item Induction form to Add Loc(s) has been successfully uploaded along with your manual maintenance form to update status .  Your item/loc  and status update should be available to use within one hour, but could take up to two hours.  If you do not see your item/locs in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
Add Supplier/Loc(s):
Email Response
Your Item Induction form to Add Supplier(s) and Loc(s) has been successfully uploaded .  Your item/supplier & locs should be available to use within one hour, but could take up to two hours.  If you do not see your item/locs in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
Update Primary Supplier:
Email Response
Your Manual Maintenance form to Update Primary Supplier has been successfully updated.  Your item/Supplier update should be available to use within one hour, but could take up to two hours. If you do not see your updates in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
Update Item/Loc Status:
Email Response
Your Manual Maintenance form to Update Status has been successfully updated.  Your item/loc update should be available to use within one hour, but could take up to two hours. If you do not see your updates in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
RMS Download:
Email Response
Your RMS Download form has been successfully updated.  Your updates should be available to use within one hour, but could take up to two hours. If you do not see your updates in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
NEW ITEM BUILDS:
Email Response
Your Item Induction form has been successfully uploaded with no errors. Please see the attached report to retrieve your item information. Your items should be available to use within one hour, but could take up to two hours. Please wait until your items are FULLY in V10 (Parent, Grandparent, UPCS, Locations, etc). If you do not see your items in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
QTY KEY UPDATES:
Email Response
Your request to add Qty Key to loc(s) xxx has been completed.

If you have any questions, please let us know!

Thank you!
Data Steward Team
NEW DITTY PACK BUILD:
Email Response
Your Pack  Induction form has been successfully uploaded with no errors. Please see the attached report to retrieve your item information. Your items should be available to use within one hour, but could take up to two hours. Please wait until your items are FULLY in V10 (Parent, Grandparent, UPCS, Locations, etc). If you do not see your items in v10 after four hours from receiving this email, please contact the team.

Loc 109 has been added and qty key added.

If you have any questions, please let us know!

Thank you!
Data Steward Team
Add Supplier & Update Primary Supplier:
Email Response
Your Item Induction form to Add Supplier & Manual Maintenance form to Update Primary Supplier has been successfully updated.  Your item/Supplier update should be available to use within one hour, but could take up to two hours. If you do not see your updates in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
Add Supplier:
Email Response
Your Item Induction form to Add Supplier has been successfully updated.  Your item/Supplier update should be available to use within one hour, but could take up to two hours. If you do not see your updates in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
Add UDAs:
Email Response
Your Item Induction form to Add UDAs has been successfully updated.  Your item/UDA updates should be available to use within one hour, but could take up to two hours. If you do not see your updates in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
RMS Download for Web Requirements & Add Web Locs:
Email Response
Your RMS Download form to Add Web Requirements has been successfully updated and your induction to add Locs has been successfully uploaded.  Your updates should be available to use within one hour, but could take up to two hours. If you do not see your updates in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
RMS Download:
Email Response
Your RMS Download form has been successfully updated.  Your updates should be available to use within one hour, but could take up to two hours. If you do not see your updates in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
Update SOM:
Email Response
Your Manual Maintenance form to Store Order Multiple has been successfully updated.  Your SOM updates should be available to use within one hour, but could take up to two hours. If you do not see your updates in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
SUCCESSFUL UPLOAD:
Email Response
Your Item Induction form has been successfully uploaded with no errors. Please see the attached report to retrieve your item information. Your items should be available to use within one hour, but could take up to two hours. Please wait until your items are FULLY in V10 (Parent, Grandparent, UPCS, Locations, etc). If you do not see your items in v10 after four hours from receiving this email, please contact the team.

If you have any questions, please let us know!

Thank you!
Data Steward Team
WEB BRAND REQUEST:
Example / reference data
BRAND_NAMEBRAND_DESCRIPTION
FEUDI SPADAFEUDI SPADA
Email Response
Your Web Brand request has been created.  Please use the below in the Brand Column (AN) on the Item Induction Template:

If you have any questions, please let us know.

Thank you,
Data Steward Team

***Provide Web Brand Name in ALL CAPS and the new Description***
**Copy Jenni Blythe or Web Team Member who approved changes**

SQL Query Reference

General Reference Queries

Note: These are day-to-day lookup queries for process tracking, item/hierarchy research, and supplier verification. For queries specific to the item re-class workflow, see the Item Re-Class Process Query Index below.

1. Process & Staging Verification

Check Today's Process Tracker Actions by User (Notification check — confirms what a user has submitted today.)

SQL
alter session set nls_date_format = 'mm/dd/yyyy  HH:MI:SS';
select *
from rms.svc_process_tracker
where USER_ID = 'ANDERSDA' 
and trunc(action_date) = trunc(sysdate) order by action_date desc;

Check Staging Table Status by Process ID (Returns the count of records by process$status for a given Process ID.)

SQL
select process$status, count (1) 
from rms.svc_item_master 
where process_id = '21006523'
group by process$status;

Find Error Messages by Process ID (Returns readable error text for a failed Process ID. The commented block can be used instead to search by RIN / VPN / transaction number.)

SQL
select r.rtk_text, 
replace(c.error_msg,'@0','') error_message,
c.*
from rms.coresvc_item_err c, rms.rtk_errors r  where /*process_id in (select process_id from rms.svc_item_master
where ( orig_ref_no like '%30NuttyConcepts46%'
or item_parent like '%30NuttyConcepts46%'
or item_grandparent like '%30NuttyConcepts46%'))
and*/ REGEXP_SUBSTR(replace(C.ERROR_MSG,'@0',''), '[^@]*') = R.RTK_KEY (+)
and process_id in ('21043093')
order by process_id desc, rtk_text;

Check Item/Location Staging Table (Confirms today's item/location records submitted by a given user (step 2 check).)

SQL
select *
from RMS.NEX_SVC_ITEM_LOC
where created_by = 'sobalvk' 
and trunc(created_date) = trunc(sysdate) order by created_date desc;

Check if Item Is Already in the Item/Supplier/Country Staging Table

SQL
select *
from rms.svc_item_supp_country_dim
where item in ('14508509');

2. Item & Hierarchy Lookups

Look Up Item Hierarchy for a New Add Transaction (Use this when users submit an add transaction — returns the parent, transaction item, hierarchy, color, and size group.)

SQL
SELECT IM.item_grandparent as "PARENT", IM.item_parent as "TRANSACTION", IM.dept, IM.class, IM.subclass, IM.diff_1 as color,
XIM.diff_2 as size_group_id, IM.diff_2 as "SIZE", IM.item_desc_secondary, IM.create_datetime, IM.create_id
FROM RMS.item_master IM, (SELECT item, diff_2 FROM RMS.item_master) XIM
WHERE IM.item_grandparent = XIM.item
and IM.item_GRANDparent in ('16863505')
--and IM.diff_1 in ('403', '651')
ORDER BY IM.dept, IM.class, IM.subclass, IM.diff_1, XIM.diff_2 asc;

Look Up Item by GTIN (Returns the item parent and primary reference item indicator for a GTIN.)

SQL
Select* ---ITEM_PARENT, ITEM, primary_ref_item_ind
from rms.item_master
where item in ('196985578839');

Check Dept / Class / Subclass Relationship

SQL
Select * 
from rms.subclass
where dept = '770';

Look Up SKULIST Detail

SQL
SELECT* 
FROM RMS.skulist_detail
WHERE SKULIST IN ('21240112','21240110','21240111');

Count Total Locations Attached to an Item

SQL
select item, count(loc) 
from rms.item_loc 
where item in ('19437854') 
group by item 
order by item asc;

Range Already-Built Items to a Destination Dept (e.g., 781) Check (Pulls web description, brand, MSRP, VPN, supplier color, and e-comm UDA values for items being ranged into an already-built dept/class/subclass.)

SQL
SELECT DISTINCT im.item_grandparent AS PARENT, im.item_parent AS TRANSACTION, im.dept, xim.item_desc_secondary AS WEB_DESC, xim.brand_name AS BRAND, xim.MFG_REC_RETAIL AS MSRP, iss.VPN AS VPN, iss.SUPP_DIFF_1 AS SUPPLIER_COLOR, uil.UDA_ID AS ECOMM_UDA, uil.UDA_VALUE AS ECOMM_UDA_VALUE 
FROM rms.item_master im JOIN rms.item_supplier iss ON im.item_parent = iss.item 
LEFT JOIN rms.uda_item_lov uil ON im.item_parent = uil.item 
AND uil.UDA_ID IN ('9630', '9631', '9632', '9627') 
JOIN (SELECT item, brand_name, mfg_rec_retail, item_desc_secondary FROM rms.item_master) xim 
ON xim.item = im.item_parent 
WHERE im.item_grandparent IN ('19507468','19507466','19507467') 
AND iss.primary_supp_ind = 'Y' 
ORDER BY im.dept, im.item_grandparent, im.item_parent ASC, uil.uda_value DESC;

3. Supplier, Vendor & Costing Checks

Show Primary Supplier at the Location Level (Manual maintenance check — the commented lines show how to swap in a SKULIST or LOC_LIST instead of a single item/location.)

SQL
select item, loc, primary_supp, status 
from rms.item_loc 
where item in ('11982497') 
--where item in (select item from rms.skulist_detail where skulist = '20380870') 
--and loc in (select location from rms.loc_list_detail where loc_list = '1395003');
and loc in ('505');

Confirm a Supplier Is Attached to an Item

SQL
select item, supplier, vpn
from rms.item_supplier
where item in ('19507468','19507466','19507467')
and supplier in ('187949904');

Identify Items Missing the Correct Primary Supplier (Cross-checks a SKULIST against a LOC_LIST to find item/location combinations where the primary supplier doesn't match what's expected.)

SQL
select sd.skulist, sd.item, lld.loc_list, il.loc, il.primary_supp, il.store_ord_mult, il.source_method, il.source_wh, il.last_update_datetime, il.last_update_id
from RMS.SKULIST_DETAIL sd, RMS.LOC_LIST_DETAIL lld, rms.item_loc il
where sd.item = il.item
and il.loc = LLD.LOCATION
and sd.skulist in ('20740102')
and lld.loc_list in ('109220')
and il.primary_supp <>'91796839'
---and il.store_ord_mult <> 'I'
order by sd.skulist, lld.location asc;

Confirm a Supplier Exists in RMS

SQL
Select *
from rms.sups
where supplier = '107257560';

Check Default Unit of Purchase (UOP)

SQL
Select item, supplier, default_uop, create_datetime, last_update_id, last_update_datetime
from rms.item_supp_country 
where item in ('13284518')
and supplier in ('9207775','8086');

Look Up Primary Supplier — Single Item, Item List, or Loc List (General-purpose template. Swap in the commented lines to search by SKULIST or LOC_LIST instead of a single item/location.)

SQL
select item, loc, primary_supp, status 
from rms.item_loc 
where item in ('') 
--where item in (select item from rms.skulist_detail where skulist = '') 
--and loc in (select location from rms.loc_list_detail where loc_list = '486217') 
and loc in ('746') 
;

Check Item/Supplier/Country Record

SQL
select* 
from rms.item_supp_country 
where item in ('7465374');

Look Up Vendor & Transaction Details by GTIN

SQL
select distinct TRUNC(IM.CREATE_DATETIME) CREATE_DATE, im.dept DEPT, s.supplier VENDOR, s.sup_name VENDOR_NAME, im.item_grandparent PARENT, im.ITEM_DESC_SECONDARY PARENT_NAME, iss.vpn VPN, im.item_parent TRANSACTION, IM.ITEM_DESC TRANSACTION_NAME, im.item GTIN, IM.STATUS 
from rms.item_master im, rms.item_supplier iss, rms.sups s 
where im.item_parent = iss.item 
and iss.supplier = s.supplier 
and im.item in ('847280052899')
and iss.primary_supp_ind = 'Y'
order by im.item_grandparent, im.item_parent asc;

Check Item/Supplier/Country Dimension Record (Same as the staging check above (G5), but against the live table rather than the staging table.)

SQL
select *
from rms.item_supp_country_dim
where item in ('14508609');

Item Re-Class Process Query Index

Note: These queries are utilized during the item re-class sequence. They are centrally managed within the Item Re-class working directory.

1. Overview (Section 2.2.1.8)

Find UDAs attached to a Skulist (Mandatory UDAs Step 2)

SQL
SELECT DISTINCT sd.item, ul.uda_id, ul.uda_value
FROM rms.uda_item_lov ul, rms.skulist_detail sd
WHERE ul.item = sd.item
  AND sd.skulist = '';

2. Forecasted Items on Re-Classes (Section 2.2.2)

Check if Departments are forecastable

SQL
SELECT DISTINCT dept, forecast_ind
FROM rms.item_master
WHERE forecast_ind = 'Y'
  AND Dept IN ('');

Determine if an item is on forecasting (Must match the destination Dept.)

SQL
SELECT DISTINCT ril.dept, ril.item, item_desc
FROM rms.repl_item_loc ril, rms.item_master im
WHERE ril.item = im.item
  AND ril.item IN ('')
  AND forecast_ind = 'Y'
  AND (deactivate_date IS NULL OR deactivate_date > sysdate);

Determine if an item list is on forecasting (The forecastability of the item must match the destination Dept.)

SQL
SELECT sd.skulist, im.ITEM_PARENT, im.item_grandparent, im.DEPT, im.class, im.subclass, im.item_desc, im.forecast_ind
FROM rms.skulist_detail sd, rms.item_master im
WHERE sd.item = im.item_parent 
  AND sd.skulist IN ('')
  AND im.forecast_ind = 'Y';

Identify domains attached to forecastable departments

SQL
SELECT *
FROM rms.domain_dept
WHERE dept IN ();

3. Components of Pack Items on Order & Error Resolution (Section 2.2.3 & 2.4)

Identifying component items on order (POs on this list will need to be closed)

SQL
SELECT *
FROM rms.ordhead oh, rms.ordsku os, rms.packitem p
WHERE oh.order_no = os.order_no
  AND oh.status = 'A'
  AND p.pack_no = os.item
  AND EXISTS (
      SELECT 'x'
      FROM rms.packitem p, rms.item_master im
      WHERE p.pack_no = os.item
        AND (im.item = '' OR im.item_parent = '' OR im.item_grandparent = '')
        AND p.item = im.item
  );

4. Identifying Open Orders for Item Profiles & Item Lists (Section 2.3.1 & 2.5.1)

Find items on an open order that is partially received

SQL
SELECT oh.order_no, oh.order_type, oh.status, ol.item, oh.written_date, oh.NOT_AFTER_DATE, ol.location, ol.qty_ordered, ol.qty_received, ol.last_received
FROM rms.ordloc ol, rms.ordhead oh
WHERE oh.order_no = ol.order_no
  AND ol.item IN (SELECT item_parent FROM rms.item_master WHERE item_grandparent IN ('12385927'))
  AND oh.status <> 'C'
  AND ol.qty_received IS NOT NULL
  AND ol.qty_ordered > ol.qty_received
ORDER BY order_no DESC;

Check deals tables (Check BOTH queries below using PO numbers from step Q7)

SQL Profile 1
SELECT *
FROM rms.deal_calc_queue
WHERE order_no IN ('');
SQL Profile 2
SELECT *
FROM rms.deal_order_temp
WHERE order_no IN ('')
ORDER BY order_no ASC;

Check for open appointments on POs (Appointments must be closed before closing a PO)

SQL
SELECT DISTINCT ad.doc, ah.loc, ah.appt rms_appt_nbr, ah.status, 
                DECODE(ah.status, 'SC', 'Scheduled',
                                  'AR', 'Arrived',
                                  'AC', 'Closed',
                                  'UNKNOWN') AS appt_status 
FROM rms.appt_head ah, rms.appt_detail ad 
WHERE ad.appt = ah.appt 
  AND ad.doc IN ('');

5. Resolving Re-Class Errors (Section 2.4)

Find a recent rejection (By user name or item; only tracks previous batch errors)

SQL
SELECT *
FROM rms.mc_rejections
WHERE user_id = 'NEXADID'; -- (By user ID)
---and item in (''); -- (By item, if using only item, replace 'and' with 'where')

Find a historical rejection (By User, date, or item)

SQL
SELECT *
FROM rms.mc_rejections_archive
WHERE change_type = 'M'; -- (By re-class change type)
  --and TRANS_DATE = 'DD-MMM-YY'; -- (By date re-class was keyed)
  AND user_id = 'NEXADID'; -- (By User ID)
  ---and item in (''); -- (By item)

Validate if Item List / SKULIST re-classed

SQL
SELECT sd.skulist, im.ITEM_PARENT, im.item_grandparent, im.DEPT, im.class, im.subclass, im.item_desc
FROM rms.skulist_detail sd, rms.item_master im
WHERE sd.item = im.item_parent 
  AND sd.skulist IN ('');

Validate if a single item re-classed

SQL
SELECT item_parent, item_desc, dept, class, subclass
FROM rms.item_master
WHERE item IN ('');

6. Lawson Department Re-Classes (Section 4.1.2)

Check for a department move by Item List (Can catch mis-keyed items from an outside department)

SQL
SELECT DISTINCT dept
FROM rms.skulist_detail sd, rms.item_master im
WHERE sd.item = im.item_parent 
  AND sd.skulist = '';

Check for financial moves by Departments

SQL
SELECT g.group_no, g.group_name, d.dept, d.dept_name, d.group_no
FROM rms.groups g, rms.deps d
WHERE g.group_no = d.group_no 
  AND d.dept IN ();

7. Nightly Batch Communication to RAVE (Section 6.1)

Check re-classes scheduled to run in the nightly batch

SQL
SELECT *
FROM rms.reclass_head
ORDER BY reclass_no ASC;

Identify re-class effective dates / submission verification

SQL
SELECT *
FROM rms.reclass_head
WHERE reclass_no IN ();

Compare item hierarchies in v16 and v10 (Must be executed the following week)

SQL
SELECT DISTINCT im.item_parent, ri.item, im.dept, im.class, im.subclass, 
                COALESCE(vim.item_parent, vim.item) AS Highest_level_RIN, 
                vim.item, vim.dept, vim.class, vim.subclass
FROM rms.nex_reclass_item ri, rms.item_master im, rms_v10.item_master vim
WHERE ri.item = im.item
  AND ri.item = vim.item
  AND im.item = vim.item
  AND reclass_date >= 'DD-MMM-YY'
  AND reclass_date <= 'DD-MMM-YY'
  AND im.item_level = '2';

8. Additional Queries

Item count per SKULIST (Target range is between 100-150 items for optimal performance)

SQL
SELECT skulist, COUNT(item)
FROM rms.skulist_detail
WHERE skulist IN ('')
GROUP BY skulist;

Adding a Size Code (ID)

*Note: Before building a new size code or Differentiator Group - please make sure that size code is not already built and, that if a team is requesting a new Diff Group that there isn't already a Diff group that contains some or a majority of the sizes requested.

Download Differentiators Template

In RMS, navigate through the menu paths to download the template foundation metadata layer:

  1. Go to: TasksFoundation DataData LoadingDownload

  2. ORACLE Merchandising
    🔔 99+
    < Data Loading
    Search for a task
    Download
    Upload
         Review Status
         Download Blank Template


  3. Once in the Download Data tab For the Template Type select Items and for Template select Differentiators

  4. ORACLE Merchandising
    Download Data ×

  5. Click Download Open with Microsoft Excel Click OK
  6. Once Excel Spreadsheet opens, go to the Diff_IDs tab
  7. Clear Diff_IDs tab out data below Headers and do as follows:
    For Action: Select CREATE from the drop-down list.
    For Diff ID: Enter the size code requested (e.g., 30").
    For Diff Description: Enter the size description (e.g., 30").
  8. Notes: Diff IDs CANNOT have spaces or underscores. If a space is needed create a USD Incident to RAVE and they will insert it on the backend.
    Diff IDs cannot be longer than 10 characters - INCLUDING spaces.

    Repeat previous steps as needed if creating more than one size

  9. Save as an .ods file
    • Naming Protocol: Sizes_Dates
    • Drive Registry Path: G:\Code_M\Code_MS\Data Steward Team\Jess\Diff\Sizes Built
  10. Go to: TasksFoundation DataData LoadingUpload
  11. ORACLE Merchandising
    🔔 99+
    < Data Loading
    Search for a task
    Download
    Upload
         Review Status
         Download Blank Template

    Once in the Upload Data tab input the following:

  12. For the Template Type select Items
  13. For Template select Differentiators
  14. For Process Description it can be left the same or edited
  15. For Source File click Browse and find .ods file that was saved

  16. ORACLE Merchandising
    Upload Data ×
    Size Uni Test 2 101218.ods


  17. Upload File
  18. To determine if induction was successful:
    If you receive a notification, there was an error. Check Issues and troubleshoot
    Run below query with LOWERCASED RMSv16 User ID:
  19. SQL
    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 = 'parkerje' 
    ORDER BY action_date DESC;
  20. Run queries included in index so add new sizes to Quick Reference Guide (QRG) listing on the SharePoint HUB and let Senior Tech or Data Steward Team Manager know new sizes were created

Creating a new Differentiator Group

  1. In RMS16 go to Tasks > Foundation Data > Items > Differentiators > Diff Groups
  2. Click Actions > Add or Click the green plus sign
  3. Note:Click Query by Example to find the next sequential Diff Group number


    Merchandising
    Upload Items from File ×
    Differentiator Groups ×
    Diff Groups
    Actions View
    ✏️
    📊 🔄
    📄 Detach 🌐
    end;
    Group Group Description Type Description Region Department
    125S BELT SIZES Size
    127S MEN'S SHIRTS Size
    128S 5/6 - 9/10 Size
    129S SHORT SLV SHIRT Size
    131S INFANTS Size
    Group Detail
    Actions View
    📊 🔄
    📄 Detach
    Sequence Size Description
    1 S/M S/M
    2 M/L M/L


    Finding/Adding a Diff Group Number

    For Group input the next sequential number (you can filter the Group category by descending to see the next number)

  4. 11. If adding a Size, S must be put after the number For Group Description input desired group name
  5. Group Description must not exceed 40 characters - INCLUDING SPACES
  6. Click OK or OK and Add Another

  7. Add Group
    *Group
    *Group Description
    *Type
    Size
    Region
    Department

  8. Save and Close

  9. Adding sizes or colors to a new Diff Group

  10. In the "Diff Groups" section click on Group wanting to edit (so it's highlighted)

  11. Diff Groups
    Actions View
    ✏️
    📊 🔄
    📄 Detach 🌐
    Group Group Description Type Description Region Department
    TODDLER MI 2T,3T,4T,S,M,L,XL Size
    GIFTCRD WEB GIFT CARD DENOMINATIONS Size
    COLOR Color Color
    321S SuperFeet Insoles Size
    320S UNIFORMS - FOOTWEAR Size
    Group Detail
    Actions View
    📊 🔄
    📄 Detach
    Sequence Size Description
    SF.B B: 4.5-6 US Women's/2.5-4 US Juniors
    SF.C C: 6.5-8 US Women's/5.5-7 US Men's
    SF.D D: 8.5-10 US Women's/7.5-9 US Men's
    SF.E E: 10.5-12 Women's/9.5-11 US Men's
    SF.F F: 12.5+US Women's/11.5-13 US Men's
    SF.G G: 13.5-15 US Men's

  12. In the Group Detail section below click the green plus sign
  13. Enter the first or next Sequence number and a valid RMS Size


  14. Click OK or OK and Add Another
  15. Click Save and Close

  16. Send the following e-mail with the information below:

    Generate Email

  17. ECOMM group will respond back that they have made the updates

  18. Differentiator Batch


    The APPWORX batch for the Diff Groups and Sizes runs every 8 hours: 4AM, 12PM, 8PM. If someone needs a size built AFTER the 12PM batch is ran, you can either - wait until the next day and submit it before 12PM or you can get RAVE to ADHOC the batch.


    To ADHOC the batch submit a USD Ticket to the RAVE team with the following message format:

    Incident Description
    
    Hi Team!
    
    Requesting to have the ORETAIL_INT_MASTER_DATA batch to run because I built the sizes after the 12pm batch.
    
    We created 10 new sizes 
    and added all 10 to the Group 313S

    Queries


    SQL
    ---Full list of Diff Groups and their respective IDs
    SELECT DISTINCT dg.diff_group_id, dg.diff_group_desc, di.diff_id
    FROM rms.diff_ids di, rms.diff_group_head dg, rms.diff_group_detail df
    WHERE df.diff_id = di.diff_id
    AND dg.diff_group_id = df.diff_group_id
    AND dg.diff_group_id <> 'COLOR'
    ORDER BY dg.diff_group_id, dg.diff_group_desc, di.diff_id;
    
    ---To see Diffs created on a specific date (change date as necessary)
    SELECT *
    FROM RMS.DIFF_IDS
    WHERE TRUNC(create_datetime) = '16-OCT-18';
    
    SELECT * 
    FROM RMS.DIFF_IDS 
    WHERE TRUNC(create_datetime) = TRUNC(SYSDATE);

Adding a Supplier via Item Induction

Use this process when adding a new supplier to an existing item. The Item Induction Form is used — only the Item Tab and (optionally) the Location Tab need to be filled out.

NOTE: If locations are ALREADY attached to items, a Manual Maintenance template will need to be filled out with the Action - Update Primary Supplier and enter the Parent Item [An Item List is required when there are 5 or more items going to the same supplier], Location List, and Supplier. Buying teams should submit both of these templates on the same e-mail.

Item Tab — Required Columns

ColumnField / Notes
A — ActionSelect Add Item Supplier
H — Parent ItemRequired
I — Transaction ItemRequired
V — VPNPopulate per Web/DST/Vendor requirements for BOPIP, Drop Ship, etc. If adding VPN: copy transaction RIN to parent column on a secondary line; delete from Transaction Item column.
BE — Supplier SiteRequired
BG — Primary Supplier IndChange to No if the new supplier is not the Primary
BN — Unit CostRequired
BR–BU — Inner Size, Case Size, Ti, HiRequired
DK — BuyerRequired
Action Status Item Type Sellable Parent Item Transaction Item VPN Supplier Site Supplier Site Name Primary Supplier Ind Unit Cost Default UOP Inner Size Case Size Ti Hi Round Level Buyer
Add Item Supplier Approved Regular Item Yes 14910832 894000C599080 8086 Yes 3.91 CS 8 8 1 1 Case 346
Add Item Supplier Approved Regular Item Yes 14910842 894000C599080 8086 Yes 3.91 CS 8 8 1 1 Case 346

Location Tab (if ranging to new locations)

ColumnField / Notes
A — ActionDefaults to Create Location
C — ItemParent-level RIN
D–E — Location ListUse if ranging by Location List
G–I — LocationUse if ranging by single location

Save file as ODS and upload to V16

Updating Primary Supplier — Item List

An Item List is required when 5 or more items are going to the same supplier. Buying teams should submit both the Item Induction template and the Manual Maintenance template in the same email.

Required columns on the Manual Maintenance template:

Action Parent Item Transaction Item Item List Number (If More than 5 Items) GTIN Item Updated GTIN Desc (ie, add _pc, add _pu) Supplier Site # Location
Update Primary Supplier 22285450 118547120 609219
Update Primary Supplier 22285450 118547120 68105
Update Primary Supplier 22285450 118547120 2325011
Update Primary Supplier 22285450 118547120 2325012
Update Primary Supplier 22285450 118547120 4180048
Update Primary Supplier 22285450 118547120 9870
Update Primary Supplier 22285450 118547120 781

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.


  3. Item List Search ×
    ▲ Search
    Match
    Saved Search
    📅
    🔍
    ▲ Results
    | | |
    Item List Description Type Total Items Created Date Created By
    22285450 Air Wick Oil 3 Items Dynamic 3 4/24/26 boydz


  4. Click the Green (+). Select the appropriate location type → 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.

Updating Primary Supplier — Single Item

Required columns on the Manual Maintenance template:

ACTION ITEM INFORMATION UPDATING PRIMARY SUPPLIER
Action Parent Item Transaction Item Item List Number (If More than 5 Items) Supplier Site # Location
Update Primary Supplier 14910832 14910842 118547120 8086

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.


  2. Results
    Actions ▼ View ▼ | 📄 📖 ✏️ 👓 | 🔍 📊 | ◪ Detach ⇄ Wrap
    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


  3. Click More Actions → Locations.


  4. Parent "14910832 | Orchard Valley Harvest Trail Mix Chocolate Raisin 8oz

    Regular Item | Approved
    ▲ Descriptions 🌐
    Oracle Retail Item Number
    ▲ Usage and Units


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


  6. Actions ▼ View ▼ | ✏️ | 📊 📅 | ◪ Detach
    Location Type Location Name Status Average Cost Unit Cost Unit Retail Currency
    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


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

NEX Gift Cards — Non-Merchandise

NEX Gift Cards follow a distinct process from 3rd Party Gift Cards. These are created in both RMS and XAdmin (unlike TPGC which is RMS + MNT only).

  1. Create the NEX Gift Card item in RMS as Non-Merchandise.
  2. Create the item in XAdmin following the XAdmin Gift Card setup steps.
  3. Complete the .mnt file for the NEX Gift Card type using the MNT Creator. Reference the NEX Gift Card Matrix in the Non-Merch SOP (Section 9.3.1).
  4. Upload and Deploy via XAdmin.
💡
See the NEX Gift Card and Third Party Gift Card Matrix (Non-Merch SOP Section 9.3.1) to confirm which matrix row applies to your card type before beginning.

Non-Merchandise — Fee Items

Non-merchandise items with an associated fee are processed through both RMS and XAdmin. The .mnt file is the mechanism used to configure these items in XStore.

A .mnt file is a configuration file used by XStore to define non-merchandise item behavior. MNT files are created using the MNT Creator file, then uploaded and deployed via XAdmin.

Step 1 — Create Item in RMS as Non-Merchandise

  1. Build the item in RMS following standard DST non-merchandise item procedures.
  2. Ensure the item is properly classified under the correct non-merchandise department and class.

Step 2 — Create Item in XAdmin & Build MNT File

  1. Open the MNT Creator file for the appropriate fee type.
  2. Fill out the required tabs with the correct data. Reference the XStore Warranty SOP (Pages 19–29) located at:
    📁G:\Code_M\Code_MS\Data Steward Team\Xstore\MNT Files
  3. Once MNT files are created, move them from your U Drive to the MNT Files folder.
  4. Upload into XAdmin and Deploy — instructions are in the XStore Warranty SOP.

Editing an Existing Fee in XAdmin

Navigate to the fee item within XAdmin and apply the required changes. Re-deploy after editing per standard XAdmin deploy procedures.

Mass UPC Deletion

IdentifierSOP-D.02.0.0
AuthorJennifer Adamson
ApprovalJeremy Liunas — Director, Merchandise Planning & Analysis
DistributionData Steward Team

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 procedure is for the Monthly AGC/PRG 832 UPC/EAN Mass Deletes. This process has been set up with the AGC (American Greeting Cards) vendor, as these departments are on Scan Base Trading — an initiative where NEXCOM does not own any inventory. AGC manages the inventory and NEXCOM receives the sales.

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

At this time, there is still a need to create the store in both RMS and Richter. When completely off of Richter, this process needs to be re-evaluated.
  1. Download or open the Item Induction Template from the HUB. The most current template may be downloaded from:
    Item Induction Template
    https://intranet.nexad.nexweb.us/M/MS/Pages/Templates.aspx
  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.

  6. 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

  7. Validate front-loading UPCs did not drop off.
  8. If you have a Security Warning Banner stating macros have been disabled, select the Enable Content button.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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
  14. 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.
  15. 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 https://rms.nexweb.us/Rms/faces/RmsHome 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:

  4. Source and Destination
    AGC-PRG Deletes_06May19 #1.ods

  5. The file will process in the background. You'll receive a notification under the Bell Icon when the file has finished processing.
  6. Select the Bell Icon; the Notifications box will open. Select the blue link, and the Data Loading Status screen will open.
  7. 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.
  8. 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.
  9. 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.
  10. For additional Delete Files, repeat the upload steps above until all Delete Files have been processed.
  11. 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):
  12. SQL — Validate CFAS Flag (RMSv16)
    SELECT *
    FROM RMS.ITEM_MASTER_CFA_EXT
    WHERE ITEM IN ('601350155138',
    '601350155145',
    '601350155152',
    '601350155169',
    '747941643698',
    '747941643704',
    '747941643711',
    '747941621757');
  13. The results you are looking for are the VARCHAR2_2 & VARCHAR2_3 fields populated with 'Y' and the Buyer #.


  14. 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

  15. 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.
  16. On the bottom right, select More Actions and scroll down to Other Attributes.
  17. Select Item Master CFAS — this opens the Item Master CFAS Screen. You should see the Delete Flag box checked.
  18. From here, the process sends the delete file to RMSv10 and places the UPCs into Delete Pending status there.
  19. 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.
  20. To validate UPCs have been deleted, run the following query in RMSv10 (SQL Developer or TOAD) — no records should be returned:
  21. 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');
  22. 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.
  23. 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.
  24. To validate UPCs have been deleted, run the same query above in RMSv16 (SQL Developer or TOAD) — no records should be returned.
  25. If records are returned, run the following queries in RMSv16:

  26. 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
If UPCs are in this field, create an Incident for RAVE requesting that they clear the field so the UPCs may be deleted in the Daily Purge job.

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.

Corporate Delete Process

We have identified the most effective way to process corporate deletes in RMS v16 so the information will translate into reports in our IKB and help eliminate holes on the shelf and lost sales.

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.
  2. Or:

  3. 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).

  4. 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."
  2. ORACLE Merchandising
    🔔
    Tasks
    Search for a task
    Foundation Data ˃
    Items ˃
    Cost ˃
    Price ˃
    Orders ˃
  3. Choose "Download Items from RMS."
  4. 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
  5. Enter the Item List # and click Search. Item details will appear at the bottom of the screen.
  6. Click the Download button.
  7. ORACLE Merchandising 👤 grayr ▾
    Download Items from RMS
    Search
    Item
    🔍
    Item Description
    Department
    Class
    Saved Search
    Default
    Subclass
    VPN
    Item List
    Supplier Site
    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
  8. 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.

  5. 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

  6. 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

  7. 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

  8. 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

  9. 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

Item Reclassification

DocumentItem Re-class SOP
AuthorData Steward Team
ScopeMandatory — all DST members

Purpose

This Standard Operating Procedure (SOP) describes the process for documenting steps needed to complete RMS item re-classes.

Scope

This SOP is a mandatory document and shall be implemented by all DST members when creating or editing item re-classes for the buying groups.

Training

The DST is responsible for ensuring that team members who follow this procedure understand the SOP's objectives and other inter-related activities. Training for the buying teams is to be held quarterly for reviewing the process that the buying team is to take for submitting item reclassifications correctly. Upon approval this document MUST be distributed to all necessary team members.

Definitions

TermDefinition
2-Level ItemAn item built with a RIN and Reference number; these are built at Trans Level 1.
3-Level ItemAn item built with a Grandparent RIN, Transaction RIN, and Reference number. All items are 3-level in v16, except Packs.
Component ItemAn item inside of a pack, such as an individual pack of cigarettes or an individual bag of jerky.
Deals TablesTables that will cause re-classes to fail when POs are on them.
ForecastingModule within RMS in which sales are estimated in the future.
Pack ItemThe container that holds other items (e.g., a carton of cigarettes, or a display/shipper with multiple items). These are the ONLY 2-level items in v16, and will not have a Parent Item.
Parent ItemThe highest item in v16, formerly known as the Grandparent in v10. All re-classes are done at this level in v16.
QueryThe script ran in SQL or Toad to pull information.
ReportThe results from the Query or RDW/QS — this is your data.
SkulistAnother word for Item List used in SQL — a group of items compiled on a single list.
Transaction ItemThe level 2 item; all orders are done at this level. Currently known as the Child item in 3-level items, or RIN in 2-level items. This is the level the item is ordered and sold at.
UDAUser Defined Attributes.

Precautions

It is essential that the buying group understand they need to communicate PO cancellations with the planner so that replenishment is not impacted. If POs need to be closed (such as for a Deals Table or a component of a Pack item on POs), we will avoid doing re-classes over the weekend or holidays. This ensures staff are in the office to address any issues that may arise and to reinstate the POs once the re-classes have completed.

Responsibility

DST is responsible for updating and maintaining these procedures.

Equipment / Systems

  • Item Re-class form submitted from buying group
  • RMSv16 & RMSv10
  • TOAD / SQL
  • DST Role in v16 & v10

Re-class Definition

  1. Within RMS, movement of an approved item from one department/class/subclass to another department/class/subclass.

Re-class Form Submission to DST Inbox

Overview

  1. All item re-class requests will be submitted to the DST Inbox by the Buying Team with the subject of FINANCIAL RECLASS or RECLASS [1,2,3,4,5, etc.] based on the type of re-class being submitted. Non-Financial re-classes will be processed on a monthly basis during the 1st full week of the month, and Financial re-classes will be processed twice a year directly after inventories have been completed (February and August).
  2. During the approved re-class cycles the DST Inbox will be checked several times daily, with received emails being moved to the received folder within the inbox. Please remember to keep them as unread until you are working on them. Re-classes will be assigned accordingly based on workload by the Manager during the open re-class periods. Upon opening the email, be sure the re-class form is filled out completely and correctly. Template can be accessed on the HUB under Code M, Support, ORUP, Templates.
  3. There is a soft cap to the amount of items that can be processed each night at 25k items. This cap incorporates all items exploded out. Each day, let RAVE/RIB know the amount of items that are getting processed so they can adjust to prevent batches from running long.

Example of Template:

Item # Item List # RC# Current Dept Current Class Current Subclass Item Count New Dept New Class New Subclass # New Dept Forecastable? Y/N Required UDAs Attached? Y/N Lawson/Financial Move? Y/N Pack or Component Items Included? Y/N
  1. If there are more than five items going to the same department/class/subclass, an item list MUST be created by the buying groups. All items in RMS16 must be handled at the Parent Level, formerly known as the Grandparent level in RMSv10. Item lists created in v16 will not flow to v10, so it is necessary for the buying team to create a separate item list for each system.
  2. Re-classes that move outside their Lawson (financial) group must be approved by the Vice President of Merchandising Support or the Director of Merchandise Planning and Analysis.
  3. In the event that orders hit the deals tables, DST will run an open order report and send any open orders to the buying group to close (see SQL Query Reference). Any orders that may need to be closed must be done by 1pm EST in v16 in order for the changes to flow to v10 correctly. The items cannot be removed from the order; the entire order must be in closed status.
  4. All MANDATORY UDA's for the Dept/Class/Subclass that the item is going to must be added to the item prior to the re-class. Note: most Mandatory UDA's were removed for RMS16.
    Use the Mandatory UDA queries in the SQL Query Reference to (1) find Mandatory UDAs by Department, then (2) find the UDAs attached to a Skulist.

Forecasted Items on Re-classes

  1. To determine if items are forecastable, run the forecastable query in the SQL Query Reference to check if a department is forecastable, if an item is on forecasting, or if an item list is on forecasting.
  2. If the item needs to remain forecastable, the new Dept/Class/Subclass that the item is going to must be set up as forecastable by the Forecasting Team. If the destination department needs to be set up as forecastable, it will need to be added to a domain for the financial group.
  3. If the item is currently forecastable, but does not need to be forecasted, work with the Forecasting Team to have the replenishment method changed to min/max. Then you'll be able to re-class the item without making the new Dept/Class/Subclass forecastable.
  4. If you do not check to see whether your item is forecastable you may get an error, but the error on the Mass Change Item Rejection Report will NOT show you the item is forecastable. Instead the item will not re-class and you will receive an unrelated error.

Merchandise Hierarchy Change Re-class Process

  1. Always confirm whether or not an item is going into a Dept/Class/Subclass that has recently had a Hierarchy Change.
    • To find if the new Dept/Class/Subclass has recently had a Hierarchy change, search the DST Inbox for an email tagged "FYI . . . Please Read" and titled "Please Map New and Edit Dept, Class, and Subclasses."
    • These will be kept in the Inbox for 48 hours, after which you will need to look in the Merchandise Hierarchy Folder to confirm they are not there.
  2. If the item is going to a Dept/Class/Subclass with a Name Change, then you may re-class as soon as the name change is visible in RMS. These do not impact downstream systems.
  3. If the item is going to a newly created Dept/Class/Subclass, then you must WAIT until confirmation is received from the downstream systems. Not waiting could result in incorrect sales.
  4. If the item is going to a re-activated Dept/Class/Subclass (one that had been N/A, but was re-opened with a new name), then you must WAIT until confirmation is received from the downstream system's POCs, found in the "Please Map New and Edit Dept, Class, and Subclasses" emails.

Keying a Re-class in RMS v16

  1. From Tasks, select Foundation Data > Items > Reclassification.
    MenuNavigation Path
    TasksFoundation Data → Items → Reclassification
  2. Selecting Reclassifications will bring up the Reclassifications Screen. From this screen you will create re-classes for single items and item lists, as well as delete any re-class that needs to be deleted.
    Screen ElementFunction
    Reclassifications GridLists all active re-classes
    Green "+" (Actions > Add)Create a new re-class
    Red "X" (Actions > Delete)Delete an existing re-class
  3. In the Reclassifications Box select the Green "+" or go to Actions > Add. All RINs must be at the Parent level; this is the Level 1 item.
    ActionResult
    Green "+" / Actions > AddOpens the Add Reclassification screen
  4. The Add Reclassification screen will open up.
    FieldDescription
    DescriptionFree-text field identifying the re-class
    Reclass DateThe date the re-class becomes effective
  5. In the Reclassification Description, enter the last name of the submitter. If they have submitted more than one re-class you can enter a number after the name, i.e., DOE - #1 for the first and DOE #2 for the second, etc.
  6. The Reclass Date is the next day. If you do not want the re-class to be effective the next day, pick any other later date. The system will hold the re-class until the day specified.
  7. In the "Select Item to Reclassify" section, select "Item" for a single item re-class and "Item List" for an item list re-class. Then enter the item or item list in the Item/Item List box. You can also use the LOV marker to search for items.
    FieldOptions / Notes
    Select Item to Reclassify"Item" (single item) or "Item List" (item list)
    Item / Item List boxEnter item/item list number, or search using the LOV marker
    NOTE: Items on your v16 item list will not match your items on the v10 item list for 2-level items.
  8. In the Select New Hierarchy section, enter the department, class, and subclass the item is GOING TO.
    FieldEnter
    DepartmentNew department the item is going to
    ClassNew class the item is going to
    SubclassNew subclass the item is going to
  9. Click OK once all the data has been entered. If you have additional re-classes to input, select "Ok and Add Another" and repeat steps 5–8, then hit "Ok".
  10. You will get a message that the item will be reclassified the night before the reclassification effective date. The re-class job runs in Phase 4 of the batches (this is the after-batch).
    MessageMeaning
    "Item will be reclassified the night before the reclassification effective date."Confirms the re-class was saved and will run in Phase 4 of the nightly batch (after-batch)
  11. Reply to the original email with the canned email once successful validation has been completed.

Resolving Re-class Errors

  1. To see the reason a re-class has failed, use the "recent rejection" and "past rejection" queries in the SQL Query Reference. The text editor will give you the rejection reason. You can determine how to correct the problem from this reason.
  2. To review whether a re-class has gone through, use the "Validate if Item List/SKULIST re-classed" and "Validate if single item re-classed" queries in the SQL Query Reference. Enter your item or item list number and run the script(s). Export to Excel and then filter the data. Select one item list at a time from the filter drop down. You may select multiple item lists at a time if they are all going to the same dept, class, and subclass. You should easily see if the items were all re-classed. If the item lists were HUGE, you could just check each drop down, because if there is more than one value for dept, class, or subclass for an individual item list, then you know there is an item that is not re-classed.

    Non-filtered results from above script — you can see which items were successfully re-classed:

    SKULISTITEMDEPTCLASSSUBCLASS
    18737610368897380008000
    18737625611697380008000
    187376553252697310013

    Filtered results from above script — you can now see these items DID NOT get re-classed and should be done again:

    SKULISTITEMDEPTCLASSSUBCLASS
    18737610368897380008000
    18737625611697380008000

Viewing / Editing Current Re-classes

  1. From Retek Enterprise Home, click on Tasks > Foundation Data > Items > Reclassification.
    MenuNavigation Path
    TasksFoundation Data → Items → Reclassification
  2. The Re-class view shows all active re-classes that will be effective in future batches.
    • Please note: this will not show any re-classes that have already processed. This is the same screen used for creating re-classes. You can see the details of the selected re-class in the Details section.
    Screen ElementShows
    Reclassifications GridAll active, future-effective re-classes
    Details SectionFull detail of the currently selected re-class
  3. If a re-class needs to be deleted for any reason, highlight it and click delete (the red "X" or Action > Delete). You will receive a warning confirming you wish to delete the re-class. Select "Yes".
    PromptAction
    Delete confirmation warningSelect "Yes" to confirm
  4. Once you have selected "Yes" the re-class will delete from the Reclassification list. Select "Save and Close" to save the delete.
    ButtonAction
    Save and CloseCommits the deletion
  5. As in v10, you won't be able to edit the existing re-class, but viewing the details will allow you to see whether you need to delete a current re-class and start again.
    NOTE: If a reclass does not process during the nightly batch, and there are no partially received orders, it MUST be deleted and reprocessed. Changing the date in the backend will not retrigger it to reprocess.

Keying a Re-class for a Single Item in RMSv10

  1. From Retek Enterprise, double-click on the Items folder. From Items, double-click and open the Reclassification Folder.
    FolderNavigation Path
    ItemsItems → Reclassification Folder
  2. Double-click on the Reclassification Folder and then select "reclassify one item".
    Folder OptionResult
    Reclassify one itemOpens the Reclassification Item screen
  3. In the Reclassification Item screen, enter the RIN of the item that is being reclassified.
  4. The reclassification number is automatically populated. Record that number on the re-class form.
  5. In the Reclassification Description, enter the last name of the buyer, then the department. If they have submitted more than one re-class you can enter a number after the name, i.e., DOE - Dept 123 #1 for the first and DOE #2 for the second, etc.
  6. The effective date is the next day. If you do not want the re-class to be effective the next day, pick any other day. The system will hold the re-class until the day specified. Enter the department, class, and subclass the item is GOING TO.
    FieldEnter
    RINThe item's RIN
    Reclassification NumberAuto-populated — record on the re-class form
    DescriptionBuyer last name + department (+ sequence number if multiple)
    Effective DateDefaults to next day; can be set later
    DepartmentNew department the item is going to
    ClassNew class the item is going to
    SubclassNew subclass the item is going to
  7. Click OK once all the data has been entered.
  8. You will get a message that the "Item(s) will be reclassified the night before the reclassification effective date." The re-class job runs in Phase 4 of the batches (this is the after-batch).
    MessageMeaning
    "Item(s) will be reclassified the night before the reclassification effective date."Confirms the re-class was saved and will run in Phase 4 (after-batch)
  9. Reply to the original email stating re-classes have been completed once validation is completed.

Keying a Re-class for an Item List in RMSv10

  1. From Retek Enterprise, double-click on the Items folder and double-click on Item List.
    FolderNavigation Path
    ItemsItems → Item List
  2. Select "Use" from the drop-down selection.
    FieldSelection
    Item List actionUse
  3. Enter the item list number and click OK.
  4. From the top of the screen select Options, Create Mass Item Change, Reclassification.
  5. The re-class form opens, but with Item List instead of Item.
  6. Record the re-class number on the re-class form.
  7. Enter the Buyer Last Name - Dept # - #1,2,3,4,5, etc. in the re-class description. Same format as used for single item re-classes.
  8. Select the effective date. The effective date is the next day. If you do not want the re-class to be effective the next day, pick any other day.
  9. Enter the Dept/Class/Subclass the items are GOING TO.
  10. Click OK.
  11. The item will be re-classed the night before the reclassification effective date.
    MessageMeaning
    Reclassification confirmationConfirms the item list re-class will run the night before the effective date

Identifying Open Orders for Items that Failed to Re-class

  1. If an item fails to re-class it may be due to an open PO on the deals table(s) or a component on a pack on order in RMS.
  2. In Toad/SQL, run the queries in the SQL Query Reference to (1) find item lists (or items) on an open order, (2) check deals tables using PO numbers, (3) check for open appointments on POs, and (4) check if a PO is not closed/re-opened.
  3. Use the open-order query to find the items on the POs, then check those POs against the deals-table and open-appointment queries — these will give you the POs that need to be closed.
  4. Export the results to Excel and save the spreadsheet with proper formatting. Proper formatting is as follows: columns expanded, header in gray, filter added, and all borders added. Columns included should be PO number, Status, and, if desired, item number.
    • If only a few POs, paste a screenshot to the email body and email the buying group to cancel the open POs and to notify DST when they have been canceled. If there are more than a few POs, send as an Excel attachment.
  5. After the buying group notifies DST that the POs have been closed, run the "PO not closed/re-opened" query to verify that the POs have been canceled, and then you can re-class the item(s). Sometimes when an open PO has been closed, the system will still see the PO as open. If this happens, wait a few minutes and try the re-class again — it should go through after waiting.

Components of Pack Items on Order (Items That Failed)

  1. There are times when an item is not on order when you run the open order query above, but the item is a component of a pack in RMS that is on order. This will cause an item to fail because of open orders. To identify these items on order, use the "Identifying component items on order" query in the SQL Query Reference.
  2. When this query comes back it will indicate the POs the pack item is on. The buying group can then cancel the order(s) the pack is on, and the re-class can be completed on the component item(s).

Re-classes Between Lawson Departments

  1. When receiving re-classes that move between Lawson departments, approval by the Vice President of Merchandising Support is needed.
  2. To verify that this is a financial move, use the department-move queries in the SQL Query Reference to find the departments, then confirm they are from different groups.
  3. Be sure to notify the DMM of Planning and Replenishment that you have an intra-department Lawson re-class. POCs are the Director of Merchandise Planning and Analysis and the Director of Merchandise Planning.
  4. Complete the re-class as stated above in Keying a Re-class in RMS v16.
  5. The Merchandise Accounting Manager runs a monthly report for these and will take any necessary action regarding financial moves.

Nightly Batch Communication to RAVE

  1. Each evening before leaving, the last team member to leave will run the nightly batch queries in the SQL Query Reference to (1) check re-classes scheduled to run in the nightly batch, (2) find how many items will process in a night, and (3) find re-class numbers running that night.
  2. Drop the amount of total items being reclassed each night in the Record Counts/Batch Count TEAMS chat.

Price for Prompt

CreatedApril 21, 2026
AuthorJ. Reynolds
SystemsRMS v16, CA Service Desk Manager (ITCSC), Outlook
Next ReviewApril 21, 2027

Price for Prompt marks specific items to prompt the cashier for a price when scanned at the register. Typical candidates are third-party services and custom items. The buying team will indicate in the email body that an item needs price prompt.

Price prompt items must be built with a retail of $0. Due to their nature, they typically have no associated GTINs and will always be built with a system-generated GTIN.

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
  3. 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
  4. 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.
  5. Once ran through the template checker, populate the template
  6. Save as .ods.
  7. 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.
Adding locations is a batch job that runs at the top of every hour. Once attached in v16, locations will flow to v10 within 1–2 hours.

Creating the Incident Ticket

Locations must be fully attached in both v16 and v10 before creating the incident ticket.
  1. Go to CA Service Desk Manager: https://support.nexad.nexweb.us/CAisd/pdmweb.exe
  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.

Quantity Key

Quantity Key updates are made at the item/location level. The Qty Key option on the Location tab is only good for new item/location relationships — for existing item/location relationships, use the steps below.

  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.

  3. Results
    Actions View
    📋 ✏️ 👓
    📊
    📄 Detach ↪️ Wrap
    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

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

  5. Transaction "14806261 | Aroma 4-Cup Rice Cooker White

    Descriptions
    Oracle Retail Item Number
    Cost and Price
    Usage and Units
    Attributes
    Suppliers
    Retail by Zone
    Locations
    Item Up Charges
    List Children
    Simple Pack
    Transformation
    Replenishment
    Substitute Items
    User Defined Attributes
    ↩️ ↪️

  6. Enter the location in the Loc field.

  7. 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

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

  9. 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




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

  11. Transaction "14806261 | Aroma 4-Cup Rice Cooker White
    Apply Updates To
    Store 461 | YOKO NEX DEPOT

    Customer Order Attributes

    Grocery Attributes

    📅
    Prohibited

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

  13. Transaction "14806261 | Aroma 4-Cup Rice Cooker White
    Apply Updates To
    Store 461 | YOKO NEX DEPOT

    Customer Order Attributes

    Grocery Attributes

    📅
    Required

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

Serializing an Item

The team will indicate in the body of an email when to serialize item(s). Once serialized, the UIN Type and UIN Label fields should be visible on the Locations screen. If not, use View → Columns to add them.

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.

Updating Item Induction Template Checker Tables

Scope: Supplier, UDA, Brand, & Size

To update the template checker anytime a new Supplier, UDA, Brand, and/or Size has been created in RMS v16, follow the steps below:


Step 1: Run the Appropriate Query in SQL or Toad


a. UDA Query

SQL
SELECT U1.UDA_ID, U1.UDA_DESC, U2.UDA_VALUE, U2.UDA_VALUE_DESC 
FROM rms.uda u1, rms.UDA_VALUES u2 
WHERE U1.UDA_ID = U2.UDA_ID 
----AND u1.uda_id = 5261 
ORDER BY U1.UDA_ID, U2.UDA_VALUE;

b. Supplier Query

SQL
SELECT supplier, duns_number, supplier_parent, sup_name, sup_status, create_datetime
FROM rms.sups
ORDER BY supplier;

c. Size Query

SQL
SELECT DGD.DIFF_GROUP_ID, DGH.DIFF_GROUP_DESC, DI.DIFF_ID, DGD.CREATE_DATETIME,
       DGD.CREATE_ID, DGD.LAST_UPDATE_DATETIME, DGD.LAST_UPDATE_ID
FROM RMS.DIFF_GROUP_DETAIL dgd, RMS.DIFF_GROUP_HEAD dgh, RMS.DIFF_IDS di
WHERE DI.DIFF_ID = DGD.DIFF_ID
  AND DGD.DIFF_GROUP_ID = DGH.DIFF_GROUP_ID
  --AND DI.DIFF_ID = '0'
  AND DGD.DIFF_GROUP_ID <> 'COLOR'
  AND NOT (DI.DIFF_ID = '0' AND DGD.DIFF_GROUP_ID = '262S') 
  --AND DI.CREATE_DATETIME > sysdate - 30
  --AND DGD.DIFF_GROUP_ID = '232S'
ORDER BY DGD.DIFF_GROUP_ID, DGH.DIFF_GROUP_DESC, DI.DIFF_ID;

d. Brand Query

SQL
SELECT *
FROM rms.brand
ORDER BY BRAND_NAME;

e. Mandatory UDA Query

SQL
SELECT DISTINCT ud.dept, c.class, c.class_name, s.subclass, s.sub_name, ud.uda_id, u.uda_desc,
       ud.required_ind, ud.hierarchy_value, u.CREATE_ID, u.CREATE_DATETIME,
       uv.UDA_VALUE, uv.UDA_VALUE_DESC, uv.CREATE_ID, uv.CREATE_DATETIME 
FROM rms.uda_item_defaults ud, rms.uda u, rms.uda_values uv, rms.class c, rms.subclass s, rms.deps d 
WHERE ud.uda_id = u.uda_id  
  AND U.UDA_ID = uv.UDA_ID 
  AND d.dept = ud.dept 
  AND d.dept = c.dept 
  AND c.class = s.class 
  AND d.dept = s.dept 
  AND ud.class = c.class 
  AND ud.subclass = s.subclass 
  AND ud.required_ind = 'Y';

f. Buyer Number Query

SQL
SELECT D.DEPT, D.DEPT_NAME, D.GROUP_NO, D.BUYER, D.PURCHASE_TYPE 
FROM rms.deps d 
ORDER BY dept;

g. Hierarchy Query

SQL
SELECT dept || '.' || class || '.' || subclass AS key, s.* FROM RMS.SUBCLASS S 
ORDER BY dept, class, subclass;
  1. Once the query has been run, save over the current file located in O:\RB\INDUCTION
    File name must match exactly when being saved and must be formatted as “.xls”
    ie, UDA, SUPPLIERS, Size, Brand2, MandatoryUDAv16, DEPS
  2. Once new file(s) have been saved, files must be cleaned up prior to updating the Template Checker
    Rename the first tab ‘Sheet 1’
    Delete the second tab with the query details (labeled SQL)
  3. Update the Item Induction Template Assistant
  4. To update the Tables in the Item Induction Template Assistant, follow the below steps:

  5. Open current version of the Item Induction Template Assistant Access database
    Either click on the individual table you are wanted to update (Supplier, Brand, UDA, or Size) or click on Update All Tables, if you ran all queries
  6. Close out and re-open; tables should be up to date
  7. Once Template Assistant Updated

  8. Once the checker tables are updated, copy the data for the Brand, UDA (filter to WEB MSTER UDA and delete rows), and Size files into <T:\Code_M\Code_MS\Data Steward Team\ORUP\QRGs\Added to HUB>
  9. Have person in charge update the HUB accordingly! Click

Web Brand Creation / Deletion — RMS v16

Last RevisedMarch 11, 2024
AuthorC. Triba / J. Parker / S. McGregor
SystemsRMS v16, SQL Developer, Outlook
ApproverJennifer Adamson, Manager DST

Brand Name — Vendor-provided brand name attached to items going to the Web.
Brand UDA — UDA created to accompany the Brand Name. A Brand Name cannot exist without a matching UDA.

There cannot be a Brand Name without a coinciding UDA for it

Creating a New Web Brand Name

All new Web Brand Name requests must be approved by a Senior Merchandising Analyst before creation in RMS v16. Senior MAs will not research Essentials Food, Beer, Beverage, Wine, Spirits, or Overseas Brands — DST must research these.
  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


  3. ORACLE Merchandising
    Download Data ×


  4. Click Download. Open the downloaded file in Microsoft Excel


  5. Opening Brands - 12.28.18 10.35 AM.ods

    You have chosen to open:

    What should Firefox do with this file?
    Microsoft Excel (default)


  6. 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
  7. Repeat for each additional brand. Save as .ods file to:
    📁T:\Code_M\Code_MS\Data Steward Team\UDA Creation v16
    Save as "Brand UDA Updates *Date*
  8. In RMS v16:
    Tasks → Foundation Data → Data Loading → Upload
    Set Template Type: Items, Template: Brands, browse to your .ods file → Upload File
  9. If no notification received → brand created successfully. If notification received → error occurred, check issues and troubleshoot using the query below.
SQL
-- 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;

Creating a New Web Brand UDA (Part 2)

Current Web Brand Master UDA IDs: 9639, 10338, 10339, 10340, 10341, 35001, 35002, 85002, 85003, 85004, 85005, 85006, 85007. Max 999 UDA Values per UDA ID.
  1. In RMS v16:
    Tasks → Foundation Data → Data Loading → Download.
    Template Type: Items,
    Template: User Defined Attributes (UDA) → Download → Open in Excel.


  2. ORACLE Merchandising
    Download Data ×


  3. Click Download. Open the downloaded file in Microsoft Excel.


  4. Opening Brands - 12.28.18 10.35 AM.ods

    You have chosen to open:

    What should Firefox do with this file?
    Microsoft Excel (default)


  5. The spreadsheet will have 5 tabs: UDAs, UDA_Translations, UDA_Values, UDA_Value_Translations, UDA_Defaults.
    Clear all data below headers on all tabs.
  6. On the UDA_Values tab:
      • Action (A): Create
      • UDA (B): 85006
      • UDA Value (C): Next available numerical value
      • UDA Value Description: Brand Description from Part 1
  7. Save as .odsto 📁T:\Code_M\Code_MS\Data Steward Team\UDA Creation v16
    Save as "Brand UDA Updates *Date* Upload via Tasks → Data Loading → Upload
    Template Type: Items
    Template: User Defined Attributes (UDA).
  8. If no notification received → brand created successfully. If notification received → error occurred, check issues and troubleshoot using the query below.
  9. SQL
    -- 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;
  10. For PE, click on Data Loading Status notification → View Issues → Correct error as needed
  11. Run queries included in index so the new Web Brand can added to the Quick Reference Guide (QRG) listing on the SharePoint HUB via Senior Supply Chain Tech or Data Steward Team Manager

  12. Reply back to email

    Reply back to users email informing them that the new Web Brand request was processed and created:



    Web Brand Request
    Hi,
    
    New Web Brand request has been created. Please use the below in the Brand Column (AN) on the Item Induction template: 
    
    *Provide newly created Web Brand Name in ALL CAPS*


Deleting a Web Brand Name

  1. In RMS v16:
    Tasks → Foundation Data → Data Loading → Download.
    Template Type: Items
    Template: Brands → Download → Open in Excel.

  2. ORACLE Merchandising
    Download Data ×

  3. On the "Brands" tab:
    Add filter to the Header Row (Row 1)
    Search/Select the Brand Name wanting to delete
    Action (A) - select DELETE from the drop-down
    Filter Action (A) to show the updates only (uncheck Delete from the listing)
    Delete all Update rows
    Remove Filter so that only the Delete Brands are showing
    Repeat previous steps as needed if deleting more than one Brand Name
    Save as an .ods file
  4. Save as .ods file to:
    📁T:\Code_M\Code_MS\Data Steward Team\UDA Creation v16
    *Save as Brand Deletes (todays date)
  5. In RMS v16:
    Tasks → Foundation Data → Data Loading → Upload
    Set
    Template Type: Items
    Template: Brands
    browse to your .ods file → Upload File
  6. If no notification received → brand created successfully. If notification received → error occurred, check issues and troubleshoot using the query below.
  7. SQL
    -- 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;
  8. Correct errors as needed


Deleting UDAs [ID] and/or UDA Values

  1. In RMS v16:
    Tasks → Foundation Data → Data Loading → Download.
    Template Type: Items,
    Template: User Defined Attributes (UDA) → Download → Open in Excel.
  2. Go to tab you are deleting from (UDAs/UDA Values):
  3. Add filter to the Header Row (Row 1)
  4. Search/Select the UDA (ID) and/or UDA Value wanting to delete; search by either number or name
  5. Action (A) - select DELETE from the drop-down
  6. Filter Action (A) to show the updates only (uncheck Delete from the listing)
  7. Delete all Update rows
  8. Remove Filter so that only the Delete UDA (ID) and or UDA Value are showing
  9. Repeat previous steps as needed if deleting more than one Brand Name
  10. Save as .ods file to:
    📁Code M\Code MS\Data Steward\UDA Creation v16
    Save as "Brand Deletes *Date*
  11. In RMS v16:
    Tasks → Foundation Data → Data Loading → Upload
    Set:
    Template Type:Items
    Template: Brands
    browse to your .ods file → Upload File
  12. If no notification received → brand created successfully. If notification received → error occurred, check issues and troubleshoot using the query below.
SQL
-- 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;


Finding Missing UDAs

When deleting Brands the corresponding Brand UDA will also need to be removed, as previously stated. Once a year a Web Master Brand UDA query should be ran to fill and try to capture all the missing numbers in the 999 long UDA listing

To find missing UDAs in the sequence run the following query:

SQL
SELECT U1.UDA_ID, U1.UDA_DESC, U2.UDA_VALUE, U2.UDA_VALUE_DESC 
FROM rms.uda u1, rms.UDA_VALUES u2 
WHERE U1.UDA_ID = U2.UDA_ID 
AND u1.uda_id IN ('9639', '10339', '10340', '10341')
ORDER BY U1.UDA_ID, U2.UDA_VALUE;
  1. Create a column with the numbers 1-999 (as that’s how many UDA Values are in any completed UDA ID)
  2. Apply Conditional Formatting to the columns with the UDA Values and the column that numbers 1-999 were added to
  3. Add a Filter to the top row with Headers and filter by 'Filter by Color' > 'No Fill" on the newly added - this should show you which UDAs are missing
  4. These are the UDA Value numbers that need to be re-used when building future Brands

  5. UDA_ID UDA_DESC UDA_VALUE UDA_VALUE_DESC Numbers to Match Up
    400 9639 WEB MSTER BRANDS 400 Chicago Cutlery 399
    482 9639 WEB MSTER BRANDS 483 Coynes 481
    507 9639 WEB MSTER BRANDS 509 Custom Leather 506
    580 9639 WEB MSTER BRANDS 586 Dream Modes 579
    581 9639 WEB MSTER BRANDS 587 Dream Star 580
    582 9639 WEB MSTER BRANDS 588 Dry Idea 581
    585 9639 WEB MSTER BRANDS 591 Dynamic Designs 584
    667 9639 WEB MSTER BRANDS 674 Fantasia 666
    802 9639 WEB MSTER BRANDS 810 Gramicci 801


    Queries

    SQL
    ---Full list of Brands---
    SELECT *
    FROM rms.brand
    ORDER BY BRAND_NAME;
    SQL
    ---Full List of UDA's with Descriptions---
    SELECT U1.UDA_ID, U1.UDA_DESC, U2.UDA_VALUE,
           U2.UDA_VALUE_DESC 
    FROM rms.uda u1, rms.UDA_VALUES u2 
    WHERE U1.UDA_ID = U2.UDA_ID 
    ----and u1.uda_id = 5261 
    ORDER BY U1.UDA_ID, U2.UDA_VALUE;

    Creating New Brand UDA IDs

    When we are running low on the current UDA ID's count for new brands.

    1. Follow the Report UDA procedure for details on how to create a new reporting UDA with the naming format "WEB MSTER BRANDS #", replacing # with the next in the series.
    2. There must be at LEAST one UDA value added when creating NEW brand UDA IDs.
    3. Once the new brand Reporting UDA ID and value(s) are created, add them to the following list.
    4. To find the newly build report UDA IDs, go to: Tasks > Foundation Data > Data Loading > Download
      Template Type: Items
      Template: User Defined Attributes (UDA)
    5. Download the file, and filter by "WEB MSTER BRANDS" in the UDAs tab. Note the newest one's UDA ID may be different from what was submitted earlier in the process.
    6. Delete all but the newly created WEB MSTER BRANDS # from the UDAs tab, and filter the UDA_Values tab by that UDA_ID. Then save this for the incident to be submitted in the following step.
    7. Current Brand UDA IDs: '9639', '10339', '10340', '10341', '35001', '35002', '85002', '85003', '85004', '85005', '85006, '85007'
    8. Lookup Create an incident (based on IN# ) to have RAVE link the new brand udas to the brand file.
    9. Incident Summary: Brand UDA newly created to update code_detail table

      Description: "We created new Brand UDA values. The Brand UDA IDs are - "35001" and "35002" and need to be added/updated in the code_detail table." -- Reference IN#IN1733034

      You will also need to attach the reporting UDAs that were added + the UDA values. You can get this from downloading the UDAs, or from updating the uploaded file with the correct UDA IDs in place of the placeholders.


      Action UDA UDA Description Display Type Data Type Data Length Single Value?
      Create 85002 WEB MSTER BRANDS 7 List of Values Alphanumeric No


      Action UDA UDA Value UDA Value Description
      Create 85002 1 REBER


    Queries

    SQL
    ---Full list of Brands---
    SELECT *
    FROM rms.brand
    ORDER BY BRAND_NAME;
    SQL
    ---Full List of UDA's with Descriptions---
    SELECT U1.UDA_ID, U1.UDA_DESC, U2.UDA_VALUE,
           U2.UDA_VALUE_DESC 
    FROM rms.uda u1, rms.UDA_VALUES u2 
    WHERE U1.UDA_ID = U2.UDA_ID 
    ----and u1.uda_id = 5261 
    ORDER BY U1.UDA_ID, U2.UDA_VALUE;

Primary Supplier / Costing Location Project

Project files are located at:

📁G:\Code_M\Code_MS\Data Steward Team\Primary Supplier at Loc Level
💡
Sort MSAs from smallest to largest file size (KB) and work the smaller ones first — these tend to already be corrected in RMS v16.

Folder Naming & Organization

  1. Copy buying team MSAs into the file path above (do not edit off the buying team's copies). Name folders: Dept XXX – MSA [Team Member Name] [Year]
  2. Inside each dept folder, create a subfolder with your DST username and "Completed" — e.g., 📁Dept 984 - MSA Carrie 2026\CALIFORNIA\Jess Completed
  3. Within your completed folder, keep: MSAs already correct (label Already Done), supplementary documents used (label SUPPLEMENTARY DOCUMENT), forms used to create Item Lists (label with ITEM LIST in the name).

Working an MSA

  1. Open the MSA (click "Don't Update" when prompted). Go to the most recent tab.
  2. Verify if the same RINs appear across all tabs. Check if sections are broken into Zones — if so, work in sections by zone.
  3. Copy ITEM + NEW ITEM columns to a new Excel sheet. Paste Special → Values only. Remove duplicates.
  4. Verify the supplier on the MSA is attached to both the Parent AND Transaction RINs. If not, send back to the buying team to add.
  5. Pull transactions and run through the long query (see SQL Reference). Update zones to match the ones you are working.
  6. Create a Location List from the zones being worked (Stores from Column G + Warehouses from Column L).
  7. Copy Parent and Transaction items to an Item List → Create Item List in v16.
  8. Mass Change locations using the Item List and the Location List created. Add DUNs, country, costing location (warehouse from Column L) → Save and Close.
  9. Rerun the query to verify no updates fell out.
  10. For franchise locations: repeat mass loc update to add only franchise locations — update Primary Supplier only (no costing location).

TPGC — DST Working Notes

Practical tips compiled from DST experience with the TPGC process.

  1. Jane (Reddick) will send TPGC information using the DST Cheat Sheet. Locate the filled-out Cheat Sheet at:
    📁G:\Code_M\Code_MS\Data Steward Team\Xstore\MNT Files
  2. Use the Cheat Sheet information to pull the correct version of the edited MNTCreator file from the same location.
  3. Fill out the MNT Creator file tabs with the proper data. Reference the XStore Warranty SOP, Pages 19–29.
  4. Create a working folder in the MNT Files folder named with the subject and date — e.g., TPGC 4.27.26. Drop the following files into this folder:
    • The MNT files created
    • The filled-out Cheat Sheet from Jane Reddick
    • The populated MNTCreatorFile with completed tabs
    • A Notepad file with all Process numbers from XAdmin
  5. Once MNT files are created, move them from your U Drive to the folder created above.
  6. Upload into XAdmin and Deploy. Instructions are in the XStore Warranty SOP.

3rd Party Gift Cards (TPGC)

Do NOT create 3rd Party Gift Cards in XAdmin. TPGC items are created in RMS as non-merchandise and configured via MNT files only.

Process Overview

  1. Create the 3rd Party Gift Card item in RMS as Non-Merchandise.
  2. Create and upload the spreadsheet for STS.
  3. Create an Incident Ticket for the STS Team to add new items to the lookup table.
  4. Submit TPGC RINs and Fee RINs to the ORUP Team.
  5. Using the MNT Creator file, create the required MNT files for the card type (see matrix below).
  6. Upload into XAdmin and Deploy.

MNT Files Required by Card Type

The number and type of .mnt files needed vary by gift card type. Refer to the XAdmin Gift Card MNT File Matrix in the Non-Merch SOP (Section 9.1.2) for the complete breakdown.

Key MNT file tabs used for TPGC creation include: GCITMProperties, TPGAttachFee, TPGC_UPC, TPGNonMerchandise, and ItemPriceAction.

Franchise Costing Location & RPM Pricing Impact

Impact of Supplier and Franchise Costing Setup Issues on RPM Pricing and Margin

Accurate RPM retail pricing depends on consistent supplier and costing data across all locations within a price zone. Two common setup issues can negatively affect RPM price strategy calculations and margin outcomes.

⚠ Inconsistent Primary Supplier Within a Price Zone

All locations within a price zone must have the same primary supplier. When a location has a different primary supplier, the item cost for that location may differ from the rest of the zone.

RPM calculates the new retail price by averaging the cost across all locations (this includes warehouses associated to the zone) in the price zone and then applying a price guide. If costs differ due to inconsistent suppliers, the averaged cost may not represent the intended cost structure, resulting in a retail price that is either too high or too low.

⚠ Franchise Locations Missing a Costing Location

Franchise locations must have a valid costing location assigned at the item/location level. If a costing location is missing, RPM may use incomplete, default, or incorrect cost data — or be unable to calculate cost at all.

When these locations are included in a price zone, their missing or incorrect costs can distort the cost average used by RPM, further impacting the suggested retail price.

Combined Impact on RPM Retail Calculation — when either, or both, of these issues exist within the same price zone:

RPM still includes all locations in the zone when averaging cost (this includes warehouses). Incorrect, inconsistent, or missing costs skew the calculated average cost, and the price guide is applied to a distorted cost base — the resulting retail price may not reflect true supplier economics.

Impact to Margin — these setup issues can lead to:

  • Overstated or understated margins at the item and zone level
  • Unexpected margin erosion or inflated pricing
  • Inconsistent margins across locations within the same price zone
  • Reduced confidence in margin reporting and pricing decisions
  • Increased need for manual price overrides and corrections
Why This Matters: Supplier consistency and valid costing locations are foundational to accurate RPM pricing. Ensuring both are correctly maintained helps protect margin integrity, ensures predictable retail pricing, and reduces operational risk.

Affected Price Strategy departments: 962 – Beverages 982 – Spirits 983 – Wine 984 – Beer 962 – Completed

Identify Supplier and Franchise Costing Location Issues

  1. Work with the department to obtain the path for the current MSA's.
  2. Open an MSA (when prompted, click "Don't Update").
    MSA File — Header & Item Section
    NEXCOM — Navy Exchange Service Command, Virginia Beach, VAPricing For: Feb-26 / LL 481294 / Zone 89 – Fallon, NV
    CompanyBreakthru Beverage Nevada — Dept. 984
    DUNS787084797POCClarissa Cox
    Emailccox2@breakthrubev.comTel775-352-1114
    Parent RIN#Trans RIN#Item DescriptionUnit UPCCase PackCurrent CostCurrent Retail
    1617433516174374Brewdog Non-Alcoholic Mix Pack 12pk 12oz Cans8428171017742$25.20$15.99
    1466662614666631El Jimador Variety Pack 12pk 12oz Cans8402456000432$29.61$18.49
    1466662514666630Jack Daniel's Country Cocktails Variety 12pk 12oz Slim Cans8402456001662$29.61$18.49
    1617319416173223Jack Daniels Country Cocktails Tea 12pk 12oz Slim Cans8402456002962$29.61$18.49
    1322180913221924BrewDog Elvis Juice Grapefruit IPA 6pk 12oz Cans8428171001974$22.00$10.49
    1322181013221925BrewDog Hazy Jane New England IPA 6pk 12oz Cans8428171003194$23.00$10.49
    121821945585288Jack Daniel's Country Cocktails Downhome Punch 6pk 10oz Bottles0821842260184$25.40$8.99
    1314734213147344Jack Daniels Country Cocktails Southern Peach 6pk 10oz Bottles0821842030884$25.40$8.99
  3. Copy the tran level RIN from the "ITEM" and "NEW ITEMS" sections within the MSA file (the sheet also contains separate "NEW ITEMS" and "DISCONTINUED" tab sections below the main item table, shown in the table above).
    The priority is to correct the active items. If an item is listed under the "DELETE" or "DISCONTINUED" section, these can be skipped unless there is SOH and bandwidth to correct them.
  4. Paste the items into an Excel worksheet.
    Paste OptionUse
    Paste ValuesPastes the RIN values only — use this option so formulas are not copied from the original MSA file
    Other Paste Options / Paste SpecialDo not use — these will carry over formulas or formatting from the source file
    Make sure to use "Paste Values" so as not to copy formulas from the original file.
  5. Format the RINs for SQL ('#',).
    CellRaw RIN ValueFormat Cells CategoryFormatted for SQL
    A116174374Custom'16174374',
    A214666631Custom'14666631',
    A314666630Custom'14666630',
    A416173223Custom'16173223',
    A513221924Custom'13221924',
    A613221925Custom'13221925',
    A75585288Custom'5585288',
    A813147344Custom'13147344',
    Validate that all of the RINs formatted correctly and correct any that did not.
  6. Open SQL or TOAD and copy/paste the query below into a blank SQL Editor tab.
    SQL — Primary Supplier / Costing Location Detail Query
    select distinct im.dept, im.item_parent as "ITEM PARENT", im.item, im.item_desc as "ITEM DESC", rzl.zone_id as "ZONE ID", rz.name, x.loc,
    CASE when ST.store_name is not null then ST.store_name else WH.wh_name end as "LOC NAME", st.store_type AS "STORE TYPE",
    x.source_method as "SOURCE METHOD", x.source_wh as "SOURCE WH", st.default_wh as "DEFAULT WH", x.costing_loc as "COSTING LOC", x.costing_loc_type as "COSTING LOC TYPE",
    X.PRIMARY_SUPP as "PRIMARY SUPP", sp.sup_name as "SUP NAME", y.unit_cost as "UNIT COST", x.unit_retail as "UNIT RETAIL", x.regular_unit_retail as "REG UNIT RTL",
    x.selling_unit_retail as "SELLING UNIT RTL", x.promo_retail as "PROMO RTL", x.clear_ind as "CLEAR IND", Y.LAST_UPDATE_DATETIME as "ISCL LAST UPDATE",
    x.create_datetime as "IL CREATE DATE", X.LAST_UPDATE_DATETIME as "IL LAST UPDATE", St.store_open_date as "STORE OPEN DATE"
    from rms.item_master im, rms.item_loc x, rms.item_supp_country_loc y, rms.sups sp, RMS.rpm_zone RZ, RMS.rpm_zone_location RZL, store st, wh,
    (select im.dept, im.item, im.item_desc, rzl.zone_id ,x.loc, CASE when ST.store_name is not null then ST.store_name else WH.wh_name end as "LOC NAME", st.store_type AS "STORE TYPE",
    x.source_method as "SOURCE METHOD", x.source_wh as "SOURCE WH", st.default_wh as "DEFAULT WH", x.costing_loc as "COSTING LOC", x.costing_loc_type as "COSTING LOC TYPE",
    X.PRIMARY_SUPP as "PRIMARY SUPP", sp.sup_name as "SUP NAME", y.unit_cost as "UNIT COST", x.unit_retail as "UNIT RETAIL", x.regular_unit_retail as "REG UNIT RTL",
    x.selling_unit_retail as "SELLING UNIT RTL", x.promo_retail as "PROMO RTL", x.clear_ind as "CLEAR IND", Y.LAST_UPDATE_DATETIME as "ISCL LAST UPDATE",
    x.create_datetime as "IL CREATE DATE", X.LAST_UPDATE_DATETIME as "IL LAST UPDATE", St.store_open_date as "STORE OPEN DATE"
    from rms.item_master im, rms.item_loc x, rms.item_supp_country_loc y, rms.sups sp, RMS.rpm_zone RZ, RMS.rpm_zone_location RZL, store st, wh
    where im.item = x.item
    and im.item = y.item
    and x.loc = y.loc
    and x.loc = rzl.location
    and x.loc = st.store (+)
    and x.loc = wh.wh (+)
    and rz.zone_id = rzl.zone_id
    and rz.zone_group_id = '2'
    and x.primary_supp = y.supplier
    and x.primary_supp = sp.supplier
    and (exists (select 'x' from rms.item_loc il, rms.store ss, RMS.rpm_zone RZ2, RMS.rpm_zone_location RZL2
    where x.item = il.item and il.loc = ss.store and costing_loc is null and store_type = 'F'
    and ss.store = rzl.location
    and rz2.zone_id = rzl2.zone_id
    and rz2.zone_group_id = '2'
    and rz.zone_id = rz2.zone_id)
    or
    exists (select 'x' from (select item, rz3.zone_id, count(distinct primary_supp) as supp_count from item_loc il2, RMS.rpm_zone RZ3, RMS.rpm_zone_location RZL3
    where il2.item = x.item
    and il2.loc = rzl3.location
    and rz3.zone_id = rzl3.zone_id
    and rz3.zone_group_id = '2'
    and rz.zone_id = rz3.zone_id
    and (il2.loc= wh.wh or il2.loc in (select store from store where store_close_date is null))
    group by item, rz3.zone_id)
    where supp_count > '1')
    )
    and st.store_close_date is NULL
    )ab
    where im.item = x.item
    and im.item = y.item
    and x.loc = y.loc
    and x.loc = rzl.location
    and x.loc = st.store (+)
    and x.loc = wh.wh (+)
    and rz.zone_id = rzl.zone_id
    and im.item_level = im.tran_level
    and rz.zone_group_id = '2'
    and x.primary_supp = y.supplier
    and x.primary_supp = sp.supplier
    and im.item = ab.item
    and rz.zone_id = ab.zone_id
    and st.store_close_date is NULL
    and im.item in ('16174374',
    '14666631',
    '14666630',
    '16173223',
    '13221924',
    '13221925',
    '5585288',
    '13147344')
    and rzl.zone_id in ('89')
    order by im.item, rzl.zone_id, x.loc ;
  7. Copy the formatted RINs from the Excel worksheet and paste them into the SQL query.
    Make sure to update the RZL.Zone ID(s) to match the MSA that you are working on.
  8. Run the query.
    • This query returns any item/location combination that is either missing a Franchise costing location and/or has a primary supplier that differs across locations within the same retail price zone.
    • If either condition exists (missing costing location or inconsistent primary supplier), the query will return all locations associated to that item within the affected zone ID.
    Important! The query validates supplier consistency across locations, not supplier accuracy. The query will not return results for an item/price zone combination when all locations within the price zone share the same primary supplier, even if the assigned supplier is not the correct supplier for the price zone.
  9. Export query results to an Excel Spreadsheet.
  10. Highlight the item/location combinations that need to be corrected. This makes it easier to keep track of what needs to be worked.
    • Orange highlight indicates that there is a franchise location that is missing a costing location.
    • Yellow highlight indicates that the supplier for that item/location is not consistent with the MSA supplier.
    DEPTITEM PARENTITEMITEM DESCZONE IDNAMELOCLOC NAMESTORE TYPESOURCE METHODCOSTING LOCPRIMARY SUPPSUP NAME
    9841466662514666630Jack Daniels Country Cocktails Variety 12pk 12oz Slim Cans89FALLON, NV384FALLON MAIN STORECS9950787084797BREAKTHRU BEVERAGE NEVADA
    9841466662514666630Jack Daniels Country Cocktails Variety 12pk 12oz Slim Cans89FALLON, NV385FALLON N LODGE STFS9950151843976ALLIED BEVERAGES INC
    9841466662514666630Jack Daniels Country Cocktails Variety 12pk 12oz Slim Cans89FALLON, NV542FALLON GASCS9950787084797BREAKTHRU BEVERAGE NEVADA
    984121821945585288JD CC 10OZ DOWNHOME PUNCH 6PK NRB89FALLON, NV384FALLON MAIN STORECS9950787084797BREAKTHRU BEVERAGE NEVADA
    984121821945585288JD CC 10OZ DOWNHOME PUNCH 6PK NRB89FALLON, NV385FALLON N LODGE STFS 787084797BREAKTHRU BEVERAGE NEVADA
    984121821945585288JD CC 10OZ DOWNHOME PUNCH 6PK NRB89FALLON, NV542FALLON GASCS9950787084797BREAKTHRU BEVERAGE NEVADA
    984121821945585288JD CC 10OZ DOWNHOME PUNCH 6PK NRB89FALLON, NV2291Vend FallonFS 23987415ASSOCIATED DISTRIBUTORS, LLC

Correct Missing Franchise Costing Locations

  • If an item/location combination is missing a costing location and has an incorrect supplier, add the costing location first before correcting the supplier.
  • Make corrections at the parent RIN whenever possible. If discrepancies exist between the parent RIN and its tran RIN(s) (e.g., a store or warehouse is ranged only at the tran level), apply updates only at the tran RIN level.
  • Any costing location added must be a primary warehouse (WH).
  • As a general rule, use the default warehouse associated with the applicable price zone.
  • If the warehouse that needs to be added as a costing location is not currently ranged, it must be ranged prior to adding the costing location.
  • When ranging a warehouse, ensure the primary supplier associated with the price zone in which the warehouse resides is used — e.g., when adding WH 9950, use the primary supplier associated with Price Zone 52 (San Diego); when adding WH 9840, use the primary supplier associated with Price Zone 1 (Norfolk).

Steps to Add a Costing Location

  1. Filter the worksheet to identify items and franchise locations that are missing a costing location:
    Filter ColumnValue
    Store TypeF
    Costing Location(Blank)
  2. Review the filtered results and determine the most efficient correction method. Apply best judgment when deciding which method to use.
    • Use manual updates when the volume is low (for example, one item across one or two locations).
    ItemStore TypeLocationCosting LocationCorrection Method
    12182194F385 – FALLON N LODGE ST(Blank)Manual — 1 item, 2 locations
    12182194F2291 – Vend Fallon(Blank)Manual — 1 item, 2 locations
    • Use item lists and location lists when the volume is higher and repetitive updates are required. If there were a high volume of locations that needed a costing location added, it would also be best practice to create a location list.
    ItemStore TypeLocationCosting LocationCorrection Method
    16174374F385 – FALLON N LODGE ST(Blank)Item List — multiple items require a costing location update
    14666631F385 – FALLON N LODGE ST(Blank)
    14666630F385 – FALLON N LODGE ST(Blank)
    16173223F385 – FALLON N LODGE ST(Blank)

Add a Costing Location Manually

Important: There are two ways to add or update a costing location within the Locations screen: (1) Edit Locations, or (2) Mass Change / Location Attributes.

Navigate to the Locations Screen

  1. Log into Oracle RMS.
  2. Navigate to Tasks → Item → Manage Items.
  3. In the Item Search form, enter the Parent RIN and click Search.
  4. From the results, click the Parent RIN hyperlink to open the item.
  5. Click More Actions and select Locations.

Option 1: Edit Locations Screen — use this option when updating one franchise location at a time.

  1. On the Locations screen, if filters are not visible, click the Filter (funnel) icon to display them.
    ScreenItem
    Item Locations — Parent 12182194 (JD CC 10OZ DOWNHOME PUNCH 6PK NRB)Filter (funnel) icon toggles the column filter row
  2. In the Locations filter field, enter the franchise location number and press Enter.
    If the franchise location does not appear, that usually means it exists only at the tran level and will need to be updated there.
    LocationStatusAverage Unit CostUnit RetailCurrencyRangedPrimary SupplierPrimary Supplier SitePrimary CountrySource Method
    Store 385 — FALLON N LODGE STActive7.997.99USD787084797BREAKTHRU BEVERAG…USASupplier
  3. Review the results. Highlight the franchise location row and click the Pencil (Edit) icon.
  4. In the edit window, enter the appropriate Costing Location.
    Edit Locations — Field Reference
    FieldValue / Notes
    Location385 — FALLON N LODGE ST
    StatusActive
    Primary Variant
    Primary Supplier Site787084797 — BREAKTHRU BEVERAGE NE...
    Primary CountryUSA
    Source MethodSupplier
    Source Warehouse
    Costing LocationEnter the appropriate warehouse number here
    Store Order Multiple
    Ranged
    Inbound Handling Days
    Case per Pallet
    CurrencyUSD
    Selling Unit Retail7.99 per EA
  5. Click OK to save and exit.

Option 2: Mass Change / Location Attributes — use this option when updating multiple franchise locations at once.

  1. From the Locations screen, click More Actions → Location Attributes.
    Location TypeLocationNameStatusAvg Unit CostUnit RetailPrimary SupplierPrimary Supplier SiteSource Method
    Store2NORF PACKAGE STOREActive7.997.9978676000CHESBAY DISTRIBUTIN…Supplier
    Store16NORF N LODGE STOREActive7.997.9978676000CHESBAY DISTRIBUTIN…Warehouse
    Store28PORTS SCOTT CTR MAINActive7.997.9978676000CHESBAY DISTRIBUTIN…Supplier
  2. The Change Item / Location Attributes screen opens.
  3. In the Apply Updates To section, click the green + icon. Select the appropriate Location type (e.g., Store or Location List) and Add all franchise locations that are missing a costing location.
    TypeLocationName
    Store385FALLON N LODGE ST
    Store2291Vend Fallon
  4. In the Location Attributes section, enter the appropriate Warehouse (WH) number in the Costing Location field.
    Change Item / Location Attributes — Field Reference
    FieldValue / Notes
    Primary Variant
    Taxable
    Primary Supplier Site
    Primary Country
    Source Method
    Source Warehouse
    Costing Location9950
    Store Order MultipleWC REPLENISHMENT
    Ranged
    Inbound Handling Days
    Daily Waste %
    Local Item Description
  5. Click Save and Close to apply the updates and exit the screen.

Add Costing Location Using Item and Location Lists

  • Item lists must be created using the parent item number.
  • Create and induct the required Item Lists and Location Lists by following the steps outlined in the Item and Location List Induction QRG:
    NEXCOM HUB → M → Merchandising Support → ORUP → Training Materials → 9.0 Item_Loc List → Item List and Location List Induction QRG
  1. After the item list has been successfully created, navigate within RMS to Foundation → Items → Manage Item Lists.
  2. Enter the appropriate Item List number and click Search.
  3. Within the search results window, highlight the Item List then select Actions / Mass Change / Item Locations.
    TypeActionTotal ItemsCreated DateCreated By
    Order Change DynamicCreate From Existing24/11/26standis

    Available actions from this menu: Create From Existing, Edit, View, Export to Excel, Reclassification, Item, Replenishment, VAT Rates, Item/Locations, User Defined Attributes, Seasons/Phases, Item Ticket, Up Charges.

  4. In the Change Item/Loc Attributes screen, click the green + icon to add the required locations (either manually or by using a Location List) and enter the appropriate Costing Location, then save the changes to complete the update.
    Item List 21860351 — "Odom Supplier change" — Change Item/Loc Attributes
    SectionFieldValue / Notes
    Apply Updates ToType / LocationNo data to display — click green + to add locations
    Location AttributesPrimary Variant
    Taxable
    Primary Supplier Site
    Primary Country
    Source Method
    Source Warehouse
    Costing LocationEnter appropriate warehouse number
    Store Order Multiple
    Ranged
    Inbound Handling Days / Daily Waste %

Correct Supplier Discrepancies

Change Item / Loc Attributes — Correcting a Supplier Discrepancy
SectionFieldValue / Notes
Apply Updates ToStore 385FALLON N LODGE ST
Store 2291Vend Fallon
Location AttributesStatus
Primary Variant
Taxable
Primary Supplier SiteEnter the correct supplier site
Primary CountryUSA
Source Method / Source Warehouse / Costing LocationLeave as-is — not being corrected in this update
Important: After completing all corrections, rerun all MSA items through the SQL query to validate that all updates were successfully applied. When item and location lists are used, items or locations that do not exist at the parent item level may be excluded from the update. Re-running the MSA will highlight any remaining items or locations requiring additional correction.

Continue to use the methods outlined above and work through each MSA.

Creating a New Report UDA Value

*Adding to an existing UDA (ID)*

Download UDA Foundation Template

In RMS, navigate through the menu selections to access the foundation data downloading terminal:

  1. Go to: TasksFoundation DataData LoadingDownload
  2. For Template Type - select Items
  3. For Template - select User Defined Attributes

  4. ORACLE Merchandising
    Download Data ×

  5. Click Download → Select Open with Microsoft Excel → Click OK.
  6. Once Excel Spreadsheet opens, there will be 5 tabs listed:
    UDAs, UDA_Translations, UDA_Values, UDA_Value_Translations, & UDA_Defaults

Worksheet Architecture Overview

When the spreadsheet opens in Microsoft Excel, you will observe 5 primary structure tabs across the workbook footer:

  • UDAs
  • UDA_Translations
  • UDA_Values
  • UDA_Value_Translations
  • UDA_Defaults

To create a new Report UDA Value to add to an existing Report UDA (ID) in the previous steps, clear all data from the UDAs & UDA_Defaults tabs below the Headers (Row 1) and do as follows on the UDA_Values tab:

  1. Convert UDA (B) and UDA Values (C) to Numbers
  2. Sort data by UDA (B) and then by UDA Values (C)
  3. Add Filter to Header (Row 1)
  4. Filter UDA (B) to UDA (ID) wanting to add new Report UDA Value to; scroll to bottom of list
  5. Current listing of UDA with Description and Value can be found under Code M/Code MS/Data Steward Team/ORUP/QRGs/Added to HUB for reference*

  6. Action (A) - select CREATE on drop-down list
  7. UDA (B) - copy the same UDA (ID) number from the row above
  8. UDA Value (C) - enter the next available numerical value
  9. *There can only be a max of 999 UDA Values per UDA (ID)*

  10. UDA Value Description (D) - enter the Report UDA Value requested in Proper Case

  11. Action UDA UDA Value UDA Value Description
    Create 50005 1 SOP Test Value

  12. Save as an .ods file
  13. Save in Code M/Code MS/Data Steward/UDA Creation v16
  14. Save as Report UDA Updates (todays date)
  15. Navigate back to RMSv16 > Tasks > Foundation Data > Data Loading > Upload

  16. Once in the Upload Data tab input the following:

  17. For the Template Type - select Items
  18. For Template - select User Defined Attributes (UDA)
  19. For Process Description - can be left as auto-populated description or edited
  20. For Source File - click Browse - find .ods file that was saved


  21. ORACLE Merchandising
    Upload Data ×
    UDA ID Updates 1.19.21 .ods




  22. Upload File
  23. To determine if induction was successful:

  24. If you do not receive a notification, new Report UDA Value has been created
  25. If you receive a notification, there was an error; check Issues and troubleshoot

Run below query with LOWERCASED RMSv16 User ID to find out if PS or PE

SQL
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;

Deleting UDA Values

  1. In RMS v16:
    Tasks → Foundation Data → Data Loading → Download


  2. ORACLE Merchandising
    Download Data ×


  3. Click Download. Open the downloaded file in Microsoft Excel
  4. Once Excel Spreadsheet opens, go to the tab you are deleting from, either UDAs or UDA-Values


  5. *Note: If deleting from the UDAs tab, you will need to delete all UDA Values associated with that UDA (ID) first*

  6. Add filter to the Header Row (Row 1)
  7. Search/Select the UDA (ID) and/or UDA Value wanting to delete; search by either number or name
  8. Action (A) - select DELETE from the drop-down
  9. Filter Action (A) to show the updates only (uncheck Delete from the listing)
  10. Delete all Update rows
  11. Remove Filter so that only the Delete UDA (ID) and or UDA Value are showing


    1. Queries

      SQL
      ---Full List of UDA's with Descriptions---
      SELECT U1.UDA_ID, U1.UDA_DESC, U2.UDA_VALUE,
             U2.UDA_VALUE_DESC 
      FROM rms.uda u1, rms.UDA_VALUES u2 
      WHERE U1.UDA_ID = U2.UDA_ID 
      ----and u1.uda_id = 5261 
      ORDER BY U1.UDA_ID, U2.UDA_VALUE;