Reusing Cross Reference Identifiers Best Practices

The following process should be used in the case of a security that has been reissued under the same identifier(s). Eagle can support duplicate cross reference identifiers (xref IDs) by adjusting your Security Cross Reference Configuration, but in most cases you want to maintain uniqueness for market identifiers; especially those used as Primary Asset ID Type (1432).

The steps listed below outline the workflow for reusing xref IDs.

1. When a new security needs to be set up using the same identifier(s), you must edit the old security first
2. Verify that there are no current holdings of the old Primary Asset ID (14)
   1. This can be done using Position Viewer by selecting All Portfolios in the Query Based On field
   2. Enter the Primary Asset ID, and all portfolios that ever traded the identifier will be returned
   3. Verify the quantity is zero for all portfolios returned
3. Change Primary Asset ID Type on the old security from the current value to INTERNAL
4. Change Primary Asset ID from XXXXXXXXX to XXXXXXXXXOLD
   1. For subsequent changes use OLD2, OLD3, etc.
5. Change all other xref IDs from XXXXX to XXXXXOLD
   1. For subsequent changes use OLD2, OLD3, etc.
6. Optional: change Issue Name from XXXXX to XXXXX OLD
   1. This is not required, but will make searching by Issue Name easier in the future
   2. For subsequent changes use OLD2, OLD3, etc.
7. Save changes
   1. Historical information can be accessed using the Security Alias, revised Primary Asset ID (XXXXXXXXXOLD), revised xref IDs (XXXXXOLD), or revised Issue Name (XXXXX OLD)
8. Add the new security with the market Primary Asset ID, xref IDs, and Issue Name