Datamart is a great tool in Murex but it also quite confusing as to how to use it and make the most out of it. As always, your Murex consulting team is the best source of advice.
The process to produce reports is usually the following:
- Define Simulation view with the data you want to retrieve
- Define a Dynamic table based on that Simulation view (note that you could base a dynamic table directly on TRNRP_PL or TRNRP_CS for instance)
- Define a feeder on that dynamic table (this will store the results into the reporting DB)
- Then use an extraction to retrieve the data from the reporting DB into a viewer.
The feeder can also source data from Murex tables or from other reporting tables. You’ll just have to build a map of the data you need and how to best access it. The feeders with SQL can retrieve data from different tables.
The advantage of using the simulation view as the source is that you can easily add fields and in a way do some WYSIWYG (what you see is what you get).
Now when designing reports, it is important to decide how frequently you would need to run the reports. For instance, if your feeders call upon other reporting tables, these ones won’t be refreshed. So re-running the reports on request is probably not always possible. Again it depends on your setup. If you’re simply sourcing from a dynamic table then it won’t apply to your case, but again each reporting setup is different.
Now one of the best feature of the reporting in Murex is the job recovery. If some of your report generation fail, from the job recovery you can re-run the report on the failed subset.
It might take many iterations but in the end you will end up with the failed trades. You can then exclude the failed trades or investigate them.
It can be used as a great tool to test if the EOD will run ok and zero on the trades that might cause issue.
Then of course, once you have your datamart running and all is good, what you need to build is the proper view/layout but that’s a different lesson.
What about you? Any good tip to share?