Enhancements

SDP-67177 GenericSMF resolution logic was enhanced to enable Primary Asset resolution by Security Alias

Primary Asset Id is required field for GenericSMF load. The client may not have a Primary Asset Id and Type but may have an Security Alias in incoming file.
The new asset resolution option RESOLVE_PRIMARY was introduced to enable Primary Asset Id and Type resolution by provided Security Alias.
It is supported for Regular, Forward and Swap securities.

Example of usage:
<assetResolutionOption>SKIP,RESOLVE_PRIMARY</assetResolutionOption>

Files changed:
eagle_default/in/xml/include/security_resolution_generic.inc
eagle_default/in/xml/include/smf_detail.inc

SDP-61939 The Cost Basis Adjustment inbound interface was expanded with new panel support

The new eagle/star/account/pan-insertadjcostbasis.htm panel support was added to the Cost Basis Adjustment interface to process Tax Lot Service Cost Basis Adjustment.
The new rule is triggered by the costAdjustmentType element with a value of 'UPDATE_TAXSERVICE_LOT'.
Example of usage:

Data Base fields and Xpath:
ESTAR.ESTAR_TAXSVC_ADJ_LOT_DETAIL.OPEN_EVENT_ID - Tag 151 - EagleML/accountingTransaction/costBasisAdjustment/openEventId
ESTAR.ESTAR_TAXSVC_ADJ_LOT_DETAIL.QUANTITY_WASHSALE_ELIGIBLE - Tag 405 - EagleML/accountingTransaction/costBasisAdjustment/qtyWashSaleEligible
ESTAR.ESTAR_TAXSVC_ADJ_LOT_DETAIL.TAX_UNIT_COST_B - Tag 163 - EagleML/accountingTransaction/costBasisAdjustment/unitCostBase
ESTAR.ESTAR_TAXSVC_ADJ_LOT_DETAIL.TAX_UNIT_COST_L - Tag 4643 - EagleML/accountingTransaction/costBasisAdjustment/unitCostLocal
ESTAR.ESTAR_TAXSVC_ADJ_LOT_DETAIL.QUANTITY - Tag 4642 - EagleML/accountingTransaction/costBasisAdjustment/quantity
ESTAR.ESTAR_TAXSVC_ADJ_LOT_DETAIL.AMORTIZED_COST_B - Tag 2690 - EagleML/accountingTransaction/costBasisAdjustment/amortizedCostBase
ESTAR.ESTAR_TAXSVC_ADJ_LOT_DETAIL.AMORTIZED_COST_L - Tag 2689 - EagleML/accountingTransaction/costBasisAdjustment/amortizedCostLocal
ESTAR.ESTAR_TAXSVC_ADJ_LOT_DETAIL.WASH_SALE_DEFERRAL_B - Tag 402 - EagleML/accountingTransaction/costBasisAdjustment/lossDeferralBase
ESTAR.ESTAR_TAXSVC_ADJ_LOT_DETAIL.WASH_SALE_DEFERRAL_L - Tag 403 - EagleML/accountingTransaction/costBasisAdjustment/lossDeferralLocal

File added:
eagle_default/in/xml/xml-costbasisinsertadj.xml

File changed:
eagle_default/in/xml/xml-costbasisadj.rsf

SDP-67272 Enable Cloud Workflow to execute with all generic extract parameters

The Cloud workflow can be executed with any parameters supported by the generic extract. SQL queries and extracted data is similar both in the generic extract and the Cloud extract. All filters supported by the generic extract can be passed in the Cloud workflow and work the same way.

Files changed:
eagle_ml-2-0_cm/create_cm.inc
eagle/estar/tpe/dynamic/msgcenter/eagle_ml-2-0_workflows/eagle_wrf_cloud_extract.wrf
eagle/estar/tpe/dynamic/msgcenter/eis/ejmwf/eagle_wrf_cloud_extract.ejmwf

SDP-66795 Issue Price and Issue PC Price inbound interfaces were enhanced to support price conversion process for Bond Forwards

The routing for the Price Conversion panels was updated to support a new Price Type Code - Tag 1843 value of 6.
Example of usage:

A new element was introduced to capture the Pricing Entity Id:
SECURITYDBO.PRICE.ENTITY_ID - Tag 7107 - EagleML/referenceTransaction/issuePrice/pricingEntityId
SECURITYDBO.PRICE_EXCHANGE.ENTITY_ID - Tag 7107 - EagleML/referenceTransaction/issuePcPrice/pricingEntityId

Files changed:
eagle_default/in/xml/xml-ref_issuepcprice.xml
eagle_default/in/xml/xml-ref_issueprice.xml

SDP-66389 Corrected the mapping for the gainSecurityLocal, lossSecurityLocal. Added gainSecurityBase and lossSecurityBase,

Mappings for the gainSecurityLocal and lossSecurityLocal were changed to TOTAL_GAIN_LOCAL and TOTAL_LOSS_LOCAL. New tags gainSecurityBase and lossSecurityBase were added and mapped to the SECURITY_GAIN and SECURITY_LOSS. Changes were applied both for the extract and the load.

Files changed:
eagle_ml-2-0_cm/out/xml/t_warehouse_trade_streaming.inc
eagle_ml-2-0_cm/out/xml/t_warehouse_trade.xml
eagle_default/in/xml/xslt/wrh_egl_gen_interface3.xsl

SDP-65723 Process Centers Partitions Resolution Logic For RTR Processing

New logic has been introduced for RTR processing in the eagle_ml-2-0_default_cm_control_message stream. It is activated by two task parameters: ResolveProcessCtrPartitions and 4896.
4896 is a tag that represents Process Center. The ResolveProcessCtrPartitions flag defaults to N, but can be set to Y or B.

The new logic resolves partitions associated with entities related to Process Center at Tag 4896. If ResolveProcessCtrPartitions is Y and the number of partitions is greater than 1, an error will be produced and the RTR process will fail. If ResolveProcessCtrPartitions is B and the number of partitions is greater than 1, a warning will be indicated and the RTR process will pass. If the flag is N, or null, no EML logic is applied. If the number of partitions is 1, then the resolved partition Id will be sent to Tag 95 to the following processes and RTR process will continue.

The example of task parameters in RTR:

The logic works for every RTR with these task parameters. It does not depend on what will be executed by this RTR. If these parameters are not presented in the RTR, then the logic will not be triggered.

SDP-65382 LedgerPostingDualEntry enhancement - USE_PRIOR_FX_RATE option to use prior FX Rate

The LedgerPostingDualEntry EagleML load interface has been enhanced to support the new processing option "USE_PRIOR_FX_RATE.". This indicates to use the prior FX Rate before the accounting date (accountingDate). The message will retrieve the most recent FX Rate and use the returned value in the posting.

Use <processingOptions>USE_PRIOR_FX_RATE</processingOptions> in <header> of LedgerPostingDualEntry message.

Example:

Files changed:
eagle_default/in/xml/xml-acct_ledgerposting.xml

SDP-65297 Changed Forward ContraSecAlias Resolution To Select The Opposing Leg

Changed the Forward security resolution to use the opposing leg instead of its own security alias. The resolution will trigger when both legs are loaded and the ContraSecAlias is 0 or is not provided.

Files changed:
eagle_default/in/xml/include/msgxchg_sec_core.inc
eagle_default/in/xml/include/security_resolution_generic.inc

SDP-61599 EDS WarehouseTrade resource was updated

The EDS WarehouseTrade resource was updated. The mapping was adjusted and additional elements were added to the Canonical model
between the element unrealizedUndistributedInvestmentIncomeLocal and warehousetrade:TradeChargesModel

monthlyAccountingDate
targetOriginalEventId
commitmentBase
fundedCapitalBase
fundedCapitalLocal
nextDayIndicator
nextDayIndicatorMargin
performanceEffectiveDate
recallableCapitalBase
recallableCapitalLocal
settleAmountBase
gainLossSecurityIdBase
gainLossSecurityIdLocal
lpExpenseBase
lpExpenseLocal
lpIncomeBase
lpIncomeLocal
acementNum

Also the mapping was added between database elements and new and existing canonical elements:

TRADE.CONSOLIDATED_FLAG -> consolidatedIndicator
TRADE.FROM_REGULATORY_CATEGORY -> fromRegulatoryCategory
TRADE.MONTHLY_ACCOUNTING_DATE -> monthlyAccountingDate
TRADE.TARGET_ORIG_EVENT_ID -> targetOriginalEventId
TRADE.TO_REGULATORY_CATEGORY -> toRegulatoryCategory
TRADE_DETAIL.CANCEL_POST_DATE -> cancelPostDate
TRADE_DETAIL.CANCEL_REASON_FLAG -> cancelReasonIndicator
TRADE_DETAIL.COMMITMENT -> commitmentAmount
TRADE_DETAIL.COMMITMENT_B -> commitmentBase
TRADE_DETAIL.DIST_INV_INC_B -> distributedInvestmentIncomeBase
TRADE_DETAIL.DIST_INV_INC_L -> distributedInvestmentIncomeLocal
TRADE_DETAIL.ECL_BASE -> expectedCreditLossAmountBase
TRADE_DETAIL.ECL_DELTA_BASE -> expectedCreditLossDeltaAmountBase
TRADE_DETAIL.ECL_DELTA_LOCAL -> expectedCreditLossDeltaAmountLocal
TRADE_DETAIL.ECL_LOCAL -> expectedCreditLossAmountLocal
TRADE_DETAIL.ECL_PREV_BASE -> expectedCreditLossPreviousAmountBase
TRADE_DETAIL.ECL_PREV_LOCAL -> expectedCreditLossPreviousAmountLocal
TRADE_DETAIL.ECL_PREV_STAGE -> expectedCreditLossPreviousStageAmount
TRADE_DETAIL.ECL_STAGE -> expectedCreditLossStageAmount
TRADE_DETAIL.EMA_COST_FLAG -> equityMethodAcctCostIndicator
TRADE_DETAIL.EMA_TREATMENT -> equityMethodAcctTreatmentMethod
TRADE_DETAIL.FUNDED_CAPITAL_B -> fundedCapitalBase
TRADE_DETAIL.FUNDED_CAPITAL_L -> fundedCapitalLocal
TRADE_DETAIL.FX_IMPAIRMENT -> fxImpairmentRate
TRADE_DETAIL.GAIN_CRCCT_EMA_B -> equityMethodAcctCRCCTGainBase
TRADE_DETAIL.GAIN_CRRCY_CURR_PRE -> currentPeriodCurrencyGain
TRADE_DETAIL.GAIN_CRRCY_INCOME -> currencyIncomeGain
TRADE_DETAIL.GAIN_LOSS_TERM -> termGainLoss
TRADE_DETAIL.GAIN_SEC_CURR_B_PRE -> currentPeriodSecurityGainBase
TRADE_DETAIL.GAIN_SEC_CURR_L_PRE -> currentPeriodSecurityGainLocal
TRADE_DETAIL.GAIN_SEC_EMA_B -> equityMethodAcctSecurityGainBase
TRADE_DETAIL.GAIN_SEC_EMA_L -> equityMethodAcctSecurityGainLocal
TRADE_DETAIL.LOSS_CRCCY_EMA_B -> equityMethodAcctCurrencyLossBase
TRADE_DETAIL.LOSS_CRRCY_CURR_PRE -> currentPeriodCurrencyLoss
TRADE_DETAIL.LOSS_CRRCY_INCOME -> currencyIncomeLoss
TRADE_DETAIL.LOSS_SEC_CURR_B_PRE -> currentPeriodSecurityLossBase
TRADE_DETAIL.LOSS_SEC_CURR_L_PRE -> currentPeriodSecurityLossLocal
TRADE_DETAIL.LOSS_SEC_EMA_B -> equityMethodAcctSecurityLossBase
TRADE_DETAIL.LOSS_SEC_EMA_L -> equityMethodAcctSecurityLossLocal
TRADE_DETAIL.MKT_VAL_EMA_B -> equityMethodAcctMarketValueBase
TRADE_DETAIL.MKT_VAL_EMA_L -> equityMethodAcctMarketValueLocal
TRADE_DETAIL.NEXT_DAY_INDICATOR -> nextDayIndicator
TRADE_DETAIL.NEXT_DAY_INDICATOR_MARGIN -> nextDayIndicatorMargin
TRADE_DETAIL.NOTIONAL_OR_UNITS_FLAG -> notionalOrUnitsIndicator
TRADE_DETAIL.OWNERSHIP_PERCENTAGE -> ownershipPercentage
TRADE_DETAIL.PERFORMANCE_EFF_DATE -> performanceEffectiveDate
TRADE_DETAIL.PRE_MKT_VAL_EMA_B -> equityMethodAcctPeriodMarketValueBase
TRADE_DETAIL.PRE_MKT_VAL_EMA_L -> equityMethodAcctPeriodMarketValueLocal
TRADE_DETAIL.PRORATA_CNC_LOSS_FLAG -> prorataCreditNonCreditLossFlag
TRADE_DETAIL.PURCHASED_IMPAIRED -> purchasedImpairedIndicator
TRADE_DETAIL.RECALLABLE_CAPITAL_B -> recallableCapitalBase
TRADE_DETAIL.RECALLABLE_CAPITAL_L -> recallableCapitalLocal
TRADE_DETAIL.RESEARCH_FEES_BASE -> researchFeeBase
TRADE_DETAIL.RESEARCH_FEES_LOCAL -> researchFeeLocal
TRADE_DETAIL.SETTLE_AMOUNT_BASE -> settleAmountBase
TRADE_DETAIL.SLEEVE_ID -> sleeveId
TRADE_DETAIL.SRC_SYS_C -> srcSysC
TRADE_DETAIL.STAR_SRC_LVL -> starSourceLevel
TRADE_DETAIL.TECHSH_SRC -> technicalShortLevel
TRADE_DETAIL.UNDIST_INV_INC_B -> undistributedInvestmentIncomeBase
TRADE_DETAIL.UNDIST_INV_INC_L -> undistributedInvestmentIncomeLocal
TRADE_DETAIL.UNREAL_UNDIST_INV_INC_B -> unrealizedUndistributedInvestmentIncomeBase
TRADE_DETAIL.UNREAL_UNDIST_INV_INC_L -> unrealizedUndistributedInvestmentIncomeLocal
TRADE_DETAIL_EXT.ACEMENT_NUM -> acementNum
TRADE_DETAIL_EXT.DEAL_SOURCE -> dealSource
TRADE_DETAIL_EXT.MIFID_ORDERTYPE -> mifidOrderType
TRADE_DETAIL_EXT.MIFID_TRADETIME -> mifidTradeTime
TRADE_DETAIL_EXT.MIFID_TRADINGVENUE -> mifidTradingVenue
TRADE_DETAIL_EXT.NEW_ISSUE -> newIssueIndicator
TRADE_EXT.GAIN_LOSS_SEC_ID_B -> gainLossSecurityIdBase
TRADE_EXT.GAIN_LOSS_SEC_ID_L -> gainLossSecurityIdLocal
TRADE_EXT.LP_EXPENSE_BASE -> lpExpenseBase
TRADE_EXT.LP_EXPENSE_LOCAL -> lpExpenseLocal
TRADE_EXT.LP_INCOME_BASE -> lpIncomeBase
TRADE_EXT.LP_INCOME_LOCAL -> lpIncomeLocal

Below elements are not supported for the load:

TRADE_DETAIL.USER_CHAR1
TRADE_DETAIL.USER_CHAR2
TRADE_DETAIL.USER_CHAR3
TRADE_DETAIL.USER_FLOAT1
TRADE_DETAIL.USER_FLOAT2
TRADE_DETAIL.USER_FLOAT3
TRADE_DETAIL_EXT.AL_HEDGE_FLAG
TRADE_DETAIL.PRINCIPAL - The PRINCIPAL value exists in TRADE table and mapped to principal canonical element.

Files changed:
metadata/core/ontology/definition/eagle-vocab-definition-wh-shared.json
metadata/core/ontology/eagle-vocab-wh-shared.json
metadata/core/ontology/warehouse/warehousetrade-models.json

SDP-59616 Conversion Workflow

The main goal of the Conversion Workflow to provide a framework for migrating years of historical Eagle Data from the Oracle database to Snowflake.

The Conversion workflow consists of two logical steps:

1. Analyze the volume of data for each Resource and create RTR’s for the corresponding extract

2. Orchestrate the execution of the generated RTR’s as parallel processes

To run the conversion workflow you need to define the list of resources that will be used to migrate the data and a date range for the historical data.

• ResourceName - Can be a list of resources for conversion, comma-separated values.

• fromeffectivedate - required parameter

• toeffectivedate - will be used as Today() if not specified in the RTR

• DistributionProfileName - parameter, which defines where the results will be uploaded for future processing

• max_batch_size - defines how many records can each RTR extract (500k by default)

• number_of_workers - defines how many workers will execute the extract RTR’s

Pattern for generated RTR’s: '{resource_name}_{#rtr_number}_{correlation_id}_{from_effective_date}_{to_effective_date}.xml'

RTR’s will be saved in the directory:

/apps/eagle/data/msgcenter/cmw_staging_folder/conversion_rtr/{CORR_ID}/*

Extract file name template:

{CORR_ID}_ASISCOPY_CONVERSION_{from_effective_date or "START"}_{to_effective_date or "END"}_@FeedType_@DateStamp.xml

Example RTR to trigger Conversion workflow:

<EagleML xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0%22 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:SchemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd" eaglemlVersion="2-0" eaglemlType="RunTaskRequest" xsi:type="RunTaskRequest">
<taskIdentifier>
<correlationId>{GUID}</correlationId>
<businessTaskId>CONVERSION</businessTaskId>
</taskIdentifier>
<taskTypeEnum>NEW</taskTypeEnum>
<synchronousExecution>no</synchronousExecution>
<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_cloud_conversion</value>
</taskParameter>
<taskParameter>
<name>ResourceName</name>
<value>warehousetrade,warehouseposition</value>
</taskParameter>
<taskParameter>
<name>fromeffectivedate</name>
<value>2010-01-01</value>
</taskParameter>
<taskParameter>
<name>toeffectivedate</name>
<value>2010-01-05</value>
</taskParameter>
</taskParameters>
</EagleML>

Example of an auto-generated RTR to move the historical data:

<EagleML eaglemlVersion="2-0" xmlns="http://www.eagleinvsys.com/2011/EagleML-2-0%22 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.eagleinvsys.com/2011/EagleML-2-0 eagleml-main-2-0.xsd" eaglemlType="RunTaskRequest" xsi:type="RunTaskRequest">
<header>
<messageId>BD2722D638DDC6F7</messageId>
<sentBy><http://www.eagleinvsys.com</sentBy>>
<sendTo><http://www.eagleinvsys.com/eagle_default_ruleservice%3C/sendTo%3E%3E
<creationTimestamp>2022-11-10T03:45:23</creationTimestamp>
</header>
<taskIdentifier>
<correlationId>821B0862BA2A63A5</correlationId>
<businessTaskId>REST</businessTaskId>
</taskIdentifier>
<taskTypeEnum>NEW</taskTypeEnum>
<taskParameters>
<taskParameter><name>servicename</name><value>ebs</value></taskParameter>
<taskParameter><name>servicemethodname</name><value>extract</value></taskParameter>
<taskParameter><name>resourcename</name><value>warehouseposition</value></taskParameter>
<taskParameter><name>fromeffectivedate</name><value>2010-01-01</value></taskParameter>
<taskParameter><name>toeffectivedate</name><value>2010-05-01</value></taskParameter>
<taskParameter><name>outfilepattern</name><value>@CORRID_CONVERSION_20100101_20100501_@FeedType_@DateStamp.xml</value></taskParameter>
<taskParameter><name>extractnamepatternex</name><value>@CORRID_CONVERSION_20100101_20100501_@FeedType_@DateStamp.xml</value></taskParameter>
<taskParameter><name>distributionprofilename</name><value>azure_dev_conversion</value></taskParameter>
</taskParameters>
</EagleML>

SDP-67376 Filename Parser for Conversion upload mode

The Filename parser was implemented to support the Conversion Workflow and historical data load as part of the Eagle-Vault pipeline.
File names with a predefined pattern for load CONVERSION_yyyymmdd_yyyymmdd.*  are generated automatically by the conversion workflow.
It will set conversion upload mode and fromEffective/toEffective date parameters for load.
Parameters will be parsed from the filename and they will override the same incoming parameter if they were passed in the incoming RTR.

If the effectiveDate is part of the resource definition, then the delete and load will be executed for dates defined in the file name. If the effectiveDate is not supported, then a full delete will be performed before load.

Files changed:
eagleinvsys/common_core/core_utils/datetime_utils.py
eagleinvsys/common_core/processing_env/instructions.py

SDP-56039 EDS codetranslation resource

codetransalation resource support has been added to EDS.
Supported table: PACE_MASTERDBO.CODE_TRANSLATION

Currently the codetranslation inflow interface supports only snowflake dbprovider.

codetranslation outflow interface supports oracle and snowflake dbproviders with the filters below:

• fromdate

• todate

• codetranslationid

File added:
metadata/core/ontology/reference/codetranslation_in.json

Files changed:
metadata/core/ontology/reference/codetranslation-models.json
metadata/core/ontology/reference/codetranslation.json
test-files/files/estar/tpe/dynamic/metadata/core/ontology/definition/eagle-vocab-definition-ref.json
test-files/files/estar/tpe/dynamic/metadata/core/ontology/definition/eagle-vocab-definition-shared.json
test-files/files/estar/tpe/dynamic/metadata/core/ontology/eagle-mashups.json
test-files/files/estar/tpe/dynamic/metadata/core/ontology/eagle-vocab-ref.json
test-files/files/estar/tpe/dynamic/metadata/core/ontology/eagle-vocab-shared.json
test-files/files/estar/tpe/dynamic/metadata/core/ontology/eagledb-vocab-common.json
test-files/files/estar/tpe/dynamic/metadata/core/ontology/reference/codecategory.json
test-files/files/estar/tpe/dynamic/metadata/core/ontology/reference/codevalue-models.json
test-files/files/estar/tpe/dynamic/metadata/core/ontology/reference/codevalue.json

Production Bugs

SDP-67873 Default Logic for Warehouse Position and Warehouse Openlot was corrected for Batch load

Regression issues was introduced by the prior change. Default logic was corrected:

• The openLotDeleteSwitch flag set to Y allows to delete data from Warehouse Openlot tables via EDS warehouseposition Resource

Default value was set to Y for load to Oracle and set to N for upload to Snowflake.

• The procedureFlag set to PD allows EDS warehouseopenlot resource to add data to Warehouse Position tables - POSITION_DETAIL or POSITION_COST_DEATIL

Default value was set to PD for load to Oracle db and set to N for upload to Snowflake db.

Files changed:
warehouseposition_in.json
warehouseopenlot_in.json

SDP-66869 Revised logic when skipping the Rating record update to still update the Reason Code of the Rating

The logic for the Issue Rating inserts a new record when both the effective date and the Rating are different than the existing values in the database. This logic is triggered by using the processingOptions SKIP_UNCHANGED_RATING in the incoming file. The logic checks if the latest rating record (highest effective date) for the same key (Security + Issue Name + Source) has a different alpha rating or the same rating. If the new record matches the existing alpha rating, the record is skipped, otherwise a new record is created.

When using the SKIP_UNCHANGED_RATING, there is still a need to update the REASON field when it has a different value then the existing record.

Usage:

<referenceTransaction>
    <header>
<objectType>Rating</objectType>
<processingOptions>SKIP_UNCHANGED_RATING</processingOptions>
    </header>
</referenceTransaction>

Modified the SKIP_UNCHANGED_RATING logic to consider Reason tag change adding Reason - Tag 1674 as a variable for evaluation.

Files changed:
eagle_default/in/xml/xml-ref_issuerating_all.xml

SDP-66032 EDS issuerrating Resource was updated

The metadata for issuerrating was updated to add support for the following fields: SOURCE_NAME, RELEASE_DATE and RELEASE_STATUS. The logic for the field SOURCE_NAME was updated to populate the same value as for the UPDATE_SOURCE.

Files changed:
metadata/core/ontology/reference/issuerrating-models.json

SDP-67953 Delta-Based Extract Regression in the October EagleML Release

The Delta-Based extract workflow had a different correlationId passing different from the process without a workflow. As a result, there was an error in the logic when the start /end time and status should be updated. The code was changed to not execute this logic when the Delta-based extract is called the in workflow process.
Files changed:
eagle_ml-2-0_cm/out/tagvalue/extract_delta_based.inc