Information Sheet: The Transfer of Planning Data
A. Object Profile
Object Name and Identification
Name of application object |
CostActivityPlanning |
Name of business object (BOR object) |
BUS6026 |
Long text object |
Not supported |
Data category |
Transaction data |
Additional Programs
Reports for displaying and evaluating transferred data |
Standard reporting |
Deletion program for mass data or reversal function? |
1) Transaction KP91, but only for plan-integrated objects 2) Set to 0 for all objects by importing zero values |
Is there a change program for mass data? Can the mass tool be used? |
Yes. Can change itself |
Tables/Databases
Relevant tables |
COKA, COKP, COKS, COKR, COKL, COSP, COSS, COSL, COSR, COEJ, COEJL, COEJR |
Customizing
Customizing activities that influence the data transfer |
Version maintenance (OKEQ/OKEV) |
Time and Sequence
Time of transfer |
Shortly before production startup |
SAP Notes
C. BAPI Information
Which authorization object is required? |
K_CCA, K_CSKB_PLA, K_CSKS_PLA, K_KA09_KVS |
Business object method |
CheckActivityInput CheckActivityOutput CheckKeyFigure CheckPrimCost PostActivityInput PostActivityOutput PostKeyFigure PostPrimCost |
Program for generating test data? |
RK_BAPI_POSTACTINPUT RK_BAPI_POSTACTOUTPUT RK_BAPI_POSTKEYFIGURE RK_BAPI_POSTPRIMCOST |
* See the Guide BAPI Development for Mass Data Transfer
D EDI Information
Message type |
(for example, ORDERS) |
Idoc type |
(for example, ORDERS01, ORDERS02) |
X12 Message type |
(for example, 850) |
Edifact message type |
(for example, ORDERS) |
Output type used? |
(for example, RD00) |
Workflow for error handling |
(for example, TS00008046) |
Processing program |
(for example, IDOC_INPUT_ORDERS) |