EagleML Release Notes - March 2018

Owned by Ilie Tomac Jnr (Deactivated)
Last updated: Nov 13, 2024 by Kinga Huszno
11 min read

This release uses XSD Revision 289

There are four overlay files that are currently packaged as part of the EagleML monthly release. Please refer to About EagleML Overlays for specific details and impact to you.

Enhancements

Enterprise

EagleML

Added Support for the Extended Detail Entity Properties Model - IncludeExtendedDetails and Shareholder Activity Model
Support was added for the Extended Detail Entity Properties Model - IncludeExtendedDetails and Shareholder Activity Model
The “IncludeExtendedDetails” and “includeEntityShareClass” flags were added.
Files changed:
extract_acct_intraday_nav.inc
t_acct_intraday_nav_streaming.inc

This issue was tracked as Item #156498.

 

Adjusted Rules to Skip Records if EntityID is not Resolved by XREFs
Currently if the entity is not found, the record is marked as a failure, by default.
The logic was updated, so it works as expected, thus if varSkipIfUnResolved parameter is set to Y, the record will be skipped, and no error will be raised.
Files Changed:
- entity_xref_resolution.inc

This issue was tracked as Item #158413.

 

Added Mapping for 'updateSource' element  in Code Value Inbound
Data being sent to the UPD_OPER field in the pace_masterdbo.code_values table was not getting updated with the value from the ‘updateSource’ in the incoming file. As a result this field was being defaulted to ‘MCADMIN’
The inbound rule for Code Value was updated with the missed mapping for the 'updateSource' element. An overlay was created for the pan-ccodeval.htm panel to ensure a properly working update cycle. This overlay was included into the install package. If you install the package without overlays, a manual overlay should be added to the environment in order for this feature to work.
In the case that the AllowAssign944 parameter is set to 1 in msgservice.ini, the UPD_OPER column with the value being sent in the 'updateSource' field of the incoming file. In the case that the AllowAssign944 parameter is set to 0 in msgservice.ini the UPD_OPER column is updated with the current user name value.
Files changed:
estar\tpe\dynamic\msgcenter\eagle_default\in\xml\xml-ref_codevalue.xml
estar\tpe\dynamic\custdat\eagle\star\reference\pan-ccodeval.htm

This issue was tracked as Item #158691.

 

Create Entity Status Master Extract Object
A new Entity Status object called 'EntityAccountingStatus' was created.
The feed type is : ENTITYACCOUNTINGSTATUSEXTRACT.
The available filters are:
- Date filters (UpdateDate and EffectiveDate)
- Entity filters (including partitions)
- Traverse Hierarchy filter
The new parameters are: 
1) RequestedStatus, default = null
Output fields ‘status’ and ‘reportType’ receive their values depending on the value of this RTR-parameter:
CASE WHEN RequestedStatus = 'controlCenterDaily'        THEN controlCenterDaily
     WHEN RequestedStatus = 'accountingPeriodDaily'     THEN accountingPeriodDaily
     WHEN RequestedStatus = 'navDaily'                  THEN navDaily
     WHEN RequestedStatus = 'accountingPeriodMonthly'   THEN accountingPeriodMonthly
     WHEN RequestedStatus = 'navMonthly'                THEN navMonthly
     WHEN RequestedStatus = 'controlCenterMonthly'      THEN controlCenterMonthly
     ELSE NULL
END  status,
RequestedStatus as reportType

2) UseShadowTable, default = ‘Y’
If the parameter ‘UseShadowTable’ = Y, then the 'shadow' tables
SHADOWDBO.ARCH_CTRLCTR_ENTITY_STATUS_CLO
SHADOWDBO.ARCH_CTRLCTR_ME_ENTITY_STATUS_
will be used as addition sources for the following fields:
- controlCenterDaily
- controlCenterDailyUpdateDate
- controlCenterMonthly
- controlCenterMonthlyUpdateDate

Files changed:
- extract_entity_accounting_status.xml
- extract_entity_accounting_status.inc
- t_entity_accounting_status_streaming.xml
- t_entity_accounting_status_streaming.inc

This issue was tracked as Item #158818.

 

Added New Rule Cap Fund Investmensts to Accounting Trade Inbound Interface
The new Cap Fund Investmensts rule for the Accounting Trade inbound interface was added for loading data using these panels:
Initial Fund (pan-initialfunding.htm) - element <buySellIndicator> = 'LPOPEN'
Capitalization (pan-capitalization.htm) - element <buySellIndicator> = 'LPCASH'
Capital Call (pan-capitalcall.htm) - element <buySellIndicator> = 'LPCOMMIT'
The following elements were added to the XSD schema as a new group in the AccountingTrade type CapFundInvestmentsInfo.model:
transactionName
totalGainLocal
totalGain
openCostBase
incomeAmountLocal
incomeAmountBase
expenseAmountLocal
expenseAmountBase
cashEventType
tradeStatus
New rule: xml-accttrade_capfundinvestments.xml
Files changed: csv-capfundinvestments_columns.inc, csv-capfundinvestments_panels.inc
Stream: eagle_ml-2-0_default_in_xml_acct_trades

This issue was tracked as Item #158869.

 

Added Missing Fields to WRHSCSTDACTIVITYEXTRACT
Some fields were missing from the WRHSCSTDACTIVITYEXTRACT extract because there was a mismatch between aliases in the Q rule and in T rules.
The aliases for the following fields were updated:
-action
-units
-userNotes
-balanceInstance

Files changed:
extract_warehouse_custody_activity.inc

This issue was tracked as Item #158923.

 

Adjusted Analytics Node Elements into wrh_egl_gen_interface3.xsl
The PD_CURVE_ANALYTICS elements were missing from the wrh_egl_gen_interface3.xsl.
The wrh_egl_gen_interface3.xsl was updated to reflect the missing PD_CURVE_ANALYTICS parameters.
Files changed:

wrh_egl_gen_interface3.xsl

This issue was tracked as Item #158952.

 

Added Support for Missed Entity Rule fields in ENTITYEXTRACT and ENTITYACCBASISEXTRACT
Some of Entity Rule fields were missing from the ENTITYEXTRACT and ENTITYACCBASISEXTRACT extracts
1. The following elements were added to the Generic Entity interface and ENTITYEXTRACT:
entityTransaction/genericEntity/entityRulesUniqueKey/backupWithholdingRuleUniqueKey/withholdingRuleDescription
entityTransaction/genericEntity/entityRulesUniqueKey/basisProcessingRuleUniqueKey/basisProcessRuleName
entityTransaction/genericEntity/entityRulesUniqueKey/primaryMixedCostBasisRuleUniqueKey/primaryMixedCostBasisRuleName
entityTransaction/genericEntity/entityRulesUniqueKey/urglAccountingRuleUniqueKey/accountingRuleName
entityTransaction/genericEntity/entityRulesUniqueKey/accretionAccountingRuleUniqueKey/accountingRuleName
entityTransaction/genericEntity/entityRulesUniqueKey/accretionAccountingRuleUniqueKey/accountingRuleDesc

2. The following elements were added to the Accounting Basis interface and ENTITYACCTBASISEXTRACT:
entityTransaction/entityAccountingBasis/entityRulesUniqueKey/cashProcessRulesUniqueKey/cashRuleName
entityTransaction/entityAccountingBasis/entityRulesUniqueKey/earnthruRuleHdrUniqueKey/earnThruRuleName
entityTransaction/entityAccountingBasis/entityRulesUniqueKey/monthEndDateRuleUniqueKey/monthRuleDesc
entityTransaction/entityAccountingBasis/entityRulesUniqueKey/ccSettlementRuleUniqueKey/ccSettlementRuleDescription
entityTransaction/entityAccountingBasis/entityRulesUniqueKey/backupWithholdingRuleUniqueKey/withholdingRuleDescription
entityTransaction/entityAccountingBasis/entityRulesUniqueKey/basisProcessingRuleUniqueKey/basisProcessRuleName
entityTransaction/entityAccountingBasis/entityRulesUniqueKey/primaryMixedCostBasisRuleUniqueKey/primaryMixedCostBasisRuleName
entityTransaction/entityAccountingBasis/entityRulesUniqueKey/urglAccountingRuleUniqueKey/accountingRuleName
entityTransaction/entityAccountingBasis/entityRulesUniqueKey/accretionAccountingRuleUniqueKey/accountingRuleName
entityTransaction/entityAccountingBasis/entityRulesUniqueKey/accretionAccountingRuleUniqueKey/accountingRuleDesc

3. The duplicate mtmRateSource element (Generic Entity Interface) was removed from the XSD

  1. The contractualCashSettlementRule type was changed from integer to string in the XSD

  2. Logic for resolving the Month End Date Rule was updated in the Generic Entity Inbound rule. The lookup has been replaced with a SQL request.

The following parameter with a value of "Y" is required:

<taskParameter>
<name>IncludeEntityRuleKeys</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter>

Files changed:
estar\tpe\dynamic\eagleml\schema\eagleml-entity-2-0.xsd
estar\tpe\dynamic\eagleml\schema\eagleml-entity-shared-2-0.xsd
estar\tpe\dynamic\eagleml\schema\estar\tpe\dynamic\msgcenter\
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\tagvalue\extract_entity_accounting_basis.inc
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\t_entity_accounting_basis_streaming.inc
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\tagvalue\extract_entity.inc
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\t_entity_streaming_eml.inc
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\t_entity_streaming.inc
estar\tpe\dynamic\msgcenter\eagle_default\in\xml\xml-ent_entitygeneric.xml

This issue was tracked as Item #159006.

 

Updated Logic Around HubSentBy and UseSentBy
There is an option to either reflect a database value or a pass through value instead. This can be controlled in extracts by using one of the following two parameters:

UseSentBy = Y (This retrieves the DB value - eg. MYDB)
HubSentBy = MYVALUE (This can be any value)
 
UseSentBy produces http://www.eagleinvsys.com/MYDB
HubSentBy produces http://www.eagleinvsys.com/MYVALUE
 
When executing a direct RTR or SOAP / WS request, the UseSentBy is independent from the HubSentBy parameter.
In the Generic Extract workflow, the UseSentBy parameter must be set to Y to activate the UseSentBy or the HubSentBy parameter:
The UseSentBy is required to activate either output.
 
<taskParameter>
<name>ALLEXTRACTS_HubSentBy</name>
<dataType>S</dataType>
<value>MYVALUE</value>
</taskParameter>
<taskParameter>
<name>ALLEXTRACTS_UseSentBy</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter>

UseSentBy is set to Y by default when HubSentBy is specified, so the user doesn't need to set UseSentBy = Y manually.
Files changed:
extract_start.inc

This issue was tracked as Item #159007.

 

mktValueSource logic added for WRHSNAVMULTIEXTRACT and added into XSD for WRHSNAVMULTIEXTRACT and WRHSNAVMONTHENDEXTRACT
Logic for the mktValueSource filter was requested for the WRHSNAVMULTIEXTRACT feed type. The mktValueSource field is required in EagleML for WRHSNAVMULTIEXTRACT and WRHSNAVMONTHENDEXTRACT.
Logic for the mktValueSource filter was added to the WRHSNAVMULTIEXTRACT feed. WRHSNAVMULTI and WRHSNAVMONTHEND extracts now both include this field.
Files changed:
t_warehouse_nav_multi_streaming.inc
t_warehouse_nav_month_streaming.inc
extract_nav_mkt_value_cash_fields.inc

This issue was tracked as Item #159185.

 

Added Ability to Store NG Debug Information for GenericSMF in to a Separate File
The process of saving the Result Variable from the smf_egl_gen_interface_ng.xsl to a file for debugging was adjusted in the generic SMF interface.
The msgxchg_sec_core.inc file was modified to save the debug data into different files depending on whether CORE or NG mode was enabled.

This issue was tracked as Item #159245.

 

EagleML - NPORT Line of Credit
There was a request to create a new inbound interface for Line of Credit.
The new inbound Line of Credit interface was created. It supports load/update of nested Entity Relationship and Issuer Relationship records.

This issue was tracked as Item #159281.

 

Add skipIfExist Flag for Generic Entity
The skipIfExist flag was absent in the Generic Entity interface.
Logic for skipIfExist flag was added in the case that the entity should not be updated.

Files changed:
estar\tpe\dynamic\msgcenter\eagle_default\in\xml-ent_entitygeneric.xml

This issue was tracked as Item #159612.

 

New Zero Balance Filter Switch to Filter Out ShareParValue and BookValue in Case of a Value of 0
There was a request to create a new switch that will control the behavior of the ZeroBalance filter for the Warehouse Position and Open Lots extracts. The ShareParValue and BookValue fields will be controlled separately.
If IncludeZeroBalances = ‘Y’ (or omitted) - there is not filter on Cash records.
If IncludeZeroBalances = ‘N’ - the filter is applied.

The new RTR-parameter is: ZeroBalanceSwitch with possible values of:
1) Cash (default value)
Filter is used in the full form:
NOT (SECURITYDBO.SECURITY_MASTER.INVESTMENT_TYPE = 'CASH'
AND HOLDINGDBO.POSITION_DETAIL.SHARE_PAR_VALUE = 0
AND HOLDINGDBO.POSITION_DETAIL.BOOK_VALUE = 0)

2) ParBookValue
NOT (HOLDINGDBO.POSITION_DETAIL.SHARE_PAR_VALUE = 0
AND HOLDINGDBO.POSITION_DETAIL.BOOK_VALUE = 0)

3) ShareParValue
NOT (HOLDINGDBO.POSITION_DETAIL.SHARE_PAR_VALUE = 0)

Files changed:
- extract_filter_zero_balance.inc - rule is created
- extract_warehouse_position.inc
- extract_warehouse_openlot.inc

This issue was tracked as Item #159626.

 

Zero Balance Filter Switch is Added Into the Held Filter
The 'ZeroBalanceSwitch' parameter will be applied in Held mode for the Generic SMF Extract.
The Held filter uses the ‘IncludeZeroBalances' parameter to filter position records: (SHARE_PAR_VALUE != 0).
The 'ZeroBalanceSwitch' parameter needs to control the Zero Balance filter so as to control the three possible values:
- NOT (INVESTMENT_TYPE = 'CASH' AND BOOK_VALUE = 0 AND SHARE_PAR_VALUE = 0)
- NOT (BOOK_VALUE = 0 AND SHARE_PAR_VALUE = 0)
- NOT (SHARE_PAR_VALUE = 0)

If IncludeZeroBalances = Y - there is not filter on Zero Balance records
If IncludeZeroBalances = N - (default for Held mode) the filter is applied.

Added the 'ZeroBalanceSwitch' parameter with possible values of:
1) Cash
Filter is used in the full form:
NOT (SECURITYDBO.SECURITY_MASTER.INVESTMENT_TYPE = 'CASH'
AND HOLDINGDBO.POSITION_DETAIL.SHARE_PAR_VALUE = 0
AND HOLDINGDBO.POSITION_DETAIL.BOOK_VALUE = 0)

2) ParBookValue
NOT (HOLDINGDBO.POSITION_DETAIL.SHARE_PAR_VALUE = 0
AND HOLDINGDBO.POSITION_DETAIL.BOOK_VALUE = 0)

3) ShareParValue (or missed), default for Held mode:
NOT (HOLDINGDBO.POSITION_DETAIL.SHARE_PAR_VALUE = 0)

Files changed:
- extract_filter_held.inc
- extract_filter_zero_balance.inc

This issue was tracked as Item #159628.

 

New object and EagleML load added for Bank Settlement Cash
A new EagleML object called Bank Settlement Cash was created.
A new XSD object was created for Bank Settlement Cash and a new interface was added into eagle_ml-2-0_default_in_xml_acct_cash.
Files changed:
bank_cash_settlement_aliases.inc
xml-bank_cash_settlement.xml

This issue was tracked as Item #159725.

 

Added Auto Bind Generation For GenericIssueAnalytic
There were differences between parameters within stored procedures across different environments.


  1. Description for the INS_UPD_SECURITY_ANALYTICS, INS_UPD_SECURITY_ANALYTICS_EQ and INS_UPD_SECURITY_ANALYTICS_FI stored procedures were added to "eagleml_reference.xml".
    2. All MSGEXCHANGE that would call the stored procedure were deleted from the “xml-ref_genericissueanalytic.xml” rule. The NG params list creation was also deleted. All of this was replaced with the use of the new “ins_upd_genericissueanalytic_req.inc” include and the “call_eagleml_dbml_request.inc” include.

This issue was tracked as Item #159738.

 

Extract interface added BANKCASHSETTLEMENTEXTRACT
A new BankCashSettlement EagleML interface was created.

A new outbound interface called BANKCASHSETTLEMENTEXTRACT was added.

Files changed:
extract_bank_cash_settlement.inc
extract_bank_cash_settlement.xml
extracts.rsf
t_eagleml-2-0_streaming.rsf
t_bank_cash_settlement_streaming.inc
t_bank_cash_settlement_streaming.xml

This issue was tracked as Item #160105.

 

Added New User Inbound Interface to Generic Loader Workflow
The generic loader workflow was using the old User inbound interface.
Logic was updated, so that now the generic loader workflow is now using the new User inbound interface.

Files changed:
- msgcenter/eagle_ml-2-0_workflows/eagle_wrf_generic_load.wrf
- msgcenter/eagle_ml-2-0_workflows/eagle_wrf_generic_load_system_objects.wrf
- msgcenter/eis/ejmwf/eagle_wrf_generic_load.ejmwf
- msgcenter/eis/ejmwf/eagle_wrf_generic_load_system_objects.ejmwf
- msgcenter/eis/profiles/eagle_wrf_generic_load.ejmsp

This issue was tracked as Item #160470.

 

Added Stream eagle_ml-2-0_default_cm_validate_by_xsd for Validation XML File Against XSD
There was no build in logic for validating XML files against EagleML XSD
The eagle_ml-2-0_default_cm_validate_by_xsd stream was created. It supports the following RTR parameters:
•         XSDValidationType  - validation type (ALL, XMLLINT, SAX)
•         XSDShemaPath –  Folder with custom schema
•         SourceFolder – Folder with XML files for validation

Files changed:
eagle_default_cm_validation_by_xsd.rsf
eagle_default_cm_validation_by_xsd.xml

This issue was tracked as Item #161173.

EJM

Delta Based Filter is Added to Traded CA Extract
There was a request to add the Delta Based filter to the Traded CA Extract.
The Delta Based filter was added for the Traded CA Extract.
<taskParameter>
 <name>DeltaBased</name>
 <dataType>S</dataType>
 <value>Y</value>
</taskParameter>

Files changed:
- extract_acct_traded_cash_activity.inc
- extract_acct_traded_cash_activity.xml

This issue was tracked as Item #158478.

 

Increase Timeout to listfiles Command
The ‘list file’ command was failing due to a timeout with a value of 20 seconds.
The timeout value was increased to 90 seconds.
Files changed:
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\tagvalue\data_file_task.x

This issue was tracked as Item #159835.

 

Added Support of Cleanup Parameters
If there were too many files piled up in the cmw/in folder timeout errors would occur.
Support for cleanup parameters was added:
• RTR parameter   –  CleanupStagingFiles=Y/N ,default is N
• Config parameter  – W_CLEANUP_STAGING_FILES=Y/N ,default is N
The following rules were changed
· eagle_ml-2-0_default_cm_unpacker (/eagle_ml-2-0_cm/unpacker/wrf_unzip.prf)
· eagle_ml-2-0_default_cm_control_message (/eagle_ml-2-0_cm/file_base64_encode.inc)
· eagle_ml-2-0_default_cm_control_message(runtaskrequest.xml)
· eagle_wrf_generic_load.wrf

This issue was tracked as Item #159843.

Software Fixes

Enterprise

EagleML

Created T-rule for Entity Analytic Type
There was no non-streaming T-rule for the Entity Analytic extract.
The non-streaming Entity Analytic extract T-rule was created.
Feed type: ENTITYANALYTICEXTRACT
Name of rule: t_entity_analytics.xml
Stream: eagle_ml-2-0_default_out_t

This issue was tracked as Item #159013.

 

EntityPeerGroupRanking: Changed Incoming Value to Have to_date Function During INSERT INTO
The effective_date parameter is declared as a VARCHAR in the stored procedure and therefore requires the use of a to_date function.
The to_date function was added to the stored procedure.
List of files changed:
xml-ent_entity_peer_group_ranking.xml

This issue was tracked as Item #159248.

 

Added Base64 Compress in Generic Extract Workflow
A user was unable to send archive files into the JMS queue.
The eagle_ml-2-0_default_cm_packer stream was split into two separate streams:
• eagle_ml-2-0_default_cm_packer –  this stream performs only the file compression
• eagle_ml-2-0_default_cm_file_distribution – this stream is responsible for the archive distribution
Both streams are based on common includes for compression and distribution. New compression methods were added in the eagle_ml-2-0_default_cm_packer stream.
Compress – This option determines how file\files will be compressed (Y[ZIP], ZIP, B64, GZIP+B64, ZIP+B64)
• Y – Default method ZIP
• ZIP – files will be compressed as a ZIP archive
• B64– files will be compressed as a ZIP archive and then it will be compress to base64 text file
• GZIP+B64 – files will be compressed as a tar.gz archive and then it will be compress to a base64 text file
• ZIP+B64– files will be compressed as a ZIP archive and then it will be compress to a base64 text file
ExtractDeliveryMethod – This option determines how the archive will be delivered (JMS,FTP,SFTP,FILE)
DeliveryStreamName – This parameter is needed when you want to use ExtractDeliveryMethod = JMS and use a custom stream, otherwise the default W_JMS_DEF_EXTRACT_STREAM stream will be used.
When ExtractDeliveryMethod is JMS archive file will be automatically compressed into base64 file and delivered to the correct stream (DeliveryStreamName  or W_JMS_DEF_EXTRACT_STREAM)

This issue was tracked as Item #159413.

 

Source Inbound Did not Populate UpdateSource And Update Datetime
Inbound source messages would not update the UpdateSource field or the datetime.
1. The "eagleml-ref-2-0.xsd" XSD was changed – the UpdateSource.model was added to the Source complex type.
2. A request to set UPD_SOURCE and UPD_DATETIME was added to the "xml-ref_source.xml" rule.

This issue was tracked as Item #159588.

 

Fixed grouping issue with T-Stream for XREFEXTRACT
The issue is that there is one security for two different Issue Name/Description and XREF values. It affects the SMFIdentifiers object and XREFEXTRACT feed type.
The t_xref.xml rule was modified. The EXECUTEON="END" option was added for three COL TAG definitions. The t_xref_streaming.inc include file was modified with the same fix.

This issue was tracked as Item #159627.

 

Changed Condition in Logic for SkipIfExistFlag
The condition for the SkipIfExistFlag was wrong. The StringLength function was returning 1 even when the argument was equal to 0.
The condition was changed to use Atoi instead of StringLength.
Files Changed:
estar\tpe\dynamic\msgcenter\eagle_default\in\xml\include\security_resolution_full.in

This issue was tracked as Item #159822.

 

Added ratingSrc alias to xml-ref_issuerating_all.xml Rule
The xml-ref_issuerating_all.xml rule did not have the ratingSrc alias in the RAW2INTERMEDIATE section, but this node existed in the XSD and was also in the IWS mapping.
The ratingSrc alias was added into xml-ref_issuerating_all.xml rule

This issue was tracked as Item #160499.

 

The Realized Gain Loss Extract worked incorrect with an Entity List
The REALIZEDGAINLOSSEXTRACT did not return records for all entities when executed using entity list filter. There was an incorrect overwriting of the sqlparam_accountingBasis and sqlparam_baseCurrency variables in the ‘foreach’.
Logic for these variables was changed to resolve the issue.
Files changed:
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\tagvalue\ extract_acct_realized_gain_loss.inc

This issue was tracked as Item #160617.

 

Fixed Elements Order in  ENTITYBANKRELEXTRACT According with the XSD Schema
The ENTITYBANKRELEXTRACT EagleML output was not passing validation against the  XSD.
The baseAmount element was returning causing the following error - Schemas validity error - Element [baseAmount]. This element is not expected.
The order of elements was changed accordingly in the last XSD version="$Revision: 289 $"
Files chagned:
t_entity_bank_relationship.xml

This issue was tracked as Item #160883.

 

EagleMl: ISSUEEXCHANGEPRICEEXTRACT Made Valid Against XSD
The ISSUEEXCHANGEPRICEEXTRACT EagleML output was not passing validation against the XSD.
The T-rules fixed. Streaming support was added for ISSUEEXCHANGEPRICEEXTRACT.

Files changed:
w_config.inc
t_eagleml-2-0_streaming.rsf
t_issueprice_exchange.xml
t_issueprice_exchange_streaming.inc
t_issueprice_exchange_streaming.xml

This issue was tracked as Item #160906.

 

Made WRHSCASHFLOWPROJEXTRACT Output Valid Against XSD Schema
WRHSCASHFLOWPROJEXTRACT EagleML output was not passing validation against XSD.
The error related to this appeared as follows:
element baseAmount- Schemas validity error - Element [baseAmount]. This element is not expected.
The order of elements was changed accordingly in the last XSD version="$Revision: 289 $"
Files:
t_warehouse_cash_flow_proj.xml
t_warehouse_cash_flow_proj_streaming.inc
t_warehouse_cash_flow_proj_streaming_eml.inc

This issue was tracked as Item #160907.

 

Fixed SQL Request When Using IncludeAccrualRate in RTR
Duplicate rows are appearing in the output when passing the IncludeAccuralRate parameter in an RTR used for a warehouse open lot extract. The reason for this is a join to the ESTAR table which contains two records with the same event id.
The SQL request was changed to mitigate this problem.

File changed:

"extract_warehouse_openlot.inc"

This issue was tracked as Item #160927.

 

Improvement of Performance for Generic SMF Load in Xref Aliases Resolution and Insert/Update of Xrefs Requests
Generic SMF load performance was getting hit as a result of two dynamically generated requests which were using literals instead of bind variables. The two requests were:

  1. Xref Aliases Resolution
    2. Insert/Update Xrefs

    The following optimizations were introduced to improve Generic SMF load performance.

    1. The request for xref aliases resolution was replaced with direct call of the PACE_MASTERDBO.ESTAR_SEC.XREF_QUERY_ONE_ROW SP via MSGEXCHANGE.

    2. The request for insert/update xrefs was replace with a parametrized request which uses an XMLDBAPI bind for Oracle. The bind file was placed into metadata\bind\estardbc\bind-custom-smf-xrefs.xml file. It is linked with the bind.xml file dynamically during EagleML installation in ‘eagle_ml-2-0_default_cm_w_setup’ step.

    For MSSQL the request was optimized in order for the body of the request to be the same for each xref pair. Also the part of request where security alias is resoling was moved to a separate request. This request is executed only if security_alias (tag 10) was not resolved earlier. Finally the request for updating secmaster_history after loading xrefs was also parametrized for Oracle and MSSQL.

Files changed:

estar\tpe\dynamic\msgcenter\eagle_default\in\xml\include\xref_alias_resolution.inc

estar\tpe\dynamic\msgcenter\eagle_default\in\xml\include\ins_upd_xrefs.inc
estar\tpe\dynamic\metadata\bind\estardbc\bind-custom-smf-xrefs.xml
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\in\xml\include\w_setup_eagle_version.xml

This issue was tracked as Item #160991.

 

Fixed Cash SPD Delta Extract Query in I2I
The HUB and Spoke environments were not in sync because the cash activity query stored procedure was returning extra records.
The stored procedure was updated with an additional condition: CANCEL_STATUS != Y. As a result the query no longer returns extra records, which had been causing position records on the SPOKE to get deleted.
Files changed:
extract_warehouse_spd_delta_log.inc

This issue was tracked as Item #161071.

EJM

Added Functionality to Define URLs in RTR, ACK, TSR, Extracts through Custom Configuration
Functionality for defining URLs in RTR, ACK, TSR and Extract outputs through custom configuration was developed.
Files changed:
eagle_extractor_demand.xml
create_cm.inc
create_cm_load.inc
create_tsr.inc
extract_upd_header.inc
taskstatus_reply.inc
w_config.inc
t_eagle_header_fields.inc
t_eagle_header_streaming.inc
task_reporter.xml
taskacknowledgement.xml

This issue was tracked as Item #159982.