SAP FVDS_IMP_GET_DATA Function Module for Get Data from Memory or CMS









FVDS_IMP_GET_DATA is a standard fvds imp get data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Data from Memory or CMS 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 imp get data FM, simply by entering the name FVDS_IMP_GET_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function FVDS_IMP_GET_DATA 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_IMP_GET_DATA'"Get Data from Memory or CMS
EXPORTING
I_BUKRS = "Company Code
I_RANL = "Contract Number

EXCEPTIONS
DATA_NOT_FOUND = 1 CMS_NOT_ACTIV = 2 KEY_NOT_FILLED = 3
.



IMPORTING Parameters details for FVDS_IMP_GET_DATA

I_BUKRS - Company Code

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

I_RANL - Contract Number

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

EXCEPTIONS details

DATA_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

CMS_NOT_ACTIV -

Data type:
Optional: No
Call by Reference: Yes

KEY_NOT_FILLED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FVDS_IMP_GET_DATA 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 VDARL-BUKRS, "   
lv_data_not_found  TYPE VDARL, "   
lv_i_ranl  TYPE VDARL-RANL, "   
lv_cms_not_activ  TYPE VDARL, "   
lv_key_not_filled  TYPE VDARL. "   

  CALL FUNCTION 'FVDS_IMP_GET_DATA'  "Get Data from Memory or CMS
    EXPORTING
         I_BUKRS = lv_i_bukrs
         I_RANL = lv_i_ranl
    EXCEPTIONS
        DATA_NOT_FOUND = 1
        CMS_NOT_ACTIV = 2
        KEY_NOT_FILLED = 3
. " FVDS_IMP_GET_DATA




ABAP code using 7.40 inline data declarations to call FM FVDS_IMP_GET_DATA

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 BUKRS FROM VDARL INTO @DATA(ld_i_bukrs).
 
 
"SELECT single RANL FROM VDARL INTO @DATA(ld_i_ranl).
 
 
 


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!