Versions Compared

Old Version 1

changes.mady.by.user proaxia

Saved on

compared with

New Version Current

changes.mady.by.user proaxia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Redesign of the service call status customizing ( /PACG/ECM_SCSTD)The FSM Cloud Connector component was released on 0215.0911.2024.

Panel
panelIconIdatlassian-yellow_star
panelIcon:yellow_star:
panelIconText:yellow_star:
bgColor#DEEBFF

Download here:

SUPPORT PACKAGE FOR ADD-ON 200 SAP ECC

SUPPORT PACKAGE FOR ADD-ON 200 FOR SAP S/4HANA

Info

FSM Cloud Connector release PACG 200/S4PACG 200 SP14 SP15 aligns with SAP FSM release 24082411

Post-installation steps

1. Notes' installation

  • Check notes and install relevant ones

2. Run /PACG/ECM_SETUP

...

Change Log (SAP NOTE 3539336)

Category

Description

Administration

FSM Cockpit
The FSM Cockpit can now show information about the number of entries in ARFCSTATE table and average of last 10 size checks. This can help to quickly identify potential performance problems

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/

...

2137096193/PACG

...

Selection class /PACG/ECM_CL_S_SEL_SCALLSTATUS2 

Change Log (SAP NOTE 3511512)

Category

Feature description

Business partners

Multiple addresses for business partner

This feature is fully supported in the systems using central business partners management (BP). From now on, Connector can correctly handle any number of address added in FSM to a single business partner.

+ECM_COCKPIT2+-+FSM+Connector+Cockpit#ARFCSTATE-Info

FSM Cockpit – IDocs report & Hotspots
In the Connector 3.0, in the IDocs list, S/4 HANA Service Orders are now correctly identified and when clicked a dedicated Fiori app is opened (analogically to other objects for which GUI transaction is started)

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages

/2309259265

Deactivate expired contact persons

Expired contact persons can now be synced with FSM. Such contacts after validating their relevancy are sent as inactive. This helps keep customers' information in both systems consistent.

Equipment

Relocation of the ‘MAX EQUI’ parameter

Due to introduction of a new param controlling number of equipment sent with service call, the param controlling number of equipment sent with subhierarchy was moved to /PACG/ECM_EQ1 configuration transaction

Service orders

Redesign of the service call status customizing

The latest Connector release delivers new version of /PACG/ECM_SCSTD transaction. Although its layout has not change its functionality was reimplemented in such a way that it’s easier to use and less error prone

/2137096193/PACG+ECM_COCKPIT2+-+FSM+Connector+Cockpit#(S4)PACG-200-Sp06-Hotspots

FSM Cockpit – IDocs report & custom IDocs
In addition to standard Connector’s IDocs, the FSM Cockpit is now capable of showing also IDocs of the custom types if such are used with Connector

New Checks for /PACG/ECM_QSTATUS
The /PACG/ECM_QSTATUS report can now send warnings in the the following new situations:

  • In case the number of entries in the ARFCSTATE table crosses defined value

  • In case when Connector’s objects stays in the queue longer than given amount of time. This helps to identify the situation when queues’ processing gets too long

  • In case when number of created Connector’s relevant IDocs in an unit of time exceeds certain defined value.

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages

/37135809

Control the number of equipment sent with service call

In addition to the existing parameter which can limit the number of equipment sent with subhierarchies this SP brings another one - a parameter that can limit the number of equipment sent with a service call

/1508114433/PACG+ECM_QSTATUS+-+Email+queue+issues#IDOCs-in-error-status

FSM Users’ Management
New FSM Connector delivers a report which can create FSM Users based on data imported from excel file

Learn more: Mass User Upload

Companies’ deletion
The existing set of deletion reports was enriched with additional one which allows for deletion of all transactional data for selected company in one go.

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/

72974378

1918926882/PACG+ECM_COPY_

SCG

COMP2+-+

Service

Copy+

call

delete+

general+settings#Max.No.Equi%2FFL

Administration & Monitoring

Change layout of /PACG/ECM_CPROP

To improve usability and intelligibility of the basic settings of FSM Connector we have entirely redesigned the /PACG/CPROP transaction

company+settings#(S4)PACG-200-SP15--Delete-program%3A-Transactional-Data

Deleting objects in FSM
The /PACG/ECM_SEND_DELRQ gained new functionality. It can sends deletion requests to FSM using the cloud identifiers of objects instead of their SAP keys. This gives the possibility of removing objects in FSM that has no counterparts in the backend system. This feature requires the lates Message Broker

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37138563

Maintenance of Connector’s number ranges
The latest Connector delivers a new transaction designed to maintain Connector’s relevant number ranges. This is solution addresses a problem that older versions of Connector were using number ranges longer than ones that could be correctly displayed in the standard transaction.

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages

/31952515Enhancements in

/2137096193/PACG+ECM_COCKPIT2+-+FSM+Connector+Cockpit#(S4)PACG-200-Sp09--Number-ranges-statuses

New selection parameters added to /PACG/ECM_O_

ALV_USERS Transaction

IDOC_T & /PACG/ECM_

ALV_USERS is now capable to show the personal area to which FSM users are assigned to. More over, it is also possible to search users based on their assignment to personal area

I_IDOC_T
A new selection parameter – ‘IDoc basic type’ was added to selection screens of both reports. This can help analyse only selected types of IDocs.

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/

975601806

New feature of FSM Cockpit

The FSM Cockpit can now show information about the actual size of Connector related data tables. This information is update by dedicated report which can be executed on demand or scheduled as a background job

1859878946

Message Broker health status
A new report which helps to monitor ‘health’ of the message broker. It relies on the information about last metadata exchange between transporter and FSM

Business Partners

Customers’ Deactivation
FSM Connector is now capable of handling customers’ deactivation in FSM


Optional transfer of Business Partners to FSM
Business partners can now be sent to FSM ‘on demand’. This means, that like in case of equipment, BP master data will be sent to FSM with their first usage in a service call instead of sending all BP master records during the fullsync process.

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/

2137096193

1166606379/PACG+ECM_

COCKPIT2

CCUST+-+

FSM

General+customizing+

Connector

for+

Cockpit#

Customer#(S4)PACG-200-

Sp14

SP15-Cust-

PACG-tabs-statistics

FSM Activities

Optional sending of activities with service order

In SP09 we disabled unconditional sending of all activities triggered from the selection class of service call. It turned out however that on rare occasions such a process is required by therefore from now on it can be enabled by a dedicated option

Learn more:

on-req and https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/

31952515

1173979146/PACG+ECM_

CPROP

CVEND+

-

Vendor+General+

Properties+of+FSM+Cloud+Connector#Send-activities-with-Service-Order

Suboperations reflected as hierarchy in FSM

By default, for each pair operation and suboperation Connector creates independent activity. In this release we have implemented a feature which can modify Connector’s behaviour and when enabled, for a pair operation and suboperation it creates activity and a follow-up activity (former suboperation)

customizing#(S4)PACG-200-SP15-Vend-on-req-(Send-Vendor%2FContact-on-request)

Regions

Work centers as regions
In FSM regions can be structured in hierarchies. This feature is now also supported by Connector which can send work centers as regions including their structural dependencies

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/

37135497

37136514/PACG+ECM_SC_

ACTIVE

GR+Group+

General

region+

Properties

for+

of

service+

E4C

calls+

Activity#Suboperation

activities#Include-

activities-as-follow-up-act

Region update on technician’s reassignment

From now on, when an activity is reassigned to a technician belonging to a different work centre than the initial one, and the region determination is based on the operation’s work centre, the Connector will update the activity’s region assignment accordingly

Hierarchy-(S4)PACG-200-SP15

Attachments

Data transfer restrictions
Sending of attachments to FSM can from now on be restricted based on the storage type used (GOS, BDS, DMS).

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages

/37136514

Work centre update in network orders

For updated activities

/928809057/Block+from+transfer+to+FSM+Outbound+configuration#%F0%9F%95%91-Block-from-transfer-to-FSM-%2F-OLD-LABEL-Outbound-configuration

Production Orders

Productions Orders as Service Calls

  • Service calls created based on production orders

  • Plannable activities’ created in reference to

network orders, like in case of CS order, Connector is capable of the redetermination of valid work centre (for instance in case of technicians reassignment)

UDF

Enhancements for the UDF building program

The report /PACG/ECM_UDFG_UDF gained two additional features and lost one functionality. The report can now create and send UDF definitions to multiple companies at once. Then, it can now also display the list of generated UDFs. And the thing it cannot do anymore is sending of deletion requests - for this there are dedicated tools in the Connector

  • production orders

  • Support of attachments added to production orders and referenced service calls

  • Time effort handling

  • Checklists’ assignment support

CS Service Orders

Handling of time units on orders’ operations
The new Connector removes limitations on the used time units with the values of duration and work time in orders’ operations. Before change it was only possible to use seconds/minutes/hours. Now Connector is capable of calculating values in any time unit used in operation.

Include functional locations in order’s object list
When service order is sent to FSM its equipment included in the object list are sent too. Beginning with the latest Connector also functional location included in this list will get sent too

FSM Activity

Fiori App
The latest SP for Connector 3.0 delivers brand new Fiori app to display FMS activities

Operation’s control key and FSM activity status
If the control key of a operation having linked activities changes to one that is not FSM relevant, the related activities will get automatically closed.

Reserved materials

Returns of materials in customer consignation process
New Connector brings changes in the return process of reserved materials. If materials that are reserved in the process of ‘Customer consignation’ are returned instead of simple goods movement a new return document is created initiating entire return process.

Arrival date determination
The initial requirement date is set automatically when reservation is created based on requirement date in the related service order. This does not take the type of process into account. This turned to be confusing for some customers. As a result new configuration option was introduced which controls whether the initial arrival date of reserved materials should be set based on requirement date or not.

Arrival date determination report
The arrival date determination report gained new selection parameters including:
• FSM Activity number
• FSM Activity status
• Shipment status
• Consider consignment

Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/

37138716

Obsolete transactions

  • /PACG/ECM_VENDMASTER

    • /PACG/ECM_CUSTMASTER

    1722679297

    Performance

    Save Purchase Order

    The even triggered on the save of the purchase orders is no longer mainteined in the SWEC transaction and instead is called by ABAP method. This way number of triggered events can be limited to those which are FSM relevant

    Enhancement of IDoc generator for Equipment

    In the IDoc generator class for equipment (and functional locations) the superfluous updates of DB tables was suppressed - this should improve overall processing.

    Processing if incoming activities

    For incoming activities the process of (re)determination valid work centres was reimplemented and simplified in a way that information can be used by related objects limiting the number of DB queries

    Authorization Objects

    • /PACG/E023 - Allows displaying Connector’s tables stats in FSM Cockpit

    • /PACG/E024 - Allows running report updating Connector’s tables stats

    • /PACG/E025 - Allows changing max number of equipment included in Service Call

    New transactions

    • /PACG/ECM_BP_ADDR - Address Determination for BP

    • /PACG/ECM_DEL_BPOADR - Delete table /PACG/ECM_BPOADR

    • /PACG/ECM_SCSTS - Status of Service Call Description

    • /PACG/ECM_TRIG_CUST - Customer, address, contact person

    • /PACG/ECM_TRIG_VEND - Vendor, address, contact person

    Equipment

    Characteristics sent as remarks
    New Connector version delivers small yet important change in how remarks are generated based on equipment’s characteristics. In case of characteristics that comes with predefined values, from now on, in addition to the values themselves Connector will also include their descriptions.

    Learn more: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953680

    UI modification

    In transactions /PACG/ECM_COMP and /PACG/ECM_CCUST entries’ deletion got suppressed. Since Connector delivers dedicated reports for deleting companies data deletion of companies deletion is not only no longer needed but can lead to data inconsistencies

    Employees

    Changes in the HR Infotype 0105 using transaction PA30 are now transferred to FSM automatically – relevant even is raised. Valid subtypes of infotype 0105 for which this will happen are

    New transactions

    • /PACG/ECM_ACTI01

    • /PACG/ECM_ACTI02

    • /PACG/ECM_ACTI03

    • /PACG/ECM_PCONF

    • /PACG/ECM_TRIG_ACTST

    • /PACG/ECM_VNRST