| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
In order to use full functionality of FSM Cockpit please check required authorizations |
| Info |
|---|
Use transaction /PACG/ECM_COCKPITCON - Cockpit Configuration to customize the Cockpit functionality. |
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.
| Table of Contents | ||||
|---|---|---|---|---|
|
FSM Cockpit functionalities - Main View
GUI Menu
| Status | ||
|---|---|---|
|
The start and end datetime of latest resend/fullsync processes can be found via Go To → Last fullsync/resend:
| Info |
|---|
The start datetime for fullsync refers to the first transferred object of the latest fullsync. The end datetime for fullsync refers to the last transferred object of the latest fullsync. The fullsync may still be ongoing and the end datetime may change after refresh. Tables /PACG/ECM_SYNCID and /PACG/ECM_ARESTC store more detailed/historic log traces. |
Toolbar
| Status | ||
|---|---|---|
|
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).
FSM Cloud Connector segment
| Status | ||
|---|---|---|
|
The ‘Mode’ property informs the user about an ongoing fullsync or resend process. It displays one of the following values:
Standard - default, no fullsync or resend is being executed
Fullsync – indicating that Message Broker is in the process of fullsync execution
Resend - indicating that Message Broker is in the process of resend execution
When Message Broker is in mode ‘Fullsync’ or ‘Resend’, an information pop-up must be additionally is displayed after opening the Cockpit.
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.
| Status | ||
|---|---|---|
|
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:
FSM Cockpit functionalities - 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
| Note |
|---|
It’s not recommended to change IDOC data unless performed extremely careful, by a knowledgeable consultant. IDOC modification cannot be reversed. |
Delete an IDOC
| Status | ||
|---|---|---|
|
This function reloads IDocs list. In the releases prior to
| Status | ||
|---|---|---|
|
| Status | ||
|---|---|---|
|
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 (
| Status | ||
|---|---|---|
|
| Status | ||
|---|---|---|
|
Marked IDocs can be deleted with ‘Delete’ button.
| Status | ||
|---|---|---|
|
| Status | ||
|---|---|---|
|
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’.
| Info |
|---|
Learn more about negative confirmations: Negative confirmations - idoc status 40 |
| Status | ||
|---|---|---|
|
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.
| Status | ||
|---|---|---|
|
Idocs can be set to processed, processed or deleted collectively by selecting multiple entries:
A summary of affected idocs will be displayed:
| Status | ||
|---|---|---|
|
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.
| Status | ||
|---|---|---|
|
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.
| Info |
|---|
The functionality is relevant for the following idoc statuses: 18, 03, 30, 02, 04, 05, 25, 29, 26, 32, 40, 51, 56, 61, 63, 65, 60, 64, 66, 69. |
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:
