SAP FVD_RBD_GET_CHANGED_CONTRACTS Function Module for
FVD_RBD_GET_CHANGED_CONTRACTS is a standard fvd rbd get changed contracts SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fvd rbd get changed contracts FM, simply by entering the name FVD_RBD_GET_CHANGED_CONTRACTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_CML_RBD
Program Name: SAPLFVD_CML_RBD
Main Program: SAPLFVD_CML_RBD
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FVD_RBD_GET_CHANGED_CONTRACTS 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 'FVD_RBD_GET_CHANGED_CONTRACTS'".
EXPORTING
I_BUKRS = "
* I_RANGE_GSART = "
* I_RANGE_RANL = "
* I_DATE_FROM = "
* I_DATE_TO = "
* I_MADAT_FROM = SY-DATUM "
IMPORTING
E_TAB_VDARLKEY = "
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for FVD_RBD_GET_CHANGED_CONTRACTS
I_BUKRS -
Data type: BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_RANGE_GSART -
Data type: TRTY_GSART_RANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RANGE_RANL -
Data type: TRTY_RANL_RANGEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE_FROM -
Data type: DATUMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE_TO -
Data type: DATUMOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MADAT_FROM -
Data type: MADATDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVD_RBD_GET_CHANGED_CONTRACTS
E_TAB_VDARLKEY -
Data type: TRTY_VDARL_KEY_PWVOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_RBD_GET_CHANGED_CONTRACTS 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_bukrs | TYPE BUKRS, " | |||
| lv_not_found | TYPE BUKRS, " | |||
| lv_e_tab_vdarlkey | TYPE TRTY_VDARL_KEY_PWV, " | |||
| lv_i_range_gsart | TYPE TRTY_GSART_RANGE, " | |||
| lv_i_range_ranl | TYPE TRTY_RANL_RANGE, " | |||
| lv_i_date_from | TYPE DATUM, " | |||
| lv_i_date_to | TYPE DATUM, " | |||
| lv_i_madat_from | TYPE MADAT. " SY-DATUM |
|   CALL FUNCTION 'FVD_RBD_GET_CHANGED_CONTRACTS' " |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_RANGE_GSART | = lv_i_range_gsart | |
| I_RANGE_RANL | = lv_i_range_ranl | |
| I_DATE_FROM | = lv_i_date_from | |
| I_DATE_TO | = lv_i_date_to | |
| I_MADAT_FROM | = lv_i_madat_from | |
| IMPORTING | ||
| E_TAB_VDARLKEY | = lv_e_tab_vdarlkey | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " FVD_RBD_GET_CHANGED_CONTRACTS | ||
ABAP code using 7.40 inline data declarations to call FM FVD_RBD_GET_CHANGED_CONTRACTS
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_madat_from) | = SY-DATUM. | |||
Search for further information about these or an SAP related objects