SMF MI Inbound Interface

Owned by Natalie Gesin (Deactivated)
Last updated: Oct 23, 2024 by Kinga Huszno
2 min read

Overview

SMF MI is not recommended for new implementations or upgrades. Clients should switch their integration to use GenericSMF and other Reference streams.

Smf_mi was designed to load the SMF along with objects related to it. This means that you should use smf_mi when you want to load specific model(s), like Issuer model, Schedule model etc.

Please note, that smf_mi should not be used for volume data load or in processes sensitive to load speed.

Issuer Role Load

Issuer Role can be loaded 

  • with a dedicated interface Reference Issuer Role via eagle_ml-2-0_default_in_xml_reference stream (objectType = IssuerRole, the message should be formatted as an <issuerRole> message) - read more on Issuer Role Inbound Interface page.

  • with SMF MI stream (objectType = GenericSMF, the message should be formatted as a <genericSMF> message) 

Batch Mode Specifics

SMF MI supports Issuer Role batch load. In order to turn it on you should have EagleML/referenceTransaction/header/processingOptions/ set to ISSUER_ROLE_GROUPING in the incoming SMF:

<header> <objectType>GenericSMF</objectType> <processingOptions>ISSUER_ROLE_GROUPING</processingOptions> </header>

 This can be turned off by adding a counter-flag DIRECT_ISSUER_ROLE_OPTIONS 

<header> <objectType>GenericSMF</objectType> <processingOptions>ISSUER_ROLE_GROUPING,ISSUER_ROLE_GROUPING</processingOptions> </header>

which allows to set processing options directly.

Here is the list of available processing options:

  • ISSUER_ROLE_GROUPING - enables batch mode (also enables ISSUE_ROLE_UPSERT_MODE, USE_LATEST_START_DATE by default) 

    Note: ISSUER_ROLE_GROUPING has no sense outside of SMF MI interface

  • ISSUE_ROLE_UPSERT_MODE - prevents the delete step in batch mode

  • USE_LATEST_START_DATE - finds the latest start date in the incoming message and uses it for each incoming record as the start date

  • DIRECT_ISSUER_ROLE_OPTIONS - counter-flag for ISSUER_ROLE_GROUPING, allows to set options directly

  • ISSUER_ROLE_PROCESSING_TYPE

    set as ISSUER_ROLE_PROCESSING_TYPE_I()__PROCESSING_TYPE

    where in I() you should set Issuer Role types which you want to be loaded in certain mode

    For example, you want to switch off default behavior and load only OWNER roles in UPSERT mode:

<processingOptions>ISSUER_ROLE_GROUPING,DIRECT_ISSUER_ROLE_OPTIONS,ISSUER_ROLE_PROCESSING_TYPE_I(OWNER)__ISSUE_ROLE_UPSERT_MODE</processingOptions>

Issue Variable Rate Model - Load Details

When you load Issue Variable Rate please note that some important values, such as source, effective date and variable rate, should be specified in the following elements (which do not belong to the Issue Variable Rate model):

EagleML/referenceTransaction/genericSMF/sourceName populates the source name field on the securitydbo.variable_rate table
EagleML/referenceTransaction/genericSMF/FloaterModel/beginDate populates the effective date field on the securitydbo.variable_rate table
EagleML/referenceTransaction/genericSMF/FloaterModel/rate field populates the variable rate field on the securitydbo.variable_rate table

 

Â