SAP ISM_SD_SHP_GETDETAIL Function Module for Shipping Schedule, Data Retrieval









ISM_SD_SHP_GETDETAIL is a standard ism sd shp getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Shipping Schedule, Data Retrieval 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 shp getdetail FM, simply by entering the name ISM_SD_SHP_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_SD_SHP_GETDETAIL 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_SHP_GETDETAIL'"Shipping Schedule, Data Retrieval
  EXPORTING
   IV_VERSION =  "Transportation Planning Version
*  IT_MSTAE =  "IS-M: Range Type for Cross-Plant Status
*  IT_MMSTA =  "IS-M: Range Type for Plant-Specific Status
*  IT_RSOG =  "IS-M: Range Type for Release Status for Order Generation
*  IT_RSTP =  "IS-M: Range Type for TP Release Status
*  IV_SFWACTIVE = 'X' "
*  IV_SFWAPPLICATION = 'JVSDTPLOAD_CHANGE' "Application for Stock Determination
*  IT_SDATE =  "IS-M: Range Table for VRSNDDATUM: Shipping Date
*  IT_WERKS =  "Range Table for Plants
*  IT_PRODUCT =  "
*  IT_ISSUE =  "IS-M: Range Table for ISMMATNR_ISSUE
*  IT_VKORG =  "IS-M: Range Table for VKORG
*  IT_VTWEG =  "IS-M: Range Table for Distribution Channel
*  IT_CYCLE =  "IS-M: Range Table for CYCLE
*  IT_MSTAV =  "IS-M: Range Type for Cross-Distribution Chain Status

 IMPORTING
   ET_WLPLA =  "
   ET_WLCON =  "
   ET_WLORD =  "IS-M: TP Worklist of Orders for Pull Process per Shippg Date
   ET_WLISS =  "
   ET_WLISSOPT =  "Shipping Dates for a Media Issue for Optimized Contracts
   ET_COMPLETE =  "
   ET_NEXTRECALLDATE =  "Shipping Plan, Next Recall Date for Issue
   ET_ISSUEDATA =  "Shipping Plan, Additional Issue Data

CHANGING
   CT_RETURN =  "Log
.



IMPORTING Parameters details for ISM_SD_SHP_GETDETAIL

IV_VERSION - Transportation Planning Version

Data type: JVSDWLTRSPPLAN-VERSION
Optional: No
Call by Reference: Yes

IT_MSTAE - IS-M: Range Type for Cross-Plant Status

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

IT_MMSTA - IS-M: Range Type for Plant-Specific Status

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

IT_RSOG - IS-M: Range Type for Release Status for Order Generation

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

IT_RSTP - IS-M: Range Type for TP Release Status

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

IV_SFWACTIVE -

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

IV_SFWAPPLICATION - Application for Stock Determination

Data type: JKSDSFAPPLICATION
Default: 'JVSDTPLOAD_CHANGE'
Optional: Yes
Call by Reference: Yes

IT_SDATE - IS-M: Range Table for VRSNDDATUM: Shipping Date

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

IT_WERKS - Range Table for Plants

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

IT_PRODUCT -

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

IT_ISSUE - IS-M: Range Table for ISMMATNR_ISSUE

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

IT_VKORG - IS-M: Range Table for VKORG

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

IT_VTWEG - IS-M: Range Table for Distribution Channel

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

IT_CYCLE - IS-M: Range Table for CYCLE

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

IT_MSTAV - IS-M: Range Type for Cross-Distribution Chain Status

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

EXPORTING Parameters details for ISM_SD_SHP_GETDETAIL

ET_WLPLA -

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

ET_WLCON -

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

ET_WLORD - IS-M: TP Worklist of Orders for Pull Process per Shippg Date

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

ET_WLISS -

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

ET_WLISSOPT - Shipping Dates for a Media Issue for Optimized Contracts

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

ET_COMPLETE -

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

ET_NEXTRECALLDATE - Shipping Plan, Next Recall Date for Issue

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

ET_ISSUEDATA - Shipping Plan, Additional Issue Data

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

CHANGING Parameters details for ISM_SD_SHP_GETDETAIL

CT_RETURN - Log

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

Copy and paste ABAP code example for ISM_SD_SHP_GETDETAIL 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_et_wlpla  TYPE JVSDWLTRSPPLAN_TAB, "   
lv_ct_return  TYPE BAPIRET2TAB, "   
lv_iv_version  TYPE JVSDWLTRSPPLAN-VERSION, "   
lv_it_mstae  TYPE RJKSD_MSTAE_RANGE_TAB, "   
lv_it_mmsta  TYPE RJKSD_MMSTA_RANGE_TAB, "   
lv_it_rsog  TYPE RJKSD_RSOG_RANGE_TAB, "   
lv_it_rstp  TYPE RJKSD_RSTP_RANGE_TAB, "   
lv_iv_sfwactive  TYPE XFELD, "   'X'
lv_iv_sfwapplication  TYPE JKSDSFAPPLICATION, "   'JVSDTPLOAD_CHANGE'
lv_et_wlcon  TYPE JVSDWLTRSPLCONTR_TAB, "   
lv_it_sdate  TYPE RJVSD_VRSNDDATUM_RANGE_TAB, "   
lv_et_wlord  TYPE JVSDWLTRSPLORDER_TAB, "   
lv_it_werks  TYPE RJKSD_WERKS_RANGE_TAB, "   
lv_et_wliss  TYPE JVSDWLTRSPLISSUE_TAB, "   
lv_it_product  TYPE RJKSD_PRODUCT_RANGE_TAB, "   
lv_it_issue  TYPE RJKSD_ISSUE_RANGE_TAB, "   
lv_et_wlissopt  TYPE JVSDSHPPLISSOPT_TAB, "   
lv_it_vkorg  TYPE RJKSD_VKORG_RANGE_TAB, "   
lv_et_complete  TYPE RJVSD_SHP_COMPLETE_TAB, "   
lv_it_vtweg  TYPE RJKSD_VTWEG_RANGE_TAB, "   
lv_et_nextrecalldate  TYPE RJVSD_SHP_ISSUEDATA2_TAB, "   
lv_it_cycle  TYPE RJVSD_CYCLE_RANGE_TAB, "   
lv_et_issuedata  TYPE RJVSD_SHP_ISSUEDATA1_TAB, "   
lv_it_mstav  TYPE RJKSD_MSTAV_RANGE_TAB. "   

  CALL FUNCTION 'ISM_SD_SHP_GETDETAIL'  "Shipping Schedule, Data Retrieval
    EXPORTING
         IV_VERSION = lv_iv_version
         IT_MSTAE = lv_it_mstae
         IT_MMSTA = lv_it_mmsta
         IT_RSOG = lv_it_rsog
         IT_RSTP = lv_it_rstp
         IV_SFWACTIVE = lv_iv_sfwactive
         IV_SFWAPPLICATION = lv_iv_sfwapplication
         IT_SDATE = lv_it_sdate
         IT_WERKS = lv_it_werks
         IT_PRODUCT = lv_it_product
         IT_ISSUE = lv_it_issue
         IT_VKORG = lv_it_vkorg
         IT_VTWEG = lv_it_vtweg
         IT_CYCLE = lv_it_cycle
         IT_MSTAV = lv_it_mstav
    IMPORTING
         ET_WLPLA = lv_et_wlpla
         ET_WLCON = lv_et_wlcon
         ET_WLORD = lv_et_wlord
         ET_WLISS = lv_et_wliss
         ET_WLISSOPT = lv_et_wlissopt
         ET_COMPLETE = lv_et_complete
         ET_NEXTRECALLDATE = lv_et_nextrecalldate
         ET_ISSUEDATA = lv_et_issuedata
    CHANGING
         CT_RETURN = lv_ct_return
. " ISM_SD_SHP_GETDETAIL




ABAP code using 7.40 inline data declarations to call FM ISM_SD_SHP_GETDETAIL

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 VERSION FROM JVSDWLTRSPPLAN INTO @DATA(ld_iv_version).
 
 
 
 
 
DATA(ld_iv_sfwactive) = 'X'.
 
DATA(ld_iv_sfwapplication) = 'JVSDTPLOAD_CHANGE'.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


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!