SAP QEEM_UNPLANNED_CHARACTERISTICS Function Module for NOTRANSL: Anlegen zusätzlicher Prüfmerkmale zum Auftrag









QEEM_UNPLANNED_CHARACTERISTICS is a standard qeem unplanned characteristics 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: Anlegen zusätzlicher Prüfmerkmale zum Auftrag 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 qeem unplanned characteristics FM, simply by entering the name QEEM_UNPLANNED_CHARACTERISTICS into the relevant SAP transaction such as SE37 or SE38.

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



Function QEEM_UNPLANNED_CHARACTERISTICS 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 'QEEM_UNPLANNED_CHARACTERISTICS'"NOTRANSL: Anlegen zusätzlicher Prüfmerkmale zum Auftrag
EXPORTING
I_PRUEFLOS = "Inspection lot
* I_AFVGD = "Work area for the operation
* I_VORNR = ' ' "External operation number
* I_ONLY_DEFINE_NEW_CHAR = 'X' "Indicator: no recording, only define new characteristics
* I_BLOCK_LOT_BY_QM = ' ' "Indicator: inspection lot is blocked by QM module

IMPORTING
E_SICHERN_FLAG = "Indicator: data ready to be saved

EXCEPTIONS
LOT_DOES_NOT_EXIST = 1 LOT_WITH_WRONG_STATUS = 2 INTERNAL_ERROR_CHARACTERISTICS = 3 PROC_OF_OPERATION_NOT_ALLOWED = 4
.




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_SAPLQEEM_001 Customer Function for Calculating Formulas in Results Recording
EXIT_SAPLQEEM_002 Customer Function: Add. Fns for Importing Insp. Chars in Results Recording
EXIT_SAPLQEEM_003 Customer Function: Add. Functions After Valuating Insp. Characteristics
EXIT_SAPLQEEM_004 Customer Function: Add. Functions After Valuating Partial Samples
EXIT_SAPLQEEM_006 Customer Function: Add. Functions After Closing Insp. Characteristics
EXIT_SAPLQEEM_007 Customer Exit: Additional Functions After Closing Partial Samples
EXIT_SAPLQEEM_011 Customer Function: Add. Functions Before Valuating Insp. Characteristics
EXIT_SAPLQEEM_012 Customer Function: Additional Functions Before Valuating Partial Samples
EXIT_SAPLQEEM_015 Customer Function: Add. Functions After Entering Individual Results
EXIT_SAPLQEEM_020 Customer Function: Additional Functions After Entering Inspector
EXIT_SAPLQEEM_021 Customer Function: Add. Functions for User Key +US1 (Char. Single Screen)
EXIT_SAPLQEEM_022 Customer Function: Add. Functions for User Key +US2 (Char. Single Screen)
EXIT_SAPLQEEM_023 Customer Function: Add. Functions for User Key +US3 (Char. Single Screen)
EXIT_SAPLQEEM_024 Customer Function: Add. Functions for User Key +US4 (Char. Single Screen)
EXIT_SAPLQEEM_025 Customer Function: Add. Functions for User Key +US1 as Pushbutton
EXIT_SAPLQEEM_026 Customer Function: Add. Functions for User Key +US2 as Pushbutton
EXIT_SAPLQEEM_027 Customer Function: Add. Functions for User Key +US3 as Pushbutton
EXIT_SAPLQEEM_028 Customer Function: Add. Functions for User Key +US4 as Pushbutton
EXIT_SAPLQEEM_029 Customer-Function for Subscreen Characteristic Overview
EXIT_SAPLQEEM_030 Customer Function for Subscreen Characteristic Single Screen
EXIT_SAPLQEEM_031 Customer Function Creating Table with External Numbers
EXIT_SAPLQEEM_032 Customer Function Characteristic Text in Logon Language

IMPORTING Parameters details for QEEM_UNPLANNED_CHARACTERISTICS

I_PRUEFLOS - Inspection lot

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

I_AFVGD - Work area for the operation

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

I_VORNR - External operation number

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

I_ONLY_DEFINE_NEW_CHAR - Indicator: no recording, only define new characteristics

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

I_BLOCK_LOT_BY_QM - Indicator: inspection lot is blocked by QM module

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

EXPORTING Parameters details for QEEM_UNPLANNED_CHARACTERISTICS

E_SICHERN_FLAG - Indicator: data ready to be saved

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

EXCEPTIONS details

LOT_DOES_NOT_EXIST -

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

LOT_WITH_WRONG_STATUS -

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

INTERNAL_ERROR_CHARACTERISTICS -

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

PROC_OF_OPERATION_NOT_ALLOWED - Operation not allowed

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

Copy and paste ABAP code example for QEEM_UNPLANNED_CHARACTERISTICS 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_i_prueflos  TYPE QALS-PRUEFLOS, "   
lv_e_sichern_flag  TYPE QM00-QKZ, "   
lv_lot_does_not_exist  TYPE QM00, "   
lv_i_afvgd  TYPE AFVGD, "   
lv_lot_with_wrong_status  TYPE AFVGD, "   
lv_i_vornr  TYPE QAPO-VORNR, "   SPACE
lv_internal_error_characteristics  TYPE QAPO, "   
lv_i_only_define_new_char  TYPE QM00-QKZ, "   'X'
lv_proc_of_operation_not_allowed  TYPE QM00, "   
lv_i_block_lot_by_qm  TYPE QM00-QKZ. "   SPACE

  CALL FUNCTION 'QEEM_UNPLANNED_CHARACTERISTICS'  "NOTRANSL: Anlegen zusätzlicher Prüfmerkmale zum Auftrag
    EXPORTING
         I_PRUEFLOS = lv_i_prueflos
         I_AFVGD = lv_i_afvgd
         I_VORNR = lv_i_vornr
         I_ONLY_DEFINE_NEW_CHAR = lv_i_only_define_new_char
         I_BLOCK_LOT_BY_QM = lv_i_block_lot_by_qm
    IMPORTING
         E_SICHERN_FLAG = lv_e_sichern_flag
    EXCEPTIONS
        LOT_DOES_NOT_EXIST = 1
        LOT_WITH_WRONG_STATUS = 2
        INTERNAL_ERROR_CHARACTERISTICS = 3
        PROC_OF_OPERATION_NOT_ALLOWED = 4
. " QEEM_UNPLANNED_CHARACTERISTICS




ABAP code using 7.40 inline data declarations to call FM QEEM_UNPLANNED_CHARACTERISTICS

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 PRUEFLOS FROM QALS INTO @DATA(ld_i_prueflos).
 
"SELECT single QKZ FROM QM00 INTO @DATA(ld_e_sichern_flag).
 
 
 
 
"SELECT single VORNR FROM QAPO INTO @DATA(ld_i_vornr).
DATA(ld_i_vornr) = ' '.
 
 
"SELECT single QKZ FROM QM00 INTO @DATA(ld_i_only_define_new_char).
DATA(ld_i_only_define_new_char) = 'X'.
 
 
"SELECT single QKZ FROM QM00 INTO @DATA(ld_i_block_lot_by_qm).
DATA(ld_i_block_lot_by_qm) = ' '.
 


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!