SAP BAPI_CMS_TC_GET_MULTI Function Module for Get Total Commitment Details of a BP in CMS









BAPI_CMS_TC_GET_MULTI is a standard bapi cms tc get multi SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Total Commitment Details of a BP in CMS 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 bapi cms tc get multi FM, simply by entering the name BAPI_CMS_TC_GET_MULTI into the relevant SAP transaction such as SE37 or SE38.

Function Group: CMS_BUSISB101_BAPI
Program Name: SAPLCMS_BUSISB101_BAPI
Main Program: SAPLCMS_BUSISB101_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_CMS_TC_GET_MULTI 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 'BAPI_CMS_TC_GET_MULTI'"Get Total Commitment Details of a BP in CMS
  EXPORTING
*  LANGUAGEISO =  "Language according to ISO 639
*  LANGUAGE =  "Total Commitment: Language Key
*  PROCESSEXTENSION =  "Flag: Execute Customer Extensions (BAdIs) in BAPI

TABLES
   BUSINESSPARTNER =  "Business Partner Identification Number
*  ROLECATEGORY =  "Business Partner Role Category
*  TOTALCOMMITMENT =  "Total Commitment of Business Partner in CMS
*  EXTENSIONIN =  "Ref. structure for BAPI parameter ExtensionIn/ExtensionOut
*  EXTENSIONOUT =  "Ref. structure for BAPI parameter ExtensionIn/ExtensionOut
*  RETURN =  "Return Parameter
.



IMPORTING Parameters details for BAPI_CMS_TC_GET_MULTI

LANGUAGEISO - Language according to ISO 639

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

LANGUAGE - Total Commitment: Language Key

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

PROCESSEXTENSION - Flag: Execute Customer Extensions (BAdIs) in BAPI

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

TABLES Parameters details for BAPI_CMS_TC_GET_MULTI

BUSINESSPARTNER - Business Partner Identification Number

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

ROLECATEGORY - Business Partner Role Category

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

TOTALCOMMITMENT - Total Commitment of Business Partner in CMS

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

EXTENSIONIN - Ref. structure for BAPI parameter ExtensionIn/ExtensionOut

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

EXTENSIONOUT - Ref. structure for BAPI parameter ExtensionIn/ExtensionOut

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

RETURN - Return Parameter

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

Copy and paste ABAP code example for BAPI_CMS_TC_GET_MULTI 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_languageiso  TYPE BAPICMS_STR_LANGU-LANGU_ISO, "   
lt_businesspartner  TYPE STANDARD TABLE OF BAPICMS_STR_BPID, "   
lv_language  TYPE BAPICMS_STR_LANGU-LANGUAGE, "   
lt_rolecategory  TYPE STANDARD TABLE OF BAPICMS_STR_ROLE_TYPE, "   
lt_totalcommitment  TYPE STANDARD TABLE OF BAPICMS_STR_TOTAL_COMMITMENT, "   
lv_processextension  TYPE BAPI_CMS_STR_CENTRAL-PROCESSEXTENSION, "   
lt_extensionin  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_extensionout  TYPE STANDARD TABLE OF BAPIPAREX, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2. "   

  CALL FUNCTION 'BAPI_CMS_TC_GET_MULTI'  "Get Total Commitment Details of a BP in CMS
    EXPORTING
         LANGUAGEISO = lv_languageiso
         LANGUAGE = lv_language
         PROCESSEXTENSION = lv_processextension
    TABLES
         BUSINESSPARTNER = lt_businesspartner
         ROLECATEGORY = lt_rolecategory
         TOTALCOMMITMENT = lt_totalcommitment
         EXTENSIONIN = lt_extensionin
         EXTENSIONOUT = lt_extensionout
         RETURN = lt_return
. " BAPI_CMS_TC_GET_MULTI




ABAP code using 7.40 inline data declarations to call FM BAPI_CMS_TC_GET_MULTI

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.

"SELECT single LANGU_ISO FROM BAPICMS_STR_LANGU INTO @DATA(ld_languageiso).
 
 
"SELECT single LANGUAGE FROM BAPICMS_STR_LANGU INTO @DATA(ld_language).
 
 
 
"SELECT single PROCESSEXTENSION FROM BAPI_CMS_STR_CENTRAL INTO @DATA(ld_processextension).
 
 
 
 


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!