Versions Compared

Key

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

In this page:

...

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

Issuer Role

...

Load

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:

Code Block
languagexml
<header>
   <objectType>GenericSMF</objectType>
   <processingOptions>ISSUER_ROLE_GROUPING</processingOptions>
</header>

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

Code Block
languagexml
<header>
   <objectType>GenericSMF</objectType>
   <processingOptions>ISSUER_ROLE_GROUPING,ISSUER_ROLE_GROUPING</processingOptions>
</header>

...

  • ISSUER_ROLE_GROUPING - enables batch mode (also enables ISSUE_ROLE_UPSERT_MODE, USE_LATEST_START_DATE by default)
  • 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:


    Expand

    <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

...