SAP J_7L_VRPNR_CHECK Function Module for NOTRANSL: REA Verpackung Prüfung
J_7L_VRPNR_CHECK is a standard j 7l vrpnr 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: REA Verpackung Prüfung 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 j 7l vrpnr check FM, simply by entering the name J_7L_VRPNR_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: J7LC
Program Name: SAPLJ7LC
Main Program: SAPLJ7LC
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function J_7L_VRPNR_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 'J_7L_VRPNR_CHECK'"NOTRANSL: REA Verpackung Prüfung.
EXPORTING
VRPNR = "Packaging
* ENTNR = "Recycling Partner
* BUKRS = "Company Code
* LAND1 = "Country Key
* DATAB = "Valid-From Date
* DATBI = "Valid To Date
* DELETE = "Deletion Indicator
* ACTIVATE = "Active Indicator for Packaging
* DEACTIVATE = "Active Indicator for Packaging
EXCEPTIONS
VRPNR_NOT_FOUND = 1 AKTION_NOT_FOUND = 2 DELETE_ERROR = 3 ACTIVATE_ERROR = 4 DEACTIVATE_ERROR = 5 ENTNR_NOT_FOUND = 6
IMPORTING Parameters details for J_7L_VRPNR_CHECK
VRPNR - Packaging
Data type: J_7LV01-VRPNROptional: No
Call by Reference: Yes
ENTNR - Recycling Partner
Data type: J_7LV03-ENTNROptional: Yes
Call by Reference: Yes
BUKRS - Company Code
Data type: J_7LV03-BUKRSOptional: Yes
Call by Reference: Yes
LAND1 - Country Key
Data type: J_7LV03-LAND1Optional: Yes
Call by Reference: Yes
DATAB - Valid-From Date
Data type: J_7LV02-DATABOptional: Yes
Call by Reference: Yes
DATBI - Valid To Date
Data type: J_7LV02-DATBIOptional: Yes
Call by Reference: Yes
DELETE - Deletion Indicator
Data type: J_7LV01-LVORMADMOptional: Yes
Call by Reference: Yes
ACTIVATE - Active Indicator for Packaging
Data type: J_7LV03-VAKTIVKZOptional: Yes
Call by Reference: Yes
DEACTIVATE - Active Indicator for Packaging
Data type: J_7LV03-VAKTIVKZOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
VRPNR_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
AKTION_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DELETE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ACTIVATE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DEACTIVATE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENTNR_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for J_7L_VRPNR_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_vrpnr | TYPE J_7LV01-VRPNR, " | |||
| lv_vrpnr_not_found | TYPE J_7LV01, " | |||
| lv_entnr | TYPE J_7LV03-ENTNR, " | |||
| lv_aktion_not_found | TYPE J_7LV03, " | |||
| lv_bukrs | TYPE J_7LV03-BUKRS, " | |||
| lv_delete_error | TYPE J_7LV03, " | |||
| lv_land1 | TYPE J_7LV03-LAND1, " | |||
| lv_activate_error | TYPE J_7LV03, " | |||
| lv_datab | TYPE J_7LV02-DATAB, " | |||
| lv_deactivate_error | TYPE J_7LV02, " | |||
| lv_datbi | TYPE J_7LV02-DATBI, " | |||
| lv_entnr_not_found | TYPE J_7LV02, " | |||
| lv_delete | TYPE J_7LV01-LVORMADM, " | |||
| lv_activate | TYPE J_7LV03-VAKTIVKZ, " | |||
| lv_deactivate | TYPE J_7LV03-VAKTIVKZ. " |
|   CALL FUNCTION 'J_7L_VRPNR_CHECK' "NOTRANSL: REA Verpackung Prüfung |
| EXPORTING | ||
| VRPNR | = lv_vrpnr | |
| ENTNR | = lv_entnr | |
| BUKRS | = lv_bukrs | |
| LAND1 | = lv_land1 | |
| DATAB | = lv_datab | |
| DATBI | = lv_datbi | |
| DELETE | = lv_delete | |
| ACTIVATE | = lv_activate | |
| DEACTIVATE | = lv_deactivate | |
| EXCEPTIONS | ||
| VRPNR_NOT_FOUND = 1 | ||
| AKTION_NOT_FOUND = 2 | ||
| DELETE_ERROR = 3 | ||
| ACTIVATE_ERROR = 4 | ||
| DEACTIVATE_ERROR = 5 | ||
| ENTNR_NOT_FOUND = 6 | ||
| . " J_7L_VRPNR_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM J_7L_VRPNR_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 VRPNR FROM J_7LV01 INTO @DATA(ld_vrpnr). | ||||
| "SELECT single ENTNR FROM J_7LV03 INTO @DATA(ld_entnr). | ||||
| "SELECT single BUKRS FROM J_7LV03 INTO @DATA(ld_bukrs). | ||||
| "SELECT single LAND1 FROM J_7LV03 INTO @DATA(ld_land1). | ||||
| "SELECT single DATAB FROM J_7LV02 INTO @DATA(ld_datab). | ||||
| "SELECT single DATBI FROM J_7LV02 INTO @DATA(ld_datbi). | ||||
| "SELECT single LVORMADM FROM J_7LV01 INTO @DATA(ld_delete). | ||||
| "SELECT single VAKTIVKZ FROM J_7LV03 INTO @DATA(ld_activate). | ||||
| "SELECT single VAKTIVKZ FROM J_7LV03 INTO @DATA(ld_deactivate). | ||||
Search for further information about these or an SAP related objects