Show TOC

Function documentationProfiling

 

Profiling is a diagnostic tool within Queue Monitor that captures timing characteristics for the steps involved in processing a SAPMEINT message and stores the timing records in the SAPMEINT_PROFILE database table. This data provides information about total processing times, step times and timing trends (see Queue Monitor).

Whenever you experience a performance issue in SAP ME ERP integration, you can use this function to diagnose where the problem is.

Caution Caution

There is a moderate loss of performance with Profiling. Therefore, enable this function only when you need to analyze such an issue.

End of the caution.

Prerequisites

  • In SAP MII, on the Global Configuration screen under Start of the navigation path SAP ME ERP Integration Next navigation step SAPMEINT Configuration End of the navigation path, you have set the SAPMEINT_IS_PROFILING_ENABLED property to TRUE or a specific step ID (see SAPMEINT Processing Steps and Step IDs and Global Configuration).

  • In SAP MII, on the Schedule Editor screen under Start of the navigation path SAP ME ERP Integration Next navigation step MII Configuration End of the navigation path, you have stopped the QueueMessageCleaner job.

    Note Note

    To preserve database space, when you are finished using Profiling, return the cleaner to its original state.

    Once a message is removed, it is no longer available for Profiling.

    End of the note.

Example

Your system transfers 1000 BOMs with 10000 components each from SAP ERP to SAP ME per day.

During the week of August 16, you notice transfers are processing too slowly. You turn off the cleaning dispatcher, turn on Profiling, and wait until an adequate sampling of messages is processed. This amount of time depends on your rate of transfer. In this case, two hours or less may be sufficient.

Filtering for the Document Type BOMMAT03 and the week of August 16 in Queue Monitor, you can view the Profiling Trends for total processing, workflow processing, or a specific step within the workflow to pinpoint where the slowdown is occurring.

For any selected BOMMAT03 row in Queue Monitor, you can also view the milliseconds consumed for each step in the workflow, and pie charts displaying these numbers.

In addition, in SAP MII, on the Workflow Configuration screen under Start of the navigation path SAP ME ERP Integration Next navigation step SAPMEINT Configuration End of the navigation path you can determine which transaction or XSLT is consuming the time. From the milliseconds consumed on that step, you may be able to determine if there is a network, ERP, or code problem.

Technology consultants can then work to improve the system or the processing time within the transaction or XSLT.