S4PACG 300 SP 3

S/4HANA Service Orders Integration

• Support for mileages - Mileages created in FSM are reflected as expense items in the related S4 HANA Service order

Learn more: SAP S/4HANA Service Order - prerequisites and basic setup | Mileages

• Support for FSM checkout  

Learn more: SAP S/4HANA Service Order - prerequisites and basic setup | Checkout

• Support for Enterprise Organizational Model in parallel to the existing support for ‘Legacy’ model + Service teams (Enterprise Organizational Model) can be used as FSM Regions for filtering activities/technicians based on service team assignment.

Learn more: /PACG/ECM_VLO_GR - Regions for Service Order/Activity

• It’s possible to add attachments directly to FSM Activities from SAP S/4HANA (by adding an attachment to a service order item). Attachments added to Activities in FSM would be saved in SAP S/4HANA – on Service Order Item level. Before it was only possible to send attachments on service call level. 

• Expanded determination options for the Service Employee Group in the 'Legacy' model and the Service Team in the Enterprise Organizational Structure (EOS) model for incoming S/4HANA Service Orders

Learn more: /PACG/ECM_VLODS - S/4HANA Service Order Default Settings

• Partner functions for S4/HANA Service Order are adjusted. Partner's role can be mapped to relevant partner functions

In-House Repair process integration

The latest FSM Connector can initiate the In-House Repair process. In response to predefined checklist (smartform) filled be technician a dedicated Return Order can be created in the backend system. This Return Order initiates further IHR process according to following diagram:

Open

Learn more: In-House Repair integration

Administration

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: /PACG/ECM_SEND_DELRQ - Send Deletion Request to the Cloud

Enhancement of /PACG/ECM_DEL_MIDMAP

The selection screen of /PACG/ECM_DEL_MIDMAP was enhanced and deletion by company Id has become an available option

Learn more: /PACG/ECM_DEL_MIDMAP - Delete table /PACG/ECM_MIDMAP

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: FSM Cloud Connector Authorizations Objects and Roles | [inlineExtension]/PACG/E026 (S4)PACG 200 SP16 / 300 SP3

FSM User maintenance

All changes related to FSM users are from now on registered and changed documents are created which can be displayed in dedicated view.

Learn more: coming soon

Transaction /PACG/ECM_IDOC_REP

Transaction /PACG/ECM_IDOC_REP is from now on linked with the report /PACG/ECM_IDOC_REPORT2. The old report /PACG/ECM_IDOC_REPORT is still available in the system.

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: /PACG/ECM_EVTD - Enable/Disable FSM Connector Events

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: /PACG/ECM_EQUI - Equipment Master | (S4)PACG 200 SP16 / 300 SP3 Equipments' 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 attachments' age.

Learn more: Block from transfer to FSM / Outbound configuration

Production Orders

Productions Orders as Service Calls

• 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: /PACG/ECM_CTET - Time posting settings

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: /PACG/ECM_BP_ADDR - Address Determination for Business Partners | (s4)PACG 200 SP16 / 300 SP03 Address Determination for 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: /PACG/ECM_TRIG_PRERV - Person reservation

New transactions

• /PACG/ECM_DELETE_IN_XML