FSM Cloud Connector component released on 30th November 2021
FSM Cloud Connector release PACG 200/S4PACG 200 SP3 aligns with SAP FSM release 2111
Post-installation steps
Install SAP NOTE 3125347 - Object not recognized during idoc processing ending with /PACG/ECMX object type
Run /PACG/ECM_SETUP
In transaction /PACG/ECM_ACTIVE check if all the settings related to setting up the references between activities' attachments meet your requirements
New features
Category | Feature description |
|---|---|
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 Please note that this integration approach is in its beta version. It contains most of the major features but is not considered fully production-ready. We release it to collect further feedback and will be happy to adjust it to your needs as part of a joint integration project. |
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. |
Purchase orders | FSM Crowd and Purchase Orders FSM Crowd gives now possibility of purchase orders' creation. Purchase orders created by FSM can now be sent to the Connector and corresponding objects will be created in the backend as well. 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 |
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 Connector’s own logging mechanism should be considered as a beta release and we would appreciate your feedback and comments |
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 |
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 |
Reserved materials | |
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 |
Expenses | |
Administration | 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. |
Performance |