SAP SD_STATUS_VBAP_CHECK Function Module for NOTRANSL: Prüfen eines Vorgangs anhand des Anwenderstatus
SD_STATUS_VBAP_CHECK is a standard sd status vbap check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Prüfen eines Vorgangs anhand des Anwenderstatus 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 sd status vbap check FM, simply by entering the name SD_STATUS_VBAP_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: V45C
Program Name: SAPLV45C
Main Program: SAPLV45C
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function SD_STATUS_VBAP_CHECK 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 'SD_STATUS_VBAP_CHECK'"NOTRANSL: Prüfen eines Vorgangs anhand des Anwenderstatus.
EXPORTING
* I_OBJNR = ' ' "
* I_POSNR = ' ' "Item Number of Sales Document
* I_VBAP = ' ' "Item Work Area
* I_VBELN = ' ' "SD Document Number
* I_VRGNG = ' ' "Business Transaction
EXCEPTIONS
NOT_ALLOWED = 1 OBJECT_NOT_FOUND = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLV45C_403 Customer exit for enterprise contract hierarchy processing
IMPORTING Parameters details for SD_STATUS_VBAP_CHECK
I_OBJNR -
Data type: VBAP-OBJNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_POSNR - Item Number of Sales Document
Data type: VBAP-POSNRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VBAP - Item Work Area
Data type: VBAPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VBELN - SD Document Number
Data type: VBAP-VBELNDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VRGNG - Business Transaction
Data type: TJ01-VRGNGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_ALLOWED - Transaction not allowed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_FOUND - Object not found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SD_STATUS_VBAP_CHECK 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.DATA: | ||||
lv_i_objnr | TYPE VBAP-OBJNR, " SPACE | |||
lv_not_allowed | TYPE VBAP, " | |||
lv_i_posnr | TYPE VBAP-POSNR, " SPACE | |||
lv_object_not_found | TYPE VBAP, " | |||
lv_i_vbap | TYPE VBAP, " SPACE | |||
lv_i_vbeln | TYPE VBAP-VBELN, " SPACE | |||
lv_i_vrgng | TYPE TJ01-VRGNG. " SPACE |
  CALL FUNCTION 'SD_STATUS_VBAP_CHECK' "NOTRANSL: Prüfen eines Vorgangs anhand des Anwenderstatus |
EXPORTING | ||
I_OBJNR | = lv_i_objnr | |
I_POSNR | = lv_i_posnr | |
I_VBAP | = lv_i_vbap | |
I_VBELN | = lv_i_vbeln | |
I_VRGNG | = lv_i_vrgng | |
EXCEPTIONS | ||
NOT_ALLOWED = 1 | ||
OBJECT_NOT_FOUND = 2 | ||
. " SD_STATUS_VBAP_CHECK |
ABAP code using 7.40 inline data declarations to call FM SD_STATUS_VBAP_CHECK
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."SELECT single OBJNR FROM VBAP INTO @DATA(ld_i_objnr). | ||||
DATA(ld_i_objnr) | = ' '. | |||
"SELECT single POSNR FROM VBAP INTO @DATA(ld_i_posnr). | ||||
DATA(ld_i_posnr) | = ' '. | |||
DATA(ld_i_vbap) | = ' '. | |||
"SELECT single VBELN FROM VBAP INTO @DATA(ld_i_vbeln). | ||||
DATA(ld_i_vbeln) | = ' '. | |||
"SELECT single VRGNG FROM TJ01 INTO @DATA(ld_i_vrgng). | ||||
DATA(ld_i_vrgng) | = ' '. | |||
Search for further information about these or an SAP related objects