Jake 11.27 note - info taken from below:
\\thenest\users\jmathews\DOC Team\RDC_PRICING CENTER\JIRAs\DOC-1625_Engine Processing
The ultimate goal of RDC Prices is to produce Gold Copy Price records for a given effective date and a fixed set of securities out of raw prices received from multiple vendors, or by using prior day Gold Copy prices. To achieve this goal, RDC Prices uses Data Strategies, and the concepts of a Main Engine and Rule Engines, to process activity.
...
Data Strategies maintain their own security criteria.
Data Strategies can reference one or more security holdings (Portfolios), each with their own selection criteria.
The final set of securities subject to processing by a Pricing Data Strategy is determined by first applying the Data Strategy Security Criteria against the Securities database, then applying all Holdings security criteria to the resulting set when Holdings criteria is selected to be applied. If holdings are not specified in the filtering criteria, all eligible securities resolved will be included.
Source Hierarchy
Data Strategies reference a Source Hierarchy where all participating vendor sources are arranged in order of importance.
The Prior Day Gold Copy source is optional, and usually assigned the lowest level in the hierarchy for Data Management clients or in when actively using Accounting, the lowest level is set as Price at Cost.
Demand Phase
The processes that load vendor data into the database need to know which prices are expected for a specific Data Strategy.
The Demand Phase is executed in order to create “shell” records for each combination of security, source from the source hierarchy, and effective date.
The Demand Phase also creates a Gold Copy “shell” record for each combination of security and effective date.
...
Data Strategies use Validation Rules to validate source prices during the Validation Phase.
Each Validation Rule has its own Selection Security Criteria that is used against the set of securities that was used to generate demand.
If a vendor price record fails validation, then it cannot be used later in Gold Price compositing.
Validation rules can be global Global or regularRegular:
Global rules are applied to every Data Strategy using global validation rules
Alternatively, Data Strategies can declare use of specific regular validation rules while ignoring global rules
...
A typical set of input parameters includes data strategy identification, effective date, specific phase identification, and a security alias selector. The security alias selector is either a range of security aliases, or a list of values.
Jake note - would it help to have an example here, or reference the system configuration that determines the maximum number of securities processed by a single rule engine?
Add label