Start of Content Area

Function documentation Planned Data Transfer  Locate the document in its SAP Library structure

Use

You transfer your planned budgets from SAP BI to SAP ECC using the Release Workbench or the Budget Monitor so that they can be used in the operational applications, such as the OTB Check.

Prerequisites

You have configured the budget processes in SAP BI and SAP ECC. The message types for OTB and the Price Planning Workbench (PPW: Sales reduction budgets) are active in SAP BI. For OTB, RFC Connection to SAP ECC is set as the communication method in Customizing.

Delta Method

If you only want the system to transfer changed or new planned values (above the tolerance threshold) to SAP ECC following the revision of a price plan, you have activated the delta method in the settings for the budget type in Customizing for SAP BI under SAP NetWeaver → Business Intelligence → Settings for BI Content → Retail → Budget Planning.

Features

You use the Release Workbench or the Budget Monitor to transfer planning data from an InfoCube in SAP BW to SAP ECC, where the system stores it as target values.SAP BI saves the transferred budgets in a transactional DataStore object.

You can release planning data directly or you can schedule a release as part of background processing. Errors or exceptions are recorded in the application log (object W, subobject MAP_RELEASE, external identification OTB (for OTB) or BUDGET (for PPW) and you can display them in the Release Workbench. When you transfer the budget values of a characteristics combination for the first time, the system assigns a budget number. To improve performance during a data transfer, you can use parallel processing by creating data packages for the RFC interface and entering a split criterion. As a split criterion, you can select a characteristic for the budget level from the budget type to be transferred.

Example

Budget planning takes place once a month and you want to transfer all the budgets for a year. If you select the InfoObject Month as the split criterion, the system creates twelve work packages and processes them in parallel (for example, four packages at a time, which is the equivalent of four months simultaneously, for a selected number of four processes).

Periodicity

Planning takes place in SAP BI for periods. Dow to the periodicity day, the system supports the calendaric periods year, half year, quarter, month, week, and also freely-definable posting periods of a fiscal year variant.

When the system transfers the planned data, it determines the start and end date for each period. SAP ECC saves these time periods. This means that operational applications no longer have to determine and interpret the time periods used; instead they use the reference date (OTB: Vendor date, PPW: Today's date) to directly determine the period in which the reference date falls.

Releasing Budgets Using the Release Workbench

...

...

       1.      You start the Release Workbench (transaction UPARI_REL) in SAP BI.

       2.      You select either OTB or Sales Reduction Budget as the message type.

       3.      You select a budget type (only relevant for OTB) for which you want to release budgets and send them to SAP ECC.

       4.      You navigate to the tab page of the selected message type and enter the appropriate selection criteria. You must enter a plan version and the selection criteria for parallel processing.

       5.      You can restrict your selection using the budget level fields.

By simulating a data release you can analyze whether and how many data records you have to transfer. You can display the result of this in the application log (subobject MAP_SIMU).

Releasing Budgets Using the Budget Monitor in SAP BI

For more information, see Budget Monitor.

See also:

Price Planning

 

End of Content Area