Content Comparison

Administration

FSM Cockpit
The FSM Cockpit can now show information about the number of entries in ARFCSTATE table and average of last 10 size checks. This can help to quickly identify potential performance problems

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/2137096193/PACG+ECM_COCKPIT2+-+FSM+Connector+Cockpit#ARFCSTATE-Info

FSM Cockpit – IDocs report & Hotspots
In the Connector 3.0, in the IDocs list, S/4 HANA Service Orders are now correctly identified and when clicked a dedicated Fiori app is opened (analogically to other objects for which GUI transaction is started)Version check in /PACG/ECM_SEND_DELRQ
Recently /PACG/ECM_SEND_DELRQ gained the possibility of removing FSM objects by FSM Guid. However this requires version 4.6 of Message Broker at least. In case of older message brokers deletion request is considered as erroneous and entire outgoing queue gets blocked. To avoid such situation the report can now check message broker version and for the older ones the deletion by FSM Guid is disabled

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/2137096193/PACG+ECM_COCKPIT2+-+FSM+Connector+Cockpit#(S4)PACG-200-Sp06-Hotspots

FSM Cockpit – IDocs report & custom IDocs
In addition to standard Connector’s IDocs, the FSM Cockpit is now capable of showing also IDocs of the custom types if such are used with Connector

New Checks for 37138563

Enhancement of /PACG/ECM_QSTATUSDEL_MIDMAP

The selection screen of /PACG/ECM_QSTATUS report can now send warnings in the the following new situations:

DEL_MIDMAP was enhanced and deletion by company Id has become an available option

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1508114433/PACG+ECM_QSTATUS+-+Email+queue+issues#IDOCs-in-error-status

FSM Users’ Management
New FSM Connector delivers a report which can create FSM Users based on data imported from excel file

Learn more: Mass User Upload

Companies’ deletion
The existing set of deletion reports was enriched with additional one which allows for deletion of all transactional data for selected company in one go75464857

FSM Cockpit - IDoc report

To avoid further confusions the ‘REPEAT’ button was removed from the screen showing incoming IDocs since it is not possible to repeat processing anyways.

Export and import transport - Connector tools

These two transactions have now the authorization checks added and new authorization roles have been created specifically for these two reports.

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/19189268821702854657/PACG+ECM_COPY_COMP2+-+Copy+delete+company+settings#FSM+Cloud+Connector+Authorizations+Objects+and+Roles#%5BinlineExtension%5D%2FPACG%2FE026-(S4)PACG-200-SP15SP16-%2F-Delete-program%3A-Transactional-Data

Equipment and functional locations

New selection class

A new selection class for equipment and functional locations has been implemented and delivered in this release

New event for triggering of functional locations

With a new event type dedicated to functional locations, it is now easier to control when equipment and functional locations are sent to FSM - independently from each other.

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1859878946

Message Broker health status
A new report which helps to monitor ‘health’ of the message broker. It relies on the information about last metadata exchange between transporter and FSM

Business Partners

Customers’ Deactivation
FSM Connector is now capable of handling customers’ deactivation in FSM, i.e. when a Business Partner is deactivated in the FSM system, it no longer gets reactivated after data synchronization with SAP. 

Optional transfer of Business Partners to FSM
Business partners can now be sent to FSM ‘on demand’. This means, that like in case of equipment, BP master data will be sent to FSM with their first usage in a service call instead of sending all BP master records during the fullsync process1832550401

Send equipment and functional locations in batches

Paging functionality was added to sending reports for equipment and functional locations. This new feature allows transmission of large amounts of data without causing program termination due to high data volumes.

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/116660637938175164/PACG+ECM_CCUSTEQUI+-+General+customizing+for+Customer#Equipment+Master#(S4)PACG-200-SP15SP16-Cust%2F-on-req and https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1173979146/PACG+ECM_CVEND+Vendor+General+customizing#(S4)PACG-200-SP15-Vend-on-req-(Send-Vendor%2FContact-on-request)

Regions

Work centers as regions
In FSM regions can be structured in hierarchies. This feature is now also supported by Connector which can send work centers as regions including their structural dependencies

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37136514/PACG+ECM_SC_GR+Group+region+for+service+calls+activities#Include-Hierarchy-(S4)PACG-200-SP15 300-SP3--Equipments%27-batch-size

Send equipment or functional location with service order

Performance improvements related to the sending of equipment (and functional locations) only if required by service order. Previously, these were sent every time sending of service orders were initiated, bypassing the hash verification functionality. From now on they will be sent only when truly needed.

Check if parent is FSM relevant

When sending equipment or functional location having the parent and the parent is not FSM relevant, the object itself will not be visible in FSM. To avoid such situations the additional check was implemented - Connector verifies relevancy of parent and removes it when irrelevant.

Attachments

Data transfer restrictions
Sending of attachments to FSM can from now on be restricted based on the storage type used (GOS, BDS, DMS)attachments' age.

Learn more:https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/928809057/Block + from + transfer + to + FSM +Outbound+configuration#%F0%9F%95%91-Block-from-transfer-to-FSM-%2F-OLD-LABEL-Outbound-/ Outbound configuration

Production Orders

Productions Orders as Service Calls

• Service calls created based on production orders

• Plannable activities’ created in reference to production orders

• Support of attachments added to production orders and referenced service calls

• Time effort handling

• Checklists’ assignment support

CS Service Orders

FSM Activity

Fiori App
The latest SP for Connector 3.0 delivers brand new Fiori app to display FMS activities

Operation’s control key and FSM activity status
If the control key of a operation having linked activities changes to one that is not FSM relevant, the related activities will get automatically closed.

Reserved materials

• The material being the subject of a production order is from now on integrated with the FSM Activity as a Service Item

• The unplanned materials’ consumption is from now supported for the production orders – reported usage is booked against relevant order

• The materials’ reservation based on ‘direct consumption’ scenario are from now on supported by production orders.

• Reopening of FSM Activities after TECO cancelation was implemented for Production Orders

• Checklists’ assignment to activities based on production orders headers’ properties was added

Learn more: SAP S/4HANA & ECC Production Orders (PP) Integration

Service contracts

• Service contracts are now capable to rely also on functional locations. Before only use of equipment was supported

• When sending equipment or functional location to FSM connector first checks if object is FSM relevant

Worktime patterns

Dynamic worktime patterns
In addition to fixed-time work patterns Connector can handle now dynamic worktime patterns where break time relies on the time of actual work

Time effort configuration

Order type dependant time efforts

Time effort configuration gained another level of granularity. From now on it will possible to handle incoming time efforts depending on the type of order they refer to

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37136235/PACG+ECM_SCTDM+Mvmts+for+mat.+consumption+in+FSM#(S4)PACG-200-SP15-Return-Cons-OrderArrival date determination
The initial requirement date is set automatically when reservation is created based on requirement date in the related service order. This does not take the type of process into account. This turned to be confusing for some customers. As a result new configuration option was introduced which controls whether the initial arrival date of reserved materials should be set based on requirement date or not.37137707

Time subtask generation

Generation of time subtask was obsoleted in this release. From now on only generation of time task is supported.

Contact persons

Addresses' handling

Addresses added to contact persons in FSM are not correctly handling by the Connector - addresses are saved in the backend system

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/20947271692309259265/PACG+ECM_VSCTDBP_ADDR+-+Address+ServiceDetermination+Callfor+typesBusiness+definition#Partners#(S4s4)PACG-200-SP15SP16-%2F-300-SP2SP03-PrefillAddress-ReservedDetermination-Material%E2%80%99sfor-Arrival-Date

Arrival date determination report
The arrival date determination report gained new selection parameters including:
• FSM Activity number
• FSM Activity status
• Shipment status
• Consider consignment

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1722679297

Equipment

Characteristics sent as remarks
New Connector version delivers small yet important change in how remarks are generated based on equipment’s characteristics. In case of characteristics that comes with predefined values, from now on, in addition to the values themselves Connector will also include their descriptions.Contact-Persons

FSM Activity

Activity maintenance transaction
The duration of activity is now calculated only if start and end time change. Otherwise the value stored in DB is displayed

Performance

Incoming XML handling

There are several objects in the Connector which require sending of the ‘Generic IDoc’ as a confirmation. For this to work, an incoming XML must be stored in the system. Until now they were saved as the regular attachments. With the newest connector, this has changed and from now on these XMLs will be stored in the dedicated table.

UI improvement

• /PACG/ECM_CHECKL_SHW can display checklists containing more than 50 field.

• ‘Deletion handling’ option was removed from configuration view /PACG/ECM_ACTIVE - this option is not supported by Connector

• Selection screen of /PACG/ECM_TRIG_PERSRESERV was improved - two different fields for providing personal number was replaced by one which is used for all supported cases

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953680

UI modification

In transactions /PACG/ECM_COMP and /PACG/ECM_CCUST entries’ deletion got suppressed. Since Connector delivers dedicated reports for deleting companies data deletion of companies deletion is not only no longer needed but can lead to data inconsistencies

Employees

Changes in the HR Infotype 0105 using transaction PA30 are now transferred to FSM automatically – relevant even is raised. Valid subtypes of infotype 0105 for which this will happen are

37138845

New transactions

• /PACG/ECM_ACTI01

• /PACG/ECM_ACTI02

• /PACG/ECM_ACTI03

• /PACG/ECM_PCONF

• /PACG/ECM_TRIG_ACTST

• /PACG/ECM_VNRSTDELETE_IN_XML