Skip to content

Financial transaction retrieval

This operation loads individual payment/financial transaction rows for a claim, keyed by claim ID, policy number, or reimbursement issue date, through Oracle stored procedures in pk83407_payment_hist_trans. It is the legacy, transaction-level financial read path, distinct from the API-backed aggregate claim reserves and payments retrieval operation used by current claim-summary consumers.

Field Value
Operation ID OP-VC-03
Trigger Caller retrieves clsFinancialTransactionCollection using one of the supported search modes
Inputs Claim ID, policy number, or reimbursement issue date; individual transaction sequence/type for single-record reads
Outputs clsFinancialTransactionCollection of clsFinancialTransaction rows, each optionally enriched with payment remarks
Primary components clsFinancialTransactionCollection.Criteria.RetrieveSQL, clsFinancialTransaction.getPayRemarks
Entry point Business\SAIF.Business.View.Claim\clsFinancialTransactionCollection.vb, Business\SAIF.Business.View.Claim\clsFinancialTransaction.vb

Steps

  1. Select the retrieval mode. A caller constructs the collection criteria using one of claim ID, policy number, or reimbursement issue date search modes (BR-001).
  2. Dispatch the mode-specific stored procedure. clsFinancialTransactionCollection.Criteria.RetrieveSQL returns SelectFinTranByClaimId, SelectFinTranByPolicyNum, or SelectReimbFinTranByIssueDate according to the selected mode (SQL-007, SQL-008, SQL-009).
  3. On failure or when Oracle source is unavailable: the corresponding stored procedure could not be located during source review, so this call path may be dead or environment-specific.**
  4. Populate transaction rows. The BOF data portal executes the resolved stored procedure and populates one clsFinancialTransaction per returned row.
  5. Resolve payment remarks. clsFinancialTransaction.getPayRemarks calls additional pk83407_payment_hist_trans procedures to resolve remark text for individual transactions (SQL-004, SQL-005).
  6. Return the transaction collection. The collection returns read-only financial-transaction data to the caller.

Process flow

The following diagram visualizes this operation's control flow.

flowchart TD
    Start([Caller selects retrieval mode]) --> Mode{Claim ID, policy number,<br>or reimbursement issue date?}
    Mode -->|Claim ID| ByClaim[SelectFinTranByClaimId]
    Mode -->|Policy number| ByPolicy[SelectFinTranByPolicyNum]
    Mode -->|Reimbursement date| ByDate[SelectReimbFinTranByIssueDate]
    ByClaim --> Populate[Populate financial transaction rows]
    ByPolicy --> Populate
    ByDate --> Populate
    Populate --> Remarks[Resolve payment remarks per transaction]
    Remarks --> Done([Return read-only transaction collection])

Failure and edge-case behavior

  • Note and financial-transaction read paths rely on Oracle stored procedures that were not found during source review, so callers of this operation may represent dead or environment-specific code paths.**
  • Payment-remark resolution is performed per transaction, so a large result set issues one additional stored-procedure call per row.*

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.View.Claim\clsFinancialTransaction.vb
  • Business\SAIF.Business.View.Claim\clsFinancialTransactionCollection.vb