Kontakt

Ansicht
Dokumentation

PMMO_RUNTIME_MEMO - Analysis of Runtime and Memory Snapshots

PMMO_RUNTIME_MEMO - Analysis of Runtime and Memory Snapshots

Vendor Master (General Section)   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.
SAP E-Book

PMMO provides various methods for capturing runtime measurements and memory snapshots of the pegging and distribution programs. This also applies for the MM-IM interface that is invoked when a goods movement is posted. This functionality is switched to active using checkpoint groups (transaction SAAB).

SAP provides the following checkpoint groups:

In transaction SAAB, proceed as follows:

  1. Enter the checkpoint group PMMO_RTM.
  2. Choose Activate.
  3. On the Activate Checkpoint Group screen, select the Logradio button under Personal Activation → Assertions (Foreground).
  4. Save the checkpoint group PMMO_RTM.

This has the following impact on the pegging & distribution run:

  • Online execution
The list of captured runtime measurements will be displayed before the report run output is displayed.
  • Background execution
  • The runtime measurements are written to the database tables PMMO_RTM_HEADERand PMMO_RTM_ITEM.

  • The runtime measurements can be displayed or deleted using transaction PMMO_RTM.

Note the following regarding the runtime measurements:

  • To display the runtime measurements in transaction MIGO you need to set the user parameter PMMO_RTM(transaction SU3) to 'X' in addition to activating the checkpoint group.
  • The system will then display the captured measurements in transaction MIGOafter the COMMIT WORKof the transaction is reached.
  • If the goods movement is carried out in the background for instance via a Business Application Programming Interface (BAPI), then the measurements are stored in the database PMMO_RTM_HEADERand PMMO_RTM_ITEM.

In transaction SAAB, proceed as follows:

  1. Enter the checkpoint group PMMO_MEM.
  2. Choose Activate.
  3. On the Activate Checkpoint Group screen, select the Logradio button under Personal Activation → Logpoints.
  4. Save the checkpoint groupPMMO_MEM.

This has the following impact on the pegging/distribution run:

  • The system creates a log entry in the SAAB log (see Log tab).
  • The system creates a full-blown memory snapshot if the memory size condition specified on the selection screen of the pegging/distribution report is reached. The determination if the memory size is beyond a certain threshhold is made at the end of a parallel processing session.

  • The SAAB log shows when and on which server a memory snapshot was created.

  • You can display these snapshots using transaction S_MEMORY_INSPECTOR.

In transaction SAAB, proceed as follows:

  1. Enter the checkpoint group PMMO_MSG.
  2. Choose Activate.
  3. On the Activate Checkpoint Group screen, select the following radio buttons:
  • Logradio button under Personal Activation → Assertions (Foreground)

  • Logradio button under Personal Activation → Logpoints

  1. Save the checkpoint group PMMO_MSG.

This has the following impact on the pegging run:

  • The switch under Assertions (Foreground)adds messages that were issued via the call of class CL_PMMO_MESSAGE_BUFFER- method ADD_MESSAGE_ON_CHKPNT_ACTIVE - to the application log. These messages are ignored if the switch is off.
  • The switch under Logpoints triggers a log entry (displayed in transaction SAABunder the Log tab) for special situations in pegging.

The system creates the following entries:

  • An entry is created when the call to the enqueue server fails for setting the locks on the material/grouping WBS element level.
  • An entry is created before a pegging session is dispatched to the parallel processing framework.
  • An entry is created after a parallel processing session was dispatched.






BAL_S_LOG - Application Log: Log header data   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 5673 Date: 20240523 Time: 190004     sap01-206 ( 83 ms )