...
The FSM Cloud Connector component was released on 2702.0509.2024.
Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Download here: |
Info |
---|
FSM Cloud Connector release PACG 200/S4PACG 200 SP13 SP14 aligns with SAP FSM release 2405 |
⚠️ Important info
Following transactions are now considered as obsoleted (SAP Note)
2408 |
Post-installation steps
1. Notes' installation
Check notes and install relevant ones
2. Run /PACG/ECM_
...
SETUP
3. Adjust selection and IDOC classesfor the /PACG/ECM
...
...
...
...
Change of the tables' keys definitions and reorder of fields for the following customizing tables:
/PACG/ECM_SCPGF
/PACG/ECM_NOPGF
Changes are following:
- Field ‘HIGH’ is no longer part of the key
- Fields SIGN and OPTI are included in the key
- Field HIGH changed its positions in the structure
OLD | NEW |
---|---|
This change may result in data loss in case if duplicated keys appeared after change - SAP automatically removes duplicated entries
⚠️ Post-installation steps
1. Adjust event settings in transaction SWETYPV (client dependent):
Deactivate event CHANGED for object BUS2012
Deactivate event CREATED for object BUS2012
...
2. Notes' installation
Install SAP NOTE 3473399 (High priority for new installations, due to an error fullsync process can be impacted)
Check other notes and install relevant ones
3. Run /PACG/ECM_SETUP
Change Log (SAP NOTE 3484470)
...
Category
...
Feature description
...
Time Effort
...
Improved rounding for time splits with breaks
Calculation of time splits for CATS entries based on time efforts with breaks used to have rounding issues: the system would convert times into floating-point values and subsequently round them to the second decimal place. When two values would have ‘5’ (or above) as their third decimal, the system would round both values up. This would lead to the situation where the sum of reported time would be higher than the actual work time. To avoid such issues, the Connector now identifies rounding problems and shifts the break time by one second.
...
Checklists
Prefill checklist instances with order/notification partners data
...
_SERVICECALL_STATUS object inhttps://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952719
Idoc class /PACG/ECM_CL_S_IDOC_O_SCALLST2
Selection class /PACG/ECM_CL_S_SEL_SCALLSTATU2
Change Log (SAP NOTE 3511512)
Category | Feature description |
Business partners | Multiple addresses for business partner This feature is fully supported in the systems using central business partners management (BP). From now on, Connector can correctly handle any number of address added in FSM to a single business partner. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/2309259265 Deactivate expired contact persons Expired contact persons can now be synced with FSM. Such contacts after validating their relevancy are sent as inactive. This helps keep customers' information in both systems consistent. |
Equipment | Relocation of the ‘MAX EQUI’ parameter Due to introduction of a new param controlling number of equipment sent with service call, the param controlling number of equipment sent with subhierarchy was moved to /PACG/ECM_EQ1 configuration transaction |
Service orders | Redesign of the service call status customizing The latest Connector release delivers new version of /PACG/ECM_SCSTD transaction. Although its layout has not change its functionality was reimplemented in such a way that it’s easier to use and less error prone. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135809 Control the number of equipment sent with service call In addition to the existing parameter which can limit the number of equipment sent with subhierarchies this SP brings another one - a parameter that can limit the number of equipment sent with a service call Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/ |
Suppress sending of empty checklist
In one of the previous FSM Cloud Connector releases, sending of checklists' assignments was replaced with sending empty checklists. In certain circumstances, sending of empty checklists should be suppressed regardless of other conditions. To allow this, an additional option was introduced - when enabled, empty checklists will not be sent, unconditionally.Administration & Monitoring | Change layout of /PACG/ECM_CPROP To improve usability and intelligibility of the basic settings of FSM Connector we have entirely redesigned the /PACG/CPROP transaction Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/ |
Network orders
Update of duration
Analogously to the already existing implementation for WBS and CS orders, also in case of network orders the DURATION and PLANNEDDURATION will be set by Connector during FSM Activity creation.
Service orders
Support for cancellation of operation deletion
When operation deletion is cancelled, a new open activity is created to allow continuing work on a given task.
Learn more: Operation deletion and its impact on activities
Administration & Monitoring
Retention Policy events handling
Handling of deletion requests generated by FSM due to the application of the Retention Policy.
Logging in FM /PACG/ECM_S_PORT
Logging in FM /PACG/ECM_S_PORT was enhanced in order to provide all possible details in case of an error.
UDF Maintenance
‘UDF Subtype’ property is from now visible only for the relevant UDF typesEnhancements in /PACG/ECM_ALV_USERS Transaction /PACG/ECM_ALV_USERS is now capable to show the personal area to which FSM users are assigned to. More over, it is also possible to search users based on their assignment to personal area. Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/975601806 New feature of FSM Cockpit The FSM Cockpit can now show information about the actual size of Connector related data tables. This information is update by dedicated report which can be executed on demand or scheduled as a background job | |
FSM Activities | Optional sending of activities with service order In SP09 we disabled unconditional sending of all activities triggered from the selection class of service call. It turned out however that on rare occasions such a process is required by therefore from now on it can be enabled by a dedicated option Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/ |
Prioritize access to customers' sales areas
Determination of sales area assignment for the Customers is now based on ordered list. Using this list, the Connector looks for the first matching sales area definition (in customer’s master data) instead of trying to look only for sales area defined as a default.
Fullsync progress
In addition to information about ongoing fullsync, FSM Cockpit provides information on the process's progress.
_CPROP+-+General+Properties+of+FSM+Cloud+Connector#Send-activities-with-Service-Order Suboperations reflected as hierarchy in FSM By default, for each pair operation and suboperation Connector creates independent activity. In this release we have implemented a feature which can modify Connector’s behaviour and when enabled, for a pair operation and suboperation it creates activity and a follow-up activity (former suboperation) Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/ |
Reserved materials
Delivery date for reserved materials after goods movement
Arrival date used to be displayed only for reserved materials before goods issue for delivery. However, the time between goods movement and arrival to the customer can take longer. Now the delivery date is also determined for reserved materials after goods movement for delivery (support for ‘SD’ scenario)E4C+Activity#Suboperation-activities-as-follow-up-act Region update on technician’s reassignment From now on, when an activity is reassigned to a technician belonging to a different work centre than the initial one, and the region determination is based on the operation’s work centre, the Connector will update the activity’s region assignment accordingly. Learn more: https:/ |
Authorization Objects
New Roles:
proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37136514 Work centre update in network orders For updated activities created in reference to network orders, like in case of CS order, Connector is capable of the redetermination of valid work centre (for instance in case of technicians reassignment) | |
UDF | Enhancements for the UDF building program The report /PACG/ECM_ |
UDFG_UDF gained two additional features and lost one functionality. The report can now create and send UDF definitions to multiple companies at once. Then, it can now also display the list of generated UDFs. And the thing it cannot do anymore is sending of deletion requests - for this there are dedicated tools in the Connector Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/ |
Obsoleted transactions
Transaction removed from Connector’s menu (but not from Connector):
Performance | Save Purchase Order The even triggered on the save of the purchase orders is no longer mainteined in the SWEC transaction and instead is called by ABAP method. This way number of triggered events can be limited to those which are FSM relevant Enhancement of IDoc generator for Equipment In the IDoc generator class for equipment (and functional locations) the superfluous updates of DB tables was suppressed - this should improve overall processing. Processing if incoming activities For incoming activities the process of (re)determination valid work centres was reimplemented and simplified in a way that information can be used by related objects limiting the number of DB queries |
Authorization Objects |
|
New transactions |
|
| |
Obsolete transactions |
|
|
|