SAP COMPONENT_VARIANT_EDIT Function Module for NOTRANSL: Workflow Methode: Ändern der PVS Variante
COMPONENT_VARIANT_EDIT is a standard component variant edit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Workflow Methode: Ändern der PVS Variante 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 component variant edit FM, simply by entering the name COMPONENT_VARIANT_EDIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CPPEWF
Program Name: SAPLCPPEWF
Main Program: SAPLCPPEWF
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COMPONENT_VARIANT_EDIT 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 'COMPONENT_VARIANT_EDIT'"NOTRANSL: Workflow Methode: Ändern der PVS Variante.
EXPORTING
VARIANT_ID = "CHAR32 GUID for iPPE Variant with Conversion
CHANGE_NO = "Change Number in iPPE
EXCEPTIONS
CANNOT_EDIT = 1
IMPORTING Parameters details for COMPONENT_VARIANT_EDIT
VARIANT_ID - CHAR32 GUID for iPPE Variant with Conversion
Data type: BAPI1176_CMP_VARIANTDATA-VARIANT_IDOptional: No
Call by Reference: Yes
CHANGE_NO - Change Number in iPPE
Data type: BAPI1176_CMP_VARIANTDATA-CHANGE_NOOptional: No
Call by Reference: Yes
EXCEPTIONS details
CANNOT_EDIT - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for COMPONENT_VARIANT_EDIT 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_variant_id | TYPE BAPI1176_CMP_VARIANTDATA-VARIANT_ID, " | |||
| lv_cannot_edit | TYPE BAPI1176_CMP_VARIANTDATA, " | |||
| lv_change_no | TYPE BAPI1176_CMP_VARIANTDATA-CHANGE_NO. " |
|   CALL FUNCTION 'COMPONENT_VARIANT_EDIT' "NOTRANSL: Workflow Methode: Ändern der PVS Variante |
| EXPORTING | ||
| VARIANT_ID | = lv_variant_id | |
| CHANGE_NO | = lv_change_no | |
| EXCEPTIONS | ||
| CANNOT_EDIT = 1 | ||
| . " COMPONENT_VARIANT_EDIT | ||
ABAP code using 7.40 inline data declarations to call FM COMPONENT_VARIANT_EDIT
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 VARIANT_ID FROM BAPI1176_CMP_VARIANTDATA INTO @DATA(ld_variant_id). | ||||
| "SELECT single CHANGE_NO FROM BAPI1176_CMP_VARIANTDATA INTO @DATA(ld_change_no). | ||||
Search for further information about these or an SAP related objects