SAP J_3G_CHECK_MACHINE_REPORT Function Module for Check Whether Shipping Document Collides With Operator's Report









J_3G_CHECK_MACHINE_REPORT is a standard j 3g check machine report SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Whether Shipping Document Collides With Operator's Report 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 j 3g check machine report FM, simply by entering the name J_3G_CHECK_MACHINE_REPORT into the relevant SAP transaction such as SE37 or SE38.

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



Function J_3G_CHECK_MACHINE_REPORT 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 'J_3G_CHECK_MACHINE_REPORT'"Check Whether Shipping Document Collides With Operator's Report
  EXPORTING
   I_ALT_J_3GEMPFAE =  "
   I_NEU_J_3GEMPDEB =  "
   I_NEU_J_3GEMPEXT =  "
   I_ALT_J_3GEMPDEB =  "
   I_ALT_J_3GEMPEXT =  "
   I_ALT_J_3GBELDAT =  "
   I_NEU_J_3GABSEND =  "
   I_NEU_J_3GABSDEB =  "
   I_NEU_J_3GABSEXT =  "
   I_NEU_J_3GBELDAT =  "
   I_NEU_J_3GEMPFAE =  "

TABLES
   T_BELP_ALT =  "
   T_BELP_NEU =  "

EXCEPTIONS
   MACHINE_REPORT_SENDER_EXISTS = 1    MACHINE_REPORT_RECEIVER_EXISTS = 2
.



IMPORTING Parameters details for J_3G_CHECK_MACHINE_REPORT

I_ALT_J_3GEMPFAE -

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

I_NEU_J_3GEMPDEB -

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

I_NEU_J_3GEMPEXT -

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

I_ALT_J_3GEMPDEB -

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

I_ALT_J_3GEMPEXT -

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

I_ALT_J_3GBELDAT -

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

I_NEU_J_3GABSEND -

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

I_NEU_J_3GABSDEB -

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

I_NEU_J_3GABSEXT -

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

I_NEU_J_3GBELDAT -

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

I_NEU_J_3GEMPFAE -

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

TABLES Parameters details for J_3G_CHECK_MACHINE_REPORT

T_BELP_ALT -

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

T_BELP_NEU -

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

EXCEPTIONS details

MACHINE_REPORT_SENDER_EXISTS -

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

MACHINE_REPORT_RECEIVER_EXISTS -

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

Copy and paste ABAP code example for J_3G_CHECK_MACHINE_REPORT 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_belp_alt  TYPE STANDARD TABLE OF J_3GBELPS, "   
lv_i_alt_j_3gempfae  TYPE J_3GBELK-J_3GEMPFAE, "   
lv_machine_report_sender_exists  TYPE J_3GBELK, "   
lv_i_neu_j_3gempdeb  TYPE J_3GBELK-J_3GEMPDEB, "   
lv_i_neu_j_3gempext  TYPE J_3GBELK-J_3GEMPEXT, "   
lt_t_belp_neu  TYPE STANDARD TABLE OF J_3GBELPS, "   
lv_i_alt_j_3gempdeb  TYPE J_3GBELK-J_3GEMPDEB, "   
lv_machine_report_receiver_exists  TYPE J_3GBELK, "   
lv_i_alt_j_3gempext  TYPE J_3GBELK-J_3GEMPEXT, "   
lv_i_alt_j_3gbeldat  TYPE J_3GBELK-J_3GBELDAT, "   
lv_i_neu_j_3gabsend  TYPE J_3GBELK-J_3GEMPFAE, "   
lv_i_neu_j_3gabsdeb  TYPE J_3GBELK-J_3GEMPDEB, "   
lv_i_neu_j_3gabsext  TYPE J_3GBELK-J_3GEMPEXT, "   
lv_i_neu_j_3gbeldat  TYPE J_3GBELK-J_3GBELDAT, "   
lv_i_neu_j_3gempfae  TYPE J_3GBELK-J_3GEMPFAE. "   

  CALL FUNCTION 'J_3G_CHECK_MACHINE_REPORT'  "Check Whether Shipping Document Collides With Operator's Report
    EXPORTING
         I_ALT_J_3GEMPFAE = lv_i_alt_j_3gempfae
         I_NEU_J_3GEMPDEB = lv_i_neu_j_3gempdeb
         I_NEU_J_3GEMPEXT = lv_i_neu_j_3gempext
         I_ALT_J_3GEMPDEB = lv_i_alt_j_3gempdeb
         I_ALT_J_3GEMPEXT = lv_i_alt_j_3gempext
         I_ALT_J_3GBELDAT = lv_i_alt_j_3gbeldat
         I_NEU_J_3GABSEND = lv_i_neu_j_3gabsend
         I_NEU_J_3GABSDEB = lv_i_neu_j_3gabsdeb
         I_NEU_J_3GABSEXT = lv_i_neu_j_3gabsext
         I_NEU_J_3GBELDAT = lv_i_neu_j_3gbeldat
         I_NEU_J_3GEMPFAE = lv_i_neu_j_3gempfae
    TABLES
         T_BELP_ALT = lt_t_belp_alt
         T_BELP_NEU = lt_t_belp_neu
    EXCEPTIONS
        MACHINE_REPORT_SENDER_EXISTS = 1
        MACHINE_REPORT_RECEIVER_EXISTS = 2
. " J_3G_CHECK_MACHINE_REPORT




ABAP code using 7.40 inline data declarations to call FM J_3G_CHECK_MACHINE_REPORT

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 J_3GEMPFAE FROM J_3GBELK INTO @DATA(ld_i_alt_j_3gempfae).
 
 
"SELECT single J_3GEMPDEB FROM J_3GBELK INTO @DATA(ld_i_neu_j_3gempdeb).
 
"SELECT single J_3GEMPEXT FROM J_3GBELK INTO @DATA(ld_i_neu_j_3gempext).
 
 
"SELECT single J_3GEMPDEB FROM J_3GBELK INTO @DATA(ld_i_alt_j_3gempdeb).
 
 
"SELECT single J_3GEMPEXT FROM J_3GBELK INTO @DATA(ld_i_alt_j_3gempext).
 
"SELECT single J_3GBELDAT FROM J_3GBELK INTO @DATA(ld_i_alt_j_3gbeldat).
 
"SELECT single J_3GEMPFAE FROM J_3GBELK INTO @DATA(ld_i_neu_j_3gabsend).
 
"SELECT single J_3GEMPDEB FROM J_3GBELK INTO @DATA(ld_i_neu_j_3gabsdeb).
 
"SELECT single J_3GEMPEXT FROM J_3GBELK INTO @DATA(ld_i_neu_j_3gabsext).
 
"SELECT single J_3GBELDAT FROM J_3GBELK INTO @DATA(ld_i_neu_j_3gbeldat).
 
"SELECT single J_3GEMPFAE FROM J_3GBELK INTO @DATA(ld_i_neu_j_3gempfae).
 


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!