Entering content frame

Background documentation Import Parameters for Transferring Planning Data Locate the document in its SAP Library structure

The table parameter, an internal table, is dependent on the business transaction for which you want to transfer the external data. It contains the data itself, and is based on the standard SAP system table structure, which is dependent on the data being transferred (VRGNG parameter). The SAP system uses four different table structures for the transfer of planning data.

For costs

   

Periodic

RKU01JA

Cumulated

RKU01G

 

For quantities

   

Periodic

RKU02JA

Cumulated

RKU02G

 

Example

The name of the table used by a function module contains the name of the structure and the letter 'I' before it.

Structure: RKU01JA

Table name: IRKU01JA

These table structures contain many fields which are not required for transferring the external data from different planning areas. The structures are designed to transfer data from other business transactions at a later date.

Fields already filled in the structure are replaced by the transferred values.

The table below provides an overview of the function modules to be called up, with their corresponding table structures.

Function Modules and Table Structures

Function Module

Table Structure

K_COSTS_PLAN_INTERFACE_PERIOD

RKU01JA

K_COSTS_PLAN_INTERFACE_TOTAL

RKU01G

K_RKP6_INTERFACE_PERIOD

RKU01JA

K_RKP6_INTERFACE_TOTAL

RKU01G

K_ACT_PLAN_INTERFACE_PERIOD

RKU02JA

K_ACT_PLAN_INTERFACE_TOTAL

RKU02G

K_RATIO_PLAN_INTERFACE_PERIOD

RKU02JA

K_RATIO_PLAN_INTERFACE_TOTAL

RKU02G

K_ACT_INPUT_INTERFACE_PERIOD

RKU01JA

K_ACT_INPUT_INTERFACE_TOTAL

RKU01G

 

Below is a list of sample fields to be filled in the RKU01JA or RKU01G structure for transferring primary cost planning data that is activity-independent (business transaction RKP1).

The GJAHR, KOKRS parameters and so on, no longer need to be transferred.

You can also make entries in more fields, such as:

One object type may be transferred for each function callup. Primary cost planning (activity-independent) on cost centers and orders, therefore, requires two separate callups.

For activity input planning for sender business processes, the P_PRZNR field must contain the key of the business process.

For order cost planning for sender business processes, the P_PRZNR field must contain the key of the business process.

 

 

Leaving content frame