Results for “po_box_number”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_ZA_BRANCH_CDV_DETAILS is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores Bank and Branch information used to verify Bank account numbers, specifically supporting the South African (ZA) localization's bank account validation and Cash Disbursement Voucher (CDV) processing. The table acts as a reference repository of bank and branch identifiers, address details, and settlement service attributes that payroll processes and third-party payment integrations rely upon when validating employee or third-party bank account data prior to disbursement.

From a data modeling perspective, the mined foreign key structure classifies this object as standalone at the heuristic level. This is a modeling suggestion rather than a definitive Data Vault assignment; because the table is self-contained and keyed by a single branch code with no evident parent-child foreign keys, it most naturally resembles a reference or lookup hub when translated into Data Vault terms, with descriptive attribute columns behaving like satellite data. The absence of documented inbound/outbound FK relationships reinforces its role as an independent reference master rather than a transactional link or dependent satellite.

Key Information Stored

The documented physical schema contains 23 columns and one unique index. The primary key, PAY_ZA_BRANCH_CDV_DETAIL_PK, is defined on BRANCH_CODE, which also serves as the sole business-key candidate (unique index). Because the surrogate and business keys coincide on BRANCH_CODE, BRANCH_CODE is the definitive identifier for each branch record.

• BRANCH_CODE — Primary key and business-key candidate; uniquely identifies each bank branch record.
• BANK_NAME and BRANCH_NAME — Human-readable identifiers for the banking institution and specific branch.
• STREAM_CODE — Classification code associated with the branch's settlement or processing stream.
• SSV_ALLOWED — Flag indicating whether the branch supports the South African Settlement Service (SSV) verification process.
• ONE_DAY_SS, TWO_DAY_SS, FIVE_DAY_SS — Settlement timing attributes for one-, two-, and five-day settlement cycles.
• STREET_ADDRESS_LINE_1, STREET_ADDRESS_LINE_2, PO_BOX_NUMBER, PO_BOX_POST_OFFICE, POSTAL_CODE — Physical and postal address attributes for the branch.
• TELEPHONE_NUMBER and DIALING_CODE — Contact information for the branch.
• TELEX1 and TELEX2 — Legacy telex identifiers retained for compatibility.
• DELETION_DATE — Indicates when a branch record was logically removed or deactivated.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard EBS WHO-column audit trail fields.

Common Use Cases and Queries

Typical scenarios include looking up valid branch codes during payroll bank account setup, validating SSV eligibility before disbursement runs, and generating branch reference reports for internal audit. The following query patterns are representative.

• Retrieve active branches for a given bank: SELECT branch_code, branch_name FROM pay_za_branch_cdv_details WHERE bank_name = :bank AND deletion_date IS NULL;
• Identify branches eligible for SSV verification: SELECT branch_code, branch_name, ssv_allowed FROM pay_za_branch_cdv_details WHERE ssv_allowed = 'Y';
• Extract settlement cycle attributes for reconciliation: SELECT branch_code, one_day_ss, two_day_ss, five_day_ss FROM pay_za_branch_cdv_details WHERE branch_code = :branch;
• Audit recently changed reference data: SELECT branch_code, last_updated_by, last_update_date FROM pay_za_branch_cdv_details WHERE last_update_date > SYSDATE - 30;

Reporting use cases center on maintaining a clean reference list for bank account validation and reconciling settlement timing attributes against payment batches.

Related Objects

The documented FK/PK data classifies PAY_ZA_BRANCH_CDV_DETAILS as standalone with no explicit foreign key links, so related objects are inferred functionally through the South African payroll bank account validation and disbursement chain rather than declared constraints. The most significant functionally associated objects include PAY_ZA_BANK_CDV_DETAILS (companion bank-level reference data), the external bank account and bank branch entities used by payroll payment methods (for example, HR external bank account and bank branch information), and the payroll payment/remittance and CDV processing references that consume BRANCH_CODE during account verification. Because join columns are not documented at the FK level, any join to dependent objects should be validated against the consuming payroll processes and the BRANCH_CODE key rather than assumed from declared constraints. Practitioners working with 12.2.2 should treat BRANCH_CODE as the stable join key across the ZA localization bank reference tables.