To be released soon. The FSM Cloud Connector component was released on 5th December 2022
| Info |
|---|
Download here: |
| Info |
|---|
FSM Cloud Connector release PACG 200/S4PACG 200 SP7 aligns with SAP FSM release 2211 |
| Table of Contents | ||||
|---|---|---|---|---|
|
Post-installation steps
Run /PACG/ECM_SETUP
Change Log (SAP NOTE 3278295)
Category | Feature description | ||
|---|---|---|---|
Attachments | Persons' attachments With its latest release the FSM Connector is now capable of handling the attachments added to a person – both in the FSM and in the backed ERP system Overwrite BDS customising There was a BAdI added that lets implementing customers' extension which allows using different document types for BDS attachments than it results from the configuration. 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 and/or 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 There has been a A new report added to FSM Connector. It can recognized contracts which can recognize contracts whose validity date has passed and as a response send relevant updates contract status update to FSM Learn more: Update contract status if the end date termination date is reached | ||
Equipment/Functional Location | Get partners for Equipment and Functional Location from the parent object A new configuration option added - when selected, when sending during master data transfer, business partner is determined from the parent objects in the hierarchy Learn more: /PACG/ECM_EQ1 - Equipment Settings, field ‘Partner source’ | ||
FSM Connector (general) | Report correcting the entries in the table BELHDR (follow up to SAP Note 3206242) There is a 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 From Fields enabling DMS and BDS attachments got removed from transaction /PACG/ECM_CPROP controls enabling DMS and BDS attachments got removed. They were obsolete since attachments control was moved to /PACG/ECM_CUST_ATTA transactions 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 was created and it ) is used to control who can send objects' deletion requests to FSM. Learn more: Authorization objects | ||
Message Broker | Automatic generation of the message broker config file This new tool lets allows users build and generate message broker config file in an easy and user-friendly way Learn more: /PACG/ECM_MBCF_GEN - Message Broker Configuration File Generator | ||
Performance | Sending reserved materials to FSM Customize FSM Connector sends from now on to send reserved material and batches from reserved material only if the service order operation is dispatchedSupress . Learn more: /PACG/ECM_SCTDM – Movements for service order type Overview and Detail, field ‘ReservedDisp’ Suppress ASA event when processing inbound final confirmation.Starting with the new FSM Connector, when When processing inbound final confirmations, the ASA event has been supressed 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 Personal Properties of personal reservations' properties which do have match in standard ERP created in FSM will be held stored in a dedicated Connector’s tabled table to avoid them being overwritten during updateoverwriting 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 can now be are stored as an infotype 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 orderWith new FSM Connector it is now also possible to maintain equipment on the operations level with the standard ERP functionality ‘Assignment of Operations to all object list entries active’ enabled 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 add , 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 are displayed 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 With the new Connector version if If a user is assigned to more than one work centres than one all will be sent to FSM as regions | UDF | New option in UDF Definition , 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 |