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.

(S4)PACG 200 SP09 This version of https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138397 offers the same interface and functionality, however is significantly faster due to a new method of collecting data. The report reads idoc data from the dedicated table - /PACG/ECM_CIDOCS - instead of EDIDC. The idoc data is written to this table during inbound and outbound idoc processing. The table can be periodically cleared using the dedicating deleting report https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1880326310.

 Steps required right after upgrade to (S4)PACG 200 SP09

The Cockpit relies on idocs gathered in the dedicated buffer table. To be able to use the tool right after upgrade to (S4)PACG 200 SP09, it’s necessary to execute the program /PACG/ECM_FILL_CIDOCS which will fill the buffer table with idoc data (see the note 3342254). Otherwise, only idocs generated after SP upgrade will be displayed in the new Cockpit. The program considers only FSM Cloud Connector-relevant idocs.

The program should be executed at the time of the day when no new idocs are being generated, to avoid inconsistencies. It’s highly recommended to execute it in background, especially if the number of idocs exceeds 10 000. Otherwise the program may run out of memory.

FSM Cockpit functionalities - Main View

GUI Menu

(S4)PACG 200 SP12 Last fullsync/resend

The start and end datetime of latest resend/fullsync processes can be found via Go To → Last fullsync/resend:

(S4)PACG 200 SP13 Fullsync progress

Navigate to FSM Connector → Fullsync/Resend → Fullsync progress to check which fullsync-relevant objects were already processed and which ones are still pending.

(S4)PACG 200 SP14 PACG tabs statistics

The ‘PACG tabs statistics' feature is a functionality in FSM Cockpit designed to provide administrators with a quick overview of the usage and status of key FSM Connector’s tables.

The feature enables users to easily access and monitor statistics about specific tables used by the FSM Connector.

The statistics for each table include:

• Technical name: The system name of the table.

• Description: A brief description of the table's purpose.

• Number of lines: The current number of entries in the table.

• Last update timestamp: The date and time when the statistics were last updated.

User can update the status of the table manually by selecting the ‘Update Report’ button, where the Update statistics of PACG logs tables program is displayed. The report collects all the required data and updates it in the table.

Authorization Controls:

The feature includes specific authorization objects to control access to the statistics and the ability to run the update report.

• To display ‘PACG tabs statistics' user must have ‘/PACG_E_0024’ permission assigned,

• To run ‘Update Report’ program, user must have ‘/PACG_E_0023’ permission assigned.

When the ‘Update Report’ is running, the button is disabled.

Toolbar

(S4)PACG 200 SP09 Number ranges statuses

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

(S4)PACG 200 SP12 Mode

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 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. 

(S4)PACG 200 SP06 Connector version

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:

(S4)PACG 200 SP15 ARFCSTATE Info

This functionality monitors the number of entries in ARFCSSTATE table, which stores the statuses of sent aRFC calls, making it possible to track whether a specific function call has been processed correctly, is waiting to be processed, or has encountered errors.

The monitoring function displays following information:

• Date of last check - the date and exact time when ARFCSSTATE table was checked. The list of performed checks is stored in a dedicated Connector table /PACG/ECM_A_ARFC.

• Number of records - current number of records in ARCSSTATE table

• Average based on 10 readings - the average number of records based on 10 last records in /PACG/ECM_A_ARFC table. If there was less than 10 records, the average is based on available number of checks.

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

• Delete an IDOC

(S4)PACG 200 SP05 Refresh

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.

(S4)PACG 200 SP05 Set to processed for idocs with status 56

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.  

(S4)PACG 200 SP05 Delete

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.

(S4)PACG 200 SP11 Change 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 for idocs with status 40

Long text for negative confirmations returned by SAP FSM can be displayed by clicking on an icon in the column ‘Long message text’. This is useful for idocs with status 40 (FSM error - status 400 code ERROR). Such a status indicates that a given message was ‘rejected’ by FSM - the long message text can help understand the reason.

(S4)PACG 200 SP11 Order number and activity

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.

(S4)PACG 200 SP06 Multiple selection

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

A summary of affected idocs will be displayed:

(S4)PACG 200 SP06 Hotspots

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.

(S4)PACG 200 SP15 / 300 SP02 Hotspots are also implemented for S4 HANA Service Orders (Lean Orders). They open an order in a Fiori app.

(S4)PACG 200 SP10 Repeat

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 https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952654, field ‘Exclude COGI’

• Exclude selection of entries from the last month in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952654, field ‘Excl. LM’

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