A ledger conversion reclassifies ledger balances for lots with a holding term of cash equivalent or short term. The ledger conversion reclassifies ledger balances only for the accounts Cost of Investments and Investment Interest Receivable from the core account to the corresponding short term and cash equivalent accounts. Reclass entries are based on cost lot field: Amortized Cost (local and base) and Period to Date Accrued Interest (local and base). The reclass entries have an accounting date equal to the ledger granularity rule's effective date specified on the entity/accounting basis.
| Note |
|---|
Eagle assumes that before you perform a holding term conversion, you set up ledger granularity rules based on holding term and assign those rules to the appropriate entity/accounting basis groupings. You must also update any lots that require a holding term trade level override using the Non Financial Trade Data Modification panel in the Book Trade tool. Eagle assumes that you will perform a holding term conversion after you perform year end processing so that all other holding term accounts are cleared out. Accounts that are closed out, such as realized gains/losses and income distribution, are not converted as part of this process as they are expected to have a zero balance at the start of a new fiscal year. |
To perform a holding term conversion:
- Do one of the following:
- In Portfolio Data Center, in the left navigation pane, click Portfolio Desk > Accounting Portfolio Rules > Ledger Granularity> Holding Term Conversion.
- In Accounting Center, in the left navigation pane, click Setup > Admin Portfolio Rules > Ledger Granularity > Holding > Holding Term Conversion.
You see the Holding Term Conversion panel. - Complete the options in the Holding Term Conversion panel.
You initially set the Conversion Type field to a value of Lot Level Conversion to update existing holdings with the appropriate holding term value. You can then use the panel to set the Conversion Type field to a value of Ledger Conversion to reclassify ledger entries into the long term/short term/cash equivalent breakout for the converted lots. - Click Submit.
Holding Term Conversion Panel Options
The following are the options in the Holding Term Conversion panel.
| Option | Tag | Description |
|---|---|---|
| Selection Criteria | ||
| Select Query Option | 2283 | Indicates whether to convert holding term information for one or all entities and securities. Options include:
|
| Conversion Type | 3914 | Identifies the type of holding term information to convert. Option include:
|
| Process Center | 4896 | Specifies the entity's process center. This field appears if you set the Select Query Option field to All Entities/All Securities. |
| Partition | 95 | Specifies the entity partition code. This field appears if you set the Select Query Option field to All Entities/One Security or All Entities/All Securities. |
| Entity Information | ||
| Entity Name | 1164 | Specifies the name of the entity. The entity you select must have a ledger granularity rule assigned to at least one of its accounting bases. This field appears if you set the Select Query Option field to One Entity/One Security or One Entity/All Securities. |
| Entity ID | 1163 | Specifies the unique identifier of the entity. This field appears if you set the Select Query Option field to One Entity/One Security or One Entity/All Securities. |
| Security Information | ||
| Long Short | 15 | Specifies the long/short indicator for lots to select for the holding term conversion. Options include Long and Short. This field appears if you set the Select Query Option field to One Entity/One Security or All Entities/One Security. |
| Asset ID Type | 1432 | Specifies the asset ID type of the security. This field appears if you set the Select Query Option field to One Entity/One Security or All Entities/One Security. |
| Primary Asset ID | 14 | Specifies the primary asset ID type of the security. This field appears if you set the Select Query Option field to One Entity/One Security or All Entities/One Security. |
| Issue Name | 961 | Specifies the issue name of the security. This field appears if you set the Select Query Option field to One Entity/One Security or All Entities/One Security. |
| Conversion Date | 3915 | Specifies the conversion date if you want the system to update positions with zero quantity (that is, fully closed). The system updates positions with zero quantity if the last transaction processed for that position occurs after the conversion date. You can specify a date less than the accounting date of the conversion, which occurs on the current date. This field appears if you set the Conversion Type field to a value of Lot Level Conversion. |
| Holding Term | 9091 | Specifies the holding term value to assign to lots in the selected position during a lot level conversion. This field appears if you set the Select Query Option field to One Entity/One Security or All Entities/One Security. Options include:
|
Perform a Custom Granularity Conversion
In the Custom Granularity Conversion panel, you can convert ledger data based on your custom granularity rules. The system updates existing ledger account records to reflect custom granularity rules where you break out core ledger accounts to custom accounts using ledger granularity rules based on criteria such as processing security type, security attributes, and security groupings. Updates made with the Custom Granularity Conversion panel have no effect on pre conversion ledger data.
After you convert your custom granularity data, you can use the Custom Granularity Reload panel to update ledger accounts on an ongoing basis. See the Update Custom Ledger Accounts section for more information.
| Note |
|---|
If you are converting data for use with ledger granularity rules that use both holding term and custom granularity, you first use the Holding Term Conversion panel to update lots with the holding term and update ledger data to reflect holding term granularity rules. Afterwards, you use the Custom Granularity Conversion panel to convert ledger data based on custom granularity rules. |
To perform a custom granularity conversion:
- Do one of the following:
- In Portfolio Data Center, in the left navigation pane, click Portfolio Desk > Accounting Portfolio Rules > Ledger Granularity> Custom Granularity Conversion.
- In Accounting Center, in the left navigation pane, click Setup > Admin Portfolio Rules > Ledger Granularity > Custom > Custom Granularity Conversion.
You see the Custom Granularity Conversion panel. - In the Select Query Option field, select One Entity to update a single entity or select All Entities to update all entities.
Additional options appear depending on the value you select. - If you selected One Entity, enter the name or identifier of the entity you want to update in the Entity Name and Entity ID fields.
- If you selected All Entities, you can restrict the conversion to a specified Process Center and/or partition by entering a value in the Process Center field and the Partition field.
- Click Submit.
Troubleshooting Issues with Custom Granularity Conversions and Reloads
When you use the Custom Granularity Conversion panel or use the Custom Granularity Reload panel, the system creates entries with the system date in the CUSTOM_GRAN_UPDATE_LOG table for every entity/accounting basis run, and writes the following status codes to that log table. If you encounter an issue during processing, you can review the statuses and run times in this table to help isolate where the issue lies. See the Perform a Custom Granularity Reload section for more information about the reload process.
The following are the status codes.
| Option | Description |
|---|---|
| LOADSTART | Indicates that Loadconv or Reload started. |
| SGLOAD | Indicates Loadconv finished security grouping run, but did not yet run PST. |
| LGLOAD | Indicates Loadconv finished both security grouping and PST runs. |
| SGRELOAD | Indicates Reload finished security grouping run, but did not yet run PST. |
| LGRELOAD | Indicates Reload finished both security grouping and PST runs. |
| SGBATCHUPD | Indicates Batch-update finished security grouping run, but did not yet run PST. |
| LGBATCHUPD | Indicates Batch-update finished both security grouping and PST runs. |