SAP VELO24_VMS_INITIAL_LOAD Function Module for Initiales Befüllen des LiveCache









VELO24_VMS_INITIAL_LOAD is a standard velo24 vms initial load SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initiales Befüllen des LiveCache 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 velo24 vms initial load FM, simply by entering the name VELO24_VMS_INITIAL_LOAD into the relevant SAP transaction such as SE37 or SE38.

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



Function VELO24_VMS_INITIAL_LOAD 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 'VELO24_VMS_INITIAL_LOAD'"Initiales Befüllen des LiveCache
EXPORTING
* PACKSIZE_IV = 5000 "Packetgröße
CONNID_IV = "Logischer Name einer Datenbankverbindung
* SYMTABNAME_IV = ' ' "Datenbanktabelle

EXCEPTIONS
FINAL_STATUS_UPDATE_FAILED = 1 SYMBOL_LOADING_FAILED = 10 DISCONNECTION_FAILED = 11 INITIAL_STATUS_UPDATE_FAILED = 12 CUST_READ_FAILED = 13 TARGET_LOADING_FAILED = 14 BADI_EXCEPTION = 15 DATABASE_ERROR = 2 CONNECTION_NOT_FOUND = 3 NO_CUST_ENTRIES_READ = 4 CONNECTION_FAILED = 5 INIT_FAILED = 6 NO_SYMBOLS_READ = 7 TARGET_CREATION_FAILED = 8 PATH_BUILDING_FAILED = 9
.



IMPORTING Parameters details for VELO24_VMS_INITIAL_LOAD

PACKSIZE_IV - Packetgröße

Data type: VLC_PACKSIZE
Default: 5000
Optional: No
Call by Reference: Yes

CONNID_IV - Logischer Name einer Datenbankverbindung

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

SYMTABNAME_IV - Datenbanktabelle

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

EXCEPTIONS details

FINAL_STATUS_UPDATE_FAILED -

Data type:
Optional: No
Call by Reference: Yes

SYMBOL_LOADING_FAILED -

Data type:
Optional: No
Call by Reference: Yes

DISCONNECTION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

INITIAL_STATUS_UPDATE_FAILED -

Data type:
Optional: No
Call by Reference: Yes

CUST_READ_FAILED -

Data type:
Optional: No
Call by Reference: Yes

TARGET_LOADING_FAILED -

Data type:
Optional: No
Call by Reference: Yes

BADI_EXCEPTION -

Data type:
Optional: No
Call by Reference: Yes

DATABASE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

CONNECTION_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NO_CUST_ENTRIES_READ -

Data type:
Optional: No
Call by Reference: Yes

CONNECTION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

INIT_FAILED -

Data type:
Optional: No
Call by Reference: Yes

NO_SYMBOLS_READ -

Data type:
Optional: No
Call by Reference: Yes

TARGET_CREATION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

PATH_BUILDING_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for VELO24_VMS_INITIAL_LOAD 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_packsize_iv  TYPE VLC_PACKSIZE, "   5000
lv_final_status_update_failed  TYPE VLC_PACKSIZE, "   
lv_symbol_loading_failed  TYPE VLC_PACKSIZE, "   
lv_disconnection_failed  TYPE VLC_PACKSIZE, "   
lv_initial_status_update_failed  TYPE VLC_PACKSIZE, "   
lv_cust_read_failed  TYPE VLC_PACKSIZE, "   
lv_target_loading_failed  TYPE VLC_PACKSIZE, "   
lv_badi_exception  TYPE VLC_PACKSIZE, "   
lv_connid_iv  TYPE DBCON_NAME, "   
lv_database_error  TYPE DBCON_NAME, "   
lv_symtabname_iv  TYPE DBTABL, "   ' '
lv_connection_not_found  TYPE DBTABL, "   
lv_no_cust_entries_read  TYPE DBTABL, "   
lv_connection_failed  TYPE DBTABL, "   
lv_init_failed  TYPE DBTABL, "   
lv_no_symbols_read  TYPE DBTABL, "   
lv_target_creation_failed  TYPE DBTABL, "   
lv_path_building_failed  TYPE DBTABL. "   

  CALL FUNCTION 'VELO24_VMS_INITIAL_LOAD'  "Initiales Befüllen des LiveCache
    EXPORTING
         PACKSIZE_IV = lv_packsize_iv
         CONNID_IV = lv_connid_iv
         SYMTABNAME_IV = lv_symtabname_iv
    EXCEPTIONS
        FINAL_STATUS_UPDATE_FAILED = 1
        SYMBOL_LOADING_FAILED = 10
        DISCONNECTION_FAILED = 11
        INITIAL_STATUS_UPDATE_FAILED = 12
        CUST_READ_FAILED = 13
        TARGET_LOADING_FAILED = 14
        BADI_EXCEPTION = 15
        DATABASE_ERROR = 2
        CONNECTION_NOT_FOUND = 3
        NO_CUST_ENTRIES_READ = 4
        CONNECTION_FAILED = 5
        INIT_FAILED = 6
        NO_SYMBOLS_READ = 7
        TARGET_CREATION_FAILED = 8
        PATH_BUILDING_FAILED = 9
. " VELO24_VMS_INITIAL_LOAD




ABAP code using 7.40 inline data declarations to call FM VELO24_VMS_INITIAL_LOAD

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_packsize_iv) = 5000.
 
 
 
 
 
 
 
 
 
 
DATA(ld_symtabname_iv) = ' '.
 
 
 
 
 
 
 
 


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!