SAP FVD_CONTRACT_MAPI_LOAN_GET Function Module for Display Master API Contract









FVD_CONTRACT_MAPI_LOAN_GET is a standard fvd contract mapi loan get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Display Master API 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 fvd contract mapi loan get FM, simply by entering the name FVD_CONTRACT_MAPI_LOAN_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVD_CONTRACT
Program Name: SAPLFVD_CONTRACT
Main Program: SAPLFVD_CONTRACT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FVD_CONTRACT_MAPI_LOAN_GET 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_CONTRACT_MAPI_LOAN_GET'"Display Master API Contract
  EXPORTING
   COMPANYCODE =  "Company Code
   LOANNUMBER =  "Contract Number
*  ARCHIVE = ' ' "Archiving Category Indicator
*  I_CALLN_APPLN = 'INT' "Calling Application

 IMPORTING
   LOAN =  "Loan
   USERFIELDS =  "Sort Values for Object
   CLERKS =  "Table Type for Table VDZSB
   FILES =  "File with documents for loan allocation
   FILE_DOCUMENTS =  "Table Type for Table VDUNTR
   PAYMENT_ADVICES =  "Table Type for VDAVIS
   ENCUMBRANCES =  "Table Type for Table VDHGRPF
   ERROR =  "TRUE (='X') and FALSE (=' ')
   PARTNER =  "Business Partner Assignment
   CONDITIONHEADER =  "Table Condition Header
   CONDITIONS =  "Table Type for Table VZZKOPO
   FORMULA =  "Table Type for Table VZZKOPA
   RECORDS =  "Table Type for Table VDBEPP
   OBJECTS =  "Tabellentyp Beleihungsobjekte
   COLLATERALS =  "Tabellentyp Sicherheiten
   CORRESPONDENCE =  "Print and Dispatch Control Data for VDARL
.



IMPORTING Parameters details for FVD_CONTRACT_MAPI_LOAN_GET

COMPANYCODE - Company Code

Data type: BUKRS
Optional: No
Call by Reference: No ( called with pass by value option)

LOANNUMBER - Contract Number

Data type: RANL
Optional: No
Call by Reference: No ( called with pass by value option)

ARCHIVE - Archiving Category Indicator

Data type: SARCHIV
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_CALLN_APPLN - Calling Application

Data type: TB_CALLNG_APPLN
Default: 'INT'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for FVD_CONTRACT_MAPI_LOAN_GET

LOAN - Loan

Data type: VDARL
Optional: No
Call by Reference: No ( called with pass by value option)

USERFIELDS - Sort Values for Object

Data type: VZSORT
Optional: No
Call by Reference: No ( called with pass by value option)

CLERKS - Table Type for Table VDZSB

Data type: TRTY_VDZSB
Optional: No
Call by Reference: No ( called with pass by value option)

FILES - File with documents for loan allocation

Data type: VDAKTE
Optional: No
Call by Reference: No ( called with pass by value option)

FILE_DOCUMENTS - Table Type for Table VDUNTR

Data type: TRTY_VDUNTR
Optional: No
Call by Reference: No ( called with pass by value option)

PAYMENT_ADVICES - Table Type for VDAVIS

Data type: TRTY_VDAVIS
Optional: No
Call by Reference: No ( called with pass by value option)

ENCUMBRANCES - Table Type for Table VDHGRPF

Data type: TRTY_VDHGRPF
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR - TRUE (='X') and FALSE (=' ')

Data type: BOOLE-BOOLE
Optional: No
Call by Reference: No ( called with pass by value option)

PARTNER - Business Partner Assignment

Data type: TRTY_VDGPO
Optional: No
Call by Reference: No ( called with pass by value option)

CONDITIONHEADER - Table Condition Header

Data type: TRTY_VZZKOKO
Optional: No
Call by Reference: No ( called with pass by value option)

CONDITIONS - Table Type for Table VZZKOPO

Data type: TRTY_VZZKOPO
Optional: No
Call by Reference: No ( called with pass by value option)

FORMULA - Table Type for Table VZZKOPA

Data type: TRTY_VZZKOPA
Optional: No
Call by Reference: No ( called with pass by value option)

RECORDS - Table Type for Table VDBEPP

Data type: TRTY_VDBEPP
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECTS - Tabellentyp Beleihungsobjekte

Data type: TRTY_VDARLOBJ
Optional: No
Call by Reference: No ( called with pass by value option)

COLLATERALS - Tabellentyp Sicherheiten

Data type: TRTY_VDARLSIC
Optional: No
Call by Reference: No ( called with pass by value option)

CORRESPONDENCE - Print and Dispatch Control Data for VDARL

Data type: VDARLDVS_EXT
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FVD_CONTRACT_MAPI_LOAN_GET 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_loan  TYPE VDARL, "   
lv_companycode  TYPE BUKRS, "   
lv_userfields  TYPE VZSORT, "   
lv_clerks  TYPE TRTY_VDZSB, "   
lv_files  TYPE VDAKTE, "   
lv_file_documents  TYPE TRTY_VDUNTR, "   
lv_payment_advices  TYPE TRTY_VDAVIS, "   
lv_encumbrances  TYPE TRTY_VDHGRPF, "   
lv_error  TYPE BOOLE-BOOLE, "   
lv_partner  TYPE TRTY_VDGPO, "   
lv_loannumber  TYPE RANL, "   
lv_archive  TYPE SARCHIV, "   SPACE
lv_conditionheader  TYPE TRTY_VZZKOKO, "   
lv_conditions  TYPE TRTY_VZZKOPO, "   
lv_i_calln_appln  TYPE TB_CALLNG_APPLN, "   'INT'
lv_formula  TYPE TRTY_VZZKOPA, "   
lv_records  TYPE TRTY_VDBEPP, "   
lv_objects  TYPE TRTY_VDARLOBJ, "   
lv_collaterals  TYPE TRTY_VDARLSIC, "   
lv_correspondence  TYPE VDARLDVS_EXT. "   

  CALL FUNCTION 'FVD_CONTRACT_MAPI_LOAN_GET'  "Display Master API Contract
    EXPORTING
         COMPANYCODE = lv_companycode
         LOANNUMBER = lv_loannumber
         ARCHIVE = lv_archive
         I_CALLN_APPLN = lv_i_calln_appln
    IMPORTING
         LOAN = lv_loan
         USERFIELDS = lv_userfields
         CLERKS = lv_clerks
         FILES = lv_files
         FILE_DOCUMENTS = lv_file_documents
         PAYMENT_ADVICES = lv_payment_advices
         ENCUMBRANCES = lv_encumbrances
         ERROR = lv_error
         PARTNER = lv_partner
         CONDITIONHEADER = lv_conditionheader
         CONDITIONS = lv_conditions
         FORMULA = lv_formula
         RECORDS = lv_records
         OBJECTS = lv_objects
         COLLATERALS = lv_collaterals
         CORRESPONDENCE = lv_correspondence
. " FVD_CONTRACT_MAPI_LOAN_GET




ABAP code using 7.40 inline data declarations to call FM FVD_CONTRACT_MAPI_LOAN_GET

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 BOOLE FROM BOOLE INTO @DATA(ld_error).
 
 
 
DATA(ld_archive) = ' '.
 
 
 
DATA(ld_i_calln_appln) = 'INT'.
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!