SAP VE_SET_OBJ_RELATIONSHIP Function Module for Set VE objects relationship
VE_SET_OBJ_RELATIONSHIP is a standard ve set obj relationship SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set VE objects relationship 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 ve set obj relationship FM, simply by entering the name VE_SET_OBJ_RELATIONSHIP into the relevant SAP transaction such as SE37 or SE38.
Function Group: CV_VE_DATA_EXTRACTION
Program Name: SAPLCV_VE_DATA_EXTRACTION
Main Program: SAPLCV_VE_DATA_EXTRACTION
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function VE_SET_OBJ_RELATIONSHIP 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 'VE_SET_OBJ_RELATIONSHIP'"Set VE objects relationship.
EXPORTING
IT_VE_RELATION = "Table type of VERELATION table
IMPORTING
ET_MESSAGE = "List of Messages of Type BAPIRET1
IMPORTING Parameters details for VE_SET_OBJ_RELATIONSHIP
IT_VE_RELATION - Table type of VERELATION table
Data type: VEOBJ_T_RELATIONOptional: No
Call by Reference: Yes
EXPORTING Parameters details for VE_SET_OBJ_RELATIONSHIP
ET_MESSAGE - List of Messages of Type BAPIRET1
Data type: VE_T_BAPIRET1Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for VE_SET_OBJ_RELATIONSHIP 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_et_message | TYPE VE_T_BAPIRET1, " | |||
| lv_it_ve_relation | TYPE VEOBJ_T_RELATION. " |
|   CALL FUNCTION 'VE_SET_OBJ_RELATIONSHIP' "Set VE objects relationship |
| EXPORTING | ||
| IT_VE_RELATION | = lv_it_ve_relation | |
| IMPORTING | ||
| ET_MESSAGE | = lv_et_message | |
| . " VE_SET_OBJ_RELATIONSHIP | ||
ABAP code using 7.40 inline data declarations to call FM VE_SET_OBJ_RELATIONSHIP
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