SAP ISM_CONTRACTDEMAND_GET Function Module for IS-M: Read Planned Quantities from IS-M

Search SAP Function Modules

ISM_CONTRACTDEMAND_GET is a standard ism contractdemand 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: Read Planned Quantities from IS-M 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 contractdemand get FM, simply by entering the name ISM_CONTRACTDEMAND_GET into the relevant SAP transaction such as SE37 or SE38.

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

Function ISM_CONTRACTDEMAND_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_CONTRACTDEMAND_GET'"IS-M: Read Planned Quantities from IS-M
  EXPORTING
   IN_DOCUMENT =  "Sales Document
   IN_ITEM =  "Sales document item
   IN_MEDIAISSUE =  "IS-M: Media Issue
*  IN_PHASEMDL =  "Phase Model in Phase-Based Delivery
*  IN_PHASENBR =  "Sequence Number in Phase-Based Delivery
*  IN_VERSION = '000       ' "

 IMPORTING
   OUT_QUANTITY =  "Target quantity in sales units
   OUT_QUANTITY_FIXED =  "
   OUT_SALESUNIT =  "Sales Unit
   OUT_ORIGINOFDEMAND =  "IS-M: Origin of Quantity
   OUT_QUANTITYEXTENSION =  "IS-M: Quantity Planning Fields
   OUT_JKSDDEMAND =  "IS-M: Planned Quantities

EXCEPTIONS
   NO_QUANTITY_FOUND = 1 

.

IMPORTING Parameters details for ISM_CONTRACTDEMAND_GET

IN_DOCUMENT - Sales Document

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

IN_ITEM - Sales document item

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

IN_MEDIAISSUE - IS-M: Media Issue

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

IN_PHASEMDL - Phase Model in Phase-Based Delivery

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

IN_PHASENBR - Sequence Number in Phase-Based Delivery

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

IN_VERSION -

Data type: JKSDDEMAND-VERSION
Default: '000 '
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISM_CONTRACTDEMAND_GET

OUT_QUANTITY - Target quantity in sales units

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

OUT_QUANTITY_FIXED -

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

OUT_SALESUNIT - Sales Unit

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

OUT_ORIGINOFDEMAND - IS-M: Origin of Quantity

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

OUT_QUANTITYEXTENSION - IS-M: Quantity Planning Fields

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

OUT_JKSDDEMAND - IS-M: Planned Quantities

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

EXCEPTIONS details

NO_QUANTITY_FOUND - No quantities found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISM_CONTRACTDEMAND_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.

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