Hierarchy Files

This is the foundation data to build any RPASCE solution. Assortment Planning Cloud Service requires the base foundation hierarchy files, such as Calendar, Product, and Location; also, additional sets of hierarchy files specific to different solutions used in APCS. By default, APCS can get the base foundation hierarchy details as part of RAP integration. The customer only needs to upload hierarchy files which are not part of RAP integration. 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 the file to the same input directory in Object Storage. All hierarchy files should have at least one valid entry, otherwise the customer will face issues in the application if the hierarchy is used in the workbook templates and if it is empty.

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:

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 base hierarchy files that can be readily interfaced in RAP integration, see the following sections:

• Calendar Hierarchy File

• Product Hierarchy File

• Location Hierarchy File

• Cluster Hierarchy File

• Product Attributes Hierarchy File

• Location Attributes Hierarchy File

• Size Hierarchy File

• Customer Segment Hierarchy File