Page Comparison

...

Expand

title	What are the default filters and what are their default values? (for example, effectivedate defaults to current day, etc.)

There is only one default filter – maxrows (count of max returned records in the extract file) – the default value of this parameter is 100.000 records (refer to . For more information, see the Available Filters page in the EagleML wiki http://eagle.helpdocsonline.com/available-filters$Common%20Filter. ??NG EagleML reference).

Expand

title	What was the rationale for having the workflows not "stack up" on each other? When one workflow is run with the same I2IProcessUID, it will kill the prior extract.

There are two different cases:

Case #1 is for the STOP-START steps in the EJM Monitoring Tool. In the STOP step, the EJM core tries to stop the previously launched instance of the same workflow. This means that if we submit the eagle_i2i_full_extract_event twice, only one (1) instance will start.

Case #2 is for the I2IProcessUID parameter. This parameter is used only for the I2I delta mode and is related to the last run time. We can store several I2I delta workflows in one environment, so to separate the last time values for each delta workflow, this parameter will be used in the EagleML code.

...

Expand

title	Is it possible to extract only from the Composite table SMF?

Yes, it is possible. Do not set "historyOnlyFlag" filter value to "Y" – skip it in RTR or set to "N". In this case, Composite SMF table will be used (for . For more details, refer to information, see the Available Filters page in the EagleML wiki http://eagle.helpdocsonline.com/available-filters$History%20Only%20Filter). ??NG EagleML reference

Expand

title	Is it possible to use entityselectiontype2=EntityList as filter for I2I workflow in the Spoke?

Yes, it is possible. In this case, two (2) EntityList filters will be applied: first in the Hub and second in the Spoke.

...

Expand

title	How can we find out what version of I2I we are running?

I2I is part of EagleML, we don't have a separate version for I2I. EagleML/I2I have the same version.

To determine which EagleML version you have in your environment, open Message Center Editor and open the following file: /eagle_ml-2-0_cm/w_config.inc.

In the top line of this file, you will find information about the installed EagleML version. For example: <!-BR-EAGLEML_PRD_20151007.1->

In this example, you see BR-EAGLEML_PRD_20151007.1. This indicates that this environment contains the September 2015 monthend release. The date for the monthend release is typically the first Wednesday after the first Tuesday of the following month. For example, September 2015 EagleML monthend package was released on October 7th 2015. Refer to the related wiki page: For more information, see the Checking Your EagleML Version page in the EagleML wiki http://eagle.helpdocsonline.com/checking-your-eagleml-version. ??NG EagleML reference You can find detailed information about each EagleML release in the EagleML Release Notes section.

Filter Questions

Security Master File (SMF) Filters Questions

Expand

title	As shown in the wiki for SMF filters, the Include form is the default. If I don't specify any filters, should I assume that no filters will be applied and thus all security types will be extracted, all process security type will be extracted, etc.

Yes, if you don't specify any filters for SMF, then all SMF will be extracted. There are no default filters, with one exception: maxrows (count of max returned records in the extract file). The default value of this parameter is 100,000 records (refer to Available Filters wiki page).. For more information, see the Available Filters page in the EagleML wiki. ??NG EagleML reference
But, on the level of I2I processes, there is also the EntityList filter which can be considered default if it is set in the spoke map. The spoke can also use one of the available Sources from the Sources List to filter SMFs – this is defined in the spoke map.

...

Expand

title	Can this be used in the SMF request? And if so, what is the meaning of Date filters for SMF extract?

Yes, they can be used in SMF extracts. But, the date filters are different for Date filters without Held Mode and Date filters with Held Mode.

Expand

title	If effectivedate is selected, I expect the extract to look at the holding for the effective date specified in this parameter and extract all securities held for this effective date and entity list specified. Is this the case?

Date filters without Held Mode:
There is no "EffectiveDate" field in the composite SMF table (SECURITY_MASTER). This means that the "EffectiveDate" filter will be ignored if you extract the SMF from the composite table. If you extract the SMF from the history table (historyonlyflag parameter is set to Y), the "EffectiveDate" filter will be used in the following way:

Code Block
SECMASTER_HISTORY.EFFECTIVE_DATE >= TO_DATE([effective date filter value], 'YYYY-MM-DD')

This means that all SMF records from the history table with EFFECTIVE_DATE value greater than or equal to the effective date filter value will be extracted.
The "updatedate" filter can be used to extract SMF records from the composite or history tables in the following way:

Code Block
[Composite or History table].UPDATE_DATE >= TO_DATE([update date filter value], 'YYYY-MM-DD')

This means that all SMF records from the composite or history table with the UPDATE_DATE value greater than or equal to the update date filter value will be extracted.

Date filters with Held Mode:
Effective Date, which will be used as a restriction in the search for SMFs from Position and Cash Activity Sources, the value for Held mode is set by the following steps:

If parameter "ProcessCenter" is used (entityselectiontype=ProcessCenter, entityselectionvalue=[Process Center filter value]), then the value of "effectivedate" filter will be found from the RULESDBO.PROCESS_CENTER table, for example:
Code Block
select to_char(pc.curr_dt,'yyyy-mm-dd') EFFECTIVE_DATE from RULESDBO.PROCESS_CENTER pc where pc.process_center = [Process Center filter value]
To use two Entity filters, the following parameters are available:

entityselectiontype / entityselectionvalue
entityselectiontype2 / entityselectionvalue2

If we want to use ProcessCenter and EntityList filters together, we can use following structure:

Code Block

language	xml

<taskParameter>
    <name>entityselectiontype</name>
    <dataType>S</dataType>
    <value>EntityList</value>
</taskParameter>
<taskParameter>
    <name>entityselectionvalue</name>
    <dataType>S</dataType>
    <value>SCPAREN3</value>
</taskParameter>
<taskParameter>
    <name>entityselectiontype2</name>
    <dataType>S</dataType>
    <value>ProcessCenter</value>
</taskParameter>
<taskParameter>
    <name>entityselectionvalue2</name>
    <dataType>S</dataType>
    <value>US</value>
</taskParameter>

Order of filters is not important. "entityselectiontype2" parameter can be used for both, ProcessCenter or EntityList as follows:

If the value of ProcessCenter parameter is incorrect, then the value of "effectivedate" filter will be set as null.

If ProcessCenter parameter is not used and "heldeffectivedate" filter value exists in RTR, then "heldeffectivedate" filter value will be used for filtering by EFFECTIVE_DATE field, for example:

Panel
HOLDINGDBO.POSITION.EFFECTIVE_DATE = to_date([held effective date filter value],'yyyy-mm-dd') – for positions CASHDBO.CASH_ACTIVITY.ACCOUNTING_DATE >= to_date('2015-11-25','yyyy-mm-dd') – for cash activity

If ProcessCenter parameter is not used and "heldeffectivedate" filter value does not exist in RTR, then the value of "effectivedate" filter will be found as MAX of EFFECTIVE_DATE in the POSITION table. Conditions used in this query are: Date filter for UpdateDate, HeldPositionSource, and Entitylist.

...

Expand

title	Please give some details on how these filters interact. For example, if only FROMeffective date is selected, what is the TO effective date default?

"effectivedate", "fromeffectivedate" and "toeffectivedate" filters are available only for SMF history extract and not available in Held Mode as follows:

If we set only "effectivedate" filter value, then following SQL restriction will be added:
Code Block
SECMASTER_HISTORY.EFFECTIVE_DATE = TO_DATE([effective date filter value], 'YYYY-MM-DD')
If we set only "fromeffectivedate" filter value, then following SQL restriction will be added:
Code Block
SECMASTER_HISTORY.EFFECTIVE_DATE >= TO_DATE([from effective date filter value], 'YYYY-MM-DD')
If we set only "toeffectivedate" filter value, then following SQL restriction will be added:
Code Block
SECMASTER_HISTORY.EFFECTIVE_DATE <= TO_DATE([to effective date filter value], 'YYYY-MM-DD')

If we set "fromeffectivedate" and "toeffectivedate" filter values, then following SQL restriction will be added:

Code Block
SECMASTER_HISTORY.EFFECTIVE_DATE >= TO_DATE([from effective date filter value], 'YYYY-MM-DD')

AND

Code Block
SECMASTER_HISTORY.EFFECTIVE_DATE <= TO_DATE([to effective date filter value], 'YYYY-MM-DD')

...

Versions Compared

Old Version 5

New Version 6

Key

Filter Questions

Security Master File (SMF) Filters Questions