SAP VELO04_READ_CVLC03 Function Module for VELO : Lesen der CVLC03
VELO04_READ_CVLC03 is a standard velo04 read cvlc03 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for VELO : Lesen der CVLC03 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 velo04 read cvlc03 FM, simply by entering the name VELO04_READ_CVLC03 into the relevant SAP transaction such as SE37 or SE38.
Function Group: VELO04
Program Name: SAPLVELO04
Main Program: SAPLVELO04
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VELO04_READ_CVLC03 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 'VELO04_READ_CVLC03'"VELO : Lesen der CVLC03.
EXPORTING
ACTION_IV = "Aktion
IMPORTING
ACTION_ES = "VELO : Aktionen
EXCEPTIONS
ACTION_NOT_DEFINED = 1
IMPORTING Parameters details for VELO04_READ_CVLC03
ACTION_IV - Aktion
Data type: CVLC03-AKTIONOptional: No
Call by Reference: Yes
EXPORTING Parameters details for VELO04_READ_CVLC03
ACTION_ES - VELO : Aktionen
Data type: CVLC03Optional: No
Call by Reference: Yes
EXCEPTIONS details
ACTION_NOT_DEFINED - Aktion ist nicht definiert
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VELO04_READ_CVLC03 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_action_es | TYPE CVLC03, " | |||
| lv_action_iv | TYPE CVLC03-AKTION, " | |||
| lv_action_not_defined | TYPE CVLC03. " |
|   CALL FUNCTION 'VELO04_READ_CVLC03' "VELO : Lesen der CVLC03 |
| EXPORTING | ||
| ACTION_IV | = lv_action_iv | |
| IMPORTING | ||
| ACTION_ES | = lv_action_es | |
| EXCEPTIONS | ||
| ACTION_NOT_DEFINED = 1 | ||
| . " VELO04_READ_CVLC03 | ||
ABAP code using 7.40 inline data declarations to call FM VELO04_READ_CVLC03
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 AKTION FROM CVLC03 INTO @DATA(ld_action_iv). | ||||
Search for further information about these or an SAP related objects