SAP ISM_SD_GET_ISSUE Function Module for Internal: Specify Issue for Product/Family









ISM_SD_GET_ISSUE is a standard ism sd get issue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Internal: Specify Issue for Product/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 issue FM, simply by entering the name ISM_SD_GET_ISSUE 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_ISSUE 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_ISSUE'"Internal: Specify Issue for Product/Family
  EXPORTING
*  MEDIA_FAMILY =  "
*  SPART =  "Division
*  VKBUR =  "Sales Office
*  VKGRP =  "Sales Group
*  MARA_READ =  "
*  CHECK_EXISTS_ORDER = 'X' "
*  COPY_NUMBER =  "Copy Number of Issue
*  PUBL_DATE =  "Publication Date
*  BP =  "Customer Number
*  BP_IN_ROLE =  "
*  DAY_FROM =  "
*  DAY_TO =  "
*  VKORG =  "Sales Organization
*  VTWEG =  "Distribution Channel

 IMPORTING
   OUT_ISSUE_TAB =  "IS-M: Table Type for Media Issues

TABLES
*  IN_ISSUE_TAB =  "Material Number
*  IN_PRODUCT_TAB =  "Media Product

EXCEPTIONS
   ERROR = 1
.



IMPORTING Parameters details for ISM_SD_GET_ISSUE

MEDIA_FAMILY -

Data type: JKSDUNSOLDITEM-MEDIA_FAMILY
Optional: Yes
Call by Reference: Yes

SPART - Division

Data type: VBAK-SPART
Optional: Yes
Call by Reference: Yes

VKBUR - Sales Office

Data type: VBAK-VKBUR
Optional: Yes
Call by Reference: Yes

VKGRP - Sales Group

Data type: VBAK-VKGRP
Optional: Yes
Call by Reference: Yes

MARA_READ -

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

CHECK_EXISTS_ORDER -

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

COPY_NUMBER - Copy Number of Issue

Data type: MARA-ISMCOPYNR
Optional: Yes
Call by Reference: Yes

PUBL_DATE - Publication Date

Data type: JKSDUNSOLDITEM-PUBL_DATE
Optional: Yes
Call by Reference: Yes

BP - Customer Number

Data type: VBPA-KUNNR
Optional: Yes
Call by Reference: Yes

BP_IN_ROLE -

Data type: VBPA-PARVW
Optional: Yes
Call by Reference: Yes

DAY_FROM -

Data type: JKSDUNSOLDITEM-DAY_FROM
Optional: Yes
Call by Reference: Yes

DAY_TO -

Data type: JKSDUNSOLDITEM-DAY_TO
Optional: Yes
Call by Reference: Yes

VKORG - Sales Organization

Data type: VBAK-VKORG
Optional: Yes
Call by Reference: Yes

VTWEG - Distribution Channel

Data type: VBAK-VTWEG
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISM_SD_GET_ISSUE

OUT_ISSUE_TAB - IS-M: Table Type for Media Issues

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

TABLES Parameters details for ISM_SD_GET_ISSUE

IN_ISSUE_TAB - Material Number

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

IN_PRODUCT_TAB - Media Product

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

EXCEPTIONS details

ERROR - Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISM_SD_GET_ISSUE 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_issue_tab  TYPE RJKSDISSUE_TAB, "   
lv_spart  TYPE VBAK-SPART, "   
lv_vkbur  TYPE VBAK-VKBUR, "   
lv_vkgrp  TYPE VBAK-VKGRP, "   
lv_mara_read  TYPE C, "   
lv_check_exists_order  TYPE C, "   'X'
lv_copy_number  TYPE MARA-ISMCOPYNR, "   
lt_in_product_tab  TYPE STANDARD TABLE OF RJKSD_ISSUE_RANGE, "   
lv_publ_date  TYPE JKSDUNSOLDITEM-PUBL_DATE, "   
lv_bp  TYPE VBPA-KUNNR, "   
lv_bp_in_role  TYPE VBPA-PARVW, "   
lv_day_from  TYPE JKSDUNSOLDITEM-DAY_FROM, "   
lv_day_to  TYPE JKSDUNSOLDITEM-DAY_TO, "   
lv_vkorg  TYPE VBAK-VKORG, "   
lv_vtweg  TYPE VBAK-VTWEG. "   

  CALL FUNCTION 'ISM_SD_GET_ISSUE'  "Internal: Specify Issue for Product/Family
    EXPORTING
         MEDIA_FAMILY = lv_media_family
         SPART = lv_spart
         VKBUR = lv_vkbur
         VKGRP = lv_vkgrp
         MARA_READ = lv_mara_read
         CHECK_EXISTS_ORDER = lv_check_exists_order
         COPY_NUMBER = lv_copy_number
         PUBL_DATE = lv_publ_date
         BP = lv_bp
         BP_IN_ROLE = lv_bp_in_role
         DAY_FROM = lv_day_from
         DAY_TO = lv_day_to
         VKORG = lv_vkorg
         VTWEG = lv_vtweg
    IMPORTING
         OUT_ISSUE_TAB = lv_out_issue_tab
    TABLES
         IN_ISSUE_TAB = lt_in_issue_tab
         IN_PRODUCT_TAB = lt_in_product_tab
    EXCEPTIONS
        ERROR = 1
. " ISM_SD_GET_ISSUE




ABAP code using 7.40 inline data declarations to call FM ISM_SD_GET_ISSUE

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 SPART FROM VBAK INTO @DATA(ld_spart).
 
"SELECT single VKBUR FROM VBAK INTO @DATA(ld_vkbur).
 
"SELECT single VKGRP FROM VBAK INTO @DATA(ld_vkgrp).
 
 
DATA(ld_check_exists_order) = 'X'.
 
"SELECT single ISMCOPYNR FROM MARA INTO @DATA(ld_copy_number).
 
 
"SELECT single PUBL_DATE FROM JKSDUNSOLDITEM INTO @DATA(ld_publ_date).
 
"SELECT single KUNNR FROM VBPA INTO @DATA(ld_bp).
 
"SELECT single PARVW FROM VBPA INTO @DATA(ld_bp_in_role).
 
"SELECT single DAY_FROM FROM JKSDUNSOLDITEM INTO @DATA(ld_day_from).
 
"SELECT single DAY_TO FROM JKSDUNSOLDITEM INTO @DATA(ld_day_to).
 
"SELECT single VKORG FROM VBAK INTO @DATA(ld_vkorg).
 
"SELECT single VTWEG FROM VBAK INTO @DATA(ld_vtweg).
 


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!