SAP OM_IPPE_POSVAR_CREATE Function Module for NOTRANSL: Positionsvariante hinzufügen

Search SAP Function Modules

OM_IPPE_POSVAR_CREATE is a standard om ippe posvar create 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: Positionsvariante hinzufügen 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 om ippe posvar create FM, simply by entering the name OM_IPPE_POSVAR_CREATE into the relevant SAP transaction such as SE37 or SE38.

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

Function OM_IPPE_POSVAR_CREATE 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 'OM_IPPE_POSVAR_CREATE'"NOTRANSL: Positionsvariante hinzufügen
  EXPORTING
   PNGUID =  "Internal Number of iPPE Node
   PVGUID =  "Internal Number of the PVS Variant
   APPLOBJ_TYPE =  "Application Object Type for iPPE
   GUID =  "Internal Identification for PVS Objects
   OTYPE =  "iPPE Object Type
   AENNR =  "Change Number in iPPE

EXCEPTIONS
   PNGUID_NOT_LOADED = 1 

.

IMPORTING Parameters details for OM_IPPE_POSVAR_CREATE

PNGUID - Internal Number of iPPE Node

Data type: PVS_PNGUID
Optional: No
Call by Reference: Yes

PVGUID - Internal Number of the PVS Variant

Data type: PVS_PVGUID
Optional: No
Call by Reference: Yes

APPLOBJ_TYPE - Application Object Type for iPPE

Data type: PVS_APPLOBJ_TYPE
Optional: No
Call by Reference: Yes

GUID - Internal Identification for PVS Objects

Data type: PVS_GUID
Optional: No
Call by Reference: Yes

OTYPE - iPPE Object Type

Data type: PVS_OTYPE
Optional: No
Call by Reference: Yes

AENNR - Change Number in iPPE

Data type: PVSCSQ-AENNR
Optional: No
Call by Reference: Yes

EXCEPTIONS details

PNGUID_NOT_LOADED - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

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

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