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

Search SAP Function Modules

ISM_CONTRACTDEMAND_GETLIST is a standard ism contractdemand getlist 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 getlist FM, simply by entering the name ISM_CONTRACTDEMAND_GETLIST 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_GETLIST 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_GETLIST'"IS-M: Read Planned Quantities from IS-M
  EXPORTING
*  IN_VKORG_TAB =  "Sales Organization
*  IN_PHASEMDL_TAB =  "Phase Model
*  IN_PHASENBR_TAB =  "Phase Number
*  IN_AUART_TAB =  "IS-M: Range Table for AUART
*  IN_BUFFER_REFRESH =  "Refresh Buffer
*  IN_VTWEG_TAB =  "Distribution Channel
*  IN_SPART_TAB =  "Division
*  IN_VKBUR_TAB =  "Sales Office
*  IN_VKGRP_TAB =  "Sales Group
*  IN_VERSION_TAB =  "IS-M: Range Table for Versions in Quantity Planning
*  IN_VBELN_TAB =  "Contract
*  IN_POSNR_TAB =  "Contract Item
*  IN_ISSUE_TAB =  "Media Issue

 IMPORTING
   OUT_DEMAND_TAB =  "IS-M: Table Type for JKSDDEMAND

EXCEPTIONS
   NOT_FOUND = 1    WRONG_INPUT = 2 

.

IMPORTING Parameters details for ISM_CONTRACTDEMAND_GETLIST

IN_VKORG_TAB - Sales Organization

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

IN_PHASEMDL_TAB - Phase Model

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

IN_PHASENBR_TAB - Phase Number

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

IN_AUART_TAB - IS-M: Range Table for AUART

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

IN_BUFFER_REFRESH - Refresh Buffer

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

IN_VTWEG_TAB - Distribution Channel

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

IN_SPART_TAB - Division

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

IN_VKBUR_TAB - Sales Office

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

IN_VKGRP_TAB - Sales Group

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

IN_VERSION_TAB - IS-M: Range Table for Versions in Quantity Planning

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

IN_VBELN_TAB - Contract

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

IN_POSNR_TAB - Contract Item

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

IN_ISSUE_TAB - Media Issue

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

EXPORTING Parameters details for ISM_CONTRACTDEMAND_GETLIST

OUT_DEMAND_TAB - IS-M: Table Type for JKSDDEMAND

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

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

WRONG_INPUT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISM_CONTRACTDEMAND_GETLIST 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_GETLIST

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