Select rating plan factors in force¶
RatingPlanFactorExtensions.AsOfDate and .RatingPlan (clsRatingPlanFactorCollection.vb:434-444)
| Field | Value |
|---|---|
| Operation ID | OP-012 |
| Trigger | Validating or applying a rating plan modification factor |
| Inputs | A sequence of clsRatingPlanFactor, a date and/or a Enums.RatingPlans value |
| Outputs | Filtered sequence |
| Primary components | `RatingPlanFactorExtensions.AsOfDate and .RatingPlan (clsRatingPlanFactorCollection.vb:434-444)` |
| Entry point | Business\SAIF.Business.Policy.Rating\clsRatingPlanFactorCollection.vb |
Steps¶
AsOfDatekeeps factors whereEffectiveDate <= inAsOfDateandRatingPlankeeps factors whoseRatingPlanequals the requested plan.clsARPCreditFactor.Factoruses the resulting factor'sUpperLimitwhen itIsValid, otherwise- Use the related data-access statements and tables for this operation: SQL-038, SQL-039, SQL-040, RATING_PLAN_CODE, RATING_PLAN_FACTOR.
Process flow¶
The following diagram visualizes this operation's control flow.
flowchart TD
Start([Trigger: validating or applying a rating plan modification factor]) --> S1[AsOfDate: keep factors where EffectiveDate is less than or equal to inAsOfDate]
S1 --> S2[RatingPlan: keep factors whose RatingPlan equals the requested plan]
S2 --> D1{Resulting factor IsValid?}
D1 -->|Yes| S3[ARPCreditFactor uses the factor's UpperLimit]
D1 -->|No| S4[Fall back per business rules]
S3 --> Done([Filtered rating plan factor sequence])
S4 --> Done
Failure and edge-case behavior¶
- Review the linked business rules and SQL documents for the validation or data-access conditions that can block this operation.
Related documentation¶
Note: Statements marked with * were inferred from code structure, naming conventions, or contextual evidence where direct confirmation was not available in source artifacts. Statements marked with ** could not be confirmed; treat as unknown until verified.
Sources¶
Business\SAIF.Business.Policy.Rating\clsRatingPlanFactorCollection.vb