SAP FVD_RFC_COLLATERALS_GETDETAIL Function Module for Loan RFC: Detailed Data for Collateral
FVD_RFC_COLLATERALS_GETDETAIL is a standard fvd rfc collaterals getdetail SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Loan RFC: Detailed Data for Collateral 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 rfc collaterals getdetail FM, simply by entering the name FVD_RFC_COLLATERALS_GETDETAIL into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_RFC_COLLATERALS
Program Name: SAPLFVD_RFC_COLLATERALS
Main Program: SAPLFVD_RFC_COLLATERALS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FVD_RFC_COLLATERALS_GETDETAIL 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_RFC_COLLATERALS_GETDETAIL'"Loan RFC: Detailed Data for Collateral.
EXPORTING
COLLATERALID = "Collateral Reference Number
IMPORTING
POLICY = "Contracts/Credit (Life Ins., Build.Savings Etc) Basic Data
LOAN = "Loan Collateral in Accordance with BAV/PRF4
STOCK = "Collateral in Securities in Accordance with BAV/PRF5
USERFIELDS = "Sort Values for Object
ERROR = "Error Indicator in BAPIs
TABLES
* EXPIRYDATA = "Ablaufleistung der Lebensversicherung
* PARTNER = "Assignment of Partner to Contract
* ARRANGEMENT = "Special arrangements
* ARRANGEMENTPARTNER = "Geschäftspartnerzuordnung der Sondervereinbarungenect
* RETURN = "Confirmation of Results
IMPORTING Parameters details for FVD_RFC_COLLATERALS_GETDETAIL
COLLATERALID - Collateral Reference Number
Data type: RSICHEROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVD_RFC_COLLATERALS_GETDETAIL
POLICY - Contracts/Credit (Life Ins., Build.Savings Etc) Basic Data
Data type: BAPICOLL_POLICYOptional: No
Call by Reference: No ( called with pass by value option)
LOAN - Loan Collateral in Accordance with BAV/PRF4
Data type: BAPICOLL_LOANOptional: No
Call by Reference: No ( called with pass by value option)
STOCK - Collateral in Securities in Accordance with BAV/PRF5
Data type: BAPICOLL_STOCKOptional: No
Call by Reference: No ( called with pass by value option)
USERFIELDS - Sort Values for Object
Data type: BAPILOAN_USERFIELDSOptional: No
Call by Reference: No ( called with pass by value option)
ERROR - Error Indicator in BAPIs
Data type: BAPILOAN_COMMON-ERROROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FVD_RFC_COLLATERALS_GETDETAIL
EXPIRYDATA - Ablaufleistung der Lebensversicherung
Data type: BAPICOLL_EXPIRYDATAOptional: Yes
Call by Reference: Yes
PARTNER - Assignment of Partner to Contract
Data type: BAPIREL_BPOBJOptional: Yes
Call by Reference: Yes
ARRANGEMENT - Special arrangements
Data type: BAPICOLL_ARRANGEMENTOptional: Yes
Call by Reference: Yes
ARRANGEMENTPARTNER - Geschäftspartnerzuordnung der Sondervereinbarungenect
Data type: BAPIREL_BPOBJOptional: Yes
Call by Reference: Yes
RETURN - Confirmation of Results
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FVD_RFC_COLLATERALS_GETDETAIL 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_policy | TYPE BAPICOLL_POLICY, " | |||
| lt_expirydata | TYPE STANDARD TABLE OF BAPICOLL_EXPIRYDATA, " | |||
| lv_collateralid | TYPE RSICHER, " | |||
| lv_loan | TYPE BAPICOLL_LOAN, " | |||
| lt_partner | TYPE STANDARD TABLE OF BAPIREL_BPOBJ, " | |||
| lv_stock | TYPE BAPICOLL_STOCK, " | |||
| lt_arrangement | TYPE STANDARD TABLE OF BAPICOLL_ARRANGEMENT, " | |||
| lv_userfields | TYPE BAPILOAN_USERFIELDS, " | |||
| lt_arrangementpartner | TYPE STANDARD TABLE OF BAPIREL_BPOBJ, " | |||
| lv_error | TYPE BAPILOAN_COMMON-ERROR, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2. " |
|   CALL FUNCTION 'FVD_RFC_COLLATERALS_GETDETAIL' "Loan RFC: Detailed Data for Collateral |
| EXPORTING | ||
| COLLATERALID | = lv_collateralid | |
| IMPORTING | ||
| POLICY | = lv_policy | |
| LOAN | = lv_loan | |
| STOCK | = lv_stock | |
| USERFIELDS | = lv_userfields | |
| ERROR | = lv_error | |
| TABLES | ||
| EXPIRYDATA | = lt_expirydata | |
| PARTNER | = lt_partner | |
| ARRANGEMENT | = lt_arrangement | |
| ARRANGEMENTPARTNER | = lt_arrangementpartner | |
| RETURN | = lt_return | |
| . " FVD_RFC_COLLATERALS_GETDETAIL | ||
ABAP code using 7.40 inline data declarations to call FM FVD_RFC_COLLATERALS_GETDETAIL
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.| "SELECT single ERROR FROM BAPILOAN_COMMON INTO @DATA(ld_error). | ||||
Search for further information about these or an SAP related objects