SAP ME_REQ_TRIGGER_EVENT Function Module for NOTRANSL: Trigger external sourcing

Search SAP Function Modules

ME_REQ_TRIGGER_EVENT is a standard me req trigger event 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: Trigger external sourcing 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 me req trigger event FM, simply by entering the name ME_REQ_TRIGGER_EVENT into the relevant SAP transaction such as SE37 or SE38.

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

Function ME_REQ_TRIGGER_EVENT 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 'ME_REQ_TRIGGER_EVENT'"NOTRANSL: Trigger external sourcing
  EXPORTING
   IV_BNFPN =  "Purchase Requisition Number
   IV_ACTIVITY =  "Transaction type
*  IV_EVENT =  "Event
*  IT_EBAN_KEY =  "Table Type MEREQ_S_EBANKEY
*  IT_BIDDER =  "Bidder Table
*  IS_SUBMISSION_TST =  "
*  IV_RFX_TYPE =  "Purchasing Document Type
*  IT_ESLL_KEY =  "Service Table
*  IT_ESUH_KEY =  "

.

IMPORTING Parameters details for ME_REQ_TRIGGER_EVENT

IV_BNFPN - Purchase Requisition Number

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

IV_ACTIVITY - Transaction type

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

IV_EVENT - Event

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

IT_EBAN_KEY - Table Type MEREQ_S_EBANKEY

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

IT_BIDDER - Bidder Table

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

IS_SUBMISSION_TST -

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

IV_RFX_TYPE - Purchasing Document Type

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

IT_ESLL_KEY - Service Table

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

IT_ESUH_KEY -

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

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

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