Versions Compared

Old Version 3

changes.mady.by.user Former user

Saved on

compared with

New Version 4

changes.mady.by.user Kinga Huszno

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. If BATCH ID position #7 = S (LEVEL), the procedure will attempt to resolve the security alias using the SEC ID and SEC ID TYPE combinations by matching SECURITY ID 1 (Field #12), if not NULL, to XREF_SECURITY_ID in the XREFERENCE table, and matching SECURITY ID 1 TYPE (Field #13), if not NULL, to XREF_TYPE:

    Fancy Bullets
    • If one (1) match is found, the procedure will use the value in SECURITY_ALIAS to populate the record and will move to the Constituent insertion logic.
    • If SECURITY ID 1 or SECURITY ID 1 TYPE is NULL, or an alias is not found, the procedure will proceed to Step 2 below.
    • If the count of possible records returned is greater than 1, the procedure will proceed to Step 2 below.

  2. The procedure will match SECURITY ID 2 (Field #14), if not NULL, to XREF_SECURITY_ID in the XREFERENCE table, and match SECURITY ID 2 TYPE (Field #15), if not NULL, to XREF_TYPE:

    fancy-bullets

    • If one (1) match is found, the procedure will use the value in SECURITY_ALIAS to populate the record and will move to the Constituent insertion logic.
    • If SECURITY ID 2 or SECURITY ID 2 TYPE is NULL, or an alias is not found, the procedure will proceed to Step 3 below.
    • If the count of possible records returned is greater than 1, the procedure will proceed to Step 3 below.
  3. The same resolution process will be followed for Fields #16-21 SECID+TYPE combinations until a match is found. If no match is found, the batch will fail with the "Security Cannot Be Resolved" error.