5.1.5 Behavior Patterns

PBSM (Profitability and Balance Sheet Management) Cloud Service’s User Defined Behavior Patterns allow you to define Principal Amortization Schedules for Non-Maturity Products in your portfolio. You can utilize a Behavior Pattern to generate Cash Flows by entering the Amortization Type Code as “Behavior Pattern” along with the actual Behavior Pattern Code for the relevant Instrument Records.

Behavior Pattern Summary

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

Figure 5-8 Behavior Pattern Summary


Behavior Pattern Summary

Search Behavior Pattern

Prerequisites: Predefined Behavior Pattern

To search for a Behavior Pattern:

Click Search after entering the search criteria. The search results are displayed in a table containing all the Behavior Patterns that meet the search criteria.

Or

An alternative method to search a Behavior Pattern 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 Behavior Pattern Summary. You can enter the Code, Name, Description or Pattern Type of the Behavior Pattern and click Search .

The Behavior Pattern Summary displays the following information:

Add: Click the Add icon on the page header to build a new Behavior Pattern.

  • Name: The Behavior Pattern's short name.
  • Dimension: The Dimension the Behavior Pattern belongs to.
  • Hierarchy: Name of the Hierarchy that is used to define Behavior Pattern.
  • Folder: The Folder name where the Behavior Pattern is saved.
  • Last Modified By: The user who last modified the Behavior Pattern.
  • Last Modified Date: The Date and Time when the Behavior Pattern 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 Behavior Pattern.
    • Multiple Delete: Enables you to select and delete one or multiple rules in the table simultaneously.
    • View/Edit: Based on the user privilege assigned, you can either only view or edit existing Behavior Patterns. To edit a rule, you must have Read/Write privilege.
    • Save As: You can reuse a Behavior Pattern 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 Behavior Patterns that you no longer require. Note that only Behavior Pattern owners and those with Read/Write privileges can delete Behavior Patterns. A Behavior Pattern that has a dependency cannot be deleted.
    • Dependency Check: You can perform a dependency check to know where a particular Behavior Pattern has been used. Before deleting a rule, it is always a good practice to do a dependency check to ensure you are not deleting Behavior Patterns that have dependencies. . A report of all rules that utilize the selected Behavior Pattern is generated.

      Note:

      This is functionality will intended for a future release.