Data Conversion

Data conversion involves moving historical actuals, hierarchies, and current plan data from the current system of record into the planning application. It is typically one of the most complex tasks in an implementation. Hierarchies are required for building the domain. However, actuals are typically loaded at the same time in the post-build process. In Retail Analytics and Planning (RAP) integration, the customer can use a single point of integration of all applications within RAP. Planning also can get data by configuring interfaces within it. For more details about RAP integration, see the Oracle Retail Merchandise Financial Planning Cloud Service Implementation Guide.

The sample configuration provided in the starter kit matches the Generally Available (GA) template application. The Implementation Guide for the GA template application can be used as a starting point for understanding the integration APIs. By comparing this information to the modification designs that should be available for the implementation, you can identify what modifications or new loads are required.

Special consideration for data conversions include:

• Beginning of Season (BOS). Many of the planning applications calculate End-of-Period (EOP) inventory and carry that forward to the start of the next period as Beginning-Of-Period (BOP) inventory. At the start of the calendar, there is no EOP to carry forward. The BOS value is used for this purpose.

Loading plan data from legacy systems can be performed with the domain post-build process by modifying the batch control files or separately using the OAT system administration task, Load Measure.