CO
BAPI
RFC
Used the same way in S/4HANA
BAPI_ACC_MANUAL_ALLOC_POST Accounting: Post Manual Cost Allocation
Manually reposts an amount on a cost element from a sender CO object to a receiver CO object (the counterpart of KB15N). Interfaces that move costs between cost centers or orders based on keys from an external system use it. Fill the sender and receiver objects and the cost element in the items; if RETURN has no errors, call BAPI_TRANSACTION_COMMIT.
- Function group
- K40C
- Remote-enabled (RFC)
- Yes
- Type
- BAPI
Importing parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| DOC_HEADER | BAPIDOCHDRU12P | Document header (controlling area, dates, user) | Yes |
| IGNORE_WARNINGS | BAPIIW-IGNWARN | Ignore warnings | — |
Exporting parameters
| Parameter | Type | Description |
|---|---|---|
| DOC_NO | BAPIDOCHDRU12P-DOC_NO | Posted CO document number |
Tables parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| DOC_ITEMS | BAPIMAITM | Manual allocation items | Yes |
| CUSTOMER_FIELDS | BAPIEXTC | Customer fields | — |
| RETURN | BAPIRET2 | Return messages | Yes |
Call template (ABAP)
A skeleton generated from the interface. It lists mandatory importing parameters, exporting parameters and tables; declare the variables with suitable types in your own program.
CALL FUNCTION 'BAPI_ACC_MANUAL_ALLOC_POST'
EXPORTING
doc_header = lv_doc_header
IMPORTING
doc_no = lv_doc_no
TABLES
doc_items = lt_doc_items
customer_fields = lt_customer_fields
return = lt_return.Related tables
Can't find the report you need?
We also build anything that is not in the catalog. Describe it briefly and we will suggest the right solution.