FSM Cloud Connector component released on 8th March 2022
FSM Cloud Connector release PACG 200/S4PACG 200 SP4 aligns with SAP FSM release 2202
Post-installation steps
Run /PACG/ECM_SETUP
New features
Category | Feature description |
|---|---|
Activity | Add a work center determined for technician to an activity object Work center determined for technician during processing of inbound activity will be stored in activity record. Additionally new customising option was added in /PACG/ECM_STCD ‘Overwrite service order operation's work center’. It controls if technician’s work center should be populated to the operation Learn more here Extend activities' customizing - number range definition SAP gives possibility of defining multiple number ranges within single number range object. It is now also possible in the Connector to assign separate number ranges to the activities depending on the company they belong to. To learn more check /PACG/ECM_ACTIVE. Learn more here Technician unassignment in SAP It is and was possible to automatically release activity by assigning technician to an operation in SAP. It is also possible now to do opposite - unassign activity from planning board by removing technician in service order’s operation Learn more here |
Attachments | Screens for DMS checklist template/instance attachments DMS attachments for checklist instances and checklist templates are displayed using the screens delivered with FSM Cloud Connector. Learn more here Attachments for Business Partners (Customers/Suppliers) and Items Create/delete GOS/BDS/DMS attachments in SAP ECC/S4 or SAP FSM for Customers, Suppliers and Items. Make sure the BUSINESSPARTNER and ITEM entries are maintained as found here. Attachments for Customers/Vendors/Items should be enabled, as described here. DMS attachments added to maintenance orders (SAP S4 only) DMS attachments added to maintenance orders (S4 object PMAUFK) can be sent to FSM. Attachments added to a service call in FSM (created based on a maintenance order) can be stored as maintenance order attachments in SAP S4. On SAP ECC the object AFKO is used for both service and maintenance orders, on SAP S4 two separate objects exist and can now be used. Learn more here Customizing of effects of DMS/BDS attachment deletion from FSM Determine how deleting an attachment in SAP FSM (which is stored as a DMS attachment in SAP ECC/S4) should affect the related DMS files and object links in SAP. You can also determine how deleting an attachment should impact the entire DMS document. New configuration options for BDS attachments allow determining how deleting an attachment in SAP FSM (stored as BDS in SAP ECC/S4) should impact the files in SAP ECC/S4. Learn more here about DMS configuration fields ‘Deletion in FSM' and 'Delete DMS document’. For BDS configuration, learn more here. |
Customers | Contact deactivation should delete contact person record or end its validity period FSM offers functionality of deactivation of contact persons. To keep FSM and backend system aligned Connector can delete deactivated contact person or end its validity period Learn more here Transfer default customers unconditionally Customers set as default (e.g. in transaction /PACG/ECM_SCTDD - Service call typ - Default values) can always be sent to SAP FSM to the company assigned in the above transactions, even if their sales area/company code/no object assignment would indicate that they shouldn’t be sent. In certain scenarios, those generic customers usually do not have sales area but are still required for every company. Learn more here Allow "company code" and "no object" assignment for customer Apart from Sales Area, CUSTOMER objects can now be sent to FSM based on company code assignment or FSM company assignment (‘No object’). Business Partner can now be sent to SAP FSM as a customer or vendor based on any partner role If a Business Partner is assigned a partner role entered in transaction /PACG/ECM_BPASGN - BP role assignment and checked as customer/vendor, it can be sent to SAP FSM as such, even if no customer/vendor master data (tables KNA1/LFA1), nor sales area is assigned. Learn more here |
Connector Cockpit | Add object number to IDOC cockpit In the Connector Cockpit, in the IDOCs report, next to already presented information also an object’s key to which IDOC relates to is displayed. Learn more here, field ‘Show objecy ID’ 'Set to processed' functionality changed. Confirmation is sent to FSM only for objects for which GENERIC message is sent. In other cases only status is changed in SAP but object in FSM remains blocked Authorization check on SMQ1, SMQ2, ST22 and SWU3 from /PACG/ECM_COCKPIT_S and /PACG/ECM_COCKPIT Authorization check was added to the Cockpit. From now on user who wants to run standard transaction through it must have necessary authorizations Authorization object Z_IDOCRSND In addition to authorizations checks mentioned above new authorization object was added. It is required to execute ‘RESEND’ from the Connector Cockpit |
FSM Connector (general) | Disable use of HASH as optional functionality Due to its overall functionality and impact on Connector’s performance the hash mechanism is no more optional and can’t be disabled. This used to be customized in transaction /PACG/ECM_CLSASSIG. 'Force sending' for all sending transactions ‘Force sending’ option was added in all sending reports. 'Force sending' means an object should be sent to SAP FSM even if it hasn't changed since last transfer. New business object /PACG/ECM4 In order to handle attachments added to service checkout new business object was implemented. Learn more here 'Use WFM' should not be used Action after calling BADI /PACG/ECM_OBJ_NEEDED For each outgoing object, it is possible to define an action after calling BADI not needed (/PACG/ECM_OBJ_NEEDED) results as true (in parameter cv_not_needed) - meaning the object is not needed in FSM. The possible options include: Set to inactive, Soft delete, Delete, Do not send to FSM. The field is useful if an object used to be relevant for the cloud, but then stopped. Using the BAdI, it can be determined as such and then sent as inactive/deleted to FSM. Learn more here |
Holiday Calendars | Work centre as source for holiday calendar The work center’s factory calendar’s holiday calendar can be sent as FSM Holiday Calendar to a given company. Holiday calendar assignment of a given technician can be determined based on its work center’s factory calendar’s holiday calendar. Holiday calendar assignments are sent only for active and plannable FSM-relevant technicians whose work centers belong to plants set as FSM holiday calendar-relevant. Learn more here |
Materials | MM06 flag for deletion on item level triggers no event Setting deletion flag in MM06 transaction will now trigger relevant events and send deletion flag for corresponding objects to FSM Add config option steering batch determination New option ‘Batch if any plant matches’ added in /PACG/ECM_ICONF. It allows checking in all relevant plants (all plants assigned to given company) if given material is batched or not and if in any of them it is then it will be sent to FSM as such Learn more here |
Reserved materials | Determine whether an additional material screen should be displayed during reserved material consumption When the Reserved Material field ‘TrackPartEquipmentUsage’ is set, it will trigger the mobile application to redirect the user to the additional material screen, where they can interact with each part that has been created and enter more information, such as filling UDFs. The FSM Cloud Connector setting ‘RM TrP’ allows to decide whether the track equipment part flag should be set for reserved materials sent to FSM. The available options are: do not send Track Part flag, send the Track Part flag for all materials, send the Track Part flag for batch-managed materials, send the Track Part flag for serialized materials or send the Track Part flag for batch-managed and serialized materials. Learn more here, field ‘RM TrP’ |
Service Order | Add Material consumption as Component in Service order New options added in the /PACG/ECM_CMAT2. It gives now possibility to added consumed materials to components of related order not only as text items but also as stock and non-stock items Learn more here Check if customer lock before sending service order Checks on service orders and activities got aligned to avoid situations when order is transferred to FSM and activity not No update of control key in service order Only control keys listed in the transaction /PACG/ECM_CKDET can be changed by Connector during operation update Learn more here, field 'NoUpdOthCK' Send service call ONLY The program /PACG/ECM_SCALL gained new option ‘Send Service Call Only’. By default service orders are sent with related objects like time tasks, activities and others. With this option enabled, only service order objects are sent to FSM. Work center determination based on work center of functional location Use functional location’s work center for orders/operations when service calls/activities are created in SAP FSM. Learn more here, field ‘Work center source’ |
Time Effort/Expense/Material consumption/Stock transfer | New BAdI /PACG/ECM_BADI_COSTS created This badi can be used posting costs in reference to service order/operation. It lets overwriting original operation with other, determined based on custom logic |
Warehouses | Improve 'Storage Location Owners' handling Two new transactions were created /PACG/ECM_WRHSE and /PACG/ECM_WRHSK which allow defining FSM relevant warehouses (regular and consignment) and also link additional owners - all in single transaction |
UDF | Links to WEB SAP Gui New configuration tools was created which allows generating UDFs that will bring links to SAP WebGUI transactions for selected objects. |
Users/Employees | Transfer skills during employee transfer Employee’s skills are transferred automatically during Employee transfer. No additional customizing is required to enable it. Learn more here Check users functionality New report was created and in addition check can be run in Mass User Maintenance Report - it allows checking if selected user are valid from the SAP perspective Learn more here |