This release uses XSD Revision 235.

Enhancements

EagleML

Created New NAV Month End Extract

A new extract was created for NAV Month End. A new XSD object and outbound rules were added to support this new extract.
This issue was tracked as Item #137594.

Effective Date field Removed from Issuer Relationship Query

The effective_date element is not required to resolve an issuer relationship object. The field was removed form the issuer relationship query so that the query no longer requires an effective date for the object.
This issue was tracked as Item #137955.

New Warehouse Open Lot Mashup Extract

There was a need to organize the open lot extract by brokers. To address this need, a new extract feed called WRHSOPENLOTBROKERROLLUPEXTRACT was created. This feed pulls the open lot extract with roll up that uses element reduction as well as grouping by broker.
This issue was tracked as Item #140962.

Added New Core Holding Block Extract

A new extract was added that combines fields from entity, SMF, and accounting periods. This allows you to see relevant information in one file rather than having to do three separate extracts. The following files were changed to allow for this extract to function:

• extract_asset_properties_fields.inc
• extract_entity_fields.inc
• extract_acct_trial_balance.xml
• extract_warehouse_openlot.xml
• extract_warehouse_position.xml

Note: You will need the task parameterIncludeExtendedDetails=Y in your RTR .  You can read more details about this on the Asset Properties Model Data Map Table page.
This issue was tracked as Item #142479.

New EagleML stream for MDC Lineage Extract

A new Metadata Center (MDC) lineage extract was created. It was based on the EAGLEKB.PKG_MDB_LINEAGE.QRY_LINEAGE_REPORT stored procedure. The following rules were created to enable the use of the outbound q and t EagleML streams:

• eagle_ml-2-0_cm/out/tagvalue/ extract_ref_mdc_leneage_graph.xml
• eagle_ml-2-0_cm/out/xml/ t_ref_mdc_leneage_graph.xml
• eagle_ml-2-0_cm/out/xml/ t_ref_mdc_leneage_graph_streaming.xml

This issue was tracked as Item #143388.

Introduced New Parameter for Effective Date

Previously, you could not use date rules when using the heldeffectivedate parameter. This limited the actions that could be performed when this parameter is used. A new parameter called heldeffectivedaterule was created to specify a date rule to be used.
This issue was tracked as Item #144723.

Enhanced Logic for Adding Issuer for Existing Role Objects

There was a demand to enhance the handling of new issuers for existing role objects. When adding issuer information, there are guidelines that allow only one role type per security. When adding a new issuer to an existing role type the correct practice is to end the current role and add the new issuer to the existing role type. This was accomplished by logic that allows the end date of the role type to be updated as the current date and also for a new row to be created in the issuer_role_details and issuer_role_details_hist tables for the new issuer and the existing role type.
This issue was tracked as Item #144764.

Added Date Rule Support for Panel-Based Extracts

There was no support for date rules in the panel-based feed types of extracts. The code was enhanced and date filters were created for the panel-based feeds and supporting date rules were included for each filter on the extracts.
This issue was tracked as Item #144765.

Added New Parameter for Delta Mode Extracts

A new SPDDELTA object flag can now be used in an RTR to extract positions that have been closed out fully when using the delta flag. The flag utilizes a new query that was built on the combination of the position and open lot extracts. This new query uses the SPD_delta table to extract the closed positions.
This issue was tracked as Item #145744.

Added Support for Extract of Non-primary Accounting Basis

EagleML was enhanced to allow for the extraction of non-primary accounting basis. This was accomplished by adding a parameter that will trigger logic to extract the other accounting basis. This parameter is named UseAllAcctBasis and will work when set to "Y".

Note: The default logic is still to extract the primary accounting basis.
This issue was tracked as Item #146051.

Added Streaming Capabilities to the Accounting Periods Extract

Previously, the accounting periods extract did not have the capability for streaming. A streaming t rule was created for this extract.
This issue was tracked as Item #146094.

New Filters for Accounting Periods

New start date and end date filters were added to the accounting period extract. The following files were changed:

• eagle_ml-2-0_cm\out\tagvalue\extract_entity_accounting_periods.xml
• eagle_ml-2-0_cm\extract_filter_date.inc

This issue was tracked as Item #146435.

EJM

Made CustomLocations and TSRStrictPatternForIWS Parameter Conditional

If you used the parameters CustomReplyLocationForIWS and TSRStrictPatternForIWS, the TSR was always sent in to the directory, even if the status of the message is SUCCESS. The code was enhanced so that it uses CustomReplyLocationForIWS and TSRStrictPatternForIWS only when the status of TSR is FAILED.

Note: This enhancement applies only to Reply messages. It is not applicable to Acknowledgements (ACKs).
This issue was tracked as Item #143239.

Remove Temporary Files

When extracts are processed through the q stream, there would be several copies of the same files created and stored at different locations such as the cmw staging folder. The code was enhanced. Instead of using the cmw staging folder, it now has the ability to move and add them to the EJM process, effectively purging the file from the staging folder.
This issue was tracked as Item #146364.

Software Fixes

EagleML

Updates to eagle_mc_import_support_data Stream

There were a few rule files missing when the eagle_mc_import_support_data stream installation was run. The lack of rule files would not allow for the stream to be installed correctly. The code was updated to resolve this issue and the installation now runs as intended.
This issue was tracked as Item #137960.

Issue with Entity Share Class Extract

The final step of the ENTITYSHARECLASSEXTRACT feed type was incorrect. It was actually coded for the ENTITYENTITLEMENTLISTEXTRACT feed type instead. The code was updated so that the last step correctly references the ENTITYSHARECLASSEXTRACT feed type now. The extract now works as expected.
This issue was tracked as Item #144159.

Issue with ChartOfAccountName in Cust Ledger Acct extract

The ChartOfAccountName parameter was not being transmitted to the extract_accounting_custom_ledger_acct step of the custom ledger account extract (which runs in the eagle_wrf_generic_extract workflow). The code was updated and the parameter was added to the step. The extract now runs as expected.
This issue was tracked as Item #144160.

Issue with SOAP Password in Custom Config

In the w_config_custom.inc file there are lines that specify the login and password required for SOAP authentication. When the password would expire, the authentication for the SOAP would fail. To resolve this issue, the login and password were both removed form the w_config_custom.inc file. This information is now pulled by a query from the database every time the SOAP authentication is triggered.
This issue was tracked as Item #144161.

Added Common Include for Partition Resolution

The engine is capable of processing partitions. Therefore, all extracts should be able to use common partitions. The file extract_filter_entity.inc was created as the common include file. The following rules were updated as part of this change:

• extract_warehouse_custody_activity.xml
• extract_warehouse_spd_delta_log.xml
• extract_sorting_sql.inc

This issue was tracked as Item #144831.

Performance Optimization for Trade and SMF Extracts

There could be performance issues with of the q stream of the Trade and SMF Extracts. Performance tuning was done for these extracts. The outbound q rules were changed to allow the extracts to run more optimally.
This issue was tracked as Item #145745.

Issue with ExchangeRateDate in Warehouse Position Extract

The exchangeRateDate was not returning any data due to an incorrect table path. The table was incorrectly listed as POSITION_COST_DETAIL.EXCHANGE_RATE_DATE. The code was updated. The table reference was switched to POSITION_DETAIL.EXCHANGE_RATE_DATE. The exchangeRateDate is now extracted as expected.
This issue was tracked as Item #145767.

Settlement Currency (Tag 63) Defaulted to USD

Settlement Currency (Tag 63) was always defaulting to USD when processing Forwards through the Accounting Trades object. The code was updated so Tag 63 is now mapped and will be filled in with the proper currency from the incoming message.
This issue was tracked as Item #145778.

Changed Key used by Cash Journal Extract

The cash journal extract could have issues since the grouping key was set to event id followed by event type. Some entries do not have either of those two fields and therefore the key needs to be adjusted. To resolve the issue, the key was expanded to include the security alias and the detail indicator.
This issue was tracked as Item #145963.

BaseCurrency was not included in Warehouse Position Extract

The base currency field as not included in Warehouse Position Extract. The underlying SQL variable name that is responsible for grabbing the data for this field from the database was changed in a recent release. The code was updated. The rule for the warehouse position extract was updated to the changed variable name.
This issue was tracked as Item #146158.

Corrected TSR formatting for Cash Projections Extract

The TSR message for the Cash Projections extract was formatted properly and the XML was not well formed. This could cause response issues with the extract. The logic for altAssetIdAndType was moved from the t_acct_cash_journal.xml and t_cash_projections_streaming.xml rules to the t_asset_identifiers_fields.inc and t_asset_identifiers_fields_streaming.inc includes. The extract now performs as expected.
This issue was tracked as Item #146528.

Issue with Cross Changes Indicator

There was an inconsistency with the Cross Changes Indicator. It was in the inbound rule as entityTransaction/benchmarkAssignment/processCrossCHG but the XSD mapped it as benchmarkAssignment\processCrossChangesIndicator. This issue was resolved. The element processCrossCHG has been replaced by element processCrossChangesIndicator in Entity Benchmark Assignment inbound rule according the XSD schema.
This issue was tracked as Item #146991.

EJM

Resolved Issue with Duplicate Sub-processes when Message Center Restarted

When Message Center is restarted, any action that was running before the restart was duplicated and launched again. This can lead to either one failing or both creating their own branch. To resolve this issue, the code in orch_param_add.inc was changed. Two new variables subprocessCorrIdBase and wrfStepNumber were created to ensure that only the correct branch is followed and the other one is cancelled.
This issue was tracked as Item #140003.

Incorrect Statuses Could Occur With Automated EagleML Server Installation Process

The Automated EagleML Server Installation Process could display success statuses when it actually completed with some errors. The following rules received an edit check so that if the MSGEXCHANGE or RUNPROCESSOR fail, the status will be marked as failed:

• eagle_mc_server_support_chmod.xml
• eagle_mc_server_support_cleanup.xml
• eagle_mc_server_support_eagle_version.xml
• eagle_mc_server_support_stream_install.xml
• eagle_mc_server_support_ulimit.xml
• eagle_mc_server_support_upload_log.xml
• eagle_mc_server_support_xmldb.xml
• eagle_mc_server_support.inc and datatowrite.inc

This issue was tracked as Item #145724.

Performance Tuning for ORCH Process

The ORCH process was not as efficient as possible. Because the code that ran each time the process launched did not have the literal variables declared, it would be parsed each time instead of being cached. The code was tuned and the the process now runs more efficiently.
This issue was tracked as Item #145755.

Fixed Order of Generic Load Workflow to Accommodate Issuer Role Details

The Issuer Role Details feed contains security information in addition issuer information. The IssuerRole object has to be loaded after the security related to it has already reached the database. However, due to the current logic this did not always occur. The code was updated to resolve this issue. The order of the eagle_wrf_generic_load had to be altered to allow the SMF to reach the database before the IssuerRole object begins loading. To accomplish this the load_issuer_role object was moved from eagle_wrf_generic_load_issuer_objects to eagle_wrf_generic_load_security_related_objects.
This issue was tracked as Item #145786.

I2I

Added I2I support for Booking Long and Short Positions

When booking a SHORTSELL on a security that already has a long position, there was an error that caused the long position to be deleted and the short position is the only one that remained. This issue was due to the fact that the longShortIndicator field was not being processed during load. As a result of these bookings, the Hub and the Spoke were no longer aligned since the long position was deleted on the Spoke. To resolve this issue, the longShortIndicator functionality was restored and now controls whether or not existing records should be deleted.
This issue was tracked as Item #146157.