...
Post-installation steps
Run /PACG/ECM_SETUP
When installing a few service packs one by one, make sure that each service pack’s post-installation steps have been performed. Pay special attention to updating processing classes and transformations. The list of the most up-to-date classes/transformations can be found on the following page: Outbound/inbound message configuration
New features
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. Learn more: Custom Activity Address 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 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, field CO Posting. | ||
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 |
| Info |
|---|
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. |
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 entriesAdd 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_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 closed and certain follow up action can be configured.
If you want to learn more, 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 – General Properties of E4C Activity, fields RemvdOpAct, Removed operation text and WF Step for removed operation.
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
If you want to learn more, check /PACG/ECM_SCTD – Service Call types definition
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 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
Field 'Use WFM' has been removed from transaction /PACG/ECM_CPROP. Its remaining code implementations have been cleared.
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
Reversed Serial number is available to consume in FSM Mobile application again
After serial number reversal in SAP, the serial number will be possible to consume again if a new setting is enabled.
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’
Project stock in reserved materials
Reserved materials can use project stock. FSM technicians can see not only unplanned project stocks but also the reserved materials from project stock.
Learn more here
Service Order
Add Material consumption as Component in Service order
New options added in the /PACG/ECM_CMAT2. It gives now possibility to add 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.
Learn more here.
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