Highlights

General SAP FSM - SAP ECC integration

• Department integration - transfer department units and employee department assignments from SAP ECC to SAP FSM. Departments assigned to employees in SAP FSM are sent to SAP S/4 with idocs of type /PACG/ECM_ITYPE_PERSONIN.

• Internal remarks integration - activity internal remarks are sent to and from SAP ECC and displayed in transaction /PACG/ECM_ACTI_VC03 - Display E4C Activity.

• 'Inactive' property - transfer objects from SAP ECC to SAP FSM as 'inactive'. A new field 'inactive' added to the idoc segment /PACG/ECM_IS_CONTROL.

• Regulate synchronization of activities with status 'draft'.

Tools

• Transfer tools of material and equipment type from SAP ECC to SAP FSM.

• Transfer business partner, person responsible relationships, attachments and relevant UDFs from SAP ECC to SAP FSM (for tools of type equipment).

• Add a required tool in SAP ERP by adding a PRT of the type material to a service order. The required tool assignment is visible in SAP WFM.

• Add a required tool in SAP FSM WFM by adding a PRT of the type material to an activity. The required tool assignment is visible on the relevant service order in SAP ERP.

• Reserve a tool in SAP FSM WFM by adding a PRT of the type equipment to an activity. The reserved tool is visible on the relevant activity in the SAP FSM mobile application.

• Register a used tool against an activity in the SAP FSM mobile application. The used tool assignment is visible on the relevant service order in SAP ERP.

Crowd

• Crowd partners are sent to SAP ECC as vendors.

• Partners' admins and technicians are sent to SAP ECC as employees (with the following infotypes: P0000, P0001, P0002, P0003, P0105, P315) and E4C users.

• Determine default HR Master Data values for incoming crowd employees (e.g. cost center).

• Technicians' skills are sent to SAP ECC and can be maintained with transaction PPDPIM.

Regions and planning scenarios

• Transfer work centers, planning groups and address regions as FSM regions.

• Create planning scenarios in SAP ECC and transfer them to SAP FSM.

Service workflow

• Workflow steps of an FSM activity can change depending on a user status of a related SAP service order.

• Workflow steps of an FSM activity can change depending on a user status of a related service notification (as a service call).

Person

• Substitute person reservation descriptions displayed in SAP FSM with custom and anonymous names (e.g. all reservation types in SAP FSM are displayed as 'off').

• Transfer person reservations from SAP ECC to SAP FSM as non-exclusive.

• A new source of usernames for person objects sent to FSM - SAP username.

Smartforms

• Redesign of setting a user status of a service order based on checklist input – combined into a view cluster with extended condition criteria possibilities.

• Manage notifications and notification tasks based on checklist input.

• Display unfinished checklist explanations in checklist display and monitoring reports.

• Add an instance-specific description to a checklist instance when creating them in SAP S/4.

Time efforts

• Time tasks can be created with reference to a person (sent once with the user data). In the standard approach, two kinds of time tasks are sent to the cloud – one referring to an object (O-type) and another one referring to a person (P-type). To prevent generation of excessive number of time tasks, tasks for technicians have been implemented. Such tasks refer to a specific technician and are sent only once, with the user data (/PACG/ECM_USERMASTER – User).

Stock

• Send stock information for project stock.

• A new special stock type defined for transaction /PACG/ECM_WRHSP – Reserved Material DC (Direct consumption).

Administration and monitoring

Activity migration program

• Define a selection of documents which should be migrated. New activities are linked with existing orders and other objects already linked to old activities. Use the program in the 'test run' mode. Set the new inbound and outbound data handling classes for E4C activities directly from the report. Logs confirm the success or failure of the process.

Processing time of outgoing idocs

• Measure time differences between statuses of inbound and outbound idocs (performance monitoring tool).

Error message for blocked objects

• Objects not confirmed by SAP ECC can be unblocked by sending an 'object error' message to SAP FSM. The message can be enabled for each incoming message type.

BDS

• Store inbound attachments using SAP Business Document Service (BDS).

Additional enhancements

• Lock mechanism in event processing of event "Service order". The mechanism checks if a service order can be locked within a set amount of time. If not, the processing is cancelled with an error which prevents reading and using data of a service order which is not fully saved.

• Check whether an attachment has already been sent in case of sending the same attachments to various companies.

• Custom service calls and activities - inject any fitting content into the structure of an idoc and send it to the cloud as an activity or a service call.

• Transfer states from SAP ECC to SAP FSM (e.g. US states).

• Employee address determined for AI planning - address determination adjusted to send multiple addresses based on info type / subtype instead of customized.

• Determine the technician's work address using the personnel area instead of infotype 0006 (Addresses).

• Additional ways of determination of cost center for time efforts. Time effort type as a source of cost center.

• Redesign of e-mail sending customizing – combined into a view cluster with more advanced condition rules.

• Default implementation of BADI DOCUMENT_OBJ created including standard /PACG/ screen. Handling E4C Activities attachments in DMS.

• If description is not provided for inbound attachments that should be stored using DMS, the filename is used instead.

• Message ID to idoc number mappings (from the /PACG/ECM_MIDMAP table) can be deleted collectively when no longer needed with a new deletion program.

• Setting Serial Number as inactive in FSM after it gets used in SAP ECC - instead of deletion mark, inactive mark is sent for serial number outbound IDoc.

• Additional configuration for 'Warranty and contract' texts sending.

• Functionality of blocking of sending attachments extended by the company indicator.

• Duration time conversion to hours on operation level of service order.

• After attachment deletion in SAP ECC, it is removed from SAP FSM as well.

• Extended check if a material is batchable – apart from the MARA table (if XCHPF is empty), the MARC table is checked for a given plant.

• Add entries to TRESC table by the setup program - TRESC table entries added by the setup program corresponding to entries added to BALOBJ and BALSUB tables.

• Book expenses on the level of service order operation.

• Book material movement on the level of service order operation
  

Bug fixes

• Company ID in the /pacg/ecm_armat table now properly filled when creating a component during service order creation.

• Stock information now always sent if MARD-LABST field has a value bigger than 0.

• Additional validation for time frames of work time tasks - actual start/finish fields now obligatory in the Work time – Time frames table. Start dates of work time in CATS now displayed correctly.

• When sending a person reservation with transaction /PACG/ECM_TRIG_PRERV error logs with not selected users and message 'User [user name] does not exist in this period' are no longer displayed.

• If the description of an equipment or functional location in tables EQKT and IFLOTX is empty, even though the record for the language relevant for sending exists, it will be omitted during selection - segment PACG/ECM_IS_EQUI_DESCR won't be created.

• Filetype of DSM attachments now always determined and sent (DMS or non-DMS).

• Sending large attachments to the cloud depending on company settings and no longer limited by an E4C constant.

• Customer data not deleted if the "General Delete Block" is set on Business Partner.

• Activity quantity for expenses now correctly imported from the customizing (transaction /PACG/ECM_VEXPNS -> Expense type assignment). Lack of a udf field for quantity doesn't cause errors with idoc processing.

• Unit of measurement for expenses defined to be booked as order confirmation is now properly put in the 'actual duration' field of PM Order Confirmations.

• All the mileage notes entered in SAP FSM are now properly recorded in the confirmation text in SAP ECC.

• UDF sorting no longer breaks sequence of long texts.

• Corrected xslt transformation for incoming Equipment in the setup program.

• Changes in the configuration transaction /PACG/ECM_DMSI – an unused field removed, added 'storage category' configuration option.

• BDS key generation fixed.

• Sending service order and notifications attachments as activity attachment feature corrected.

• Numeric data type introduced for number input fields on checklist.

• Correct sending of components without a storage location – define a special E4C stock without a type in transaction /PACG/ECM_WRHSP.

• Set inactive flag instead of delete service order (transaction /PACG/ECM_SCREQ).

• Service Order and Notification attachments are now linked to an activity.