CO
BAPI
RFC
Used the same way in S/4HANA
BAPI_ACC_MANUAL_ALLOC_CHECK Accounting: Check Manual Cost Allocation
Checks manual cost allocation data without posting. Upload programs use it to validate the lines before calling BAPI_ACC_MANUAL_ALLOC_POST. The only result is the messages in the RETURN table; no document is created.
- 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 | — |
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_CHECK'
EXPORTING
doc_header = lv_doc_header
TABLES
doc_items = lt_doc_items
customer_fields = lt_customer_fields
return = lt_return.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.