EagleML Release Notes - December 2019

Owned by Olga Galis (Deactivated)
Dec 06, 2019
5 min read

Enhancements:


SDP-30295: CONSEARNEDINCOMEEXTRACT was updated to correct SP failure

The RPT_POS_CONSO_INC_EARNED Stored Procedure was failing in V17R2.16 due to the wrong number of arguments.
An additional parameter, in_primary_asset_id, was added to support the Stored Procedure executed during the Consolidated Earned Income Outbound interface.

Files changed:

eagle_ml-2-0_cm/out/tagvalue/extract_acct_cons_earned_inc.inc


SDP-30197: IssueFxRate interface was updated to correct issue with the Update Source

The Update Source was not taken into account or stored in the database if the accountingValidationFlag was set to Y.
The issue was corrected.

Configuration flag AllowAssign944=1 is set via msgservice.ini to allow control and population of tag944 from the data file.

Files changed:

xml-ref_fxrate.xml


SDP-29980: PRICINGREPORTEXTRACT was enhanced to include two additional fields

Two new fields were added to the PRICINGREPORTEXTRACT:
The instance field is from the rulesdbo.price_rule_securities.final_validation_status and its description is resolved from the rulesdbo.price_edits.short_desc.

Two new EagleML elements were created:
finalValidationStatus
finalValidationstatusDescription

Files changed:

eagle_ml-2-0_cm/out/tagvalue/extract_pricing_report.inc
eagle_ml-2-0_cm/out/xml/t_pricing_report_streaming.inc


SDP-29939: Stream Category and Description were updated and packaged for every stream included in the default EagleML package

For each stream included in the EagleML package, the Stream Category and Description were populated. There was no Installer changes at this time, therefore updates are available only in case of Fresh Install.

Additional details are available on the WIKI: https://eagledocs.atlassian.net/wiki/spaces/EAGLEML/pages/251921932/Post+Install+-+Verify+and+Enable+Required+Message+Streams


SDP-30911: The Multiple Leg Accounting Trade interface was updated to support a new element commissionAndFeesSettleSeparately

A new flag commissionAndFeesSettleSeparately was added for multi-leg trades. Supported values are Y and N.
The change is supported only for the V17 core release and applied when the required elements, tag12860 and tag10057, are available via panels.

Files changed:

tradeleg_aliases.inc
tradeleg_columns.inc
xml-accttrade_multipleleg.xml
multiplelegtrade_aliases.inc

SDP-29720: Open and Close Trades interfaces were updated to support a new element commissionAndFeesSettleSeparately

A new element commissionAndFeesSettleSeparately was added for the Open and Close Trades. Supported values are Y and N.
The change is available only for V17 core release where required tag12860 and tag10057 are available via panels.

Files changed:

trade_aliases.inc
csv-buy_columns.inc
csv-sell_columns.inc

SDP-29343: ISSUERANALYTIC Inbound and Outbound Interfaces

The issuerAnalytic records were incorrectly grouped on the transformation step.
The following changes were completed to correct the issue:

  • Added a default sorting by Primary Key=Issuer Alias + Source Interface Instance + Effective Date
  • Corrected grouped by =Issuer Alias + Source Interface Instance + Effective Date

The following improvements were made to the issuerAnalytic interface:

  • added the default inbound issuerAnalytic interface
  • added the issuer resolution for inbound issuerAnalytic interface
  • added error processing for missed or unresolved key fields
  • added delete functionality to the inbound issuerAnalytic interface
  • added the source filter to outbound interface

Files changed:

eagle_ml-2-0_cm/out/tagvalue/extract_issuer_analytic.inc
eagle_ml-2-0_cm/out/xml/t_issuer_analytic_streaming.inc
eagle_ml-2-0_cm/generate_sp_on_fly.inc
eagle_default/in/xml/xml-ref_delete.xml
eagle_default/in/xml/xml-ref_issueranalytic.xml
eagle_default/in/xml/xml-ref_objects.rsf

Files added:

eagle_ml-2-0_cm/out/tagvalue/ref_issueranalytic_delete.inc


SDP-29169: MultiLeg SMF Inbound Interface was enhanced to provide support for additional elementss

Added support for additional elements <generateSwapResetScheduleSwitch>and <corporateActionResetIndicator> to the MultiLeg SMF Interface.

Files changed:

eagle_default/in/xml/include/contract_leg_alliases.inc
eagle_default/in/xml/include/contract_mapping.inc
eagle_default/in/xml/include/pay_leg_alliases.inc
eagle_default/in/xml/include/pay_mapping.inc
eagle_default/in/xml/include/receive_leg_alliases.inc
eagle_default/in/xml/include/receive_mapping.inc
eagle_default/in/xml/xml-smf_multileg_swap.xml
eagle_default/in/xml/include/contract_leg_alliases.inc 


SDP-28982: Corrected issue with duplicated correlation Id for requests loaded via Profiled Loader

Corrected issue with duplicate correlation Ids for requests as the  "get_corrid_from_filename.inc" was removed from the "launch_load_by_profile.inc" to prevent errors with duplicate correlation Ids when the correlation Id from the incoming file was used as correlationId in the RTR for the "eagle_ml-2-0_default_cm_control_message" stream.

Files changed:

eagle_ml-2-0_cm/ndfa/launch_load_by_profile.inc


SDP-28270: Created new EagleML Feed Type PACEFIELDATTRIBUTEEXTRACT

A new outbound interface Pace Field Attribute Extract was created.
Feedtype = PACEFIELDATTRIBUTEEXTRACT.
XSD type that describes the interface is PaceAttribute and based on Reference group.

Data is extracted from the following database tables:
RULESDBO.FIELD_ATTRIBUTES
RULESDBO.FIELD_ATTRIBUTE_DETAIL
RULESDBO.FIELD_ATTRIBUTE_PROCESS
PACE_MASTERDBO.PACE_INV_FIELDS
PACE_MASTERDBO.CODES.

Supported filters:
Source filter
Common filter (maxrows)
Custom filters:
Description - by RULESDBO.FIELD_ATTRIBUTES.FIELD_ATTRIBUTE_DESCRIPTION
Code - by RULESDBO.FIELD_ATTRIBUTE_DETAIL.FIELD_IDENTIFIER
Database - by RULESDBO.FIELD_ATTRIBUTES.DATABASE_NAME
Table - by RULESDBO.FIELD_ATTRIBUTES.TABLE_NAME
Column - by RULESDBO.FIELD_ATTRIBUTES.FIELD_NAME
ProductCode - by RULESDBO.FIELD_ATTRIBUTES.FIELD_INDICATOR
ReportName - if specified, then EagleML extract will contain only Field Attributes that indicate Report Rule used by the specified Report Name (Report Profile) in Performance Center / General Reporting tool
ReportRule - if specified, then the EagleML extract will contain only Field Attributes that indicate the Report Rule in Performance Center / General Reporting tool


SDP-20136: Provided support to delete records from TRADESDBO.TRADE_XREFERENCE via the default workflow 'eagle_wrf_generic_delete'

Prior to the changes, if a Trade had any Trade Xreference records upon trying to delete the Trade an error was produced and the Trade could not be deleted.
The eagle_wrf_generic_delete workflow and the eagle_ml-2-0_default_in_xml_delete_objects stream were enhanced to delete the trade xreferences records.

Note that trade xreference table exists only on V17 environments.

File changed:

eagle_default/in/xml/t_eagle_ml-2-0_default_in_xml_delete_warehouse_trade.xml


SDP-10928: Delete of warehousePerformance transactions was improved

The delete of Warehouse Performance records via the eagle_ml-2-0_default_in_xml_delete_objects stream was not working correctly when the  perfSummaryType and statusFlag elements had different values.
The issue was corrected.
The following composite key is used to identify and delete records from main and child tables: entityID +effectiveDate+sourceName+perfFreqCode+dictionaryId+perfSummaryType.

Files changed:

eagle_default/in/xml/t_eagle_ml-2-0_default_in_xml_delete_warehouse_performance.xml


SDP-9886: Corporate Action Inbound rule was updated to support additional panel logic

Corporate Action rule was updated to support additional panel logic for accounting mode when :9153: != 'MC_MODE '

Files changed:

eagle_default/in/xml/xml-ref_ca.xml


Production Bugs:


SDP-30814: Corrected Cancel Process of WAITEVENTS when the W_WAITEVENTS_DATABASE_MODE is turned off

When the  W_WAITEVENTS_DATABASE_MODE was set to N, the cancel of WAITEVENTS was working incorrectly resulting in all workflow instances being stopped.
The condition to update the information about WAITEVENTS was fixed.

Files changed:

eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/cancel_global_event_wait.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/out/tagvalue/execute_wrkfl_event.xml


SDP-30625: Entity Regulatory Interface was updated to correct issues in UPSERT Mode

The issue was introduced in a prior release after EagleML begin using generated the stored procedure instead of a direct database request.

The generated stored procedure did not check values already loaded into the database and inserted Nulls into the fields not specified in the input file via UPSERT mode.
The issue was corrected and the update is properly supported.

File changed:

eagle_ml-2-0_cm/generate_sp_on_fly.inc


SDP-30449: Update Date Logic was corrected for DeltaBased Extracts

There was a problem related to the LAST_RUN_DATE and UPDATE_DATE being out of sync in the EJM ORCH tables: ORCH_REQUEST_PARAMS and ORCH_REQUEST_DEF.

The Update Date logic was corrected to synchronize the Update Date in the ORCH tables for all records within a single instance or correlationId.

File changed:

out/tagvalue/extract_delta_orch.inc


SDP-30362: Corrected uploading the Price Status into the PRICE_STATUS table via the Exchange Price Inbound Interface

There was an issue loading the Price Statuses via the Exchange Price inbound interface.
If a record contained multiple Prices like Bid Price, Ask Price or Mid Price, then the Price Status was updated only for a single Price.
The issue was fixed and all Price Statuses are properly loading into PRICE_STATUS table.

File changed:

eagle_default/in/xml/xml-ref_exchangeprice.xml


SDP-30353: Warehouse Performance Extract does not return perfRollupReturnsId field in case of zero value

The Warehouse Performance extract, WRHSPERFORMANCEEXTRACT, returned perfRollupReturnsId field when the value was equal to 0.
The Warehouse Performance extract was corrected for this case, to not return the perfRollupReturnsId field when the value is 0.

File changed:

extract_warehouse_performance.inc


SDP-30344: Error description text was fixed for case when date rule was not calculated.

The Error description text was incorrect when a date rule was not calculated.
The Error description text was corrected.
Example of error text: Date was not calculated for daterule= '2007 Q1' and ruleasofdate='09/06/2019'

File changed:

date_rule_calculation.inc


SDP-30338: Corrected issue with the status of distribution stream for a filename with space

The stream eagle_ml_file_distribution was incorrectly processing files with spaces in their filename and there was no error reported.
The logic was enhanced to process files with spaces in the filename and report an error in case of a failure of moving the file for any reason.

File changed:

eagle_ml-2-0_cm/out/tagvalue/eagle_default_cm_file_distribution.xml


SDP-30068: Corrected issue with Indexes for Extension Tables

Indexes were not used for the fields that were using the RTRIM function, making the query execution execute inefficiently.
The RTRIM function for the extension tables join was removed to allow index processing.
The primary key fields and their type must be identical between the main table and extension tables.

Files changed:

eagle_ml-2-0_cm/extract_extension_add_tables_into_join.inc


SDP-28911: ToAssetId Security Resolution logic was updated for Generic CA

Added logic to skip the ToAssetId Security resolution in case there is no ToAssetId node in the incoming message by setting the processingOptions flag to IGNORE_TOASSET_CHECK for Reference CA and Generic CA Load records.

Files changed:

eagle_default/in/xml/xml-ref_generic_ca.xml
eagle_default/in/xml/xml-ref_ca.xml


SDP-22637: Supported Rollup Functionality across multiple Partitions

The RollUp procedure was not working for the Warehouse Position and Warehouse OpenLot if data was loaded into a partition other than the default primary partition. This issue was observed in Oracle environments only. The issue was fixed and the RollUp Procedure is now supported across all partitions.

Files changed:

eagle_default\in\xml\xml-dbdirect_invar_eofp.xml
eagle_default\in\xml\include\xml-dbdirect_wrhs_delete_statement.inc


SDP-22575: Resolved link issue between Data Exporter and EJM processes

The Parent Sequence Instance was not set for the child EJM process and as a result, the Data Exporter used to fail since it could not determine the status of the child event.
The data exporter now correctly displays the sub-processes and the Sequence instance for the EJM process is properly retrieved.

Files changed:

eagle_ml-2-0_cm/out/tagvalue/exec_file_distribution.xml
eagle_ml-2-0_cm/orch_query.inc