SAP JITOUT04_DETERMINE_MSG_PARTNER Function Module for NOTRANSL: Actions for JIT Outbound









JITOUT04_DETERMINE_MSG_PARTNER is a standard jitout04 determine msg partner 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: Actions for JIT Outbound 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 jitout04 determine msg partner FM, simply by entering the name JITOUT04_DETERMINE_MSG_PARTNER into the relevant SAP transaction such as SE37 or SE38.

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



Function JITOUT04_DETERMINE_MSG_PARTNER 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 'JITOUT04_DETERMINE_MSG_PARTNER'"NOTRANSL: Actions for JIT Outbound
  EXPORTING
*  OUTPO_IV =  "

CHANGING
*  LIFNR_IV =  "
*  EKORG_IV =  "Purchasing Organization
*  STOCK_LIFNR_IV =  "
*  NO_ERR_IV =  "
*  JITODATA_CS =  "Interface Structure for Outbound Action Control

TABLES
*  JITODIACO_IT =  "

EXCEPTIONS
   GENERAL_ERROR = 1
.



IMPORTING Parameters details for JITOUT04_DETERMINE_MSG_PARTNER

OUTPO_IV -

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

CHANGING Parameters details for JITOUT04_DETERMINE_MSG_PARTNER

LIFNR_IV -

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

EKORG_IV - Purchasing Organization

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

STOCK_LIFNR_IV -

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

NO_ERR_IV -

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

JITODATA_CS - Interface Structure for Outbound Action Control

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

TABLES Parameters details for JITOUT04_DETERMINE_MSG_PARTNER

JITODIACO_IT -

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

EXCEPTIONS details

GENERAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for JITOUT04_DETERMINE_MSG_PARTNER 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_lifnr_iv  TYPE LIFNR, "   
lv_outpo_iv  TYPE JITO_OUTPO, "   
lt_jitodiaco_it  TYPE STANDARD TABLE OF JITODIACO, "   
lv_general_error  TYPE JITODIACO, "   
lv_ekorg_iv  TYPE EKORG, "   
lv_stock_lifnr_iv  TYPE LIFNR, "   
lv_no_err_iv  TYPE CHAR1, "   
lv_jitodata_cs  TYPE JITODATA. "   

  CALL FUNCTION 'JITOUT04_DETERMINE_MSG_PARTNER'  "NOTRANSL: Actions for JIT Outbound
    EXPORTING
         OUTPO_IV = lv_outpo_iv
    CHANGING
         LIFNR_IV = lv_lifnr_iv
         EKORG_IV = lv_ekorg_iv
         STOCK_LIFNR_IV = lv_stock_lifnr_iv
         NO_ERR_IV = lv_no_err_iv
         JITODATA_CS = lv_jitodata_cs
    TABLES
         JITODIACO_IT = lt_jitodiaco_it
    EXCEPTIONS
        GENERAL_ERROR = 1
. " JITOUT04_DETERMINE_MSG_PARTNER




ABAP code using 7.40 inline data declarations to call FM JITOUT04_DETERMINE_MSG_PARTNER

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!