PACG 200 SP 11 / S4PACG 200 SP 11
- proaxia
- proaxia
The FSM Cloud Connector component was released on 4th of December 2023
FSM Cloud Connector release PACG 200/S4PACG 200 SP11 aligns with SAP FSM release 2311
Post-installation steps
NEW INSTALLATIONS & UPGRADE
Install SAP notes. The list of available notes can be found here.
Run /PACG/ECM_SETUP
UPGRADE ONLY TO (S4)PACG 200 SP11
If you used the functionality of Reservations created based on CATS entries, please execute the migration program.
Due to significant enhancements in the area of CATS and Person Reservation integration, the structure of the key of CATS-based reservations' objects were entirely redesigned.Classes /PACG/ECM_CL_S_IDOC_I_WORKTIME and /PACG/ECM_CL_S_IDOC_I_TIMEEFF were refactored and, in a large extent, rewritten to the new classes /PACG/ECM_CL_S_IDOC_I_WORKTIM1 and /PACG/ECM_CL_S_IDOC_I_TIMEEFF1.
The old classes can still be used however it is recommended to adjust customising in /PACG/ECM_CLSASSIGIN - FSM Connector's Incoming Messages Configuration
Change Log (SAP NOTE 3407001)
Category | Feature description |
|---|---|
Service calls | Inclusion of FSM-related Work Centres The customizing Service call type workcenter exclusionice calls assigned to them on header o allows to specify which work centers are not relevant for FSM. Servr operation level will not be transferred to FSM. For various customers, with more complex organization structure, it made more sense to INCLUDE the allowed work centers instead of EXLUDING the ones not allowed. Such a possibility was implemented in the latest service pack, significantly reducing the potential customizing maintenance effort. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1203273736
Customer no more obligatory Service orders/network orders/notifications/WBS elements without customers can be transferred to FSM. Activities for such service calls will be successfully created and transferred as well. This means that the partner function entered in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/2094727169/PACG+ECM+VSCTD+-+Service+Call+types+definition#Customer-role does not have to be maintained in service orders/network orders/notifications/WBS elements for a service call to be transferred to FSM.
Planning/cancel/unassigned statuses on header level Until now, it was possible to set a dedicated user status to an operation when the related activity’s state was changed (it was planned/cancelled/unassigned). With new Connector’s release we give users possibility to set these statuses on order’s header level. This feature is mainly addressed to customers who work with single-operation orders.
Planning groups-based filtering of service calls This functionality is analogous to the one of work centre exclusion/inclusion. Now users can optionally define which planning groups make an order relevant for transfer to a given FSM company. This functionality introduces better granularity of the selection of orders integrated with FSM.
Support for user name-based responsible partner function for service calls In the Service Call types definition customizing, users can define which service order partner function should be used to store the ‘person responsible’ of service calls. Since only personnel number-based partner functions used to be supported, users without personnel numbers couldn't be added as service call responsible. The newest FSM Cloud Connector service pack allows usage of user name-based partner functions - a service call responsible can be stored as a user name instead of a personnel number. |
Activities |
|
Equipment and functional location | UDF characteristics for functional locations Functional location characteristics can be transferred to FSM as UDF values and displayed in FSM master data. Update of a functional location characteristic in FSM results in update on the SAP ECC/S4 side. In the previous FSM Cloud Connector versions this functionality was supported only for equipment. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/314605599
Allow replacement of one equipment by multiple with consumption of a serialized material During consumption of a serialized material you could optionally decide to replace another equipment with the one represented by the consumed serial number, however the initial implementation would foresee only one serial material being consumed at once and hence it attempted to replace the ‘old’ equipment with only one ‘new’ equipment. The functionality has been extended – if multiple serial numbers are consumed at once, they will all replace the old quipment (more precisely, they will all be installed to the dismantled equipment’s super-equipment). Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1615921170
Functional locations’ plants reassignment With the new Connector service pack, we have introduced a functionality of functional locations reassignment. This feature has been implemented for equipment and is in use for some time already. If a functional location is reassigned from one plant to the other and both plants are relevant for different FSM companies, then in the ‘source’ company the functional location will be ‘softly’ deleted and accordingly undeleted/created in the destination one. This is a functional location-relevant equivalent of the functionality below: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/558006287
Performance of selection In the method ‘Send’ of the class /PACG/ECM_CL_S_SEL_EQUI redefined data types were used in order to save date while selecting big amounts of records from database into internal tables |
Items | Item dependency Until now the Item’s (Material) relevancy in relation to FSM has been based on the sales area assignment. This approach had one serious limitation – materials had to be assigned to at least one sales area defined as FSM relevant. In the latest service pack, Connector brings additional possibilities – from now on it becomes possible to define materials’ relevancy toward FSM based on their plants or define materials as ‘object independent’ so they will be simply transferred to selected companies. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952548
New config options in /PACG/ECM_ITYPE
|
Business Partners | Email address for contact person retrieved from relationship If Business Partners (transaction BP) are used on a system and relationships between customers and contact persons are maintained, the relationships can have their own email address. The email from relationship didn’t use to be retrieved at all – now it is retrieved first and has priority over the email from contact person's main data. Only if no relationship email is maintained would the main mail be used as contact person’s email in FSM. |
Users | Additional property added to the FSM Users maintenance In the list of users’ properties that can be controlled in the Connector a new one was added: loginable. When this option is disabled then corresponding user cannot login to FSM anymore (although they’re still active).
Users’ deletion In order to prevent additional deletion of FSM users several changes have been made.
Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1957691394
Users’ inactivation based on users’ roles in SAP If an FSM-relevant user role is unassigned from a user, the related FSM users are inactivated on company level only if no other role relevant for this company is assigned to them. Users are inactivated on account level only if they’re not assigned to any role relevant for any other of their companies. Additionally, whenever a user is deactivated on company level, the property ‘loginenabled’ is set to false for a given user in a given company.
Sending technicians as regular master data New option was added in /PACG/ECM_CPROP - ‘Per w/o FSMUser’ (Allow transfer of non-FSM-rel. employees (w/o access to FSM). With this option enables Connector will transfer all employee defined in HR (considering however all company assignments condition) regardless if given person has a corresponding FSM user defined |
Person Reservations | Store Person Reservations as CATS entries Person Reservations created in FSM can be reflected as CATS entries in SAP ECC/S4. The solution supports creation, update and deletion of single and multi-day reservations. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1966211165, https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/831848449/Automatic+transfer+of+CATS+entries+as+person+reservations |
Skills | Multiple skill sources for a user Skills’ source configuration got extended in the last Connector version. Before the change, there were only two options and a user had to decide which of them is used for the entire company. Now it gained additional flexibility – the user can select multiple sources for the skills and define priority/order in which they will be checked. Moreover, next to the existing sources, two new ones were added:
|
Regions | Region determination for notification-based activities A standard regions’ determination got implemented for activities based on notifications’ tasks. The solution is analogous to already existing one implemented for regular service orders and activities. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37136514 |
Time Efforts & Worktimes | BAdI /PACG/ECM_BREAK A new BAdI /PACG/ECM_BREAK was defined. With this BADdI customers can implement own logic for calculating actual time of technicians work and the breaks
Reimplementation of time effort and worktime handling class. Old classes /PACG/ECM_CL_S_IDOC_I_WORKTIME and /PACG/ECM_CL_S_IDOC_I_TIMEEFF got replaced by /PACG/ECM_CL_S_IDOC_I_WORKTIM1 and /PACG/ECM_CL_S_IDOC_I_TIMEEFF1 which are refactored and in large extent reimplemented versions of predecessors and from. /PACG/ECM_CL_S_IDOC_I_WORKTIME and /PACG/ECM_CL_S_IDOC_I_TIMEEFF are now considered as obsolete and will not be developed in future |
Checklists | Checklists' based notifications A functional gap was filled causing that when dropdown was in use, then instead of actual value of a field its index number was transferred. |
Administration and monitoring | FSM Cockpit enhancements - order/network/notification/WBS numbers Additional information was added to FSM Cockpit Idocs’ list. Wherever it is available, the Connector will display the number of an order (or network order/notification/WBS) and operation equivalent that the transferred object refers to.
FSM Cockpit enhancements – IDocs status change The list of Connector improvements got enriched by a new function added to the FSM Cockpit. From now on, with a single click it will be possible to change IDoc’s status. This report tool is analogous to standard RC1_IDOC_SET_STATUS but it got limited to Connector relevant object only with its own authorization object so it can used independently form the standard one
Express queue A new type of Connector’s queues was introduced in the latest service pack – so-called express queue. When it's enabled and objects are added to it then they’re processed with super-high priority. In terms of SAP queues this means that other Connector queues are immediately stopped and remain blocked until the express queue gets processed. Decision which objects are added to express queue depends on the individual needs and technically relies on BAdI that must be implemented.
Fullsync process
Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1699708945
New authorization objects
|
UX/UI improvements | Further improvements in the 'Copy company settings' and ‘Consistency check’ reports The ‘Copy company settings’ report gained a number of smaller improvements. Among them:
‘Copy to another company’ function added in the configuration transactions A dedicated option which allows easy copying of the configuration (it also covers mapping of data in the relevant cases) between companies was added to the following transactions:
|
Dictionary objects | Change of enhancement categories An enhancement category of a number of Connector’s tables and structures was not specified. This has been now updated and all these dictionary objects got relevant enhancement category assigned.
New Search helps New search help objects were created and added to relevant fields of the /PACG/ECM_SCTD:
Search help in /PACG/ECM_SASA Search help linked with the status field has not updated search help added - it allows user to filter statuses based on status profile |
New transactions | List of new transactions:
|
If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.