...
Category | Feature description | ||
|---|---|---|---|
Activities | Activities' addresses handling In the FSM planning board it is now possible, with the preview mode enabled, to use a new modal UI. One of the functionalities it offers is the possibility of changing the addresses in the activities including an option of defining completely new address. The newest Connector delivers corresponding functionality which lets supporting of these changes in the backend SAP system. New properties added to activity object Activity object was extended with two fields: LATESTSTARTDATE and LATESTSTARTTIME. Because there are no SAP standard equivalents fields can be filled by a BAdI and content can be seen in /PACG/ECM_ACTI_VC03 transactions Operation’s deletion in service order After deletion of an operation in a service order in the backend SAP system, corresponding activity is being closed and certain follow up action can be configured. Changes in operations' texts handling Configuration option ‘Operation text' was removed in /PACG/ECM_SCTD and new option was introduced instead ‘Orders' header long text to acti remarks’. This option controls propagation of service order’s header text to activities Reopen after TECO This is functionality implemented once for sales activities and now can be used with FSM activities. If TECO is set in service order all related activities are being closed. If this option is enabled and TECO is reverted closed activities will be reopened for further processing Learn more: /PACG/ECM_SCSTD - Status of Service Call, field ReopenAfterTECO. | ||
Activity feedback codes | Activity Feedback The activity feedback codes functionality has been extended. Users are able to use FSM object activity codes and activity composed codes for SAP catalogs. In order to use this functionality tables /PACG/ECM_SERCC - Service error composed codes and /PACG/ECM_SERCCT - Service error composed codes - Texts need to be filled with data. It can be done by using a new report /PACG/ECM_LOADSERCC - Load Service Error Codes (ACC) . Please note that if you used activity codes in the past, you need to delete all activity codes before using activity codes with activity composed codes. | ||
Attachments | Activities' attachments to Equipment New BAdI definition that lets users link attachment added to activities with equipment determined based on some custom logic. By default, if relevant option is enabled, activities' attachments are linked with equipment linked with current activity Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135497/PACG/+ECM_+ACTIVE – +General+Properties+of+E4C+Activity#Link-FSM-Attachments-from-Activity-to-Equipment and https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1466761219/BAdI+definitions#I_GET_EQUI_FOR_REFERENCE Activities' attachments to Functional location Analogically to the logic applied to equipment, if instead of equipment functional location is used additional references will be created if relevant customizing is enabled Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37135497/PACG/+ECM_+ACTIVE – +General+Properties+of+E4C+Activity#Link-SAP-Attachments-of-Functional-location-to-Activity | ||
Contact Person | Contact person integration with FSM New Connector SP3 brings full integration between Contact Persons and FSM. Contact persons created in FSM will now be created in SAP backend system and Connector can support both standard solution: ‘Customer’ related contact person and ‘Business Partner’ related contact person. | ||
Contracts | Contracts deletion Missing bit of contracts' integration is brought by SP3. Now when contract is deleted in transaction VA42 the deletion request will also be sent to FSM | ||
Equipment | Tools configuration The configuration transaction /PACG/ECM_EQ1 - Equipment Settings was extended with options dedicated to tools only | ||
Logs | Error logs viewer By default Connector uses standard SAP logging solution which is BALLOG but the transaction SLG1 used for browsing and viewing logs has its limitations. This is why with the new service pack alternative, custom solution is introduced. If you want to learn more, check /PACG/ECM_LOG_VIEWER - FSM Error Log Viewer
| ||
Mileages | Do not create cost documents for mileages without distance If no distance is entered for a mileage on the mobile app (e.g. because this field is purposely hidden), a direct activity allocation document cannot be created in SAP. By default, further processing would be stopped and CATS/confirmation couldn't be created either. Now posting of CO documents can be skipped. If a new option is enabled, mileages with missing distance do not run into an error. No cost document is posted but if CATS or confirmations are activated for mileages, such documents are created. Learn more: /PACG/ECM_MLGG – Mileage – General Settings | ||
Payment terms and methods | Object filtering In older releases the FSM Connector was sending to FSM all existing payment terms and all payment methods. This was causing loads of unnecessary data being transferred. There are new configuration transactions added which let users build filters on payment term and methods and send them selectively. | ||
Purchase orders | FSM Crowd and Purchase Orders Purchase orders created in FSM are now integrated with backend SAP system. Purchase orders created by FSM (CROWD or mobile apps) can now be sent to the Connector and corresponding objects will be created there. The integration includes also automation based on related activities. Depending on the activity’s status purchase order can be either released or confirmed or even deleted and even purchase requisition can be created and converted into purchase order. If you want to learn more, check Integration of the Crowd with purchase orders | ||
PS integration | The second approach to PS integration with SAP FSM - WBS elements can be used as FSM service calls and activities The first approach to integration of FSM with SAP Project Systems was introduced in the previous FSM Cloud Connector versions. In that approach, network orders and network activities can be used as FSM service calls and activities. The new service pack introduces the second approach to PS integration - WBS elements can be used as FSM service calls or activities (depending on the WBS project type). The integration currently supports:
Get better insight into the integration’s scope: WBS element integration
| ||
Reserved materials | New properties added to reserved material object Reserved material (RESERVEDMATERIAL) object was extended with new fields ARRIVAL and TRACKPART. Because there are no SAP standard equivalents fields can be filled by a BAdI. Consider ‘Reservation Relevance’ standard option when creating reservations New Connector delivers enhanced logic of sending Reserved Materials relying on SAP standard option ‘Reservation Relevance’. In the transaction /PACG/ECM_SCTD configuration ‘Do not send R RMat’ was extended with new selection option ‘Avoid sending of 'R' RMats with Res./Purc. req set as Never’ so if this option is selected and ‘Reservation Relevance’ is set to NEVER then reserved material will not be sent to FSM | ||
Skills | Enable 'Dummy booking' for inbound SKILL objects 'Dummy booking' for inbound messages means that a confirmation will be sent to SAP FSM to unblock an object, but no additional processing (e.g. saving this object in SAP ECC/S4) will take place. Now this functionality is available also for inbound Skill objects. Learn more: /PACG/ECM_CLSASSIGIN - FSM Connector's Incoming Messages Configuration | ||
Time efforts | Time effort update from FSM In theory it is not possible to update synced time efforts in FSM. However in practice it is still can be doable with business rules. Before SP3 such inbound time efforts were simply considered as incorrect and left in the error state. This in turn resulted in parent object being blocked as well. With SP3 this logic in Connector was enhanced and in case of an update of the time effort objects content is compared to what was received before and if this hasn’t changed confirmation is sent to FSM. However if there was a change then error is raised and Idoc ends uprocessed If you want to learn more, check Time efforts updated in SAP FSM | ||
Administration & Configuration | Connector uninstallation Connector’s Setup program creates number of entries in the system tables, Idoc related entries, events definitions, ballog config just to name a few. In this release Connector brings /PACG/ECM_UNINSTALL. This tool simply reverse changes introduced by the Setup. Change of logical system without transport New transaction /PACG/ECM_COMPL - Logical system for company was added - this lets define logical system for company without creation of transport which means it can be changed in each system independently ‘No workflow’ config option was obsoleted If this option was disabled (unchecked) in /PACG/ECM_CPROP, if an error occurred when sending documents from backend to FSM a special ‘Error workflow’ was being triggered. By default this option was set to true disabling the workflow on error. In addition disabling the option could led to performance issues therefore eventually it was decided that it should be removed. Extension of the Queue Email Alert generation program An Email Alert can be sent to responsible persons when FSM queues stop working/are not active. The program retrieves existing queues and checks if their names/statuses match the selection criteria. Queue statuses taken into consideration used to be hardcoded. Now, the user can add any additional queue status to the list. The most common statuses can be selected using checkbox parameters. Learn more: /PACG/ECM_QSTATUS - Email queue issues Setting default values In transactions /PACG/ECM_SAASG, /PACG/ECM_PLAS, /PACG/ECM_PAAS and /PACG/ECM_EKAS where it is necessary to select default entries program does not allow setting more defaults than one for related entries |
...