Docs / Monitoring

Operations Guide

Recommended scheduled jobs and settings for running the ASAPIO Integration Add-on reliably in a productive system — change pointer cleanup, failed call reprocessing, log/trace retention, active alerting, and trace configuration. See also Monitor & Traces and SAP Cloud ALM.

Tasks to Schedule

We recommend scheduling the following reports as periodic background jobs (SM36) to keep a productive ASAPIO system clean and performant, and to catch delivery failures proactively.

Delete Change Pointers

Report /ASADEV/ACI_DELETE_CPS manages framework change pointers used for event reprocessing and tracking in table /ASADEV/MESG_STS.

Legacy note (releases below 9.32604 SP13): use report RBDCPCLR or transaction BD22 instead, which operates on table BDCP2. See SAP Note 2676539 for details.

Recommended schedule:

• Processed change pointers: clean up after 1–2 weeks
• Unprocessed change pointers: clean up after 1–2 months

Reprocess Failed Calls

Report /ASADEV/AMR_REPLICATOR reprocesses failed outbound calls. Create a variant in transaction /ASADEV/ACI and schedule it for periodic execution.

Recommended schedule: every 15 minutes (typical).

Delete Traces and Logs

Report /ASADEV/ACI_AMRLOG_DELETE deletes traces and logs from the framework tables (visible in transaction /ASADEV/ACI_MONITOR).

Typical retention: 1–3 months.

Active Alerting

Report /ASADEV/ACI_ACTIVE_ALERTING schedules monitoring of interface status, analyzing the failed/successful call ratio and sending automated notifications when thresholds are exceeded.

Trace Settings in Productive Systems

Disable trace in productive environments by unclicking the corresponding trace checkbox in the ASAPIO configuration.

Note: all messages are still logged and remain visible in the monitor application, including the cloud response. In case of an error, a trace is generated automatically regardless of this setting.