SAP ISM_SD_SET_ORDER_DATES2 Function Module for IS-M: Set Media Issue Dates for Order Generation









ISM_SD_SET_ORDER_DATES2 is a standard ism sd set order dates2 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: Set Media Issue Dates for Order Generation 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 set order dates2 FM, simply by entering the name ISM_SD_SET_ORDER_DATES2 into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_SD_SET_ORDER_DATES2 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_SET_ORDER_DATES2'"IS-M: Set Media Issue Dates for Order Generation
EXPORTING
IN_HEAD = "Communication Fields: Sales Document Header
IN_ISSUE = "Media Issue
IN_CONTRACT = "Contract
* IN_BLOCKED = "Quantities Cannot Be Maintained Using Planning Calendar

IMPORTING
OUT_REQ_DATE = "Schedule Line Date
OUT_MS_DATE = "Material Staging/Availability Date
OUT_LOAD_DATE = "Loading Date
OUT_GI_DATE = "Goods Issue Date

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for ISM_SD_SET_ORDER_DATES2

IN_HEAD - Communication Fields: Sales Document Header

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

IN_ISSUE - Media Issue

Data type: MARA-MATNR
Optional: No
Call by Reference: Yes

IN_CONTRACT - Contract

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

IN_BLOCKED - Quantities Cannot Be Maintained Using Planning Calendar

Data type: JKSDDEMAND-BLOCKED
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISM_SD_SET_ORDER_DATES2

OUT_REQ_DATE - Schedule Line Date

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

OUT_MS_DATE - Material Staging/Availability Date

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

OUT_LOAD_DATE - Loading Date

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

OUT_GI_DATE - Goods Issue Date

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

EXCEPTIONS details

ERROR - Errors have occurred

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

Copy and paste ABAP code example for ISM_SD_SET_ORDER_DATES2 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, "   
lv_in_head  TYPE BAPISDHD1, "   
lv_out_req_date  TYPE SY-DATUM, "   
lv_in_issue  TYPE MARA-MATNR, "   
lv_out_ms_date  TYPE SY-DATUM, "   
lv_in_contract  TYPE JKSECONTRINDEX, "   
lv_out_load_date  TYPE SY-DATUM, "   
lv_in_blocked  TYPE JKSDDEMAND-BLOCKED, "   
lv_out_gi_date  TYPE SY-DATUM. "   

  CALL FUNCTION 'ISM_SD_SET_ORDER_DATES2'  "IS-M: Set Media Issue Dates for Order Generation
    EXPORTING
         IN_HEAD = lv_in_head
         IN_ISSUE = lv_in_issue
         IN_CONTRACT = lv_in_contract
         IN_BLOCKED = lv_in_blocked
    IMPORTING
         OUT_REQ_DATE = lv_out_req_date
         OUT_MS_DATE = lv_out_ms_date
         OUT_LOAD_DATE = lv_out_load_date
         OUT_GI_DATE = lv_out_gi_date
    EXCEPTIONS
        ERROR = 1
. " ISM_SD_SET_ORDER_DATES2




ABAP code using 7.40 inline data declarations to call FM ISM_SD_SET_ORDER_DATES2

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 DATUM FROM SY INTO @DATA(ld_out_req_date).
 
"SELECT single MATNR FROM MARA INTO @DATA(ld_in_issue).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_out_ms_date).
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_out_load_date).
 
"SELECT single BLOCKED FROM JKSDDEMAND INTO @DATA(ld_in_blocked).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_out_gi_date).
 


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!