---
title: Retrieve policy minimum premium
summary: Retrieve policy minimum premium.
status: draft
owner: Technical Writer
last_reviewed: 2026-07-31
library: SAIF.Business.Policy
reference_type: package
operation_id: OP-006
trigger: A caller supplies a premium-history set id.
---

# Retrieve policy minimum premium

Retrieve policy minimum premium.

| Field | Value |
| --- | --- |
| **Operation ID** | OP-006 |
| **Trigger** | A caller supplies a premium-history set id. |
| **Inputs** | `IDataPortalInfo`, premium-history set id |
| **Outputs** | Minimum premium amount |
| **Primary components** | `PolicyInformation` |
| **Entry point** | `Business\SAIF.Business.Policy\PolicyInformation.vb` |

## Steps

1. Create a stored-procedure request using [SQL-010](../sql/SQL-010-saif-business-policy.md).
2. Bind the input set id and the two OUT parameters used by the Oracle package.
3. Execute inside an empty catch block so data-access failures do not propagate.
4. Read `out_minimum_premium_amount` when available; otherwise return `0`.
5. The Oracle package dispatches into voluntary, combination-voluntary, or assigned-risk logic on behalf of the caller.
5. Apply related business rules: [BR-POL-007](../business-rules.md#br-pol-007-database-failures-are-swallowed-for-minimum-premium-retrieval), [BR-POL-008](../business-rules.md#br-pol-008-missing-procedure-results-return-zero), [BR-POL-020](../business-rules.md#br-pol-020-procedure-dispatches-by-market-type), [BR-POL-021](../business-rules.md#br-pol-021-voluntary-combination-policies-use-combination-wide-minimum-logic), [BR-POL-022](../business-rules.md#br-pol-022-voluntary-periods-before-the-cut-over-date-use-a-fixed-minimum), [BR-POL-023](../business-rules.md#br-pol-023-assessment-handling-changes-at-the-alignment-date), [BR-POL-027](../business-rules.md#br-pol-027-procedure-failures-are-raised-inside-oracle-but-suppressed-by-the-net-caller)

## Process flow

The following diagram visualizes the main control flow for this operation.

```mermaid

flowchart TD

  Start([Trigger]) --> Work[Execute operation steps]

  Work --> Done([Return result])

```

## Failure and edge-case behavior

- Business rules are cross-referenced from the catalog page and the SQL or procedure logic cited in these steps.
- Database and procedure failures surface according to the underlying implementation path.

## Related documentation

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

## Sources

- `Business\SAIF.Business.Policy\PolicyInformation.vb`