Load Hierarchies (load_hier)

This task is used to load the hierarchy files listed below. Before loading the hierarchy file, the hierarchy file needs to be uploaded into Object Storage. Only if the hierarchy file is available it will load, otherwise, it will skip loading that hierarchy file. It is configured to load all the hierarchy files listed below with the purge age as zero, but it can be configured to change the purge age in the batch_exec_list.txt control file. If RAP integration (Enable RDX) is enabled, it only loads the hierarchies which are interfaced through RAP integration.

This task automatically always runs as part of the weekly batch.

Following is the list of hierarchies that are loaded, if available, to be reloaded.

If Batch Uses RDX is not enabled:

• Calendar (clnd)

• Product (prod)

• Location (loc)

• Cluster (clrh)

• Product Attributes (patr)

• Location Attributes (satr)

• Assortment (asrt)

• Curve (curv)

• Location Space (sspc)

• Performance Group (pos1)

• Clustering Strategy (pos2)

• Cluster Source (csls)

• Cluster Version (cver)

• Customer Segment (csgh)

• Level (lvlh)

• Custom Messages (cmsh)

• Size (sizh)

If Batch Uses RDX is enabled:

• Assortment (asrt)
• Curve (curv)
• Location Space (sspc)
• Performance Group (pos1)
• Clustering Strategy (pos2)
• Cluster Source (csls)
• Cluster Version (cver)
• Level (lvlh)
• Custom Messages (cmsh)
• Customer Segment (csgh)
• Size (sizh)

For details about hierarchies, see the Oracle Retail Assortment Planning Cloud Service Implementation Guide.