SAP ISM_CONTRACTDEMAND_BPTRANSACT Function Module for IS-M: Refresh Quantity Planning for Customer (Dialog)

Search SAP Function Modules

ISM_CONTRACTDEMAND_BPTRANSACT is a standard ism contractdemand bptransact 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: Refresh Quantity Planning for Customer (Dialog) 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 bptransact FM, simply by entering the name ISM_CONTRACTDEMAND_BPTRANSACT 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_BPTRANSACT 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_BPTRANSACT'"IS-M: Refresh Quantity Planning for Customer (Dialog)
  EXPORTING
   IN_BP =  "Customer Number
   IN_CALENDARID =  "
   IN_INTERVALTAB =  "IS-M: Table of Planning Suspensions for Business Partner
   IN_OLDINTERVALTAB =  "IS-M: Table of Planning Suspensions for Business Partner

 IMPORTING
   OUT_MSG_TAB =  "Application Log: Log Handle Table

EXCEPTIONS
   ERROR_IN_CALENDER = 1    ERROR_MISSING_DATE = 2    BP_NO_CALENDER_ID = 3    ERROR_NO_PRODUCT_FOUND = 4    ERROR_ISSUE_NOTFOUND = 5    DEMAND_LOCKED = 6 

.

IMPORTING Parameters details for ISM_CONTRACTDEMAND_BPTRANSACT

IN_BP - Customer Number

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

IN_CALENDARID -

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

IN_INTERVALTAB - IS-M: Table of Planning Suspensions for Business Partner

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

IN_OLDINTERVALTAB - IS-M: Table of Planning Suspensions for Business Partner

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

EXPORTING Parameters details for ISM_CONTRACTDEMAND_BPTRANSACT

OUT_MSG_TAB - Application Log: Log Handle Table

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

EXCEPTIONS details

ERROR_IN_CALENDER -

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

ERROR_MISSING_DATE -

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

BP_NO_CALENDER_ID -

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

ERROR_NO_PRODUCT_FOUND -

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

ERROR_ISSUE_NOTFOUND -

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

DEMAND_LOCKED -

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

Copy and paste ABAP code example for ISM_CONTRACTDEMAND_BPTRANSACT 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_BPTRANSACT

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