Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 28 Next »

The field UDF Name has been hidden and is no longer visible in /PACG/ECM_UDF_CONF as it was redundant.

Overview screen

Send sel. UDFs to FSM

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

Detailed screen

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

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:

  • /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 (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.

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.

Examples

 Click to expand example 1

Workforce Management handles a User Defined Field (UDF) where the SAP FSM Cloud Connector will send commands. With this the send service activities are either added to planned section (as assigned or released) or in the unplanned section. The UDF Name must be COR_CLOUD_AssgPlan.The UDF is to be assigned for each company. Example values shown in the outbound message depending on the settings: This field is updated by the settings in "/PACG/ECM_SCTD - Service call types definition" with checkbox "Release Assignments". Assignment is automatically released to the technician if the responsible person and the assigned technician are the same. Else, it will be pre-assigned to the technician but not released.

Example values shown in the outbound message depending on the settings:

This field is updated by the settings in "/PACG/ECM_SCTD - Service call types definition" with checkbox "Release Assignments". Assignment is automatically released to the technician if the responsible person and the assigned technician are the same. Else, it will be pre-assigned to the technician but not released.

 Click to expand example 2

In the below example, a selection list is created for this UDF field that is applicable to the service call. The custom UDF field is shown in FSM service call screen as below.

The custom UDF field is shown in FSM service call screen as below.

  • No labels