SAP JITOUT04_ACTION_APPEND_JC Function Module for NOTRANSL: Anhängen von Komponenten / Teilegruppen zu einem bestehenden Abr









JITOUT04_ACTION_APPEND_JC is a standard jitout04 action append jc 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: Anhängen von Komponenten / Teilegruppen zu einem bestehenden Abr 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 action append jc FM, simply by entering the name JITOUT04_ACTION_APPEND_JC 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_ACTION_APPEND_JC 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_ACTION_APPEND_JC'"NOTRANSL: Anhängen von Komponenten / Teilegruppen zu einem bestehenden Abr
EXPORTING
* CHAINED_ACTION_IV = ' ' "Single-Character Indicator

IMPORTING
MSSG_RET_CT = "Transfer Table for System Messages

CHANGING
* JITODIAHD_CT = "Table Type for JITODIAHD
JITODIAIT_CT = "Table Type for JITODIAIT
JITODIACO_CT = "Table Type for JITODIACO
* JITOAD_CT = "Additional Data for JIT Outbound
ASYNC_POSTING_CV = "
* STATUS_UPD_DONE_CV = "Single-Character Indicator
* JITODATA_CS = "Interface Structure for Outbound Action Control

TABLES
* JITDIAPO_IT = "JIT : Dialog Structure Seq.JIT Entry

EXCEPTIONS
APPEND_NOT_POSSIBLE = 1
.



IMPORTING Parameters details for JITOUT04_ACTION_APPEND_JC

CHAINED_ACTION_IV - Single-Character Indicator

Data type: CHAR1
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for JITOUT04_ACTION_APPEND_JC

MSSG_RET_CT - Transfer Table for System Messages

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

CHANGING Parameters details for JITOUT04_ACTION_APPEND_JC

JITODIAHD_CT - Table Type for JITODIAHD

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

JITODIAIT_CT - Table Type for JITODIAIT

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

JITODIACO_CT - Table Type for JITODIACO

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

JITOAD_CT - Additional Data for JIT Outbound

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

ASYNC_POSTING_CV -

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

STATUS_UPD_DONE_CV - Single-Character Indicator

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

JITODATA_CS - Interface Structure for Outbound Action Control

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

TABLES Parameters details for JITOUT04_ACTION_APPEND_JC

JITDIAPO_IT - JIT : Dialog Structure Seq.JIT Entry

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

EXCEPTIONS details

APPEND_NOT_POSSIBLE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for JITOUT04_ACTION_APPEND_JC 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_jitdiapo_it  TYPE STANDARD TABLE OF JITDIAPO, "   
lv_mssg_ret_ct  TYPE MSSG_RET_TT, "   
lv_jitodiahd_ct  TYPE JITODIAHD_TT, "   
lv_chained_action_iv  TYPE CHAR1, "   ' '
lv_append_not_possible  TYPE CHAR1, "   
lv_jitodiait_ct  TYPE JITODIAIT_TT, "   
lv_jitodiaco_ct  TYPE JITODIACO_TT, "   
lv_jitoad_ct  TYPE JITOAD_TT, "   
lv_async_posting_cv  TYPE C, "   
lv_status_upd_done_cv  TYPE CHAR1, "   
lv_jitodata_cs  TYPE JITODATA. "   

  CALL FUNCTION 'JITOUT04_ACTION_APPEND_JC'  "NOTRANSL: Anhängen von Komponenten / Teilegruppen zu einem bestehenden Abr
    EXPORTING
         CHAINED_ACTION_IV = lv_chained_action_iv
    IMPORTING
         MSSG_RET_CT = lv_mssg_ret_ct
    CHANGING
         JITODIAHD_CT = lv_jitodiahd_ct
         JITODIAIT_CT = lv_jitodiait_ct
         JITODIACO_CT = lv_jitodiaco_ct
         JITOAD_CT = lv_jitoad_ct
         ASYNC_POSTING_CV = lv_async_posting_cv
         STATUS_UPD_DONE_CV = lv_status_upd_done_cv
         JITODATA_CS = lv_jitodata_cs
    TABLES
         JITDIAPO_IT = lt_jitdiapo_it
    EXCEPTIONS
        APPEND_NOT_POSSIBLE = 1
. " JITOUT04_ACTION_APPEND_JC




ABAP code using 7.40 inline data declarations to call FM JITOUT04_ACTION_APPEND_JC

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.

 
 
 
DATA(ld_chained_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!