SAP EXIT_SAPLQSMT_021 Function Module for Customer Enhancement: Create IDocs (Replicated BAPI Inspection Method)
EXIT_SAPLQSMT_021 is a standard exit saplqsmt 021 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 Enhancement: Create IDocs (Replicated BAPI Inspection Method) 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 saplqsmt 021 FM, simply by entering the name EXIT_SAPLQSMT_021 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XQSMT
Program Name: SAPLXQSMT
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLQSMT_021 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_SAPLQSMT_021'"Customer Enhancement: Create IDocs (Replicated BAPI Inspection Method).
TABLES
T_INSP_METHOD = "Inspection Method Master Record
T_SHORTTEXTTAB = "Short Text Table for Inspection Methods
* T_LONGTEXTTAB = "Long Text Lines for Inspection Methods
* T_EXTENSION1 = "Container for 'Customer Exit' Parameter
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ALE_QMTB_SAVEREPLICA NOTRANSL: BAPI -> IDoc: ALE_QMTB_SAVEREPLICA
BAPI_QMTB_REPLICATE Prepare QM Inspection Methods for Distribution
BAPI_QMTB_SAVEREPLICA Replication of QM Inspection Methods
IDOC_INPUT_QSMT NOTRANSL: IDoc -> BAPI: IDOC_INPUT_QSMT
MAP2E_QMTB_TO_BAPIQMTB_QMTB NOTRANSL: qmtb -> bapiqmtb_qmtb
MAP2E_QMTT_TO_BAPIQMTB_QMTT NOTRANSL: qmtt -> bapiqmtb_qmtt
MAP2E_QPMLTXT_TO_BAPIQMTB_LONG NOTRANSL: qpmltxt -> bapiqmtb_longtext
MAP2I_BAPIQMTB_LONGTEXT_TO_QPM NOTRANSL: bapiqmtb_longtext -> qpmltxt
MAP2I_BAPIQMTB_QMTB_TO_QMTB NOTRANSL: bapiqmtb_qmtb -> qmtb
MAP2I_BAPIQMTB_QMTT_TO_QPMKTXT NOTRANSL: bapiqmtb_qmtt -> qpmktxt
QSMT_INSP_METH_DATE_DELETE NOTRANSL: Gültigkeitsstand einer Prüfmethode löschen
QSMT_INSP_METH_POST NOTRANSL: Verbuchungsbaustein für Prüfmethoden (QMTB)
QSMT_INSP_METH_TEXT_POST NOTRANSL: Verbuchungsbaustein für die Texte einer Prüfmethode (QMTB)
QSMT_INSP_METH_VERS_CHANGE NOTRANSL: Version einer Prüfmethode ändern
QSMT_INSP_METH_VERS_CREATE NOTRANSL: Version einer Prüfmethode vollständig anlegen
QSMT_INSP_METH_VERS_DELETE NOTRANSL: Version einer Prüfmethode löschen
TABLES Parameters details for EXIT_SAPLQSMT_021
T_INSP_METHOD - Inspection Method Master Record
Data type: QMTBOptional: No
Call by Reference: Yes
T_SHORTTEXTTAB - Short Text Table for Inspection Methods
Data type: QMTTOptional: No
Call by Reference: Yes
T_LONGTEXTTAB - Long Text Lines for Inspection Methods
Data type: QPMLTXTOptional: Yes
Call by Reference: No ( called with pass by value option)
T_EXTENSION1 - Container for 'Customer Exit' Parameter
Data type: BAPIEXTCOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPLQSMT_021 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_t_insp_method | TYPE STANDARD TABLE OF QMTB, " | |||
| lt_t_shorttexttab | TYPE STANDARD TABLE OF QMTT, " | |||
| lt_t_longtexttab | TYPE STANDARD TABLE OF QPMLTXT, " | |||
| lt_t_extension1 | TYPE STANDARD TABLE OF BAPIEXTC. " |
|   CALL FUNCTION 'EXIT_SAPLQSMT_021' "Customer Enhancement: Create IDocs (Replicated BAPI Inspection Method) |
| TABLES | ||
| T_INSP_METHOD | = lt_t_insp_method | |
| T_SHORTTEXTTAB | = lt_t_shorttexttab | |
| T_LONGTEXTTAB | = lt_t_longtexttab | |
| T_EXTENSION1 | = lt_t_extension1 | |
| . " EXIT_SAPLQSMT_021 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLQSMT_021
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.Search for further information about these or an SAP related objects