BAPIs for Appropriation Requests 

Use

Various methods are supplied in the AppropriationRequest (BUS2204) business object for accessing appropriation requests of the R/3 System from external systems.

Features

Business Application Programming Interfaces (BAPIs)

BAPI

Description

Create

Create an appropriation request (with variant)

AddVariant

Add a variant to an appropriation request

Change

Change an appropriation request

ChangeVariant

Change a variant of an appropriation request

Delete

Delete an appropriation request

RemoveVariant

Delete a variant of an appropriation request

SetPlanValues

Enter plan values for an appropriation request variant

ResetPlanValue

Reset plan values of an appropriation request variant

AssignVariantToVersion

Assign an appropriation request variant to plan versions

UnAssignVariantVersion

Remove assignment of an appropriation request variant to plan versions

AssignToExpenditureProgPos

Assign appropriation request to investment program positions

ChangeAssignmentToExpProgPos

Change assignment of appropriation request to investment program positions

UnAssignExpenditureProgPos

Remove assignment of appropriation request to investment program positions

GetDetail

Display appropriation request

GetStatus

Display the active system status and user status of an appropriation request

For detailed documentation of the individual BAPIs and their parameters, refer to the BAPI Explorer (transaction: BAPI).

The BAPIs for appropriation requests are buffered BAPIs. This means that the changes to appropriation requests triggered by these BAPIs are carried out initially in the buffer. They are not stored in the database until BAPIService.TransactionCommit is called.

For this reason, SAP recommends that you do not use the BAPIs for appropriation requests together with BAPIs for other business objects, since the other BAPIs do not have access to the buffer. Therefore, set a BAPIService.TransactionCommit before calling BAPIs of other business objects.