5.3.2.6 Transaction Strategy Rules

With the Transaction Strategy Rules you can test the impact of various hedging strategies that are integrated with basic scenario modeling assumptions. This functionality supports you to test the alternative strategies and their incremental impact on results. The testing is facilitated by the separation of transaction strategies from basic scenario assumptions allows you to easily view the results with and without the incremental transaction(s). Use this Rule to add specific instrument records to a processing run without changing the actual instrument data. A transaction is either positive or negative and can be defined for any product leaf member. A Transaction Strategy Rule is made up of any number of individual transactions.

Search Transaction Strategies Rule

Prerequisites: Predefined Transaction Strategies Rule

To search for a Transaction Strategies Rule:

On the Transaction Strategies Summary, enter your search criteria in the search box and click Search. The Transaction Strategies Rules meeting your search criteria are displayed.

Or

An alternative method to search a Transaction Strategies Rule is through the Field Search option. This is an inline wildcard UI search that allows you to enter a search value (such as code, name, etc.) partially or fully. Rows that contain the string you are searching for are fetched and displayed in the Transaction Strategies Rule Summary. You can enter the Code, Name, Description, Hierarchy, and Folder of the Transaction Strategies Rule, partially or fully, and click Search.

Transaction Strategies Rule Summary

This page is the gateway to all Transaction Strategies Rules and related functionality. You can navigate to other pages relating to Transaction Strategies Rules from this point.

Figure 5-189 Transaction Strategies Rule Summary

The Transaction Strategies Rule Summary displays the following information:

Add: Click the Add icon on the page header to build a new Transaction Strategies Rule.

Multiple Delete: Enables you to select and delete one or multiple rules in the table simultaneously.

• Name: The Transaction Strategies Rule's short name.
• Hierarchy: Name of the hierarchy that is used to define the Transaction Strategies Rule.
• Folder: The folder where the Transaction Strategies Rule is saved.
• Last Modified By: The user who last modified the Transaction Strategies Rule.
• Last Modified Date: The Date and Time when the Transaction Strategies Rule was last modified.
• Access Type: The access type of the rule. It can be Read-Only or Read/Write.
• Action: Click this icon to view a list of actions that you can perform on the selected Transaction Strategies Rule.
  • View/Edit: Based on the user privilege assigned, you can either only view or edit existing Transaction Strategies Rules. To edit a rule, you must have Read/Write privilege.
  • Save As: You can reuse a Transaction Strategies Rule by saving it under a new name thus saving time and effort in entering data multiple times; it also leads to reduced data entry errors.
  • Delete: You can delete Transaction Strategies Rules that you no longer require. Note that only Transaction Strategies Rule owners and those with Read/Write privileges can delete Transaction Strategies Rules. A Transaction Strategies Rule that has a dependency cannot be deleted. A rule cannot be retrieved after deletion.
  • Dependency Check: You can perform a dependency check to know where a particular Transaction Strategies Rule has been used. Before deleting a rule, it is always a good practice to do a dependency check to ensure you are not deleting Transaction Strategies Rules that have dependencies. A report of all rules that utilize the selected Transaction Strategies Rule is generated.

Also See:

• Create Transaction Strategies Rules