SAP JITOUT03_SET_LOCK_JITOUTBOUND Function Module for NOTRANSL: Setzen von Schreibsperren für JIT-Outbound









JITOUT03_SET_LOCK_JITOUTBOUND is a standard jitout03 set lock jitoutbound 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: Setzen von Schreibsperren für 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 jitout03 set lock jitoutbound FM, simply by entering the name JITOUT03_SET_LOCK_JITOUTBOUND into the relevant SAP transaction such as SE37 or SE38.

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



Function JITOUT03_SET_LOCK_JITOUTBOUND 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 'JITOUT03_SET_LOCK_JITOUTBOUND'"NOTRANSL: Setzen von Schreibsperren für JIT-Outbound
  EXPORTING
   WAITFLAG_IV =  "
   JITOLO1_IT =  "
*  JITOLO2_IT =  "Table with Locked Relationships: JIT Call - Transfer Order
*  JITOLO3_IT =  "Table with Locked Relationships: JIT Call - Transfer Order

 IMPORTING
   LOCK_ERROR_ET =  "
   LOCK_ERROR2_ET =  "Table with Locked Relationships: JIT Call - Transfer Order
   LOCK_ERROR3_ET =  "Table with Locked Relationships: Summ. JIT Call - Delivery

EXCEPTIONS
   JITOUTBOUND_LOCKED = 1    SYSTEM_ERROR = 2    JITOTO_LOCKED = 3    PABASN_LOCKED = 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_SAPLJITOUT03_001

IMPORTING Parameters details for JITOUT03_SET_LOCK_JITOUTBOUND

WAITFLAG_IV -

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

JITOLO1_IT -

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

JITOLO2_IT - Table with Locked Relationships: JIT Call - Transfer Order

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

JITOLO3_IT - Table with Locked Relationships: JIT Call - Transfer Order

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

EXPORTING Parameters details for JITOUT03_SET_LOCK_JITOUTBOUND

LOCK_ERROR_ET -

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

LOCK_ERROR2_ET - Table with Locked Relationships: JIT Call - Transfer Order

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

LOCK_ERROR3_ET - Table with Locked Relationships: Summ. JIT Call - Delivery

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

EXCEPTIONS details

JITOUTBOUND_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_ERROR - System Error

Data type:
Optional: No
Call by Reference: Yes

JITOTO_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

PABASN_LOCKED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for JITOUT03_SET_LOCK_JITOUTBOUND 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_waitflag_iv  TYPE C, "   
lv_lock_error_et  TYPE JITOLO1_TT, "   
lv_jitoutbound_locked  TYPE JITOLO1_TT, "   
lv_jitolo1_it  TYPE JITOLO1_TT, "   
lv_system_error  TYPE JITOLO1_TT, "   
lv_lock_error2_et  TYPE JITOLO2_TT, "   
lv_jitolo2_it  TYPE JITOLO2_TT, "   
lv_jitoto_locked  TYPE JITOLO2_TT, "   
lv_lock_error3_et  TYPE JITOLO3_TT, "   
lv_jitolo3_it  TYPE JITOLO3_TT, "   
lv_pabasn_locked  TYPE JITOLO3_TT. "   

  CALL FUNCTION 'JITOUT03_SET_LOCK_JITOUTBOUND'  "NOTRANSL: Setzen von Schreibsperren für JIT-Outbound
    EXPORTING
         WAITFLAG_IV = lv_waitflag_iv
         JITOLO1_IT = lv_jitolo1_it
         JITOLO2_IT = lv_jitolo2_it
         JITOLO3_IT = lv_jitolo3_it
    IMPORTING
         LOCK_ERROR_ET = lv_lock_error_et
         LOCK_ERROR2_ET = lv_lock_error2_et
         LOCK_ERROR3_ET = lv_lock_error3_et
    EXCEPTIONS
        JITOUTBOUND_LOCKED = 1
        SYSTEM_ERROR = 2
        JITOTO_LOCKED = 3
        PABASN_LOCKED = 4
. " JITOUT03_SET_LOCK_JITOUTBOUND




ABAP code using 7.40 inline data declarations to call FM JITOUT03_SET_LOCK_JITOUTBOUND

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!