To prevent performance decrease and business processes hindrance as well as to reduce manual effort, it is highly recommended that certain integration management activities be run periodically. Integration administrators together with BASIS consultants can schedule background jobs to automate the processes.
Automation of monitoring processes
Certain monitoring processes such as idoc reprocessing or queue monitoring can be automated to reduce manual effort.
Administration activity | Program | Interval / range |
|---|---|---|
Reprocessing of unprocessed IDOCs 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 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. If you want to trigger automatic activation of queues via BB job, wherever possible, see also: Restart queues via BG job (program /PACG/ECM_RESTART_QUEUES) | Program /PACG/ECM_QSTATUS, transaction /PACG/ECM_QSTATUS - Email queue issues | Hourly for FSM Cloud Connector-related queues with statuses SYSFAIL, CPICERR, STOPPING, STOP, NOSENDS. Optionally for READY, WAITING, WAITSTOP with min. lifetime of e.g. 15 min. |
Table deletion
Tables storing technical data can quickly grow and hence should be reduced regularly in order to optimize performance.
For the first-time deletion, it’s recommended to split the deletion process into a few parts, based on age.
Administration activity | Program | Interval / range |
|---|---|---|
Delete entries from table /PACG/ECM_MIDMAP - Mapping of the message ID to the idoc number | Program /PACG/ECM_DELETE_MIDMAP, transaction /PACG/ECM_DEL_MIDMAP - Delete table /PACG/ECM_MIDMAP | Entries can be deleted if older than the number of days set in /PACG/ECM_CPROP - General Properties of FSM Cloud Connector, field Unconf.IdocsAge. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/75464857/PACG+ECM+DEL+MIDMAP+-+Delete+table+PACG+ECM+MIDMAP#Execution-recommendations |
Delete entries from table /PACG/ECM_EOBREF - SAP -> external object reference | Program /PACG/ECM_DELETE_EOBREF, transaction /PACG/ECM_DEL_EOBREF - Delete table /PACG/ECM_EOBREF | Delete entries older than a year. |
Delete entries from table /PACG/ECM_MSIDIM - Incoming message mapping | Program /PACG/ECM_DELETE_MSIDIM, transaction /PACG/ECM_DEL_MSIDIM - Delete table /PACG/ECM_MSIDIM | Delete entries without error status after 2 days. |
Delete entries from table /PACG/ECM_ARMAT - E4C: Reseved Materials Stock. For SD reserved materials on activity level, see also deletion report for table /PACG/ECM_RESBVB: Delete entries from table /PACG/ECM_RESBVB | Program /PACG/ECM_DELETE_ARMAT, transaction /PACG/ECM_DEL_ARMAT - Delete table /PACG/ECM_ARMAT | Preferably, delete entries based on order status (relevant for business process completion). |
Delete FSM Logs | Program /PACG/ECM_FSMLGH_DELETE, transaction /PACG/ECM_LOG_DELETE - Delete FSM logs or SBAL_DELETE, transaction SLG2 - Application Log: Delete logs, depending on settings in /PACG/ECM_CUSLOG, field Log Type | Delete entries older than 3 months or according to your company rules for data retention |
Delete unneeded IDOCs (and idoc data for the Cockpit in table /PACG/ECM_CIDOCS) Once the FSM Cloud Connector IDOCs have been successfully processed or sent, they are not needed in the system much longer. It is up to the Administrator whether they will stay on the system or will be archived with other IDOCs or old FSM Cloud Connector IDOCs will be just deleted. | For idoc deletion, use WE11. Learn more: Deleting unneeded IDOCs For deletion of idoc data used by /PACG/ECM_COCKPIT - FSM Connector Cockpit, see program /PACG/ECM_DELETE_CIDOCS, transaction /PACG/ECM_DEL_CIDOCS - Delete table /PACG/ECM_CIDOCS | Delete entries older than 3 months or according to your company rules for data retention |
Delete entries from table /PACG/ECM_ALTEW - Not booked Time Effort and Work Time | Program /PACG/ECM_DELETE_ALTEW, transaction /PACG/ECM_DEL_ALTEW - Delete table /PACG/ECM_ALTEW | The table stores all inbound time efforts therefore can grow to significant size. Deletion frequency and criteria should depend on whether time efforts are updated in FSM after synchronization (see Time efforts updated in SAP FSM) and whether the functionality of parking is used (see /PACG/ECM_POST_TIMEF - Rebooking of not booked Work Time and Time Effort). |
Delete entries from table /PACG/ECM_CIDOCS - Cockpit relevant Idocs | Program /PACG/ECM_DELETE_CIDOCS, transaction /PACG/ECM_DEL_CIDOCS - Delete table /PACG/ECM_CIDOCS | Idoc data is written to this table during inbound/outbound idoc processing, so that it can be later used by /PACG/ECM_COCKPIT2 - FSM Connector Cockpit (new). Delete entries with the same interval as idocs. |
Archiving
Archiving certain objects, such as FSM Activities or Message Broker logs, is a safer solution than permanent deletion.
Administration activity | Program | Interval/range |
|---|---|---|
Archive (ZIP) Message Broker logs | N/A, log storage location depends on Message Broker configuration. Learn more: Logs maintenance | Monthly |
Archive unnecessary FSM Activities FSM Activity objects can be archived. The solution provides three programs to write archive file, delete data from SAP DB and restore data into DB. If Activities should be deleted instead, use program /PACG/ECM_DELETE_OLD_ACT_CHK / transaction /PACG/ECM_DEL_OLD_AC - Delete activities | /PACG/ECM_ARC_DLT_E4CACT. Learn more: Custom Data Archiving - E4C activities | According to company’s data retention rules |
Other
Administration activity | Program | Interval/range |
|---|---|---|
Automated offboarding of FSM users. A dedicated tool allows to easily find persons in the company who are no longer employed based on Action type from PA30 (infotype 0000) such as retirement or leaving. | /PACG/ECM_USERS_OFFBOARD, transaction /PACG/ECM_USR_OFFBRD - Automated offboarding of FSM users | Depending on turnover rate and according to company’s data retention rules |
FSM attachments no longer needed in the SAP ECC/S4 system can be removed using the dedicated tool. It does not affect attachments in FSM. | Program /PACG/ECM_DELETE_ATTCHMS, transaction /PACG/ECM_DEL_ATTS - Delete Attachments | According to company’s data retention rules |
If arrival date should be calculated for reserved materials and displayed in FSM, a dedicated tool has to calculate it regularly | Program /PACG/ECM_RMAT_ARRIVAL, transaction /PACG/ECM_RMAT_ARRIV - Reserved Material - arrival date | Depending on reserved material process |
Assign the relevant authorization objects or roles to new SAP users. Learn more: FSM Cloud Connector Authorizations Objects and Roles |
|