SAP ISM_CQP_SPLIT_INTERVAL Function Module for Split Constant Service Interval









ISM_CQP_SPLIT_INTERVAL is a standard ism cqp split interval SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Split Constant Service Interval 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 cqp split interval FM, simply by entering the name ISM_CQP_SPLIT_INTERVAL into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_CQP_SPLIT_INTERVAL 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_CQP_SPLIT_INTERVAL'"Split Constant Service Interval
  EXPORTING
   IM_CONTRACT =  "Contract Number
   IM_ITEM =  "Item Number in Contract
   IM_SERVICETYPE =  "Service Type
   IM_STATUS =  "
   IM_SPLITDATE =  "Split Date
   IM_WEEKDAY =  "Weekday
*  IM_PLANORG_TAB =  "Planning Organization
*  IM_UPDATETASK = 'X' "
*  IM_NOCOMMIT = 'X' "

 IMPORTING
   EX_RETURN_TAB =  "Table of Messages
.



IMPORTING Parameters details for ISM_CQP_SPLIT_INTERVAL

IM_CONTRACT - Contract Number

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

IM_ITEM - Item Number in Contract

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

IM_SERVICETYPE - Service Type

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

IM_STATUS -

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

IM_SPLITDATE - Split Date

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

IM_WEEKDAY - Weekday

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

IM_PLANORG_TAB - Planning Organization

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

IM_UPDATETASK -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_NOCOMMIT -

Data type: XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISM_CQP_SPLIT_INTERVAL

EX_RETURN_TAB - Table of Messages

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

Copy and paste ABAP code example for ISM_CQP_SPLIT_INTERVAL 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_im_contract  TYPE JVBELNCONTRACT, "   
lv_ex_return_tab  TYPE BAPIRET2TAB, "   
lv_im_item  TYPE JPOSNRCONTRACT, "   
lv_im_servicetype  TYPE JSERVICETYPE, "   
lv_im_status  TYPE STATUSSERVICE, "   
lv_im_splitdate  TYPE SYDATUM, "   
lv_im_weekday  TYPE ISM_WEEKDAY, "   
lv_im_planorg_tab  TYPE RJKSD_PLANORG_RANGE_TAB, "   
lv_im_updatetask  TYPE XFELD, "   'X'
lv_im_nocommit  TYPE XFELD. "   'X'

  CALL FUNCTION 'ISM_CQP_SPLIT_INTERVAL'  "Split Constant Service Interval
    EXPORTING
         IM_CONTRACT = lv_im_contract
         IM_ITEM = lv_im_item
         IM_SERVICETYPE = lv_im_servicetype
         IM_STATUS = lv_im_status
         IM_SPLITDATE = lv_im_splitdate
         IM_WEEKDAY = lv_im_weekday
         IM_PLANORG_TAB = lv_im_planorg_tab
         IM_UPDATETASK = lv_im_updatetask
         IM_NOCOMMIT = lv_im_nocommit
    IMPORTING
         EX_RETURN_TAB = lv_ex_return_tab
. " ISM_CQP_SPLIT_INTERVAL




ABAP code using 7.40 inline data declarations to call FM ISM_CQP_SPLIT_INTERVAL

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.

 
 
 
 
 
 
 
 
DATA(ld_im_updatetask) = 'X'.
 
DATA(ld_im_nocommit) = 'X'.
 


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!