This release uses XSD Revision 252.  

Enhancements

EagleML

New Accounting Extract

The WorkingTrialBalance extract was created. A new complex type and model was added to the XSD.

This issue was tracked as Item #142063.

Added Logic to Include AllocationRatio Field in Warehouse NAV and NAV Multi Extracts

The warehouse NAV daily extracts include the AllocationRatio field, but it was not being populated directly. The AllocationRatio is calculated based on three fields from the ESTAR_ALLOC_PERCENTAGE_HIST. The extract_alloc_ratio.inc include file was created and added to the extract rules for the NAV daily extracts. This include file has the following variables which are used to calculate the AllocationRatio:

• varPortfolioAcctTemp
• varShareClassTemp
• varAccountingDateTemp

This issue was tracked as Item #148398.

Added SharesOutstanding Field to SUBSCRIBEREDEEMEXTRACT

The SharesOutstanding field was added to the SUBSCRIBEREDEEMEXTRACT. This field can be extracted as is from the database or the value in the database can be used in a calculation which considers one of three dates and populates the field in the extract based on the date criteria. The three dates that can be used are:

• PostDate
• AcountingDate (ValidationDate)
• MonthEndAccountingDate

The SharesOutstanding.model group was added to the XSD and extract_acct_subscribe_reedem.xml, extract_asset_properties_fields.inc files were changed to accommodate population of the field.

This issue was tracked as Item #148802.

Added Support for maxeffectivedate to Reference Objects

The maxeffectivedate filter is now supported by the following reference feed types:

• ISSUEVARRATEEXTRACT
• SCHEDULEEXTRACT
• FACTOREXTRACT
• ISSUEEXCHANGEPRICEEXTRACT
• ISSUEFXRATEEXTRACT
• ISSUEPRICEEXTRACT
• ISSUEFXPCRATEEXTRACT
• SSUERRATINGEXTRACT

Before this enhancement, the maxeffectivedate filter was only supported in the RATINGEXTRACT. The corresponding outbound q rules were edited to allow for the filter to be used with the new feeds.

This issue was tracked as Item #148908.

New EagleML Reference Inbound and Outbound Interface

The SecurityOverrides type was added to the XSD. The corresponding object is securityOverrides. This interface allows access to the SECURITYDBO.SECURITY_OVERRIDES database table. The xml-ref_security_overrides.xml rule was created to allow loading and extracts from the table mentioned above.

This issue was tracked as Item #149193.

Created Streaming Functionality in Generic Issuer Extract

Streaming functionality was added to the generic issuer extract. This was crucial since large volume extracts were running extremely slowly or even failing altogether. A new streaming t rule was created for the generic issuer feed type to allow for streaming capabilities.

This issue was tracked as Item #149322.

New Parameter to Control Signage in Warehouse Trade Extract

Some fields in the warehouse extract have to be calculated while others are taken directly from the database. The EnableSignageLogic parameter was introduced to control these fields being calculated or filled in from the database. If this field's value is "Y" then the logic will be enabled.

This issue was tracked as Item #150250.

New Logic for Custom Parameters

If some custom parameters have not been set then the MDC workflow always stays in progress and works with errors. Changed logic for handling of the result of tasks and added logic for handling custom parameters.

This issue was tracked as Item #150406.

Changed Streaming Functionality Result File Name to Not Be Only Correlation Id

The streaming functionality result file would be named with only the correlation Id which was not enough detail for clients to connect results to individual incoming files. The logic in the streaming_task_getinfo.inc file was changed to allow the result file name to contain the incoming file name as well as the correlation Id.

This issue was tracked as Item #150624.

Modified Naming Convention of Releases
The naming convention of the releases has been slightly modified. Changes were made to eagle_mc_installer.prf (estar/tpe/dynamic/msgcenter/eagle_mc/installer) to remove prefixes such as "BR-" or "IN-SPC-". Streams are always installed now. To disable it, the archive name should have "_N" suffix.

This issue was tracked as Item #150946.

EJM

Added Support to Entity Filter in Issue Var Rate Extract

Held only mode entity filter support was added to the ISSUEVARRATEEXTRACT. The extract_issue_variable_rate.xml was edited to allow for the filter to be used for extracts.

This issue was tracked as Item #149761.

Added Support for Entity Selection Filters to All Extracts

There was a problem that would not allow the entity filters to work with the custom where clause in extracts. In held only mode the entityselectiontype and entityselectionvalue filters should have worked in tandem to allow filtering on type and value, but the value filter would not register. The eagle_ml_2-0/extract_filter_entity.inc file was edited to move the filters from the custom where clause to the inner join in the SQL request. This allowed both the entity filters to work consistently together.

This issue was tracked as Item #149984.

Authentication Added to Get EagleML Release from Artifactory

The jfrog.io artifactory was added so that Eagle ACCESS clients could have access to EagleML releases from any artifactory. The retrieve_build.inc file was changed to add authentication to this artifactory.

This issue was tracked as Item #151270.

Software Fixes

EagleML

Added Support to Extension of Issue PC Price Table

There were fields in the Issue PC Price related database table that were not accessible with the core rules and stored procedures. Some information from this table could not be extracted and information couldn't be loaded to this table through EagleML. The xml-ref_exchangeprice.xml rule was changed to accommodate the new fields.

This issue was tracked as Item #149859.

Added Master Coupon Column to ISSUEVARRATEEXTRACT

The SECURITY_MASTER.COUPON column was not accessible by the outbound Issue Var Rate rule. The logic in the outbound rule requires the value stored in this field so the rule would not work properly since the field was inaccessible. The extract_issue_variable_rate.xml rule was changed to allow the master coupon field to be accessed.

This issue was tracked as Item #149953.

Added Missed Elements to XSD

The nextCallDate, nextCallPrice, nextPutDate, nextPutPrice, parCallDate, parPutDate elements were not present in the XSD. They were all part of the schedule object which should be include in EagleML. The elements were added to the new group schedule.model in eagleml-ref-shared-2-0.xsd.

This issue was tracked as Item #150022.

Fixed CHMOD Load Errors

There was an issue with the CHMOD process on Eagle versions 12 and 13. This was caused by the differences between user rights on these versions compared to others. The CHMOD and UNSIP steps were combined to avoid these errors.

This issue was tracked as Item #150925.

Corrected Formatting of Generic Issuer Extract

The extract was appearing as separate reference transactions. Instead, the extract should be one reference transaction with several child nodes for each issuer object. The outbound t rule was edited to allow the extract to appear in the correct format. The streaming t rule that was created in BT149322 also took into consideration the proper format.

This issue was tracked as Item #149323.

Fixed missing Security Details in Generic Issuer Extract

The Generic Issuer Extract did not have the Security Details in the IssuerRole section. The outbound t rule was edited to include the Security Details in the IssuerRole section.

This issue was tracked as Item #149324.

Fixed Missing Xref Types in SMF Extract

There was an issue with the SMF extract where the non-standard xref types would not make it to the underlying model of the SMF extract. The missing xrefs were a misrepresentation of data and therefore finding a way to include them was crucial. The SMF extract was split into several extracts so that the underlying model is included as a separate reference transaction. This allows the non-standard xrefs to be included in these transactions.

This issue was tracked as Item #149573.

Added Extensions Support for Warehouse Position and Open Lot Extracts

There was already support to inbound interfaces for the EagleML extensions, but the outbound interfaces did not support it. The following rules were changed to allow access to the extensions interface:

• eagle_ml-2-0_cm\out\xml\t_warehouse_openlot.xml
• eagle_ml-2-0_cm\out\xml\t_warehouse_position.xml
• eagle_ml-2-0_cm\out\xml\t_warehouse_openlotstreaming.xml
• eagle_ml-2-0_cm\out\xml\t_warehouse_position_streaming.xml
• eagle_ml-2-0_cm\out\xml\t_warehouse_trade_streaming.xml
• eagle_ml-2-0_cm\ dbkeysmap.inceagle_ml-2-0_cm\out\tagvalue\extract_warehouse_openlot.xml
• eagle_ml-2-0_cm\out\tagvalue\extract_warehouse_position.xml

This issue was tracked as Item #149635.

Fixed Issue with Truncation on New Line Symbol

When loading generic SMF objects there would occasionally be an issue with values getting truncated at the new line symbol. This would cause the data going in for loading incomplete and incorrectly populate the database tables. The gen_smf_tags.inc file was changed to make the individual lines to be separated by quotes which would allow for the new line symbol to not be ignored if it was part of the value, therefore not truncating the records.

This issue was tracked as Item #149889.

Fixed False Positive Result in Reference Stream

In the case that a Merger Corporate Action is loaded into the reference stream without tag 302, the security alias look up would return 0. This means that the security alias was not found and the stream should show an error, but it was only returning a warning. An editcheck based on tag 302 was added in the xml-ref_generic_ca.xml rule so that the stream would fail if the tag was not present.

This issue was tracked as Item #149896.

Fixed "security was updated by earlier event" Error

When updating securities an error would occasionally occur which would claim that the security could not be updated since it was updated by a prior event. This error was due to the update date on the incoming record being earlier than the one in the database. To avoid this the inbound rule was changed to add 15 seconds to the current time before setting the update date.

This issue was tracked as Item #150467.

Added Missing Fields to CASHJOURNALEXTRACT

Two fields were requested for the cash journal extract. The two requested fields which were missing were added as well as 19 other new fields.

This issue was tracked as Item #150971.

TSR Parameter Caused Issues with IWS
This variable in w_config_custom.inc include 

<COL TAG="w_simple_tsr" EXPRESSION="'Y'"/>

could cause you issues when trying to access IWS in that environment.

To resolve this issue, the eagle_ml-2-0_cm/eis_config.inc file was updated to include

<COL TAG="SimpleTSR" EXPRESSION="'N'"/>

This issue was tracked as Item #149705.

Issue Deleting NAV Multi Objects When Partition > 1
You were not able to delete NAV Multi Objects when the partition > 1.

The code was updated to resolve this issue.

This issue was tracked as Item #150460.

EJM

Fixed Logic for varFolder

The runpreprocessor was running when it should not have at times.

To resolve this issue, the logic for varFolder was fixed and configuration was added to ignore the unzip runpreprocessor. The eagle_ml-2-0_cm\eis\in\xml\eis_save_file.xml file was edited to include the new logic.

This issue was tracked as Item #146548.

Fixed MCC Errors Related to DB Column Alias Length

There was an issue that was occurring in the out_q stream during extracts. The database column names would receive an alias with a PF_ prefix which would occasionally cause these aliases to exceed 30 characters. This was the maximum length allowed in MCC and therefore when aliases longer than 30 characters were encountered an error would pop up.

Logic was added to the extract_profile_add_column.inc file which checks all fields for length and truncates them to a maximum of 30 characters in the case that they are longer.

This issue was tracked as Item #148697.

I2I

Fixed False Positive for unpacker stream in I2I

There was an issue that would report a success status in the unpacker stream even if had not worked properly in I2I. An edit check was added that would return the proper error in the TSR.

This issue was tracked as Item #150169.