SAP QET4_SYNCHRONIZE_DATA Function Module for NOTRANSL: Positioniert in den Daten der Toolbox









QET4_SYNCHRONIZE_DATA is a standard qet4 synchronize data 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: Positioniert in den Daten der Toolbox 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 qet4 synchronize data FM, simply by entering the name QET4_SYNCHRONIZE_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function QET4_SYNCHRONIZE_DATA 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 'QET4_SYNCHRONIZE_DATA'"NOTRANSL: Positioniert in den Daten der Toolbox
  EXPORTING
   I_CELLS =  "

 IMPORTING
   XXXE_INSPLOT =  "
   E_DURING_POSTING =  "
   E_ISSKIP =  "
   E_ISDIRTY =  "Checkbox
   E_ISBLOCKED =  "Checkbox
   E_OPERATION =  "
   E_CHAR_REQUIREMENTS =  "
   E_CHAR_RESULT =  "
   E_SAMPLE_RESULT =  "
   E_INSP_POINT =  "
   E_INSP_POINT_REQUIREMENTS =  "
   E_INSP_LOT =  "
   E_LOCKED =  "
.



IMPORTING Parameters details for QET4_SYNCHRONIZE_DATA

I_CELLS -

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

EXPORTING Parameters details for QET4_SYNCHRONIZE_DATA

XXXE_INSPLOT -

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

E_DURING_POSTING -

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

E_ISSKIP -

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

E_ISDIRTY - Checkbox

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

E_ISBLOCKED - Checkbox

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

E_OPERATION -

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

E_CHAR_REQUIREMENTS -

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

E_CHAR_RESULT -

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

E_SAMPLE_RESULT -

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

E_INSP_POINT -

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

E_INSP_POINT_REQUIREMENTS -

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

E_INSP_LOT -

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

E_LOCKED -

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

Copy and paste ABAP code example for QET4_SYNCHRONIZE_DATA 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_cells  TYPE QETBCELLS, "   
lv_xxxe_insplot  TYPE BAPI2045L1, "   
lv_e_during_posting  TYPE QKZ, "   
lv_e_isskip  TYPE XFELD, "   
lv_e_isdirty  TYPE XFELD, "   
lv_e_isblocked  TYPE XFELD, "   
lv_e_operation  TYPE BAPI2045L2, "   
lv_e_char_requirements  TYPE BAPI2045D1, "   
lv_e_char_result  TYPE BAPI2045D2, "   
lv_e_sample_result  TYPE BAPI2045D3, "   
lv_e_insp_point  TYPE BAPI2045L4, "   
lv_e_insp_point_requirements  TYPE BAPI2045D5, "   
lv_e_insp_lot  TYPE BAPI2045D_IL0, "   
lv_e_locked  TYPE QKZ. "   

  CALL FUNCTION 'QET4_SYNCHRONIZE_DATA'  "NOTRANSL: Positioniert in den Daten der Toolbox
    EXPORTING
         I_CELLS = lv_i_cells
    IMPORTING
         XXXE_INSPLOT = lv_xxxe_insplot
         E_DURING_POSTING = lv_e_during_posting
         E_ISSKIP = lv_e_isskip
         E_ISDIRTY = lv_e_isdirty
         E_ISBLOCKED = lv_e_isblocked
         E_OPERATION = lv_e_operation
         E_CHAR_REQUIREMENTS = lv_e_char_requirements
         E_CHAR_RESULT = lv_e_char_result
         E_SAMPLE_RESULT = lv_e_sample_result
         E_INSP_POINT = lv_e_insp_point
         E_INSP_POINT_REQUIREMENTS = lv_e_insp_point_requirements
         E_INSP_LOT = lv_e_insp_lot
         E_LOCKED = lv_e_locked
. " QET4_SYNCHRONIZE_DATA




ABAP code using 7.40 inline data declarations to call FM QET4_SYNCHRONIZE_DATA

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



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!