SAP FVDS_OBJ_ASSIGN_GET_SINGLE Function Module for Loans: Determine Object Assignments for the Contract
FVDS_OBJ_ASSIGN_GET_SINGLE is a standard fvds obj assign get single SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Loans: Determine Object Assignments for the 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 fvds obj assign get single FM, simply by entering the name FVDS_OBJ_ASSIGN_GET_SINGLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVDS
Program Name: SAPLFVDS
Main Program: SAPLFVDS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVDS_OBJ_ASSIGN_GET_SINGLE 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 'FVDS_OBJ_ASSIGN_GET_SINGLE'"Loans: Determine Object Assignments for the Contract.
EXPORTING
* I_BUKRS = "Company Code
* I_RANL = "Contract Number
* I_ROBJNR = "Collateral Object Number
* I_SOBJKAT = "Objektklasse hinsichtlich der Art der Sicherheit
* I_FLG_COPY_CMS = ' ' "
IMPORTING
E_TAB_VDARLOBJ = "Table Type for Table VDHOBJ (Collateral Object)
E_FLG_CMS = "CMS aktiv: TRUE (='X') und FALSE (=' ')
EXCEPTIONS
NOT_FOUND = 1 NO_VALID_PARAMETERS = 2 COPY_NOT_POSSIBLE = 3
IMPORTING Parameters details for FVDS_OBJ_ASSIGN_GET_SINGLE
I_BUKRS - Company Code
Data type: BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_RANL - Contract Number
Data type: RANLOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ROBJNR - Collateral Object Number
Data type: ROBJNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_SOBJKAT - Objektklasse hinsichtlich der Art der Sicherheit
Data type: SOBJKATOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_COPY_CMS -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FVDS_OBJ_ASSIGN_GET_SINGLE
E_TAB_VDARLOBJ - Table Type for Table VDHOBJ (Collateral Object)
Data type: TRTY_VDARLOBJOptional: No
Call by Reference: No ( called with pass by value option)
E_FLG_CMS - CMS aktiv: TRUE (='X') und FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - Object does not exist
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_VALID_PARAMETERS - keine gültigen Selektionsparameter
Data type:Optional: No
Call by Reference: Yes
COPY_NOT_POSSIBLE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVDS_OBJ_ASSIGN_GET_SINGLE 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_vdarlobj | TYPE TRTY_VDARLOBJ, " | |||
| lv_i_ranl | TYPE RANL, " | |||
| lv_e_flg_cms | TYPE BOOLE_D, " | |||
| lv_no_valid_parameters | TYPE BOOLE_D, " | |||
| lv_i_robjnr | TYPE ROBJNR, " | |||
| lv_copy_not_possible | TYPE ROBJNR, " | |||
| lv_i_sobjkat | TYPE SOBJKAT, " | |||
| lv_i_flg_copy_cms | TYPE XFELD. " SPACE |
|   CALL FUNCTION 'FVDS_OBJ_ASSIGN_GET_SINGLE' "Loans: Determine Object Assignments for the Contract |
| EXPORTING | ||
| I_BUKRS | = lv_i_bukrs | |
| I_RANL | = lv_i_ranl | |
| I_ROBJNR | = lv_i_robjnr | |
| I_SOBJKAT | = lv_i_sobjkat | |
| I_FLG_COPY_CMS | = lv_i_flg_copy_cms | |
| IMPORTING | ||
| E_TAB_VDARLOBJ | = lv_e_tab_vdarlobj | |
| E_FLG_CMS | = lv_e_flg_cms | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| NO_VALID_PARAMETERS = 2 | ||
| COPY_NOT_POSSIBLE = 3 | ||
| . " FVDS_OBJ_ASSIGN_GET_SINGLE | ||
ABAP code using 7.40 inline data declarations to call FM FVDS_OBJ_ASSIGN_GET_SINGLE
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_flg_copy_cms) | = ' '. | |||
Search for further information about these or an SAP related objects