Scribd
Upload
137 views3 pages

SAP BAPIS Replacement MM

The document discusses obsolete transactions, IDocs, BAPIs and archiving reports related to purchase orders and purchase requisitions in SAP. It provides the replacements for the outdated transactions and IDocs/BAPIs as well as the new archiving reports that should be used instead of the old ones.

Uploaded by

Rodrigo Funes Gez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
137 views3 pages

SAP BAPIS Replacement MM

The document discusses obsolete transactions, IDocs, BAPIs and archiving reports related to purchase orders and purchase requisitions in SAP. It provides the replacements for the outdated transactions and IDocs/BAPIs as well as the new archiving reports that should be used instead of the old ones.

Uploaded by

Rodrigo Funes Gez
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Symptom

You are facing an issue with the "old" application transactions, IDocs or BAPIs
for maintaining Purchase Orders or Purchase Requisitions: ME21, ME22,
ME23, ME51, ME52, ME53 et al.
(For the more detailed list of out-dated transactions and BAPIs see section
"Solution" below.)

You are facing an issue with the "old" archiving reports in MM


Purchasing RM06*47 or RM06*30.

Other Terms

MEPO, SAPMM06E, BUS2012, PurchaseOrder, CreateFromData, GetList,


GetDetail, PurchaseOrder.CreateFromData, BUS2012.CREATEFROMDATA,
BUS2012.GETLIST, BUS2012.GETDETAIL,
Single-screen transaction, Enjoy transaction, 'old' transaction,
Enjoy, BAPI_PR_GETDETAIL, PurchaseRequisition, CreateFromData1,
Change1, BUS2105, BAnf, maintenance, restrictive, restriction, service,
servicing, repair, correction

Archiving, RM06E*47, RM06B*47, RM06I*47, RM06*30.

Reason and Prerequisites

Starting with release SAP R/3 4.6C the "old" transactions and BAPIs related to
business objects Purchase Order and Purchase Requisition were replaced by
new single-screen (Enjoy-)transactions, new IDocs and new BAPIs. All of these
new transactions, IDocs and BAPIs are available with SAP R/3 Enterprise
Release 4.70 and in subsequent releases.

The extended maintenance offered by SAP for several older releases, including
SAP R/3 4.6C, SAP R/3 Enterprise Release 4.70 and SAP ERP 2004, ended on
March 31, 2013 (see SAP Service Marketplace).

Therefore, from April 2013 onwards, all functionality that is available


through the "new" transactions, IDocs and BAPIs is NO longer maintained
in the "old" transactions, IDocs and BAPIs (see list below).

Solution

Business Value

The mentioned obsolete transactions have been replaced by more user-friendly


new transactions covering the features of the replaced transactions.

The out-dated transactions were replaced by the following single-screen (Enjoy)


transactions that deliver improved usability and enhanced functionality:
ME21, ME22, ME23 -> ME21N, ME22N, ME23N
ME24 -> ME21N, ME22N
ME25 -> ME21N (Holding the PO)
ME27 -> ME21N
ME28 -> ME29N
ME51, ME52, ME53 -> ME51N, ME52N, ME53N
ME54 -> ME54N
ME59 -> ME59N

The corresponding IDoc / BAPI replacements are:


"old" FMs of function group MEWP -> will be replaced by "new" FMs of function
group 2012, e.g.:
IDOC_INPUT_PORDCR -> IDOC_INPUT_PORDCR1, IDOC_INPUT_PORDCH
BAPI_PO_CREATE -> BAPI_PO_CREATE1, BAPI_PO_CHANGE
BAPI_PO_GETDETAIL -> BAPI_PO_GETDETAIL1

"old" FMs of function group MEWQ -> will be replaced by "new" FMs of function
group 2105, e.g.:
IDOC_INPUT_PREQCR -> IDOC_INPUT_PREQCR1
BAPI_REQUISITION_CREATE, BAPI_REQUISITION_CHANGE ->
BAPI_PR_CREATE, BAPI_PR_CHANGE
BAPI_REQUISITION_GETDETAIL -> BAPI_PR_GETDETAIL

SAP STRONGLY recommends to use these new transactions, IDocs


and BAPIs to process Purchase Order and Purchase Requisition
documents.

ALL developments that are done for the business object Purchase Order and
Purchase Requisition are based on these transactions, IDocs and BAPIs.
Future enhancements that are related to Purchase Order or Purchase
Requisiton will only be done for the "new" transactions, IDocs and BAPIs.

Beyond improved usability, there are a lot of new functions which are only
available with the new transactions. The following lists the most important
enhancements:
- Single-screen transaction - all info at a glance
- Document overview with definable display variant
- Put incomplete purchase orders "on hold"
- Adopting items from reference documents by mouse-click
- Simplified navigation - master data easily accessible
- Use of own data fields
- Multiple account assignment
- New release strategy
- External sourcing
- Central Contract Management
- Down payment
- Outsourced Manufacturing
- Connection availability to SOA, SUS/SRM Integration
- Availability of BAdIs
This list will be constantly updated.

Archiving reports for archiving MM_EKKO, MM_EBAN or MM_EINA:

Since release ECC 6.0 EhP4 (SAP_APPL_604) the latest archiving reports


have been provided R/3 standard systems.

The reports are named RM06E*70, RM06B*70 and RM06I*70.

SAP STRONGLY recommends to use the new archiving reports as of


release ECC 6.0 EhP4 (SAP_APPL 604):

Archiving Object MM_EKKO


RM06EV70 -> instead of report RM06EV47
RM06EW70 -> instead of report RM06EW47
RM06ED70 -> instead of report RM06ED47

Archiving Object MM_EBAN


RM06BV70 -> instead of report RM06BV47
RM06BW70 -> instead of report RM06BW47
RM06BD70 -> instead of report RM06BD47

Archiving Object MM_EINA


RM06IW70 -> instead of report RM06IW47
RM06ID70 -> instead of report RM06ID47

The new archiving reports RM06**70 have to be used at least as of


release ECC 6.0 EhP7 (SAP_APPL_617).
With this release all other archiving reports (like RM06E*47, RM06B*47
and RM06I*47) are marked as obsolete and are not supported anymore !

Older archiving reports like RM06E*30, RM06B*30 and RM06I*30 are also out


of maintenance since ECC 6.0 (SAP_APPL_600).

The reports for reading archived data, reports RM06ER30, RM06BR30


and RM06IR30 are not effected by this change (SARA => READ Program).
They can still be used but it is recommended to use the AIS (Archive
Information System) with transaction SARI to display archived MM Purchasing
documents.

You might also like