SAP ISM_ISSUECOMP_CHANGE_CHECK Function Module for IS-M/SD: Media Issue - Add Component









ISM_ISSUECOMP_CHANGE_CHECK is a standard ism issuecomp change check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-M/SD: Media Issue - Add Component 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 ism issuecomp change check FM, simply by entering the name ISM_ISSUECOMP_CHANGE_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_ISSUECOMP_CHANGE_CHECK 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 'ISM_ISSUECOMP_CHANGE_CHECK'"IS-M/SD: Media Issue - Add Component
EXPORTING
IN_ISSUECOMP = "

IMPORTING
OUT_TABIX = "

EXCEPTIONS
NOT_EXISTING = 1 WRONG_CALL = 2
.



IMPORTING Parameters details for ISM_ISSUECOMP_CHANGE_CHECK

IN_ISSUECOMP -

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

EXPORTING Parameters details for ISM_ISSUECOMP_CHANGE_CHECK

OUT_TABIX -

Data type: SY-TABIX
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_EXISTING -

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

WRONG_CALL -

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

Copy and paste ABAP code example for ISM_ISSUECOMP_CHANGE_CHECK 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_out_tabix  TYPE SY-TABIX, "   
lv_in_issuecomp  TYPE RJVSDISSUECOMP, "   
lv_not_existing  TYPE RJVSDISSUECOMP, "   
lv_wrong_call  TYPE RJVSDISSUECOMP. "   

  CALL FUNCTION 'ISM_ISSUECOMP_CHANGE_CHECK'  "IS-M/SD: Media Issue - Add Component
    EXPORTING
         IN_ISSUECOMP = lv_in_issuecomp
    IMPORTING
         OUT_TABIX = lv_out_tabix
    EXCEPTIONS
        NOT_EXISTING = 1
        WRONG_CALL = 2
. " ISM_ISSUECOMP_CHANGE_CHECK




ABAP code using 7.40 inline data declarations to call FM ISM_ISSUECOMP_CHANGE_CHECK

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 TABIX FROM SY INTO @DATA(ld_out_tabix).
 
 
 
 


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!