...
Files changed:
eagle_ml-2-0_cm/out/tagvalue/extract_pricing_report.inc
SDP-
...
A new flag, ValuationSource, has been added for the PRICINGREPORTEXTRACT. When it set to MONTHLY, pricing data will be extracted from the ESTAR.MONTHLY_PORTFOLIO_VALUATION. When it set to DAILY or not presented in the RTR, data will be extracted from the ESTAR.MONTHLY_PORTFOLIO_VALUATION table. The default value is DAILY.
The functionality can also be specified in the /eagle_ml-2-0_custom_cm/w_config_custom.inc file via the global W_PRICINGREPORTEXTRACT_VALUATION_SRC variable for all PRICINGREPORTEXTRACT requests.
The RTR has higher priority over the custom include file. When both the ValuationSource and W_PRICINGREPORTEXTRACT_VALUATION_SRC are not null, the pricing table is chosen from the RTR parameter.
<taskParameter>
<name>ValuationSource</name>
<dataType>S</dataType>
<value>MONTHLY</value>
</taskParameter>
Files changed:
eagle_ml-2-0_cm/out/tagvalue/extract_pricing_report.inc
SDP-85845 VoluntaryCAElection interface resolves the custody elements
A new custodian element, entityBankAlias, is supported in the Corporate Actions Voluntary Elections for load.
If none of the new elements, custodianBankCode, custodyBankAccount, custodyBankSubaccount are sent, nothing changes for existing clients. However, if at least one of the new elements is present in the upload file, new logic is applied to check all custodian fields. Once all three elements are resolved, the entityBankAlias is resolved as a result. If even one of the identifiers is not found in the panel lookup or was not sent in the file, an "entityBankAlias" error is produced.
Additionally, a new processing option has been introduced:
<processingOptions>USE_ENTITY_BANK_ALIAS</processingOptions>
When using this option, the entityBankAlias is expected during the load process.
EagleML Xpath:
EagleML/referenceTransaction/voluntaryCAElection/custodianBankCode - Tag 1176
EagleML/referenceTransaction/voluntaryCAElection/custodyBankAccount - Tag 1660
EagleML/referenceTransaction/voluntaryCAElection/custodyBankSubaccount - Tag 1661
EagleML/referenceTransaction/voluntaryCAElection/entityBankAlias - Tag 16
Files changed:
eagle_default/in/xml/xml-ref_voluntarycaelections.xml
SDP-85455 Asset Resolution Options for Warehouse Trade Interface
Two resolution options were added for the warehouseTrade object:
RESOLVE_PRIMARY is used to resolve the primaryAssetId; this can be useful to validate the securityAlias
<assetResolutionOption>RESOLVE_PRIMARY</assetResolutionOption>
SKIP is used to use the securityAlias passed from the incoming data without resolution
<assetResolutionOption>SKIP</assetResolutionOption>
Both options allow to load trades via the warehouseTrade object using only the securityAlias.
Files changed:
eagle_default/in/xml/include/xml-dbdirect_sec_resolution.inc
SDP-85425 SFTP Distribution with Optional Public Key
Optional SFTP Distribution Key. If the SFTP_PUBLICKEY parameter is not defined, then the process will use the SFTP_PRIVATEKEY instead.
Files changed:
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/reporter_dist_methods.inc
SDP-85213 DBTATA (TBA) Trades updated To Support All Lot Selection Methods
The AccountingTrade interface has been enhanced for TBA trades. All Eagle Lot Selection Methods or Tag 27 are available for the Processing Security Type (PST) DBTATA trades in EML now. Previously, IDLOT was only allowed for DBTATA.
Files changed:
eagle_default/in/include/csv-sell_columns.inc
SDP-84964 VOLCAELECTIONEXTRACT enhanced to support new elements
New custodian elements custodyBankAccount, custodianBankCode, custodianBankName, custodyBankSubaccount, and entityBankAlias are supported in the Corporate Actions Voluntary Elections for extract.
Xpath | DB mapping:
voluntaryCAElection/custodianBankCode | RULESDBO.ENTITY_CUSTODY_RELATIONSHIP.CUSTODY_BANK_CODE
/voluntaryCAElection/custodianBankName | RULESDBO.ENTITY_CUSTODY_RELATIONSHIP.CUSTODY_BANK_DESC
voluntaryCAElection/custodyBankAccount | RULESDBO.ENTITY_CUSTODY_RELATIONSHIP.CUSTODY_BANK_ACCT_NUM
/voluntaryCAElection/custodyBankSubaccount | RULESDBO.ENTITY_CUSTODY_RELATIONSHIP.CUSTODY_BANK_SUB_ACCT
/voluntaryCAElection/entityBankAlias | SECURITYDBO.VOL_CORP_ACTION_ELECTION.ENTITY_BANK_ALIAS
...
85947 Python CSV2XML: name 'getvariable' is not defined - adjust getVariable functionality
A new object called getvariable has been implemented to support dynamic expression calculation for variables.
Dynamic expression calculation means the presence of two execution steps, as opposed to the traditional single execution step seen with a variable, where expression can be only static.
For example:
[
"getvariable",
"extUSER_CHAR",
"iif(stringlength(get_instruction_param('USER_CHAR', :GVAR_RTR: )>0,get_instruction_param('USER_CHAR', :GVAR_RTR: ,'')"
],
In this case there will be two executions (calculations):
The first Execution will calculate expression (iif(stringlength(get_instruction_param('USER_CHAR', :GVAR_RTR: )>0,get_instruction_param('USER_CHAR', :GVAR_RTR: ,'')). In our example the result of this expression is |57|;
The second Execution will use the result of the 1st execution, it works as expression for the second execution. In this scenario, the value will be taken from column 57 of the incoming CSV file.
This variable then can be used in the mapping as typical variable:
[
":extUSER_CHAR:",
"",
false,
null,
"",
"accountingTrade/userChar5"
],
In the resulting file, we should expect to find the value from column 57 in the element accountingTrade/userChar5.
It works the same way if the variable is defined with static expression:
[
"variable",
"extUSER_CHAR",
"|57|"
],
However, in the scenario, it's expected that the definition will be dynamically defined and the column number will be modified.
SDP-82063 Added new flag ValuationSource for PRICINGREPORTEXTRACT
A new flag, ValuationSource, has been added for the PRICINGREPORTEXTRACT. When it set to MONTHLY, pricing data will be extracted from the ESTAR.MONTHLY_PORTFOLIO_VALUATION. When it set to DAILY or not presented in the RTR, data will be extracted from the ESTAR.MONTHLY_PORTFOLIO_VALUATION table. The default value is DAILY.
The functionality can also be specified in the /eagle_ml-2-0_custom_cm/w_config_custom.inc file via the global W_PRICINGREPORTEXTRACT_VALUATION_SRC variable for all PRICINGREPORTEXTRACT requests.
The RTR has higher priority over the custom include file. When both the ValuationSource and W_PRICINGREPORTEXTRACT_VALUATION_SRC are not null, the pricing table is chosen from the RTR parameter.
<taskParameter>
<name>ValuationSource</name>
<dataType>S</dataType>
<value>MONTHLY</value>
</taskParameter>
Files changed:
eagle_ml-2-0_cm/out/tagvalue/extract_pricing_report.inc
SDP-85845 VoluntaryCAElection interface resolves the custody elements
A new custodian element, entityBankAlias, is supported in the Corporate Actions Voluntary Elections for load.
If none of the new elements, custodianBankCode, custodyBankAccount, custodyBankSubaccount are sent, nothing changes for existing clients. However, if at least one of the new elements is present in the upload file, new logic is applied to check all custodian fields. Once all three elements are resolved, the entityBankAlias is resolved as a result. If even one of the identifiers is not found in the panel lookup or was not sent in the file, an "entityBankAlias" error is produced.
Additionally, a new processing option has been introduced:
<processingOptions>USE_ENTITY_BANK_ALIAS</processingOptions>
When using this option, the entityBankAlias is expected during the load process.
EagleML Xpath:
EagleML/referenceTransaction/voluntaryCAElection/custodianBankCode - Tag 1176
EagleML/referenceTransaction/voluntaryCAElection/custodyBankAccount - Tag 1660
EagleML/referenceTransaction/voluntaryCAElection/custodyBankSubaccount - Tag 1661
EagleML/referenceTransaction/voluntaryCAElection/entityBankAlias - Tag 16
Files changed:
eagle_default/in/xml/xml-ref_voluntarycaelections.xml
SDP-85455 Asset Resolution Options for Warehouse Trade Interface
Two resolution options were added for the warehouseTrade object:
RESOLVE_PRIMARY is used to resolve the primaryAssetId; this can be useful to validate the securityAlias
<assetResolutionOption>RESOLVE_PRIMARY</assetResolutionOption>
SKIP is used to use the securityAlias passed from the incoming data without resolution
<assetResolutionOption>SKIP</assetResolutionOption>
Both options allow to load trades via the warehouseTrade object using only the securityAlias.
Files changed:
eagle_default/in/xml/include/xml-dbdirect_sec_resolution.inc
SDP-85425 SFTP Distribution with Optional Public Key
Optional SFTP Distribution Key. If the SFTP_PUBLICKEY parameter is not defined, then the process will use the SFTP_PRIVATEKEY instead.
Files changed:
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/out/xml/t_voluntary_ca_election_streamingreporter_dist_methods.inceagle_ml-2-0_cm/out/tagvalue/extract_voluntary_ca_election.xml
SDP-84906 The multipleLegAccountingTrade single event inbound interface enhanced with new elements
multipleLegAccountingTrade single event inbound interface enhanced with new elements
<payTradeLeg>
<tradedInterest>30</tradedInterest> <!-- Tags 17937, 18280 -->
<tradedInterestBase>25</tradedInterestBase> <!-- Tags 17942, 18281 -->
<firstPeriodCouponRate>3</firstPeriodCouponRate> <!-- Tag 18282 -->
<lotLevelDatedDate>2024-01-04</lotLevelDatedDate><!-- Tag 18283 -->
</payTradeLeg>
<receiveTradeLeg>
<tradedInterest>40</tradedInterest> <!-- Tags 17938, 18280 if not exist in pay leg -->
<tradedInterestBase>35</tradedInterestBase> <!-- Tags 17943, 18281 if not exist in pay leg -->
<firstPeriodCouponRate>3</firstPeriodCouponRate> <!-- Tag 18282 if not exist in pay leg -->
<lotLevelDatedDate>2024-01-04</lotLevelDatedDate><!-- Tag 18283 if not exist in pay leg -->
</receiveTradeLeg>
Files changed:
eagle_default/in/xml/xml-accttrade_singleleg.xml
SDP-83690 Additional Load Fields for the ExchangePrice Load and ISSUEEXCHANGEPRICEEXTRACT
New fields added for the load and extract for the ExchangePrice Load and ISSUEEXCHANGEPRICEEXTRACT:
EagleML/referenceTransaction/exchangePrice/actualSettlementPrice SECURITYDBO.PRICE_EXCHANGE.PX_SETTLE_ACTUAL - Tag 18582
EagleML/referenceTransaction/exchangePrice/actualSettlementPriceDate SECURITYDBO.PRICE_EXCHANGE.PX_SETTLE_ACTUAL_DATE - Tag 18583
EagleML/referenceTransaction/exchangePrice/marketStatus SECURITYDBO.PRICE_EXCHANGE.MARKET_STATUS - Tag 18584
EagleML/referenceTransaction/exchangePrice/foreignInstitutionalInvestorLimit SECURITYDBO.PRICE_EXCHANGE.FII_LIMIT - Tag 18585
EagleML/referenceTransaction/exchangePrice/cleanDirtyFlag SECURITYDBO.PRICE_EXCHANGE.CLEAN_DIRTY_FLAG - Tag 18586
EagleML/referenceTransaction/exchangePrice/exchangeListedFlag SECURITYDBO.PRICE_EXCHANGE.EXCHANGE_LISTED_FLAG - Tag 18587
EagleML/referenceTransaction/exchangePrice/holidayFlag SECURITYDBO.PRICE_EXCHANGE.HOLIDAY_FLAG - Tag 18588
Also, following pricing flags are added for existing fields: closingPriceCondition, oidYieldPriceCondition, highPriceCondition, lowPriceCondition, referencePriceCondition, nominalDirtyPriceCondition, cleanInclOptionPriceCondition, dirtyInclOptionPriceCondition, cleanExclOptionPriceCondition, dirtyExclOptionPriceCondition, callOptionPriceCondition, putOptionPriceCondition, fairValuePriceCondition, averagePriceCondition, fixingPriceCondition, grossAskPriceCondition, grossBidPriceCondition, grossMidPriceCondition, midClosePriceCondition, meanPriceCondition, nominalPriceCondition, officialClosePriceCondition, vwapClosePriceCondition, askAdrPriceCondition, bidAdrPriceCondition, lastAdrPriceCondition, lastUpdatePriceCondition, naicPriceCondition, navCurrentPriceCondition, userFee1PriceCondition, userFee2PriceCondition, userFee3PriceCondition, userNav1PriceCondition, userNav2PriceCondition, userNav3PriceCondition, userNav4PriceCondition, userNav5PriceCondition, pxSettleCondition, actualSettlementPriceCondition, pxYestPriceCondition.
Files changed:
metadata/bind/eagleml_ref_exchangeprice.xml
eagle_default/in/xml/xml-ref_exchangeprice.xml
eagle_default/in/xml/include/xml-ref_security_pricing_common.inc
eagle_ml-2-0_cm/out/xml/t_issueprice_exchange_streaming.inc
SDP-87039 The Warehouse Trade EagleML Inbound interface was enhanced with additional elements
The warehouseTrade EagleML inbound interface enhanced with new elements:
EagleML/warehouseTransaction/warehouseTrade/eventSequence
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate1
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate2
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate3
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate4
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate5
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate6
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate7
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate8
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate9
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate10
File changed:
eagle_default/in/xml/xslt/wrh_egl_gen_interface3.xsl
SDP-86384 Data Rules Profile Templates for Conversion and Cloud Workflows for New Resources
Added Data Rules profile templates for the Conversion and Cloud Workflows for issuerentityrelationship, entityliquidity and entitypeergroupranking resources.
Files added:
msgcenter/profile/workflows/EagleToVault-cloud-entityliquidity_tmp.profile
msgcenter/profile/workflows/EagleToVault-cloud-entitypeergroupranking_tmp.profile
msgcenter/profile/workflows/EagleToVault-cloud-issuerentityrelationship_tmp.profile
msgcenter/profile/workflows/EagleToVault-conversion-entityliquidity_tmp.profile
msgcenter/profile/workflows/EagleToVault-conversion-entitypeergroupranking_tmp.profile
msgcenter/profile/workflows/EagleToVault-conversion-issuerentityrelationship_tmp.profile
Files changed:
eagle/estar/EAGLE_EXTRACTSERVICE.pkg
eagle/estar/eagle_default_workflows.pkg
SDP-86309 Additional fields supported for Oracle load via entityaccountingbasis resource
The fields PERF_NAV_FORWARD_PRICE_SOURCE (performanceNavForwardPriceSource) and PERF_NAV_VALUATION_FX_SOURCE (performanceNavValuationFxSource) now supported for load.
Files changed:
entityaccountingbasis-models.json
SDP-86235 The warehouseposition resource was updated to support a few missing fields
The warehouseposition resource has been enhanced to support additional fields for both database providers for load and extract. The mapping was implemented for missing canonical elements.
Database Field Canonical Element
POSITION_DETAIL.SHARE_CLASS - shareClass
POSITION_DETAIL.CUST_PRINCIPAL_BALANCE - custodianPrincipalBalanceBase
POSITION_DETAIL.CUST_PRINCIPAL_BALANCE_LOCAL - custodianPrincipalBalanceLocal
POSITION_DETAIL.CUST_INCOME_BALANCE - custodianIncomeBalanceBase
POSITION_DETAIL.CUST_INCOME_BALANCE_LOCAL - custodianIncomeBalanceLocal
Files Changed:
eagle-vocab-wh-shared.json
eagle-vocab-definition-wh-shared.json
warehouseposition-models.json
SDP-86200 Warehouseposition Reinitbatch Stored Procedure was updated for Oracle load to ingest data correctly
All warehouseposition fields loaded data passed without null values. Previously, a number of fields passed where ignored during the load process.
Files Changed:
metadata\core\ontology\templates\eagle_wrhs_warehouseposition_reinitbatch.oracle
SDP-86196 Dynamic expression calculation for Data Rules Custom Interface
A new object called getvariable has been implemented to support dynamic expression calculation for variables.
Dynamic expression calculation means the presence of two execution steps, as opposed to the traditional single execution step seen with a *variable*, where the expression can be only static.
For example:
[
"getvariable",
"extUSER_CHAR",
"iif(stringlength(get_instruction_param('USER_CHAR', :GVAR_RTR: )>0,get_instruction_param('USER_CHAR', :GVAR_RTR: ,'')"
],
In this case there will be two executions (calculations):
# The first Execution will calculate the expression (iif(stringlength(get_instruction_param('USER_CHAR', :GVAR_RTR: )>0,get_instruction_param('USER_CHAR', :GVAR_RTR: ,'')). In our example, the result of this expression is *|57|;*
# The second Execution will use the result of the 1st execution in the expression for the second execution. In this scenario, the value will be taken from column 57 of the incoming CSV file.
This variable then can be used in the mapping as typical variable:
[
":extUSER_CHAR:",
"",
false,
null,
"",
"accountingTrade/userChar5"
],
In the resulting file, the expectation is to find the value from column 57 in the element {{accountingTrade/userChar5}}.
It works the same way if the variable is defined with *static* expression:
[
"variable",
"extUSER_CHAR",
"|57|"
],
...
SDP-85213 DBTATA (TBA) Trades updated To Support All Lot Selection Methods
The AccountingTrade interface has been enhanced for TBA trades. All Eagle Lot Selection Methods or Tag 27 are available for the Processing Security Type (PST) DBTATA trades in EML now. Previously, IDLOT was only allowed for DBTATA.
Files changed:
eagle_default/in/include/csv-sell_columns.inc
SDP-84964 VOLCAELECTIONEXTRACT enhanced to support new elements
New custodian elements custodyBankAccount, custodianBankCode, custodianBankName, custodyBankSubaccount, and entityBankAlias are supported in the Corporate Actions Voluntary Elections for extract.
Xpath | DB mapping:
voluntaryCAElection/custodianBankCode | RULESDBO.ENTITY_CUSTODY_RELATIONSHIP.CUSTODY_BANK_CODE
/voluntaryCAElection/custodianBankName | RULESDBO.ENTITY_CUSTODY_RELATIONSHIP.CUSTODY_BANK_DESC
voluntaryCAElection/custodyBankAccount | RULESDBO.ENTITY_CUSTODY_RELATIONSHIP.CUSTODY_BANK_ACCT_NUM
/voluntaryCAElection/custodyBankSubaccount | RULESDBO.ENTITY_CUSTODY_RELATIONSHIP.CUSTODY_BANK_SUB_ACCT
/voluntaryCAElection/entityBankAlias | SECURITYDBO.VOL_CORP_ACTION_ELECTION.ENTITY_BANK_ALIAS
Files changed:
eagle_ml-2-0_cm/out/xml/t_voluntary_ca_election_streaming.inc
eagle_ml-2-0_cm/out/tagvalue/extract_voluntary_ca_election.xml
SDP-84906 The multipleLegAccountingTrade single event inbound interface enhanced with new elements
multipleLegAccountingTrade single event inbound interface enhanced with new elements
<payTradeLeg>
<tradedInterest>30</tradedInterest> <!-- Tags 17937, 18280 -->
<tradedInterestBase>25</tradedInterestBase> <!-- Tags 17942, 18281 -->
<firstPeriodCouponRate>3</firstPeriodCouponRate> <!-- Tag 18282 -->
<lotLevelDatedDate>2024-01-04</lotLevelDatedDate><!-- Tag 18283 -->
</payTradeLeg>
<receiveTradeLeg>
<tradedInterest>40</tradedInterest> <!-- Tags 17938, 18280 if not exist in pay leg -->
<tradedInterestBase>35</tradedInterestBase> <!-- Tags 17943, 18281 if not exist in pay leg -->
<firstPeriodCouponRate>3</firstPeriodCouponRate> <!-- Tag 18282 if not exist in pay leg -->
<lotLevelDatedDate>2024-01-04</lotLevelDatedDate><!-- Tag 18283 if not exist in pay leg -->
</receiveTradeLeg>
Files changed:
eagle_default/in/xml/xml-accttrade_singleleg.xml
SDP-83690 Additional Load Fields for the ExchangePrice Load and ISSUEEXCHANGEPRICEEXTRACT
New fields added for the load and extract for the ExchangePrice Load and ISSUEEXCHANGEPRICEEXTRACT:
EagleML/referenceTransaction/exchangePrice/actualSettlementPrice SECURITYDBO.PRICE_EXCHANGE.PX_SETTLE_ACTUAL - Tag 18582
EagleML/referenceTransaction/exchangePrice/actualSettlementPriceDate SECURITYDBO.PRICE_EXCHANGE.PX_SETTLE_ACTUAL_DATE - Tag 18583
EagleML/referenceTransaction/exchangePrice/marketStatus SECURITYDBO.PRICE_EXCHANGE.MARKET_STATUS - Tag 18584
EagleML/referenceTransaction/exchangePrice/foreignInstitutionalInvestorLimit SECURITYDBO.PRICE_EXCHANGE.FII_LIMIT - Tag 18585
EagleML/referenceTransaction/exchangePrice/cleanDirtyFlag SECURITYDBO.PRICE_EXCHANGE.CLEAN_DIRTY_FLAG - Tag 18586
EagleML/referenceTransaction/exchangePrice/exchangeListedFlag SECURITYDBO.PRICE_EXCHANGE.EXCHANGE_LISTED_FLAG - Tag 18587
EagleML/referenceTransaction/exchangePrice/holidayFlag SECURITYDBO.PRICE_EXCHANGE.HOLIDAY_FLAG - Tag 18588
Also, following pricing flags are added for existing fields: closingPriceCondition, oidYieldPriceCondition, highPriceCondition, lowPriceCondition, referencePriceCondition, nominalDirtyPriceCondition, cleanInclOptionPriceCondition, dirtyInclOptionPriceCondition, cleanExclOptionPriceCondition, dirtyExclOptionPriceCondition, callOptionPriceCondition, putOptionPriceCondition, fairValuePriceCondition, averagePriceCondition, fixingPriceCondition, grossAskPriceCondition, grossBidPriceCondition, grossMidPriceCondition, midClosePriceCondition, meanPriceCondition, nominalPriceCondition, officialClosePriceCondition, vwapClosePriceCondition, askAdrPriceCondition, bidAdrPriceCondition, lastAdrPriceCondition, lastUpdatePriceCondition, naicPriceCondition, navCurrentPriceCondition, userFee1PriceCondition, userFee2PriceCondition, userFee3PriceCondition, userNav1PriceCondition, userNav2PriceCondition, userNav3PriceCondition, userNav4PriceCondition, userNav5PriceCondition, pxSettleCondition, actualSettlementPriceCondition, pxYestPriceCondition.
Files changed:
metadata/bind/eagleml_ref_exchangeprice.xml
eagle_default/in/xml/xml-ref_exchangeprice.xml
eagle_default/in/xml/include/xml-ref_security_pricing_common.inc
eagle_ml-2-0_cm/out/xml/t_issueprice_exchange_streaming.inc
SDP-87039 The Warehouse Trade EagleML Inbound interface was enhanced with additional elements
The warehouseTrade EagleML inbound interface enhanced with new elements:
EagleML/warehouseTransaction/warehouseTrade/eventSequence
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate1
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate2
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate3
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate4
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate5
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate6
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate7
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate8
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate9
EagleML/warehouseTransaction/warehouseTrade/trdDetExtUserDate10
File changed:
eagle_default/in/xml/xslt/wrh_egl_gen_interface3.xsl
SDP-86384 Data Rules Profile Templates for Conversion and Cloud Workflows for New Resources
Added Data Rules profile templates for the Conversion and Cloud Workflows for issuerentityrelationship, entityliquidity and entitypeergroupranking resources.
Files added:
msgcenter/profile/workflows/EagleToVault-cloud-entityliquidity_tmp.profile
msgcenter/profile/workflows/EagleToVault-cloud-entitypeergroupranking_tmp.profile
msgcenter/profile/workflows/EagleToVault-cloud-issuerentityrelationship_tmp.profile
msgcenter/profile/workflows/EagleToVault-conversion-entityliquidity_tmp.profile
msgcenter/profile/workflows/EagleToVault-conversion-entitypeergroupranking_tmp.profile
msgcenter/profile/workflows/EagleToVault-conversion-issuerentityrelationship_tmp.profile
Files changed:
eagle/estar/EAGLE_EXTRACTSERVICE.pkg
eagle/estar/eagle_default_workflows.pkg
SDP-86309 Additional fields supported for Oracle load via entityaccountingbasis resource
The fields PERF_NAV_FORWARD_PRICE_SOURCE (performanceNavForwardPriceSource) and PERF_NAV_VALUATION_FX_SOURCE (performanceNavValuationFxSource) now supported for load.
Files changed:
entityaccountingbasis-models.json
SDP-86235 The warehouseposition resource was updated to support a few missing fields
The warehouseposition resource has been enhanced to support additional fields for both database providers for load and extract. The mapping was implemented for missing canonical elements.
Database Field Canonical Element
POSITION_DETAIL.SHARE_CLASS - shareClass
POSITION_DETAIL.CUST_PRINCIPAL_BALANCE - custodianPrincipalBalanceBase
POSITION_DETAIL.CUST_PRINCIPAL_BALANCE_LOCAL - custodianPrincipalBalanceLocal
POSITION_DETAIL.CUST_INCOME_BALANCE - custodianIncomeBalanceBase
POSITION_DETAIL.CUST_INCOME_BALANCE_LOCAL - custodianIncomeBalanceLocal
Files Changed:
eagle-vocab-wh-shared.json
eagle-vocab-definition-wh-shared.json
warehouseposition-models.json
SDP-86200 Warehouseposition Reinitbatch Stored Procedure was updated for Oracle load to ingest data correctly
All warehouseposition fields loaded data passed without null values. Previously, a number of fields passed where ignored during the load process.
Files Changed:
metadata\core\ontology\templates\eagle_wrhs_warehouseposition_reinitbatch.oracle
SDP-86196 Information in data load error is not sufficient to triage issue
Logic for reporting error messages to the end users was improved to inherit global parameter for length, also this value can be adjusted via RTR parameter: procstatusmsgsize. The Default size is set to 300.
For troubleshooting purposes you can increase value to get more details via error message, but please be aware that too long error messages can cause unexpected behavior.
If the error has a line number, then the error message will have text from this line for troubleshooting purposes.
Files changed:
common-core/descriptor/dbdescriptor.py
common-core/processing-env/proc_log_stru.py
common-core/processing-env/processing_context.py
common-core/processing-env/processing_log.py
common-core/processing-env/proc_log_policy.py
...