The field UDF Name has been hidden and is no longer visible in /PACG/ECM_UDF_CONF as it was redundant.
(S4)PACG 200 SP07 Use the Send sel. UDFs to FSM button to trigger transfer of the selected UDFs to FSM. Otherwise, transaction /PACG/ECM_TRIG_UDF - UDF Definition would have to be executed.
UDF ID | A unique Id of the UDF |
---|---|
Cloud Message Type | A type of the FSM object which the UDF will be linked to |
Object Subtype | Relevant for UDFs of cloud message type PERSON. FSM doesn’t recommended using the ‘no subtype’ option for PERSON UDFs (as stated in FSM Docs). Additionally, having the ‘no subtype’ option set clears UDF values entered in FSM, after synchronization. |
Type of the User Defined Field | Selection List (Selection list on mobile Devices), Character String, Integer …etc. |
UDF active | Activate/Deactivate field |
Mandatory | If ‘Mandatory’ is set to TRUE then the filed representing the UDF in FSM applications will be become mandatory to fill in |
Multiple Val. | Applicable only for types of UDFs that offer such possibility like Selection List. When this option is set to TRUE it is then possible to select more than a single value |
Field Length | Field length |
Default Value | Default value of the UDF |
Validation Regex | Validation regular expression |
Parent UDF ID | Parent UDF |
OBLIGATORY UDF Description | Description of the UDF which will be displayed in FSM applications. |
Source characteristic | Filled automatically by the UDF building program if a UDF definition was built based on an equipment characteristic class. |
Store internal | When this option is enabled then an UDF does not need any additional handling (BAdI implementation) in the backend ERP system. The value entered in the FSM is automatically stored and sent back. This option is relevant only for the scenarios where UDFs' values are maintained in FSM only To avoid duplicates, do not check this field when using custom UDF implementations. Learn more about the feature and see detailed examples: Automatic inbound and outbound data processing of UDFs |
(S4)PACG 200 SP06 Inb. BAdI / Out BAdI | Navigate to an inbound/outbound BAdI definition dedicated to a specific cloud message type (e.g. for UDFs with cloud message type ACTIVITY, the links lead to BAdI definitions /PACG/ECM_UDF_IN_ACTI_E or /PACG/ECM_UDF_OUT_ACTI_E accordingly). Mapping between cloud message types and BAdI definitions is stored in table /PACG/ECM_UDFMAP. It is filled by the setup program (/PACG/ECM_SETUP). Please note that each button can lead to 1 BAdI definition, based on the prefilled customizing. For certain message types, there exists more than 1 possible inbound/outbound BAdI definitions. For SERVICECALL, the following other BAdI definitions exist:
For EQUIPMENT:
For BUSINESSPARTNER:
For EXPENSE:
|
(S4)PACG 200 SP07 Send to FSM | Use the Send sel. UDFs to FSM to trigger transfer of the selected UDFs to FSM. Otherwise, transaction /PACG/ECM_TRIG_UDF - UDF Definition would have to be executed. |
Companies Assignment
UDF must be assigned to at least one company otherwise it will not be sent to FSM due to a missing destination.
Values - Selection List
Relevant for UDFs of type Selection List.
A selection list requires list of possible options to be defined. For UDF of type ‘Selection List’ assigned to multiple companies it is possible to define a unique list for each of them by assigning. To achieve that selection option must be defined to relevant companies accordingly.