SAP EXIT_SAPLM60P_003 Function Module for Creation of Superior Instance









EXIT_SAPLM60P_003 is a standard exit saplm60p 003 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Creation of Superior Instance 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 exit saplm60p 003 FM, simply by entering the name EXIT_SAPLM60P_003 into the relevant SAP transaction such as SE37 or SE38.

Function Group: X60P
Program Name: SAPLX60P
Main Program:
Appliation area:
Release date: 01-Jan-1970
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EXIT_SAPLM60P_003 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 'EXIT_SAPLM60P_003'"Creation of Superior Instance
EXPORTING
* I_MATERIAL = "Material Number
* I_DATE = "Date and Time, Current (Application Server) Date
* I_KLART = "Class Type
I_NEW_INSTANCE = "

IMPORTING
E_PARENT_INSTANCE = "

CHANGING
CS_FUZZY_DDB = "
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
M60P_CONFIGURE_DEMAND NOTRANSL: Konfiguration von Planprimärbedarfen
M60P_DELETE_SHARED_BUFFER_LPDX NOTRANSL: Selektives Löschen des Laufzeitobjektes LPDX
REQUIREMENTS_CALC_PROB NOTRANSL: Alternativer Baustein Wahrscheinlichkeitsberechnung
REQUIREMENTS_COPY_CONFIG NOTRANSL: Kopiere eine CUOBJ
REQUIREMENTS_DISPLAY_CHAR NOTRANSL: Anzeige von Merkmalswerten im Primärbedarf/Einkauf
REQUIREMENTS_EXPLAIN_PROB NOTRANSL: Alternativer Baustein Wahrscheinlichkeitsberechnung
REQUIREMENTS_GET_COMBINATION NOTRANSL: Merkmalskombinationen aus dem Profil zu einer Kundenauftragkonfi
REQUIREMENTS_INTERN_LIST_PROC NOTRANSL: Listabwicklung ohne DB Zugriffe
REQUIREMENTS_LIST_CHAR_VAL_PLN NOTRANSL: Liste: Geplante Einsatzwahrscheinlichkeiten
REQUIREMENTS_MAINTAIN_CONFIG NOTRANSL: Pflege der Einsatzwahrscheinlichkeiten in der Programmplanung
REQUIREMENTS_MAINTAIN_CONF_ALL NOTRANSL: Pflege aller Stützpunkte der Merkmalsvorplanung
REQUIREMENTS_MAINTAIN_RELEVANC NOTRANSL: Pflege des Vorplanungsprofils in der Programmplanung
REQUIREMENTS_MAINTAIN_REL_TMP NOTRANSL: Pflege der Vorplanungsrelevanz temporaer
REQUIREMENTS_MAINT_CONFIG_BACK NOTRANSL: Pflege der EWAHR im Hintergrund
REQUIREMENTS_MAINT_RELE_BACK NOTRANSL: Pflege des Vorplanungsprofils im Hintergrund
REQUIREMENTS_VT_CALC_PROB NOTRANSL: Wahrscheinlichkeit einer planungsrelevanten Merkmalskombination

IMPORTING Parameters details for EXIT_SAPLM60P_003

I_MATERIAL - Material Number

Data type: MARA-MATNR
Optional: Yes
Call by Reference: Yes

I_DATE - Date and Time, Current (Application Server) Date

Data type: SY-DATUM
Optional: Yes
Call by Reference: Yes

I_KLART - Class Type

Data type: KLAH-KLART
Optional: Yes
Call by Reference: Yes

I_NEW_INSTANCE -

Data type:
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for EXIT_SAPLM60P_003

E_PARENT_INSTANCE -

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

CHANGING Parameters details for EXIT_SAPLM60P_003

CS_FUZZY_DDB -

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

Copy and paste ABAP code example for EXIT_SAPLM60P_003 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_i_material  TYPE MARA-MATNR, "   
lv_cs_fuzzy_ddb  TYPE CUFET_FUZZY_DDB, "   
lv_e_parent_instance  TYPE CUFET_INSTANCE, "   
lv_i_date  TYPE SY-DATUM, "   
lv_i_klart  TYPE KLAH-KLART, "   
lv_i_new_instance  TYPE KLAH. "   

  CALL FUNCTION 'EXIT_SAPLM60P_003'  "Creation of Superior Instance
    EXPORTING
         I_MATERIAL = lv_i_material
         I_DATE = lv_i_date
         I_KLART = lv_i_klart
         I_NEW_INSTANCE = lv_i_new_instance
    IMPORTING
         E_PARENT_INSTANCE = lv_e_parent_instance
    CHANGING
         CS_FUZZY_DDB = lv_cs_fuzzy_ddb
. " EXIT_SAPLM60P_003




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLM60P_003

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 MATNR FROM MARA INTO @DATA(ld_i_material).
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_date).
 
"SELECT single KLART FROM KLAH INTO @DATA(ld_i_klart).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!