SAP ISM_ISSUECOMP_GET Function Module for IS-M/SD: Media Issue - Read Component
ISM_ISSUECOMP_GET is a standard ism issuecomp get 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 - Read 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 get FM, simply by entering the name ISM_ISSUECOMP_GET 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_GET 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_GET'"IS-M/SD: Media Issue - Read Component.
EXPORTING
IN_MEDIAISSUE = "Higher-Level Media Product
* IV_NO_INITIAL_NODE = ' ' "
IMPORTING
OUT_ISSUECOMP = "
EV_NOT_EXIST = "
EXCEPTIONS
WRONG_CALL = 1
IMPORTING Parameters details for ISM_ISSUECOMP_GET
IN_MEDIAISSUE - Higher-Level Media Product
Data type: ISMMATNR_ISSUEOptional: No
Call by Reference: Yes
IV_NO_INITIAL_NODE -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISM_ISSUECOMP_GET
OUT_ISSUECOMP -
Data type: RJVSDISSUECOMPTABOptional: No
Call by Reference: Yes
EV_NOT_EXIST -
Data type: XFELDOptional: No
Call by Reference: Yes
EXCEPTIONS details
WRONG_CALL -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_ISSUECOMP_GET 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_wrong_call | TYPE STRING, " | |||
lv_in_mediaissue | TYPE ISMMATNR_ISSUE, " | |||
lv_out_issuecomp | TYPE RJVSDISSUECOMPTAB, " | |||
lv_ev_not_exist | TYPE XFELD, " | |||
lv_iv_no_initial_node | TYPE XFELD. " SPACE |
  CALL FUNCTION 'ISM_ISSUECOMP_GET' "IS-M/SD: Media Issue - Read Component |
EXPORTING | ||
IN_MEDIAISSUE | = lv_in_mediaissue | |
IV_NO_INITIAL_NODE | = lv_iv_no_initial_node | |
IMPORTING | ||
OUT_ISSUECOMP | = lv_out_issuecomp | |
EV_NOT_EXIST | = lv_ev_not_exist | |
EXCEPTIONS | ||
WRONG_CALL = 1 | ||
. " ISM_ISSUECOMP_GET |
ABAP code using 7.40 inline data declarations to call FM ISM_ISSUECOMP_GET
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_iv_no_initial_node) | = ' '. | |||
Search for further information about these or an SAP related objects