SAP ISM_CONTRACTDEMAND_BLOCKED Function Module for IS-M: Planned Quantities Not Allowed for Customer (Customer Calendar)

Search SAP Function Modules

ISM_CONTRACTDEMAND_BLOCKED is a standard ism contractdemand blocked 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: Planned Quantities Not Allowed for Customer (Customer Calendar) 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 blocked FM, simply by entering the name ISM_CONTRACTDEMAND_BLOCKED into the relevant SAP transaction such as SE37 or SE38.

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

Function ISM_CONTRACTDEMAND_BLOCKED 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_BLOCKED'"IS-M: Planned Quantities Not Allowed for Customer (Customer Calendar)
  EXPORTING
   IN_MEDIAISSUE =  "Media Issue
   IN_DOCUMENT =  "Sales and Distribution Document Number
   IN_ITEM =  "Item Number of Sales Document
*  IN_CALENDARID =  "Factory Calendar
*  IN_REQ_DELIVERY_DATE =  "Requested Delivery Date
*  IN_DEMAND_BLOCKED_ORIGIN =  "IS-M: Origin of 'Quantity Planning Locked' Indicator

 IMPORTING
   OUT_ISBLOCKED =  "
   OUT_OPEN_DATE =  "Publication Date

EXCEPTIONS
   ERROR_IN_CALENDER = 1    ERROR_MISSING_DATE = 2    ERROR_NO_PRODUCT_FOUND = 3    ERROR_ISSUE_NOTFOUND = 4    ERROR_SUSPEND_TYPE = 5    ERROR_INTERRUPT_NOT_ALLOWED = 6 

.

IMPORTING Parameters details for ISM_CONTRACTDEMAND_BLOCKED

IN_MEDIAISSUE - Media Issue

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

IN_DOCUMENT - Sales and Distribution Document Number

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

IN_ITEM - Item Number of Sales Document

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

IN_CALENDARID - Factory Calendar

Data type: SCAL-FCALID
Optional: Yes
Call by Reference: Yes

IN_REQ_DELIVERY_DATE - Requested Delivery Date

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

IN_DEMAND_BLOCKED_ORIGIN - IS-M: Origin of 'Quantity Planning Locked' Indicator

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

EXPORTING Parameters details for ISM_CONTRACTDEMAND_BLOCKED

OUT_ISBLOCKED -

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

OUT_OPEN_DATE - Publication Date

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

EXCEPTIONS details

ERROR_IN_CALENDER -

Data type:
Optional: No
Call by Reference: Yes

ERROR_MISSING_DATE -

Data type:
Optional: No
Call by Reference: Yes

ERROR_NO_PRODUCT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

ERROR_ISSUE_NOTFOUND -

Data type:
Optional: No
Call by Reference: Yes

ERROR_SUSPEND_TYPE -

Data type:
Optional: No
Call by Reference: Yes

ERROR_INTERRUPT_NOT_ALLOWED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISM_CONTRACTDEMAND_BLOCKED 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_BLOCKED

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