PACG 200 SP 12 / S4PACG 200 SP 12

The FSM Cloud Connector component was released on 26th of February 2024. Subscribe to the webinar dedicated to Service Pack 12.

FSM Cloud Connector release PACG 200/S4PACG 200 SP12 aligns with SAP FSM release 2402

Pre-installation steps

UPGRADE ONLY TO (S4)PACG 200 SP12

Please implement SAP NOTE 3434673 (Activities are not generated after upgrade to SP12) or follow steps listed below to avoid problems with the FSM Activities not being created after the event.

  • Run transaction /PACG/ECM_CEVT

  • Go to edit mode and click 'New Entries'

  • Enter 'Object Type': /PACG/ECM_CL_S_EVENT_ASA

  • Press 'SAVE'

Post-installation steps

NEW INSTALLATIONS & UPGRADE

image-20240412-061754.png
image-20240412-062056.png

 

 

Change Log (SAP NOTE 3407001)

Category

Feature description

Category

Feature description

Network-based Service Calls

Time Efforts

Time efforts created for network order activity-based FSM activities can be saved as CATS entries or network order confirmations

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/771719171/Network+order+integration+-+process+overview#Time-efforts

Activities

  • In the previous release, we disconnected FSM Activities from SAP Sales Area. In this release, we provide a dedicated report which cleans the no longer necessary configurations entries. The report is launched automatically when is executed.

  • New IDOC types were introduced for outgoing and incoming activities: /PACG/ECM_ITYPE_ACTIVITY02_OUT and /PACG/ECM_ITYPE_ACTIVITY01_IN accordingly. In both, a new segment /PACG/ECM_IS_ADDRESS was added.

Checklists

Handling of multiple selection in the dropdown list

Support for multiple selections in the Smartforms' dropdown lists.

Learn more:

Contact Persons

Contact persons' communication data determination

Communication data of contact persons can be retrieved from multiple sources in SAP and determined in different ways depending on business requirement. In order to face this problem, a new customizing transaction was implemented.

Learn more:

Equipment and functional location

Limit size of sent hierarchies

In order to prevent overflowing the FSM Cloud with the number of equipment objects sent along with service calls, a new setting was introduced. It defines a number of equipments that are allowed to be sent to FSM. This is particularly important when equipments are organised in hierarchies containing thousands of subobjects and a root node of such a hierarchy is selected to be sent.

Learn more:

Users

Users' organizations assignment

The users' maintenance transaction /PACG/ECM_ALV_USERS gained new functionality. Now it is possible to collectively manage users' organizations assignment.

Learn more: and

Organization structure definition

Enhancement of /PACG/ECM_CUST_ORG

We have improved management of the organizational structures. From now on, one can easily transport entire structure or selected parts of it to other systems.

Learn more:

Person Reservations

Support for multiple persons reservation

A Person Reservation created for multiple persons in FSM results in multiple time documents in SAP ECC/S4 (CATS or confirmations separate for each person). In case of update or deletion of such a person reservation in SAP ECC/S4, the initial reservation object in FSM is deleted and updated/remaining reservations are sent to FSM as separate objects (separate for each technician).

Mileage

Distance Unit

The standard Mileage property - distanceUnit - selected during mileage recording on the mobile app can have impact on activity type used for cost documents and hence their unit.

Learn more:

Posting framework

Log Viewer Enhancements

The posting framework Log Viewer gained two features which significantly improves its usability.

  • Select entries related to failed and not yet reprocessed scenarios

  • Rerun failed scenarios directly from the log viewer

Enhancement of ‘Assignment configuration - /PACG/ECM_FRMDEF’

The /PACG/ECM_FRMDEF transaction gained an UX improvement. Next to smartform template Id and version, also smartform’s category and name are displayed.

Performance

Is event active

A new check was introduced in the method that controls triggering of events. This is configuration based (/PACG/ECM_EVTD) - if an event is disabled, it will be suppressed by the program.

Learn more:

Resend start

A new internal message was added - /PACG/ECM_RESENDSTART. It is sent to the Message Broker right after the Resend request is received. It’s goal is to help avoiding situations where Message Broker restarts the ‘resend’ process due to the timeout caused by the delay in the response from the SAP system.

Administration and monitoring

'Send Deletion Request' report

A verification of the field ‘Cloud message type’ was added to transaction /PACG/ECM_SEND_DELRQ. Before that change, system did not control entered values. If they were incorrect, the processing got terminated due to an error and the outbound queue was blocked.

New deletion report

A few releases ago an internal Connector’s events queue was introduced. It relies on the table /PACG/ECM_EVENTS. Under certain conditions this table may grow rapidly. In this release we added a report (/PACG/ECM_DELETE_EVENTS) which can help removing obsolete entries.

FSM Cockpit

New information on the Connector’s state available in the FSM Connector. From now on it shows Connector’s state, whether it is in the normal operation mode, in the Fullsync mode or if the Resend is running. It is also possible to check one the last Fullsync and Resend were executed.

Learn more: and

Adjustment of /PACG/ECM_MBCF_GEN to the Message Broker 4.2

In the Message Broker 4.2 new properties were added in the configuration. In the SP12 Connector’s MB Config File Generator was updated in order to create the most valid config files.

FSM Irrelevant

A new property ‘FSM Irrelevant’ was introduced. It can control whether a message should be passed to FSM and is intended for internal communication between Connector and Message Broker. This setting is visible in transaction /PACG/ECM_CLSASSIG but is defined as ‘read-only’

UX/UI improvements

Support of PTMW transaction

Time entries created/updated/deleted via PTMW transaction are automatically and immediately transferred to FSM.

Learn more:

Transactions /PACG/ECM_O_IDOC_T & /PACG/ECM_I_IDOC_T

Transactions /PACG/ECM_O_IDOC_T & /PACG/ECM_I_IDOC_T that help measure Connector’s performance were enhanced and gained a new selection field - ‘Created At’.

Learn more:

‘Copy to another company’ function added in the configuration transactions

A dedicated option which allows easy copying of the configuration (it also covers mapping of data in the relevant cases) between plants was added to the following transactions:

  • /PACG/ECM_CSPLIT

  • /PACG/ECM_CSPLIT_R

Learn more:

Support for table /PACG/ECM_UDF3 in the company copy report

We’ve overcome technical challenges and now provide complete support for the /PACG/ECM_UDF3 table in the company settings copy program.

Learn more:

Mandatory fields in /PACG/ECM_WRHSE and /PACG/ECM_WRHSK

It used to be possible to create empty entries (having no company nor plant defined) in the Warehouse Definition transaction which was causing certain issues during data selection. In addition it negatively impacted configurations' transparency. From now on Company, Plant and Storage Location (/PACG/ECM_WRHSE) and Company, Plant, Customer (/PACG/ECM_WRHSK) are obligatory

Search help ‘/PACG/ECM_CLTTH2’ improved

The search help /PACG/ECM_CLTTH2 used in transactions /PACG/ECM_CHLCF and /PACG/ECM_FRM06 was enhanced with the Smartforms' template category name in order to help uniquely identify needed template.

New transactions

List of new transactions:

Others

  • Additional verification of resend Id in /PACG/ECM_CL_S_CHANNEL_XML_WS - this change was introduced to avoid sending to message broker objects with invalid resend Id (such messages are ignored so sending them is only unnecessary effort

  • Call to FM ‘BUP_MEMORY_CENTRAL_INIT' added before call to FM ‘BUPA_ADDRESSES_GET’. This solved the problem with the error message 'R11 335’ (“Errors occurred during call of function module”) caused by not initial variables used by FM.

If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.