SAP ABAP IMG Activity PPH_MDPSX_DBSYS_OPT (Optimization for Reading Supply and Demand)
Hierarchy
☛ SAP_APPL (Software Component) Logistics and Accounting
   ⤷ PP-MRP (Application Component) Material Requirements Planning
     ⤷ PPH_GENERAL (Package) PP on HANA: General Functions
IMG Activity
ID PPH_MDPSX_DBSYS_OPT Optimization for Reading Supply and Demand  
Transaction Code S_EX1_23000047   (empty) 
Created on 20120919    
Customizing Attributes PPH_MDPSX_DBSYS_OPT   Optimization for Reading Supply and Demand 
Customizing Activity PPH_MDPSX_DBSYS_OPT   Optimization for Reading Supply and Demand 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name PPH_MDPSX_DBSYS_OPT    

Use

This Business Add-In (BAdI) is used in the Material Requirements Planning (PP-MRP) component. You can use it to apply new database techniques for improving the performance in many evaluation transactions such as Display Stock/Requirements Situation (MD04), Current Material Overview (MD07) and in MRP planning transactions such as MRP Run (MD01), MRP - Single-Item, Multi-Level (MD02).

The high-level idea behind the BAdI and its methods is to pre-read the supply and demand situation for many materials and access the pre-read data in the subsequent program logic. Where and how the methods are called in the coding is predefined to ensure the smooth running of the transactions using the BAdI. Within the the methods described in detail at a later point, only the pre-read of the supply and demand data, the read access of this data along with the preparation of the data has to be implemented.

BAdI Methods

The BAdI methods available are divided into two groups:

Pre-read methods and data access methods

  • SELECT_MRP_CONTROLLER_AGG

    This BAdI method is used to select the supply and demand elements from the database for all materials belonging to an MRP controller in a plant (aggregated).

  • SELECT_MATNR_WERKS_BERID_AGG

    This BAdI method is used to select the supply and demand elements from the database for a given set of material/plant/MRP area combinations (aggregated). The IV_BUFFER is either set to 'X' or to 'P' that allows the implementation to control the buffer logic as required.

  • SELECT_MATNR_WERKS_BERID_NOAGG

    This BAdI method is used to select the supply and demand elements from the database for a given set of material/plant/MRP area combinations (non-aggregated). The IV_BUFFER is either set to 'X' or to 'P' that allows the implementation to control the buffer logic as required.

  • GET_MAT_WERKS_AGG

    This BAdI method is used to retrieve data from the buffer for a given material/plant combination. It expects at least the ET_MDPSX parameter to be filled with the supply and demand elements. ET_MDPSX is used in evaluation/display transactions that call the function AUFBAUEN_MDPSX_ANZEIGEN. If called for planning purposes using function AUFBAUEN_MDPSX_DISPOSITION, parameters ET_MDPSO, ET_MDPSL and ET_MDLPY also have to be supplied.

  • GET_MAT_WERKS_NONAGG

    This BAdI method is used to retrieve data from the buffer for a given material/plant combination (non-aggregated).

The methods in this first group read the supply and demand elements from the database and store the data in an implementation-specific buffer. These methods only have input parameters defining the selection criteria and a buffer parameter defining how to buffer the data.

Retrieve methods

  • AUFBAUEN_MDPSX_ANZEIGEN (evaluation)
  • AUFBAUEN_MDPSX_DISPOSITION (planning)

The retrieve methods in this second group are called in exactly two standard ERP function modules which are responsible for populating internal tables used in evaluation and planning transactions.

The methods retrieve the data from the buffer or (depending on the implementation) also from the database and prepare it so that it matches the format of the output tables as expected by the calling programs. The input parameters of these methods define selection criteria (material and plant) and pass on the context information of the calling program. This enables the implementation to prepare the data accordingly.

The key challenge when implementing the BAdI methods is to understand the logic of the two standard ERP function modules with regard to reading the data from the database and preparing the data.

There are methods for selecting and retrieving data in an aggregated mode (AGG) and in a non-aggregated mode (NO(N)AGG). This makes sense if you want to aggregate customer requirements (DB table VBBE) and reservations (DB table RESB) on a daily basis for performance reasons on a database - provided that the detailed information is not needed. The implementation of the methods may also read non-aggregated. This has no effect on the features of the optimized transactions.

Note

This BAdI is intended exclusively for database providers. It allows them to optimize functions that have already been optimized by SAP for SAP HANA for their database without modifications.

Requirements

The BadI implementation is only considered by the system if the business function Read Optimization for MDPSX (LOG_PPH_MDPSX_READ) 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).

  • Enhancement Spot

    Database-Specific Optimization (PPH_DBSYS_OPT)

  • BAdI Definition

    Optimization for Reading Supply and Demand (PPH_MDPSX_DBSYS_OPT)

  • SAP Implementation

    The SAP BAdI implementation PPH_MDPSX_DBSYS_OPT reads and aggregates supply and demand data. This BAdI implementation is assigned to filter value #HDB#.

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 3   Nonrequired 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 PPH_MDPSX_DBSYS_OPT 0 HLA0009520 Production Planning and Control 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20120919 
SAP Release Created in 616