SAP BD_CO_GET_METER_READING_DATES Function Module for UCES: Meter Reading Times for Contract
BD_CO_GET_METER_READING_DATES is a standard bd co get meter reading dates 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: Meter Reading Times for Contract 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 meter reading dates FM, simply by entering the name BD_CO_GET_METER_READING_DATES 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_METER_READING_DATES 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_METER_READING_DATES'"UCES: Meter Reading Times for Contract.
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
E_MR_DATA = "UCES: Data for Consumption History
RETURN = "Return Parameter(s)
TABLES
* XT_UCES_EXTENSION = "UCES: Display Customer-Specific Fields from JSP
IMPORTING Parameters details for BD_CO_GET_METER_READING_DATES
I_PARTNER - Business Partner Number
Data type: GPART_KKOptional: No
Call by Reference: No ( called with pass by value option)
I_ACCOUNT - Contract Account Number
Data type: VKONT_KKOptional: No
Call by Reference: No ( called with pass by value option)
I_SPRAS - Language Key
Data type: SPRASDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CONTRACT - Contract
Data type: VERTRAGOptional: No
Call by Reference: No ( called with pass by value option)
I_DATE - Date
Data type: DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BD_CO_GET_METER_READING_DATES
E_MR_DATA - UCES: Data for Consumption History
Data type: UCES_TAB_CO_MR_DATEOptional: No
Call by Reference: No ( called with pass by value option)
RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BD_CO_GET_METER_READING_DATES
XT_UCES_EXTENSION - UCES: Display Customer-Specific Fields from JSP
Data type: UCES_TAB_DUMMYOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BD_CO_GET_METER_READING_DATES 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_e_mr_data | TYPE UCES_TAB_CO_MR_DATE, " | |||
| lv_i_partner | TYPE GPART_KK, " | |||
| lt_xt_uces_extension | TYPE STANDARD TABLE OF UCES_TAB_DUMMY, " | |||
| lv_return | TYPE BAPIRET2, " | |||
| lv_i_account | TYPE VKONT_KK, " | |||
| lv_i_spras | TYPE SPRAS, " SY-LANGU | |||
| lv_i_contract | TYPE VERTRAG, " | |||
| lv_i_date | TYPE DATUM. " SY-DATUM |
|   CALL FUNCTION 'BD_CO_GET_METER_READING_DATES' "UCES: Meter Reading Times for Contract |
| EXPORTING | ||
| I_PARTNER | = lv_i_partner | |
| I_ACCOUNT | = lv_i_account | |
| I_SPRAS | = lv_i_spras | |
| I_CONTRACT | = lv_i_contract | |
| I_DATE | = lv_i_date | |
| IMPORTING | ||
| E_MR_DATA | = lv_e_mr_data | |
| RETURN | = lv_return | |
| TABLES | ||
| XT_UCES_EXTENSION | = lt_xt_uces_extension | |
| . " BD_CO_GET_METER_READING_DATES | ||
ABAP code using 7.40 inline data declarations to call FM BD_CO_GET_METER_READING_DATES
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_i_spras) | = SY-LANGU. | |||
| DATA(ld_i_date) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects