---
title: "Retrieve affiliated policies / policies for an account"
summary: "Retrieve affiliated policies / policies for an account."
status: draft
owner: Technical Writer
last_reviewed: 2026-07-31
library: SAIF.Business.Policy.Core
reference_type: package
operation_id: "OP-002"
trigger: "caller needs the set of policies related to a subject policy or account"
---

# Retrieve affiliated policies / policies for an account

Retrieve affiliated policies / policies for an account describes the corresponding policy-core workflow and its BOF or Oracle touchpoints.

| Field | Value |
| --- | --- |
| **Operation ID** | OP-002 |
| **Trigger** | caller needs the set of policies related to a subject policy or account |
| **Inputs** | data portal, policy number, `AffiliationTypes` value, mask-data flag |
| **Outputs** | `clsPolicyCollection` |
| **Primary components** | ``clsPolicyCollection.GetAffiliatedPolicies(...)`, `clsPolicyCollection.GetPoliciesForAccount(...)`` |
| **Entry point** | `Business\SAIF.Business.Policy.Core` |

## Steps
1. Select the affiliation strategy from the `AffiliationTypes` enum (`Relationship` vs `Account`).
2. Configure the criteria with the corresponding predicate over `POLICY` / `POLICY_RELATIONSHIP`.
3. Execute retrieval; `Fill` each item, applying masking per [BR-020](../business-rules.md#br-020-when-masking-is-requested-policyholder-names-contact-identitycontact-method) when requested.
4. Return the collection.
5. Consolidate supporting references.
   - Related business rules: [BR-020](../business-rules.md#br-020-when-masking-is-requested-policyholder-names-contact-identitycontact-method)
   - Related SQL statements: [SQL-074](../sql/SQL-074-saif-business-policy-core.md)
   - Related tables: [POLICY](../database-tables.md#policy)

## Process flow

The following diagram visualizes this operation's control flow.

```mermaid
flowchart TD
    Start([Trigger]) --> S1[Apply policy-core logic]
    S1 --> D{Validation or branch?}
    D -->|Continue| S2[Execute BOF SQL or Oracle call]
    D -->|Stop| EndErr([Return error or empty result])
    S2 --> EndOk([Return populated result])
```

## Failure and edge-case behavior
- Error, warning, and empty-result behavior follows the rules and SQL cited in the steps above.
- Stored-procedure-backed paths depend on Oracle-side logic outside this repository.**

## Related documentation
- [Operations and processes](../operations-processes.md)
- [Business rules](../business-rules.md)
- [SQL catalog](../sql/index.md)
- [Database tables](../database-tables.md)

> **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.Core\clsPolicy.vb`
- `Business\SAIF.Business.Policy.Core\clsPolicyPeriodBase.vb`
- `Business\SAIF.Business.Policy.Core\clsPolicyPeriod.vb`
- `Business\SAIF.Business.Policy.Core\clsLegacyPolicyPeriod.vb`
- `Business\SAIF.Business.Policy.Core\clsCancelReasonOverride.vb`
- `Business\SAIF.Business.Policy.Core\WCISInquiry.vb`