SAP MEREQS_EBAN_INVALIDATE Function Module for NOTRANSL: Banf aus Proxy besorgen
MEREQS_EBAN_INVALIDATE is a standard mereqs eban invalidate 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: Banf aus Proxy besorgen 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 mereqs eban invalidate FM, simply by entering the name MEREQS_EBAN_INVALIDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MEREQS
Program Name: SAPLMEREQS
Main Program: SAPLMEREQS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MEREQS_EBAN_INVALIDATE 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 'MEREQS_EBAN_INVALIDATE'"NOTRANSL: Banf aus Proxy besorgen.
EXPORTING
IM_BANFN = "Purchase Requisition Number
IM_BNFPO = "Item Number of Purchase Requisition
EXCEPTIONS
FAILURE = 1
IMPORTING Parameters details for MEREQS_EBAN_INVALIDATE
IM_BANFN - Purchase Requisition Number
Data type: BANFNOptional: No
Call by Reference: Yes
IM_BNFPO - Item Number of Purchase Requisition
Data type: BNFPOOptional: No
Call by Reference: Yes
EXCEPTIONS details
FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MEREQS_EBAN_INVALIDATE 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_failure | TYPE STRING, " | |||
| lv_im_banfn | TYPE BANFN, " | |||
| lv_im_bnfpo | TYPE BNFPO. " |
|   CALL FUNCTION 'MEREQS_EBAN_INVALIDATE' "NOTRANSL: Banf aus Proxy besorgen |
| EXPORTING | ||
| IM_BANFN | = lv_im_banfn | |
| IM_BNFPO | = lv_im_bnfpo | |
| EXCEPTIONS | ||
| FAILURE = 1 | ||
| . " MEREQS_EBAN_INVALIDATE | ||
ABAP code using 7.40 inline data declarations to call FM MEREQS_EBAN_INVALIDATE
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