SAP EXIT_SAPLMEKO_001 Function Module for Extend Communication Structure KOMK for Pricing
EXIT_SAPLMEKO_001 is a standard exit saplmeko 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Extend Communication Structure KOMK for Pricing 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 saplmeko 001 FM, simply by entering the name EXIT_SAPLMEKO_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XM06
Program Name: SAPLXM06
Main Program: SAPLXM06
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLMEKO_001 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_SAPLMEKO_001'"Extend Communication Structure KOMK for Pricing.
EXPORTING
* I_EKKO = "
* I_WEDATEN = "
* I_EKPO = "
* I_LFA1 = "
* I_T001 = "
* I_LFM1 = "
* I_T001W = "
I_KOMK = "
* I_EINA = "
* I_EINE = "
CHANGING
E_KOMK = "
TABLES
* T_EKPA = "
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ME_CHECK_BMEIN NOTRANSL: Prüfen der Bestellmengeneinheit gegen Matstamm und Infosatz
ME_CHECK_CONDITION_COPY NOTRANSL: Überprüft und handelt das Kopieren von Konditionen im Beleg
ME_CHECK_DIFFERENT_CURRENCY NOTRANSL: Prüft, ob Währungen mit unterschiedlichen Nachkommastellen vorli
ME_CHECK_KSCHL_IN_SCHEME NOTRANSL: Prüft ob eine bestimmte Konditionsart in einem Schema vorkommt
ME_CHECK_KSCHL_KOND_COPY NOTRANSL: Prüft, ob eine Konditionsart aus dem letzten Beleg übernommen we
ME_CHECK_POINTS NOTRANSL: Prüfen, ob eine Einheit als Punkteeinheit zulässig ist
ME_CHECK_PRICE_PRINT NOTRANSL: Überprüft anhand des Kalkulationsschemas, ob das Kz. PRSDR geset
ME_CHECK_PRICING_RESULT NOTRANSL: Prüft das Ergebnis der Preisfindung
ME_CHECK_TAX_INDICATOR_ACCESS NOTRANSL: Prüft, ob Konditionsarten für Steuern mit Zugriffsfolge da sind
ME_COND_SUPPLIER_CHECK NOTRANSL: Prüfen des abweichenden Lieferanten bei Bezugsnebenkosten
ME_CONVERSION_BPRME NOTRANSL: Ermittlung von Konditionsumrechnungsfaktoren im RM
ME_CONVERSION_MEINS NOTRANSL: Ermittlung von Konditionsumrechnungsfaktoren im RM
ME_CONVERSION_MULTIPLY NOTRANSL: Ermittelt aus zwei Umrechnungsfaktoren einen
ME_COPY_TIME_DEP_CONDITIONS NOTRANSL: Kopieren Stammkonditionen aus Vorlagebeleg (Rahmenvertrag/Angebo
ME_COPY_TIME_DEP_COND_HEADER NOTRANSL: Kopieren Stammkonditionen (Kopfkonditionen)
ME_COPY_TIME_DEP_COND_INFOREC NOTRANSL: Kopieren Stammkonditionen aus Infosatz
ME_CREATE_COND_INFOREC NOTRANSL: Erzeugen Infosatzkonditionen aus Stammkonditionen Kontrakt
ME_CREATE_TIME_DEP_COND_EXT NOTRANSL: Erzeugung von Stammkonditionen von externer Quelle
ME_CREATE_TIME_DEP_COND_MAN NOTRANSL: Erzeugen Stammkonditionen aus manueller Eingabe
ME_CREATE_TIME_DEP_COND_RFQ NOTRANSL: Erzeugen Stammkonditionen aus Belegkonditionen eines Angebots
ME_DETERMINE_KOTABNR NOTRANSL: Bestimmen der Konditionstabelle für den Infosatz
ME_FILL_KOMG_IN NOTRANSL: Füllen der Schlüsselfelder für die Konditionen aus dem Infosatz
ME_FILL_KOMG_PO NOTRANSL: Füllen der Keyfelder zum Lesen der Konditionstabellen (Einkaufsb
ME_FILL_KOMK_IN NOTRANSL: Füllen der KOMK für Infosätze
ME_FILL_KOMK_PO NOTRANSL: Füllen der Kommunikationsstrukturen für Konditionen im Einkaufsb
ME_FILL_KOMP_IN NOTRANSL: Füllen der KOMP für Infosätze
ME_FILL_KOMP_PO NOTRANSL: Füllen der KOMP für Einkaufsbelege
ME_GET_CONDITIONS_TO_SEARCH NOTRANSL: Sucht alle Konditionsarten mit Zugriffsfolge
ME_GET_CONDITION_TO_SEARCH NOTRANSL: Sucht die richtige Konditionsart aus dem Kalkulationsschema
ME_GET_CONTRACT_CONDITIONS NOTRANSL: Liest die Kontraktkonditionen von der Datenbank für Druckausgabe
ME_GET_DISCOUNTINKIND_SCHEME NOTRANSL: Sucht das Naturalrabatt-Schema für den Einkauf
ME_GET_INFORECORD_CONDITIONS NOTRANSL: Ermittelt die Infosatzkonditionen in Druckform (nur bis Netto)
ME_GET_INFORECORD_CONDITIONS_1 NOTRANSL: Lesen aller Konditionen zum Infosatz bei Änderung der Bestell-ME
ME_GET_PACKNO_CONDITIONS NOTRANSL: Lesen von Leistungskonditionen
ME_GET_PRICE_CONDITION NOTRANSL: Sucht zu einem Kalkulationsschema die Konditionsart des Preises
ME_GET_PRICING_SCHEME NOTRANSL: Sucht das Kalkulationsschema für den Einkauf
ME_GET_PRICING_SCHEME_TRANS NOTRANSL: Sucht das Kalkulationsschema für den Einkauf für Umlagerung
ME_GET_TIME_DEP_COND NOTRANSL: Lesen der Stammkonditionen zu einem Rahmenvertrag
ME_GET_UNITS_FOR_INFORECORD NOTRANSL: Ermittelt alle möglichen Mengeneinheiten für Infosatzkonditionen
ME_GET_UNIT_FOR_POINTS NOTRANSL: Hilfefunktion für Punkteeinheit
ME_GET_VARCONDS_FOR_INFORECORD NOTRANSL: Ermittelt alle möglichen Variantenschlüssel für Infosatzpflege
ME_HELP_POINTS NOTRANSL: Hilfefunktion für Punkteeinheit
ME_MAINTAIN_PO_DATA_BUFFER Buffering of PO Data for Price Determination
ME_PRECHECK_ACCESS NOTRANSL: Prüfen, ob Daten des Vorlieferanten für Konditionszugriffe benöt
ME_PRINT_CONTRACT_CONDITIONS NOTRANSL: Liefert Stammkonditionen des Kontrakts in ausgabefähiger Form zu
ME_PRINT_PACKNO_CONDITIONS NOTRANSL: Drucken der Leistungskonditionen
ME_RESET_CONTRACT_CONDITIONS NOTRANSL: Zurücksetzen der Daten für Druckausgabe Kontraktkonditionen
IMPORTING Parameters details for EXIT_SAPLMEKO_001
I_EKKO -
Data type: EKKOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_WEDATEN -
Data type: MEPRWEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EKPO -
Data type: EKPOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_LFA1 -
Data type: LFA1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_T001 -
Data type: T001Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LFM1 -
Data type: LFM1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_T001W -
Data type: T001WOptional: Yes
Call by Reference: No ( called with pass by value option)
I_KOMK -
Data type: KOMKOptional: No
Call by Reference: No ( called with pass by value option)
I_EINA -
Data type: EINAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EINE -
Data type: EINEOptional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for EXIT_SAPLMEKO_001
E_KOMK -
Data type: KOMKOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLMEKO_001
T_EKPA -
Data type: EKPAOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLMEKO_001 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_e_komk | TYPE KOMK, " | |||
| lv_i_ekko | TYPE EKKO, " | |||
| lt_t_ekpa | TYPE STANDARD TABLE OF EKPA, " | |||
| lv_i_wedaten | TYPE MEPRWE, " | |||
| lv_i_ekpo | TYPE EKPO, " | |||
| lv_i_lfa1 | TYPE LFA1, " | |||
| lv_i_t001 | TYPE T001, " | |||
| lv_i_lfm1 | TYPE LFM1, " | |||
| lv_i_t001w | TYPE T001W, " | |||
| lv_i_komk | TYPE KOMK, " | |||
| lv_i_eina | TYPE EINA, " | |||
| lv_i_eine | TYPE EINE. " |
|   CALL FUNCTION 'EXIT_SAPLMEKO_001' "Extend Communication Structure KOMK for Pricing |
| EXPORTING | ||
| I_EKKO | = lv_i_ekko | |
| I_WEDATEN | = lv_i_wedaten | |
| I_EKPO | = lv_i_ekpo | |
| I_LFA1 | = lv_i_lfa1 | |
| I_T001 | = lv_i_t001 | |
| I_LFM1 | = lv_i_lfm1 | |
| I_T001W | = lv_i_t001w | |
| I_KOMK | = lv_i_komk | |
| I_EINA | = lv_i_eina | |
| I_EINE | = lv_i_eine | |
| CHANGING | ||
| E_KOMK | = lv_e_komk | |
| TABLES | ||
| T_EKPA | = lt_t_ekpa | |
| . " EXIT_SAPLMEKO_001 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLMEKO_001
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