2 Implementation Considerations
The following information must be considered before configuring MFP Cloud Service:
Configuration Considerations
MFP Cloud Service provides two solution options, Retail and Cost, method of implementation. The default implementation uses the Retail Solution. Both solution options use a similar solution template, but mostly differ in the calculation of Key Metrics specific to the planning. For details on the calculations of Key Planning Metrics to help decide which solution option fits for the customer, see the Oracle Retail Merchandise Financial Planning Cost Cloud Service User Guide and Oracle Retail Merchandise Financial Planning Retail Cloud Service User Guide.
The customer has the option to change the solution type by patching the configuration. Each solution option can be chosen with or without the Whole Sale Franchise and Local Currency options using automation plug-ins. For more information about generating configurations for different solutions and plug-in options using the Configuration Tools, see the Oracle Retail Merchandise Financial Planning Cloud Service Starter Kit Guide.
During implementation, the user has option to extend the application configuration using Extensibility guidelines. For more details about the extensibility of the configuration, see the Oracle Retail Analytics and Planning Implementation Guide.
Whole Sale Franchise Option
Retailers having whole sale franchise capabilities and wanting to plan specific metrics to support those functions can choose the Whole Sale Franchise option. Selecting a provision with this option provides additional tasks in the task flow, worksheets, and measures to support this process. For more information about these tasks, see the Oracle Retail Merchandise Financial Planning Cost Cloud Service User Guide or Oracle Retail Merchandise Financial Planning Retail Cloud Service User Guide. If a provision containing this option is chosen, the retailer must also provide additional data files to support this process. For more details, see Data Files.
Local Currency Option
Retailers who want to plan in both primary currency as well as local currency can chose provisions containing this option. Selecting provisions with this option provides additional tasks, worksheets, and measures to support this process. The retailer must set up the Local Currency conversion details in the administration workbooks specific to this option. For more information details, see the Oracle Retail Merchandise Financial Planning Cost Cloud Service User Guide or Oracle Retail Merchandise Financial Planning Retail Cloud Service User Guide.
Data
MFP Cloud Service needs the following sets of data from customers, which are broadly classified as hierarchy files and data files. The data is described in the following sections:
Figure 2-1 MFP Cloud Service Data Interfaces
Hierarchy Files
This is the foundation data to build any RPASCE solution. MFP Cloud Service requires the following three foundation hierarchy files: Calendar, Product, and Location. In addition, it also requires the Local Currency VAT (Value Added Tax) and Location Attributes hierarchies. To load the Hierarchy files during the batch process, the customer can upload their hierarchy files as individual files into Object Storage under the input directory or zip them up as hiers.zip and upload that zip file to the same input directory in Object Storage.
Customers can get all the hierarchy files data using RAP integration. Customers need to upload only the hierarchy files data that is not coming through RAP integration. These are specified under the Notes sections of the respective hierarchies.
Note:
In order to implement Planning cloud services on Retail Analytics and Planning (RAP), the customer should ensure their foundation data, that is, Product and Organization hierarchies align with Oracle Retail Merchandising Foundation Cloud Service (RMFCS) so that the foundation and transactional data can be used by all services in RAP. They can have more alternate dimensions than available in RMFCS if needed for their Planning Cloud Services.
Customers can use the flex fields available in RAP Foundation files to interface this data. Also, if multiple Planning cloud services such as MFPCS, APCS, and IPOCS-Demand Forecasting are residing in the same PDS, then hierarchies which are common across them should have the same dimension names so they can share the same data interfaced from RAP. However, additional non-shared dimensions can be present in each service, but shared dimensions should have the same name.
Note:
In all the hierarchy files, the hierarchy type User Defined Alternates (UDA) and data for those alternates do not need to be present in the hierarchy files. Administration users can directly set values for those alternates directly in the application. For more information, see the Oracle Retail Predictive Application Server Cloud Edition Administration Guide. If a retailer also provides these details in the hierarchy files, data for all user alternates for that hierarchy must be present in that file with header information.
Note:
Hierarchy files should always contain header information and columns in any order but the file name must be in the format <hier>.hdr.csv.dat.
For information on the hierarchy files, see the following sections:
Calendar Hierarchy File
File name: clnd.hdr.csv.dat
File format: comma-separated values file
The following table describes the fields in this file.
| Name | Label | Hierarchy Type | Parent |
|---|---|---|---|
|
DAY |
Day |
Main |
None |
|
WEEK |
Week |
Main |
DAY |
|
MNTH |
Month |
Main |
WEEK |
|
QRTR |
Quarter |
Main |
MNTH |
|
HALF |
Half |
Main |
QRTR |
|
YEAR |
Year |
Main |
HALF |
|
HLDY |
Holiday |
UDA |
WEEK |
|
EVNT |
Event |
UDA |
WEEK |
|
WOYR |
Week of Year |
Alternate |
WEEK |
|
STDB |
STD/BTA |
UDA |
WEEK |
Example:
day,day_label,week,week_label,mnth,mnth_label,qrtr,qrtr_label,half,half_label,year,year_label,hldy,hldy_label,evnt,evnt_label,woyr,woyr_label,stdb,stdb_label 20170129,1/29/2017,w01_2017,2/4/2017,m01_2017,Feb FY2017,q01_2017,Quarter1 FY2017,h1_2017,Half1 FY2017,a2017,FY2017,0,None,0,None,1,Week 01,0,0 20170130,1/30/2017,w01_2017,2/4/2017,m01_2017,Feb FY2017,q01_2017,Quarter1 FY2017,h1_2017,Half1 FY2017,a2017,FY2017,0,None,0,None,1,Week 01,0,0 20170131,1/31/2017,w01_2017,2/4/2017,m01_2017,Feb FY2017,q01_2017,Quarter1 FY2017,h1_2017,Half1 FY2017,a2017,FY2017,0,None,0,None,1,Week 01,0,0 20170201,2/1/2017,w01_2017,2/4/2017,m01_2017,Feb FY2017,q01_2017,Quarter1 FY2017,h1_2017,Half1 FY2017,a2017,FY2017,0,None,0,None,1,Week 01,0,0
Notes:
Though RPASCE supports a string for position IDs, for calendar position week, it is preferred to use the date format YYYYMMDD. If the customer uses RAP integration to get the data, the day and week position IDs at which the data needs to be stored are in YYYYMMDD format.
Product Hierarchy File
File name: prod.hdr.csv.dat
File format: comma-separated values file
The following table describes the fields in this file.
| Name | Label | Hierarchy Type | Parent |
|---|---|---|---|
|
SKU |
Item |
Main |
None |
|
SCLS |
Subclass |
Main |
SKUP |
|
CLSS |
Class |
Main |
SCLS |
|
DEPT |
Department |
Main |
CLSS |
|
PGRP |
Group |
Main |
DEPT |
|
DVSN |
Division |
Main |
PGRP |
|
CMPP |
Company |
Main |
DVSN |
|
SCL1 |
Subclass Group 1 |
UDA |
SCLS |
|
SCL2 |
Subclass Group 2 |
UDA |
SCLS |
|
CLSG |
Class Group |
UDA |
CLSS |
|
CONS |
Consignment/Non-Cons |
UDA |
SCLS |
Example:
SKU,SKU_LABEL,SCLS,SCLS_LABEL,SCL1,SCL1_LABEL,SCL2,SCL2_LABEL,CLSS,CLSS_LABEL,CLSG,CLSG_LABEL,DEPT,DEPT_LABEL,PGRP,PGRP_LABEL,DVSN,DVSN_LABEL,CMPP,CMPP_LABEL,CONS,CONS_LABEL 22222222,22222222 Ground De-Caffeinated Can,100000,100000 Ground,110000,110000 Brewed,120000,120000 Bag-Jar-Can,10000,10000 Coffee,11001,11001 Coffee,1000,1000 Shelf Stable Beverages,100,100 Shelf Stable Grocery,10,10 Grocery,1,1 Acme,1,Consignment 44444444,44444444 Ground Regular - Caffeinated Can,100000,100000 Ground,110000,110000 Brewed,120000,120000 Bag-Jar-Can,10000,10000 Coffee,11001,11001 Coffee,1000,1000 Shelf Stable Beverages,100,100 Shelf Stable Grocery,10,10 Grocery,1,1 Acme,1,Consignment 11111111,11111111 Ground De-Caffeinated Bag,100000,100000 Ground,110000,110000 Brewed,120000,120000 Bag-Jar-Can,10000,10000 Coffee,11001,11001 Coffee,1000,1000 Shelf Stable Beverages,100,100 Shelf Stable Grocery,10,10 Grocery,1,1 Acme,1,Consignment 33333333,33333333 Ground Regular - Caffeinated Bag,100000,100000 Ground,110000,110000 Brewed,120000,120000 Bag-Jar-Can,10000,10000 Coffee,11001,11001 Coffee,1000,1000 Shelf Stable Beverages,100,100 Shelf Stable Grocery,10,10 Grocery,1,1 Acme,1,Consignment
Notes:
In MFP Cloud Service, the lowest level of planning is done at the Subclass level. Partitioning of the Planning Data Schema should be done above the Subclass level. The customer should have balanced data at the partition level to have better performance. The MFP GA is partitioned by default at the department level. MFPCS also needs aggregated actual data only at the Subclass level. The base MFP configuration is defined to load actual data only at the Item level. Data will be visible within the application only at the Subclass level, but the lowest hierarchy level is still defined at the Item Level to support integration in RAP.
Location Hierarchy File
File name: loc.hdr.csv.dat
File format: comma-separated values file
The following table describes the fields in this file.
| Name | Label | Hierarchy Type | Parent |
|---|---|---|---|
|
STOR |
Location |
Main |
None |
|
DSTR |
District |
Main |
STOR |
|
REGN |
Region |
Main |
DSTR |
|
CHNL |
Area |
Main |
REGN |
|
CHAN |
Chain |
Main |
CHNL |
|
COMP |
Company |
Main |
CHAN |
|
LOCT |
Location Type |
Alternate |
STOR |
|
PHWH |
Physical Warehouse |
Alternate |
STOR |
|
FFLT |
Fulfillment Tupe |
Alternate |
STOR |
|
CHNG |
Chain Group |
UDA |
CHAN |
|
RGNG |
Region Group |
UDA |
REGN |
|
DSTG |
District Group |
UDA |
DSTR |
|
STRC |
Location Cluster |
Alternate |
STOR |
|
CHNC |
Channel |
Alternate |
STRC |
|
CCTY |
Channel Country |
Alternate |
CHNC |
Note:
The Planning Location Hierarchy is aligned with the Merchandising Organization Hierarchy for RAP integration, so Region aggregates to Area as in the Merchandising Hierarchy. Channel is an attribute in RMFCS and is not part of the Organization Hierarchy. RMFCS integration to RAP will send the Planning Channel and Planning Country and that will be mapped to the Channel (CHNC) and Country (CCTY) dimension. Merch Plans and Merch Targets will be created at the Channel (CHNC) level.
Note:
The STRC (Location Cluster) dimension is not currently used in the MFP GA, but it is added to align with the Assortment Planning GA and also to allow for extensibility of MFP or for the non-template customer to enhance to include Location clustering. During hierarchy load, it can be mapped to load with the same STOR dimensions.
Note:
If the customer has Warehouses holding inventory and receipts data, the Virtual Warehouse locations for each Channel can be loaded as locations with Location type as ‘W’. The batch process allows splitting of Warehouse Inventory to locations to include in the Location Inventory for Location Planning.
Example:
STOR,STOR_LABEL,DSTR,DSTR_LABEL,REGN,REGN_LABEL,CHNL,CHNL_LABEL,CHAN,CHAN_LABEL,COMP,COMP_LABEL,LOCT,LOCT_LABEL,PHWH,PHWH_LABEL,FFLT,FFLT_LABEL,STRC,STRC_LABEL,CHNC,CHNC_LABEL,CCTY,CCTY_LABEL,DSTG,DSTG_LABEL,RGNG,RGNG_LABEL,CHNG,CHNG_LABEL 1000,1000 Charlotte,1070,North Carolina,170,Mid-Atlantic,1,Brick & Mortar,1,US,1,Retailer Ltd,1,Store,WH-1,Warehouse - US,1,Brick & Mortar,1000,1000 Charlotte,1,Brick & Mortar,1,USA,170,Mid-Atlantic,1,North,1,North America 1001,1001 Atlanta,1023,Georgia,400,South Atlantic,1,Brick & Mortar,1,US,1,Retailer Ltd,2,Kiosk,WH-1,Warehouse - US,1,Brick & Mortar,1001,1001 Atlanta,1,Brick & Mortar,1,USA,400,South Atlantic,2,South,1,North America 1002,1002 Dallas,1104,Texas,230,Gulf States,1,Brick & Mortar,1,US,1,Retailer Ltd,1,Store,WH-1,Warehouse - US,1,Brick & Mortar,1002,1002 Dallas,1,Brick & Mortar,1,USA,230,Gulf States,2,South,1,North America 1003,1003 Boston,1051,Massachusetts,200,New England,1,Brick & Mortar,1,US,1,Retailer Ltd,1,Store,WH-1,Warehouse - US,1,Brick & Mortar,1003,1003 Boston,1,Brick & Mortar,1,USA,200,New England,1,North,1,North America 1004,1004 New York,1066,New York,200,New England,1,Brick & Mortar,1,US,1,Retailer Ltd,1,Store,WH-1,Warehouse - US,1,Brick & Mortar,1004,1004 New York,1,Brick & Mortar,1,USA,200,New England,1,North,1,North America 1005,1005 Philadelphia,1083,Pennsylvania,170,Mid-Atlantic,1,Brick & Mortar,1,US,1,Retailer Ltd,1,Store,WH-1,Warehouse - US,1,Brick & Mortar,1005,1005 Philadelphia,1,Brick & Mortar,1,USA,170,Mid-Atlantic,1,North,1,North America
Currency Hierarchy File
The Currency Hierarchy file is used to define unique currencies to be used in the application. The retailer can customize this hierarchy during implementation and can use the GA dataset hierarchy as a reference. If the Local Currency provision option is enabled during implementation, this hierarchy is loaded, and currency conversion rates are set in the Local Currency Setup workbook. Users can review the plan data in more than one currency.
File name: curh.hdr.csv.dat
File format: comma-separated values file
The following table describes the fields in this file.
| Name | Description |
|---|---|
|
Currency |
This is the unique currency. The plan data can be converted when the Local Currency provision option is enabled. |
Example:
curr,curr_label USD,USD EUR,EUR GBP,GBP BRL,BRL JPY,JPY DKK,DKK KRW,KRW
VAT Hierarchy File
The VAT hierarchy file is used to define unique Value Added Tax to be used in the application. The retailer can customize this hierarchy during implementation and can use the GA dataset hierarchy as a reference. Users can set more than one VAT group and VAT rates for them in the administration workbooks. Then, users have the options to choose any one VAT group to use within the solution.
Notes:
This hierarchy data is not coming as part of RAP integration, so the customer needs to explicitly provide this file with at least one valid data.
File name: vath.hdr.csv.dat
File format: comma-separated values file
The following table describes the fields in this file.
| Name | Description |
|---|---|
|
VAT Group |
This is the unique VAT group used to define different VAT rates that can be used within the application. |
Example:
vatb,vatb_label "VAT00","Zero Rate" "VAT05","Reduced Rate" "VAT20","Standard Rate"
Location Attributes Hierarchy File
The Location Attributes hierarchy represents attributes associated with locations. These attributes are used to group locations to plan in the Location Planning templates.
This hierarchy is intended to capture all location attributes for all locations. The attributes are then assigned to individual locations. This assignment is used when processing the dynamic rollups in the location planning templates.
| Name | Label | Hierarchy Type | Aggs |
|---|---|---|---|
|
SATV |
Loc Attribute Value |
Main |
None |
|
SATT |
Loc Attribute |
Main |
SATV |
File name: satr.hdr.csv.dat
File format: comma-separated values file
The following table describes the fields in this file.
| Name | Description |
|---|---|
|
Loc Attribute Value |
The various values that an attribute might have. For example, the climate attribute might take the values cold, hot, or humid. |
|
Loc Attribute |
The name of a location attribute, such as climate, store volume, and so on. |
Notes:
This hierarchy data is not coming as part of RAP integration, so the customer needs to explicitly provide this file with at least one valid data.
Example:
satv,satv_label,satt,satt_label grade,Sales Perf Grp,grade,Sales Perf Grp space,Space,space,Space sfmt1,Downtown,sfmt,Store Format sfmt2,Strip Mall,sfmt,Store Format sfmt3,Standalone,sfmt,Store Format clmt1,Marine,clmt,Climate clmt2,Cold,clmt,Climate clmt3,Very Cold,clmt,Climate clmt4,Hot Dry,clmt,Climate clmt5,Mixed Dry,clmt,Climate clmt6,Mixed Humid,clmt,Climate clmt7,Hot Humid,clmt,Climate clmt8,Mediterranean,clmt,Climate clmt9,N/A,clmt,Climate
Level Hierarchy File
The Level hierarchy is an internal application-specific hierarchy to define different levels of the Dynamic Hierarchy Rollup for Product and Location using its attributes in various workbook templates. It is hard coded to have three levels in the MFPCS solution. By default, this file will be included as part of the GA deploy.
File name: lvlh.hdr.csv.dat
File format: comma-separated values file
The following table describes the field in this file.
| Name | Description |
|---|---|
|
Level |
Attribute Roll-Up Level. |
Example:
lvld,lvld_label lvl1,Level 1 lvl2,Level 2 lvl3,Level 3
Custom Messages Hierarchy File
MFP Cloud Service also has an additional internal hierarchy for custom messages used in the application called Custom Messages Hierarchy (CMSH). Custom messages used in the application are pre-configured in that hierarchy file and, unless a retailer needs different custom messages, that file does not need to be changed. By default, this file will be included as part of the GA deploy.
File name: cmsh.hdr.csv.dat
File format: comma-separated values file
The following table describes the fields in this file.
| Name | Label | Hierarchy Type | Parent |
|---|---|---|---|
|
CMSD |
Messages |
Main |
None |
Example:
"CMS01","Seeding completed successfully!"
"CMS02","Seeding not successful. Please select Wp Seed Source."
Data Files
The following tables describe the data files (measures) needed, load intersection, data type, file name, required/optional, and expected data source details. In the Data Source column, RI means any Data Warehouse or equivalent/RMS and data readily available from RAP integration, Internal means any retailer internal system or the data using data files, and Admin means either data can be directly set up by an administration user or can be loaded as files.
Customers need to provide and upload only data files that are not available through RAP integration.
Note:
The selected value for each file in the Required/Optional column in the following tables is specific to the Provision option chosen. If the Wholesale Franchise Provision option is chosen for implementation, all wholesale franchise specific measures are required.
MFP Cloud Service Input Measure List
The following table lists the input data for an MFP Cloud Service implementation:
Table 2-1 MFP Cloud Service Input Measure List
| Measure Name | Measure Label | Load Intersection | Data Type | File Name | Solution Type | Required or Optional? | Data Source |
|---|---|---|---|---|---|---|---|
|
drtyeop1c |
Ty EOP Reg+Promo C |
week/sku/stor |
real |
eopx.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyeop1r |
Ty EOP Reg+Promo R |
week/sku/stor |
real |
eopx.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyeop1u |
Ty EOP Reg+Promo U |
week/sku/stor |
real |
eopx.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyeop2c |
Ty EOP Clr C |
week/sku/stor |
real |
eopx.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyeop2r |
Ty EOP Clr R |
week/sku/stor |
real |
eopx.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyeop2u |
Ty EOP Clr U |
week/sku/stor |
real |
eopx.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyrinva1c |
Ty RMF Shrink Inventory Adjust C |
week/sku/stor |
real |
inva.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyrinva1r |
Ty RMF Shrink Inventory Adjust R |
week/sku/stor |
real |
inva.csv.ovr |
Retail |
required |
RI |
|
drtyrinva1u |
Ty RMF Shrink Inventory Adjust U |
week/sku/stor |
real |
inva.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyrinva2c |
Ty RMF Non-Shrink Inventory Adjust C |
week/sku/stor |
real |
inva.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyrinva2r |
Ty RMF Non-Shrink Inventory Adjust R |
week/sku/stor |
real |
inva.csv.ovr |
Retail |
required |
RI |
|
drtyrinva2u |
Ty RMF Non-Shrink Inventory Adjust U |
week/sku/stor |
real |
inva.csv.ovr |
Retail/Cost |
required |
RI |
|
drtymkdcanr |
Ty Markdown Cancel R |
week/sku/stor |
real |
mkd.csv.ovr |
Retail/Cost |
required |
RI |
|
drtymkdclrr |
Ty Markdown Clear R |
week/sku/stor |
real |
mkd.csv.ovr |
Retail/Cost |
required |
RI |
|
drtymkdpclr |
Ty Markdown Promo Clear R |
week/sku/stor |
real |
mkd.csv.ovr |
Retail/Cost |
required |
RI |
|
drtymkdpror |
Ty Markdown Promo R |
week/sku/stor |
real |
mkd.csv.ovr |
Retail/Cost |
required |
RI |
|
drtymkdregr |
Ty Markdown Reg R |
week/sku/stor |
real |
mkd.csv.ovr |
Retail/Cost |
required |
RI |
|
drtymkupr |
Ty Markup R |
week/sku/stor |
real |
mkd.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyicmkdr |
Ty Inter-Company Markdown R |
week/sku/stor |
real |
mkd.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtyicmkur |
Ty Inter-CompanyMarkup R |
week/sku/stor |
real |
mkd.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtywfmkdr |
Ty W/F Markdown R |
week/sku/stor |
real |
wfms.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtywfmkur |
Ty W/F Markup R |
week/sku/stor |
real |
wfms.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtywfslsu |
Ty W/F Sales U |
week/sku/stor |
real |
wfms.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtywfslsc |
Ty W/F Sales C |
week/sku/stor |
real |
wfms.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtywfslsr |
Ty W/F Sales R |
week/sku/stor |
real |
wfms.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtywfrtnu |
Ty W/F Returns U |
week/sku/stor |
real |
wfms.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtywfrtnc |
Ty W/F Returns C |
week/sku/stor |
real |
wfms.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtywfrtnr |
Ty W/F Returns R |
week/sku/stor |
real |
wfms.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtynslsclrc |
Ty Net Sales Clear C |
week/sku/stor |
real |
nsls.csv.ovr |
Cost |
required |
RI |
|
drtynslsclrr |
Ty Net Sales Clear R |
week/sku/stor |
real |
nsls.csv.ovr |
Retail/Cost |
required |
RI |
|
drtynslsclru |
Ty Net Sales Clear U |
week/sku/stor |
real |
nsls.csv.ovr |
Retail/Cost |
required |
RI |
|
drtynslsproc |
Ty Net Sales Promo C |
week/sku/stor |
real |
nsls.csv.ovr |
Cost |
required |
RI |
|
drtynslspror |
Ty Net Sales Promo R |
week/sku/stor |
real |
nsls.csv.ovr |
Retail/Cost |
required |
RI |
|
drtynslsprou |
Ty Net Sales Promo U |
week/sku/stor |
real |
nsls.csv.ovr |
Retail/Cost |
required |
RI |
|
drtynslsregc |
Ty Net Sales Reg C |
week/sku/stor |
real |
nsls.csv.ovr |
Cost |
required |
RI |
|
drtynslsregr |
Ty Net Sales Reg R |
week/sku/stor |
real |
nsls.csv.ovr |
Retail/Cost |
required |
RI |
|
drtynslsregu |
Ty Net Sales Reg U |
week/sku/stor |
real |
nsls.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyrtnclrc |
Ty Returns Clear C |
week/sku/stor |
real |
rtn.csv.ovr |
Cost |
required |
RI |
|
drtyrtnclrr |
Ty Returns Clear R |
week/sku/stor |
real |
rtn.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyrtnclru |
Ty Returns Clear U |
week/sku/stor |
real |
rtn.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyrtnproc |
Ty Returns Promo C |
week/sku/stor |
real |
rtn.csv.ovr |
Cost |
required |
RI |
|
drtyrtnpror |
Ty Returns Promo R |
week/sku/stor |
real |
rtn.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyrtnprou |
Ty Returns Promo U |
week/sku/stor |
real |
rtn.csv.ovr |
Retail/Cost |
required/optional |
RI |
|
drtyrtnregc |
Ty Returns Reg C |
week/sku/stor |
real |
rtn.csv.ovr |
Cost |
required |
RI |
|
drtyrtnregr |
Ty Returns Reg R |
week/sku/stor |
real |
rtn.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyrtnregu |
Ty Returns Reg U |
week/sku/stor |
real |
rtn.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyooc |
Ty On Order C |
week/sku/stor |
real |
oo.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyoor |
Ty On Order R |
week/sku/stor |
real |
oo.csv.ovr |
Retail |
required |
RI |
|
drtyoou |
Ty On Order U |
week/sku/stor |
real |
oo.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyporcptc |
Ty PO Receipt C |
week/sku/stor |
real |
rcpt.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyporcptr |
Ty PO Receipt R |
week/sku/stor |
real |
rcpt.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyporcptu |
Ty PO Receipt U |
week/sku/stor |
real |
rcpt.csv.ovr |
Retail/Cost |
required |
RI |
|
drtytraninbc |
Ty Transfers In Book C |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytraninbr |
Ty Transfers In Book R |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytraninbu |
Ty Transfers In Book U |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytraninic |
Ty Transfers In ICT C |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytraninir |
Ty Transfers In ICT R |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytraniniu |
Ty Transfers In ICT U |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytraninr |
Ty Transfers In R |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytraninc |
Ty Transfers In C |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
required |
RI |
|
drtytraninu |
Ty Transfers In U |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
required |
RI |
|
drtytranoutbc |
Ty Transfers Out Book C |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytranoutbr |
Ty Transfers Out Book R |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytranoutbu |
Ty Transfers Out Book U |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytranoutic |
Ty Transfers Out ICT C |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytranoutir |
Ty Transfers Out ICT R |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytranoutiu |
Ty Transfers Out ICT U |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
optional |
RI |
|
drtytranoutr |
Ty Transfers Out R |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
required |
RI |
|
drtytranoutu |
Ty Transfers Out U |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
required |
RI |
|
drtytranoutc |
Ty Transfers Out C |
week/sku/stor |
real |
tranx.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyvndfndr |
Ty Vendor Funds R |
week/sku/stor |
real |
tran.csv.ovr |
Retail/Cost |
required |
RI |
|
drtyroyalr |
Ty Royalties R |
week/sku/stor |
real |
tran.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtycogsr |
Ty COGS Adj R |
week/sku/stor |
real |
tran.csv.ovr |
Retail |
optional |
Internal |
|
drtyconsinvc |
Ty Cons Inv C |
week/sku/stor |
real |
tran.csv.ovr |
Cost |
optional |
Internal |
|
drtyconsinvr |
Ty Cons Inv R |
week/sku/stor |
real |
tran.csv.ovr |
Retail |
optional |
Internal |
|
drtymiscadjc |
Ty Misc Adj C |
week/sku/stor |
real |
tran.csv.ovr |
Cost |
optional |
Internal |
|
drtymiscadjr |
Ty Misc Adj R |
week/sku/stor |
real |
tran.csv.ovr |
Retail |
optional |
Internal |
|
drtymiscadju |
Ty Misc Adj U |
week/sku/stor |
real |
tran.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtybocancu |
Ty Backorder Cancel U |
week/sku/stor |
real |
fulfill.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtybofulfillu |
Ty Backorder Fulfilled U |
week/sku/stor |
real |
fulfill.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtycancu |
Ty Cancel U |
week/sku/stor |
real |
fulfill.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtydemandu |
Ty Demand U |
week/sku/stor |
real |
fulfill.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtyfulfillu |
Ty Fulfilled U |
week/sku/stor |
real |
fulfill.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtytrafficu |
Ty Traffic U |
week/sku/stor |
real |
fulfill.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtyims1r |
Ty Pick up in Store (Reg+Promo) R |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtyims1u |
Ty Pick up in Store (Reg+Promo) U |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtyims2r |
Ty Pick up in Store (Clr) R |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtyims2u |
Ty Pick up in Store (Clr) U |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtymtd1r |
Ty Return Back to Online (Reg+Promo) R |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtymtd1u |
Ty Return Back to Online (Reg+Promo) U |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtymtd2r |
Ty Return Back to Online (Clr) R |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtymtd2u |
Ty Return Back to Online (Clr) U |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtystc1r |
Ty Ship to Customer (Reg+Promo) R |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtystc1u |
Ty Ship to Customer (Reg+Promo) U |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtystc2r |
Ty Ship to Customer (Clr) R |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtystc2u |
Ty Ship to Customer (Clr) U |
week/sku/stor |
real |
fulfill_x.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtybisscvp |
Ty Buy in Store Ship to Customer % |
week_scls_ccty |
real |
fulfill_a.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtybopisvp |
Ty Buy Online Pick-Up in Store % |
week_scls_ccty |
real |
fulfill_a.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtyborisvp |
Ty Buy Online, Return to Store % |
week_scls_ccty |
real |
fulfill_a.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtyborovp |
Ty Buy Online, Return Online % |
week_scls_ccty |
real |
fulfill_a.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtyincngstku |
Ty Store to Warehouse Restocking $/ U |
week_scls_ccty |
real |
fulfill_a.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtymtdvp |
Ty Return Back to Online % |
week_scls_ccty |
real |
fulfill_a.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtyonstku |
Ty Warehouse Restocking $/ U |
week_scls_ccty |
real |
fulfill_a.csv.ovr |
Retail/Cost |
optional |
Internal |
|
drtystrstku |
Ty Store Restocking $/ U |
week_scls_ccty |
real |
fulfill_a.csv.ovr |
Retail/Cost |
optional |
Internal |
|
addvlagl2t |
Lag Lly |
week |
text |
lag.csv.ovr |
Retail/Cost |
required |
Admin |
|
addvlaglyt |
Lag Ly |
week |
text |
lag.csv.ovr |
Retail/Cost |
required |
Admin |
|
addvvatcp |
VAT C % |
week_vatb |
real |
vat.csv.ovr |
Retail |
required |
Admin |
|
addvvatvp |
VAT % |
week_vatb |
real |
vat.csv.ovr |
Retail/Cost |
required |
Admin |
|
addvlikepocd |
Like Location End Date |
stor |
date |
stor_a.csv.ovr |
Retail/Cost |
optional |
Admin |
|
addvlikepoct |
Like Location |
stor |
text |
stor_a.csv.ovr |
Retail/Cost |
optional |
Admin |
|
addvlocopnd |
Location Open Dt |
stor |
date |
stor_a.csv.ovr |
Retail/Cost |
optional |
RI |
|
addvlocendd |
Location Close Dt |
stor |
date |
stor_a.csv.ovr |
Retail/Cost |
optional |
RI |
|
addvlocrefd |
Location Refurbrish Dt |
stor |
date |
stor_a.csv.ovr |
Retail/Cost |
optional |
RI |
|
addvwfpoct |
W/F Location Type |
stor |
text |
stor_a.csv.ovr |
Retail/Cost |
optional |
RI |
|
addvpocdesct |
Location Description |
stor |
text |
stor_a.csv.ovr |
Retail/Cost |
optional |
Admin |
|
addvchnlmapt |
Channel Type |
chnc |
text |
addvchnlmapt.csv.ovr |
Retail/Cost |
optional |
Admin |
|
addvlcratet |
Local Currency Symbol |
curc |
text |
addvlcratet.csv.ovr |
Retail/Cost |
optional |
Admin |
|
addvpocsqmv |
Location Square Meter |
dept_stor |
real |
addvpocsqmv.csv.ovr |
Retail/Cost |
optional |
Admin |
|
drtylcratex |
Ty Local Currency Rate |
day_curc |
real |
curr.csv.ovr |
Retail/Cost |
optional |
RI |
|
addvlocattt |
Location Attribute |
stor_satt |
text |
addvlocattt.csv.ovr |
Retail/Cost |
optional |
Admin |
All measure files that need to be loaded as data files need to be grouped based on the File Name; the files should contain the header for the measures to be loaded and should be in .csv format. Measures within a file can be grouped in any order as long as the header column is correctly marked. If a measure is optional in a file, the customer can ignore that measure and group the remaining measures which are available for the customer.
Example:
In the following example, if the customer is not using RAP integration, so only grouping the data which is required and not optional in a file for the data that the customer has.
File Name: tranx.csv.ovr
Base Intersection: week/sku/stor
Data Type: real
week,sku,stor,drtytraninr,drtytraninu,drtytranoutr,drtytranoutu w01_2021,100000,1000,30.96,31.52,0,0 w02_2021,100000,1000,169.13,112.61,1,37.85 w03_2021,100000,1000,233.54,50.26,1,35.09
Historical Data
It is recommended that you have at least two years of historical sales and inventory data for creating MFP targets. Less data can be used, but the more data that is available, the more statistical significance can be given to the MFP targets.
It is also important to have two years of history to produce an optimal forecast.
Note:
Ty BOS measures (drtybos*) are optional. These measures are the very first week BOP values within the domain. If they are not loaded, it will only affect the very first period inventory within the domain. For the rest of the weeks, the loaded previous period EOP will be used as BOP after the weekly batch. When the calendar is purged, Ty BOS will be reset by the weekly batch.
Loading and Extracting Data
Data can be loaded into MFP Cloud Service using the Online Administration Tools, which in turn use standard RPASCE services. For more information on loading and extracting data using Online Administration Tools, see the Oracle Retail Merchandise Financial Planning Cloud Service Administration Guide.
The measure data load is grouped based on the frequency of the data load. For the list of measures loaded for different data load groups, see Appendix: Data Load.
Integration
MFP Cloud Service supports the integration of foundation data files from RMFCS or other source systems. It can get forecast data from AI Foundation and can send approved plans to Retail Insights (RI) using Retail Analytics and Planning (RAP) Integration. For more details about RAP integration, see RAP Integration.
For more details about RMFCS integration and direct integration with RMFCS using a file-based approach, see Appendix: RMFCS Integration.
Retailers using either the template or non-template version must extract and provide the foundation files needed from other source systems as flat files in the required format as needed by RAP integration and then upload to Object Storage. Any data or hierarchy files that are specific to their Planning Solution that cannot be integrated using RAP integration can be directly uploaded to Object Storage for Planning. In the same way, exported files from the solution if not part of RAP integration are sent back to the Object Storage and retailers can download the extracted files from there. The retailer must integrate it with any other system that requires extracted plan data from MFP Cloud Service, if not part of RAP integration.
MFP can also integrate with the 19.0.x release of Oracle Retail Assortment Planning Cloud Service to send plan data. For information on the integration and file format, see Appendix: Integration with Oracle Retail Assortment Planning Cloud Service. For more information on the tasks, see the Oracle Retail Merchandise Financial Planning Cloud Service Administration Guide.
User Roles and Security
To define workbook template security, the system administrator grants individual users, or user groups, access to specific workbook templates. Granting access to workbook templates provides users with the ability to create, modify, save, and commit workbooks for the assigned workbook templates. Users are typically assigned to groups based on their user application (or solution) role. Users in the same group can be given access to workbook templates that belong to that group alone. Users can be assigned to more than one group and granted workbook template access without belonging to the user group that typically uses a specific workbook template. Workbook access is either denied, read-only, or full access. Read-only access allows a user to create a workbook for the template, but the user is not able to edit any values or commit the workbook. The read-only workbook can be refreshed.
Note:
Users must have access to workbooks based on their role. The administrator must always follow the principal of least privilege; that is, each user must only be granted access to the product areas for which the user is responsible.
The following table provides guidance regarding which MFP users must have access to each of the workbooks.
Table 2-2 User’s Access Permission for MFP Workbooks
| Workbook | User Roles |
|---|---|
|
MFP Admin |
Merchandise Financial Planner Administrator or Manager |
|
Merch Plan Targets |
Merchandise Financial Planning Manager/Executive |
|
Merch Plan |
Merchandise Financial Planner |
|
Location Plan Targets |
Merchandise Financial Planning Manager/Executive |
|
Location Plan |
Merchandise Financial Planner |
For more information on security, see the Oracle Retail Predictive Application Server Cloud Edition Administration Guide. For more information on data security in a cloud environment, see the Hosting Policy documents for the cloud solution.
Internationalization
Internationalization is the process of creating software that can be translated more easily. Changes to the code are not specific to any particular market.
Oracle Retail applications have been internationalized to support multiple languages.
The RPASCE platform supports associated solution extensions and solution templates:
-
A solution extension includes a collection of code and generally available configurations. Typically, solution extensions are implemented by a retailer with minimal configuration.
-
A solution template does not include code. A solution template is most typically implemented as a retailer configuration.
Oracle Retail releases the translations of the RPASCE server and client, as well as strings from the solution extensions.
Translations of the solution templates are not released. Since the labels for measures, hierarchies, dimensions, and workbook templates are typically changed by the retailer at implementation time, languages for the templates are not released. All templates have the ability to support multi-byte characters.
For more information on internationalization, see the Oracle Retail Predictive Application Server Cloud Service Administration Guide.
Translations are available for MFP Cloud Service for the following languages:
-
Chinese (Simplified)
-
Chinese (Traditional)
-
Croatian
-
Dutch
-
French
-
German
-
Greek
-
Hungarian
-
Italian
-
Japanese
-
Korean
-
Polish
-
Portuguese (Brazilian)
-
Russian
-
Spanish
-
Swedish
-
Turkish
Batch Process and Scheduling
Batch services are lists of commands or jobs executed without human intervention. A batch window is the time frame in which the batch process must run. It is the upper limit on how long the batch can take. Batch services are used for importing and exporting data and for generating targets. The retailer must decide the best time for running the batch process within the available batch window.
How often to upload updated sales and inventory data and how often to re-create targets must be determined:
-
The retailer must consider at what interval to load the latest sales and inventory data. Though the source transaction system is likely to change daily, the retailer must consider how frequently to load the actualized sales and inventory data. A weekly load of transactional type data is supported, since the base intersection is at week. It is recommended that some information from a transactional system, such as RMFCS, be loaded daily. For example, On-Order that can change on a daily basis.
-
Product availability and seasonal changes can be reasons for recalculating the targets. This can also be triggered by the addition of new products and availability of substantial new sales and inventory history.
The recommended batch schedule for MFP Cloud Service is to load historical and actual data on a weekly basis. All hierarchy changes can be loaded on a weekly basis.
In MFP Cloud Service, batch tasks can be controlled by a system administrator by using the Online Administration Tools. The tools are a predefined set of online administration tasks that are pre-configured for MFP Cloud Service. Those tasks, in turn, call the required batch services with preset parameters to perform the required tasks. The jobs scheduled in the OAT tools can be monitored using the Online Administration Status Dashboard for status of each of the steps the batch is doing. For more information on the Online Administration Tool tasks, see the Oracle Retail Merchandise Financial Planning Cloud Service Administration Guide.
In MFP Cloud Service, the entire batch process is controlled using a set of batch control files and the RPAS batch framework. A predefined set of batch services reads those control files during the batch process. Though users cannot make any changes to underlying batch services/scripts, they can make some changes to batch control files to support their batch schedule.
For more details about the list of batch control files, the batch process using them, and details about updating them, see the batch framework in the Oracle Retail Predictive Application Server Cloud Edition Implementation Guide.
The customer can use JOS/POM if RAP integration is used and if implemented to schedule pre-configured daily and weekly batch tasks in MFP. Those tasks scheduled using JOS/POM in turn call the same Configured batch tasks under the Online Administration Tool tasks. For more details about scheduling of tasks using JOS/POM, see the Oracle Retail Predictive Application Server Cloud Service Administration Guide. For more details about the MFP schedule in JOS/POM, see the Appendix: MFPCS Scheduling in JOS/POM.