MM
BAPI
RFC
Used the same way in S/4HANA
BAPI_ENTRYSHEET_RELEASE Release Service Entry Sheet
Releases (accepts) a service entry sheet with the given release code; the acceptance posts the goods receipt for the service. Developers use it to automate service acceptance from an external approval flow or a portal. The user needs authorization for the release code; check RETURN and call BAPI_TRANSACTION_COMMIT if you passed NO_COMMIT_WORK = 'X'.
- Function group
- MLBO
- Remote-enabled (RFC)
- Yes
- Type
- BAPI
Importing parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| ENTRYSHEET | BAPIESSR-SHEET_NO | Entry sheet number | Yes |
| REL_CODE | BAPIMMPARA-REL_CODE | Release code | Yes |
| NO_COMMIT_WORK | BAPIFLAG-BAPIFLAG | Do not perform COMMIT WORK | — |
Tables parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| RETURN | BAPIRETURN1 | Processing errors that occurred | — |
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_ENTRYSHEET_RELEASE'
EXPORTING
entrysheet = lv_entrysheet
rel_code = lv_rel_code
TABLES
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.