...
Files changed:
eagle_ml-2-0_cm\wrkfl_add_log_entry.inc
eagle_ml-2-0_cm\wrkfl_cancel_log_entries.inc
eagle_ml-2-0_cm\wrkfl_get_processed_events_count.inc
eagle_ml-2-0_cm\wrkfl_read_log_file.inc
eagle_ml-2-0_cm\wrkfl_write_log_file.inc
SDP-42710: Introduction of new capabilities to supportprocessing of Multileg Corporate Actions
A new object type, MultilegCA, was created and will support the load of multi-legged corporate actions via eagle_ml-2-0_default_in_xml_reference. It was created to support the load and insert process of select multi-legged corporate actions. This process imitates the front-end process for inserting multiple legs of one corporate action under the same Corporate Action ID, Sub Priority, and Batch Event ID.
Each individual leg may have different values for the required and user defined fields while the sharing the same global parameters. This new functionality will be loaded via eagle_ml-2-0_default_in_xml_reference for the following panels:
pan-addcallput.htm
pan-addexchangeoffer.htm
pan-addmerger.htm
pan-addmerger-rate.htm
pan-addrightsissue.htm
pan-addspinoff.htm
pan-addspinoff-rate.htm
pan-addtender.htm
In the case of any error, whether at the global level or one of the individual legs, all legs will be deleted/rolled back from the corporate action tables and the EML message will fail with error description.
Files added:
eagle_default/in/xml/include/xml-ref_ca_common.inc
eagle_default/in/xml/xml-ref_multileg_ca.xml
...
When the GenericEntity is sent without a populated entityId node, there is functionality to generate a dummy (system generated) entity Id. This method returns the next sequence “RULESDBO.ENTITY“ integer value . In some cases such as high generation, it returns non-unique values. To escape and prevent the problem, a new “GUID” method to generate a unique dummy entity id was added. It may be set as USE_GUID_AUTO_GEN_ENTITY_ID value in the <processingOptions> or set the global parameter W_USE_GUID_AUTO_GEN_ENTITY_ID variable to Y in the w_config_custom.inc. When applied, the “GUID” method will be used to generate an entity id.
It will generate and return a combination of eight alphanumeric characters. An additional check will be executed that checks the uniqueness of this combination in the DB using the entity lookup. If it is not unique, then a new combination will be generated.
Files changed:
eagle_default/in/xml/include/entity_common_header_aliases.inc;
eagle_default/in/xml/include/entity_xref_resolution.inc.
SDP-42483: GenericSMF Ontology was updated to support additional fields from SECURITYDBO.SECURITY_MIFID
...
If a twin CA record is found, check the Cp Status (tag 54).
If the cpStatus of a twin CA record is PD/Pending or NC/Incomplete, then the twin CA record is generates a Delete CA announcement and a new ROC or CASHDIV corporate action will be created. When processed, the original corporate action will be deleted.
If the cpStatus of a twin CA record is RD/Released, then it must have a unique subpriority when using the accountingValidationFlag set to Y in order to pass the business and system edits. The twin CA record is will generate a Cancel Corporate Action announcement and a new ROC or CASHDIV corporate action. When processed, the original corporate action will be canceled.
Processing The processing option should be part of the incoming file:
<referenceTransaction>
<header>
<processingOptions>CA_TRANS_TYPE_TWINS</processingOptions>
</header>
</referenceTransaction>
...
The dynamic procedure, ESTAR.PRF_EGL_GEN_INTERFACE_EXT, responsible for the data insert/update in Batch mode only as part of Warehouse Performance Inbound interface, was raising database errors during data processing. The failures occurred when an entity was not assigned to a partition or when the UpdateSource was not part of the incoming data file. Both issues were fixed.
...