SAP BD_CO_GET_CUSTOM Function Module for UCES: Custom Data for Customer-Specific TAB in Contract Overview

Search SAP Function Modules

BD_CO_GET_CUSTOM is a standard bd co get custom SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for UCES: Custom Data for Customer-Specific TAB in Contract 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 bd co get custom FM, simply by entering the name BD_CO_GET_CUSTOM into the relevant SAP transaction such as SE37 or SE38.

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

Function BD_CO_GET_CUSTOM 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 'BD_CO_GET_CUSTOM'"UCES: Custom Data for Customer-Specific TAB in Contract Overview
  EXPORTING
   I_PARTNER =  "Business Partner Number
   I_ACCOUNT =  "Contract Account Number
*  I_SPRAS = SY-LANGU "Language Key
   I_CONTRACT =  "Contract
*  I_DATE = SY-DATUM "Date

 IMPORTING
   RETURN =  "Return Parameter(s)
   E_TAB_NAME =  "UCES: Texts

TABLES
*  XT_UCES_EXTENSION =  "UCES: Display Customer-Specific Fields from JSP

.

IMPORTING Parameters details for BD_CO_GET_CUSTOM

I_PARTNER - Business Partner Number

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

I_ACCOUNT - Contract Account Number

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

I_SPRAS - Language Key

Data type: SPRAS
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CONTRACT - Contract

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

I_DATE - Date

Data type: DATUM
Default: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BD_CO_GET_CUSTOM

RETURN - Return Parameter(s)

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

E_TAB_NAME - UCES: Texts

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

TABLES Parameters details for BD_CO_GET_CUSTOM

XT_UCES_EXTENSION - UCES: Display Customer-Specific Fields from JSP

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

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

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