SAP MEDI_REQ_CHECK_NEW_VERSION Function Module for NOTRANSL: Prüfen auf versionsrelevante Änderung

Search SAP Function Modules

MEDI_REQ_CHECK_NEW_VERSION is a standard medi req check new version 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: Prüfen auf versionsrelevante Änderung 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 medi req check new version FM, simply by entering the name MEDI_REQ_CHECK_NEW_VERSION into the relevant SAP transaction such as SE37 or SE38.

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

Function MEDI_REQ_CHECK_NEW_VERSION 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 'MEDI_REQ_CHECK_NEW_VERSION'"NOTRANSL: Prüfen auf versionsrelevante Änderung
  EXPORTING
   IM_EBAN =  "
   IM_EBAN_OLD =  "Purchase Requisition Old
   IM_EBKN =  "
   IM_EBKN_OLD =  "
*  IM_CHANGED_TEXTS =  "Table Type: Change Documents for Texts
*  IM_SERVICE_CHANGED = 'N' "
*  IM_DOCUMENTS_CHANGED = 'N' "

 IMPORTING
   EX_NEW_VERSION =  "New Version

.

IMPORTING Parameters details for MEDI_REQ_CHECK_NEW_VERSION

IM_EBAN -

Data type: EBAN
Optional: No
Call by Reference: Yes

IM_EBAN_OLD - Purchase Requisition Old

Data type: EBAN
Optional: No
Call by Reference: Yes

IM_EBKN -

Data type: MEREQ_T_EBKN
Optional: No
Call by Reference: Yes

IM_EBKN_OLD -

Data type: MEREQ_T_EBKN
Optional: No
Call by Reference: Yes

IM_CHANGED_TEXTS - Table Type: Change Documents for Texts

Data type: MEREQ_T_CDTXT
Optional: Yes
Call by Reference: Yes

IM_SERVICE_CHANGED -

Data type: CHAR1
Default: 'N'
Optional: Yes
Call by Reference: Yes

IM_DOCUMENTS_CHANGED -

Data type: CHAR1
Default: 'N'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for MEDI_REQ_CHECK_NEW_VERSION

EX_NEW_VERSION - New Version

Data type: MMPUR_BOOL
Optional: No
Call by Reference: Yes

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

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