Enhancements:
SDP-35011: Enhanced post-load validation step for profiled generic load to allow dynamically assign main data set and extract data set aliases for source files
As part of the larger data quality effort, the Data Validation and Comparison Interfaces were enhanced with new core functionality that allows using mashups for custom resolution. Several inbound interfaces have custom resolution logic which will replace the identifiers from the source files with the actual identifiers returned by the resolution. When comparing extracted data to the source file, these discrepancies used to cause the report to generate false positives.
The new core functionality allows the comparison interface dynamically change the content of the source file to get the correct identifiers and therefore avoid the false positives. The implementation now allows passing both parameters to the load validation profile: the main dataset comparison_maindsName and the extract dataset comparison_extractdsName. If these are left blank, the original source file and extract_data file with standard aliases will be used respectively.
Files changed:
eagle_ml-2-0_cm/unpacker/profiled_load_validation.xml
SDP-34835: Added new feature to preserve the original file name in the TSR
Added a new feature to keep the original file name in the final TSR. The functionality is supported for custom load workflows with the data load via the NDFA stream.
A new RTR parameter, PreserveRemoteFileName, was introduced and when set to Y it will preserve the original file name.
The corresponding global parameter W_PRESERVE_REMOTE_FILE_NAME is also supported.
The PreserveRemoteFileName populated in the RTR will override the config setting.
RTR parameter:
<taskParameter>
<name>PreserveRemoteFileName</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter>
w_config_custom.ini setting - :W_PRESERVE_REMOTE_FILE_NAME: := 'Y';
Files changed:
task_reporter_gen_step_summary.inc
SDP-34563: Unsettled Transactions Extract was updated
UNSETTLEDTRANSACTIONSEXTRACT was failing with database error when the accountingValidationFlag was set to Y. The error occurred due to the recent change in the core SP ESTARDBO.EC_DET_RPT.RPT_UNSET_ACT_NEW. The EagleML code was updated to sync with the updated stored procedure and the issue was resolved.
Files changed:
eagle_ml-2-0_cm/out/tagvalue/extract_acct_unsettled_transactions.inc
SDP-34449: Xref Logic was enhanced to support a new element for the IssuerOrganization and IssuerXref interfaces
The IssuerOrganization and IssuerXref interfaces were updated to allow optional Xref validation.
A new flag xrefConfigCheckSwitch , tag2364 (Skip Check) was added to control the Xref validation. If the flag is set to N, then the Xref validation will be skipped. If the flag is set to Y, then the Xref check is in place and will process as usual.
Files changed:
metadata/bind/eagleml_ref_issuerorganization.xml
metadata/bind/eagleml_ref_issuerxref.xml
eagle_default/in/xml/xml-ref_issuer_xref.xml
eagle_default/in/xml/xml-ref_issuer_xref_mi.xml
eagle_default/in/xml/xml-ref_issuerorganization.xml
eagle_default/in/xml/xslt/eagleml_issuer_org.xsl
eagle_default/in/xml/xslt/eagleml_issuer_xref.xsl
SDP-34437: New filter transactioncode was added for Warehouse Trade Extract
A new filter parameter transactioncode was introduced to the Warehouse Trade Extract.
The filter is linked to the database field - TRADESDBO.TRADE.TRANS_CODE
RTR Example:
<taskParameter>
<name>transactioncode</name>
<dataType>S</dataType>
<value>E(CONVERSION,CONVERSIONCANCEL)</value>
</taskParameter>
Below is the list of sample values:
I(CONVERSION,CONVERSIONCANCEL) - Include for values (CONVERSION,CONVERSIONCANCEL)
E(CONVERSION,CONVERSIONCANCEL) - Exclude for values (CONVERSION,CONVERSIONCANCEL)
CONVERSION,CONVERSIONCANCEL - Include for values (CONVERSION,CONVERSIONCANCEL)
L(%CONVERSION%) - Include for values LIKE (%CONVERSION%)
File changed:
eagle_ml-2-0_cm/out/tagvalue/extract_warehouse_trade.inc
SDP-34334: CorrelarionIdPrefix Parameter for EJM Tasks
A new RTR parameter, CorrelarionIdPrefix, is supported for EJM tasks executed via the Generic Load and Generic Extract workflows. The prefix to the CorrelationId is configured via a profile or RTR. The maximum length for the prefix is limited to 10 symbols.
The functionality is available by default and controlled by a new global default parameter. The parameter is named g_nCorrIdPrefixMaxLength with a default value set to 5 symbols.
The following parameters were added to support this functionality:
CorrelationIdPrefix will allow to set a Prefix
CorrelationIdPrefixDisable will allow to disable the Prefix
Example of the CorrelationIdPrefix parameter:
<taskParameter>
<name>CorrelationIdPrefix</name>
<dataType>S</dataType>
<value>PROD</value>
</taskParameter>
in result:
<taskIdentifier>
<correlationId correlationIdScheme="correlationIdScheme">PROD-FCOCJKM97Q3VR4LC</correlationId>
<businessTaskId correlationIdScheme="businessTaskIdScheme">TEST_SRV</businessTaskId>
</taskIdentifier>
Note: The CorrelationIdPrefix functionality is only supported in v17R2.x version.
Files changed:
w_config.inc
runtaskrequest.xml
get_correlation_id_prefix.inc
collect_task_parameters.inc
get_w_state.inc
upd_w_state.inc
execute_wrkfl_exent.xml
SDP-34166: Corporate Action Processing Logic was Updated
Corporate Action Processing logic was adjusted and will rely on two CA Business Keys:
If the clientSpecificCAId is part of the incoming message, then the CA Key applied is:
SecurityAlias + Trans Type + clientSpecificCAIdIf the clientSpecificCAId is null in the incoming message, then the CA Key applied is:
SecurityAlias + Trans Type + Ex Date + To Security Alias + Sub Priority + Term Flag
As well, the following logic was added:
If the CpStatus of the Corporate Action is RD (Released) in the database, then the Ex Date may not be updated on the Rebook (as To Security Alias)
If the Ex Date in the incoming file does not match to the database value in the RD record, then the load will fail with an error message: Ex Date on File Does Not Match Database for Released Corporate Action
Files changed:
eagle_default/in/xml/xml-ref_ca.xml
SDP-34130: PRICINGREPORTEXTRACT was enhanced to include two additional fields
Two new fields were added to the PRICINGREPORTEXTRACT:
RULESDBO.PRICE_RULE_SECURITIES.SOURCE_DETAIL
RULESDBO.PRICE_RULE_SECURITIES.PRICE_CONDITION
The sourceDetail is a field where users (Pricing Team) may enter a name or further descriptive information for a source. It is also used to define the source of the file name used (e.g. BBEQFILE, CORPFIFILE, CORPEQFILE).
The priceCondition is populated with a code value that provides additional detail on the state of the price provided. These may vary region to region, but common values include P for Price and FV for Fair Value.
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-34115: The Schedule Inbound Interface was updated to support additional fields
The schedule interface was updated to add support for all database fields. The new fields are only supported by the Stored Procedure mode load and not supported via the Accounting Validation mode.
Files changed:
metadata/bind/eagleml_ref_schedule.xml
eagle_default/in/xml/xml-ref_schedule.xml
eagle_default/in/xml/xml-ref_schedule_mi.xml
eagle_default/in/xml/xslt/eagleml_smf_mi_schedule.xsl
eagle_default/in/xml/xslt/eagleml_smf_schedule.xsl
eagle_default/in/xml/xslt/eagleml_smf_schedule_batch.xsl
eagle_ml-2-0_cm/out/xml/t_schedule_streaming.inc
SDP-33971: Warehouse Open Lot Interface was updated to support new field sleeveId
The Warehouse Open Lot Inbound and Outbound Interfaces were updated to add support of the new field sleeveId.
The field holdingdbo.lot_level_position.SLEEVE_ID is only supported for Eagle Core v17R2.x Oracle.
Files changed:
wrh_egl_gen_interface3.xsl
t_warehouse_openlot_streaming.inc
t_warehouse_openlot_xmldbapi_streaming.inc
SDP-33828: SECURITYDEFAULTEXTRACT is supported via Extract Service
Expanded the SECURITYDEFAULTEXTRACT to include support via MC2. It supports the common and security related filters.
Files changed:
eagle_ml-2-0_cm\out\xml\extract_service.rsf
eagle_ml-2-0_cm\out\xml\extract_service_start.inc
eagle_ml-2-0_cm\out\xml\t_eagleml-2-0_out_extract_service.rsf
eagle_ml-2-0_cm\out\xml\extract_service_ref_security_default.xml
SDP-33688: Post Extract Data Validation sub-process was Enhanced
The additional framework via the eagle_ml-2-0_default_cm_extract_validation stream was implemented to handle comparison between the baseline and new extract file according to the defined validation of the EDS interface.
The baseline extract file may be setup by the user or the first generated extract file will be used as a baseline by default.
If the validation step fails, then the distribution steps will not execute and incorrect extract will not be delivered to recipient.
The following RTR parameters should be used to define extract file validation:
PostExtractValidationBaselineFile - defines baseline file name (relative to cmw/extracts folder)
PostExtractValidationFilter - defines filter to apply on validation step
PostExtractValidationSetAsBaseline - flag to set current extract file as baseline file, no validation will be performed. Use Y value to enable this logic.
PostExtractValidationTolerance - value to define failure tolerance level
PostExtractValidationInterface - value to define the validation interface; if omitted, then current FeedType with ‘_validation’ will be used as default validation interface name
PostExtractValidationOutputFormat - value to define validation report format.
New Files:
eagle_ml-2-0_default_cm_extract_validation.pkg
eagle_ml-2-0_cm/mc2/ebs/extract_validation.rsf
eagle_ml-2-0_cm/mc2/ebs/extract_validation.xml
Files changed:
eagle_default_workflows.pkg
eagle_ml-2-0_workflows/eagle_wrf_generic_extract.wrf
eis/ejmwf/eagle_wrf_generic_extract.ejmwf
SDP-33246: New Inbound Interface - InterportfolioTransfer
The InterportfolioTransfer object type was added to allow the transfer of security positions from one entity to another utilizing corresponding the core panel /reorg/pan-interporttransfer.htm. The functionality transfers quantity and cost, but does not transfer the cash. The interface is also supported via the eagle_wrf_generic_load workflow.
Files added:
eagle_default/in/xml/xml-acct_interporttransfer.xml
Files changed:
eagle_default/in/xml/xml-acct_trades.rsf
SDP-32752: Inbound and Outbound User Interfaces were adjusted to reflect UI and Core SP changes in regards of the User Password
The field Password may be modified only via the UI application or corresponding panels going forward.
The USEREXTRACT will not return the value for Password field. If the Password field is part of the Inbound file, then it will be ignored and will not be loaded into the database.
Files Changed:
extract_user_user.inc
t_user_user_streaming.inc
t_user_user_scim_streaming.inc
t_ref_user_streaming.inc
user_common.inc
metadata\bind\eagleml_user.xml
metadata\bind\eagleml_user_user.xml
Production Bugs:
SDP-34533: Swagger file was updated with Filters definitions for the Pace Field Attribute Extract
Added missing filter definitions for PACEFIELDATTRIBUTEEXTRACT in the swagger-extracts.json
#/parameters/Description_OwnFilters
#/parameters/Code_OwnFilters
#/parameters/Database_OwnFilters
#/parameters/Table_OwnFilters
#/parameters/Column_OwnFilters
#/parameters/ProductCode_OwnFilters
#/parameters/ProductName_OwnFilters
#/parameters/ReportRule_OwnFilters
#/parameters/ReportName_OwnFilters
Previously these filters cannot be used via an API call because of missing definitions.
SDP-34086: Warehouse NAV Multi Inbound Interface was updated
The security resolution logic was corrected for the WarehouseNavMulti Object. The interface supports two optional fields holdingdbo.nav_multi.GROSS_ASSETS and holdingdbo.nav_multi.TICKER. These fields were required on EagleML side, and if Security Alias was not resolved, the error was returned during data load. Security resolution is no longer required.
Files changed:
eagle_default/in/xml/include/xml-warehouse_common.inc
SDP-10921: Added the issuerId and the issuerName filters to ISSUERRATINGEXTRACT
The Issuer Rating Extract was enhanced to support additional filters: issuerId and issuerName.
<taskParameter>
<name>issuerId</name>
<dataType>S</dataType>
<value> </value>
</taskParameter>
<taskParameter>
<name>issuerName</name>
<dataType>S</dataType>
<value> </value>
</taskParameter>
Files changed:
extract_issuer_rating.inc