SAP PLM_VARIANT_UPDATE Function Module for Change SMP variant extensions

Search SAP Function Modules

PLM_VARIANT_UPDATE is a standard plm variant update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change SMP variant extensions 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 plm variant update FM, simply by entering the name PLM_VARIANT_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: OGSL
Program Name: SAPLOGSL
Main Program: SAPLOGSL
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function PLM_VARIANT_UPDATE 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 'PLM_VARIANT_UPDATE'"Change SMP variant extensions
  EXPORTING
   REPORT =  "
   VARIANT =  "
   DISPLAY =  "

 IMPORTING
   NEW_VERSION =  "

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLOGSL_001 D28 : Put level maintance, get valid serial no status
EXIT_SAPLOGSL_002 OGM10006 - Put level maintance, get date for SC validation
EXIT_SAPLOGSL_003 OGM10002 - User exit to handle complex characteristic value comparison
EXIT_SAPLOGSL_004 OGM10003 - User exit to check whether SW material can be used in SMP
EXIT_SAPLOGSL_005 OGM10004 - User exit to check whether service material can be used in SMP
EXIT_SAPLOGSL_006 OGM10007 - Modify list of orders (ivbakap) for order due list
EXIT_SAPLOGSL_007 OGM10008 - User exit to add additional fields in order creation
EXIT_SAPLOGSL_008 OGM10010 - User exit-Retrieve ranges of char. values for compex comparison
EXIT_SAPLOGSL_009 OGM10010 - User exit to enable an alternative selection from Ibase
EXIT_SAPLOGSL_010 OGM10014 - Alow additional selec. info to be stored when updt sel. variant
EXIT_SAPLOGSL_011 OGM10014 - Alow additional selec. info to be deleted from stored variant
EXIT_SAPLOGSL_012 Customer processing for slection variant
EXIT_SAPLOGSL_401 Customer processing for order due list

IMPORTING Parameters details for PLM_VARIANT_UPDATE

REPORT -

Data type: RSVAR-REPORT
Optional: No
Call by Reference: No ( called with pass by value option)

VARIANT -

Data type: RSVAR-VARIANT
Optional: No
Call by Reference: No ( called with pass by value option)

DISPLAY -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for PLM_VARIANT_UPDATE

NEW_VERSION -

Data type: VBAP-MATNR
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for PLM_VARIANT_UPDATE 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.

ABAP code using 7.40 inline data declarations to call FM PLM_VARIANT_UPDATE

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