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

• Product Hierarchy File

• Location Hierarchy File

• Currency Hierarchy File

• VAT Hierarchy File

• Location Attributes Hierarchy File

• Level Hierarchy File

• Custom Messages Hierarchy File