Information Sheet for the Transfer of Sender Activity
Object Profile
Object Name and Identification
Name of business object (BOR object) |
BUS6014 (Acctng SenderActivity) |
Long text object |
Not supported |
Data category |
Transaction data |
Number assignment |
Internal |
Additional Programs
Reports for displaying and evaluating transferred data |
Standard reporting |
Deletion program for mass data or reversal function? |
Reversal BAPI is available |
Tables/Databases
Relevant tables |
COBK, COEPL, COSL |
Time and Sequence
Time of transfer |
Any |
Dependency on other data |
Controlling area, account assignment objects (cost centers, activity types, orders and so on) |
BAPI Information
Which authorization object is required? |
K_PVARIANT, K_VRGNG, S_ADMI_FCD, S_ALV_LAYO, S_BDS_DS, S_CTS_ADMI, S_DATASET, S_DEVELOP, S_DOKU_AUT, S_PRO_AUTH, S_RFC, S_TABU_DIS, S_TCODE, S_TRANSLAT, C_AFKO_AWK, P_ORGIN, S_TRANSPRT, S_OC_DOC, S_OC_ROLE, S_OC_SEND, S_SPO_DEV |
Business object method |
POST |
Message type |
ACC_SENDER_ACTIVITIES |
Are the objects created specified in a message within the standard parameter RETURN?* |
Yes: CO document number |
Test run indicator (details*) |
CHECK method |
Is a mass update possible? Has the buffer concept been realized? |
Can several BAPIs be posted within one
|
Notes for parallelization |
Parallelization possible |