SAP EXIT_SAPLXGV1_001 Function Module for Customer exit for customer hierarchy eligibility check
EXIT_SAPLXGV1_001 is a standard exit saplxgv1 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Customer exit for customer hierarchy eligibility check 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 exit saplxgv1 001 FM, simply by entering the name EXIT_SAPLXGV1_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XGV1
Program Name: SAPLXGV1
Main Program: SAPLXGV1
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPLXGV1_001 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 'EXIT_SAPLXGV1_001'"Customer exit for customer hierarchy eligibility check.
EXPORTING
CUSTOMER = "
DATE = "
HTYPE = "
SALES_CHANNEL = "
SALES_DIVISION = "
SALES_ORG = "
TABLES
HPATH = "
EXCEPTIONS
EXCEPTION_1 = 1 EXCEPTION_2 = 2 EXCEPTION_3 = 3
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.EXIT_SAPLV45C_403 Customer exit for enterprise contract hierarchy processing
EXIT_SAPLXGV1_001 Customer exit for customer hierarchy eligibility check
IMPORTING Parameters details for EXIT_SAPLXGV1_001
CUSTOMER -
Data type: KUAGV-KUNNROptional: No
Call by Reference: No ( called with pass by value option)
DATE -
Data type: VBAK-VDATUOptional: No
Call by Reference: No ( called with pass by value option)
HTYPE -
Data type: TVAK-HITYP_PROptional: No
Call by Reference: No ( called with pass by value option)
SALES_CHANNEL -
Data type: VBAK-VTWEGOptional: No
Call by Reference: No ( called with pass by value option)
SALES_DIVISION -
Data type: VBAK-SPARTOptional: No
Call by Reference: No ( called with pass by value option)
SALES_ORG -
Data type: VBAK-VKORGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLXGV1_001
HPATH -
Data type: VBPAVBOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
EXCEPTION_1 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTION_2 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTION_3 -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLXGV1_001 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: | ||||
lt_hpath | TYPE STANDARD TABLE OF VBPAVB, " | |||
lv_customer | TYPE KUAGV-KUNNR, " | |||
lv_exception_1 | TYPE KUAGV, " | |||
lv_date | TYPE VBAK-VDATU, " | |||
lv_exception_2 | TYPE VBAK, " | |||
lv_htype | TYPE TVAK-HITYP_PR, " | |||
lv_exception_3 | TYPE TVAK, " | |||
lv_sales_channel | TYPE VBAK-VTWEG, " | |||
lv_sales_division | TYPE VBAK-SPART, " | |||
lv_sales_org | TYPE VBAK-VKORG. " |
  CALL FUNCTION 'EXIT_SAPLXGV1_001' "Customer exit for customer hierarchy eligibility check |
EXPORTING | ||
CUSTOMER | = lv_customer | |
DATE | = lv_date | |
HTYPE | = lv_htype | |
SALES_CHANNEL | = lv_sales_channel | |
SALES_DIVISION | = lv_sales_division | |
SALES_ORG | = lv_sales_org | |
TABLES | ||
HPATH | = lt_hpath | |
EXCEPTIONS | ||
EXCEPTION_1 = 1 | ||
EXCEPTION_2 = 2 | ||
EXCEPTION_3 = 3 | ||
. " EXIT_SAPLXGV1_001 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLXGV1_001
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 KUNNR FROM KUAGV INTO @DATA(ld_customer). | ||||
"SELECT single VDATU FROM VBAK INTO @DATA(ld_date). | ||||
"SELECT single HITYP_PR FROM TVAK INTO @DATA(ld_htype). | ||||
"SELECT single VTWEG FROM VBAK INTO @DATA(ld_sales_channel). | ||||
"SELECT single SPART FROM VBAK INTO @DATA(ld_sales_division). | ||||
"SELECT single VKORG FROM VBAK INTO @DATA(ld_sales_org). | ||||
Search for further information about these or an SAP related objects