...
The element Security Alias should not be specified in the incoming EagleML message. Please refer to Security Resolution for Warehouse Objects
Entity Resolution Logic
There are two ways to define Entity Id for Warehouse objects:
1. Refer to Entity Resolution for Warehouse Objects.
2. Providing EntityXrefIdType and EntityXrefId in the Batch Key in the incoming message.
...
| Element | Optional/ Required | Sample | Description | |
---|---|---|---|---|---|
1 | EntityID(EntityXrefId) | R | TSTVAL01 | ENTITY_ID from the RULESDBO.ENTITY table | |
2 | EntityXrefIdType | O |
| XREF_ACCOUNT_ID_TYPE from the RULESDBO.entity_xreference table. | |
3 | EndEffectiveDate | R | 20130713 | Date in format (YYYYMMDD) | |
4 | SourceName | R | EAGLE PACE | SHORT_DESC from the PACE_MASTERDBO.INTERFACES table | |
5 | FrequencyCode | O/R | D | D - DAY | |
6 | DictionaryName | R | TestValue2 | DICTIONARY_NAME from the RULESDBO.DICTIONARIES table | |
7 | PerfSummaryType | R | S | S - Index Constituent Performance Record(s) |
...
Anchor | ||||
---|---|---|---|---|
|
Severity can take the following values: F, W.
Once the dictionary_id is resolved, the Dictionary Node within the appropriate dictionary level must be resolved. This is also referred to as the Dictionary Item ID. If a dictionary Node is not found, the procedure will be permitted to add that node only if the severity on the edit 'Dictionary item not found' is set to 'W' (which stands for warning). If the severity level is set to 'F' for (fatal), this will result in an error condition as documented below. Constituent/Security returns (Security_alias != 0) are stored in the Perform.Perf_Sec_Returns table with a perf_rollup_returns_id of '0'. The procedure will not have the ability to establish new levels within a dictionary, only nodes within established levels.
...
- The procedure will evaluate variables (dictLevel2… dictLevel8) in the incoming record to determine which is the first column having a NULL value:
- If none of the variables are null, the incoming record is assigned DICTIONARY_LEVEL_CODE of 8.
- If a column other than DL1 (not input from file) is found to be NULL, the procedure will check whether any subsequent columns in the subset are NOT NULL.
- If any subsequent columns are NOT NULL, an error will be given that 'Invalid Dictionary Levels Found'.
If no subsequent columns in the subset are NULL, the procedure will assign DICTIONARY_LEVEL_CODE based on the first column that was found to be NULL in accord with the table below:
First NULL Column in Subset
DICTIONARY_LEVEL_CODE
DL 2 (dictLevel2)
1
DL 3 (dictLevel3)
2
DL 4 (dictLevel4)
3
DL 5 (dictLevel5)
4
DL 6 (dictLevel6)
5
DL 7 (dictLevel7)
6
DL 8 (dictLevel8)
7
The procedure will perform a lookup in the rulesdbo.dictionary table selecting Dictionary_item_id where the following characteristics are met:
Fancy Bullets - Dictionary_id = Dictionary_id
- DICT_L1_CODE_VALUE = DL1
- DICT_L2_CODE_VALUE = DL 2
- DICT_L3_CODE_VALUE = DL 3
- DICT_L4_CODE_VALUE = DL 4
- DICT_L5_CODE_VALUE = DL 5
- DICT_L6_CODE_VALUE = DL 6
- DICT_L7_CODE_VALUE = DL 7
- DICT_L8_CODE_VALUE = DL 8
- If the result is NOT NULL, the procedure will consider the variable to be DICTIONARY_ITEM_ID and store the record in accord with the data map.
- If the result is NULL, the procedure will check the severity level of the edit 'Dictionary Item Not Found.'
- If the edit is not found or if the result is anything other than 'F' or 'W' the procedure will give an error that 'Dictionary Item ID unclear'.
- If the result is 'F', the procedure will fail the record with the error 'Dictionary Item not found.
- If the result is 'W', the procedure will count the number of records in the rulesdbo.dictionary_format table having the following attributes:
Dictionary_id = DICTIONARY_ID
Dictionary_level = DICTIONARY_LEVEL_CODE
...
Field No. | Derived Field | Description | Notes | PACE Database | PACE Table(s) | PACE Field | Format | Validation | STAR Tag | |||
---|---|---|---|---|---|---|---|---|---|---|---|---|
89 | Update Date | Update Date | The procedure will populate current system date into the update_date field. The update_date in perf_summary and Perf_Sec_Returns should always be the same, even when there is no change to the perf_summary record directly. | Perform | Perf_summary/ | Update_date | Datetime |
| ||||
90 | Dictionary Id | Dictionary Id | Refer to the Dictionary ID Resolution Logic section. | Perform | Perf_Summary | Dictionary_id |
|
|
| |||
91 | Calendar Month End | Calendar Month End | Actual calendar month end for a specific month. For example, June 2004 would have a Calendar Month End date of 06/30/2004. | Perform | Perf_summary | End_effective_date | Datetime |
|
| |||
92 | Begin Effective Date | Begin Effective Date | The Begin effective date is derived from the end effective date. For example, June 2004 would have a Begin Effective Date of 06/01/2004. | Perform | Perf_Summary | Begin_Effective_date | Datetime |
| ||||
93 | LEVEL TYPE | Level Type |
| Perform | Perf_summary | Level_type | Char(8) |
| ||||
94 | PERF SEC ROLLUP RELATION INSTANCE | Instance Number | Perform | Perf_sec_rollup_relation | Instance | Number |
|
| ||||
95 | PERF SEC UNIVERSE INSTANCE | Instance Number | Refer to Perf Sec Universe Instance Logic | Perform | Perf_sec_universe | Instance | Number |
|
|