SAP EXIT_SAPLQUOT_001 Function Module for User Exit: SD Product Allocation, Enhanced Checks
EXIT_SAPLQUOT_001 is a standard exit saplquot 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 User Exit: SD Product Allocation, Enhanced Checks 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 saplquot 001 FM, simply by entering the name EXIT_SAPLQUOT_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XVZ1
Program Name: SAPLXVZ1
Main Program:
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function EXIT_SAPLQUOT_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_SAPLQUOT_001'"User Exit: SD Product Allocation, Enhanced Checks.
EXPORTING
EXIT_001_I_POSNR = "Checked Item in Order
EXIT_001_I_MATNR = "Material Number from the Order
EXIT_001_I_KOSCH = "Product Allocation Determination Procedure (Standard)
EXIT_001_I_GSTRU = "Info Structure (Standard)
IMPORTING
EXIT_001_E_KOSCH = "New Product Allocation Determination Procedure (Mod) If Necessary
EXIT_001_E_GSTRU = "New Product Allocation Object (Mod) If Necessary
EXIT_001_E_AFLAG = "Activity after the User Exit
TABLES
EXIT_001_T_MDVEX = "Product Allocation: Availability
* EXIT_001_T_OLDQT = "Product Allocation: Comm. Structure For DB Change
EXIT_001_T_QTKEY = "Key Fields of the Info Structure
* EXIT_001_T_QTCOR = "Correct Quantities
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.QUOTA_ALLOCATION_INIT NOTRANSL: ATP_C:Initialisierung der Kontingentierung; Customizingeinstellu
QUOTA_CHECK NOTRANSL: CUST: Überprüfung einer Kontingentierungseinstellung
QUOTA_CHECK_STRUCT NOTRANSL: CUST: Überprüfung ob Info-Struktur für die Kontingentierung geei
QUOTA_DATE_CHECK NOTRANSL: CUST: Kontrolle des Datums: Ende einer Periode
QUOTA_DISPLAY_CHECK_RESULTS NOTRANSL: ATP_D:Anzeige von ATP und Kontingenten
QUOTA_DISPLAY_INIT ATP_D: Prepare display of used product allocation in the order
QUOTA_DISPLAY_RESULTS_ATP NOTRANSL: ATP_D:Kontingentierungsereignisse vom ATP-Server abholen
QUOTA_INFO_CONTENT NOTRANSL: CUST: Info-Struktur mit allg. Hierarchie bearbeiten (Sammelkonti
QUOTA_MASK_GET NOTRANSL: CUST: Maskenzeichen der Struktur liefern
QUOTA_OBJECT_FIND NOTRANSL: ATP_C:Merkmalskombinationen für den ATP-Server abstrahieren
QUOTA_ORDER_DATA_READ NOTRANSL: ATP_C:Anwendung: Merkmalswerte aus dem Auftrag bestimmen
QUOTA_PERIODS_DETERMINE NOTRANSL: ATP_C:Periode eines Datums bestimmen
QUOTA_QUANTITY_CHECK NOTRANSL: ATP_S:Freie Kontingente für Kunde/Material bestimmen
QUOTA_QUANTITY_CHECK_ATP NOTRANSL: ATP_S:Freie Kontingente für Kunde/Material bestimmen
QUOTA_SHARED_BUFFER_DELETE NOTRANSL: INIT: Periodentabelle wird aus dem Shared Buffer gelöscht
QUOTA_VECTOR_CALC NOTRANSL: PLAN: Verrechung der Kontingentbelegung in Zeitintervall für fle
IMPORTING Parameters details for EXIT_SAPLQUOT_001
EXIT_001_I_POSNR - Checked Item in Order
Data type: VBAP-POSNROptional: No
Call by Reference: No ( called with pass by value option)
EXIT_001_I_MATNR - Material Number from the Order
Data type: VBAP-MATNROptional: No
Call by Reference: No ( called with pass by value option)
EXIT_001_I_KOSCH - Product Allocation Determination Procedure (Standard)
Data type: T190-KOSCHOptional: No
Call by Reference: No ( called with pass by value option)
EXIT_001_I_GSTRU - Info Structure (Standard)
Data type: IV03V-GSTRUOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPLQUOT_001
EXIT_001_E_KOSCH - New Product Allocation Determination Procedure (Mod) If Necessary
Data type: T190-KOSCHOptional: No
Call by Reference: No ( called with pass by value option)
EXIT_001_E_GSTRU - New Product Allocation Object (Mod) If Necessary
Data type: IV03V-GSTRUOptional: No
Call by Reference: No ( called with pass by value option)
EXIT_001_E_AFLAG - Activity after the User Exit
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLQUOT_001
EXIT_001_T_MDVEX - Product Allocation: Availability
Data type: QUOT03Optional: No
Call by Reference: No ( called with pass by value option)
EXIT_001_T_OLDQT - Product Allocation: Comm. Structure For DB Change
Data type: QUOT04Optional: Yes
Call by Reference: No ( called with pass by value option)
EXIT_001_T_QTKEY - Key Fields of the Info Structure
Data type: QV03VOptional: No
Call by Reference: No ( called with pass by value option)
EXIT_001_T_QTCOR - Correct Quantities
Data type: QUOTCOROptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLQUOT_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: | ||||
lv_exit_001_e_kosch | TYPE T190-KOSCH, " | |||
lv_exit_001_i_posnr | TYPE VBAP-POSNR, " | |||
lt_exit_001_t_mdvex | TYPE STANDARD TABLE OF QUOT03, " | |||
lv_exit_001_e_gstru | TYPE IV03V-GSTRU, " | |||
lv_exit_001_i_matnr | TYPE VBAP-MATNR, " | |||
lt_exit_001_t_oldqt | TYPE STANDARD TABLE OF QUOT04, " | |||
lv_exit_001_e_aflag | TYPE C, " | |||
lv_exit_001_i_kosch | TYPE T190-KOSCH, " | |||
lt_exit_001_t_qtkey | TYPE STANDARD TABLE OF QV03V, " | |||
lv_exit_001_i_gstru | TYPE IV03V-GSTRU, " | |||
lt_exit_001_t_qtcor | TYPE STANDARD TABLE OF QUOTCOR. " |
  CALL FUNCTION 'EXIT_SAPLQUOT_001' "User Exit: SD Product Allocation, Enhanced Checks |
EXPORTING | ||
EXIT_001_I_POSNR | = lv_exit_001_i_posnr | |
EXIT_001_I_MATNR | = lv_exit_001_i_matnr | |
EXIT_001_I_KOSCH | = lv_exit_001_i_kosch | |
EXIT_001_I_GSTRU | = lv_exit_001_i_gstru | |
IMPORTING | ||
EXIT_001_E_KOSCH | = lv_exit_001_e_kosch | |
EXIT_001_E_GSTRU | = lv_exit_001_e_gstru | |
EXIT_001_E_AFLAG | = lv_exit_001_e_aflag | |
TABLES | ||
EXIT_001_T_MDVEX | = lt_exit_001_t_mdvex | |
EXIT_001_T_OLDQT | = lt_exit_001_t_oldqt | |
EXIT_001_T_QTKEY | = lt_exit_001_t_qtkey | |
EXIT_001_T_QTCOR | = lt_exit_001_t_qtcor | |
. " EXIT_SAPLQUOT_001 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLQUOT_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 KOSCH FROM T190 INTO @DATA(ld_exit_001_e_kosch). | ||||
"SELECT single POSNR FROM VBAP INTO @DATA(ld_exit_001_i_posnr). | ||||
"SELECT single GSTRU FROM IV03V INTO @DATA(ld_exit_001_e_gstru). | ||||
"SELECT single MATNR FROM VBAP INTO @DATA(ld_exit_001_i_matnr). | ||||
"SELECT single KOSCH FROM T190 INTO @DATA(ld_exit_001_i_kosch). | ||||
"SELECT single GSTRU FROM IV03V INTO @DATA(ld_exit_001_i_gstru). | ||||
Search for further information about these or an SAP related objects