SAP CMS_API_BP_OVR_GET Function Module for Fetch data for the business partner overview









CMS_API_BP_OVR_GET is a standard cms api bp ovr get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fetch data for the business partner overview 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 cms api bp ovr get FM, simply by entering the name CMS_API_BP_OVR_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function CMS_API_BP_OVR_GET 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 'CMS_API_BP_OVR_GET'"Fetch data for the business partner overview
EXPORTING
I_BPID = "Business Partner Identification Number
* I_TAB_BPF = "Range Table for Business Partner Functions
* I_CAG_TYP = "Collateral Agreement Type

IMPORTING
E_TAB_CON = "Constellation data
E_STR_BP_CALC = "Calculations relevant for a Business Partner
E_TAB_RC = "Return Code and corresponding Message
.



IMPORTING Parameters details for CMS_API_BP_OVR_GET

I_BPID - Business Partner Identification Number

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

I_TAB_BPF - Range Table for Business Partner Functions

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

I_CAG_TYP - Collateral Agreement Type

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

EXPORTING Parameters details for CMS_API_BP_OVR_GET

E_TAB_CON - Constellation data

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

E_STR_BP_CALC - Calculations relevant for a Business Partner

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

E_TAB_RC - Return Code and corresponding Message

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

Copy and paste ABAP code example for CMS_API_BP_OVR_GET 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_i_bpid  TYPE CMS_DTE_BPID, "   
lv_e_tab_con  TYPE CMS_TAB_CON, "   
lv_i_tab_bpf  TYPE CMS_TAB_BPF_RNG, "   
lv_e_str_bp_calc  TYPE CMS_STR_BP_OVR_BP_CALC, "   
lv_e_tab_rc  TYPE CMS_TAB_MSG_COL_MESSAGE, "   
lv_i_cag_typ  TYPE CMS_DTE_CAG_TYP. "   

  CALL FUNCTION 'CMS_API_BP_OVR_GET'  "Fetch data for the business partner overview
    EXPORTING
         I_BPID = lv_i_bpid
         I_TAB_BPF = lv_i_tab_bpf
         I_CAG_TYP = lv_i_cag_typ
    IMPORTING
         E_TAB_CON = lv_e_tab_con
         E_STR_BP_CALC = lv_e_str_bp_calc
         E_TAB_RC = lv_e_tab_rc
. " CMS_API_BP_OVR_GET




ABAP code using 7.40 inline data declarations to call FM CMS_API_BP_OVR_GET

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



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!