Versions Compared

Key

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

SDP-

...

15754 : Add support of WarehouseNavMonthEnd object to eagle_wrf_generic_load workflow.

Generic Load workflow was enhanced to support WarehouseNavMonthEnd objects.

Files changed:
msgcenter\eis\ejmwf\eagle_wrf_generic_load.ejmwf
msgcenter\eagle_ml-2-0_workflows\eagle_wrf_generic_load.wrf


SDP-14563 :  Pricing Center - Parent event showing completed prior to child event completing

When a Pricing Center Event consists of one rule, the sub-event that is executed for this rule runs independently. Pricing Center event does not wait for its completion and reports that the whole event is finished. When Pricing Center event is executed via EJM, the process is marked as complete even if sub-event is still running.

...

Modified file:
sequencer_orch.xml


SDP-

...

15048 EagleML: Source interface has an issue with long sourceName

Added logic to check that the value of sourceName element does not exceed 15 characters during the Source Interface load.

Files changed:
xml-ref_source.xml


SDP-12457 : Incorrect error message for WarehousePosition

Wrong security identifiers could be displayed in TSR when warehouse position load fails in the Batch mode.
Changed errors processing for the batch mode. Error returned by database will be displayed in TSR because it has correct identifiers.

...

ActionType = CANCELFILE
StreamName=eagle_ml-2-0_default_cm_execwkfl
CancelWorkflowName – Workflow Name to cancel event wait (optional parameter, should be used when W_WAITEVENTS_DATABASE_MODE=Y and W_ENABLE_EXTENDED_FILE_STATISTICS=N)
To cancel event wait for run workflow should use one from the next parameters:
WaitEventCorrelationId – CorrelationID of the file to cancel event wait
FileName – a name of the file to cancel event waitFiles Changed:
eagle\estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\cancel_global_event_wait.inc
eagle\estar\tpe\dynamic\msgcenter\eagle)
To cancel event wait for run workflow should use one from the next parameters:
WaitEventCorrelationId – CorrelationID of the file to cancel event wait
FileName – a name of the file to cancel event wait


Files Changed:
eagle\estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\cancel_global_event_wait.inc
eagle\estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\get_file_stat.inc
eagle\estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\tagvalue\execute_wrkfl_event.xml
eagle\estar\tpe/dynamic\msgcenter\eagle_ml-2-0_cm\cleanup_orch_wait_state.inc


SDP-17577 :  WRHSOPENLOTEXTRACT and WRHSPOSITIONEXTRACT - MSTARDIRECT source with IncludePortfolioValuation set to Y or ALL failing

When Source is 'MSTARDIRECT', the extract SQL query was generated incorrectly.

Fixed the error of executing of Warehouse Position and OpenLot extracts with parameter 'IncludePortfolioValuation' = Y or ALL and Source filter = 'MSTARDIRECT'.
Changed rules:
- extract_holding_ext_port_valuation_fields.inc


SDP-15207 : EagleML: Warehouse Rollback functionality shouldn't use CorrId from the file name(XMLDBAPI)
SDP-15191 : EagleML: Warehouse Rollback functionality shouldn't use CorrId from the file name(EagleML)

Roll Up rule handled correlationId value in the incoming file name for the Rollback functionality. 
This value was used in the query for checking which sub batches had failed on the load and run a roll back for the whole batch.

Only correlationId in the file name can link key and data files related to the one process instance. 
This method was not reliable because correlationId should be in exact place in the file name.

This approach was replaced by adding correlationId value on the Python transformation step in the files itself.
Now key and data files have an additional value CORRELATION_ID(XMLDBAPI) and taskIdentifier/correlationId (EagleML).
It helps to link key and data files related to the one process more reliable, because each process has unique correlationId.

Changed files:
include/xml-warehouse_common.inc
xml-dbdirect_invar.xml
xml-dbdirect_invar_rollup.xml
xml-warehouse_v2.xml


SDP-9851 :  issue in loading extended generic SMF (Xpanels extension and fieldCompareFlag=Y bug)

There was a problem with extension processing when fieldCompareFlag = Y, because insert\update to the extension table happens in separate DB call and as a result extension and core tables could not be in sync.

The new implementation allows to extend core stored procedure to support loading extension fields and keep extension and core tables in sync.
Please note: To activate this logic and switch to the new processing some manual steps are required. 
They have to be done only once, please visit confluence page about extensions.

Changed files:

eagle_default/in/xml/include/custom_fields.inc
eagle_default/in/xml/include/msgxchg_sec_core.inc
eagle_default/in/xml/include/ng_exec_sp.inc
eagle_ml-2-0_cm\get_file_stat.inc
eagle\estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\tagvalue\execute_wrkfl_event.xml
eagle\estar\tpe/dynamic\msgcenter\eagle_ml-2-0_cm\cleanup_orch_wait_state.inc

SDP-17577 :  WRHSOPENLOTEXTRACT and WRHSPOSITIONEXTRACT - MSTARDIRECT source with IncludePortfolioValuation set to Y or ALL failing

When Source is 'MSTARDIRECT', the extract SQL query was generated incorrectly.

Fixed the error of executing of Warehouse Position and OpenLot extracts with parameter 'IncludePortfolioValuation' = Y or ALL and Source filter = 'MSTARDIRECT'.
Changed rules: /generate_sp_on_fly.inc

 

SDP-10059 : Issues with EXPENSEACTIVITYEXTRACT

Expense Activity Extract does not report any error in case mandatory filters reportStartDate and reportEndDate were not specified. 

Correct parameter handling was added so that appropriate error message is returned.

File changed:
extract_acct_expense_activity.inc

 

SDP-17578 : WRHSOPENLOTEXTRACT and WRHSPOSITIONEXTRACT - Malformed XML

Issue in grouping in Warehouse Position and OpenLot extracts when ‘IncludePortfolioValuation’  was set to Y or ALL when more than one price information exists for the specific position.

PortfolioValuation logic has been enhanced and new repeated node pvAssetPrice was added in extendedPortValuationModel.
This model will describe all prices which exist for the specific position.

Changed rules: 
- extract_holding_ext_port_valuation_fields.inc
- t_holding_portfolio_valuation_fields_streaming.inc
- extract_save_and_execute_query.inc