SAP EXIT_SAPLMEWP_003 Function Module for Customer Exit to Determine Allowed Catalogs

Search SAP Function Modules

EXIT_SAPLMEWP_003 is a standard exit saplmewp 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 Customer Exit to Determine Allowed Catalogs 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 saplmewp 003 FM, simply by entering the name EXIT_SAPLMEWP_003 into the relevant SAP transaction such as SE37 or SE38.

Function Group: XMEW
Program Name: SAPLXMEW
Main Program:
Appliation area: M
Release date: 24-Apr-1998
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLMEWP_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_SAPLMEWP_003'"Customer Exit to Determine Allowed Catalogs
  EXPORTING
*  MATERIAL_GROUP =  "Material Group
*  PLANT =  "Plant

TABLES
   VALID_CATALOGS =  "Catalogs Determined to Date via Standard Customizing

.

Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
ALE_PO_CREATE BAPI -> IDoc: ALE_PO_CREATE
ALE_PO_GETDETAIL BAPI -> IDoc: ALE_PO_GETDETAIL
BAPI_PO_CREATE Create Purchase Order
BAPI_PO_GETDETAIL Display Purchase Order Details
BAPI_PO_GETITEMS List Purchase Order Items
BAPI_PO_GETITEMSREL List Purchase Orders for Release (Approval): New as of 4.0A
BAPI_PO_GETRELINFO Display Detailed Release (Approval) Information on Purchase Order
BAPI_PO_GET_LIST List Purchase Orders - Only up to 4.0A
BAPI_PROCOPERATION_GETCATALOGS Determine Valid Catalogs as Value Help
BAPI_PROCOPERATION_GETINFO Analysis of Objects to Be Generated in Purchasing
IDOC_INPUT_PORDCR IDoc -> BAPI: IDOC_INPUT_PORDCR
IDOC_INPUT_PORDGD IDoc -> BAPI: IDOC_INPUT_PORDGD
ME_PUR_DOCU_CHANGE NOTRANSL: Ändern mehrerer Felder einer Bestellung via Funktionsbaustein

IMPORTING Parameters details for EXIT_SAPLMEWP_003

MATERIAL_GROUP - Material Group

Data type: BAPIEBAN-MAT_GRP
Optional: Yes
Call by Reference: No ( called with pass by value option)

PLANT - Plant

Data type: BAPIEBAN-PLANT
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for EXIT_SAPLMEWP_003

VALID_CATALOGS - Catalogs Determined to Date via Standard Customizing

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

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

ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLMEWP_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.

Search for further information about these or an SAP related objects