SAP ISM_PARTIAL_ORDERS_GET Function Module for









ISM_PARTIAL_ORDERS_GET is a standard ism partial orders get 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 partial orders get FM, simply by entering the name ISM_PARTIAL_ORDERS_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_PARTIAL_ORDERS_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_PARTIAL_ORDERS_GET'"
EXPORTING
IN_SHIPPING_DATE = "
IN_DISTRICT = "
IN_DELIVERY_SET = "

IMPORTING
OUT_PARTIALORDERS_TAB = "
.



IMPORTING Parameters details for ISM_PARTIAL_ORDERS_GET

IN_SHIPPING_DATE -

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

IN_DISTRICT -

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

IN_DELIVERY_SET -

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

EXPORTING Parameters details for ISM_PARTIAL_ORDERS_GET

OUT_PARTIALORDERS_TAB -

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

Copy and paste ABAP code example for ISM_PARTIAL_ORDERS_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:
lv_in_shipping_date  TYPE STRING, "   
lv_out_partialorders_tab  TYPE STRING, "   
lv_in_district  TYPE STRING, "   
lv_in_delivery_set  TYPE STRING. "   

  CALL FUNCTION 'ISM_PARTIAL_ORDERS_GET'  "
    EXPORTING
         IN_SHIPPING_DATE = lv_in_shipping_date
         IN_DISTRICT = lv_in_district
         IN_DELIVERY_SET = lv_in_delivery_set
    IMPORTING
         OUT_PARTIALORDERS_TAB = lv_out_partialorders_tab
. " ISM_PARTIAL_ORDERS_GET




ABAP code using 7.40 inline data declarations to call FM ISM_PARTIAL_ORDERS_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.

 
 
 
 


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!