SDP-15754 : Add support of WarehouseNavMonthEnd object to eagle_wrf_generic_load workflow.
The Generic Load workflow was enhanced to support the 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. The Pricing Center event does did not wait for its completion and reports reported that the whole event is had finished. When the Pricing Center event is executed via EJM, the process is was marked as complete even if the sub-event is was still running.
EJM EJM was enhanced to check statuses of Pricing Center sub-events and wait for their completion.
Files changed:
exec_pace_event.xml
exec_pace_event_pricing_check.inc
SDP-15206 : In the Generic Loader change to process change the processing so that the SMF Composite is only executed to execute when loading SMF data
The Generic Load workflow has a sub-process, “eagle_generic_load_smf_composite” composite,” which can be used to call a Pace Event or , RDC or SRM events.
When one of the following parameters (PACEEventName, W_ExecuteSRM or W_ExecuteRDC) is was set (for example in w_config_custom.inc) this sub process was launched.
The problem was regardless of whether This sub-process was triggered whether or not SMF files were present in the incoming files, this sub-process was triggered.
Condition The condition to trigger this step was updated to check if the SMF file is part of the incoming files.
...
SDP-14278 : Add handling any issues in TSR from reason node processed by i2i_parse_errors_from_hub.xsl/taskstatusresponse.xml
In During the the Instance2Instance process, two environments exchange RTR's \TSR's with each other. In case if error happens If an error occurs on the remote server, when it sends back a failed TSR , is sent. The change is for the local environment should to be able to process this the TSR and show the correct error description message on the local environment.
The XSL Transformation file has been adjusted to process all error descriptions present in the incoming TSR file.
...
issuePrice has been adjusted that in case of an invalid effectiveDate or sourceName fields in the incoming message, the logic goes defaults to insert mode, instead of update mode as it was before. (Different stored procedure)
Files changed:
- msgcenter\eagle_default\in\xml\xml-ref_issueprice.xml
...
The AccountingAssetCash Interface was enhanced to support the cashEventType element for MISC Income and Expense Asset Cash message types (Asset Cash Type = AMISCINC or AMISCEXP).
Possible values of Cash Event Type: DISB, RECPT.
...
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
...