| Scenario |
A report that had previously
received detailed attention to improve its
performance was still unable to run
in the project’s high volume test environment.
The volume of data was simply too large and
processing terminated with a runtime error. |
| Goal |
- Provide the capability to produce flexible
and interactive results that engage business
users with a richness that would not otherwise
be possible.
- Minimise runtime to provide information
in a time-efficient manner.
- Maximise utilisation of available computing
resources to avoid long-running processes
that affect overall system performance.
- Leveraging current skill-sets and existing
investment in custom-developments.
|
| Outcome |
After converting the report to run under
the control of MDR, the report ran successfully
in the high-volume test environment, processing
around 10 million customers and 50 million
financial line items in under 15 minutes. |
| Output Usability |
MDR report output is not static and lengthy
since interactive reporting techniques, such
as drill-down and exporting to spreadsheets
are supported. An MDR report can be run much
more frequently, as the periodic batch window
is under less pressure. |
| Output Delivery |
The original report provided it’s
output as a static list in the spool, this
is typical of a background report output.
MDR provided the interactive results as a
link to the users inbox. |
| Customer learning curve |
MDR can be easily understood by SAP developers
of all skill levels. A report that had previously
received detailed attention to improve its
performance was still unable to run in the
project’s high volume test environment.
The volume of data was simply too large and
processing terminated with a runtime error. |
