SAP FVD_PPM_DB_READ_LINK Function Module for Read Entry in VDARL_PAYM_PLAN









FVD_PPM_DB_READ_LINK is a standard fvd ppm db read link SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Entry in VDARL_PAYM_PLAN 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 ppm db read link FM, simply by entering the name FVD_PPM_DB_READ_LINK into the relevant SAP transaction such as SE37 or SE38.

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



Function FVD_PPM_DB_READ_LINK 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_PPM_DB_READ_LINK'"Read Entry in VDARL_PAYM_PLAN
EXPORTING
I_BUKRS = "Company Code
I_RANL = "Contract Number
I_COMPONENT = "Component of Object to Which Premium Plan Belongs
I_EXT_KEY = "External Key for Objects for a Premium Plan

IMPORTING
E_PAYM_PLAN_KEY = "Key of a Condition for a Payment Plan

EXCEPTIONS
NOT_FOUND = 1 NOT_QUALIFIED = 2
.



IMPORTING Parameters details for FVD_PPM_DB_READ_LINK

I_BUKRS - Company Code

Data type: BUKRS
Optional: No
Call by Reference: Yes

I_RANL - Contract Number

Data type: RANL
Optional: No
Call by Reference: Yes

I_COMPONENT - Component of Object to Which Premium Plan Belongs

Data type: TB_PPM_COMPONENT
Optional: No
Call by Reference: Yes

I_EXT_KEY - External Key for Objects for a Premium Plan

Data type: TB_PPM_EXT_KEY
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FVD_PPM_DB_READ_LINK

E_PAYM_PLAN_KEY - Key of a Condition for a Payment Plan

Data type: RPPM_PP_KEY
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_FOUND - The record you want to delete does not exist

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

NOT_QUALIFIED - Die Eingabeparameter reichen nicht aus

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

Copy and paste ABAP code example for FVD_PPM_DB_READ_LINK 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_paym_plan_key  TYPE RPPM_PP_KEY, "   
lv_i_ranl  TYPE RANL, "   
lv_not_qualified  TYPE RANL, "   
lv_i_component  TYPE TB_PPM_COMPONENT, "   
lv_i_ext_key  TYPE TB_PPM_EXT_KEY. "   

  CALL FUNCTION 'FVD_PPM_DB_READ_LINK'  "Read Entry in VDARL_PAYM_PLAN
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_RANL = lv_i_ranl
         I_COMPONENT = lv_i_component
         I_EXT_KEY = lv_i_ext_key
    IMPORTING
         E_PAYM_PLAN_KEY = lv_e_paym_plan_key
    EXCEPTIONS
        NOT_FOUND = 1
        NOT_QUALIFIED = 2
. " FVD_PPM_DB_READ_LINK




ABAP code using 7.40 inline data declarations to call FM FVD_PPM_DB_READ_LINK

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



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!