PS
BAPI
RFC
Used the same way in S/4HANA
BAPI_BUS2002_CHANGE Change Network Header
Changes header data of an existing network, such as dates, scheduling data or the assigned WBS element. Interfaces use it to update networks after changes in a planning tool. Flag the changed fields in I_NETWORK_UPD. Call BAPI_PS_INITIALIZATION first, then BAPI_PS_PRECOMMIT and BAPI_TRANSACTION_COMMIT only when ET_RETURN has no type E or A messages.
- Function group
- CN2002
- Remote-enabled (RFC)
- Yes
- Type
- BAPI
Importing parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| I_NUMBER | BAPI_NETWORK_LIST-NETWORK | Network number | Yes |
| I_NETWORK | BAPI_BUS2002_CHG | Network header changes | Yes |
| I_NETWORK_UPD | BAPI_BUS2002_UPD | Network header change flags | Yes |
Tables parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| ET_RETURN | BAPIRET2 | Return messages | Yes |
| EXTENSIONIN | BAPIPAREX | Customer fields (inbound) | — |
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_BUS2002_CHANGE'
EXPORTING
i_number = lv_i_number
i_network = lv_i_network
i_network_upd = lv_i_network_upd
TABLES
et_return = lt_et_return
extensionin = lt_extensionin.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.