Enhancements:
SDP-28462: The Inbound The Inbound Interface for Accounting Asset Cash was updated to support Accounting Cash Miscellaneous Expenses
The Inbound Interface for the Accounting Asset Cash was updated. The AMISCEXP, assetCashType='AMISCEXP', is now supported.
The logic for tag85 and mapping for tag5363 was corrected. Users can now specify the Settlement Currency separately from the asset currently via the RTR.
File changed:
eagle_default\in\include\csv-cash_misc_inc_exp.inc
SDP-28432: Enhanced Enhanced Security Resolution logic for the Warehouse Broker Trade Quotes inbound interface when a security with the same XREF identifiers and different currencies is processed
Following improvements were made to tradeQuotes:
Implemented the Generic EagleML Security resolution to the inbound interface
Implemented the Generic EagleML Entity resolution to the inbound interface
Added support of the tradeQuotes extract for MSSQL
Added the assetIdentifiers model to outbound interface
Files changed:
eagle_ml-2-0_cm/out/tagvalue/extract_ref_trade_quotes.inc
eagle_ml-2-0_cm/out/tagvalue/extract_ref_trade_quotes.xml
eagle_ml-2-0_cm/out/xml/t_eagleml-2-0_streaming.rsf
eagle_ml-2-0_cm/out/xml/t_ref_trade_quotes_streaming.inc
eagle_ml-2-0_cm/w_config.inc
eagle_default/in/xml/xml-ref_tradequotes.xml
File removed:
eagle_default/in/xml/include/tradequote.inc
SDP-28360: EagleML EagleML Inbound Interface for Price Classification
...
Files changed:
metadata\bind\ eagleml_ref_priceclassification.xml
eagle_default\in\xml\eagleml_reference.xml
xml-ref_price_classification.xml
xml-ref_objects.rsf
SDP-27846: The The logic for the calcTransactionId and calcCancelTransactionId was modified in the Warehouse Trade Extract - WRHSTRADEEXTRACT
The fields calcTransactionId and calcCancelTransactionId are concatenated with starTag26 when the parameters EnhanceCalcTransactionId = Y and IncludedExtendedDetails = Y or ALL. The logic of these fields was modified as following: starTag26 is now applied only if the recordType of the trade is 350 or 450 when the parameters EnhanceCalcTransactionId = Y and IncludedExtendedDetails = Y or ALL.
Files changed:
extract_warehouse_trade.inc
SDP-27841: Fields Fields buysell and amortizationParValue were added into the IncludeExtendedDetails mode
...
extract_asset_properties_fields.inc
t_asset_properties_fields.inc
t_asset_properties_fields_start.inc
t_asset_properties_fields_streaming.inc
SDP-27767: Additional Additional fields added to GenericSMF Data Model
...
Files changed:
eagleml-sec-shared-2-0.xsd
smf_egl_gen_interface_template.xsl
smf_egl_gen_interface_template_mssql.xsl
t_smf_streaming_eml.inc
SDP-27290: I2I I2I Interface was improved to retrieve TSR and RTR messages
...
eagle_ml-2-0_cm/in/xml/i2i_control_messages.rsf
eagle_ml-2-0_cm/in/xml/i2i_message_distribution.xml
eagle_ml-2-0_cm/out/xml/t_i2i_message_distribution.xml
eagle_ml-2-0_cm/out/xml/t_i2i_message_distribution_columns.inc
eagle_ml-2-0_cm/out/xml/t_i2i_message_distribution_dist.inc
eagle_ml-2-0_cm/out/xml/t_i2i_message_distribution_resmsgcolumns.inc
SDP-26957: Added New Processing Option for Issuer Role Batch Load via SMF MI Interface
A new processing option that enables grouping for Issuer Role Batch Loads was introduced.
To leverage this option, you will need to include ISSUER_ROLE_GROUPING in the data file:
<header>
<objectType>GenericSMF</objectType>
<processingOptions>ISSUER_ROLE_GROUPING</processingOptions>
</header>
This new option allows you to load Issuer Role as Batch and generate complete ownership period for Security + Role Type Key.
Issuer Role batch records have 2 processing options set by default: <processingOptions>ISSUE_ROLE_UPSERT_MODE,USE_LATEST_START_DATE</processingOptions>, where
ISSUE_ROLE_UPSERT_MODE - prevents delete of existing records that preserves history about previous ownership
USE_LATEST_START_DATE - applies max start date to each issuer role record,
...
forming 1 ownership period based on incoming Issuer Roles even if they have different start dates.
Files changed:
eagleml_smf_issuer_role.xsl
SDP-26502: Two Two new processing options introduced for IssuerRole batch mode
...
Files changed:
xml-ref_issuerrole_batch.xml
SDP-26467: Added Added new EagleML object - Global Tax Rates
...
Files changed:
eagle_default/in/xml/xml-ref_global_tax_rate.xml
eagle_default/in/xml/xml-ref_objects.rsf
workflow related files
SDP-25042: Added Added support for load and extract of Variation Margin Override Rule Name in the GenericEntity
...
eagleml_ent_genericentity.xml
xml-ent_entitygeneric.xml
entity_aliases.inc
entity_acct.inc
entity_panels.inc
extract_entity.inc
extract_entity_accounting_basis.inc
t_entity_streaming.inc
t_entity_streaming_eml.inc
t_entity_accounting_basis_streaming.inc
SDP-22873: Two Two additional fields added to GenericSMF Data Model
...
Files changed:
eagleml-sec-shared-2-0.xsd
smf_egl_gen_interface_template.xsl
smf_egl_gen_interface_template_mssql.xsl
t_smf_streaming_eml.inc
SDP-22186: Corrected Corrected issue resolving SOAP Port for Date Rule requests
...
SDP-19651: Added possibility to include details of the Successful messages into the Consolidated TSR
A Consolidated TSR represents an additional report of the workflow, summing up the TSR's for each of the subprocesses of the workflow. The Consolidated TSR was improved to include SUCCESS Messages now. A new flag IncludeAllDetails (W_INCLUDE_ALL_DETAILS) was added. Possible values: Y/N. The default value is N.
The flag allows to include details for SUCCESS messages in the Consolidated TSR like:
<transactionId>B90DBM55FL6PIXJB</transactionId>
<eagleDetailId>4839327</eagleDetailId>
<identifier><identifierName>fromId</identifierName><identifierValue>1</identifierValue>
</identifier><identifier><identifierName>account</identifierName><identifierValue>261</identifierValue>
</identifier><identifier><identifierName>referenceNumber</identifierName><identifierValue>-3862</identifierValue>
</identifier><identifier><identifierName>identifier2</identifierName><identifierValue>19900101</identifierValue>
</identifier><identifier><identifierName>identifier3</identifierName><identifierValue>99</identifierValue>
</identifier>
...
Files changed:
mc2_task_reporter_generate_task_unit.inc
task_reporter_gen_step_summary.inc
task_reporter_gen_task_unit_realtime.inc
task_reporter_generate_task_unit.inc
Production Bugs:
SDP-29036: Generic Generic Extract Workflows were updated where the wrong status No_Data was returned under MC2 Engine
Extracts below used to return a NO_DATA status if the eagle_wrf_generic_extract was launched under MC2 engine:
SOURCEEXTRACT
XREFCONFIGEXTRACT
PACESYSEXTRACT
PRICINGSYSSETTINGEXTRACT
RPTTIMESTAMPS
CLIENT
The issue was related to incorrect condition in Generic Extract workflow for these feed types.
Files changed:
Generic extract related files.
SDP-28434: Added Added securityAlias to Security Notes extract
...
extract_ref_security_notes.inc
SDP-28396: Sink Sink Schedule amount cannot exceed 1.00
...
Files changed:
eagle_default/in/xml/xml-ref_schedule.xml
eagle_default/in/xml/xml-ref_schedule_mi.xml
SDP-28287: Resolved Resolved Pricing Center Event Timeouts
...
Files changed:
exec_pace_event_pricing_check.inc
SDP-28129: Entitlement Entitlement filter for extracts was changed to avoid duplicate records in Entity Filter V2
...
The Entitlement filter (usergroups) is a part of Entity filter for many extracts. The rule extract_filter_entity_entitlement.inc is called inside the extract_filter_entity.inc file.
The Entity and Entitlement filters use two separate temp tables for storing values.
The Entitlement filter was called outside of the extract_filter_entity.inc for the below list of extracts:
ENTITYBANKRELEXTRACT
ENTITYCOMPOSITELISTEXTRACT
ENTITYLISTEXTRACT
ENTITYMANAGEREXTRACT
ENTITYMANAGERRELEXTRACT
ENTITYREGULATORYEXTRACT
ENTITYSHARECLASSEXTRACT
ENTITYXREFEXTRACT
WRHSSPDDELTALOGEXTRACT
In the case of the Entity Filter V2 and the Entitlement filter, data was inserted twice into the temp table: the first time in a separate call extract_filter_entity_entitlement.inc; and the second time in the Entity Filter V2 itself.
As a result, the temp table for the Entitlement filter contained duplicates and multiple result set of records after the join. As a result, the extract files contained duplicates. For the above list of extracts, the separate call of extract_filter_entity_entitlement.inc was deleted and moved inside the extract_filter_entity.inc as it works for most parts of the objects.
...
extract_filter_entity.inc
extract_filter_entity_entitlement.inc
extract_entity_bank_relationship.inc
extract_entity_composite_list.inc
extract_entity_list.inc
extract_entity_manager.inc
extract_entity_manager_relationship.inc
extract_entity_regulatory.inc
extract_entity_share_class.inc
extract_entity_xref.inc
extract_warehouse_spd_delta_log.inc
SDP-27918: GenericSMF GenericSMF Load replaces some Xref data with Primary Asset or Alt Asset values
...
File changed:
smf_forwrd.inc
SDP-27850: Mapping Mapping issue for OriginalSource Field was corrected in the IssueFxRate Inbound rule
...
Files changed:
xml-ref_fxrate.xml
SDP-27770: Allowed Allowed use of local currency for security resolution on load to Warehouse Trade Extension Table
...
Files changed:
eagle_default/in/xml/include/xml-dbdirect_sec_parse_xrefs.inc
SDP-27726: Added Added Mapping for Additional Fields in Exchange Price Inbound/Outbound Interfaces
...
Files changed:
metadata/bind/eagleml_ref_exchangeprice.xml
eagle_default/in/xml/xml-ref_exchangeprice.xm
eagle_ml-2-0_cm/generate_sp_on_fly.inc
eagle_ml-2-0_cm/out/xml/t_issueprice_exchange_streaming.inc
SDP-27452: Cancel Cancel EJM Process was improvedwas improved
The Cancel EJMProcess continued running, therefore the status was changed from CANCELLED back to SUCCESS.
The issue was corrected by including a restart MC Process command at the end of the Canceled Process for all MC Instances.
Files changed:
control_cancel_process.inc
control_process.xml
SDP-26575: FX FX Rates load was optimized
The Fx Rate inbound rule was improved to use a direct-SQL call instead of a panel call, which is much slower compared to the direct SQL query. The load rate was improved
from 20 rec/sec up to 200 rec/sec. Additionally, the Fx Rate load is currently supported via an XMLDBAPI request with the load rate being about 350 rec/sec.
This is the non-default mode and requires a parameter in the incoming EagleML message to not use the panel load and validations:
<accountingValidationFlag>N</accountingValidationFlag>
Files changed:
xml-ref_fxrate.xml