This release uses XSD Revision 239.

Enhancements

EagleML

Introduced New Fields to the Generic Entity Extract

New fields were added to the Generic Entity Extract. The following fields are now included:

• RULESDBO ENTITY PORT_COMP_TYPE
• RULESDBO ENTITY_STAR_PROCESSING ENTITY_ID
• RULESDBO ENTITY_STAR_PROCESSING SECTOR_TYPE
• RULESDBO ENTITY LEI and RULESDBO ENTITY_DETAIL ENTITY_ID

This issue was tracked as Item #146472.

Added Extended Models to Settled and Traded Cash Activity Extracts

Entity and SMF extended models were added to settled and traded cash activity extracts. The extract_acct_traded_cash_activity.xml, extract_acct_settled_cash_activity.xml, t_acct_traded_cash_activity_streaming.xml and t_acct_settled_cash_activity_streaming.xml rules were all changed to allow for this enhancement.
This issue was tracked as Item #146639.

New Elements Introduced to SUBSCRIBEREDEEMEXTRACT

Additional elements were added to the shareholder mashup extract. The SUBSCRIBEREDEEMEXTRACT rule was edited to allow access to the RULESDBO.ENTITY_SHARE_CLASS table. The following elements were added to this extract:

• className
• classStatus
• transferAgency
• taCode
• classTerminationDt
• classTicker
• classCusip

Each one correlates to a field in the database.
This issue was tracked as Item #146683.

Additional Fields in NAV Month End Extract

The NAV Month End Extract received the following new fields:

• Market Value Base Cash
• Market Value Foreign Cash

The elements were added to the WHNAV extract which allowed them to be leveraged in the NAV month end extract.
This issue was tracked as Item #146860.

Added Binding on Dates in RTR

All extracts will now use bind parameters on dates just like the SMF and entity extracts do. The following rules were updated to make the binding of dates possible for all extracts:

• extract_filter_bind_pars_sql.inc
• extract_filter_date.inc
• extract_filter_date_one.inc

This issue was tracked as Item #146927.

Added Support for Held Only Filters in Xref Extract

Previously, the xref extract did not support the held only filter. The extract feed type (XREFEXTRACT) was added to the estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\ extract_filter_held.inc include file to allow the extracts to use both the held only filter and consequently the entity filters.
This issue was tracked as Item #147067.

Partition Support for SMF Extracts in Held Only Mode

The SMF extract was enhanced to support partitions in held only mode. The extract_smf.xml rule was changed to allow for held only support with partitions.
This issue was tracked as Item #147338.

New Elements in Entity and SMF Common Models

Cost method was added to the entity common mode and issue price and issue country were added to the SMF common model. The element names are entityCostMethod, entityBaseCurrency, and issuePrice. To include in extracts, the IncludeExtendedDetails parameter must be set to "Y".
This issue was tracked as Item #147340.

New Custom Benchmark Interface

The XSD was updated to reflect the new necessary elements for the new Custom Benchmark Interface offered by the Data Integration Services (DIS) team.

Note: This interface is only available to DIS clients.
This issue was tracked as Item #145130.

EJM

Added Separate Warning Line for Overlay Activity

The EagleML package may contain panel overlays. If the target environment contains custom overlays with the same name, the EagleML Installer applies conflict resolution logic. Depending on installation parameters, either existing overlays are backed up, or the ones delivered with the release get installed with a different name. It was not easy to find these details in the Message Center Console's Status tab because they were buried under a lot of information in the standard output of the command line. Now, a separate warning line has been added. This warning line shows only overlay-related activity.
This issue was tracked as Item #145742.

I2I

Added I2I Xref Output Inclusion or Exclusion Functionality

I2I was enhanced to allow you to include or exclude certain xreferences in the output. This feature is based on the configuration of the SPOKE and only available for the SMFEXTRACT feed type. It makes it possible to select the types of xreferences that will be available to the SPOKE. The t_smf.xml and t_streaming_smf.xml outbound rules as well as one common I2I include were all changed to allow for this enhancement.
This issue was tracked as Item #144432.

Software Fixes

EagleML

ENTITY_XREF Node Missed

The ENTITY_XREF node was missing from the TRDC_EGL_GEN_INTERFACE. This node is important for security resolution. The code was changed to ensure that the node would show in the Warehouse Trade Charges interface as well as other related Generic interfaces.
This issue was tracked as Item #131365.

Issue with Logic for the Load Order of Spots and Forward Rates

There was an issue with loading spot FX rates and forward FX rates. The forward rate are dependent on the spot rate and therefore must be loaded after the spot but this was not always occurring. Logic was added to the generic load workflow to allow all spot rates to be loaded before the forward rates are loaded.
This issue was tracked as Item #137515.

Issue with Some Fields in Entity Bank Relationship

Two fields from Entity Bank Relationship were not getting stored in the database upon load. These are:

and

in the XSD. dTCBankId was not mapped correctly and custodyBankAccountName did not have the necessary tag association. The code was updated to resolve these issues.
This issue was tracked as Item #138575.

Corrected Begin Date for Synthetic Securities

The begin date for synthetic securities was incorrectly set as the current date. This behavior was inconsistent with the begin date assigned by the panel. The code in the secmastersynthetic.inc include was edited to make the begin date 19000102 which is consistent with the panel.
This issue was tracked as Item #139894.

EagleML Compatibility for Eagle v2017

EagleML was updated to accommodate some of the changes in the upcoming Eagle v2017 release. Changes included updates to the EagleML inbound rules to accommodate for the changes.
This issue was tracked as Item #141599.

Included fromdate/todate filters for Entity Tables

The entity tables ENTITY_XREFERENCE and LEI_DETAILS did not support the fromdate and todate filters. The extract_entity.xml rule was changed to allow for these filters to function with these newer tables.
This issue was tracked as Item #143639.

Fixed mapping for tag 676

There was in incorrect mapping for tag 676 which had the element name mapped as forwardBrokerCode. This is inconsistent with the schema which shows the element as fwdBrokerCode. The following rules were edited for the mapping change:

• generic_smf_fields_logic.inc
• msgxchg_sec_core.inc
• smf_egl_gen_interface_template.xsl

The mappings now have the field listed as fwdBrokerCode.
This issue was tracked as Item #144243.

Issue With Invalid TSR Related to Consolidated TSR Option

When the option to produce a consolidated TSR is selected for a workflow, there was a scenario in which an invalid TSR could be returned. This could occur due to files having too many errors when being sent for loading. Task reporter rule was modified to handle this condition.
This issue was tracked as Item #145434.

Filter Support for Realized Gain Loss extract

Additional parameters were added to leverage the report execution filters on the Realized Gain Loss extract. The filters include:

• entityIdType
• entityId
• accountingBasis
• reportType
• reportPeriod
• reportStartDate
• reportEndDate
• reportFilters
• filterSecurityBy
• xrefid
• xrefidtype
• primaryassetid
• issuename
• longShort
• eventType
• assetCurrency
• investmentType
• securityType
• processingSecurityType

The extract_acct_realized_gain_loss.xml rule was edited to allow these filters to work properly with the realized gain loss extract.
This issue was tracked as Item #145490.

Performance Improvements to TRADECAEXTRACT and SETTLEDCAEXTRACT

Performance optimization was done to TRADECAEXTRACT and SETTLEDCAEXTRACT. The extract_acct_traded_cash_activity.xml and extract_acct_settled_cash_activity.xml outbound rules were changed as part of the optimization.
This issue was tracked as Item #145891.

Case Sensitivity Issue on Filters for Certain Extracts

The localCurrency filter did not work for the Earned Income Extract. This issue was because the parameters were case sensitive. For example, LocalCurrency would work but locaLcUrrency would not work. There was the same issue in several other extracts as well. The following extracts were updated to allow the filters used to all be case insensitive:

• CASHJOURNALEXTRACT
• CONSEARNEDINCOMEEXTRACT
• OPENRECPAYMULTIEXTRACT
• REALIZEDGAINLOSSEXTRACT

This issue was tracked as Item #146527.

Added Mapping for historyOnlyFlag in Generic Entity

The historyOnlyFlag was not mapped and therefore could not be properly utilized in the generic entity interface. The mapping was added in the xml-ent_entitygeneric.xml (inbound generic entity rule) to resolve this issue.
This issue was tracked as Item #146583.

Fixed Logic for Issue Tax Type Element

The Issue Tax Type had incorrect logic that caused issues during load and would report the element as invalid or missing. The xml-smf_generic.xml rule was changed to fix the logic for this element.
This issue was tracked as Item #146764.

Issue with Issuer Organization Parameters

Parameters were added to the UPDATE_ISSUER_ORGANIZATION (in_history_switch and in_event_name) and INSERT_ISSUER_ORG (in_history_switch) stored procedures but were not functional. This was due to the lack of support for these parameters in the inbound issuer organization rule. The code was updated to resolve this issue. The /eagle_default/in/xml/xml-ref_issuerorganization.xml rule was edited to recognize these parameters.
This issue was tracked as Item #146775.

Fixed Issue With Max Effective Date Calculation in Ratings Extract

In the ratings extract there is functionality that allows you to query for the maxEffectiveDate. This ability was not working properly as a result of incorrect SQL. The original logic was based around source name, whereas the security alias was a required piece to finding the max effective date. To resolve this issue, the security alias was added to the query responsible for retrieving the max effective date. Now the date is calculated based on the source name and security alias pairings. A record is added to the extract for each such pair and the effective date is contained to no more than the value of the maxEffectiveDate parameter.
This issue was tracked as Item #146908.

Added Custom Where Clause Support for the Xref Extract

The Xref Extract did not have support for a custom where clause. Code was added to the xref_extract.xml rule to allow for where this custom clause support.
This issue was tracked as Item #146919.

Issue with Null Values Sent to ENTITY_EXTENSION_HIST Table

There was an issue updating NULL data values for historical records in the ENTITY_EXTENSION_HIST table. To resolve this issue, logic was created in the eagle_default\in\xml\xml-ent_entitygeneric.xml rule to allow the conversion of null values to database acceptable equivalents.
This issue was tracked as Item #147210.

Corrected Mapping in Entity Common Model Extension

The elements accountType, parentCompositeId and counterpartyId were mapped incorrectly. This resulted in the database fields being populated with the incorrect values. These mappings were corrected.
This issue was tracked as Item #147372.

Duplicate Records Issues For Extracts that Use extended models

There was a scenario in which duplicate rows appeared in the output of warehouse extracts as a result of the join to the underlying security table. The common include for underlying table join was modified. It will no longer return duplicates.
This issue was tracked as Item #147507.

Corrected Issuer Logic

An enhancement was included in the EagleML Nov 2016 release around adding issuers for existing role objects. However, this code incorrectly expected that when you created a new issuer, you would include a date for that new issuer to expire. The code was corrected to allow you to not send in an expiration date for the new issuer.
This issue was tracked as Item #147582.

Xref Issue for Currency Forwards

For currency Forward, xreference identifiers (except for Primary and Ticker) were not being stored in the database. This issue was a result of incorrect code, where the identifiers were parsed and sent to the panel. The code was updated to resolve this issue.
This issue was tracked as Item #147638.

Edited debtToCapital Element

There was in issue with the debtToCapital mapping in the wrh_egl_gen_interface3.xsl.bThe incoming field was named as in_debt_to_capt which was not consistent with the database field name which was in_debt_to_capital. The mapping in the XSLTwas changed so that there would be consistency between the incoming parameter and the database field.
This issue was tracked as Item #147667.

EJM

Changes to Eas_distribution_light.xml Rule

Some elements in the eas_distribution_light.xml rule were changed. The varSubCategory element value was changed to "Other" and the varNewIncident field now uses a conditional statement that will assign a value of "Y" in the case of a warning and "N" in the case of an error.
This issue was tracked as Item #144803.

Fixed Time Out Issue with PACE Extracts

PACE extracts could fail as a result of time out conditions. In the extract rule there is a move command (mv) that is responsible for relocating a file from one folder to another. In the case that the compression parameter was set to "N" (indicating that the extract would not be zipped), the mv command would wait for your response and therefore never actually execute. The /eagle_extractor/eagle_extractor_cm_execute_zip.xml rule was changed so that the mv command became a mv -f command, which removed the need for a response requirement. The extract now works as intended.
This issue was tracked as Item #145737.

Fixed Issue with Future Creation Timestamp on EJM Jobs

There was a bug that caused EJM jobs to be timestamped in the future. This occurred due to the way the calculation used the local time zone. The code had a literal value of -05:00 for the time zone which is correct as far as the EST (Eastern Standard Time) is concerned. Due to day light savings, however, this time zone is no longer correct in the winter months as the EST transfers to the EDT (Eastern Daylight Time) also known as Eastern Daylight Savings Time (EDST). EDT as opposed to EST is actually -04:00. The logic for calculating the timestamp now involves distinguishing when EST vs EDT are the active time zone. The TSR now has the correct timestamp.
This issue was tracked as Item #146479.

Added Parameters to Parameter Overrides in Generic Purge and Archive Workflow

To address a gap when running in Automation Center, new CustomPurgeArchiveParams added to the parameters in the eagle_wrf_generic_purge_archive. The new parameters were added to the Begin step of the workflow.
This issue was tracked as Item #147362.