/PACG/ECM_UDO_CONF - UDO configuration

General purpose

In FSM you can define UDO (User defined Object). In this transaction you have the possibility to do it from SAP.

Sending transaction (?)

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/38175456

(S4)PACG 200 SP09 You can navigate to the sending transaction using the button Send to FSM, placed on the toolbar.

Object assignment (?)

Object UDOMETA must be added to https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952609 for a given company

User-Defined Objects allow to create a custom object type and its instances, using User-Defined Fields as properties (see also https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138034). Use this transaction to create UDO definitions and transfer them to FSM. UDO instances (UDO values) are generated using custom implementations.

Example use cases

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.

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