PP
BAPI
RFC
Used the same way in S/4HANA
BAPI_PRODORDCONF_CREATE_HDR Enter Production Order Header Confirmation
Posts confirmations at production order header level, where all operations are confirmed together as in CO15. It fits simple production processes and interfaces that only report the finished quantity per order. Use TESTRUN to validate the data first, then post and call BAPI_TRANSACTION_COMMIT if DETAIL_RETURN shows no errors.
- Function group
- 2116
- Remote-enabled (RFC)
- Yes
- Type
- BAPI
Importing parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| POST_WRONG_ENTRIES | BAPI_CORU_PARAM-INS_ERR | Post incorrect entries to error pool | — |
| TESTRUN | BAPI_CORU_PARAM-TESTRUN | Test run (no update) | — |
Exporting parameters
| Parameter | Type | Description |
|---|---|---|
| RETURN | BAPIRET1 | Return messages |
Tables parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| ATHDRLEVELS | BAPI_PP_HDRLEVEL | Order header confirmations | Yes |
| CHARACTERISTICS_BATCH | BAPI_CHAR_BATCH | Batch characteristics | — |
| DETAIL_RETURN | BAPI_CORU_RETURN | Detailed return messages per object | — |
| GOODSMOVEMENTS | BAPI2017_GM_ITEM_CREATE | Goods movements | — |
| LINK_CONF_GOODSMOV | BAPI_LINK_CONF_GOODSMOV | Link between confirmation and goods movement | — |
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_PRODORDCONF_CREATE_HDR'
IMPORTING
return = lv_return
TABLES
athdrlevels = lt_athdrlevels
characteristics_batch = lt_characteristics_batch
detail_return = lt_detail_return
goodsmovements = lt_goodsmovements
link_conf_goodsmov = lt_link_conf_goodsmov.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.