Versions Compared

Key

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

...

Contact Source

Source object for Contact Person in Activity. Option ‘Only cloud’ means that contact person property should be filled in FSM and will not be overwritten by SAP values (service order/notification/customer partner functions). If not entered in FSM, contact person will remain empty.

Equi source /
Status
titleOld LABEL
Send Equi

Customize what is sent as equipment in outbound activity idocs.

Note

In the past the Equi&telo setting in transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953646 handled this functionality. The new customizing has been separated and expanded.

Note

If an equipment were assigned to an activity in SAP FSM, the exact same equipment would be resent, regardless of the ‘SEND_EQUI’ setting for activities. This is checked in table /PACG/ECM_ACTI, field ‘EQUIPMENT’ (or ‘FUNCTIONAL LOC’) and serves the purpose of avoiding overwriting activity information updated from FSM.

Send equipment from service order operation as activity equipment

Expand
titleClick to expand the example

In transaction /PACG/ECM_ACTIVE, set the ‘Send Equi’ field to ‘Equipment from operation’.  

 

Create a service order operation with equipment assigned.  

 

After saving, the operation equipment can be found in a new /PACG/ECM_ACTIVITY_OUT idoc, segment ‘/PACG/ECM_IS_ACTIVITY’ and field ‘EQUIPMENT’.

Planning Plant

If field is checked notification plant ID in IDOC is taken from planning plant otherwise plant ID is taken from maintenance plant. Configuration is working when service notification is sent as activity to FSM.

Act/Ord in Subj

Depends on selected option Activity subject can be send to FSM as:

  • Activity number + operation short text

  • Order number + operation short text

  • Only operation short text

Example in FSM: Activity subject from activity number option

Operation texts

Use the operation’s long text as the activity’s remarks, instead of the service order’s long text.

Please note that starting form the Release 2111 this option will not be available - operation’s long text will be always used as the activity remarks. Additionally, the new option Order’s header long text to acti remarks will be available in transaction/PACG/ECM_SCTD.

No Customer TZ

Planning Times can be interpreted in Time zone of Customer (Setting in /PACG/ECM_COMP - Company definition). As company setting is for planning times & time effort, it can be overruled here.

Cont. Person SO

Enter a service order partner function which should be used for service call and activity contact person determination. If lefft empty, value ‘CP’ will be used. Please note that contact person masterdata must be sent beforehand to FSM, otherwise the contact person in service call/activity overview will not be displayed correctly. Contact persons are sent together with customer master data.

Activity Partner Role

SP&SH Partner Function from SC Definition - Partner role for “sold to” and “ship to” will be taken from settings t-code /PACG/ECM_SCTD (Sold to & Ship to)

SP&SH Partner Function from AC Property - partner role will be taken from configuration Activity Sold-To, Activity Ship-to

This values are stored in table /PACG/ECM_ACTI for created activity.

Upd Operation Method

Allow operation update based on changes of activity in FSM, e.g. activity description/technician/dates update in FSM results in operation description/technician/dates update in SAP ECC/S4.

Note

Please note that this option does not have any impact if ‘Use req. ass.’ is enabled in transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/2094727169. The option "UseReqAssign" should be used in case of multiple activities created to single operation. In such a case you there’s only one place on the backend side and several activities assigned to it. If you change anything on operation level, then all activities will be affected. Therefore if the option "UseReqAssign" is active there is no update on operations. This is not a bug, it is implemented by design. If you would like to have the operations updated from activities, please switch this option off.

SArea Object

During creation of an activity, FSM Cloud Connector gets sales area from sales area assignment for object ACTIVITY with flag “default”. This means that all activities created during ASA event (in SAP ECC/S4) and during creation from FSM have only one sales area per company. This is not good for companies working with sales area assignment for service order and/or for service notification as a service call.


If this flag is set, FSM Cloud Connector:

  1. Checks if the service order/service notification has an assignment to sales area (entries in transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952565 for objects SERVICECALL - if it’s a maintenance order, or SNOTC, for service notification-based service calls)

  2. Checks if the found sales area is set in a given order/notification

  3. If it’s set and this sales area is also defined in transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952565 for object ACTIVITY, then the Connector sets this sales area assignment for the processed activity (instead of the one marked as “default”).

RemvdOpAct

By default, removing an operation in transaction IW32 will result in setting the related activities' status to ‘CLOSED’. To make it clear that an activity is closed because of a removed operation, a user-specified text can be added to activity remarks or the activity subject (as a prefix).

The attachment will be saved in SAP ECC/S4 on the activity level.

The attachment will also be available from the activity’s service order’s notification’s level in SAP ECC/S4.

Removed operation text

Enter the text to be set as activity subject prefix or remarks for activities related to deleted operations. See field ‘RemvdOpAct’ above.

WF Step for removed operation

By default, removing an operation in transaction IW32 will result in setting the related activities' status to ‘CLOSED’. To make it clear that an activity is closed because of a removed operation, a user-specified workflow step can be set for such activities. Enter the name of a workflow step which should be assigned.

If left empty, no workflow step will be set.

Number range interval number
Status
title(S4)PACG 200 SP04

This property lets selecting different interval for FSM Activities number range (/PACG/ECM1) than the default 01. The interval must be defined with SNRO before it can be used. In case provided interval didn't exist it will be created with the default range

Suboperation activities as follow-up act

This function defines a hierarchy of operations and their suboperations.

If function is enable, for each suboperation an activity is created and they’re linked to the parent activity (operation) in a visible way.

image-20240816-083412.png

The hierarchy is reflected in the FSM mobile application, enabling technicians to easily identify and manage the sequence of tasks, ensuring the correct workflow and order of tasks. The enhancement provides a visible connection between operation and sub operations.

image-20240816-082210.png

image-20240816-082329.png

If a functionality is deactivated, created hierarchy of suboperations for the parent operation won’t be reflected in FSM. The activities related to the suboperations are not linked to the main operation’s activity – they exists on the same level.

Info

Creating a new follow-up activity in FSM won’t generate any new suboperations in the related order, just an operation or relationship to an existing operation. 

Suboperation entries are stored in the /PACG/ECM_ACTI table.

image-20240816-091747.pngImage Added

Attachment-related customizing options

...