Versions Compared

Old Version 27

changes.mady.by.user proaxia

Saved on

compared with

New Version 28

changes.mady.by.user proaxia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

UDF ID

A unique Id of the UDF

Cloud Message Type

A type of the FSM object which the UDF will be linked to

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

UDF Name

Field name (technical in cloud not in UI) no longer visible

UDF Description

Description of the UDF which will be displayed in FSM applications. This field is

Status
colourRed
titleOBLIGATORY
.

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

Panel
panelIconIdatlassian-warning
panelIcon:warning:
bgColor#FFC400

To avoid duplicates, do not check this field when using custom UDF implementations.

Info

Learn more about the feature and see detailed examples: Automatic inbound and outbound data processing of UDFs

Status
title(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).

Note

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).

Info

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:

  • /PACG/ECM_UDF_IN_SERVNOTIF_CH [used also for INCIDENT],

  • /PACG/ECM_UDF_IN_SERVNOTIF_CR [used during inbound service call processing for notification creation purposes],

  • /PACG/ECM_UDF_OUT_SNOTC [in case we send notifications as Service Calls],

  • /PACG/ECM_UDF_OUT_WBS [when WBS is used as Service Call]

For EQUIPMENT:

  • /PACG/ECM_UDF_IN_TELO [Dedicated for functional locations]

For BUSINESSPARTNER:

  • /PACG/ECM_UDF_OUT_CUST [customers as Business Partners]

For EXPENSE:

  • /PACG/ECM_UDF_IN_EXP_FI [posting to FI]

Send to FSM

Status
title(S4)PACG 200 SP07

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.

...