Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

To be released soon.

Download here:

SUPPORT PACKAGE FOR ADD-ON 200 SAP ECC

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

FSM Cloud Connector release PACG 200/S4PACG 200 SP7 aligns with SAP FSM release 2211

Post-installation steps

  • Run /PACG/ECM_SETUP

Change Log

Category

Feature description

Attachments

Persons' attachments

With its latest release the FSM Connector is now capable of handling the attachments added to a person – both in the FSM and in the backed ERP system

Overwrite BDS customising

There was a BAdI added that lets implementing customers' extension which allows using different document types for BDS attachments than it results from the configuration.

Automatic population of attachments added to Service Call in FSM to activities should be optional

From now on it is possible to disable automatic population of attachments added to service calls to activities and/or notifications

Contracts

Update contract status if the end date or termination date is reached

There has been a new report added to FSM Connector. It can recognized contracts which validity date has passed and send relevant updates to FSM

Equipment/Functional Location

Get partners for Equipment and Functional Location from parent object

A new configuration option added - when selected, when sending master data, business partner is determined from parent objects in the hierarchy

FSM Connector (general)

Report correcting the entries in the table BELHDR (follow up to SAP Note 3206242)

There is a new report added to Connector’s toolset which can fix entries in BELHDR table (application logs) which cannot be removed otherwise

Changes in FSM Connector General Properties /PACG/ECM_CPROP

From transaction /PACG/ECM_CPROP controls enabling DMS and BDS attachments got removed. They were obsolete since attachments control was moved to /PACG/ECM_CUST_ATTA transactions.

Also the control enabling FSM Activities got removed since this is the only solution and disabling them may lead to inconsistencies

Sending deletion requests requires an authorization

A new authorization object /PACG/E010 was created and it is used to control who can send objects' deletion requests to FSM

Message Broker

Automatic generation of the message broker config file

This new tool lets users build and generate message broker config file in an easy and user friendly way

Performance

Sending reserved materials to FSM

FSM Connector sends from now on reserved material and batches from reserved material only if the service order operation is dispatched

Supress ASA event when processing inbound final confirmation.

Starting with the new FSM Connector, when processing inbound final confirmations the ASA event has been supressed and not triggered anymore. This in tuned improved significantly the entire operation especially in case of orders having a huge number of assigned activities

Personal reservations

Store inbound person reservation properties in SAP ECC/S4 to avoid overwriting them

Personal reservations' properties which do have match in standard ERP will be held in dedicated Connector’s tabled to avoid them being overwritten during update.

Store/retrieve descriptions for person reservations saved as HR absences

Personal reservations' remarks can now be stored as an infotype long text.

Service Order

Maintain equipment on the operation via Assignment functionality on the Object tab in the service order

With new FSM Connector it is now also possible to maintain equipment on the operations level with the standard ERP functionality ‘Assignment of Operations to all object list entries active’ enabled

Users/Employees

In FSM Users' maintenance reports add additional info about user name or personal number

Now in users maintenance transactions, both are displayed employee and user name for each defined FSM person (only when corresponding objects exist). In addition both of them work as links to related transactions SU01 in case of user and PA30 in case of employee

In the transaction /PACG/ECM_USERG allow using other email sources than 4 predefined ones

It is now possible to use other subtypes of infotype 0105 than four predefined values as the source of email address for the users

Multiple work centers assigned to a person sent as a region

With the new Connector version if user is assigned to more work centres than one all will be sent to FSM as regions

UDF

New option in UDF Definition transaction

UDF definition transaction has now the option that allows sending UDFs definition to FSM based on selected items

  • No labels