In this page:
...
- with a dedicated interface Reference Underlying SMF via eagle_ml-2-0_default_in_xml_reference stream (objectType = UnderlyingSMF)
- with SMF via eagle_ml-2-0_default_in_xml_smf_generic stream (objectType = GenericSMF with UnderlyingModel)
Related rules
- Default rule for Underlying processing is xml-smf_underling.xml
- If the Batch Key is set, the data is routed to xml-smf_underling_batch.xml
...
Local parameter - underlyingDeleteReinsertSwitch
Setting to Y allows to delete the underlying record by SecurityAlias + UnderlyingSecurityAlias key and reinsert a new incoming one.
Underlying Retain Begin Date Switch
...
There will be only one record, meaning that only one underlying SMF will be open for a combination of Main Security Alias + Underlying Type.
If there is an open record for the same combination of Main Security Alias and Underlying Type as that of the incoming record, the open record will now be closed with the end date = incoming begin date - 1.
This option may be turned on via the global flag W_UNDERLYINGSMF_UNIQUE_RECORD_PER_TYPE_SWITCH set to Y or within the incoming file.
Example of usage:
| Code Block | ||
|---|---|---|
| ||
<header> <objectType>UnderlyingSMF</objectType> <processingOptions>UNIQUE_RECORD_PER_UNDERLYING_TYPE</processingOptions> |
...
</header> |
This new option may be used independently or in combination with the W_UNDERLYINGSMF_DELETE_REINSERT_SWITCH.
If both the W_UNDERLYINGSMF_DELETE_REINSERT_SWITCH and W_UNDERLYINGSMF_UNIQUE_RECORD_PER_TYPE_SWITCH are set to Y, the expected behavior is as follows:
The existing records with the same security alias (main security) + underlying alias (underlying security) as that of the incoming record are deleted before load.
All open records with the same Main security and Underlying Type will be closed with the end date = incoming begin date -1.
An error is thrown when the incoming begin date is less than the existing begin date in the database.
A new record is stored in the database.