PACG 200 SP 2 / S4PACG 200 SP 2

Service order/Activities

• Default FSM Connector linkage type between the operation and activity is one to one – one operation, one activity. However, under certain business-related circumstances it can be more suitable to link several activities with a single operation in the service order. From now on such feature will be available based on the new configuration option. This also covers planning and rearranging reserved materials among activities linked to single operation

• The COR_CLOUD_AssgPlan UDF is crucial for proper functioning of activities and assignments. Because it is “just a UDF”, it was treated like other UDFs which means it had to be assigned to a company (or companies) and sent to SAP FSM (for instance manually, using sending report). With this release, we automated sending of this particular UDF to FSM so users don’t need to care about it anymore. It is a relatively small enhancement but thanks to it, situation where it was forgotten resulting in problems with activities’ automatic release from SAP can be easily avoided

• It is possible to set user status in the service order based on Origin value set in FSM service call. This was working fine when using unnumbered users’ status. However, this was a limitation for customers who often use numbered status (defining certain dependencies between them). With this release this functionality got extended and from now on, FSM Connector can deal properly with both statuses' types

• The update of an activity is sent to FSM when it is recognized in the backend system that the objects has changed. Till now, the determination of the change was done based on certain standard properties. With this release, we introduced a new BADi which lets users add own logic to this determination process

Reserved materials

‘Book component’ option in service order settings of FSM Cloud Connector causes addition of new reservation for material in case of so-called ‘unplanned consumption’. The new reservation was also created if there was already one for a given material. Due to customers’ request, this has changed. Now, in case of unplanned consumption, FSM Connector first checks if there is already a reservation for a material and creates it there is none.

Materials

Additional way of determining if a material is batch-managed - this new feature has a significant impact on the determination of batchable/non-batchable materials but specially the latter. Default determination was the following: check general material data, check plant material data, and check valuation of material. Even if material was set as non-batchable but valuation was found, it was sent as batchable. A new configuration option was introduced. If enabled, the valuation is not checked and only material’s settings are considered.

Expenses

Until now, when posting expenses using cost center, the cost center was determined based on either work center of the person (technician) or simply the fixed value stored in the customizing was used. A new option was introduced - it will also be possible to use cost center determined based on the activity type.

Performance

• FSM Cloud Connector will be sending the list of supported objects to SAP FSM - relying on it, the FSM will be able to suppress sending of objects to the Connector which cannot be interpreted correctly

• In order to lower the load of the outbound queues and speed up the entire communication process, we introduced additional options giving more flexibility in setting up system queues

  • Split traffic between inbound and outbound queues. Until now, only outbound queue was used for handling traffic in both directions (despite its name). Now it will be possible to use the inbound queue for inbound traffic and the outbound queue for outbound.

  • In addition to the point above, it will also be possible to enable additional queue only for handling confirmations

  • Last but not least, it will be possible to define own queues using a newly created BADi and split the traffic among in a way that best fits the requirements

• The default number of messages that can be processed within a single LUW was increased and in addition can be controlled with a configuration option