PS
BAPI
RFC
Used the same way in S/4HANA
BAPI_BUS2001_CHANGE Change Project Definition
Changes fields of an existing project definition. Interfaces use it to keep dates, responsible persons or organizational data of projects in sync with external systems. Set 'X' in I_PROJECT_DEFINITION_UPD for each field you change. 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
- CJ2001
- Remote-enabled (RFC)
- Yes
- Type
- BAPI
Importing parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| I_PROJECT_DEFINITION | BAPI_BUS2001_CHG | Project definition changes | Yes |
| I_PROJECT_DEFINITION_UPD | BAPI_BUS2001_UPD | Project definition change flags | Yes |
Tables parameters
| Parameter | Type | Description | Required |
|---|---|---|---|
| ET_RETURN | BAPIRET2 | Return messages | — |
| 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_BUS2001_CHANGE'
EXPORTING
i_project_definition = lv_i_project_definition
i_project_definition_upd = lv_i_project_definition_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.