Batting Order Specifics

Owned by Copy Page Tree (Unlicensed)
Last updated: Jun 07, 2022 by Anna Krapivina
3 min read

Batting order determines the order of the reference identifiers for matching.

Important Note

  • The batting order provides the order for matching.  However, you must populate the Security Resolution parameter to define which xref types you want to actually match on.  
  • Xref types that are listed in the batting order but NOT included in your security resolution parameter are IGNORED during security resolution.

The default batting order contains all possible identifiers, which can be specified in an incoming message. This default value of batting order is used when batting order is not specified.  

By default, the preset value of the of batting order is:

‘cusip,isin,sedol,reuters,bloombergId,sicovmId,valorenId,cedel,internalId,cinsId,ticker,xId1,xId2,xId3,xId4,xId5,xId6,xId7,xId8,xId9,xId10,uniqueProductId,uniqueSwapId’.

If you do not want to use the default batting order, you can change the it for all workflows using the Config Batting Order or for one individual workflow using the Specific Batting Order or to a single record using a Specific Batting Order on Message Node.

Note

  • If you use Config Batting Order, this takes priority over the regular default Batting Order for all your workflows.  So if you have set Config Battting order, the default batting order listed above does not apply.
  • If you use Specific Batting Order, that will take priority over the Config Batting Order and the default Batting Order for that particular workflow.
  • If you set the batting order on the node of your message, that will take priority over any other batting orders but only for that single, current record.

Config Batting Order (All Workflows)

You can specify a batting order for all workflows that differs from the default.

It is set in the custom configuration file eagle_ml-2-0_custom_cm/w_config_custom.inc.

To edit config batting order, open the custom configuration file in Message Center Editor and define the ‘CONFIG_BATTING_ORDER’ variable.

Specific Batting Order (Single Workflow)

Specific batting order is used to define the batting order for a single workflow.

It can be set inside the transform solution in IWS.

Specific batting order has higher priority than default and batting order for security resolution, but only for the workflow in which specific batting order is set.

To set a specific batting order, edit the ‘battingOrder’ field in Destination grid.

Click   button near the function text box to apply changes. Save and Export the solution.

Specific Batting Order on Message Node (Single Message) 

The specific batting order is used to define transformations that should occur for one record in the xml  in the source file.

The specific batting order will have the higher priority relative to default and batting order for the security transformation, but only for the current record where specific batting order is set.

To use it, you should fill the batting order node of your message (refer to the data map table of the object and make sure the node is placed in agreement with the XSDs).

<battingOrder>sicovmId,valorenId,cedel</battingOrder>

For example: 

<EagleML>
    <header>
    ...
    </header> 
    <referenceTransaction><!—this record will use the batting order specified below> 
        <header>
        ...
        </header>
        <genericIssueAnalytic> 
            ...
            <battingOrder>sicovmId,valorenId,cedel</battingOrder>
            ...
        </genericIssueAnalytic>
    </referenceTransaction>
    <referenceTransaction><!—this record will use default batting order>
        <header>
        ...
        </header>
        <genericIssueAnalytic> 
        ...
        </genericIssueAnalytic>
    <referenceTransaction>
</EagleML>Â