Legacy limits
warning
This file is deprecated and will be removed in Atoti Limits version 4.0.0.
Download sample file: legacy_limits.csv
This file is used to create Limit Definitions in bulk. For information on how to upload Limit Definitions using this file, see Upload new limits.
| Column Name | Description | Required | Value Example |
|---|---|---|---|
| Group | Name of a group of limits. Group is a way of grouping similar limits | N | Equity Desk |
| ID | The Reference ID to the Limits Golden Source Upstream | N | id_desk_00023 |
| Name | The KPI name created in the business cube | Y | Delta |
| Comment | Note about the limit | N | This is a comment |
| Start Date | Effective Start Date | Y | 2020-01-01 |
| End Date | Effective End Date | N | 2020-01-31 |
| Frequency Type | The type of frequency: either OFFICIAL or TEMPORARY. | N | OFFICIAL |
| Polling Frequency | Data time relevancy of the limit (End of day, Start of day, or Intraday) | Y | EOD |
| Kpi Type | The type of KPI (supported types are Greater Than, Less Than) | Y | Greater Than |
| Limit Values | Array of KPI values in the specified currency | Y | [100000,5000] |
| Absolute Value Indicator | Is the Limit Value an absolute value | Y | false |
| Warning Threshold | Percent value from a breach where a user will receive a warning | N | 10 |
| Measure Name | Measure of the KPI | Y | PV |
| Scope | This determines which members the new limit applies to. You can choose any level of the currently selected cube and a corresponding value from said level. An example scope filter is “Desk=Rates”. Multiple scope filters can be added to a single limit definition. Every scope filter is separated by a pipe. | Y | Desk=Bonds|Book=FI_HY_LEGACY |
| Precedence | If a location in the Cube has more than one matched limit applied, the limit with the highest precedence is used. The default is the Integer.MIN in Java. | Y | 100 |
| Limit Status | The limit’s status along the workflow. | Y | APPROVED |
| Limit Changes Workflow | Limit Change workflow type. You can select the are approval type: Four Eye, Six Eyes or Straight Through | N | Four Eyes |
| Limit Changes Workflow Parameters | The party charged with reviewing a limit’s workflow. Potential options are USERS or MANAGERS | N | Examiners=USERS|Approvers=MANAGERS |
| Exception Workflow | Exception workflow type: the workflow that handles a limit with a BREACHED or WARNING status. | N | Exception |
| Utilization Dashboard ID | The ID of a utilization dashboard that may exist for the limit structure. The ID maps to a dashboard ID in the content server. | N | b3a |
| User ID | The limit creator’s user ID | N | Sheila from Risk Control |
| Cube Name | Name of the cube for the KPI | Y | Sensitivity Cube |
| Server Name | Name of the server the cube is running | Y | MRA |