PACG 200/S4PACG 200

Attachments

Redesigned attachments handling.

Until now, it was possible to use only one of the following three solutions for storing attachments: SAP Office, BDS or DMS. With the new attachment’s solution, it will be possible to use all storage methods in parallel and the final decision how the attachment file should be saved can be taken based on Company/Message Type/File Type.

Learn more: /PACG/ECM_CUST_ATTA - Inbound/Outbound Attachment Configuration

Checklists

Automatic posting framework.

ISU Posting Framework is the mechanism allowing automatic processing of inbound checklist in a step-based manner. It allows to define scenarios consisting of one or multiple steps (methods). Such scenario is then linked with a checklist (template id and version) and processed automatically once the corresponding checklist is submitted in the FSM. This can be especially useful in situations such as ISU meter exchange.

Learn more: Posting Framework

Person

ALV based users’ maintenance.

A new ALV-based transaction for maintaining users’ data. ALV by standard allows data sorting and filtering. In addition, the transaction allows mass data changing.

Learn more: /PACG/ECM_ALV_USERS - Mass User Maintenance

UDF

Automatic inbound and outbound UDF’s data processing.

In case there was no need to change UDF’s data in the backend system, enable storing UDF values related to a given UDF ID. After a UDF value is entered in SAP FSM and sent to SAP, it will be stored in a dedicated table and sent back to SAP FSM with the outbound object, without the need to implement an additional BAdI.

Learn more: Automatic inbound and outbound data processing of UDFs

Activity

Hazard Type and Travel Time.

Activities' properties Hazard Type and Travel Time are now integrated with ERP/S4. Because there are no corresponding fields within SAP standard, a BAdI has been defined that allows to prefill them when activity is created in SAP.

Learn more: Hazard Type (signal word) and Travel time from and to in minutes

Activity feedback without code groups.
Transfer feedback activity codes without corresponding code groups. When recording Activity Feedback codes, code groups are not displayed and the number of clicks made by technicians is reduced.

Do not overwrite existing items in notifications with activity feedback items

With a new setting ('New entry' in /PACG/ECM_ACTGS), Activity feedback will always create new entries in notification’s items instead of overwriting the existing ones.

Learn more: /PACG/ECM_ACTGS - Act. Codes - General Settings

Material without sales organization data will be transferred to SAP FSM.
Until now one of the requirements to send materials’ data to FSM was assignment to sales area. This has been now redesigned and plant assignment is sufficient to send master data to SAP FSM.

Learn more: /PACG/ECM_ITYPE – Material Group and Company assignment | Plant dependent material

Ref. Functional Location Update.
After reference functional location is changed in transaction IL12, an update of all related functional locations will be sent to SAP FSM.

Customize Start Fixed, End Fixed and Technician Fixed properties of person reservation.
New properties of the SAP FSM Person Reservation object - ‘Start Fixed’, ‘End Fixed’ and ‘Technician fixed’ - can be maintained in SAP ECC/S4 and transferred to SAP FSM.

Learn more: /PACG/ECM_T554S - Att./Abs. types for Person reservations | Fixed properties

Re-designing and extension of Ping Message Broker functionality in E4C Cockpit.
The ‘PING’ functionality in FSM Cloud Connector’s Cockpit has been enhanced. The Cockpit shows the status of each Message Broker which is used by FSM Cloud Connector.

Learn more: /PACG/ECM_COCKPIT - FSM Connector Cockpit

Handling of supporting persons
After releasing an activity with supporting persons, the supporting person information is sent to SAP, saved in the dedicated table and resent to FSM. 

Learn more: Supporting Persons