SAP Function Modules

MEX_CHECK_CHANGED_SOURCE SAP Function module







MEX_CHECK_CHANGED_SOURCE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name MEX_CHECK_CHANGED_SOURCE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: MEXF
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM MEX_CHECK_CHANGED_SOURCE - MEX CHECK CHANGED SOURCE





CALL FUNCTION 'MEX_CHECK_CHANGED_SOURCE' "
  EXPORTING
    im_eban =                   " eban          Purchase Requisition
    im_t160d_erfb1 =            " t160d-erfb1   Function Authorizations: Purchase Order
    im_po_lifnr =               " ekko-lifnr    Vendor's Account Number
    im_po_reswk =               " ekko-reswk    Supplying (issuing) plant in case of stock transport order
    im_po_ekorg =               " ekko-ekorg    Purchasing Organization
    im_po_konnr =               " ekpo-konnr    Number of Principal Purchase Agreement
    im_po_ktpnr =               " ekpo-ktpnr    Item Number of Principal Purchase Agreement
    im_po_bsakz =               " ekko-bsakz    Control Indicator for Purchasing Document Type
    .  "  MEX_CHECK_CHANGED_SOURCE

ABAP code example for Function Module MEX_CHECK_CHANGED_SOURCE





The ABAP code below is a full code listing to execute function module MEX_CHECK_CHANGED_SOURCE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).


DATA(ld_im_eban) = 'Check type of data required'.

SELECT single ERFB1
FROM T160D
INTO @DATA(ld_im_t160d_erfb1).


SELECT single LIFNR
FROM EKKO
INTO @DATA(ld_im_po_lifnr).


SELECT single RESWK
FROM EKKO
INTO @DATA(ld_im_po_reswk).


SELECT single EKORG
FROM EKKO
INTO @DATA(ld_im_po_ekorg).


SELECT single KONNR
FROM EKPO
INTO @DATA(ld_im_po_konnr).


SELECT single KTPNR
FROM EKPO
INTO @DATA(ld_im_po_ktpnr).


SELECT single BSAKZ
FROM EKKO
INTO @DATA(ld_im_po_bsakz).
. CALL FUNCTION 'MEX_CHECK_CHANGED_SOURCE' EXPORTING im_eban = ld_im_eban im_t160d_erfb1 = ld_im_t160d_erfb1 im_po_lifnr = ld_im_po_lifnr im_po_reswk = ld_im_po_reswk im_po_ekorg = ld_im_po_ekorg im_po_konnr = ld_im_po_konnr im_po_ktpnr = ld_im_po_ktpnr im_po_bsakz = ld_im_po_bsakz . " MEX_CHECK_CHANGED_SOURCE
IF SY-SUBRC EQ 0. "All OK ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_im_eban  TYPE EBAN ,
ld_im_t160d_erfb1  TYPE T160D-ERFB1 ,
ld_im_po_lifnr  TYPE EKKO-LIFNR ,
ld_im_po_reswk  TYPE EKKO-RESWK ,
ld_im_po_ekorg  TYPE EKKO-EKORG ,
ld_im_po_konnr  TYPE EKPO-KONNR ,
ld_im_po_ktpnr  TYPE EKPO-KTPNR ,
ld_im_po_bsakz  TYPE EKKO-BSAKZ .

ld_im_eban = 'Check type of data required'.

SELECT single ERFB1
FROM T160D
INTO ld_im_t160d_erfb1.


SELECT single LIFNR
FROM EKKO
INTO ld_im_po_lifnr.


SELECT single RESWK
FROM EKKO
INTO ld_im_po_reswk.


SELECT single EKORG
FROM EKKO
INTO ld_im_po_ekorg.


SELECT single KONNR
FROM EKPO
INTO ld_im_po_konnr.


SELECT single KTPNR
FROM EKPO
INTO ld_im_po_ktpnr.


SELECT single BSAKZ
FROM EKKO
INTO ld_im_po_bsakz.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name MEX_CHECK_CHANGED_SOURCE or its description.