SAP EXIT_SAPLMEWP_002 Function Module for Customer Exit: Creation of Purchase Order via BAPI_PO_CREATE
EXIT_SAPLMEWP_002 is a standard exit saplmewp 002 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: Creation of Purchase Order via BAPI_PO_CREATE 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 002 FM, simply by entering the name EXIT_SAPLMEWP_002 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XMEW
Program Name: SAPLXMEW
Main Program: SAPLXMEW
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function EXIT_SAPLMEWP_002 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_002'"Customer Exit: Creation of Purchase Order via BAPI_PO_CREATE.
EXPORTING
PO_HEADER = "Purchase Order Header Data
PO_ADDRESS = "Address Data
PO_HEADER_ADD_DATA = "
IMPORTING
ABORT = "Abort Transaction Flag ('X'=ABORT)
PO_HEADER_CHANGED = "Create Transfer Structure: PO Header
PO_ADDRESS_CHANGED = "BAPI Transfer Structure for Addresses
PO_HEADER_ADD_CHANGED = "
TABLES
PO_ITEMS = "Purchase Order Item Data
* PO_SERVICES_TEXT = "
* PO_RETURN = "Return parameter
* EXTENSIONIN = "Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
* PO_ADDRDELIVERY = "Purchase Order Item: Address for Inward Delivery
* PO_ITEM_ADD_DATA = "
PO_ITEM_SCHEDULES = "Schedule Lines for Item
PO_ITEM_ACCOUNT_ASSIGNMENT = "Item Account Assignment Data
PO_ITEM_TEXT = "Texts for Item
* PO_LIMITS = "
* PO_CONTRACT_LIMITS = "
* PO_SERVICES = "
* PO_SRV_ACCASS_VALUES = "
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_002
PO_HEADER - Purchase Order Header Data
Data type: BAPIEKKOCOptional: No
Call by Reference: No ( called with pass by value option)
PO_ADDRESS - Address Data
Data type: BAPIADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
PO_HEADER_ADD_DATA -
Data type: BAPIEKKOAOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for EXIT_SAPLMEWP_002
ABORT - Abort Transaction Flag ('X'=ABORT)
Data type: EKPO-LOEKZOptional: No
Call by Reference: No ( called with pass by value option)
PO_HEADER_CHANGED - Create Transfer Structure: PO Header
Data type: BAPIEKKOCOptional: No
Call by Reference: No ( called with pass by value option)
PO_ADDRESS_CHANGED - BAPI Transfer Structure for Addresses
Data type: BAPIADDRESSOptional: No
Call by Reference: No ( called with pass by value option)
PO_HEADER_ADD_CHANGED -
Data type: BAPIEKKOAOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for EXIT_SAPLMEWP_002
PO_ITEMS - Purchase Order Item Data
Data type: BAPIEKPOCOptional: No
Call by Reference: No ( called with pass by value option)
PO_SERVICES_TEXT -
Data type: BAPIESLLTXOptional: Yes
Call by Reference: No ( called with pass by value option)
PO_RETURN - Return parameter
Data type: BAPIRETURNOptional: Yes
Call by Reference: Yes
EXTENSIONIN - Reference Structure for BAPI Parameters EXTENSIONIN/EXTENSIONOUT
Data type: BAPIPAREXOptional: Yes
Call by Reference: Yes
PO_ADDRDELIVERY - Purchase Order Item: Address for Inward Delivery
Data type: BAPIMEPOADDRDELIVERYOptional: Yes
Call by Reference: Yes
PO_ITEM_ADD_DATA -
Data type: BAPIEKPOAOptional: Yes
Call by Reference: Yes
PO_ITEM_SCHEDULES - Schedule Lines for Item
Data type: BAPIEKETOptional: No
Call by Reference: No ( called with pass by value option)
PO_ITEM_ACCOUNT_ASSIGNMENT - Item Account Assignment Data
Data type: BAPIEKKNOptional: No
Call by Reference: No ( called with pass by value option)
PO_ITEM_TEXT - Texts for Item
Data type: BAPIEKPOTXOptional: No
Call by Reference: No ( called with pass by value option)
PO_LIMITS -
Data type: BAPIESUHCOptional: Yes
Call by Reference: No ( called with pass by value option)
PO_CONTRACT_LIMITS -
Data type: BAPIESUCCOptional: Yes
Call by Reference: No ( called with pass by value option)
PO_SERVICES -
Data type: BAPIESLLCOptional: Yes
Call by Reference: No ( called with pass by value option)
PO_SRV_ACCASS_VALUES -
Data type: BAPIESKLCOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EXIT_SAPLMEWP_002 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_abort | TYPE EKPO-LOEKZ, " | |||
lt_po_items | TYPE STANDARD TABLE OF BAPIEKPOC, " | |||
lv_po_header | TYPE BAPIEKKOC, " | |||
lt_po_services_text | TYPE STANDARD TABLE OF BAPIESLLTX, " | |||
lt_po_return | TYPE STANDARD TABLE OF BAPIRETURN, " | |||
lt_extensionin | TYPE STANDARD TABLE OF BAPIPAREX, " | |||
lt_po_addrdelivery | TYPE STANDARD TABLE OF BAPIMEPOADDRDELIVERY, " | |||
lv_po_address | TYPE BAPIADDRESS, " | |||
lt_po_item_add_data | TYPE STANDARD TABLE OF BAPIEKPOA, " | |||
lv_po_header_changed | TYPE BAPIEKKOC, " | |||
lt_po_item_schedules | TYPE STANDARD TABLE OF BAPIEKET, " | |||
lv_po_address_changed | TYPE BAPIADDRESS, " | |||
lv_po_header_add_data | TYPE BAPIEKKOA, " | |||
lv_po_header_add_changed | TYPE BAPIEKKOA, " | |||
lt_po_item_account_assignment | TYPE STANDARD TABLE OF BAPIEKKN, " | |||
lt_po_item_text | TYPE STANDARD TABLE OF BAPIEKPOTX, " | |||
lt_po_limits | TYPE STANDARD TABLE OF BAPIESUHC, " | |||
lt_po_contract_limits | TYPE STANDARD TABLE OF BAPIESUCC, " | |||
lt_po_services | TYPE STANDARD TABLE OF BAPIESLLC, " | |||
lt_po_srv_accass_values | TYPE STANDARD TABLE OF BAPIESKLC. " |
  CALL FUNCTION 'EXIT_SAPLMEWP_002' "Customer Exit: Creation of Purchase Order via BAPI_PO_CREATE |
EXPORTING | ||
PO_HEADER | = lv_po_header | |
PO_ADDRESS | = lv_po_address | |
PO_HEADER_ADD_DATA | = lv_po_header_add_data | |
IMPORTING | ||
ABORT | = lv_abort | |
PO_HEADER_CHANGED | = lv_po_header_changed | |
PO_ADDRESS_CHANGED | = lv_po_address_changed | |
PO_HEADER_ADD_CHANGED | = lv_po_header_add_changed | |
TABLES | ||
PO_ITEMS | = lt_po_items | |
PO_SERVICES_TEXT | = lt_po_services_text | |
PO_RETURN | = lt_po_return | |
EXTENSIONIN | = lt_extensionin | |
PO_ADDRDELIVERY | = lt_po_addrdelivery | |
PO_ITEM_ADD_DATA | = lt_po_item_add_data | |
PO_ITEM_SCHEDULES | = lt_po_item_schedules | |
PO_ITEM_ACCOUNT_ASSIGNMENT | = lt_po_item_account_assignment | |
PO_ITEM_TEXT | = lt_po_item_text | |
PO_LIMITS | = lt_po_limits | |
PO_CONTRACT_LIMITS | = lt_po_contract_limits | |
PO_SERVICES | = lt_po_services | |
PO_SRV_ACCASS_VALUES | = lt_po_srv_accass_values | |
. " EXIT_SAPLMEWP_002 |
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLMEWP_002
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 LOEKZ FROM EKPO INTO @DATA(ld_abort). | ||||
Search for further information about these or an SAP related objects