SAP ISM_SE_GET_ORDER_DATA Function Module for









ISM_SE_GET_ORDER_DATA is a standard ism se get order data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 se get order data FM, simply by entering the name ISM_SE_GET_ORDER_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_SE_GET_ORDER_DATA 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_SE_GET_ORDER_DATA'"
EXPORTING
IN_CONTRACT = "
IN_ISSUE = "
IN_NIP = "

IMPORTING
OUT_QUANTITY = "
OUT_UNIT = "
OUT_DELIVERY_BLOC = "
OUT_SHIPPING_DATE = "
OUT_BILLING_DATE = "

EXCEPTIONS
NO_SUBSEQUENT_DELIVERY = 1
.



IMPORTING Parameters details for ISM_SE_GET_ORDER_DATA

IN_CONTRACT -

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

IN_ISSUE -

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

IN_NIP -

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

EXPORTING Parameters details for ISM_SE_GET_ORDER_DATA

OUT_QUANTITY -

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

OUT_UNIT -

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

OUT_DELIVERY_BLOC -

Data type: JKSESCHED-DELIVERY_BLOC
Optional: No
Call by Reference: Yes

OUT_SHIPPING_DATE -

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

OUT_BILLING_DATE -

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

EXCEPTIONS details

NO_SUBSEQUENT_DELIVERY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISM_SE_GET_ORDER_DATA 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_in_contract  TYPE JKSECONTRINDEX, "   
lv_out_quantity  TYPE JORDERQUAN, "   
lv_no_subsequent_delivery  TYPE JORDERQUAN, "   
lv_in_issue  TYPE MATNR, "   
lv_out_unit  TYPE JORDERUNIT, "   
lv_in_nip  TYPE CL_ISM_SE_NIP, "   
lv_out_delivery_bloc  TYPE JKSESCHED-DELIVERY_BLOC, "   
lv_out_shipping_date  TYPE JSHIPPING_DATE, "   
lv_out_billing_date  TYPE JBILLING_DATE. "   

  CALL FUNCTION 'ISM_SE_GET_ORDER_DATA'  "
    EXPORTING
         IN_CONTRACT = lv_in_contract
         IN_ISSUE = lv_in_issue
         IN_NIP = lv_in_nip
    IMPORTING
         OUT_QUANTITY = lv_out_quantity
         OUT_UNIT = lv_out_unit
         OUT_DELIVERY_BLOC = lv_out_delivery_bloc
         OUT_SHIPPING_DATE = lv_out_shipping_date
         OUT_BILLING_DATE = lv_out_billing_date
    EXCEPTIONS
        NO_SUBSEQUENT_DELIVERY = 1
. " ISM_SE_GET_ORDER_DATA




ABAP code using 7.40 inline data declarations to call FM ISM_SE_GET_ORDER_DATA

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 DELIVERY_BLOC FROM JKSESCHED INTO @DATA(ld_out_delivery_bloc).
 
 
 


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!