SAP ISM_SD_ORDER_GET Function Module for IS-M: Select Orders According to Specific Criteria









ISM_SD_ORDER_GET is a standard ism sd order get 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: Select Orders According to Specific Criteria 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 order get FM, simply by entering the name ISM_SD_ORDER_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_SD_ORDER_GET 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_ORDER_GET'"IS-M: Select Orders According to Specific Criteria
  EXPORTING
*  X_MANUAL = ' ' "
*  X_PARTNER_OR = '' "
*  X_GENERATED = 'X' "
*  X_NO_FOLLOW_UP_DOCS = 'X' "

TABLES
*  IN_VKORG =  "Sales Organization
*  IN_POSNR =  "
*  IN_SHIP_TO_PARTY =  "Ship-to Party
*  IN_SOLD_TO_PARTY =  "
*  IN_WHOLESALER =  "
*  IN_ORDER_DOC =  "
   OUT_ORDER =  "
*  IN_VTWEG =  "Distribution Channel
*  IN_SPART =  "Division
*  IN_VKBUR =  "Sales Office
*  IN_VKGRP =  "Sales Group
*  IN_ISSUE =  "Media Issue
*  IN_CONTRACT =  "Contract Number
*  IN_CONTRACT_DOC =  "
*  IN_ORDER =  "Order

EXCEPTIONS
   NO_ORDER_FOUND = 1
.



IMPORTING Parameters details for ISM_SD_ORDER_GET

X_MANUAL -

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

X_PARTNER_OR -

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

X_GENERATED -

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

X_NO_FOLLOW_UP_DOCS -

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

TABLES Parameters details for ISM_SD_ORDER_GET

IN_VKORG - Sales Organization

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

IN_POSNR -

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

IN_SHIP_TO_PARTY - Ship-to Party

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

IN_SOLD_TO_PARTY -

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

IN_WHOLESALER -

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

IN_ORDER_DOC -

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

OUT_ORDER -

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

IN_VTWEG - Distribution Channel

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

IN_SPART - Division

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

IN_VKBUR - Sales Office

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

IN_VKGRP - Sales Group

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

IN_ISSUE - Media Issue

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

IN_CONTRACT - Contract Number

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

IN_CONTRACT_DOC -

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

IN_ORDER - Order

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

EXCEPTIONS details

NO_ORDER_FOUND -

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

Copy and paste ABAP code example for ISM_SD_ORDER_GET 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:
lt_in_vkorg  TYPE STANDARD TABLE OF RJKSD_VKORG_RANGE, "   
lv_x_manual  TYPE C, "   ' '
lv_no_order_found  TYPE C, "   
lt_in_posnr  TYPE STANDARD TABLE OF RJKSD_POSNR_RANGE, "   
lt_in_ship_to_party  TYPE STANDARD TABLE OF RJKSD_BP_RANGE, "   
lt_in_sold_to_party  TYPE STANDARD TABLE OF RJKSD_BP_RANGE, "   
lt_in_wholesaler  TYPE STANDARD TABLE OF RJKSD_BP_RANGE, "   
lt_in_order_doc  TYPE STANDARD TABLE OF RJKSD_AUART_RANGE, "   
lt_out_order  TYPE STANDARD TABLE OF RJKSDORDER2, "   
lt_in_vtweg  TYPE STANDARD TABLE OF RJKSD_VTWEG_RANGE, "   
lv_x_partner_or  TYPE C, "   ''
lt_in_spart  TYPE STANDARD TABLE OF RJKSD_SPART_RANGE, "   
lv_x_generated  TYPE C, "   'X'
lt_in_vkbur  TYPE STANDARD TABLE OF RJKSD_VKBUR_RANGE, "   
lv_x_no_follow_up_docs  TYPE C, "   'X'
lt_in_vkgrp  TYPE STANDARD TABLE OF RJKSD_VKGRP_RANGE, "   
lt_in_issue  TYPE STANDARD TABLE OF RJKSD_ISSUE_RANGE, "   
lt_in_contract  TYPE STANDARD TABLE OF RJKSD_VBELN_RANGE, "   
lt_in_contract_doc  TYPE STANDARD TABLE OF RJKSD_AUART_RANGE, "   
lt_in_order  TYPE STANDARD TABLE OF RJKSD_VBELN_RANGE. "   

  CALL FUNCTION 'ISM_SD_ORDER_GET'  "IS-M: Select Orders According to Specific Criteria
    EXPORTING
         X_MANUAL = lv_x_manual
         X_PARTNER_OR = lv_x_partner_or
         X_GENERATED = lv_x_generated
         X_NO_FOLLOW_UP_DOCS = lv_x_no_follow_up_docs
    TABLES
         IN_VKORG = lt_in_vkorg
         IN_POSNR = lt_in_posnr
         IN_SHIP_TO_PARTY = lt_in_ship_to_party
         IN_SOLD_TO_PARTY = lt_in_sold_to_party
         IN_WHOLESALER = lt_in_wholesaler
         IN_ORDER_DOC = lt_in_order_doc
         OUT_ORDER = lt_out_order
         IN_VTWEG = lt_in_vtweg
         IN_SPART = lt_in_spart
         IN_VKBUR = lt_in_vkbur
         IN_VKGRP = lt_in_vkgrp
         IN_ISSUE = lt_in_issue
         IN_CONTRACT = lt_in_contract
         IN_CONTRACT_DOC = lt_in_contract_doc
         IN_ORDER = lt_in_order
    EXCEPTIONS
        NO_ORDER_FOUND = 1
. " ISM_SD_ORDER_GET




ABAP code using 7.40 inline data declarations to call FM ISM_SD_ORDER_GET

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.

 
DATA(ld_x_manual) = ' '.
 
 
 
 
 
 
 
 
 
DATA(ld_x_partner_or) = ''.
 
 
DATA(ld_x_generated) = 'X'.
 
 
DATA(ld_x_no_follow_up_docs) = 'X'.
 
 
 
 
 
 


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!