The FSM Cloud Connector component was released on 31st of August 2023
FSM Cloud Connector release PACG 200/S4PACG 200 SP10 aligns with SAP FSM release 2308
Post-installation steps
Install SAP notes. The list of available notes can be found here. Especially these should be considered:
Run /PACG/ECM_SETUP
Change Log (SAP NOTE 3370295)
Category | Feature description |
|---|---|
Activities | Cancel activities based on service order status Transaction /PACG/ECM_SCSTD - Status of Service Call allows to specify how service order’s status should affect the status of the related FSM activities, among the others it allows closing the activities. With the new release of Connector, it becomes possible to also CANCEL activities, making such activities disappear from the FSM planning board. Sales area assignment It is no longer required to define sales area assignments for the Activity object (/PACG/ECM_SAASG - Sales Area Assignment). From now on, the newly created activities will inherit sales area data from the parent object such as, for instance, service order (if such data exist). Reopening of closed activities The FSM Cloud Connector had the ability to reopen activities closed by setting the TECO status in an order - once this status was reverted. With the new release, it is possible to reopen activities after removing any system/user status (and not only TECO). Show related IDocs With the latest release a report showing IDocs for selected activity got enhanced - in addition to failed IDocs it can now show all IDocs related to it. Save of Activity object refactored Technical change focused mainly on the method /PACG/ECM_CL_A_E4CACTI->SAVE and subsequent methods and functions. The main change in this area was moving all database updated to FM /PACG/ECM_A_E4CACTI_DBUPDATE, in addition this function is now called in a foreground task and not as a update module. Remaining changes cover:
|
Customer/Contact person | Default contact person handling With the newest release FSM Connector became capable of default contact person handing. This is part of standard functionality of FSM but not ERP which was causing the information’s loss. This gap is now closed and Connector can now keep relevant data |
Equipment/Functional location | Measuring points and readings Further changes in the area of measuring points handling.
Learn more: Measuring points and measurements readings |
Service Order | Show related IDocs With the latest release a report showing IDocs for selected service order got enhanced - in addition to failed IDocs it can now show all IDocs related to it |
Reserved materials | Van stock functionality optional The reserved materials processing gained new option. It has now became possible to ‘disable’ van stock. This means that plant with selected storage location can be used also for SD/DC scenarios and warehouse owners are not required Linking sales data with reservations Table /PACG/ECM_RESBVB was extended with new fields: creation data and change date. This will help keeping consistent reference between service orders’ components and sales orders' data. In addition a report was created which can update these new fields based on historical data. |
Skills | Expired skills not transferred to FSM You can decide not to transfer skills whose ‘valid to’ date is in the past, compared to the system date. Qualification deletion in PPDPIM triggers skills' deletion from FSM Deletion of a qualification in transaction PPDPIM results in deletion of the related skill in FSM. Such a skill will no longer be visible in FSM master data for the affected technician. Learn more: Qualification deletion in SAP ECC/S4 |
Expenses | Selection of infotype for cost centre determination One of the expenses posting options is based on technicians' cost centres. Cost centre is derived from technicians' HR records. In the latest release this functionality got enhanced and will be possible from now on to decide on which infotype should be considered for determination. |
Mileage | Allow for posting mileage expenses without direct activity allocation Mileage distance can be posted as a direct activity allocation and optionally an expense (so-called mileage allowance). Until now it was not possible to post the second type of these two only. With new release, if no activity type is maintained in /PACG/ECM_MLGPRP for the relevant entry, an incoming mileage IDoc’s processing instead of being terminated with an error, gets processed and the expense (allowance) document is created. |
Time effort/Worktime | Time split table verification The time splits definitions can be very complex depending on business requirements. Their complexity, at the same time, makes them susceptible to error. With the latest release, the FSM Connector delivers a report which helps to verify the correctness of entered definitions. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137758/PACG+ECM+CSPLIT+-+Time+Effort+-+Time+Frames+for+Activity+Type#(S4)PACG-200-SP10-Consistency-check and https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137870/PACG+ECM+VWRKTC+-+Work+Time+Task+Definition#(S4)PACG-200-SP10-Consistency-check Split customizing with no source activity type With new release it is possible to define splits for worktime with source activity blank - such entries will be used as the default ones. Sum Duration Option When DuratSOpt (Sum Duration Option) is enabled, during time splitting previously recorded entries are considered. This however was applied to CATS entries. In this release the functionality has been enhanced and now also service orders' confirmations are taken into account Worktime update & deletion Work time deletion in FSM can be reflected in SAP ECC/S4. It can result in cancellation of the related SAP document. Learn more: Deletion and update of Work Time in FSM Cost centre determination With the newest release the cost centre determination works not only for CATS postings as it was till now but also for orders confirmations' |
Administration and monitoring | Copy company settings The ‘Company copy’ report was completely redesigned. A set of brand-new functionalities make it a more powerful and flexible tool - highly useful during FSM companies’ rollout. It now allows users to precisely control which customizing tables are copied and which are not, as well as to group tables relevant for copy into reusable sets, clear all customizing entries for a given company and much more. Learn more: /PACG/ECM_COPY_COMP2 - Copy/delete company settings Consistency check Together with the redesign and redevelopment of Companies’ copying report, we have also developed a dedicated tool which helps consultants to check and compare existing configuration between two companies. Learn more: /PACG/ECM_CONS_CHCK - Customising consistency check Copy assignments configuration Easily copy object assignment entries from one company to another. Use the assignment areas from the source company or specify which assignment areas from the source company should be copied into which areas in the target one. The functionality is implemented in the following configuration transactions: plant assignment, sales area assignment, purchase organization assignment, personnel area assignments and company code assignment. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952576/PACG+ECM+PLAS+-+Plant+Assignment#(S4)-PACG-200-SP10-Copy-to-another-company, https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952565/PACG+ECM+SAASG+-+Sales+Area+Assignment#(S4)-PACG-200-SP10-Copy-to-another-company, https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952598/PACG+ECM+EKAS+-+Purchasing+Organization+assignments#(S4)-PACG-200-SP10-Copy-to-another-company, https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952587/PACG+ECM+PAAS+-+Personnel+Area+assignments#(S4)-PACG-200-SP10-Copy-to-another-company Dummy booking
/PACG/ECM_RESTART_QUEUES The program /PACG/ECM_RESTART_QUEUES serves the purpose of restarting FSM Cloud Connector-related queues (name starting with ‘/PACG/ECM*’). Until now this program supported only outbound queues. With the latest release Inbound queues are also supported. Additionally, the program can react on two new queues statuses' RUNNING & WAITSTOP. Learn more: Restart queues via BG job (program /PACG/ECM_RESTART_QUEUES) Message broker failover When the Heartbeat report discovers that the primary message broker stopped functioning, next to switching to the secondary one it can now also send notification email to the indicated recipients. Learn more: Message Broker Failover - /PACG/ECM_HEARTBEAT Filling new Cockpit’s buffer tables New Cockpit introduced in previous release relies on its own dedicated tables which must be filled with relevant data, otherwise there is nothing report could show. In order to make this tool usable right from the beginning we have added dedicated report which can fill cockpit’s buffers with historical data Re-processing of outbound idocs It is possible that if transfer of an outbound idoc fails, in the period between the initial attempt of sending the IDoc and the attempt of resending it, a newer version of an object is created in FSM and synchronized to SAP. That means that resending of the previously failed IDOC may lead to a situation in which a newer version of the object will get overwritten by the older one. This can be avoided by using the new ‘Repeat’ option for failed outbound idocs in the FSM Connector Cockpit. New authorization objects
|
Performance | Use of bgRFC The newest FSM Connector delivers a new way of incoming objects' processing - next to online processing it become possible to use bgRFC. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952515/PACG+ECM+CPROP+-+General+Properties+of+FSM+Cloud+Connector#Incoming-confirmation and https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952515/PACG+ECM+CPROP+-+General+Properties+of+FSM+Cloud+Connector#Incoming-message |
UX improvements | Branches Obsolete property removed from customising The configuration transaction /PACG/ECM_MLGPRP contained two properties called ‘mileage type’. One of them was obsolete and not used by Connector. In this release this obsolete property was removed. The second ‘Mileage type’ option became ‘MlgTypeFromUDF’ to better describe its role. Activate split conf. in /PACG/ECM_SCTD directly from split configuration In order to make time splits in time effort and worktime processing works they must be enabled. Because splits' definition is handled by one transaction and switching them on and off by a different one we added a ‘functional bridge’ between these and from now on splits can be enables/disabled directly from the splits' maintenance transaction Learn more: /PACG/ECM_CSPLIT - Time Effort - Time Frames for Activity Type Sending reports' enhacements Following sending reports were enhanced - from now it became possible to select data based on creation date and/or change date (not always both dates are available in the system)
|
New transactions | List of new transactions:
|