Transformations in Planning
Planning applications allow the loading of fact data at the load intersection level (such as Item and Location) but uses the data within the application at an aggregated level (called the base intersection). In MFP, though all facts are loaded at the item level, it only needs data to plan at the Subclass level. The data will be aggregated from item level to subclass level for all the configured metrics to be directly used by the application. During re-classifications (such as when one item is moved from one subclass to another subclass), after the new hierarchy details are imported into MFP it also triggers re-classification of all fact data. Re-aggregation of fact data then happens only for shared facts having different load and base intersections.
In Planning applications, fact data is grouped as dynamic fact groups based mainly on the base intersection and interface
details, as defined in the Data Interface of the Application Configuration. RI and AI Foundation use a relational data model,
whereas Planning applications internally use a hierarchical data model. Data from RAP, stored using the relational data model,
needs to be transformed to be loaded into Planning applications. A similar approach is necessary for data coming out of planning
applications to AI Foundation or external sources. These data transformations happen as part of the interfaces defined in interface.cfg
(Interfaces Configuration File), which is a mapping of dimensions and measures from Planning applications
to external system table columns. Refer to the application-specific Implementation Guides for more information about Planning
Data Interfaces.