SAP GET_VERIFICATION_PROFILE Function Module for Identify and get the verification profile









GET_VERIFICATION_PROFILE is a standard get verification profile SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Identify and get the verification profile 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 get verification profile FM, simply by entering the name GET_VERIFICATION_PROFILE into the relevant SAP transaction such as SE37 or SE38.

Function Group: LMOC
Program Name: SAPLLMOC
Main Program:
Appliation area: L
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function GET_VERIFICATION_PROFILE 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 'GET_VERIFICATION_PROFILE'"Identify and get the verification profile
EXPORTING
WHSEN = "Warehouse
* SOURCE = "Source storage type
* DESTIN = "Destination storage type
* MVTTYP = "Movement type
* PROFIL = "Verification profile

IMPORTING
E_T313A = "Determination of Verification Profile
E_T313B = "Definition of Verification Profile

EXCEPTIONS
PARAMETER_INCONSISTENCY = 1 MISSING_T313A_ENTRY = 2 MISSING_T313B_ENTRY = 3
.




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_SAPLLMOC_001 Influence material description

IMPORTING Parameters details for GET_VERIFICATION_PROFILE

WHSEN - Warehouse

Data type: T313A-LGNUM
Optional: No
Call by Reference: No ( called with pass by value option)

SOURCE - Source storage type

Data type: T313A-VLTYP
Optional: Yes
Call by Reference: No ( called with pass by value option)

DESTIN - Destination storage type

Data type: T313A-NLTYP
Optional: Yes
Call by Reference: No ( called with pass by value option)

MVTTYP - Movement type

Data type: T313A-BWLVS
Optional: Yes
Call by Reference: No ( called with pass by value option)

PROFIL - Verification profile

Data type: T313A-PROFI
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for GET_VERIFICATION_PROFILE

E_T313A - Determination of Verification Profile

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

E_T313B - Definition of Verification Profile

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

EXCEPTIONS details

PARAMETER_INCONSISTENCY -

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

MISSING_T313A_ENTRY -

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

MISSING_T313B_ENTRY -

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

Copy and paste ABAP code example for GET_VERIFICATION_PROFILE 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_whsen  TYPE T313A-LGNUM, "   
lv_e_t313a  TYPE T313A, "   
lv_parameter_inconsistency  TYPE T313A, "   
lv_source  TYPE T313A-VLTYP, "   
lv_e_t313b  TYPE T313B, "   
lv_missing_t313a_entry  TYPE T313B, "   
lv_destin  TYPE T313A-NLTYP, "   
lv_missing_t313b_entry  TYPE T313A, "   
lv_mvttyp  TYPE T313A-BWLVS, "   
lv_profil  TYPE T313A-PROFI. "   

  CALL FUNCTION 'GET_VERIFICATION_PROFILE'  "Identify and get the verification profile
    EXPORTING
         WHSEN = lv_whsen
         SOURCE = lv_source
         DESTIN = lv_destin
         MVTTYP = lv_mvttyp
         PROFIL = lv_profil
    IMPORTING
         E_T313A = lv_e_t313a
         E_T313B = lv_e_t313b
    EXCEPTIONS
        PARAMETER_INCONSISTENCY = 1
        MISSING_T313A_ENTRY = 2
        MISSING_T313B_ENTRY = 3
. " GET_VERIFICATION_PROFILE




ABAP code using 7.40 inline data declarations to call FM GET_VERIFICATION_PROFILE

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 LGNUM FROM T313A INTO @DATA(ld_whsen).
 
 
 
"SELECT single VLTYP FROM T313A INTO @DATA(ld_source).
 
 
 
"SELECT single NLTYP FROM T313A INTO @DATA(ld_destin).
 
 
"SELECT single BWLVS FROM T313A INTO @DATA(ld_mvttyp).
 
"SELECT single PROFI FROM T313A INTO @DATA(ld_profil).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!