Register Login

BAPI_REQUIREMENTS_CHANGE

Transaction BAPI permits the call of the three function modules:

  • BAPI_REQUIREMENTS_CHANGE (change planned independent requirement)
  • BAPI_REQUIREMENTS_CREATE (create planned independent requirement)
  • BAPI_REQUIREMENTS_GETDETAIL (display details for the planned independent requirement)

In these BAPIs, only some interface parameters of function module REQUIREMENTS_MAINTAIN are coded hard and this is then called.

Thus, the BAPIs are only a wrapper of the REQUIREMENTS_MAINTAIN with a minimized import interface.

REQUIREMENTS_MAINTAIN serves for the maintenance of planned independent requirements in the batch or dialog.

A "COMMIT WORK." is issued within the following BAPIs:

  • BAPI_REQUIREMENTS_CHANGE (change planned independent requirement)
  • BAPI_REQUIREMENTS_CREATE (create planned independent requirement)

The "COMMIT WORK." causes the end of the current LUW (logical unit of work) at database level. Side effects as, for example, the deletion of lock entries resulting hereof might be not desired.