Custom Flex Attribute Mapping

Custom flex attributes (also known as CFAS) data comes from RMFCS. This data is passed through the data warehouse and transformed to match RPAS data requirements. The CFAS data is exported to the planning integration schema in 9 tables: 3 sets of tables for each intersection of item, location, and item/location, with each set broken out by datatype (string, number, date). Each set of tables will uses anidentical structure where the source data in the data warehouse (which is in multiple columns) is pivoted into a single column having all the attribute values for a given intersection and datatype.

Specifically for location attributes, the same table may optionally include location attributes from other sources which can then be used to extend your Planning applications with that data. CFAS attributes are exported automatically from the data warehouse when they are integrated from MFCS; but for the other types, it requires additional configurations. The reason for requiring configurations is that location attributes data does not come with associated group IDs and group names that Planning requires to use the data, so the implementer must separately generate these groupings first.

The list of supported tables on this integration are below:

Source Tables	Target Table
W_INT_ORG_D_CFA W_INT_ORG_ATTR_D W_ORGANIZATION_FLEX_D	W_PDS_ORG_ATTR_STR_D
W_INT_ORG_D_CFA	W_PDS_ORG_ATTR_NBR_D
W_INT_ORG_D_CFA	W_PDS_ORG_ATTR_DT_D
W_PRODUCT_D_CFA	W_PDS_PRODUCT_ATTR_STR_D
W_PRODUCT_D_CFA	W_PDS_PRODUCT_ATTR_NBR_D
W_PRODUCT_D_CFA	W_PDS_PRODUCT_ATTR_DT_D
W_RTL_IT_LC_D_CFA	W_PDS_PROD_ORG_ATTR_STR_D
W_RTL_IT_LC_D_CFA	W_PDS_PROD_ORG_ATTR_NBR_D
W_RTL_IT_LC_D_CFA	W_PDS_PROD_ORG_ATTR_DT_D

All of the tables include an ATTR_ID column that is automatically generated from either the CFAS attribute group name or the user-supplied group names, stripped of unsupported characters for ID columns. They also have an ATTR_VALUE column containing the attribute values from the source table, which is a combination of all the values in all columns having the same data type (CHAR, NUM, DATE). ATTR_VALUE for string types are a trimmed version with unsupported characters removed. Also specific to string types, there is an ATTR_VALUE_DESC column which has the unmodified string value from the source table.

To leverage location string attributes for non-CFAS data, you need to load the location group definitions to the common translation lookup table in the data warehouse, W_DOMAIN_MEMBER_LKP_TL. From APEX, you may insert the group names to the staging table W_DOMAIN_MEMBER_DS_TL and then run the associated POM job W_DOMAIN_MEMBER_LKP_TL_JOB to populate the target table. You need to populate the columns with specific values as described below:

Column	Usage
DOMAIN_CODE	Use RTL_ORG_ATTR for columns in W_INT_ORG_ATTR_D and RTL_ORG_FLEX for columns in W_ORGANIZATION_FLEX_D
DOMAIN_MEMBER_CODE	Specify the exact column in the source table having this attribute in it, such as FLEX1_CHAR_VALUE
DOMAIN_MEMBER_NAME	Specify the name of the attribute group, such as Climate
LANGUAGE_CODE	Specify the primary language code used for all translated lookup data, such as US
SRC_LANGUAGE_CODE	Specify the primary language code used for all translated lookup data, such as US