The SMF default message stream is used to load securities to specific tables in the SECURITY database, under the control of event field (tag 55), which determines the routing of each message to the appropriate database update stored procedure.
SMF transactions are loaded using the following streams:
- eagle_default_in_csv_smf
- eagle_default_in_star_smf
The ADDSECMASTER bind uses stored procedures INSERT_UPDATE_SECURITY_INFO and UPDATE_NAME_CHANGE_STATUS. Additional sector-related data fields are allowed when Eagle Accounting validation is not invoked, as explained in the [Additional SMF Related Information section.
You must set Event Type (tag 55) to ADDSECMASTER to add securities using this stream.
The following data tables are described for SMF:
|
|
|
|
|
|
|
|
|
|
|
|
[Panels, binds, and stored procedures for the SMF stream are also described in the following pages.
To review the results of processing securities in the database, use the Issue Viewer under the Reference category in Eagle Accounting.
Multilingual Implementation
You can load Issue Names for a security in a foreign language using the following streams:
- eagle_default_in_csv_smf_ml
- eagle_default_in_star_smf_ml
Issue Names in an Eagle multilingual implementation are stored to security tables in the SECURITY database using table names ending in "_ml". An example of data loaded to the SECURITY_MASTER_ML table is shown below.
Resolve Security Alias for the SMF Stream
This section describes guidelines for resolving the security alias (tag 10) using the XREFERENCE table, for transactions processed through the SMF default message stream.
To resolve security alias when using the SMF default message streams:
- Use the tag series 7052 to 7080 to specify an ordered list of xreference ID and types to use for security resolution using the XREFERENCE table. The XREFERENCE table is not updated by the actions of this step. To refine the security lookup, you can specify several secondary fields that, when present, must also match to the XREFERENCE table information for a successful security resolution:
- Asset Currency (tag 85)
- Xref Exchange (tag 1981)
- Inactive Flag (tag 11043)
- Maturity Date (tag 38)
- If unresolved, use the Primary Asset ID (tag 14) to resolve the security.
- If resolved, the tag series 1952 to 1971 is used to maintain the XREFERENCE table by triggering inserts and updates to the XREFERENCE table once the security has been successfully resolved. This tag series does not affect the security resolution process, which uses the 70xx series for resolution.
NOTE: If not resolved using any of the arguments, a new security is assumed and a new security alias is generated.
Restrict Updates to History Tables
You can restrict database updating to only posting to the security history tables by setting Transaction Type (tag 1257) = HISTORY_ONLY.
Add Comment