In current order-based planning, order key figures (OKF) are calculated on the fly, out of OBP's primary persistency. Many master data tables and order tables in OBP must be accessed to calculate the order key figure and pass it to the UI (for example, Microsoft Excel). Some key figures (like the Projected Stock key figure) will be significantly impacted. The data retrieval calculation process is realized by the procedures injected into the calculation scenario. These procedures have to be compiled, and compilation takes time.
This current OBP reality is in contrast to time-series planning, in which, to pass the key figure to the UI, it is necessary to access only one planning level, one table.
With the introduction of the OKF cache, the data retrieval process for order key figures will become similar to the retrieval in the time-series space. This can't be achieved 100%, but this is the solution directionally.
The OKF persistency is a cache of the data sources assigned to a planning level, such as the LOCPROD level. OKF is linked to the planning area planning level via the PLOBJ mapping table. OKF cache also carries PERIODID access. Data in the OKF cache is stored at the granular level. The key fields are object IDs (for example, order IDs).
Since the OKF Cache carries PERIODID and PLOBJID access is realized via PLOBJMAP table, the execution plan of the query is lean resulting in much lower compile time and significantly faster execution time of the calculation scenario query.
OKF cache has an impact on the configuration of the planning area. This configuration is realized in HPA.
There are several job templates associated with the order key figures in the Harmonized Planning Area.
- Initial Loading of Order Key Figures (Cached)
- Deletion of Order Key Figures (Cached)
Delete the cache in which the key figure values of order key figures are stored in case of inconsistencies
- Reconcile Planning Objects for Order Key Figure (Cached)
- Needs to be triggered after Initial Loading of Order Key Figures (Cached) was executed
- Needs to be executed regularly for non-tightly coupled planning levels since PLOBJs are not automatically generated
- Order-Based Planning: Generate Detailed Pegging Based Order Key Figures (Cached)
- Consistency Check Order Key Figures (Cached)