/PACG/ECM_ACTIVE – General Properties of E4C Activity

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.

Customize what is sent as equipment in outbound activity idocs.

Send equipment from service order operation as activity equipment

 Click 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’.

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.

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

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.

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.

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.

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.

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.

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

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.

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

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.

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

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.

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.

PRTs of type ‘Document’ which are assigned to an operation will be transferred to FSM as activity attachments.  

More specifically, PRT document refer to DMS documents whose files will be transferred as activity attachments.

Activities can inherit attachments from the related service orders. When an attachment is created for a service order in SAP ECC/S4 and this field is checked, an attachment reference will be created for the related activities in SAP. Such new activity attachments will be automatically transferred to SAP FSM, if not blocked by the outbound configuration (e.g. setting ‘block out’ in the General configuration).

See: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/842661889

Example process

 Click to expand the example

Make sure that the ‘Link SAP Atta. of Service Ord. to Acti’ field is enabled.

Create an attachment of any relevant type (GOS/BDS/DMS) for a service order. In the example below it is a SAP Office (GOS) attachment.

The attachment reference will be automatically added to the service order’s activity in SAP ECC/S4.

Additionally, the new activity attachment will be transferred to SAP FSM.

Activities can inherit attachments from the related notifications. When an attachment is created for a notification in SAP ECC/S4 and this field is checked, an attachment reference will be created for the related activities in SAP. Such new activity attachments will be automatically transferred to SAP FSM, if not blocked by the outbound configuration (e.g. setting ‘block out’ in the General configuration).

See: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/842661889

Example process

 Click to expand the example

Make sure that the ‘Link SAP Atta. of Notification to Acti’ field is enabled.

Create a new service notification and a related service order, so that an activity is generated.

Create an attachment of any relevant type (GOS/BDS/DMS) for the notification. In the example below it is a DMS attachment, created with transaction CV01N. Add the notification number as an object link.

Add an original file. Make sure to check it in. Save the document.

Open the document with transaction CV03N and notice that another object link - referring to the related activity - was added.

The new activity attachment will be transferred to SAP FSM.

Attachments added to a service notification task in SAP ECC/S4 will be linked also to the activity created based on that task (integration scenario where notifications are used as service calls and their tasks as activities). The solution applies to GOS and BDS attachments (object type QMSM).

Enable inheriting equipment’s attachments by activities (after adding an attachment to equipment) if the equipment is assigned to the activity (field ‘Equipment’ in table /PACG/ECM_ACTI).

The equipment can also be added to the service order operation related to the activity or the header of the service order related to the activity.  

Attachments will be added to all open activities - if the configuration field is set and an activity or its reference object has the same equipment as the one to which an attachment was added. The logic is executed in Equipment event after attachment creation in SAP ECC/S4. The solution works with GOS, BDS and DMS attachments. 

Example 

 Click to expand the example

Check the ‘Link SAP Attachments form Equipment to Activity’ field for the test company. 

Notice that the test equipment 10010859 is assigned to 2 activities (directly on activity level):

 

Create a GOS attachment for the test equipment in transaction IE02:

 

Outbound attachment idocs should be generated for both EQUIPMENT and ACTIVITY objects – the ones to which the equipment is assigned.

 

Navigate to SAP FSM and notice that the equipment’s attachment can be found on both, activity and equipment level.

Attachments added to functional location in SAP ECC/S4 will be inherited by activities using this functional location ('Funct loc' in table /PACG/ECM_ACTI).

Example - GOS attachments added to functional location are inherited by existing activities using the functional location, as well as activities created later

 Click to expand the example

Add a GOS attachment to a functional location in transaction IL02:

Attachment reference is added also to the activity using the functional location:

The activity attachment is sent to SAP FSM:

Create a new operation using the functional location:

The attachment is inherited by the new activity and sent to SAP FSM:

Attachments added in SAP FSM with reference to activity will be added in SAP ECC/S4 as attachments to both the activity itself and its related service order.

Example process

 Click to expand the example

Add an attachment to an activity in SAP FSM.

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 level in SAP ECC/S4.

The attachment is resent to SAP FSM with reference to the service call and can be found on the service call level.

Attachments added in SAP FSM with reference to activity will be added in SAP ECC/S4 as attachments to both the activity itself and its related notification.

Example process

 Click to expand the example

Add an attachment to an activity in SAP FSM.

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.

Attachments added to a service notification task-based activity in SAP FSM will be linked also to the related notification task in SAP ECC/S4 (integration scenario where notifications are used as service calls and their tasks as activities). The solution applies to GOS and BDS storage methods.

Attachments added in SAP FSM with reference to activity will be added in SAP ECC/S4 as attachments to both the activity itself and the pointed equipment.

Equipment is primarily searched in table /PACG/ECM_ACTI for a given activity but it will be overwritten by BAdI implementation. Equipment is determined based on implementation of BAdI https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1466761219/BAdI+definitions#I_GET_EQUI_FOR_REFERENCE. The provided implementation’s logic is the following: create an additional attachment reference for equipment whose serial number can be found in the first (out of 3 or more) segment of the attachment’s name:

You can create your own BAdI implementation or disable the existing one, which will result in the equipment being determined solely based on assignment to the activity in table /PACG/ECM_ACTI.

Example

 Click to expand the example

Add an attachment to an activity in SAP FSM.

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

The attachment will also be available from the equipment’s level in SAP ECC/S4 - equipment related to the serial number from the attachment’s description.

Attachments added in SAP FSM with reference to activity will be added in SAP ECC/S4 as attachments to both the activity itself and its assigned functional location.

Functional location is searched in table /PACG/ECM_ACTI.

Example - attachments added to an activity in SAP FSM are added as GOS attachments to the assigned functional location

 Click to expand the example

Functional location is added as equipment to an activity:

Storage type for inbound attachments set as ‘GOS’ in transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/842661889 :

Create a new attachment for the activity in SAP FSM:

The new GOS attachment can be found in SAP ECC/S4, in the functional location’s attachment list:

The attachment inherited by the fuctional location is then sent to SAP FSM and can be found in the functional location’s master data:

Attachments added to activities in FSM and saved as DMS will be linked also to the related maintenance order operation.

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1624211457/DMS+attachments+added+to+maintenance+orders+SAP+S4+only#Creation-in-FSM.1

Make sure to execute the setup program before so that the following entry is created in /PACG/ECM_CUST_ATTA:

Link attachment from MSO activity in FSM to the header of MSO in Fiori app. Learn more: Advanced Execution Service Order - Attachments

Link attachment from MSO activity in FSM to the Service Order Item which is inside of MSO order in Fiori app. Learn more: Advanced Execution Service Order - Attachments