Custom enhancements

This subsection serves as a high-level overview of selected FSM Cloud Connector customizing steps for custom enhancements' implementation:

1 UDFs
2 Custom classes

For more detailed descriptions, navigate to links included in each step.

UDFs

Creation of user-defined fields allows addition of custom properties to any FSM object.

Configuration Step	Customizing transaction	Corresponding sending transaction
Specify user-defined fields, which extend the standard FSM objects	https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138034	/PACG/ECM_TRIG_UDF - UDF Definition

Custom classes

Each idoc processing class delivered with FSM Cloud Connector can be copied and adjusted to customer’s needs. It’s advised however 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.

Configuration Step	Customizing transaction
Replace the standard inbound processing classes with your own Z-classes. Specify if an object should not be saved in SAP ECC/S4, only confirmed back to SAP FSM (the so-called dummy booking). Use field 'Inb. Data creation' to replace the standard inbound processing logic with a custom Z-class logic. Learn more about inbound idoc processing logic in FSM Cloud Connector: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/940573207	https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952767
Replace the standard outbound processing classes with your own Z-classes Use fields ‘IDOC class / Data selection’ to replace the standard outbound processing logic with a custom Z-class logic. Learn more about outbound idoc processing logic in FSM Cloud Connector:

Next chapter: