Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
MM-PUR-GF (Application Component) Basic Functions⤷
MMPUR_HDB (Package) In-Memory Optimizations for MM-PUR
IMG Activity
| ID | MMPUR_DBSYSOPT_POH | BAdI: Purchase Order History for List Reports - Optimization |
| Transaction Code | S_EX1_23000011 | (empty) |
| Created on | 20120817 | |
| Customizing Attributes | MMPUR_DBSYSOPT_POH | BAdI: Purchase Order History for List Reports - Optimization |
| Customizing Activity | MMPUR_DBSYSOPT_POH | BAdI: Purchase Order History for List Reports - Optimization |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | MMPUR_DBSYSOPT_POH |
Use
This Business Add-In (BAdI) is used in the Purchasing component (MM-PUR) and in the Inventory Management component (MM-IM). You can use this BAdI to apply new database technologies for improving the performance in transactions which evaluate the purchase order (PO) history, namely ME2K, ME2L, ME2M, ME2N, and MB5S.
The following two methods are available:
- PO_HISTORY_READ
You can use this method to read purchase order history data for purchase order items according to specific selection criteria. The method is used by the optimized transactions ME2K, ME2L, ME2M, and ME2N.
- GET_PO_HISTORY_VALUES
This method is used by the new function module ME_READ_HISTORY_DAO to retrieve aggregated PO history values. If you use the default implementation of this BAdI, the optimization is not supported if one of the following conditions applies:
- if the PO history data contains delivery costs
- if the multiple account assignment switch is active
The optimization is supported for all PO item types except services.
If the optimization is supported, function module ME_READ_HISTORY no longer needs to be called. The method is used by the optimized transactions MB5S, ME2K, ME2L, ME2M, and ME2N.
Performance improvements from using new database techniques are expected to arise from:
- Generally faster data selection by state-of-the-art databases
- Aggregation of purchase order history data on database level instead of ABAP server level
- Reduced volume of data transferred from the database to the ABAP server
Requirements
The BAdI implementation is only considered by the system if the business function Optimization PO History (LOG_MM_OPT_POH) is active.
Standard settings
For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).
BAdI Definition
- MMPUR_DBSYSOPT_POH
The filter DBSYS_TYPE has been defined for this BAdI. When an instance of the BAdI is created, this filter is applied with the value of the static attribute DBSYS_TYPE in class CL_DB_SYS.
- SAP Implementations
The SAP BAdI implementation ES_MM_PUR_POH_DBSYS_OPT reads and aggregates data. This BAdI implementation is assigned to filter value 'HDB'.
More Information
BAdI method documentation:
For information about implementing such an optimization BAdI, see Optimization BAdIs.
Example
Business Attributes
| ASAP Roadmap ID | 207 | Establish Reporting |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | MMPUR_DBSYSOPT_POH | 0 | E4A0000001 | Optimization in Purchasing |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20120817 |
| SAP Release Created in | 616 |
