Product Attributes Hierarchy File

The product attributes hierarchy represents attributes associated with products. These attributes are used to group products within categories. This grouping is what consumer decision trees are built on and are used when showing dynamic rollups at the item level.

This hierarchy is intended to capture all product attributes for all product types. The attributes are then assigned to individual products. This assignment is used when processing the dynamic rollups.

This hierarchy is intended to be customized for the individual retailer's needs.

Name	Label	Hierarchy Type	Aggs
PATV	Prod Attribute Value	Main	None
PATT	Prod Attribute	Main	PATV

File name: patr.hdr.csv.dat

File format: comma-separated values file

The following table describes the fields in this file.

Field	Description
Prod Attribute Value	The various values that an attribute might have. For example, the package type attribute might take the values bag, box, or convenience.
Prod Attribute	The name of a product attribute, such as brand, family type, flavor, grain, package type, size, or temperature.

Example:

patv,patv_label,patt,patt_label
prodtype_llc,LLC,prodtype,Product Type
prodtype_slc,SLC,prodtype,Product Type
prodtype_z9999,Z_Other,prodtype,Product Type
brand_dylanrose,Dylan Rose,brand,Brand
brand_forevercali,Forever Cali,brand,Brand
brand_legaci,Legaci,brand,Brand
brand_z9999,Z_Other,brand,Brand

Note:

PATR is used as the Attribute Hierarchy to support the 2-dimensional Product attribute measure. For detailed information on how this configuration is set up, see the Oracle Retail Predictive Application Server Cloud Edition Configuration Tools User Guide.

Note:

APCS has separate workbook flows defined for Items classified as LLC or SLC based on the product attribute Product Type. It is recommended to use the Product Type attribute with LLC and SLC attribute values for all the Items. The LLC type defines items whose selling pattern is the same across all assortment periods where the SLC items selling pattern varies by Season. The customer can assign any UDA to identify the SLC/LLC items in RMFCS and later can assign that attribute and attribute value in the Planning Admin -> Batch Setup view for the Item Attribute for Basic Items and Product Attribute Value for SLC/LLC Item measures.

Note:

APCS uses the Nested Dynamic Rollup of Hierarchies option to review products based on the combination of various product attributes. If non-template customers want to use the same features, customization of their configuration is needed.

For more details about customizing the configuration to use Nested Dynamic Rollup, see the Oracle Retail Predictive Application Server Cloud Edition Configuration of Nested Dynamic Hierarchies Reference Paper. It is available on My Oracle Support in the Oracle Retail Predictive Application Server (RPAS) Cloud for Planning and Optimization / Supply Chain Cloud Services Documentation Library Doc ID: 2492295.1.

Note:

APCS GA uses the Z_Other attribute values for all the attributes with the hard-coded value as z9999. This specific Attribute is used to dynamically group the Attributes with sales below a preset threshold to focus more on critical attribute values for assortments, so the customer needs to include that attribute value if they are loading attributes using a flat file. If they are importing attributes from RAP, then they need to enable the Integration variable PATR_OTHER to Y in order to include the hard-coded attribute value as part of Product Attribute Hierarchy Import.