5.3.2.1 Product Characteristics

Product Characteristic Rules are used to define payment, pricing, and repricing characteristics for new business. These Product Characteristics are rules that are placed on MDBSS nodes to be used in Forecasting that instruct the Application on what key new business contractual and behavioral features are to be included, such as amortization, adjustable type, compounding, day count, and other key features.

The new business assumptions are based on the MDBSS structure and ALMCS key features. In ALMCS, Product Characteristics is for new business forecasting only and does not include any existing business assumptions.

As part of creating and editing Product Characteristic Rules, you assign product attribute assumptions to applicable products from the product hierarchy.

Note:

Oracle Asset Liability Management Cloud provides the option to copy, in total or selectively, the product assumptions contained within ALM business Rules from one currency to another currency or a set of currencies or from one product to another product or a set of products.

Product Characteristic Rule Summary Page

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

Figure 5-143 Product Characteristics Summary


Product Characteristics Summary

Search Product Characteristic Rule

Prerequisites: Predefined Product Characteristic Rule

To search for a Product Characteristic Rule:

Click Search after entering the search criteria. The search results are displayed in a table containing all the Product Characteristic Rules that meet the search criteria.

Or

An alternative method to search a Product Characteristic 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 Product Characteristic Rule Summary. You can enter the Code, Name, Description, Hierarchy, and Folder of the Product Characteristic Rule and click Search .

The Product Characteristic Rule Summary displays the following information:

Add: Click the Add icon on the page header to build a new Product Characteristic Rule.

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

  • Name:The Product Characteristic Rule's short name.
  • MDBSS Hierarchy: Name of Hierarchy that is used to define Product Characteristic Rule.
  • Folder: The Folder where the Product Characteristic Rule is saved.
  • Last Modified By: The user who last modified the Product Characteristic Rule.
  • Last Modified Date: The Date and Time when the Product Characteristic 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 Product Characteristic Rule.
    • View/Edit: Based on the user privilege assigned, you can either only view or edit existing Product Characteristic Rules. To edit a rule, you must have Read/Write privilege.
    • Save As: You can reuse a Product Characteristic 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 Product Characteristic Rules that you no longer require. Note that only Product Characteristic Rule owners and those with Read/Write privileges can delete Product Characteristic Rules. A Product Characteristic 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 Product Characteristic 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 Product Characteristic Rules that have dependencies. A report of all rules that utilize the selected Product Characteristic Rule is generated.