Reference code retrieval¶
This operation covers the library's set of simple, structurally near-identical reference-code lookups: closure location type, closure type-of-order, MCO status reason, order type, work status, work release, vocational responsibility, claim cost category, and claim activity type/category codes. Each lookup follows the same shape — a single-record class filtered by code and a companion collection class that returns the full code list — with inline Oracle SELECT statements and no business-rule branching beyond code filtering. They are documented together because they share one governing pattern rather than distinct rule sets.
| Field | Value |
|---|---|
| Operation ID | OP-VC-09 |
| Trigger | Caller retrieves a specific lookup object or its collection (e.g. clsClosureLocationTypeCode(Collection), clsClosureTypeofOrderCode(Collection), clsMcoStatusReasonCode(Table), clsOrderTypeCode(Collection), clsWorkStatusCode(Table), clsWorkReleaseCode(Table), clsVocResponsibilityData, clsClaimCostCategoryCode(Collection), clsClaimActivityTypeCode(Collection)) |
| Inputs | Optional code filters depending on the lookup object |
| Outputs | Reference code rows (code, description, and lookup-specific metadata) |
| Primary components | clsClosureLocationTypeCode(Collection), clsClosureTypeofOrderCode(Collection), clsMcoStatusReasonCode(Table), clsOrderTypeCode(Collection), clsWorkStatusCode(Table), clsWorkReleaseCode(Table), clsVocResponsibilityData, clsClaimCostCategoryCode(Collection), clsClaimActivityTypeCode(Collection) |
| Entry point | Business\SAIF.Business.View.Claim\clsClosureLocationTypeCode.vb, Business\SAIF.Business.View.Claim\clsClosureTypeofOrderCode.vb, Business\SAIF.Business.View.Claim\clsMcoStatusReasonCode.vb, Business\SAIF.Business.View.Claim\clsOrderTypeCode.vb, Business\SAIF.Business.View.Claim\clsWorkStatusCode.vb, Business\SAIF.Business.View.Claim\clsWorkReleaseCode.vb, Business\SAIF.Business.View.Claim\clsVocResponsibilityData.vb, Business\SAIF.Business.View.Claim\clsClaimCostCategoryCode.vb, Business\SAIF.Business.View.Claim\clsClaimActivityTypeCode.vb |
Steps¶
- Invoke a specific lookup object or its collection. A caller invokes either the single-record class (filtered by code) or the collection class (full list) for the reference domain it needs.
- Execute inline Oracle SQL. Each object issues its own inline
SELECTagainst its reference table: - Closure location type: SQL-014, SQL-015 (CL_CLOSURE_LOCATION_TYPE_CODE)
- Closure type-of-order: SQL-016, SQL-017 (CL_CLOSURE_TYPE_OF_ORDER_CODE)
- MCO status reason: SQL-018, SQL-019 (CL_MCO_STATUS_REASON_CODE)
- Order type: SQL-020, SQL-021 (CL_ORDER_TYPE_CODE)
- Work status: SQL-023, SQL-024 (CL_WORK_STATUS_CODE)
- Work release: SQL-025, SQL-026 (CL_WORK_RELEASE_CODE)
- Vocational responsibility: SQL-027 (VOCATIONAL_RESP_CODE)
- Claim cost category: SQL-012 (CL_CLAIM_COST_CATEGORY_CODE)
- Claim activity category/type: SQL-028 (CLAIM_ACTIVITY_CAT_TYPE_CODE)
- Return the read-only row(s). Returned rows populate read-only business objects consumed by higher-layer claim workflows and lookups.
Process flow¶
The following diagram visualizes this operation's control flow.
flowchart TD
Start([Caller invokes a reference lookup or its collection]) --> Domain{Which reference domain?}
Domain -->|Closure location/order type| Closure[Query closure/order code table]
Domain -->|MCO status reason| Mco[Query MCO status reason table]
Domain -->|Order type| Order[Query order type table]
Domain -->|Work status or release| Work[Query work status/release table]
Domain -->|Vocational responsibility| Voc[Query vocational responsibility table]
Domain -->|Cost category or activity type| Cost[Query cost category/activity type table]
Closure --> Done([Populate read-only lookup object])
Mco --> Done
Order --> Done
Work --> Done
Voc --> Done
Cost --> Done
Failure and edge-case behavior¶
- Many reference-data queries use unqualified table names, so schema ownership is unknown from source alone.**
- Each lookup is independently implemented with no shared base retrieval helper found in this library, so a bug in one lookup's SQL would not necessarily affect the others.*
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.View.Claim\clsClaimActivityTypeCodeCollection.vbBusiness\SAIF.Business.View.Claim\clsClaimCostCategoryCodeCollection.vbBusiness\SAIF.Business.View.Claim\clsClosureLocationTypeCode.vbBusiness\SAIF.Business.View.Claim\clsClosureLocationTypeCodeCollection.vbBusiness\SAIF.Business.View.Claim\clsClosureTypeOfOrderCodeCollection.vbBusiness\SAIF.Business.View.Claim\clsClosureTypeofOrderCode.vbBusiness\SAIF.Business.View.Claim\clsMcoStatusReasonCode.vbBusiness\SAIF.Business.View.Claim\clsMcoStatusReasonCodeTable.vbBusiness\SAIF.Business.View.Claim\clsOrderTypeCode.vbBusiness\SAIF.Business.View.Claim\clsOrderTypeCodeCollection.vbBusiness\SAIF.Business.View.Claim\clsVocResponsibilityData.vbBusiness\SAIF.Business.View.Claim\clsWorkReleaseCode.vbBusiness\SAIF.Business.View.Claim\clsWorkReleaseCodeTable.vbBusiness\SAIF.Business.View.Claim\clsWorkStatusCode.vbBusiness\SAIF.Business.View.Claim\clsWorkStatusCodeTable.vb