The FSM Cloud Connector component was released on 5th December 2022
FSM Cloud Connector release PACG 200/S4PACG 200 SP7 aligns with SAP FSM release 2211
Post-installation steps
Run /PACG/ECM_SETUP
Change Log (SAP NOTE 3278295)
Category | Feature description |
|---|---|
Attachments | Persons' attachments GOS/BDS attachments added to employees (transaction PA30) will be automatically transferred to FSM and displayed in FSM master data - on Person level, under the tab ‘Attachments’. Attachments added in FSM master data for a Person under the tab ‘Attachments’ or ‘Personal information’ can be saved as GOS/BDS attachments in SAP ECC/S4 (to be displayed via PA30 → 'Attachment List'). Overwrite BDS customising A new BAdI can be used to store BDS attachments with a document type different from the one resulting from the configuration. Automatic population of attachments added to Service Call in FSM to activities should be optional From now on, it is possible to disable automatic population of attachments added to service calls to the related activities/notifications. Learn more: /PACG/ECM_SCTD – Service Call types definition: Overview and Detail, fields ‘Cpy.Att.To.Notif’ and ‘Cpy.Att.To.Acti’ |
Contracts | Update contract status if the end date or termination date is reached A new report can recognize contracts whose validity date has passed and as a response send relevant contract status update to FSM Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1774649345 |
Equipment/Functional Location | Get partners for Equipment and Functional Location from the parent object A new configuration option added - when selected, during master data transfer, business partner is determined from the parent objects in the hierarchy Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953646, field ‘Partner source’ |
FSM Connector (general) | Report correcting the entries in the table BELHDR (follow up to SAP Note 3206242) A new report added to Connector’s toolset (folder 'Administration') which can fix entries in BELHDR table (application logs), which cannot be removed otherwise. Changes in FSM Connector General Properties - transaction /PACG/ECM_CPROP Fields enabling DMS and BDS attachments got removed from transaction /PACG/ECM_CPROP. They were obsolete since attachments control was moved to /PACG/ECM_CUST_ATTA transaction. Also, the control field enabling FSM Activities ('FSM activity') got removed since this is the only solution and disabling them may lead to inconsistencies. Sending deletion requests requires an authorization A new authorization object (/PACG/E010) is used to control who can send objects' deletion requests to FSM. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1702854657 |
Message Broker | Automatic generation of the message broker config file This new tool allows users build and generate message broker config file in an easy and user-friendly way Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1802272856 |
Performance | Sending reserved materials to FSM Customize FSM Connector to send reserved material and batches only if the service order operation is dispatched. Learn more: /PACG/ECM_SCTDM – Movements for service order type Overview and Detail, field ‘ReservedDisp’ Suppress ASA event when processing inbound final confirmation When processing inbound final confirmations, the ASA event is suppressed and not triggered anymore. This in tuned improved significantly the entire operation, especially in case of orders having a huge number of assigned activities |
Personal reservations | Store inbound person reservation properties in SAP ECC/S4 to avoid overwriting them Properties of personal reservations' created in FSM will be stored in a dedicated table to avoid overwriting them after synchronization with the backend. This includes e.g. fixed technician or exclusive reservation properties which do not have any matching property in SAP ECC/S4. Store/retrieve descriptions for person reservations saved as HR absences Personal reservations' remarks are stored as Absence infotype’s long text. This allows accessing them in SAP and prevents losing them after synchronization with the backend. |
Service Order | Maintain equipment on the operation via Assignment functionality on the Object tab in the service order When equipment is maintained in SAP ECC/S4 via Object assignment, equipment added to activities in FSM/inherited from copied activities will be properly populated to the operation. In order to create an object with link to the operation, make sure to select ‘Create object’ in field ‘Change equi’ of transaction /PACG/ECM_SCTD. Learn more: /PACG/ECM_SCTD – Service Call types definition: Overview and Detail, field ‘Change equi’ |
Transactions | List of new transactions:
|
Users/Employees | In FSM Users' maintenance reports, additional info about user name or personal number is added Now in users maintenance transactions (/PACG/ECM_ALV_USERS - Mass User Maintenance/ /PACG/ECM_MAINT_USER - FSM users), both employee personnel number and user name are displayed for each defined FSM person (only when corresponding objects exist). In addition, both of them work as links to the related transactions SU01 in case of user and PA30 in case of employee In the transaction /PACG/ECM_USERG allow using other email sources than 4 predefined ones It is now possible to use other subtypes of infotype 0105 than the four predefined values as the source of email address for the users Learn more: /PACG/ECM_USERG – User – General Settings, field ‘Email src’ Multiple work centers assigned to a person sent as a region If a user is assigned to more than one work centres, all of them can be displayed as technician’s regions. In the past a technician could have only one region assigned. Learn more: /PACG/ECM_P_GR - Group object for technicians, field ‘Multiple regions’ |
UDF | Transfer UDF definitions directly in the UDF configuration transaction UDF definition transaction has now the option that allows sending UDFs definition to FSM based on selected items |