FSM Cloud Connector Enhancements

FSM Cloud Connector offers the following enhancement capabilities:

1 UDFs
2 UDOs
3 BAdIs
4 Custom classes
5 Posting Framework

UDFs

User-Defined Fields allow extending an existing data model in FSM. A custom field can be added to any object type in order to store properties not represented by standard FSM fields.

Example use case of UDFs #1 – display properties not related to standard fields

Equipment characteristics values can be transferred as UDF values and displayed in FSM master data. Update of the equipment characteristic values in FSM results in update on the SAP ECC/S4 side.

Example use case of UDFs #2 – trigger action in SAP backend

UDFs can be used to trigger certain action in the backend. E.g. to decide what kind of equipment structure update should take place when consuming a serialized material.

Example use case of UDFs #3 – update a master data object based on data from Activity/Service Call

Phone number of a Contact Person entered in an Activity UDF would update phone number of the related Contact Person record. Business Rule copies it to Contact Person’s UDF - this triggers object update and the contact person’s number is updated in SAP backend.

UDOs

User-Defined Objects allow to create a custom object type and its instances, using User-Defined Fields as properties.

Example use case of UDOs #1 – trigger action in FSM (e.g. a notification) based on action in SAP backend

A technician should get a notification about a goods movement/delivery in SAP. FSM Cloud Connector generates a UDO instance whose creation triggers a business rule sending a push notification to technician’s phone.

Example use case of UDOs #2 – configurable selection list in checklists, which can additionally be filtered

Checklist pickers can refer to UDO values (instances). UDOs can be used as input help
A UDO picker can use another UDO as a filter. Selection within one field impacts the available values displayed in another

BAdIs

Business Add-In (BAdI) is an is an object-oriented enhancement implementation technique that empowers developers to add custom functionality to a solution without altering the original source code.

Example use case of BAdIs #1 – determination of values for custom fields and objects

Determination of UDF values based on custom logic

Example use case of BAdIs #2 – custom logic for determination of certain properties

Determination of Equipment coordinates

Example use case of BAdIs #3 – idoc output

Edit entire idoc or decide if it’s even relevant for sending based on properties

Example use case of BAdIs #4 – trigger event

Specify if an event should be triggered – based on object key, type, category, event name and other values

Custom classes

Each class delivered with FSM Cloud Connector can be reimplemented and adjusted to customer’s needs. Such classes are referred to as custom classes or Z-classes.

It’s advised to implement BAdIs instead, wherever possible. Replacement of a standard class with a Z-equivalent results in breaking upgrade continuity - functionalities or corrections delivered for the affected processing step in new service packs/SAP notes must be implemented manually.

Example use cases of custom classes

Overwriting or extending standard processing. In principle implement logic which cannot be implemented as a BAdI.

Service checkout trigger sales order update

Fully custom reserved material creation process

Additional filter/selection criteria during outbound idoc processing

Posting Framework

Posting Framework is the mechanism allowing automatic processing of inbound checklist in a step-based manner. It allows to define scenarios consisting of one or multiple steps.

The diagrams below demonstrate the posting framework mechanism:

Learn more: Posting Framework