| Product(s): | APM Implementation and Performance Management | ||
| Version(s): | 7.6 & lower | ||
| Environment: | N\A | ||
| Area: | N/A | ||
| Subarea: | N\A |
The SAP PI integration component was not running for a number of days, and the SAP transactions entered during that time, were not passed over to APM after SAP PI was started.
The SAP PI component fetches SAP changes that occurred within the last day. This would mean that for the period of time that SAP PI was inactive, when it is reactivated, only the transactions within the last day will be sent to APM.
The Triggering_Outbound_Interface_DM document has a section on Creating a Job to Trigger the Outbound Interface, that can be followed to recover the missed transactions. The steps are in a sub-section title Creating Variants. This will allow you to schedule a job to capture transactions for a user-defined number of days. This document is applicable to both single-stack and dual-stack.
Note: Ensure that you set the correct "RFC Destination" for your integration environment.
N/A.
| Original Author: | Roy Suthers |