Monitor inbound/outbound idocs, as well as Message Broker status, queues, short dumps (runtime errors), logs and COGI entries. From this transaction users can navigate directly to SLG1, SMQ1/SMQ2, COGI and ST22.

FSM Cockpit functionality

Main view

Ping Message Broker

Cockpit pings all used logical ports from the company assignment and the status icon displays the results according to the below logic: 

• If all pings are successful, then the status icon should be green,  

• If all pings result in error, then the status icon should be red, 

• If there are different results, then the status icon should be yellow. 

Ping button shows results for all or for selected companies. If All option is chosen, then the company list with the icon status (green/red) is displayed in the pop-up window.  

After choosing (double clicking) the specific company, the status of the message broker related to the chosen company is displayed in Message broker status icon section.  If the company is not set up in /PACG/ECM_CACC - Company Account Assignment, then the new blue status icon is displayed. 

Connector version

(S4)PACG 200 SP06

Connector version can be checked from main Cockpit’s screen. In FSM Cloud Connector section is available button ‘Connector Version’, after click on it will be displayed pop window with information:

Number ranges statuses

(S4)PACG 200 SP09

Use the button ‘Number ranges statuses’ to navigate to an overview of FSM Cloud Connector-related number range intervals and their statuses.

Click the ‘Change status’ button in a given entry to navigate to change number range status transaction (SNRO).

Idoc view

In the idoc view you can:

• Set IDOC as processed (set IDOC status)

• Process IDOC – call transaction BD87

• Display processing log as in transactions WE02/WE05

• Display IDOC content as in transactions WE02/WE05

• Change IDOC data

• Delete an IDOC

Refresh

(S4)PACG 200 SP05

This function reloads IDocs list. In the releases prior to (S4)PACG 200 SP5 the refresh functionality for idoc list was available under the ‘Idoc’ menu. only.

Set to processed for idocs with status 56

(S4)PACG 200 SP05

If the FSM Cloud Connector transporter does not receive confirmation for a message after a certain amount of time (around 15 minutes), the transporter resends the same message. Such timeout should not happen if connection and traffic is well optimized. Duplicated messages will be identified and receive status 56 ((S4)PACG 200 SP6 - from SP06 automatically set to status 68) but this does not prevent them from being reprocessed in SAP. That could cause data overwriting. To avoid that, it is now possible to set idocs with status 56 to processed. When idocs are manually set to processed, their status changes to 68 (for inbound idocs). As a result, the idoc’s status is changed to 68 and the IDoc can no longer be re-processed.  

Delete

(S4)PACG 200 SP05

Marked IDocs can be deleted with ‘Delete’ button.

(S4)PACG 200 SP08

Deletion is carried out by means of the report /PACG/ECM_RSETESTD (tcode: /PACG/ECM_WE11) which is a copy of SAP standard report RSETESTD. The difference between the standard report and Connectors version is that second one can delete only /PACG/* IDocs and utilize authorization object /PACG/E013.

Change status

(S4)PACG 200 SP11

Changing Idoc status can be done in similar way as in standard report RC1_IDOC_SET_STATUS. However, the new tool in cockpit2 assume better consistency (Cockpit2 does not consider status changes done in standard report) and is easily accessed. ‘Message type’ and ‘Current status’ inputs are limited only to the ones applying to the selected IDocs. Additionally, in new ‘New status’ can be entered value only for allowed statuses - if the user wants to select for outgoing messages a status dedicated only to incoming messages, the system will display an error message. Moreover, it is possible to choose statuses only relevant for Connector. Access to functionality can be customized by authorization object /PACG/E021.

Long text message

Long text for negative confirmations returned by SAP FSM can be displayed by clicking on an icon in the column ‘Long message text’.

Order number and activity

(S4)PACG 200 SP11

In the column ‘Order’ you can find reference to the idoc’s order number. After clicking on the number, user will be navigated to order’s related transaction. Depending on selected order type, hotspot will redirect to following transaction:

• Service order - IW33

• Service Notification - IW53

• PM notification - IW23

• Network orders - CN23

• WBS orders - CJ13

In the column ‘Operation/Activity’ the order’s operation’s number is displayed. This functionality works for both incoming and outgoing Idocs.

Multiple selection

(S4)PACG 200 SP06

Idocs can be set to processed, processed or deleted collectively by selecting multiple entries:

A summary of affected idocs will be displayed:

Hotspots

(S4)PACG 200 SP06

Object key fetches links which can redirecting to transaction. The object key holds information in the form of a link. Most objects have it, so that after click on it user can move to the related transaction. For example, if an object relates to a service call then hotspot will move the display to iw33.

Repeat

(S4)PACG 200 SP10

It is possible that if transfer of an outbound idoc fails, in the period between the initial attempt of sending the IDoc and the attempt of resending it, a newer version of an object is created in FSM and synchronized to SAP. That means that resending of the previously failed IDOC may lead to a situation in which a newer version of the object will get overwritten by the older one. This can be avoided by using the ‘Repeat’ option for failed outbound idocs.

The option performs two actions:

• Set the status of a failed idoc directly to ‘processed’ (41) - treat the idoc as sent but don’t perform actual transfer

• Initiate resending of the related object – this way we can assure that latest available version of an object is sent to FSM

Access to the functionality requires authorization objects /PACG/E018 and /PACG/E019.

Cockpit’s performance

There are a few ways in which the Cockpit’s performance can be improved:

• Exclude COGI selection in /PACG/ECM_COCKPITCON - Cockpit Configuration, field ‘Exclude COGI’

• Exclude selection of entries from the last month in /PACG/ECM_COCKPITCON - Cockpit Configuration, field ‘Excl. LM’

• Create an index for the table EDIDC on your system, see an example below: