| Oracle® Retail Assortment & Item Planning for Fashion/Softlines Cloud Service Implementation Guide Release 19.0 F24867-12 |
|
 Previous |
 Next |
| Oracle® Retail Assortment & Item Planning for Fashion/Softlines Cloud Service Implementation Guide Release 19.0 F24867-12 |
|
Previous |
Next |
Assortment & Item Planning Cloud Service supports integration with Oracle Retail Merchandising Foundation Cloud Service (RMF CS). If a retailer has RMF CS as the source system for inventory and transactional data, they can readily integrate to get foundation hierarchy data, inventory, and transactional data from RMF Cloud Service. This appendix provides details on the list of hierarchies and data files that are integrated with Oracle Retail Merchandising Foundation Cloud Service.
Following is a list of requirements/assumptions for integration with RMF CS:
A&IP CS Channel is mapped to RMF CS Area.
Warehouses are sent to A&IP CS as locations. RMF CS Warehouses holds inventory and on-order data. RMF CS Warehouses needs to be mapped to A&IP CS Channels within A&IP CS in order to get the true picture of inventory and on-order data.
RMF CS sends hierarchy and data files on a weekly basis.
RMF CS sends the data at item level, so A&IP CS needs to be implemented with the lowest data load intersection as item.
RMF CS sends all data based on only one primary currency. It also sends currency conversion rates for different currencies. That can be used within A&IP CS to plan and view data on different local currencies.
RMF CS sends the following sets of hierarchy and data files. All RMF CS files are copied to the common cloud service share location from where A&IP CS can pick up the files for further processing. Interface files need to be transformed to format the files into the A&IP CS required format to filter columns not used and split and create different group of files as needed by A&IP CS. A&IP CS Configured Batch Process will transform the files to the A&IP CS required formats, rename the final files as needed by A&IP CS, and copy them to the domain input location for subsequent hierarchy or measure load processing. For each of the hierarchy and data files, RMF CS also sends a trigger file with the same name as the original file with the extension .complete. The Assortment & Item Planning for Fashion/Softlines Cloud Service batch process waits for the trigger files to start processing the corresponding data or hierarchy file. After processing, it deletes those trigger files.
The following hierarchy files are provided by RMF CS and need to be transformed to the A&IP CS format before loading them into IP Cloud Service. For each hierarchy file, RMF CS only sends the base and alternate dimensions of the hierarchies and not the user alternate rollups.
Calendar Hierarchy - rms_clnd.csv.dat
RMF CS sends the calendar hierarchy file without calendar labels. Calendar labels are added in the weekly batch process by calling the A&IP CS custom script (ra_custom) with the parameter rms_clnd_label, which adds the calendar labels. If the customer wants to use different calendar labels, they can load their preferred calendar labels using generic hierarchy position translations enabled for the calendar hierarchy.
RMF CS sends the calendar hierarchy file with dates for five years. Based on the current date, two year historical dates, current year dates, and two future year dates.
The following table contains the list of column contents from the file. Only required columns for A&IP CS are filtered by the transform process.
| Field Name | Field Description | A&IP CS Mapping |
|---|---|---|
| Day | The date from which the 4-5-4 data was derived, in YYYYMMDD format. | day |
| Week | The end of week date for the day, in YYYYMMDD format. | week |
| Month | The 4-5-4 month of the year, valid values 1 to 12. | mnth |
| Quarter | The 4-5-4 quarter of the year, valid values 1 to 4. | qtr |
| Half | The 4-5-4 half of the year, valid values 1 or 2. | half |
| Year | The 4-5-4 year. | year |
| week_of_year | The 4-5-4 week of the year, valid values 1 to 53. | woyr |
| day_of_week | The day number within the week, valid values 1 to 7. |
Product Hierarchy - rms_prod.csv.dat
RMF CS exports all sellable and inventoried items.
The following table contains the list of column contents from the file. Only required columns for A&IP CS are filtered by the transform process. Some measure data files are also extracted and loaded from this RMF CS product hierarchy file.
| Field Name | Functional Name | A&IP CS Mapping |
|---|---|---|
| ITEM | Item ID | sku |
| ITEM_DESC | Item Description | sku_label |
| ITEM_PARENT_DIFF | Parent/Diff ID | skup |
| ITEM_PARENT_DIFF_DESC | Parent/Diff Description | skup_label |
| ITEM_PARENT | Parent ID | skug |
| ITEM_PARENT_DESC | Parent Description | skug_label |
| SUBCLASS_ID | Subclass ID | scls |
| SUB_NAME | Subclass Name | scls_label |
| CLASS_ID | Class ID | clss |
| CLASS_NAME | Class Name | clss_label |
| DEPT | Department | dept |
| DEPT_NAME | Department Name | dept_label |
| GROUP_NO | Group | pgrp |
| GROUP_NAME | Group Name | pgrp_label |
| DIVISION | Division | dvsn |
| DIV_NAME | Division Name | dvsn_label |
| COMPANY | Company | cmpp |
| CO_NAME | Company Name | cmpp_label |
| FORECAST_IND | Forecastable Item flag | |
| CLASS_DISPLAY_ID | Class Display ID | drtyclsst |
| SUBCLASS_DISPLAY_ID | Subclass Display ID | drtysclst |
| BRAND_NAME | Brand ID | drdvprdatt |
| BRAND_DESCRIPTION | Brand Description | |
| SUPPLIER | Supplier Site | drdvprdatt |
| SUP_NAME | Supplier Name | |
| DIFF_TYPE1 | Diff Type1 | |
| DIFF_ID1 | Diff 1 | drdvprdatt |
| DIFF_TYPE2 | Diff Type2 | |
| DIFF_ID2 | Diff 2 | drdvprdatt |
| DIFF_TYPE3 | Diff Type3 | |
| DIFF_ID3 | Diff 3 | drdvprdatt |
| DIFF_TYPE4 | Diff Type4 | |
| DIFF_ID4 | Diff 4 | drdvprdatt |
Location Hierarchy - rms_loc.csv.dat
RMF CS Area will be exported as A&IP CS Channel.
All Virtual Warehouses in RMF CS will be exported as unique locations.
The following table contains the list of column contents from the file. Only required columns for A&IP FSL CS are filtered by the transform process.
| Field Name | Functional Name | A&IP CS Mapping |
|---|---|---|
| LOCATION | Location ID | stor, strc |
| LOC_NAME | Location Name | stor_label,strc_label |
| DISTRICT | District ID | dstr |
| DISTRICT_NAME | District Name | dstr_label |
| REGION | Region ID | regn, tdar |
| REGION_NAME | Region Name | regn_label, tdar_label |
| AREA | Area ID | chnl, chnc |
| AREA_NAME | Area Name | chnl_label, chnc_label |
| CHAIN | Chain ID | chan |
| CHAIN_NAME | Chain Name | chan_label |
| COMPANY | Company ID | comp |
| CO_NAME | Company Name | comp_label |
| COMPANY_CURRENCY | Primary Currency | |
| LOC_TYPE | Location Type | loct |
| LOC_TYPE_NAME | Location Type Description | loct_label |
| PHYSICAL_WH | Physical WH ID | phwh |
| PHYSICAL_WH_NAME | Physical WH Name | phwh_label |
| CHANNEL_ID | WH Channel ID | fflt |
| CHANNEL_NAME | WH Channel Name | fflt_label |
| STORE_CLASS | Store Class | |
| STORE_CLASS_DESCRIPTION | Store Class Description | |
| STORE_FORMAT | Store Format | |
| STORE_FORMAT_NAME | Store Format Name |
Currency Hierarchy - rms_curr.csv.ovr
The Currency conversion rate data file from RMF CS will be transformed to be loaded as a Currency Hierarchy file to load the unique currency codes.
The following table contains the list of column contents from the file. Only required columns for A&IP CS are filtered by the transform process.
| Field Name | Functional Name | A&IP CS Mapping |
|---|---|---|
| EFFECTIVE_DATE | Effective Date | |
| FROM_CURRENCY_CODE | From Currency | |
| TO_CURRENCY_CODE | To Currency | curc, curc_label |
| EXCHANGE_TYPE | Exchange Rate Type | |
| EXCHANGE_RATE | Exchange Rate |
Product Attribute Hierarchy - rms_uda.csv.dat, rms_brand.csv.dat,
rms_vendor.csv.dat, rms_diff.csv.dat
UDA, Suppliers (Vendor), Brand, and Diffs in RMF CS are treated as product attributes in Item Planning. RMF CS provides them as individual files in the same format; those will be merged and loaded as one product attribute file. UDA_VALUE (Product Attribute Values) are not unique across UDA_ID in RMF CS. While transforming and loading as a product attribute, UDA_ID position will be concatenated with UDA_VALUE using an underscore ("_").
The following table contains the list of column contents from the file.
| Field Name | Functional Name | A&IP CS Mapping |
|---|---|---|
| UDA_ID | UDA | patt |
| UDA_DESC | UDA Description | patt_label |
| UDA_VALUE | UDA Value | patv |
| UDA_VALUE_DESC | UDA Value Description | patv_labael |
The following data files are provided by RMF CS and need to be transformed to the A&IP CS format before loading them into IP Cloud Service. All RMF CS files are transformed first and loaded together using the single Load Task Load - RMS Interface Data.
Inventory Data File - rms_inv.csv.ovr
The following table contains the list of column contents from the file. Only required columns for A&IP CS are filtered by the transform process.
| Field Name | Functional Name | A&IP CS Mapping |
|---|---|---|
| EOW_DATE | End of week date | week |
| ITEM | Item ID | sku |
| LOCATION | Location ID | stor |
| LOC_TYPE | Location Type | |
| CLEAR_IND | Clearance flag | |
| REGULAR_INVENTORY_UNITS | Inventory Units | drtyeopu |
| REGULAR_INVENTORY_COST | Inventory Cost | drtyeopc |
| REGULAR_INVENTORY_RETAIL | Inventory Retail | drtyeopr |
| UNIT_COST | Unit Cost | drtyslsprcc |
| AV_COST | Average Cost | |
| UNIT_RETAIL | Unit Retail | drtyslsprcr |
Transaction Data File - rms_tran.csv.ovr
The following table contains the list of column contents from the file. Only required columns for A&IP CS are filtered by the transform process. RMF CS sends Net Sales in all regular, promotion, and clearance buckets. But A&IP FSL CS GA also needs Gross Sales. After loading, additional batch calculations, which run as part of RMF CS batch transforms, calculate those required measures. Also, RMF CS sends multiple type transaction details specific to receipts; batch calculations will calculate the effective receipts data.
| Field Name | Functional Name | A&IP CS Mapping |
|---|---|---|
| EOW_DATE | End of Week Date | week |
| ITEM | Item ID | sku |
| LOCATION | Location ID | stor |
| LOC_TYPE | Location Type | |
| CLEAR_IND | Clearance flag | |
| STANDARD_UOM | Standard UOM | |
| CURRENCY_CODE | Currency Code | |
| NET_SALES_REG_UNITS | Net Sales Units - Reg | drtynslsregu |
| NET_SALES_REG_COST | Net Sales Cost - Reg | drtynslsregc |
| NET_SALES_REG_RETAIL | Net Sales Retail - Reg | drtynslsregr |
| NET_SALES_PROMO_UNITS | Net Sales Units - Promo | drtynslsprou |
| NET_SALES_PROMO_COST | Net Sales Cost - Promo | drtynslsproc |
| NET_SALES_PROMO_RETAIL | Net Sales Retail - Promo | drtynslspror |
| NET_SALES_CLEAR_UNITS | Net Sales Units - Clear | drtynslsclru |
| NET_SALES_CLEAR_COST | Net Sales Cost - Clear | drtynslsclrc |
| NET_SALES_CLEAR_RETAIL | Net Sales Retail - Clear | drtynslsclrr |
| NET_SALES_REG_RETAIL_VAT_EXCL | Net Sales (VAT Exclusive) Retail - Reg | |
| NET_SALES_PROMO_RETAIL_VAT_EXCL | Net Sales (VAT Exclusive) Retail - Promo | |
| NET_SALES_CLR_RETAIL_VAT_EXCL | Net Sales (VAT Exclusive) Retail - Clear | |
| RETURNS_REG_UNITS | Returns Units - Reg | drtyrtnregu |
| RETURNS_REG_COST | Returns Cost - Reg | drtyrtnregc |
| RETURNS_REG_RETAIL | Returns Retail - Reg | drtyrtnregr |
| RETURNS_PROMO_UNITS | Returns Units - Promo | drtyrtnprou |
| RETURNS_PROMO_COST | Returns Cost - Promo | drtyrtnproc |
| RETURNS_PROMO_RETAIL | Returns Retail - Promo | drtyrtnpror |
| RETURNS_CLEAR_UNITS | Returns Units - Clear | drtyrtnclru |
| RETURNS_CLEAR_COST | Returns Cost - Clear | drtyrtnclrc |
| RETURNS_CLEAR_RETAIL | Returns Retail - Clear | drtyrtnclrr |
| REG_MARKDOWN_RETAIL | Regular Markdown | |
| PROMO_MARKDOWN_RETAIL_REG | Promotion Markdown (Regular) | |
| PROMO_MARKDOWN_RETAIL_CLEAR | Promotion Markdown (Clearance) | |
| CLEAR_MARKDOWN_RETAIL | Clearance Markdown | |
| WF_MARKDOWN_RETAIL | Franchise Markdown | |
| WF_MARKUP_RETAIL | Franchise Markup | |
| SHRINK_UNITS | Shrink Units | |
| SHRINK_COST | Shrink Cost | |
| SHRINK_RETAIL | Shrink Retail | |
| DEAL_INCOME_SALES | Deal Income Sales Based | |
| PO_RECEIPT_UNITS | PO Receipt Units | drtyporcptu |
| PO_RECEIPT_COST | PO Receipt Cost | drtyrpocptc |
| PO_RECEIPT_RETAIL | PO Receipt Retail | drtyporcptr |
| NON_SHRINK_ADJ_UNITS | Non-Shrink Adjustments Units | |
| NON_SHRINK_ADJ_COST | Non-Shrink Adjustments Cost | |
| NON_SHRINK_ADJ_RETAIL | Non-Shrink Adjustments Retail | |
| DEAL_INCOME_PURCHASES | Deal Income Purchases Based | |
| MARKUP | Markup | drtymkupr |
| MARKDOWN_CANCEL | Markdown Cancel | drtymkdcanr |
| INTERCOMPANY_MARKUP | Intercompany Markup | drtyicmkur |
| INTERCOMPANY_MARKDOWN | Intercompany Markdown | drtyicmkdr |
| RTV_UNITS | RTV Units | |
| RTV_COST | RTV Cost | |
| RTV_RETAIL | RTV Retail | |
| TSF_IN_UNITS | Transfer/Allocation Inbound Units | drtytraninu |
| TSF_IN_COST | Transfer/Allocation Inbound Cost | drtytraninc |
| TSF_IN_RETAIL | Transfer/Allocation Inbound Retail | drtytraninr |
| TSF_IN_UNITS_BOOK | Book Transfer/Allocation Inbound Units | drtytraninbu |
| TSF_IN_COST_BOOK | Book Transfer/Allocation Inbound Cost | drtytraninbc |
| TSF_IN_RETAIL_BOOK | Book Transfer/Allocation Inbound Retail | drtytraninbr |
| TSF_OUT_UNITS | Transfer/Allocation Outbound Units | drtytranoutu |
| TSF_OUT_COST | Transfer/Allocation Outbound Cost | drtytranoutc |
| TSF_OUT_RETAIL | Transfer/Allocation Outbound Retail | drtytranoutr |
| TSF_OUT_UNITS_BOOK | Book Transfer/Allocation Outbound Units | drtytranoutbu |
| TSF_OUT_COST_BOOK | Book Transfer/Allocation Outbound Cost | drtytranoutbc |
| TSF_OUT_RETAIL_BOOK | Book Transfer/Allocation Outbound Retail | drtytranoutbr |
| RECLASS_IN_UNITS | Reclass In Units | |
| RECLASS_IN_COST | Reclass In Cost | |
| RECLASS_IN_RETAIL | Reclass In Retail | |
| RECLASS_OUT_UNITS | Reclass Out Units | |
| RECLASS_OUT_COST | Reclass Out Cost | |
| RECLASS_OUT_RETAIL | Reclass Out Retail | |
| TSF_IN_UNITS_ICT | Intercompany Transfer/Allocation Inbound Units | drtytraniniu |
| TSF_IN_COST_ICT | Intercompany Transfer/Allocation Inbound Cost | drtytraninic |
| TSF_IN_RETAIL_ICT | Intercompany Transfer/Allocation Inbound Retail | drtytraninir |
| TSF_OUT_UNITS_ICT | Intercompany Transfer/Allocation Outbound Units | drtytranoutiu |
| TSF_OUT_COST_ICT | Intercompany Transfer/Allocation Outbound Cost | drtytranoutic |
| TSF_OUT_RETAIL_ICT | Intercompany Transfer/Allocation Outbound Retail | drtytranoutir |
| INTERCOMPANY_MARGIN | Intercompany Margin | |
| TSF_RECEIPT_UNITS | Transfer/Allocation Receipt Units | |
| TSF_RECEIPT_COST | Transfer/Allocation Receipt Cost | |
| TSF_RECEIPT_RETAIL | Transfer/Allocation Receipt Retail | |
| RTV_RESTOCK_FEE | RTV Restocking Fee | |
| FRANCHISE_SALES_UNITS | Franchise Sales Units | drtywfslsu |
| FRANCHISE_SALES_COST | Franchise Sales Cost | drtywfslsc |
| FRANCHISE_SALES_RETAIL | Franchise Sales Retail | drtywfslsr |
| FRANCHISE_RETURNS_UNITS | Franchise Returns Units | drtywfrtnu |
| FRANCHISE_RETURNS_COST | Franchise Returns Cost | drtywfrtnc |
| FRANCHISE_RETURNS_RETAIL | Franchise Returns Retail | drtywfrtnr |
| FRANCHISE_RESTOCK_FEE | Franchise Restocking Fee |
On Order Data File - rms_oo.csv.ovr
The following table contains the list of column contents from the file. Only required columns for A&IP CS are filtered by the transform process.
| Field Name | Functional Name | A&IP CS Mapping |
|---|---|---|
| EOW_DATE | End of week date | week |
| ITEM | Item ID | sku |
| LOCATION | Location ID | stor |
| LOC_TYPE | Location Type | |
| CLEAR_IND | Clearance flag | |
| ON_ORDER_UNITS | On Order Units | drtyoou |
| ON_ORDER_COST | On Order Cost | drtyooc |
| ON_ORDER_RETAIL | On Order Retail | drtyoor |
Currency Conversion Rate File - rms_curr.csv.ovr
The following table contains the list of column contents from the file. Only required columns for A&IP CS are filtered by the transform process.
| Field Name | Functional Name | A&IP CS Mapping |
|---|---|---|
| EFFECTIVE_DATE | Effective Date | day |
| FROM_CURRENCY_CODE | From Currency | |
| TO_CURRENCY_CODE | To Currency | curc |
| EXCHANGE_TYPE | Exchange Rate Type | |
| EXCHANGE_RATE | Exchange Rate | drtylcratex |
Location File - rms_store.csv.ovr
The following table contains the list of column contents from the file. Only required columns for A&IP CS are filtered by the transform process.
| Field Name | Functional Name | A&IP CS Mapping |
|---|---|---|
| STORE | Store ID | stor |
| STORE_NAME | Store Name | |
| DISTRICT | District ID | |
| STORE_CLOSE_DATE | Store Close Date | addvlocendd |
| STORE_OPEN_DATE | Store Open Date | |
| REMODEL_DATE | Remodel Date | addvlocrefd |
| STORE_CLASS | Store Class | |
| STORE_CLASS_DESCRIPTION | Store Class Description | |
| STORE_FORMAT | Store Format | |
| STORE_FORMAT_NAME | Store Format Name | |
| CURRENCY | Currency Code | |
| STORE_TYPE | Store Type | addvwfpoct |
| STOCKHOLDING_IND | Stockholding |
Item Attribute Mapping File - rms_prdattt.csv.ovr
The following table contains the list of column contents from the file. Only required columns for A&IP CS are filtered by the transform process. This file only contains Product Attribute mappings for UDA attributes. Item Attribute mappings for Brand, Supplier, and Diffs are derived and loaded from the RMF CS Product file.
| Field Name | Functional Name | A&IP CS Mapping |
|---|---|---|
| ITEM | Item ID | sku |
| UDA_ID | UDA ID | patt |
| UDA_DESC | UDA Description | |
| UDA_VALUE | UDA Value | drdvprdatt |
| UDA_VALUE_DESC | UDA Value Description | |
| FORECAST_IND | Forecastable Item |
The following table lists the measures that are loaded as part of the administration task Load - RMS Interface Data which runs as part of the Weekly Batch with RMS after transforming the RMF CS files. The table also provides the main RMF CS interface file from where measure data is transformed.
Table C-1 A&IP Cloud Service Load - RMS Interface Data Measures
| Measure Name | Measure Label | RMF CS Interface File | Transformed File |
|---|---|---|---|
|
drtynslsregr |
Ty Net Sales Reg R |
rms_tran.csv.ovr |
drtynsls.csv.ovr |
|
drtynslspror |
Ty Net Sales Promo R |
rms_tran.csv.ovr |
drtynsls.csv.ovr |
|
drtynslsclrr |
Ty Net Sales Clr R |
rms_tran.csv.ovr |
drtynsls.csv.ovr |
|
drtynslsregc |
Ty Net Sales Reg C |
rms_tran.csv.ovr |
drtynsls.csv.ovr |
|
drtynslsproc |
Ty Net Sales Promo C |
rms_tran.csv.ovr |
drtynsls.csv.ovr |
|
drtynslsclrc |
Ty Net Sales Clr C |
rms_tran.csv.ovr |
drtynsls.csv.ovr |
|
drtynslsregu |
Ty Net Sales Reg U |
rms_tran.csv.ovr |
drtynsls.csv.ovr |
|
drtynslsprou |
Ty Net Sales Promo U |
rms_tran.csv.ovr |
drtynsls.csv.ovr |
|
drtynslsclru |
Ty Net Sales Clr U |
rms_tran.csv.ovr |
drtynsls.csv.ovr |
|
drtyrtnregr |
Ty Returns Reg R |
rms_tran.csv.ovr |
drtyrtns.csv.ovr |
|
drtyrtnpror |
Ty Returns Promo R |
rms_tran.csv.ovr |
drtyrtns.csv.ovr |
|
drtyrtnclrr |
Ty Returns Clr R |
rms_tran.csv.ovr |
drtyrtns.csv.ovr |
|
drtyrtnregc |
Ty Returns Reg C |
rms_tran.csv.ovr |
drtyrtns.csv.ovr |
|
drtyrtnproc |
Ty Returns Promo C |
rms_tran.csv.ovr |
drtyrtns.csv.ovr |
|
drtyrtnclrc |
Ty Returns Clr C |
rms_tran.csv.ovr |
drtyrtns.csv.ovr |
|
drtyrtnregu |
Ty Returns Reg U |
rms_tran.csv.ovr |
drtyrtns.csv.ovr |
|
drtyrtnprou |
Ty Returns Promo U |
rms_tran.csv.ovr |
drtyrtns.csv.ovr |
|
drtyrtnclru |
Ty Returns Clr U |
rms_tran.csv.ovr |
drtyrtns.csv.ovr |
|
drtyaggwb |
TY Aggregate Elapsed Week |
rms_tran.csv.ovr |
drtyaggwb.csv.ovr |
|
drtyicmkur |
Ty Inter-Company Markup R |
rms_tran.csv.ovr |
drtyicmkur.csv.ovr |
|
drtyicmkdr |
Ty Inter-Company Markdown R |
rms_tran.csv.ovr |
drtyicmkdr.csv.ovr |
|
drtyeopc |
Ty EOP C |
rms_inv.csv.ovr |
drtyeop.csv.ovr |
|
drtyeopr |
Ty EOP R |
rms_inv.csv.ovr |
drtyeop.csv.ovr |
|
drtyeopu |
Ty EOP U |
rms_inv.csv.ovr |
drtyeop.csv.ovr |
|
drtyslsprcc |
TY Base Unit Price C |
rms_inv.csv.ovr |
drtyslsprc.csv.ovr |
|
drtyslsprcr |
TY Base Unit Price R |
rms_inv.csv.ovr |
drtyslsprc.csv.ovr |
|
drtyeopb |
TY EOP Loaded |
rms_inv.csv.ovr |
drtyeopb.csv.ovr |
|
drtyporcptu |
Ty PO Receipt U |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtyporcptc |
Ty PO Receipt C |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtyporcptr |
Ty PO Receipt R |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytraninu |
TY Transfers In U |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytraninc |
TY Transfers In C |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytraninr |
TY Transfers In R |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytraninbu |
TY Transfers In Book U |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytraninbc |
TY Transfers In Book C |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytraninbr |
TY Transfers In Book R |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytranoutu |
TY Transfers Out U |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytranoutc |
TY Transfers Out C |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytranoutr |
TY Transfers Out R |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytranoutbu |
TY Transfers Out Book U |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytranoutbc |
TY Transfers Out Book C |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytranoutbr |
TY Transfers Out Book R |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytraniniu |
TY Transfers In ICT U |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytraninic |
TY Transfers In ICT C |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytraninir |
TY Transfers In ICT R |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytranoutiu |
TY Transfers Out ICT U |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytranoutic |
TY Transfers Out ICT C |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtytranoutir |
TY Transfers Out ICT R |
rms_tran.csv.ovr |
drtyrcpts.csv.ovr |
|
drtywfslsu |
TY W/F Sales U |
rms_tran.csv.ovr |
drtywfsls.csv.ovr |
|
drtywfslsc |
TY W/F Sales C |
rms_tran.csv.ovr |
drtywfsls.csv.ovr |
|
drtywfslsr |
TY W/F Sales R |
rms_tran.csv.ovr |
drtywfsls.csv.ovr |
|
drtywfrtnu |
TY W/F Returns U |
rms_tran.csv.ovr |
drtywfsls.csv.ovr |
|
drtywfrtnc |
TY W/F Returns C |
rms_tran.csv.ovr |
drtywfsls.csv.ovr |
|
drtywfrtnr |
TY W/F Returns R |
rms_tran.csv.ovr |
drtywfsls.csv.ovr |
|
drtyoou |
Ty On Order U |
rms_oo.csv.ovr |
drtyoo.csv.rpl |
|
drtyoor |
Ty On Order R |
rms_oo.csv.ovr |
drtyoo.csv.rpl |
|
drtyooc |
Ty On Order C |
rms_oo.csv.ovr |
drtyoo.csv.rpl |
|
drtylcratex |
Ty Local Currency Rate |
rms_curr.csv.ovr |
drtylcratex.csv.ovr |
|
addvlocendd |
Location Close Dt |
rms_store.csv.ovr |
addvlocendd.csv.ovr |
|
addvlocrefd |
Location Refurbish Dt |
rms_store.csv.ovr |
addvlocrefd.csv.ovr |
|
drtypclsst |
TY RMS Display Class Id |
rms_prod.csv.dat |
|
|
drtypsclst |
TY RMS Display Sub-Class Id |
rms_prod.csv.dat |
|
|
drdvprdattt |
Product Attribute - Item Level |
rms_uda.csv.dat, |
drdvprdattt.csv.ovr |
|
drdvppatvt |
RMS Product Attribute Value |
rms_uda.csv.dat, |
drdvppatvt.csv.ovr |
|
drtyudab |
TY RMS UDA |
rms_uda.csv.dat |
drtyudab.csv.ovr |
In RMF CS, warehouses hold inventory, receipts, and on-order data that are not mapped to any specific channels. In A&IP CS, plans are only created at the A&IP CS Channel level. In order to get the full picture of inventory for a channel, each warehouse location needs to be mapped to a channel within A&IP CS using the Warehouse Mapping workbook template in Location Setup or the mapping needs to be loaded to the measure addvchwhmapt.
After the mapping data is set, the weekly batch process will transform the loaded inventory, on-order, and receipt data for those warehouses to assigned channels. This can also be done by running the batch Online Administration Tool task Transform RMS Warehouse Data. The batch process will spread the Warehouse data at the channel level to the store level using the Warehouse to Store Spread Method which has options to use Location Plan, Location Sales, Actuals, and Actual Sales with the default option using Location Plan interfaced from MFP. The customer can change this option in the Batch Setup view in the Admin workbooks.
New Placeholder Items (Style/Color or Styles) created in A&IP can be integrated with RMF CS. It involves multiple levels of process which are detailed below:
First, the RMF CS Server should be connected with A&IP CS during deployment, after mapping the dimensions (style/color, style) to item in RMF CS. New Placeholder items created in A&IP will directly use the reserved item numbers from RMF CS. For more details, refer to the RPASCE-RMS Integration for Item Management - Slow Item Build section in the Oracle Retail Predictive Application Server Cloud Edition Administration Guide.
The customer can then create new placeholder items within A&IP and assign attributes to them. RMF CS does not contain style/color as a separate level, so an attribute should be selected as RMF CS Color attribute in the Product Setup view in Planning Administration. All new style/colors created should be assigned with a unique color attribute. The customer should then select the style/color ready for Export to RMF CS. The process only allows for creating new placeholder items and assigning initial attributes. Any further updates/maintenance of the item or RMF CS specific item attributes should be managed in the RMF CS side.
The customer can then schedule the Export New Items batch task to the RMF CS task which will export all items marked for Export to RMF CS. During this process, it also renames the style/color positions created as style concatenated with a color attribute as it will be identified in the RMF CS product hierarchy file. It then creates an XML file in the format needed by the RMF CS Item Induction process.
The RMF CS Item Induction process should then make use of that exported XML file to load the new items, once it is approved in the RMF CS side. The same items will be coming in the product hierarchy file as regular items. Since it will use the same position names for Item and Style/Color, the standard hierarchy load process in the A&IP CS side will formalize the informal placeholder items.
The following sets of Online Administration Tools tasks are pre-configured in Configured Batch Tasks to support RMF CS integration. For more details about running the tasks, see the Oracle Retail Assortment & Item Planning for Fashion/Softlines Cloud Service Administration Guide.
Run Batch Task Group > Weekly Batch
If Enable RMF CS Integration is set to true, the existing Weekly Batch task will run additional tasks to process the RMF CS files. It also runs the transformation of RMF CS Warehouse data as part of the weekly batch.
Run Batch Task Group > Transform RMS Files
This task only transforms all hierarchy and data files to the A&IP CS required format and copies the hierarchy files to the SFTP output as rms_hier.zip. It will not load those files.
Typically, this can be used during initial installation to transform the initial set of RMF CS files and rebuild the domain with the initial set of RMF CS hierarchy files.
Run Batch Task Group > Transform RMS Warehouse Data
Whenever there is any change in the warehouse mapping, users can schedule this task to transform the RMF CS Warehouse data to channels for inventory, order, and receipts. This task also gets called as part of the Weekly Batch with RMS.
Run Batch Task Group > Set RMS Dimension Mapping
RMF CS can be linked with the A&IP domain in real time to get the reserved item numbers for new placeholder items created. In order to do that, connections between the RMF CS servers and RPAS server needs to be set up during installation time. For more details about those setups, see the Oracle Retail Predictive Application Server Cloud Edition Administration Guide. Once those are set, running this task will map the sku (Item) and skup (style/color) dimensions to Item in RMF CS. Once this mapping is done, any new place holder sku or skup created will use the reserved RMF CS item numbers directly from RMF CS.
Run Batch Task Group > Export New Items to RMS
This task exports the newly created items with the assigned attributes information to RMF CS and formats it into following XML format as style_color_item_data.dat in the Cloud Share Location that can be readily used by RMF CS for Item Induction. Only New Items ready to be exported will be sent to RMF CS as new items.
Sample XML file created:
<STYLE_COLOR_ITEM_DATA>
<table name="item_master">
<table_row value="1">
<action>NEW</action>
<item>9000000001</item>
<item_desc>KL_DiffAggTest</item_desc>
<dept>3041</dept>
<class>1</class>
<subclass>2</subclass>
<item_parent></item_parent>
<item_level>1</item_level>
<item_aggregate_ind>Y</item_aggregate_ind>
<diff_1></diff_1>
<diff_1_aggregate_ind>Y</diff_1_aggregate_ind>
<brand_name></brand_name>
</table_row>
<table_row value="2">
<action>NEW</action>
<item>9000000002</item>
<item_desc>KL_DiffAggTest:Navy:Small</item_desc>
<dept>3041</dept>
<class>1</class>
<subclass>2</subclass>
<item_parent>9000000001</item_parent>
<item_level>2</item_level>
<item_aggregate_ind>N</item_aggregate_ind>
<diff_1>NAVY</diff_1>
<diff_1_aggregate_ind>N</diff_1_aggregate_ind>
<brand_name></brand_name>
</table_row>
</table>
<table name="item_supplier">
<table_row value="1">
<action>NEW</action>
<item>9000000001</item>
<supplier>2900</supplier>
</table_row>
</table>
<table name="uda_item_lov">
<table_row value="1">
<action>NEW</action>
<item>9000000001</item>
<uda_id>s</uda_id>
<uda_value>LARGE</uda_value>
</table_row>
<table_row value="2">
<action>NEW</action>
<item>9000000002</item>
<uda_id>c</uda_id>
<uda_value>NAVY</uda_value>
</table_row>
</table>
</STYLE_COLOR_ITEM_DATA>
If RMF CS needs to be integrated as part of an initial implementation, then the following needs to be done in this order:
After the Assortment & Item Planning Cloud Service environment is provisioned using the Self-Service Administration Task in the bootstrap domain, build the default solution with GA data files.
Upload the RMF CS Hierarchy and data files for the initial conversion data.
Run the Transform RMS Files batch task to transform hierarchy files to A&IP CS format. Those will be copied to SFTP output.
Upload the generated hierarchy files and also additional hierarchy files needed for A&IP CS, that are not provided by RMF CS (use the GA data set as a reference to create additional hierarchy files) into the SFTP server, at the
INCOMING_FTP_PATH/input subdirectory.
Using the Self-Service Administration Task in the bootstrap domain, rebuild the domain with the required plug-in options for A&IP CS and without selecting "Use GA Data." The above process will rebuild the domain using the initial set of RMF CS hierarchy files.
After building the domain, set the Enable RMF CS Integration flag in the Plan Admin workbook, then re-send all the hierarchy and data files from RMF CS and use the regular "Weekly Batch" to process the hierarchy and data files.
