BookRunner® User Tip #21
Did
you know that…
The latest versions of BookRunner® allow users to run the MtM process
based on a subset of transactions in the system? Using the Ad-Hoc MtM
Process form (found under the Admin section on the Navigator), users can
specify to run the MtM process for only certain deals based upon selected
criteria, including position date, company, counterparty, DBS code and
XRef code. This Ad-Hoc function decreases the time to run the MtM Process
by limiting the amount of transactions that are included in the process.
This will help the user in situations where the MTM Process is executed
several times in a day (i.e. for stress testing) and only requires the
necessary transactions to be included.
BookRunner® User Tip #22
Did
you know that…
Several transactions can be linked together in the system and then reported
on? In addition to the DBS code field, transactions can also be grouped
together by Ticket Number, Xref code and Xref code2 on the Transaction
Input forms. These fields can be found on several of the most commonly
used report parameter pages, including the Mark-to-Market and VaR reports.
For example, users can create a Physical deal buying at AECO/NIT, a Transportation
deal moving the gas from AECO/NIT to DAWN, and a Physical deal selling
at DAWN. They can then link the three deals together by entering in a
common code in the Xref code field (i.e. the first deal’s transaction
number). On the MtM Report, they can then group the report by XRef code
and the three deals will display together with a sub-total for position
and MtM.