Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

ESP-333: EAGLE ML - ADD NEW ACCOUNTING EXTRACT OBJECT COMPLIANCE2A7PRICINGEXTRACT

An extract was created for the new Compliance2A7PricingReport EagleML object. The Compliance2A7PricingReport object was added to the XSD with an outbound interface created for it. The feed type of the extract is COMPLIANCE2A7PRICINGEXTRACT. This extract calls the eagle/star/reports/pan-ec_2a7report.htm panel, which allows the use of the following filters (panel tags are shown after the EagleML equivalent filter):

...

Example of run task request:
<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>COMPLIANCE2A7PRICINGEXTRACT</messageId>
<sentBy>http://www.client.com</sentBy>
<sendTo>http://www.eagleinvsys.com/eagle_ml-2-0_default_cm_control_message</sendTo>
<replyTo>http://www.client.com/Eagle Control Messages</replyTo>
<creationTimestamp>2012-08-02T22:13:32.272-05:00</creationTimestamp>
</header>
<taskIdentifier>
<correlationId correlationIdScheme="correlationIdScheme">asCOMPL2A7PRICING_160818_04</correlationId>
<businessTaskId correlationIdScheme="businessTaskIdScheme">COMPLIANCE2A7PRICINGEXTRACT</businessTaskId>
</taskIdentifier>
<taskTypeEnum>NEW</taskTypeEnum>
<taskParameters>
<taskParameter>
<name>ActionType</name>
<dataType>S</dataType>
<value>EXTRACT</value>
</taskParameter>
<taskParameter>
<name>StreamName</name>
<dataType>S</dataType>
<value>eagle_ml-2-0_default_out_q</value>
</taskParameter>
<taskParameter>
<name>FeedType</name>
<dataType>S</dataType>
<value>COMPLIANCE2A7PRICINGEXTRACT</value>
</taskParameter>
<taskParameter>
<name>entityselectiontype</name>
<dataType>S</dataType>
<value>EntityID</value>
</taskParameter>
<taskParameter>
<name>entityselectionvalue</name>
<dataType>S</dataType>
<value>AMERICA1,AMERICA2,AMERICA3,AMERICA4,AMERICA5,AMERICA6</value>
</taskParameter>
<taskParameter>
<name>SelectView</name>
<dataType>S</dataType>
<value>TotalFund</value>
</taskParameter>
<taskParameter>
<name>reportdate</name>
<dataType>S</dataType>
<value>2016-02-01</value>
</taskParameter>
<taskParameter>
<name>reportFilters</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter>
<taskParameter>
<name>filtersecurityby</name>
<dataType>S</dataType>
<value>XREF</value>
</taskParameter>
<taskParameter>
<name>primaryassetid</name>
<dataType>S</dataType>
<value>D1AVENDD2</value>
</taskParameter>
<taskParameter>
<name>advancedReportOptions</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter>
</taskParameters>
</EagleML>

Example of extract record:
<EagleML
eaglemlVersion="2-0"
eaglemlType="AccountingTransactionMessage"
eaglemlRevision="312"
xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd"
xsi:type="AccountingTransactionMessage"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0">
<header>
<messageId>B80IGH53DIBITMFC</messageId>
<sentBy>http://www.eagleinvsys.com/</sentBy>
<creationTimestamp>2018-08-16T16:35:33-04:00</creationTimestamp>
</header>
<taskIdentifier>
<correlationId>asCOMPL2A7PRICING_160818_08</correlationId>
<businessTaskId>COMPLIANCE2A7PRICINGEXTRACT</businessTaskId>
<sequenceNumber>1</sequenceNumber>
</taskIdentifier>
<accountingTransaction>
<header>
<objectType>Compliance2A7PricingReport</objectType>
</header>
<compliance2A7PricingReport>
<objectType>Compliance2A7PricingReport</objectType>
<objectId>Compliance2A7PricingReport</objectId>
<objectDescription>ACCOUNTING</objectDescription>
<entityId>AMERICA1</entityId>
<entityName>AMERICA1</entityName>
<entityType>PORT</entityType>
<accountingBasis>USTAX</accountingBasis>
<baseCurrency>USD</baseCurrency>
<costMethod>I</costMethod>
<primaryAssetId>D1AVENDD2</primaryAssetId>
<primaryAssetType>INTERNAL</primaryAssetType>
<issueName>d1a ven d2</issueName>
<xrefIdentifiers>
<xId>
<xId>D1AVENDD2</xId>
<xIdType>INTERNAL</xIdType>
</xId>
</xrefIdentifiers>
<securityAlias>680832843</securityAlias>
<assetCurrency>USD</assetCurrency>
<investmentType>FI</investmentType>
<processingSecurityType>DBIBFD</processingSecurityType>
<issueCountryCode>US</issueCountryCode>
<priceMultiplier>0.0100</priceMultiplier>
<quantityScale>1.000000000000</quantityScale>
<coupon>2.000000</coupon>
<maturityDate>2026-12-31</maturityDate>
<investmentTypeDescription>Fixed Income</investmentTypeDescription>
<processingSecurityTypeDescription>Interest Bearing Debt Instrument</processingSecurityTypeDescription>
<currencyDescription>US Dollar</currencyDescription>
<countryDescription>United States</countryDescription>
<actualMarketValue>5371600.00000000</actualMarketValue>
<actualValuationPrice>103.30000000</actualValuationPrice>
<amortizedCostBase>5148000.00</amortizedCostBase>
<localPrice>103.300000000000</localPrice>
<longShortIndicator>L</longShortIndicator>
<navAmount>13245850.000000</navAmount>
<navAmountPerShare>1.017346</navAmountPerShare>
<navCurrentShares>13020000.000000</navCurrentShares>
<originalPriceSource>4(1438)</originalPriceSource>
<persentRate>0.774368231047</persentRate>
<quantity>5200000.000000</quantity>
<reportDate>2016-02-01</reportDate>
<tier>2</tier>
<totalLocalMarketValue>5371600.00</totalLocalMarketValue>
<totalUrglBase>223600.00</totalUrglBase>
</compliance2A7PricingReport>
</accountingTransaction>
</EagleML>

Added files:
\dynamic\msgcenter\eagle_ml-2-0_cm\out\tagvalue\extract_acct_compilance_2a7_pricing_report.xml
\dynamic\msgcenter\eagle_ml-2-0_cm\out\tagvalue\extract_acct_compilance_2a7_pricing_report.inc
\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\t_acct_compilance_2a7_pricing_report_streaming.xml
\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\t_acct_compilance_2a7_pricing_report_streaming.inc
Changed files:
\dynamic\msgcenter\eagle_ml-2-0_cm\out\tagvalue\extracts.rsf
\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\t_eagleml-2-0_streaming.rsf
\dynamic\msgcenter\eagle_ml-2-0_cm\w_config.inc


ESP-434 ESP-2058: EagleML - ADD/Change Sector Setup/Change with Accounting Validation Flag = Y

Support for loading MASTER/SECTOR entities was added. The mutualEntityType field now supports both the MASTER and SECTOR values.

Examples of values in the inbound file:

<mutualEntityType>SECTOR</mutualEntityType>

<mutualEntityType>MASTER</mutualEntityType>

Files changed:

csv-entity_columns.inc

entity_aliases.inc

entity_panels.inc

extract_entity.inc

t_entity_streaming.inc

t_entity_streaming_eml.inc


ESP-986: New rowcount, transactioncount and objectcount require additional modifications to display the accurate information

...

Files changed: 
- extract_xref.inc
- t_xref.xml
- t_xref_streaming.inc


ESP1172: EagleML - Enhance the entity process to support tag 989 for PDC

Support was added for loading entities in PDC in history switch mode. This now allows loading new entities to both the history and master tables.

This functionality is only available on environments running Eagle version 17.2 or higher. The older versions will always load the entities in history only mode.

Files changed: 
- xml-ent_entitygeneric.xml


ESP-1576: Provide additional filters for the GENCORPACTIONSEXTRACT

...

The XPath Values for the WRHSPOSITIONEXTRACT:
EagleML/WarehouseTransaction/warehousePosition/extendedPortValuationModel/urglSecurityLocal
EagleML/WarehouseTransaction/warehousePosition/extendedPortValuationModel/priceRuleActivePrice
EagleML/WarehouseTransaction/warehousePosition/extendedPortValuationModel/activePriceSource
EagleML/WarehouseTransaction/warehousePosition/extendedPortValuationModel/portValuationUpdateTimeStamp
EagleML/WarehouseTransaction/warehousePosition/extendedPortValuationModel/priceRuleUpdateTimeStamp

The XPath Values for the WRHSOPENLOTEXTRACT: 
EagleML/WarehouseTransaction/warehouseOpenLot/extendedPortValuationModel/urglSecurityBase
EagleML/WarehouseTransaction/warehouseOpenLot/extendedPortValuationModel/urglSecurityLocal
EagleML/WarehouseTransaction/warehouseOpenLot/extendedPortValuationModel/priceRuleActivePrice
EagleML/WarehouseTransaction/warehouseOpenLot/extendedPortValuationModel/activePriceSource
EagleML/WarehouseTransaction/warehouseOpenLot/extendedPortValuationModel/portValuationUpdateTimeStamp
EagleML/WarehouseTransaction/warehouseOpenLot/extendedPortValuationModel/priceRuleUpdateTimeStamp

...

This is a new enhancement that leverages MetaData Center and enables the extract of configurations.  
Enables the use of MDC to extract configurations within the system.

...

The following MDC types are supported:
Automation Center Schedule - automationCenterSchedule
Accounting Events Manager Event - accountingEventsManagerEvent
Advanced Reporting Engine Event - advancedReportingEngineEvent
Entity Build Event - entityBuildEvent 
Message Center Process - messageCenterProcess  
Msgcenter Include - msgcenterInclude  
Msgcenter Matching Rule - msgcenterMatchingRule
Msgcenter Preprocessing Rule - msgcenterPreprocessingRule
Msgcenter Rule - msgcenterRule
Msgcenter Ruleset - msgcenterRuleset  
Msgcenter Schedule Rule - msgcenterScheduleRule
Msgcenter Split Rule - msgcenterSplitRule
Msgcenter Stream - msgcenterStream
Msgcenter Validation Rule - msgcenterValidationRule  
OLAP Reports Event - oLAPReportsEvent
Performance Analysis Event - performanceAnalysisEvent 
Performance Calculation Event - performanceCalculationEvent
Website Overlay - websiteOverlay

...

<EagleML xsi:SchemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd" eaglemlVersion="2-0" eaglemlType="RunTaskRequest" xsi:type="RunTaskRequest" xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<header>
<messageId>YPGLN4ORDT3H1O8JF</messageId>
<sentBy>user</sentBy>
<sendTo>http://www.eagleinvsys.com/eagle_ml-2-0_default_cm_control_message</sendTo>
<replyTo>http://www.client.com/Eagle Control Messages</replyTo>
</header>
<taskIdentifier>
<correlationId>METADATA_1732_STEP_2_V_001</correlationId>
<businessTaskId>WH_META_1732_STEP_2</businessTaskId>
</taskIdentifier>
<taskTypeEnum>NEW</taskTypeEnum>
<taskParameters>
<taskParameter>
<name>StreamName</name>
<dataType>S</dataType>
<value>eagle_ml-2-0_default_cm_execwkfl</value>
</taskParameter>
<taskParameter>
<name>ActionType</name>
<dataType>S</dataType>
<value>EXECUTE</value>
</taskParameter>
<taskParameter>
<name>WorkflowName</name>
<dataType>S</dataType>
<value>eagle_wrf_generic_extract</value>
</taskParameter>
<taskParameter>
<name>ExtractSendNotification</name>
<dataType>S</dataType>
<value>ONFAILURE</value>
</taskParameter>
<taskParameter>
<name>maxrows</name>
<dataType>S</dataType>
<value>100</value>
</taskParameter>
<taskParameter>
<name>Compress</name>
<dataType>S</dataType>
<value>N</value>
</taskParameter>
<taskParameter> 
<name>FeedType</name>
<dataType>S</dataType>
<value>METADATAEXTRACT</value>
</taskParameter>
<!-- <taskParameter>
<name>ItemType</name>
<dataType>S</dataType>
<value>Msgcenter Rule,Msgcenter Stream,Msgcenter Ruleset,Msgcenter Schedule Rule,Msgcenter Preprocessing Rule</value>
</taskParameter>
<taskParameter>
<name>ItemId</name>
<dataType>S</dataType>
<value>eagle_ml-2-0_cm/ndfa/ndfa_exec.xml,eagle_ml-2-0_default_cm_execwkfl,eagle_ml-2-0_cm/out/xml/t_eagleml-2-0.rsf,eagle_ml-2-0_cm/installer/mc_import_stream.prf,eagle_ml-2-0_cm/installer/schedule/mc_server_support_jms.sch</value>
-->
</taskParameters>
</EagleML>

...

Changed files:
t_eagleml-2-0_streaming.rsf
extracts.rsf
w_config.inc
eagle_wrf_generic_extract workflow


ESP-1755: Issue with ALLEXTRACTS_ExtractNamePattern

When running extract with “ALLEXTRACTS_” as a value for the EtractNamePattern RTR parameter the output files would not have the “ALLEXTACTS_” string as part of their names.

The get_w_custom_params.inc file was changed to fix this issue.

Files changed:
get_w_custom_params.inc 


ESP-1765: Update logic for tag7250 in GenericSmf to pass only for Main Security Resolution

...

Case 1: Main Security Resolution logic will be skipped, Underlying Security Resolution logic applied 
genericSMF/assetResolutionOption = 'SKIP':
<assetResolutionOption>SKIP</assetResolutionOption>

Case 2: Underlying Security Resolution logic will be skipped, Main Security Resolution logic applied. 
genericSMF/UnderlyingModel/assetResolutionOption = 'SKIP':
<UnderlyingModel>
<assetResolutionOption>SKIP</assetResolutionOption>
</UnderlyingModel>

...

<EagleML
eaglemlVersion="2-0"
eaglemlType="ReferenceTransactionMessage"
eaglemlRevision="311"
xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd"
xsi:type="ReferenceTransactionMessage"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0">
<header>
<messageId>B80I1D704ELCVLBW</messageId>
<sentBy>http://www.eagleinvsys.com/</sentBy>
<creationTimestamp>2018-08-20T12:57:00-04:00</creationTimestamp>
</header>
<taskIdentifier>
<correlationId>I1D65NSZJEHSW009</correlationId>
<businessTaskId>EXTR162199000#extract_issuer_analytic</businessTaskId>
<sequenceNumber>1</sequenceNumber>
</taskIdentifier>
<referenceTransaction>
<header>
<objectType>IssuerAnalytic</objectType>
</header>
<issuerAnalytic>
<objectType>IssuerAnalytic</objectType>
<objectId>IssuerAnalytic</objectId>
<objectDescription>REFERENCE</objectDescription>
<updateTimestamp>2018-08-20T12:56:03-04:00</updateTimestamp>
<sourceName>TEST</sourceName>
<updateSource>TEST</updateSource>
<issuerId>10376</issuerId>
<issuerAlias>2501858</issuerAlias>
<issuerXrefIdentifiers>
<xId>
<xId>10176</xId>
<xIdType>IDBB</xIdType>
</xId>
</issuerXrefIdentifiers>
<commonShares>140861</commonShares>
<cashFlowFromOper>39151</cashFlowFromOper>
<sharesOutstanding>6139.425</sharesOutstanding>
<corpMeetingLastDate>2018-04-27</corpMeetingLastDate>
<corpMeetingNextDate>2019-06-01</corpMeetingNextDate>
<pretaxIncome>1539</pretaxIncome>
<salesRevTurn>16546</salesRevTurn>
<bsNumberOfTsySh>35.81</bsNumberOfTsySh>
</issuerAnalytic>
</referenceTransaction>
</EagleML>

...

gainLossCurrency988
washsaleDisallowedReversalLocal
washsaleDisallowedReversalBase
impairmentLtdLocalExt
impairmentLtdBaseExt
impairmentFxLtd

Signage logic is applied when the parameter EnableSignageLogic is set to Y. If the value is N or null, the numeric fields are presented as stored in the database. If the value is Y, some numeric fields have their own algorithm for signing the values.

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

...

extract_wrhs_trade_signage_logic.inc


ESP-1854: EagleML - Outbound Nuggetizer should allow splitting data on logical lines

Splitting logic has been reviewed and new parameters have been introduced:
MicroBatchKeyRecordCount instead of RecordCountPerNugget.
RecordCountPerNugget is still supported for compatibility, but MicroBatchKeyRecordCount has a higher priority than the old parameter.

W_MICRO_BATCH_KEY_RECORD_COUNT instead of W_RECORD_COUNT_PER_NUGGET. 
W_RECORD_COUNT_PER_NUGGET is still supported for compatibility, but W_MICRO_BATCH_KEY_RECORD_COUNT has higher priority than old parameter.

The MicroBatchKeyRecordCount parameter is now used to specify the maximum number of records in each new split file.

Additionally the new MicroBatchSplitKey parameter was also added to allow a user to provide a split key. The key can be complex and include multiple values separated by commas, where each value represents a database column. As a result the user needs to know the exact names of the database columns. If the names are incorrectly provided there will be an error in the eagle_ml-2-0_default_out_q stream.

Changed files:
t_extract_data_splitter_begin.inc
t_extract_data_splitter_end.inc
t_extract_data_splitter.inc


ESP-1958: GenericEntity - cannot update Entity Xrefs. Need logic to update Xref

...

Changed files:
entity_xref_ins_upd.inc


ESP-1964: EagleML - NLIQUID

The XSD for the Warehouse Position and Warehouse Performance objects was updated to include the POSITION_DETAIL_LIQUIDITY and PSR_LIQUDITY fields.


ESP-1965: Added filters to CASHPROJECTIONSEXTRACT

...

Sample RTR:

<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>CASHPROJECTIONSEXTRACT</messageId>
<sentBy>http://www.client.com</sentBy>
<sendTo>http://www.eagleinvsys.com/eagle_ml-2-0_default_cm_control_message</sendTo>
<replyTo>http://www.client.com/Eagle Control Messages</replyTo>
<creationTimestamp>2012-08-02T22:13:32.272-05:00</creationTimestamp>
</header>
<taskIdentifier>
<correlationId>ESP-1965-startDate_endDate_T13_v001</correlationId>
<businessTaskId>CASHPROJECTIONSEXTRACT</businessTaskId>
</taskIdentifier>
<taskTypeEnum>NEW</taskTypeEnum>
<synchronousExecution>no</synchronousExecution>
<taskParameters>
<taskParameter>
<name>ActionType</name>
<dataType>S</dataType>
<value>EXTRACT</value>
</taskParameter>
<taskParameter>
<name>StreamName</name>
<dataType>S</dataType>
<value>eagle_ml-2-0_default_out_q</value>
</taskParameter>
<taskParameter>
<name>FeedType</name>
<dataType>S</dataType>
<value>CASHPROJECTIONSEXTRACT</value>
</taskParameter>
<taskParameter>
<name>startdate</name>
<dataType>S</dataType>
<value>2018-08-09</value>
</taskParameter>
<taskParameter>
<name>enddate</name>
<dataType>S</dataType>
<value>2018-12-31</value>
</taskParameter> 
<taskParameter>
<name>IncludeEntityInfo</name>
<dataType>S</dataType>
<value>ALL</value>
</taskParameter>
<taskParameter>
<name>IncludeAllEntXref</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter> 
<taskParameter>
<name>IncludeExtendedDetails</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter> 
<taskParameter>
<name>CashProjectionInstanceType</name>
<dataType>S</dataType>
<value>Max</value>
</taskParameter>
<taskParameter>
<name>CashProjectionReportType</name>
<dataType>S</dataType>
<value>FI|DIV</value>
</taskParameter>
<taskParameter>
<name>TraverseHierarchy</name>
<dataType>S</dataType>
<value>N</value>
</taskParameter>
<taskParameter>
<name>entityselectiontype</name>
<dataType>S</dataType>
<value>EntityID</value>
</taskParameter>
<taskParameter>
<name>entityselectionvalue</name>
<dataType>S</dataType>
<value>SMPLENT1</value>
</taskParameter>
</taskParameters>
</EagleML>

...

To delete activities send a GenericEntity file in eagle_ml-2-0_default_in_xml_entity stream with <action>DELETEACTIVITY</action>.

Example:
<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" eaglemlVersion="2-0" eaglemlType="EntityTransactionMessage" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd" xsi:type="EntityTransactionMessage">
<header>
<messageId messageIdScheme="http://www.eagleinvsys.com/coding-scheme/message-id-2-0">TEST</messageId>
</header>
<entityTransaction>
<header>
<objectType>GenericEntity</objectType>
<action>DELETEACTIVITY</action>
</header>
<genericEntity>
<objectType>GenericEntity</objectType>
<objectId>GenericEntity</objectId>
<objectDescription>ENTITY</objectDescription>
<updateSource>MCADMIN</updateSource>
<accountingValidationFlag>Y</accountingValidationFlag>
<entityId>ES1987E1</entityId>
<entityName>ES1987E1</entityName>
<entityXrefs>
<entityXref>
<xrefAccountId>ES1987E1_XREF01</xrefAccountId>
<xrefAccountIdType>XREF1</xrefAccountIdType>
<xrefClassCode>TF1</xrefClassCode>
</entityXref>
</entityXrefs>
<entityType>PORT</entityType>
</genericEntity>
</entityTransaction>
</EagleML>

...

Example of incoming file:
<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" eaglemlVersion="2-0" eaglemlType="EntityTransactionMessage" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd" xsi:type="EntityTransactionMessage">
<header>
<messageId messageIdScheme="http://www.eagleinvsys.com/coding-scheme/message-id-2-0">TEST</messageId>
</header>
<entityTransaction>
<header>
<objectType>GenericEntity</objectType>
<action>DELETE</action>
<checkActivity>Y</checkActivity>
</header>
<genericEntity>
<objectType>GenericEntity</objectType>
<objectId>GenericEntity</objectId>
<objectDescription>ENTITY</objectDescription>
<entityId>ESP19881</entityId>
<entityName>ESP19881_NAME</entityName>
</genericEntity>
</entityTransaction>
</EagleML>

...

Files changed:
eagle/estar/EAGLE_EXTRACTSERVICE.pkg
eagle/estar/EAGLE_ML_2_0.pkg
eagle/estar/eagle_ml-2-0_default_out_extract_service.pkg
eagle/estar/eagle_ml-2-0_default_out_q.pkg
eagle/estar/eagle_ml-2-0_default_out_streaming_t.pkg
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/extract_start.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/out/tagvalue/extract_acct_settled_cash_activity.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/out/tagvalue/extract_acct_traded_cash_activity.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/out/tagvalue/extract_ca_properties_fields.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/out/tagvalue/extract_warehouse_trade.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/out/xml/t_acct_settled_cash_activity_streaming.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/out/xml/t_acct_traded_cash_activity_streaming.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/out/xml/t_ca_properties_fields_streaming.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/out/xml/t_warehouse_trade_streaming.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_cm/out/xml/t_warehouse_trade_streaming_eml.inc


ESP-2107: Adjust eagle_generic_load_smf_objects to have additional generic_smf before load_generic_smf task

Support for loading files with the _UNDERLYINGENERICSMF_ through the eagle_ml-2-0_deafult_in_xml_smf_generic stream was added.

This enhancement allows for loading underlying SMF records via the eagle_wrf_generic_load workflow. The underlying records will always be loaded before the generic SMF records.

Files changed: 
- eagle_wrf_generic_load.wrf
- eagle_wrf_generic_load_smf_objects.wrf


ESP-2324: EntityAccountingPeriod insert/update issue on 2017R2(ORA)

...

This parameter’s value is ultimately stored in the w_config_version.inc file.

Files created: 
get_version.inc

Changed files:
eagle_mc_server_support_get_version.xml
w_setup_eagle_version.xml


2484 Factor revisions (ACORPACTION_REBOOK) are not processing successfully where data files are passed through EagleML stream, with a Correlation ID

Data was not being loaded correctly during the GenericCA update through real time processing.

The issue was tied to an incorrect instance of the GenericCA files being sent to the panel.

The logic for determining which instance to send was edited to correct this problem.

Files changed:
xml-ref_ca.xml


ESP-2497: Add handling for key files of xmldbapi objects in eagle_wrf_generic_load 

...