This subsection serves as a high-level overview of selected FSM Cloud Connector customizing steps for custom enhancements' implementation. :
| Table of Contents |
|---|
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 | /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 transactionCorresponding sending 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).
| /PACG/ECM_CLSASSIGIN - FSM Connector's Incoming Messages Configuration | |||||||||||
Replace the standard outbound processing classes with your own Z-classes
| /PACG/ECM_CLSASSIG - FSM Connector's Outgoing Messages Configuration |
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Next chapter: Mass synchronization (full sync) |