...
- The contractualCashSettlementRule type was changed from integer to string in the XSD
- Logic for resolving the Month End Date Rule was updated in the Generic Entity Inbound rule. The lookup has been replaced with a SQL request.
The following parameter with a value of "Y" is required:
<taskParameter>
<name>IncludeEntityRuleKeys</name>
<dataType>S</dataType>
<value>Y</value>
</taskParameter>
Files changed:
estar\tpe\dynamic\eagleml\schema\eagleml-entity-2-0.xsd
estar\tpe\dynamic\eagleml\schema\eagleml-entity-shared-2-0.xsd
estar\tpe\dynamic\eagleml\schema\estar\tpe\dynamic\msgcenter\
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\tagvalue\extract_entity_accounting_basis.inc
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\t_entity_accounting_basis_streaming.inc
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\tagvalue\extract_entity.inc
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\t_entity_streaming_eml.inc
estar\tpe\dynamic\msgcenter\eagle_ml-2-0_cm\out\xml\t_entity_streaming.inc
estar\tpe\dynamic\msgcenter\eagle_default\in\xml\xml-ent_entitygeneric.xml
This issue was tracked as Item #159006.
...
Add skipIfExist Flag for Generic Entity
The skipIfExist flag was absent in the Generic Entity interface.
Logic for skipIfExist flag was added in the case that the entity should not be updated.
Files changed:
estar\tpe\dynamic\msgcenter\eagle_default\in\xml-ent_entitygeneric.xml
...
EagleMl: ISSUEEXCHANGEPRICEEXTRACT Made Valid Against XSD
The ISSUEEXCHANGEPRICEEXTRACT EagleML output was not passing validation against the XSD.
The T-rules fixed. Streaming support was added for ISSUEEXCHANGEPRICEEXTRACT.
Files changed:
w_config.inc
t_eagleml-2-0_streaming.rsf
t_issueprice_exchange.xml
t_issueprice_exchange_streaming.inc
t_issueprice_exchange_streaming.xml
...
- Xref Aliases Resolution
2. Insert/Update Xrefs
The following optimizations were introduced to improve Generic SMF load performance.
1. The request for xref aliases resolution was replaced with direct call of the PACE_MASTERDBO.ESTAR_SEC.XREF_QUERY_ONE_ROW SP via MSGEXCHANGE.
2. The request for insert/update xrefs was replace with a parametrized request which uses an XMLDBAPI bind for Oracle. The bind file was placed into metadata\bind\estardbc\bind-custom-smf-xrefs.xml file. It is linked with the bind.xml file dynamically during EagleML installation in ‘eagle_ml-2-0_default_cm_w_setup’ step.
For MSSQL the request was optimized in order for the body of the request to be the same for each xref pair. Also the part of request where security alias is resoling was moved to a separate request. This request is executed only if security_alias (tag 10) was not resolved earlier. Finally the request for updating secmaster_history after loading xrefs was also parametrized for Oracle and MSSQL.
Files changed:
estar\tpe\dynamic\msgcenter\eagle_default\in\xml\include\xref_alias_resolution.inc
...