Import Parameters For Transferring Planning Data 
The following parameters are independent of the planning area for the plan data that you wish to transfer:
Function Module Import Parameters for Transferring Planning Data
Import parameters |
Transfer Of |
Description |
BLTXT |
Data |
Document text |
GJAHR |
Data |
Fiscal year |
KOKRS |
Data |
Controlling area |
PERAB |
Data |
From period |
PERBI |
Data |
To period |
VERSN |
Data |
Version |
VRGNG |
Data |
Transaction |
IRKU01_CUR |
Control information |
Currency field group indicator |
IRKU02_CUR |
Control information |
Currency field group indicator |
MESSAGES_SHOW |
Control information |
Display messages |
UPDATE_VALUES |
Control information |
Check existing values |
COMMIT |
Control information |
Execute commit using function module |
DELTA |
Control information |
Indicator for supplementary entry |
TESTMODE |
Control information |
Error message without update |
ONLINE_VB |
Control information |
Online posting |
Additional Import Parameters for Function Modules K_ACT_PLAN_INTERFACE_TOTAL and K_ACT_PLAN_INTERFACE_PERIOD
Import parameters |
Transfer Of |
Description |
PRICE_QUANT_PLAN |
Control information |
Plan the quantities and/or prices |
Import Parameters VERSN and VRGNG
Use the VERSN parameter to select the version you require.
The VRGNG parameter contains the business transactions in the Cost Center Accounting component (CO-OM-CCA) and controls which planning area you transfer the external data to. To see an overview of all the Controlling component business transactions, use transaction OKC1. See: Table Structures and Function Modules for Planning Data for the business transactions used in the planning function modules.
Import Parameters IRKU01_CUR and IRKU02_CUR
You use the IRKU01_CUR (for cost planning) and IRKU02_CUR import parameters (for activity planning) to define which currency field groups the posted amounts are transferred to in the interface, so defining which amount currency is used for display (transaction, object currency, or controlling area currency).
Caution
The use of parameters IRKU01-CUR or IRKU02_CUR is strongly recommended.
The IRKU01_CUR and IRK02_CUR import parameters replace the RPLAN import parameter that was used up to Release 3.0B. If the import parameters are not transferred, or are blank in the callup program, the system continues to use RPLAN, in which the standard plan parameter CO-01 is defaulted. RPLAN is included for compatibility reasons only, and should no longer be used.
Caution
You must use import parameter IRKU01_CUR for plan data transfers that use function modules K_RKP6_INTERFACE_PERIOD and K_RKP6_INTERFACE_TOTAL.
Use Import Parameters for Indication of Currency Field Groups in the Function Modules for the Transfer of Planning Data.
Function Module |
Data |
Import parameters |
K_ACT_PLAN_INTERFACE_TOTAL |
Cumulated activity types |
IRKU02_CUR |
K_ACT_PLAN_INTERFACE_ PERIOD |
Periodic activity types |
IRKU02_CUR |
K_COSTS_PLAN_INTERFACE_ TOTAL |
Activity-independent cumulated primary costs |
IRKU01_CUR |
K_COSTS_PLAN_INTERFACE_PERIOD |
Activity-independent periodic primary costs |
IRKU01_CUR |
K_RKP6_INTERFACE_PERIOD |
Activity-dependent periodic primary costs |
IRKU01_CUR |
K_RKP6_INTERFACE_TOTAL |
Activity-dependent cumulated primary costs |
IRKU01_CUR |
Caution
If you wish to use the individual import parameters in function modules for control purposes, activate the corresponding structure field with an "X" for the currency field groups that are to be manually planned.
Field Groups for Import Parameter IRKU01_CUR
Name |
Description |
WKG_MAN |
Total value in controlling area currency, manual |
WKF_MAN |
Fixed value in controlling area currency, manual |
WTG_MAN |
Total value in transaction currency, manual |
WTF_MAN |
Fixed value in transaction currency, manual |
WOG_MAN |
Total value in object currency, manual |
WOF_MAN |
Fixed value in object currency, manual |
Field Groups of Import Parameter IRKU02_CUR
Name |
Description |
TKG_MAN |
Total price in controlling area currency, manual |
TKF_MAN |
Fixed price in controlling area currency, manual |
TOG_MAN |
Total price in object currency, manual |
TOF_MAN |
Fixed price in object currency, manual |
Note
Currency field groups can be activated for one currency only (transaction, object, or controlling area). Other field groups are calculated using currency translation, based on the exchange rate table.
( )
You need to plan total and fixed amounts in the same currency. If no fixed amounts are planned, do not activate the corresponding indicator.
Import Parameter PRICE_QUANT_PLAN
The import parameter PRICE_QUANT_PLAN is only used for the K_ACT_PLAN_INTERFACE_TOTAL and K_ACT_PLAN_INTERFACE_PERIOD function modules.
Values of Parameter PRICE_QUANT_PLAN
Parameter value |
Description |
B |
Quantities and prices |
P |
Transfer prices only |
Q |
Transfer quantities only |
The PRICE_QUANT_PLAN parameter is defaulted with B .
Optional Parameters
Transferring import parameters BLTXT, COMMIT, DELTA, MESSAGES_SHOW, UPDATE_VALUES, and ONLINE_VB is optional. These parameters are defaulted and should only be changed if you wish to have different defaults.
You can use the BLTXT parameter to transfer a header text if planning documents were created.
The COMMIT import parameter indicates whether the commit was executed using the function module (enter X ), or the callup program (enter a blank space). The parameter default is X. If the program is only used to call up one function module, or if separate sets of planning data are transferred, you can use a function module to execute the commit. If multiple callups with separate but dependent plan data are executed, and you wish to ensure that the planning data is completely transferred only if no function module errors occur, then you need to deactivate the parameter. At the end of the program, you need to transmit a COMMIT WORK.
If you activate the MESSAGES_SHOW import parameter with X, the SAP system issues the error messages that occurred during the function module callup. It is useful to activate this parameter, but if you call up the log interface in your own program for evaluation, then you should not activate it. Nor should you activate it during background processing.
If you activate the TESTMODE parameter, the SAP system displays error messages without running an update. If you transfer data for more than one planning area successively, this is included in the error messages. For example, the error messages for activity input planning take into account whether the data for activity planning has been transferred already.
The default for the UPDATE_VALUES parameter is blank, which means that values already planned cannot be overwritten. Activate this parameter to overwrite planned values.
The default for ONLINE_VB should not be changed. The DELTA parameter is for internal use only.