Patches

Patch fixes included in release 4.5 are:

Forwarding Reason – Reassign All

Ability to use F4 to see forwarding reasons when using Reassign All in DWC in the Manager View.
F4 was not available in the Reassign All function from the DWC, this has now been made available to enable the user to select the forwarding reason from the list of options rather than needing to enter the reason directly.

Update to Master Data for Device Location

Ability to build Master Data Hierarchy using the Device Location.
In previous versions when using Identify Account with the Device Location as the parent object – the connection object list was built from the Device Location and the parent was switched to the Connection Object. This is how SAP builds the Master Data in the Data Environment. This has been changed to enable the Device Location to become the parent and build the Master Data using only the data relating to that specific Device Location.

Boomerang Aging Assignments

The Aging assignments has been rebuilt to determine the assignments from the work queues rather than getting the position of the processor ID.
Two options for assignments view when running the Boomerang Aging Report.

• Determine Current Assignment
• Assignment of Processor.
  

In the previous version there was no difference between these views.
Now the Determine Current Assignment option will fetch the actual assignment of the case either:
From the work queue or if the case has a processor the processor ID will be displayed.
Assignment of Processor – will display the cases with a processor ID and determine which positions the users are assigned too.
This is showing the cases belonging to the users within a team in the org structure rather than where the cases routed too.

Enhancement created to enable new Master Data objects to be added

This is a technical update to enable the ability to add new Master Data using a new enhancement spot in the build Master Data step.
This means the Business Add-In (BAdI) can be implemented and the logic rebuilt according to customer requirements. Example here was to add Provider Contract into the Master Data Hierarchy.
See the development cookbook for more details on using this BAdI.

Blade – Add key date from to selection screen parameter for Late Invoicing Report

Added new parameter into Late Invoicing Report to add a Key Date From. This will enable the from and to date to be determined for the Late Invoiced period to reduce performance issues and change the selection of the criteria when the report is executed. Previously all dates were considered in the report. This meant the report picked up archived billing periods in error and also would check accounts back to move in dates if no invoice found.

Now the key date from can be input to reduce the period back in which Blade will evaluate Late Invoiced period.