SAP FVD_CBR_OBJ_PROCESS_RFC Function Module for Data Reported to Credit Bureau About Parallel Processing
FVD_CBR_OBJ_PROCESS_RFC is a standard fvd cbr obj process rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Data Reported to Credit Bureau About Parallel Processing 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 fvd cbr obj process rfc FM, simply by entering the name FVD_CBR_OBJ_PROCESS_RFC into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_CBR_PROCESS
Program Name: SAPLFVD_CBR_PROCESS
Main Program: SAPLFVD_CBR_PROCESS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FVD_CBR_OBJ_PROCESS_RFC 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_CBR_OBJ_PROCESS_RFC'"Data Reported to Credit Bureau About Parallel Processing.
EXPORTING
I_CREATION_DATE = "Created Date
I_CREATION_TIME = "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
I_APP_LOG_OBJECT = "Application Log: Object Name (Application Code)
I_SIMULATION = "New Input Values
I_TAB_VDCBR_KEY = "Key for Data Supply to Credit Bureau
I_EXT_LOGNO = "Application Log: External Identification
IMPORTING
E_TAB_VDCBR_HIST = "Histry of Data Reported to Credit Bureau
E_TAB_VDCBR_RES_DATA = "Table of Credit Bureau Data Reported Per Loan
E_TAB_VDCBR_RES_PART = "Partner Data Reported for Credit Bureau
E_STR_VDCBR_RES_HT = "Header and Totals Records for Data Reported to Credit Bureau
IMPORTING Parameters details for FVD_CBR_OBJ_PROCESS_RFC
I_CREATION_DATE - Created Date
Data type: TB_CBR_CREATION_DATEOptional: No
Call by Reference: No ( called with pass by value option)
I_CREATION_TIME - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
Data type: TIMESTAMPOptional: No
Call by Reference: No ( called with pass by value option)
I_APP_LOG_OBJECT - Application Log: Object Name (Application Code)
Data type: BALOBJ_DOptional: No
Call by Reference: No ( called with pass by value option)
I_SIMULATION - New Input Values
Data type: XFLAGOptional: No
Call by Reference: No ( called with pass by value option)
I_TAB_VDCBR_KEY - Key for Data Supply to Credit Bureau
Data type: TRTY_RVD_CBR_KEYOptional: No
Call by Reference: No ( called with pass by value option)
I_EXT_LOGNO - Application Log: External Identification
Data type: BALNREXTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVD_CBR_OBJ_PROCESS_RFC
E_TAB_VDCBR_HIST - Histry of Data Reported to Credit Bureau
Data type: TRTY_VDCBR_HISTOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_VDCBR_RES_DATA - Table of Credit Bureau Data Reported Per Loan
Data type: TRTY_VDCBR_RES_DATAOptional: No
Call by Reference: No ( called with pass by value option)
E_TAB_VDCBR_RES_PART - Partner Data Reported for Credit Bureau
Data type: TRTY_VDCBR_RES_PARTOptional: No
Call by Reference: No ( called with pass by value option)
E_STR_VDCBR_RES_HT - Header and Totals Records for Data Reported to Credit Bureau
Data type: VDCBR_RES_HTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FVD_CBR_OBJ_PROCESS_RFC 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_creation_date | TYPE TB_CBR_CREATION_DATE, " | |||
| lv_e_tab_vdcbr_hist | TYPE TRTY_VDCBR_HIST, " | |||
| lv_i_creation_time | TYPE TIMESTAMP, " | |||
| lv_e_tab_vdcbr_res_data | TYPE TRTY_VDCBR_RES_DATA, " | |||
| lv_i_app_log_object | TYPE BALOBJ_D, " | |||
| lv_e_tab_vdcbr_res_part | TYPE TRTY_VDCBR_RES_PART, " | |||
| lv_i_simulation | TYPE XFLAG, " | |||
| lv_e_str_vdcbr_res_ht | TYPE VDCBR_RES_HT, " | |||
| lv_i_tab_vdcbr_key | TYPE TRTY_RVD_CBR_KEY, " | |||
| lv_i_ext_logno | TYPE BALNREXT. " |
|   CALL FUNCTION 'FVD_CBR_OBJ_PROCESS_RFC' "Data Reported to Credit Bureau About Parallel Processing |
| EXPORTING | ||
| I_CREATION_DATE | = lv_i_creation_date | |
| I_CREATION_TIME | = lv_i_creation_time | |
| I_APP_LOG_OBJECT | = lv_i_app_log_object | |
| I_SIMULATION | = lv_i_simulation | |
| I_TAB_VDCBR_KEY | = lv_i_tab_vdcbr_key | |
| I_EXT_LOGNO | = lv_i_ext_logno | |
| IMPORTING | ||
| E_TAB_VDCBR_HIST | = lv_e_tab_vdcbr_hist | |
| E_TAB_VDCBR_RES_DATA | = lv_e_tab_vdcbr_res_data | |
| E_TAB_VDCBR_RES_PART | = lv_e_tab_vdcbr_res_part | |
| E_STR_VDCBR_RES_HT | = lv_e_str_vdcbr_res_ht | |
| . " FVD_CBR_OBJ_PROCESS_RFC | ||
ABAP code using 7.40 inline data declarations to call FM FVD_CBR_OBJ_PROCESS_RFC
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