SAP VELO14_READ_SALESCAMPAGNTXT Function Module for VELO : Verkaufskampagne lesen
VELO14_READ_SALESCAMPAGNTXT is a standard velo14 read salescampagntxt 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 : Verkaufskampagne lesen 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 velo14 read salescampagntxt FM, simply by entering the name VELO14_READ_SALESCAMPAGNTXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: VELO14
Program Name: SAPLVELO14
Main Program: SAPLVELO14
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VELO14_READ_SALESCAMPAGNTXT 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 'VELO14_READ_SALESCAMPAGNTXT'"VELO : Verkaufskampagne lesen.
TABLES
VLCDIAVEHI_CONF_IT = "VELO : Tabellentyp für die VLCDIAVEHI
SALESCAMPGN_ET = "
EXCEPTIONS
ERROR_OCCURED = 1
TABLES Parameters details for VELO14_READ_SALESCAMPAGNTXT
VLCDIAVEHI_CONF_IT - VELO : Tabellentyp für die VLCDIAVEHI
Data type: VLCDIAVEHI_CONF_TOptional: No
Call by Reference: No ( called with pass by value option)
SALESCAMPGN_ET -
Data type: VLCC_SALESCAMPGN_PTOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VELO14_READ_SALESCAMPAGNTXT 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_error_occured | TYPE STRING, " | |||
| lt_vlcdiavehi_conf_it | TYPE STANDARD TABLE OF VLCDIAVEHI_CONF_T, " | |||
| lt_salescampgn_et | TYPE STANDARD TABLE OF VLCC_SALESCAMPGN_PT. " |
|   CALL FUNCTION 'VELO14_READ_SALESCAMPAGNTXT' "VELO : Verkaufskampagne lesen |
| TABLES | ||
| VLCDIAVEHI_CONF_IT | = lt_vlcdiavehi_conf_it | |
| SALESCAMPGN_ET | = lt_salescampgn_et | |
| EXCEPTIONS | ||
| ERROR_OCCURED = 1 | ||
| . " VELO14_READ_SALESCAMPAGNTXT | ||
ABAP code using 7.40 inline data declarations to call FM VELO14_READ_SALESCAMPAGNTXT
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