Cost Center Planning: Data Retraction
Use
SAP delivers two function modules for the planning application cost center planning, together they provide a
retractor function. You can use data retraction to transfer the plan data generated within cost center planning for activity inputs, statistical key figures, and primary costs from the SAP Business Information Warehouse (SAP BW) into your operational R/3 System. In the operational system, you can use this data in different ways in Cost Center Accounting (CO-OM-CCA): For example, you can compare the plan data with actual data generated in current business activities, replace the plan data already entered in the R/3 System with the data from SEM-BPS, or use certain functions for further processing that are supported in CO-OM-CCA (but not in SEM-BPS).Integration
With the data retraction, you create a connection between the plan data generated in SAP BW and the plan and actual data stored in the operational system that arise in current business activities.
Prerequisites
The retractor function refers to a certain thematic area of cost center planning that you specify when starting the retractor:
In each of these areas, the system orientates itself to the technical names of certain delivered InfoObjects of SAP Business Content. The necessary objects for the retractor functions delivered within cost center planning are already completely configured. If you want to use the delivered planning application as a template to structure your own cost center planning then you must ensure that you use the appropriate InfoObjects.
You require SAP R/3 4.6B or higher to transfer the plan data read from SAP BW during data retraction to the data structures of cost center accounting. In addition, in the system in which you operate SEM-BPS, an RFC destination must be maintained through which you can create a connection to the R/3 System into which the data should be transferred.
Features
During the data retraction, you can choose whether you want to update the data to be transferred directly into the target system or whether you want to execute a test run to check the correct process without data being changed.
You can choose between two different types of data update: You can either add the data to already existing data, or you can choose to overwrite existing data with the newly transferred data.
Activities
Proceed in one of the following ways, depending on whether you want to execute data retraction within the delivered planning application or whether you want to set up a retractor in a planning application you have modified:
Executing Retraction in the Delivered Planning Application
Setting Up Retraction in the Modified Planning Application
Both delivered function modules are divided into an initialization module and the actual retractor module. Therefore, it is possible to realize the retractor functions by creating a planning function of the type
Exit, and setting the parameters so that they correspond to your system landscape:
|
Parameter |
Data Element |
Meaning |
|
BUSI |
I_BUSI |
R/3 component |
|
CASE |
I_CASE |
Retractor control |
|
DELTA |
DEL_BOOK |
Delta update |
|
MAPP |
KCD_REPID |
Sender structure for field assignment (see SAP Note 525543) |
|
RFC_DEST |
RFCDEST |
RFC destination |
|
TEST |
TST_X |
Test mode |
|
ZARE |
I_COAR |
Controlling area |
|
ZELM |
I_CELM |
Cost element |
|
ZTYP |
I_CTYP |
Cost element category |

To ensure the correct execution of the function modules, avoid the inclusion of the characteristics listed below in the list of fields to be changed:
You get the possible values and their meaning from the F4 help.

Note generally when executing data retraction that the function modules you have assigned to the exit function can always only operate at a given time on the data that results from splitting the package selection into internal data objects. For more information, see
Data Transfer to Planning Functions.