SAP JIT03_ADD_DELIVERY Function Module for NOTRANSL: JIT : Lieferung: weitere Positionen hinzufügen









JIT03_ADD_DELIVERY is a standard jit03 add delivery 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: JIT : Lieferung: weitere Positionen hinzufügen 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 jit03 add delivery FM, simply by entering the name JIT03_ADD_DELIVERY into the relevant SAP transaction such as SE37 or SE38.

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



Function JIT03_ADD_DELIVERY 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 'JIT03_ADD_DELIVERY'"NOTRANSL: JIT : Lieferung: weitere Positionen hinzufügen
EXPORTING
ACTION_IV = "JIT : External Status

IMPORTING
PGSTATUSUPD_EV = "

CHANGING
* PG_SPEC_CT = "

TABLES
JITIT_CT = "

EXCEPTIONS
NO_PARTGROUP = 1 MORE_THAN_ONE_CUSTO = 2 NO_DELIVERY_UPDATED = 3 NO_OPEN_DELIVERY = 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_SAPLJIT03_001 JIT: Sorting Header and Item Data
EXIT_SAPLJIT03_002 JIT: Defining Handling Units (Delivery)
EXIT_SAPLJIT03_003 JIT: Printing the Component List using Action Call
EXIT_SAPLJIT03_004 JIT: Print Picking List using Action Call
EXIT_SAPLJIT03_005 JIT: Delivery Scheduling
EXIT_SAPLJIT03_006 JIT: Check-Digit Determination
EXIT_SAPLJIT03_007 JIT: Components Group Material Determination
EXIT_SAPLJIT03_008 JIT: Carry Out Material Movements
EXIT_SAPLJIT03_009 JIT: Modification of Backflush Data
EXIT_SAPLJIT03_011 Exit for Inbound Processing Summarized JIT Call
EXIT_SAPLJIT03_012 JIT: Customer Exit for Replacement Logic Summarized JIT Call Inbound
EXIT_SAPLJIT03_013 SumJC: Set Control Parameters for EXIDV2 in HU
EXIT_SAPLJIT03_014 JIT: Modify Print Data for Transfer to Spool
EXIT_SAPLJIT03_015 JIT: Adjusting Data when Creating Delivery

IMPORTING Parameters details for JIT03_ADD_DELIVERY

ACTION_IV - JIT : External Status

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

EXPORTING Parameters details for JIT03_ADD_DELIVERY

PGSTATUSUPD_EV -

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

CHANGING Parameters details for JIT03_ADD_DELIVERY

PG_SPEC_CT -

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

TABLES Parameters details for JIT03_ADD_DELIVERY

JITIT_CT -

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

EXCEPTIONS details

NO_PARTGROUP -

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

MORE_THAN_ONE_CUSTO -

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

NO_DELIVERY_UPDATED -

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

NO_OPEN_DELIVERY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for JIT03_ADD_DELIVERY 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_jitit_ct  TYPE STANDARD TABLE OF JITIT, "   
lv_action_iv  TYPE CJIT05-AKTION, "   
lv_pg_spec_ct  TYPE JIT00_PG_STATUS_PT, "   
lv_no_partgroup  TYPE JIT00_PG_STATUS_PT, "   
lv_pgstatusupd_ev  TYPE C, "   
lv_more_than_one_custo  TYPE C, "   
lv_no_delivery_updated  TYPE C, "   
lv_no_open_delivery  TYPE C. "   

  CALL FUNCTION 'JIT03_ADD_DELIVERY'  "NOTRANSL: JIT : Lieferung: weitere Positionen hinzufügen
    EXPORTING
         ACTION_IV = lv_action_iv
    IMPORTING
         PGSTATUSUPD_EV = lv_pgstatusupd_ev
    CHANGING
         PG_SPEC_CT = lv_pg_spec_ct
    TABLES
         JITIT_CT = lt_jitit_ct
    EXCEPTIONS
        NO_PARTGROUP = 1
        MORE_THAN_ONE_CUSTO = 2
        NO_DELIVERY_UPDATED = 3
        NO_OPEN_DELIVERY = 4
. " JIT03_ADD_DELIVERY




ABAP code using 7.40 inline data declarations to call FM JIT03_ADD_DELIVERY

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 AKTION FROM CJIT05 INTO @DATA(ld_action_iv).
 
 
 
 
 
 
 


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!