SAP JIT04_ACTION_MODIFY_COMPONENT Function Module for Aktion: Komponente aus JIT-Abruf verändern









JIT04_ACTION_MODIFY_COMPONENT is a standard jit04 action modify component SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Aktion: Komponente aus JIT-Abruf verändern 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 jit04 action modify component FM, simply by entering the name JIT04_ACTION_MODIFY_COMPONENT into the relevant SAP transaction such as SE37 or SE38.

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



Function JIT04_ACTION_MODIFY_COMPONENT 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 'JIT04_ACTION_MODIFY_COMPONENT'"Aktion: Komponente aus JIT-Abruf verändern
 IMPORTING
   PGSTATUSUPD_EV =  "

CHANGING
   PG_SPEC_IT =  "
*  ASYNC_POSTING_CV = ' ' "

TABLES
   JC_HD_IT =  "JIT : Dialog Structure for JITHD
   JC_POS_IT =  "JIT : Dialog Structure Seq.JIT Entry
   JC_IT_IT =  "Components Group

EXCEPTIONS
   JITCALL_NOT_MODIFIED = 1
.




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_SAPLJIT04_001 JIT04 - Action Control: User-Defined Actions
EXIT_SAPLJIT04_002 JIT04 - Action Control: Exit before each Action (PRE)
EXIT_SAPLJIT04_003 JIT04 - Action Control: Exit after each Action (POST)
EXIT_SAPLJIT04_004 JIT: Customer-Exit Action PIN - Schedule Grouping Information
EXIT_SAPLJIT04_005 JIT: Customer-Exit Action POUT - Schedule Grouping Information

EXPORTING Parameters details for JIT04_ACTION_MODIFY_COMPONENT

PGSTATUSUPD_EV -

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

CHANGING Parameters details for JIT04_ACTION_MODIFY_COMPONENT

PG_SPEC_IT -

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

ASYNC_POSTING_CV -

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

TABLES Parameters details for JIT04_ACTION_MODIFY_COMPONENT

JC_HD_IT - JIT : Dialog Structure for JITHD

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

JC_POS_IT - JIT : Dialog Structure Seq.JIT Entry

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

JC_IT_IT - Components Group

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

EXCEPTIONS details

JITCALL_NOT_MODIFIED -

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

Copy and paste ABAP code example for JIT04_ACTION_MODIFY_COMPONENT 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_jc_hd_it  TYPE STANDARD TABLE OF JITDIAHD, "   
lv_pg_spec_it  TYPE JIT00_PG_STATUS_PT, "   
lv_pgstatusupd_ev  TYPE C, "   
lv_jitcall_not_modified  TYPE C, "   
lt_jc_pos_it  TYPE STANDARD TABLE OF JITDIAPO, "   
lv_async_posting_cv  TYPE C, "   ' '
lt_jc_it_it  TYPE STANDARD TABLE OF JITIT. "   

  CALL FUNCTION 'JIT04_ACTION_MODIFY_COMPONENT'  "Aktion: Komponente aus JIT-Abruf verändern
    IMPORTING
         PGSTATUSUPD_EV = lv_pgstatusupd_ev
    CHANGING
         PG_SPEC_IT = lv_pg_spec_it
         ASYNC_POSTING_CV = lv_async_posting_cv
    TABLES
         JC_HD_IT = lt_jc_hd_it
         JC_POS_IT = lt_jc_pos_it
         JC_IT_IT = lt_jc_it_it
    EXCEPTIONS
        JITCALL_NOT_MODIFIED = 1
. " JIT04_ACTION_MODIFY_COMPONENT




ABAP code using 7.40 inline data declarations to call FM JIT04_ACTION_MODIFY_COMPONENT

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_async_posting_cv) = ' '.
 
 


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!