Versions Compared

Old Version 48

changes.mady.by.user proaxia

Saved on

compared with

New Version 49

changes.mady.by.user proaxia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Administration activity

Program

Interval / range

Reprocessing of unprocessed IDOCs

Panel
panelIconId1f4a1
panelIcon:bulb:
panelIconText💡
bgColor#FFFAE6

Certain IDOCs fail because of object lock, e.g. locked service order or CATS. This prevents an idoc from being successfully processed at a given moment and keeps the related object locked in FSM. The issue does not require any customizing/master data adjustment. An administrator can simply re-process such idocs manually later (e.g. in /PACG/ECM_COCKPIT - FSM Connector Cockpit). It’s recommended however to automate it by scheduling a periodic BG job.

RBDMANI2. Learn how to set up a BG job for this report: Reprocessing the unprocessed incoming IDOCs

Execute a few times a day (not more often than hourly) for FSM Cloud Connector-related idocs (MESSAGE TYPE /PACG/ECM*) with status 51 created in the last 24-48 hours

Queue monitoring

Panel
panelIconId1f4a1
panelIcon:bulb:
panelIconText💡
bgColor#FFFAE6

FSM Cloud Connector-related queues should be monitored on a regular basis to ensure the communication between SAP and FSM is undisrupted. An administrator/BASIS consultant could monitor queues using standard SAP transactions SMQ1 and SMQ2. It’s recommended however to automate this process by using the dedicated queue monitoring program and scheduling a periodic BG job.

Program /PACG/ECM_QSTATUS, transaction /PACG/ECM_QSTATUS - Email queue issues

Every minute for close-to-real-time monitoring of FSM Cloud Connector-related queues - with statuses SYSFAIL, CPICERR, STOPPING, STOP, NOSENDS. Optionally for READY, WAITING, WAITSTOP with min. lifetime of e.g. 5 min.

...