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