SAP VELO11_SOEU_EXECUTE Function Module for VELO : Aktion SOEU (Kundenauftrag für Gebrauchtfahrzeuge anlegen)
VELO11_SOEU_EXECUTE is a standard velo11 soeu execute 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 : Aktion SOEU (Kundenauftrag für Gebrauchtfahrzeuge anlegen) 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 velo11 soeu execute FM, simply by entering the name VELO11_SOEU_EXECUTE into the relevant SAP transaction such as SE37 or SE38.
Function Group: VELO11
Program Name: SAPLVELO11
Main Program: SAPLVELO11
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VELO11_SOEU_EXECUTE 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 'VELO11_SOEU_EXECUTE'"VELO : Aktion SOEU (Kundenauftrag für Gebrauchtfahrzeuge anlegen).
EXPORTING
* DIALOGUE_ALLOWED_IV = "Wenn das Flag gesetzt ist, sind z. B. Popups erlaubt.
* ABA_SOEU_IV = ABA_SOEU_GC "Type of Document for Action
CHANGING
VLCACTDATA_CS = "VELO : Übergabestruktur für Aktionen (Kopf und Positionen)
TABLES
VLCDIAVEHI_CT = "VELO : Dialogstruktur für Fahrzeuge
VLCH_MSSG_CT = "
VLCBAPICU_IT = "VELO : Enthält die Konfiguration mehrerer Fahrzeuge
EXCEPTIONS
DIFFERENT_KUNNR = 1 CONTR_ENTITY_NOT_FOUND = 2 DIFFERENT_CONTR_ENTITY = 3 CUSTOMER_DATA_NOT_FOUND = 4 VEHIUSAGE_NOT_FOUND = 5 PARTNER_ERROR = 6 ACTION_NOT_PERFORMED = 7 UPDATE_NOT_PERFORMED = 8
IMPORTING Parameters details for VELO11_SOEU_EXECUTE
DIALOGUE_ALLOWED_IV - Wenn das Flag gesetzt ist, sind z. B. Popups erlaubt.
Data type: COptional: Yes
Call by Reference: Yes
ABA_SOEU_IV - Type of Document for Action
Data type: VLC_ACTDOCTYPEDefault: ABA_SOEU_GC
Optional: Yes
Call by Reference: Yes
CHANGING Parameters details for VELO11_SOEU_EXECUTE
VLCACTDATA_CS - VELO : Übergabestruktur für Aktionen (Kopf und Positionen)
Data type: VLCACTDATAOptional: No
Call by Reference: Yes
TABLES Parameters details for VELO11_SOEU_EXECUTE
VLCDIAVEHI_CT - VELO : Dialogstruktur für Fahrzeuge
Data type: VLCDIAVEHIOptional: No
Call by Reference: No ( called with pass by value option)
VLCH_MSSG_CT -
Data type: VLCH_MSSG_PTOptional: No
Call by Reference: No ( called with pass by value option)
VLCBAPICU_IT - VELO : Enthält die Konfiguration mehrerer Fahrzeuge
Data type: VLCBAPICU_TOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DIFFERENT_KUNNR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CONTR_ENTITY_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DIFFERENT_CONTR_ENTITY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CUSTOMER_DATA_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
VEHIUSAGE_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARTNER_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ACTION_NOT_PERFORMED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UPDATE_NOT_PERFORMED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for VELO11_SOEU_EXECUTE 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_vlcactdata_cs | TYPE VLCACTDATA, " | |||
| lt_vlcdiavehi_ct | TYPE STANDARD TABLE OF VLCDIAVEHI, " | |||
| lv_different_kunnr | TYPE VLCDIAVEHI, " | |||
| lv_dialogue_allowed_iv | TYPE C, " | |||
| lv_aba_soeu_iv | TYPE VLC_ACTDOCTYPE, " ABA_SOEU_GC | |||
| lt_vlch_mssg_ct | TYPE STANDARD TABLE OF VLCH_MSSG_PT, " | |||
| lv_contr_entity_not_found | TYPE VLCH_MSSG_PT, " | |||
| lt_vlcbapicu_it | TYPE STANDARD TABLE OF VLCBAPICU_T, " | |||
| lv_different_contr_entity | TYPE VLCBAPICU_T, " | |||
| lv_customer_data_not_found | TYPE VLCBAPICU_T, " | |||
| lv_vehiusage_not_found | TYPE VLCBAPICU_T, " | |||
| lv_partner_error | TYPE VLCBAPICU_T, " | |||
| lv_action_not_performed | TYPE VLCBAPICU_T, " | |||
| lv_update_not_performed | TYPE VLCBAPICU_T. " |
|   CALL FUNCTION 'VELO11_SOEU_EXECUTE' "VELO : Aktion SOEU (Kundenauftrag für Gebrauchtfahrzeuge anlegen) |
| EXPORTING | ||
| DIALOGUE_ALLOWED_IV | = lv_dialogue_allowed_iv | |
| ABA_SOEU_IV | = lv_aba_soeu_iv | |
| CHANGING | ||
| VLCACTDATA_CS | = lv_vlcactdata_cs | |
| TABLES | ||
| VLCDIAVEHI_CT | = lt_vlcdiavehi_ct | |
| VLCH_MSSG_CT | = lt_vlch_mssg_ct | |
| VLCBAPICU_IT | = lt_vlcbapicu_it | |
| EXCEPTIONS | ||
| DIFFERENT_KUNNR = 1 | ||
| CONTR_ENTITY_NOT_FOUND = 2 | ||
| DIFFERENT_CONTR_ENTITY = 3 | ||
| CUSTOMER_DATA_NOT_FOUND = 4 | ||
| VEHIUSAGE_NOT_FOUND = 5 | ||
| PARTNER_ERROR = 6 | ||
| ACTION_NOT_PERFORMED = 7 | ||
| UPDATE_NOT_PERFORMED = 8 | ||
| . " VELO11_SOEU_EXECUTE | ||
ABAP code using 7.40 inline data declarations to call FM VELO11_SOEU_EXECUTE
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_aba_soeu_iv) | = ABA_SOEU_GC. | |||
Search for further information about these or an SAP related objects