SAP ISM_SD_GET_PRODUCT Function Module for IS-M: Specify Media Product for Media Issue/Media Family
ISM_SD_GET_PRODUCT is a standard ism sd get product 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: Specify Media Product for Media Issue/Media Family 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 sd get product FM, simply by entering the name ISM_SD_GET_PRODUCT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JKSDORDER1
Program Name: SAPLJKSDORDER1
Main Program: SAPLJKSDORDER1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ISM_SD_GET_PRODUCT 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_SD_GET_PRODUCT'"IS-M: Specify Media Product for Media Issue/Media Family.
EXPORTING
* MEDIA_FAMILY = "
* COPY_NUMBER = "Copy Number of Issue
* PUBL_DATE = "Publication Date
* ONSALEDATE = "IS-M: On-Sale Date
* OFFSALEDATE = "IS-M: End of Sales Period
* INITSHIPDATEBEGIN = "
* INITSHIPDATEEND = "
IMPORTING
OUT_PRODUCT_TAB = "Media Products
TABLES
* IN_ISSUE_TAB = "Material Number
* IN_PRODUCT_TAB = "Media Product
* IN_MSTAV = "IS-M: Range Type for Cross-Distribution Chain Status
* IN_VMSTA = "IS-M: Range Type for Cross-Distribution Chain Status
* IN_MSTAE = "IS-M: Range Type for Cross-Plant Status
* IN_MMSTA = "IS-M: Range Type for Plant-Specific Status
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for ISM_SD_GET_PRODUCT
MEDIA_FAMILY -
Data type: JKSDUNSOLDITEM-MEDIA_FAMILYOptional: Yes
Call by Reference: Yes
COPY_NUMBER - Copy Number of Issue
Data type: MARA-ISMCOPYNROptional: Yes
Call by Reference: Yes
PUBL_DATE - Publication Date
Data type: JKSDUNSOLDITEM-PUBL_DATEOptional: Yes
Call by Reference: Yes
ONSALEDATE - IS-M: On-Sale Date
Data type: MVKE-ISMONSALEDATEOptional: Yes
Call by Reference: Yes
OFFSALEDATE - IS-M: End of Sales Period
Data type: MVKE-ISMOFFSALEDATEOptional: Yes
Call by Reference: Yes
INITSHIPDATEBEGIN -
Data type: MVKE-ISMINITSHIPDATEOptional: Yes
Call by Reference: Yes
INITSHIPDATEEND -
Data type: MVKE-ISMINITSHIPDATEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for ISM_SD_GET_PRODUCT
OUT_PRODUCT_TAB - Media Products
Data type: RJKSDISSUE_TABOptional: No
Call by Reference: Yes
TABLES Parameters details for ISM_SD_GET_PRODUCT
IN_ISSUE_TAB - Material Number
Data type: RJKSD_ISSUE_RANGEOptional: Yes
Call by Reference: Yes
IN_PRODUCT_TAB - Media Product
Data type: RJKSD_ISSUE_RANGEOptional: Yes
Call by Reference: Yes
IN_MSTAV - IS-M: Range Type for Cross-Distribution Chain Status
Data type: RJKSD_MSTAV_RANGEOptional: Yes
Call by Reference: Yes
IN_VMSTA - IS-M: Range Type for Cross-Distribution Chain Status
Data type: RJKSD_VMSTA_RANGEOptional: Yes
Call by Reference: Yes
IN_MSTAE - IS-M: Range Type for Cross-Plant Status
Data type: RJKSD_MSTAE_RANGEOptional: Yes
Call by Reference: Yes
IN_MMSTA - IS-M: Range Type for Plant-Specific Status
Data type: RJKSD_MMSTA_RANGEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ERROR - Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISM_SD_GET_PRODUCT 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_error | TYPE STRING, " | |||
lt_in_issue_tab | TYPE STANDARD TABLE OF RJKSD_ISSUE_RANGE, " | |||
lv_media_family | TYPE JKSDUNSOLDITEM-MEDIA_FAMILY, " | |||
lv_out_product_tab | TYPE RJKSDISSUE_TAB, " | |||
lv_copy_number | TYPE MARA-ISMCOPYNR, " | |||
lt_in_product_tab | TYPE STANDARD TABLE OF RJKSD_ISSUE_RANGE, " | |||
lt_in_mstav | TYPE STANDARD TABLE OF RJKSD_MSTAV_RANGE, " | |||
lv_publ_date | TYPE JKSDUNSOLDITEM-PUBL_DATE, " | |||
lt_in_vmsta | TYPE STANDARD TABLE OF RJKSD_VMSTA_RANGE, " | |||
lv_onsaledate | TYPE MVKE-ISMONSALEDATE, " | |||
lt_in_mstae | TYPE STANDARD TABLE OF RJKSD_MSTAE_RANGE, " | |||
lv_offsaledate | TYPE MVKE-ISMOFFSALEDATE, " | |||
lt_in_mmsta | TYPE STANDARD TABLE OF RJKSD_MMSTA_RANGE, " | |||
lv_initshipdatebegin | TYPE MVKE-ISMINITSHIPDATE, " | |||
lv_initshipdateend | TYPE MVKE-ISMINITSHIPDATE. " |
  CALL FUNCTION 'ISM_SD_GET_PRODUCT' "IS-M: Specify Media Product for Media Issue/Media Family |
EXPORTING | ||
MEDIA_FAMILY | = lv_media_family | |
COPY_NUMBER | = lv_copy_number | |
PUBL_DATE | = lv_publ_date | |
ONSALEDATE | = lv_onsaledate | |
OFFSALEDATE | = lv_offsaledate | |
INITSHIPDATEBEGIN | = lv_initshipdatebegin | |
INITSHIPDATEEND | = lv_initshipdateend | |
IMPORTING | ||
OUT_PRODUCT_TAB | = lv_out_product_tab | |
TABLES | ||
IN_ISSUE_TAB | = lt_in_issue_tab | |
IN_PRODUCT_TAB | = lt_in_product_tab | |
IN_MSTAV | = lt_in_mstav | |
IN_VMSTA | = lt_in_vmsta | |
IN_MSTAE | = lt_in_mstae | |
IN_MMSTA | = lt_in_mmsta | |
EXCEPTIONS | ||
ERROR = 1 | ||
. " ISM_SD_GET_PRODUCT |
ABAP code using 7.40 inline data declarations to call FM ISM_SD_GET_PRODUCT
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 MEDIA_FAMILY FROM JKSDUNSOLDITEM INTO @DATA(ld_media_family). | ||||
"SELECT single ISMCOPYNR FROM MARA INTO @DATA(ld_copy_number). | ||||
"SELECT single PUBL_DATE FROM JKSDUNSOLDITEM INTO @DATA(ld_publ_date). | ||||
"SELECT single ISMONSALEDATE FROM MVKE INTO @DATA(ld_onsaledate). | ||||
"SELECT single ISMOFFSALEDATE FROM MVKE INTO @DATA(ld_offsaledate). | ||||
"SELECT single ISMINITSHIPDATE FROM MVKE INTO @DATA(ld_initshipdatebegin). | ||||
"SELECT single ISMINITSHIPDATE FROM MVKE INTO @DATA(ld_initshipdateend). | ||||
Search for further information about these or an SAP related objects