PACG 200 SP 1 / S4PACG 200 SP 1

Attachment’s handling 

Additional improvements of modernized attachment handling: 

• copy or remove entire configuration nodes and sub-nodes 

• customize inbound attachments of a specific file/object type to not be stored in SAP 

• activities can inherit attachments from the assigned equipment 

• refined linkages between Notifications’, Service Orders’ and Activities’ attachments 

• enhanced BAdI methods and interfaces 

Learn more: /PACG/ECM_CUST_ATTA - Inbound/Outbound Attachment Configuration

Checklists  

• Prefilling of the picker element in the checklists sent from SAP to SAP FSM  

• Fill outbound checklists with data using configurable mapping and build a set of rules based on which checklist can be assigned to an activity 

Learn more: /PACG/ECM_CL_PREF - Checklist prefilling configuration

Workflow step-related checkout  

Perform checkout of activities based on freely selected workflow step.

Learn more: Service Checkout on various steps of workflow

Equipment  

• Create and update equipment and functional locations based on inbound data from SAP FSM (this solution is a response to the changes implemented in SAP FSM).  

• Equipment, Functional location or Ibase materials objects are all transferred to SAP FSM as Equipment. There used to be no way to clearly distinguish them. This has been solved by implementing a new property - objectCategory.  

SAP ECC/S4 → SAP FSM 

Equipment objects transferred to SAP FSM contain category information, which provides clear distinction between Equipment and Functional Location. 

SAP FSM → SAP ECC/S4 

Equipment objects created in SAP FSM will be handled differently in SAP ECC/S4, depending on their category: 

• create Equipment for objects with category 'Equipment' 

• create a Functional Location for objects with category 'Functional location'  

• other categories can be handled by a BAdI implementation  

Teams 

• Teams’ descriptions can be edited using the FSM Cloud Connector maintenance transaction. 

• Validation for unique team names within one company 

Service order/Activities 

Filter service orders and operations relevant for integrations based on work center. It will be possible to define an exclusion list of work centers and if a work center added to the service order header or its operation is listed, such an order won’t be sent to SAP FSM (likewise, an activity won’t be created).   

Learn more: /PACG/ECM_SCTD_WCE - Workcenter exclusion/inclusion for service calls

Work schedule 

Reimplementation of work schedules integration: 

• Use periodic work schedules instead of entire holiday calendars 

• Work Schedule can be generated for different periods 

• Include lunch break in worktime pattern (multiple time ranges within work day) 

Holiday calendars  

Additional improvements for the holiday calendar integration feature:  

• Transfer holiday calendars and assignments based on personnel area: 

  • Specify which personnel areas are relevant for calendars in each company. Use these personnel areas to determine proper holiday calendars – based on assignment of holiday calendars to personnel subareas in transaction Define Groupings for the Public Holiday Calendar 

  • Determine which users will be transferred as holiday calendar assignments based on employees’ personnel subareas (infotype 0001)  

• Support for weekday-dependent holidays 

• Transfer calendar assignments automatically, during employee transfer 

Learn more: Calendar integration

Materials 

• Additional ways of determining if a transferred item is serialized – use non-default or delivering plants  

Learn more: /PACG/ECM_ICONF - Item Configuration

• New fields can be transferred within outbound item objects: PROPERTY, EAN, ITEMURLS.

• Extended customizing for the ‘REMARKS’ field – use sales text, basic data text or do not send item remarks. 

User maintenance  

• After record's deletion in user maintenance transactions /PACG/ECM_MAINT_USER and in /PACG/ECM/ALV_USERS soft deletion is being sent instead of hard deletion. Hard deletion was not reversible by re-uploading the user and resulted in assigning user with a new ID. As a result, all history data related to the previous user ID was lost. In case when the soft deletion flag is in use, then the record is re-created with the previous user ID and relevant user history data is maintained. 

Learn more: /PACG/ECM_MAINT_USER - FSM users

Other 

• A new report for deletion of closed activities and checklists instances from SAP FSM, if they are closed since the specified number of days. 

Learn more: /PACG/ECM_DEL_OLD_AC - Delete old activities & smartformsarchived

• To avoid blocking FSM Cloud Connector ↔ SAP FSM communication, handling of unknown objects has been implemented. When FSM Cloud Connector receives not supported objects, an error message is sent back to SAP FSM. This will cause SAP FSM to not send the same objects again. 

Learn more: /PACG/ECM_CLSASSIGIN - FSM Connector's Incoming Messages Configuration