J_1I_EXCISE_INBOUND_DELIVERY SAP Function module - Capturing Excise Details for SUS and Background J1IEX

J_1I_EXCISE_INBOUND_DELIVERY is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name J_1I_EXCISE_INBOUND_DELIVERY into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: J1IEX
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM J_1I_EXCISE_INBOUND_DELIVERY - J 1I EXCISE INBOUND DELIVERY

CALL FUNCTION 'J_1I_EXCISE_INBOUND_DELIVERY' "Capturing Excise Details for SUS and Background J1IEX
* EXPORTING
*   idoc_control =              " edidc         Control record (IDoc)
*   idoc_data =                 " delif_t_edidd
*   delivery_com =              " delif_t_komdlgn
*   packing_head =              " delif_t_verko
*   packing_item =              " delif_t_verpo
*   processing_status =         " i
*   processing_protocol =       " delif_t_prott
    .  "  J_1I_EXCISE_INBOUND_DELIVERY

ABAP code example for Function Module J_1I_EXCISE_INBOUND_DELIVERY

The ABAP code below is a full code listing to execute function module J_1I_EXCISE_INBOUND_DELIVERY including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_idoc_control) = 'Check type of data required'.

DATA(ld_idoc_data) = 'Check type of data required'.

DATA(ld_delivery_com) = 'Check type of data required'.

DATA(ld_packing_head) = 'Check type of data required'.

DATA(ld_packing_item) = 'Check type of data required'.

DATA(ld_processing_status) = 'Check type of data required'.

DATA(ld_processing_protocol) = 'Check type of data required'.
.

CALL FUNCTION 'J_1I_EXCISE_INBOUND_DELIVERY'
* EXPORTING
*   idoc_control =               ld_idoc_control
*   idoc_data =                  ld_idoc_data
*   delivery_com =               ld_delivery_com
*   packing_head =               ld_packing_head
*   packing_item =               ld_packing_item
*   processing_status =          ld_processing_status
*   processing_protocol =        ld_processing_protocol
    .  "  J_1I_EXCISE_INBOUND_DELIVERY

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_idoc_control
 
 TYPE EDIDC ,
ld_idoc_data
 
 TYPE DELIF_T_EDIDD ,
ld_delivery_com
 
 TYPE DELIF_T_KOMDLGN ,
ld_packing_head
 
 TYPE DELIF_T_VERKO ,
ld_packing_item
 
 TYPE DELIF_T_VERPO ,
ld_processing_status
 
 TYPE I ,
ld_processing_protocol
 
 TYPE DELIF_T_PROTT .


ld_idoc_control = 'Check type of data required'.
ld_idoc_data = 'Check type of data required'.
ld_delivery_com = 'Check type of data required'.
ld_packing_head = 'Check type of data required'.
ld_packing_item = 'Check type of data required'.
ld_processing_status = 'Check type of data required'.
ld_processing_protocol = 'Check type of data required'.