Pricing Grid

Specifies the criteria that forms the pricing grid. The criteria can be associated with date periods, risk profile of the borrower and utilised amount of the facility. Each Grid Criterion must be defined in the system so that the system knows from where the data should be taken during processing.

The user can define the grid criteria at:

• Drawing Arrangement (for example, drawing currency)
• Facility Arrangement (for example, facility utilised amount)
• Customer (for example, borrower risk rating)
• Collateral pool (for example, LTV)

It has to be a valid record from the AA.DATA.ELEMENT table. When defining a pricing grid, the criteria to be used are selected and their order of precedence is defined. The order in which the data element is entered is a precedence order. It is a multi-value field. A maximum of 10 multi-values are allowed. If a target is defined, at least one criterion must be available.

• Specifies the target(s) element defined under the grid.
• It has to be a valid record from the AA.TARGET.ELEMENT table.
• Associated multi-value set.

• This field contains default target value to be used if none of the criteria combinations are satisfied at runtime.
• Each target defined has a default value.
• This field is mandatory for Fixed Rate targets and optional for margin targets.
• It accepts any numeral.

Specifies a set of 10 criterion fields that stores the grid values of the criterion selected by the user.

Specifies a set of 10 target fields that stores the grid values of the target(s) selected by the user.

If Criteria field is set as Balance, then the user can setup this field as LEVEL or BAND.

Unique ID defined by the user

The description of the data element

This is a mandatory field, which defines if the data element is balance, field or property. When Pricing Grid is defined, this is an Interest property. When the Type field is set as,

• Field - DATA SOURCE is mandatory.
• Balance - DATA SOURCE can only be ARRANGEMENT.
• Property - No other input is required in the table. 

This is a conditional mandatory field and it defines the source from where the data element is retrieved. It allows one of the following options:

• Arrangement
• Customer
• Collateral
• Evidence

The data is directly referenced from CUSTOMER and COLLATERAL applications. When the ARRANGEMENT is chosen, the data can be referenced from an existing arrangement; else, it refers to the Interest or Account Property Class. 

• This is a conditional mandatory field.
• The user can enter a value in this  field, when the Data Source field is set as ARRANGEMENT.
• At runtime, the system either retrieves the data value from the arrangement processed or from its parent.
• When a value is not entered in this field (NULL), the system defaults to ‘Self’ arrangement, during validation.
• Allowed values are Self and Parent

Conditional mandatory field. The user can enter a value in this field, when Data Source field is set as ARRANGEMENT. Required if Data Source field is specified. Allowed values are:

• Interest
• Account
• Arrangement

• Mandatory field.
• The field name in Customer or Limit or Collateral module or the Arrangement source where the data is located.
• When the Type is set as ‘Field’, then the actual field is validated for its presence against the respective Module. 
• When it is an ARRANGEMENT, the field is validated against the ARRANGEMENT SOURCE mentioned that is, the AA.ARRANGEMENT table or the respective AA.ARR.PROPERTY. 

• Optional field.
• Specifies the relevant options valid for the Field.

• Balance to be retrieved.
• Refers to a valid AA balance type when Field is set to ‘Balance’.

• Optional field
• Defaulted by referring to SOURCE application.
• It is a system-updated field but can be modified by the user.

• Optional field.
• Valid check file is available in Transact. If the Field is linked to a check file, this the system-updated field contains the table name.

• Conditional mandatory field.
• This field is mandatory when Data Check File is entered.
• The user can provide selection criteria for the Transact, to filter the list of IDs to present to the user.
• If the field name mentioned is valid in the check file, then the system checks if the field name and value should be separated by an operand.
• If the format is incorrect, then an error message is displayed.
• If there are multiple values, then it should be separated by a space. For example, SECTOR == '2000' .There can only be one condition indicated in this field. The format of the field is <'Field name' OPERAND 'Value'. Allowed operands are == and!=>

Mandatory field. Defines a catch all ‘value’ in a pricing grid. It provides option to indicate if it is mandatory or optional for a grid definition. Allowed values are:

• None
• Mandatory
• Optional

A multi-language field to create a meaningful label. When Catch All field value is set as Mandatory or Optional, then a value is allowed in this field.

It is a unique ID defined by the user

A meaningful description of the Target Element

It is a mandatory field. Allowed values are:

• Margin Type
• Fixed Rate

• Defaulted based on the value selected in Type field.
• If Type field is set as ‘Fixed Rate’, then one row with Field value as ‘FIXED RATE’ should be defaulted.
• If Type is ‘Margin Type’, then three rows with Field value as ‘MARGIN.TYPE’, MARGIN.OPER’ and ‘MARGIN.RATE’ are defaulted. These values should be valid fields in the AA.ARR.INTEREST table.
• System maintained field.

• The system defaults the data type of the respective field defined. 
• System maintained field.

Indicates whether each field value is  pre-defined or is entered. Allowed values are:

• Defined
• Input

• If Value Type is set as ‘Defined’, then the value should be pre-defined in the EB.LOOKUP table.
• If Value Type is set as ‘Input’, then necessary value is for structuring the grid