Enhancements:
SDP-28462: The Inbound Interface for Accounting Asset Cash was updated to support Accounting Cash Miscellaneous Expenses
The Inbound Interface for the Accounting Asset Cash was updated. The AMISCEXP, assetCashType='AMISCEXP', is now supported.
The logic for tag85 and mapping for tag5363 was corrected. Users can now specify the Settlement Currency separately from the asset currently via the RTR.
File changed:
eagle_default\in\include\csv-cash_misc_inc_exp.inc
...
SDP-27846: The logic for the calcTransactionId and calcCancelTransactionId was modified in the Warehouse Trade Extract - WRHSTRADEEXTRACT
The fields calcTransactionId and calcCancelTransactionId are concatenated with starTag26 when the parameters EnhanceCalcTransactionId = Y and IncludedExtendedDetails = Y or ALL. The logic of these fields was modified as following: starTag26 is now applied only if the recordType of the trade is 350 or 450 when the parameters EnhanceCalcTransactionId = Y and IncludedExtendedDetails = Y or ALL.
...
SDP-26957: Added New Processing Option for Issuer Role Batch Load via SMF MI Interface
A new processing option that enables grouping for Issuer Role Batch Loads was introduced.
To leverage this option, you will need to include ISSUER_ROLE_GROUPING in the data file:
<header>
<objectType>GenericSMF</objectType>
<processingOptions>ISSUER_ROLE_GROUPING</processingOptions>
</header>
This new option allows you to load Issuer Role as Batch and generate complete ownership period for Security + Role Type Key.
Issuer Role batch records have 2 processing options set by default: <processingOptions>ISSUE_ROLE_UPSERT_MODE,USE_LATEST_START_DATE</processingOptions>, where
ISSUE_ROLE_UPSERT_MODE - prevents delete of existing records that preserves history about previous ownership
USE_LATEST_START_DATE - applies max start date to each issuer role record, forming 1 ownership period based on incoming Issuer Roles even if they have different start dates.
Files changed:
eagleml_smf_issuer_role.xsl
...
SDP-19651: Added possibility to include details of the Successful messages into the Consolidated TSR
A Consolidated TSR represents an additional report of the workflow, summing up the TSR's for each of the subprocesses of the workflow. The Consolidated TSR was improved to include SUCCESS Messages now. A new flag IncludeAllDetails (W_INCLUDE_ALL_DETAILS) was added. Possible values: Y/N. The default value is N.
The flag allows to include details for SUCCESS messages in the Consolidated TSR like:
<transactionId>B90DBM55FL6PIXJB</transactionId>
<eagleDetailId>4839327</eagleDetailId>
<identifier><identifierName>fromId</identifierName><identifierValue>1</identifierValue>
</identifier><identifier><identifierName>account</identifierName><identifierValue>261</identifierValue>
</identifier><identifier><identifierName>referenceNumber</identifierName><identifierValue>-3862</identifierValue>
</identifier><identifier><identifierName>identifier2</identifierName><identifierValue>19900101</identifierValue>
</identifier><identifier><identifierName>identifier3</identifierName><identifierValue>99</identifierValue>
</identifier>
...
The Fx Rate inbound rule was improved to use a direct-SQL call instead of a panel call, which is much slower compared to the direct SQL query. The load rate was improved
from 20 rec/sec up to 200 rec/sec. Additionally, the Fx Rate load is currently supported via an XMLDBAPI request with the load rate being about 350 rec/sec.
This is the non-default mode and requires a parameter in the incoming EagleML message to not use the panel load and validations:
<accountingValidationFlag>N</accountingValidationFlag>
Files changed:
xml-ref_fxrate.xml