Enhancements
SDP-45172: The EDS load process was updated to support the dynamic query profile
The EDS load process was updated to support the generation of dynamic query profiles. This functionality allows the avoidance of unnecessary fields in the generated SQL request. Also, if the feed type supports several tables, then only the tables involved in the load will be affected. The dynamic query is generated based on the incoming fields in the file. Only the populated fields will be used to generate insert and update requests.
SDP-44554: The initial version of Resolution Service for EDS Load process
The initial version of Resolution Services was implemented. It provides the Asset Resolution and Entity Resolution by 1 pair of Xreference Identifiers. For the Entity, the Entity Resolution is triggered for elements xrefAccountId and xrefAccountIdType specified in the incoming message:
<xrefAccountId>XREFID</xrefAccountId>
<xrefAccountIdType>XREFTYPE</xrefAccountIdType>
The Asset Resolution applied for the Security Identifiers specified in the incoming message, primaryAssetId and primaryAssetType or cusip/isin/... :
<primaryAssetId>PRIMARYID</primaryAssetId>
<primaryAssetType>PRIMARYTYPE</primaryAssetType>
SDP-44356: PRICINGREPORTEXTRACT enhanced with new capability to resolve REASON Code Value / Resolve Price At Cost Workflow
When the PRICINGREPORTEXTRACT is executed, if the REASON value from the RULESDBO.PRICE_STATUS is returned, then it is translated to the code description of the Code Value table from the IPCCHGREASON code category.
Refined logic for the following elements:
targetSourceName
targetSourceDescription
priceSource
priceSourceDescription
priceType
activePriceSourceName
activePriceSourceDescription
The logic has been revised to resolve the Reason Code from the PRICE_RULE_SECURITIES table and to support Price At Cost when a source is resolved in the Pricing Tables, else the Price at Cost defaults to the Portfolio Valuation table.
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-44092: GenericSMF Inbound and Outbound interfaces were enhanced to support new SMF fields for IFRS-9 Reporting
The Generic SMF Fixed Income Model was updated to support new fields:
SECURITYDBO.FIXED_INCOME.SPPI_TEST (date) - Tag 17933
SECURITYDBO.FIXED_INCOME.SPPI_ATTRIBUTE - Tag 17934
SECURITYDBO.FIXED_INCOME.SPPI_HISTORICAL_DATE - Tag 17935
SECURITYDBO.FIXED_INCOME.OBS_PERIOD_ADJ_DAYS - Tag 18086
Xpath:
EagleML/referenceTransaction/genericSMF/FixedIncomeModel/sppiTest
EagleML/referenceTransaction/genericSMF/FixedIncomeModel/sppiAttribute
EagleML/referenceTransaction/genericSMF/FixedIncomeModel/sppiHistoricalDate
EagleML/referenceTransaction/genericSMF/FixedIncomeModel/observationPeriodAdjustDays
Files changed:
eagleml-sec-shared-2-0.xsd
dynamic/msgcenter/eagle_default/in/xml/xslt/smf_egl_gen_interface_template.xsl
dynamic/msgcenter/eagle_default/in/xml/xslt/smf_egl_gen_interface_template_mssql.xsl
dynamic/msgcenter/eagle_default/in/xml/include/smf_panels.inc
dynamic/msgcenter/eagle_default/in/xml/include/contract_leg_aliases.inc
dynamic/msgcenter/eagle_default/in/xml/include/contract_leg_mapping.inc
dynamic/msgcenter/eagle_default/in/xml/include/pay_leg_aliases.inc
dynamic/msgcenter/eagle_default/in/xml/include/pay_leg_mapping.inc
SDP-44089: The Generic Entity and Issuer Organization Inbound interfaces were updated to support additional fields in SECURITYDBO.LEI_DETAILS
The Inbound rules and XSD schema were updated to support new fields added to the SECURITYDBO.LEI_DETAILS tables:
NEXT_RENEWAL_DATE (date) - Tag 17932
ULTIMATE_PARENT_COMPANY (Nvarchar2(255)) - Tag 17930
VALIDATION_SOURCES (Nvarchar2(255)) - Tag 17931
Xpath:
EagleML/referenceTransaction/issuerOrganization/legalEntityId/ultimateParentCompany
EagleML/referenceTransaction/issuerOrganization/legalEntityId/verificationSourcesValidity
EagleML/referenceTransaction/issuerOrganization/legalEntityId/nextRenewalDate
Files changed:
eagleml-sec-shared-2-0.xsd
eagleml_ent_genericentity.xml
eagleml_ref_issuerorganization.xml
dynamic/msgcenter/eagle_default/in/include/csv-entity_columns.inc
dynamic/msgcenter/eagle_default/in/include/entity_aliases.xml
dynamic/msgcenter/eagle_default/in/include/entity_panels.xml
dynamic/msgcenter/eagle_default/in/xml/xml_ent_entitygeneric.xml
dynamic/msgcenter/eagle_default/in/xml/xml_ref_issuerorganization.xml
SDP-43903: EDS Extract TaskStatus
A new Ontology Resource, TaskStatus, was designed to allow end users to inquire and retrieve the information and current status of the task.
The TaskStatus resource supports all common filters like fromdate, todate, OutputFormat, querystatus, querycorrelationid, querybusinesstaskid, maxrows, SaveSQLQuery, and also a few additional filters like - querycorrelationid, bussinesstaskid, querystatus.
Files changed:
eagle-vocab-definition-common.json
eagle-interfaces.json
eagle-vocab-common.json
eagle-vocab-enumerations.json
taskstatus.json
taskstatus-models.json
SDP-43829: Issuer Analytic inbound Interface was updated to support core stored procedure
The Issuer Analytic inbound inbound interface was enhanced to utilize the core stored procedure ADD_CHANGE_ISSUER_ANALYTICS. The previously used stored procedure, INS_UPD_ISSUER_ANALYTICS, is still supported for backward compatibility when the core procedure is not available within an environment. The change was implemented for the Oracle platform only.
Files changed:
metadata/bind/eagleml_ref_issueranalytic.xml
msgcenter/eagle_ml-2-0_cm/generate_sp_on_fly.inc
SDP-43313: The IssuePcPrice and the ExchangePrice objects were enhanced to support a new Pricing Center option Use Extended Update
A new optional element, extendedUpdate, is now supported via the IssuePcPrice and ExchangePrice objects to be in sync with Pricing Center changes. The core stored procedure PACE_MASTERDBO.PRICING_PACE.PRICE_UPLOAD was updated to support the new optional parameter in_extended_update, tag7105 (Use Extended Update).
When the price is the same as the current value in the system and the extendedUpdate is set to Y, the price load will update the record for the following elements:
Market Date
Current Price
Price Level
Volume
Source Detail
Original Vendor Source
Confidence Interval
Price Condition
Prior to this enhancement, if the price was the same for an existing record, the existing record was not updated for the same case.
Files changed:
eagle_default/in/xml/xml-ref_issuepcprice.xml
eagle_default/in/xml/xml-ref_exchangeprice.xml
eagle_default/in/xml/include/xml-ref_security_pricing_common.inc
metadata/bind/eagleml_ref_exchangeprice.xml
SDP-42975: Database tables HOLDINGDBO.POSITION_COST_LOT_USER and HOLDINGDBO.POSITION_COST_DETAIL_USER are supported via EDS Extracts
Additional database tables, HOLDINGDBO.POSITION_COST_LOT_USER and
HOLDINGDBO.POSITION_COST_DETAIL_USER, are supported via EDS Extracts.
Please note that Warehouse Open Lot CostUDF Model and Warehouse Position CostUDF Model are only supported via EDS interfaces. Extracts are implemented and load is currently in progress.
Please see Eagleml wiki for additional details.
Warehouse Position EDS Extract RTR Example: Warehouse Position EDS Extract RTR Example
Warehouse Open Lot EDS Extract RTR Example: Warehouse Open Lot EDS Extract RTR Example
Files changed:
dynamic/metadata/core/ontology/eagle-vocab-wh.json
dynamic/metadata/core/ontology/eagle-vocab-wh-shared.json
dynamic/metadata/core/ontology/definition/eagle-vocab-definition-wh.json
dynamic/metadata/core/ontology/definition/eagle-vocab-definition-wh-shared.json
dynamic/metadata/core/ontology/warehouse/warehouseposition.json
dynamic/metadata/core/ontology/warehouse/warehouseopenlot.json
dynamic/metadata/core/ontology/warehouse/warehouseposition-models.json
dynamic/metadata/core/ontology/warehouse/warehouseopenlot-models.json
SDP-42753: New EDS Extract targetFxRate
The database table RULESDBO.FX_TARGET is supported for extracts via the new EDS Resource targetFxRate. It will allow users to pull the composited rates data for reporting.
Supported Filters:
sourcename
fromdate
todate
effectivedate
fromeffectivedate
toeffectivedate
RTR example:
<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="RunTaskRequest" eaglemlVersion="2-0" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd" eaglemlType="RunTaskRequest">
<header>
<messageId>E30X5FTN4N317JFF</messageId>
<sentBy>MC2EJM</sentBy>
<sendTo>http://www.eagleinvsys.com/eagle_default_ruleservice</sendTo>
<creationTimestamp>2018-04-13T09:52:39.73-05:00</creationTimestamp>
<expiryTimestamp/>
<expiryLoadFlag/>
</header>
<taskIdentifier>
<processingSequenceNumber/>
<correlationId>EDS_TARGETFX_EXTRACT_
{GUID}
</correlationId>
<businessTaskId>EDS_TARGETFX_EXTRACT</businessTaskId>
<sequenceNumber/>
</taskIdentifier>
<taskTypeEnum>NEW</taskTypeEnum>
<synchronousExecution>yes</synchronousExecution>
<taskParameters>
<taskParameter>
<name>ServiceName</name>
<value>EBS</value>
</taskParameter>
<taskParameter>
<name>ServiceMethodName</name>
<dataType>S</dataType>
<value>extract</value>
</taskParameter>
<taskParameter>
<name>ResourceName</name>
<value>targetfxrate</value>
</taskParameter>
</taskParameters>
</EagleML>
Files added:
ontology/reference/targetfxrate-models.json
ontology/reference/targetfxrate.json
Files changed:
ontology/definition/eagle-vocab-definition-ref.json
ontology/definition/eagle-vocab-definition-shared.json
ontology/definition/eagle-vocab-definition-wh-shared.json
ontology/eagle-vocab-enumerations.json
ontology/eagle-vocab-ref.json
ontology/eagle-vocab-shared.json
ontology/eagle-vocab-wh-shared.json
Production Bugs:
SDP-45180: The WarehouseTrade inbound interface was updated to fix the Entity resolution issue on load to custom database extension table
The Entity resolution used to fail if the WarehouseTrade incoming message contained Entity Xreferences instead of the Entity ID. The Database error was raised: Error Executing trd_egl_gen_interface in 'TRADESDBO'=>ORA-20101: Entity *** not found in entity table, on load to custom database extension table via XPanels application.
The issue was fixed and the Entity Resolution logic by Xreferences now works correctly for WarehouseTrade payload to the extended database.
Files changed:
eagle_default/in/xml/include/xml-warehouse_common.inc
SDP-44976: The WarehouseTrade inbound interface was improved to support load into the custom database extension table via XPanels application
The WarehouseTrade inbound interface was improved to correctly load data into the custom database extension table.
Previously, the WarehouseTrade inbound interface did not support load into the custom database extension table via XPanels. The Interface was enhanced to support the load of the extended data into the custom database extension table for WarehouseTrade.
Below are the key fields required to create a custom Extension table:
ENTITY_ID - CHAR(8)
EFFECTIVE_DATE - DATE
SRC_INTFC_INST - NUMBER
SECURITY_ALIAS - NUMBER
MASTER_TICKET_NUMBER - VARCHAR2(500)
Files changed:
eagle_default/in/xml/include/wrhs_ext_custom_fields.inc
SDP-44801: Resolved the exception raised during Synthetic SMF Processing at midnight
When the update time for the Synthetic SMF's current time processing spanned across midnight, the time value rolled to the next day, but the day value remained the previous day, and, as a result, it reflected an invalid update date.
The logic was revised to increase the day value for cases when the current time value is approaching midnight.
Files changed:
eagle_default/in/xml/include/secmastersynthetic.inc
SDP-44727: The Issuer resolution was improved for Issuer Relationship interface
The IssuerRelationship used to work incorrectly in the case when the toIssuer did not exist. As a result, if toIssuer was not resolved, the rule would create a Relationship of the fromIssuer to itself. The issue was fixed.
File changed:
eagle_default/in/xml/xml-ref_issuerrelationship.xml