SAP JITOUT06_POST_GOODS_MOVEMENT Function Module for NOTRANSL: Buchen der Warenbewegungen









JITOUT06_POST_GOODS_MOVEMENT is a standard jitout06 post goods movement 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: Buchen der Warenbewegungen 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 jitout06 post goods movement FM, simply by entering the name JITOUT06_POST_GOODS_MOVEMENT into the relevant SAP transaction such as SE37 or SE38.

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



Function JITOUT06_POST_GOODS_MOVEMENT 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 'JITOUT06_POST_GOODS_MOVEMENT'"NOTRANSL: Buchen der Warenbewegungen
  EXPORTING
   IMKPF_IS =  "MMIM: Input Structure for General FM to Post Goods Movement
*  DLCNO_IS =  "Last Delivery Confirmation Number to Vendor

 IMPORTING
   EMKPF_ES =  "MMIM: Output Structure For General FM To Post Goods Movement

CHANGING
*  DLCNOHD_CT =  "Delivery Confirmations Header
*  DLCNOCO_CT =  "Delivery Confirmations Items
*  DLCNORF_CT =  "References for Delivery Confirmation
*  JITODIACO_CT =  "Dialog Structure Outbound Components Group
*  REPRL_CV =  "Entry Available in Reprocessing List

TABLES
   IMSEG_IT =  "MMIM: Input Structure for General FM to Post Goods Movement
   MSSG_RET_ET =  "Transfer Structure for System Messages
   EMSEG_ET =  "MMIM: Output Structure For General FM To Post Goods Movement

EXCEPTIONS
   GOODS_MOVEMENT_ERROR = 1
.



IMPORTING Parameters details for JITOUT06_POST_GOODS_MOVEMENT

IMKPF_IS - MMIM: Input Structure for General FM to Post Goods Movement

Data type: IMKPF
Optional: No
Call by Reference: Yes

DLCNO_IS - Last Delivery Confirmation Number to Vendor

Data type: DLCNO
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for JITOUT06_POST_GOODS_MOVEMENT

EMKPF_ES - MMIM: Output Structure For General FM To Post Goods Movement

Data type: EMKPF
Optional: No
Call by Reference: Yes

CHANGING Parameters details for JITOUT06_POST_GOODS_MOVEMENT

DLCNOHD_CT - Delivery Confirmations Header

Data type: DLCNOHD_TT
Optional: Yes
Call by Reference: Yes

DLCNOCO_CT - Delivery Confirmations Items

Data type: DLCNOCO_TT
Optional: Yes
Call by Reference: Yes

DLCNORF_CT - References for Delivery Confirmation

Data type: DLCNORF_TT
Optional: Yes
Call by Reference: Yes

JITODIACO_CT - Dialog Structure Outbound Components Group

Data type: JITODIACO_TT
Optional: Yes
Call by Reference: Yes

REPRL_CV - Entry Available in Reprocessing List

Data type: JITO_REPRL
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for JITOUT06_POST_GOODS_MOVEMENT

IMSEG_IT - MMIM: Input Structure for General FM to Post Goods Movement

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

MSSG_RET_ET - Transfer Structure for System Messages

Data type: MSSG_RET
Optional: No
Call by Reference: Yes

EMSEG_ET - MMIM: Output Structure For General FM To Post Goods Movement

Data type: EMSEG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

GOODS_MOVEMENT_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for JITOUT06_POST_GOODS_MOVEMENT 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_emkpf_es  TYPE EMKPF, "   
lv_imkpf_is  TYPE IMKPF, "   
lt_imseg_it  TYPE STANDARD TABLE OF IMSEG, "   
lv_dlcnohd_ct  TYPE DLCNOHD_TT, "   
lv_goods_movement_error  TYPE DLCNOHD_TT, "   
lv_dlcno_is  TYPE DLCNO, "   
lv_dlcnoco_ct  TYPE DLCNOCO_TT, "   
lt_mssg_ret_et  TYPE STANDARD TABLE OF MSSG_RET, "   
lt_emseg_et  TYPE STANDARD TABLE OF EMSEG, "   
lv_dlcnorf_ct  TYPE DLCNORF_TT, "   
lv_jitodiaco_ct  TYPE JITODIACO_TT, "   
lv_reprl_cv  TYPE JITO_REPRL. "   

  CALL FUNCTION 'JITOUT06_POST_GOODS_MOVEMENT'  "NOTRANSL: Buchen der Warenbewegungen
    EXPORTING
         IMKPF_IS = lv_imkpf_is
         DLCNO_IS = lv_dlcno_is
    IMPORTING
         EMKPF_ES = lv_emkpf_es
    CHANGING
         DLCNOHD_CT = lv_dlcnohd_ct
         DLCNOCO_CT = lv_dlcnoco_ct
         DLCNORF_CT = lv_dlcnorf_ct
         JITODIACO_CT = lv_jitodiaco_ct
         REPRL_CV = lv_reprl_cv
    TABLES
         IMSEG_IT = lt_imseg_it
         MSSG_RET_ET = lt_mssg_ret_et
         EMSEG_ET = lt_emseg_et
    EXCEPTIONS
        GOODS_MOVEMENT_ERROR = 1
. " JITOUT06_POST_GOODS_MOVEMENT




ABAP code using 7.40 inline data declarations to call FM JITOUT06_POST_GOODS_MOVEMENT

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!