5.2.4 Payment Patterns

User defined payment patterns allow you to define custom repayment patterns for products in your portfolio. You can include a payment pattern while generating cash flows by entering the payment pattern code for the instrument.

This chapter describes the procedure for capturing instrument payment patterns that are too complex to be accommodated in the standard fields of Instrument tables.

The procedure for working with and managing Payment Patterns is, similar to that of other Oracle assumption rules.

Payment Pattern Summary

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

Figure 5-48 Payment Summary

Search Payment Pattern

Prerequisites: Predefined Payment Pattern

To search for a Payment Pattern:

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

Or

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

The Payment Pattern Summary displays the following information:

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

• Name: The Payment Pattern's short name.
• Pattern Type: The Payment Pattern Type, such as Absolute or Relative.
• Created By: The Name of the user who created the Payment Pattern.
• Created Date: The Date and Time at which the Payment Pattern was created.
• Last Modified By: The user who last modified the Payment Pattern.
• Last Modified Date: The Date and Time when the Payment Pattern was last modified.
• Action: Click this icon to view a list of actions that you can perform on the Payment 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 Payment Patterns. To edit a rule, you must have Read/Write privilege.
  • Save As: You can reuse a Payment 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 Payment Patterns that you no longer require. Note that only Payment Pattern owners and those with Read/Write privileges can delete Payment Patterns. A Payment Pattern 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 Payment 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 Payment Patterns that have dependencies. A report of all rules that utilize the selected Payment Pattern is generated.

Also See:

• Creating Payment Patterns