SAP QLCO_CONFIRMATION_START Function Module for NOTRANSL: Rückmelden Vorgang ausführen. Trennung zwischen QM und PP Auftra

Search SAP Function Modules

QLCO_CONFIRMATION_START is a standard qlco confirmation start 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: Rückmelden Vorgang ausführen. Trennung zwischen QM und PP Auftra 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 qlco confirmation start FM, simply by entering the name QLCO_CONFIRMATION_START into the relevant SAP transaction such as SE37 or SE38.

Function Group: QLCO
Program Name: SAPLQLCO
Main Program: SAPLQLCO
Appliation area: Q
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function QLCO_CONFIRMATION_START 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 'QLCO_CONFIRMATION_START'"NOTRANSL: Rückmelden Vorgang ausführen. Trennung zwischen QM und PP Auftra
  EXPORTING
   I_PLNFL =  "Sequence number
   I_VORNR =  "Operation number
   I_QALS =  "Inspection lot
   I_RUECK =  "Confirmation number of the operation

 IMPORTING
   E_UPD_FLAG =  "Ind. change to database required

EXCEPTIONS
   NO_CONF_REQUIRED = 1 

.

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_SAPLQLCO_001 Altenative Cost Report for QM Order
EXIT_SAPLQLCO_002 Activities Confirmation Default Values for QM Order

IMPORTING Parameters details for QLCO_CONFIRMATION_START

I_PLNFL - Sequence number

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

I_VORNR - Operation number

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

I_QALS - Inspection lot

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

I_RUECK - Confirmation number of the operation

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

EXPORTING Parameters details for QLCO_CONFIRMATION_START

E_UPD_FLAG - Ind. change to database required

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

EXCEPTIONS details

NO_CONF_REQUIRED - Confirmation not possible

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

Copy and paste ABAP code example for QLCO_CONFIRMATION_START 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.

ABAP code using 7.40 inline data declarations to call FM QLCO_CONFIRMATION_START

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