SAP VB_CP_VERSION_APPROVE Function Module for Approve Batch Record

Search SAP Function Modules

VB_CP_VERSION_APPROVE is a standard vb cp version approve SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Approve Batch Record processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for vb cp version approve FM, simply by entering the name VB_CP_VERSION_APPROVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: VBP_EBR
Program Name: SAPLVBP_EBR
Main Program: SAPLVBP_EBR
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VB_CP_VERSION_APPROVE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'VB_CP_VERSION_APPROVE'"Approve Batch Record
  EXPORTING
   I_VERS =  "Batch Record: Buffer Table for Versions

EXCEPTIONS
   DEVIATION_CHECK_ERROR = 1    ACTIVITY_NOT_ALLOWED = 2    NO_AUTHORITY = 3    SIGN_ERROR = 4    STATUS_ERROR = 5    ARCHIVE_ERROR = 6    STATUS_NOT_ALLOWED = 7    CANCELLED_BY_USER = 8    SIGNING_PROCEDURE_CANCELLED = 9 

.

IMPORTING Parameters details for VB_CP_VERSION_APPROVE

I_VERS - Batch Record: Buffer Table for Versions

Data type: VBCP8
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

DEVIATION_CHECK_ERROR -

Data type:
Optional: No
Call by Reference: Yes

ACTIVITY_NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY - No Authorization

Data type:
Optional: No
Call by Reference: Yes

SIGN_ERROR -

Data type:
Optional: No
Call by Reference: Yes

STATUS_ERROR -

Data type:
Optional: No
Call by Reference: Yes

ARCHIVE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

STATUS_NOT_ALLOWED - Status not permitted

Data type:
Optional: No
Call by Reference: Yes

CANCELLED_BY_USER -

Data type:
Optional: No
Call by Reference: Yes

SIGNING_PROCEDURE_CANCELLED - Signature Process was Canceled

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for VB_CP_VERSION_APPROVE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM VB_CP_VERSION_APPROVE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects