Results for “jgzz_fiscal_code”

4 results




Overview
Explore in AI Chat

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

Overview

CE_UPGA_BANK_REC is an audit table in the Oracle E-Business Suite Cash Management (CE) module, owned by the CE schema. Its documented purpose is to retain audit history for the records held in CE_UPG_BANK_REC, the upgrade staging table used during the bank and bank branch upgrade process that migrates legacy banking data into the standard Cash Management bank model. Because the parent table is a staging structure whose rows are transformed and consumed during the upgrade, CE_UPGA_BANK_REC preserves a snapshot of that data for traceability, troubleshooting, and post-upgrade verification.

The table is documented as VALID in ETRM 12.2.2, with a physical schema of 46 columns and the primary key CE_UPGA_BANK_REC_PK, defined solely on the CE_UPGRADE_ID column. The heuristic Data Vault classification mined from the foreign key structure is standalone. As a modeling suggestion, this indicates the table is not integrated into a hub-and-link topology within the documented schema; it functions as an independent satellite-style audit record keyed by its own upgrade identifier rather than participating in a broader Data Vault hub or link structure.

Key Information Stored

The surrogate primary key is CE_UPGRADE_ID, which uniquely identifies each audit row and anchors the CE_UPGA_BANK_REC_PK constraint. PARENT_UPGRADE_ID provides a candidate business linkage back to the parent upgrade record, and GROUP_ID supports grouping of related bank records across a single upgrade run. UPGRADE_STATUS records the processing state of the audited row, while PRIMARY_FLAG and SECONDARY_FLAG denote the role of a bank or branch within the upgrade hierarchy.

Financial and institutional identification is captured through BANK_ENTITY_TYPE, INSTITUTION_TYPE, BANK_OR_BRANCH_NUMBER, BANK_CODE, and BRANCH_CODE. Geographic and classification data reside in COUNTRY, BRANCH_TYPE, and RFC_CODE. Descriptive attributes include ORGANIZATION_NAME, ORGANIZATION_NAME_PHONETIC, KNOWN_AS, JGZZ_FISCAL_CODE, and MISSION_STATEMENT. Effective-dating is supported by START_DATE_ACTIVE and END_DATE_ACTIVE, with associated identifiers EFT_USER_NUM and CLEARING_HOUSE_ID. The standard Oracle WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE columns provide audit stamping and a flexible descriptive flexfield. Note that no unique indexes beyond the primary key are documented, so CE_UPGRADE_ID is the sole enforced uniqueness constraint.

Common Use Cases and Queries

Typical scenarios involve post-upgrade reconciliation, tracing individual banks or branches through the upgrade, and auditing changes captured relative to CE_UPG_BANK_REC.

  • Identify all audited rows for a given upgrade: SELECT * FROM ce.ce_upga_bank_rec WHERE ce_upgrade_id = :id;
  • Reconcile a record against its parent staging row using PARENT_UPGRADE_ID as the join key.
  • Report on upgrade outcomes by status: SELECT upgrade_status, COUNT(*) FROM ce.ce_upga_bank_rec GROUP BY upgrade_status;
  • Trace branch classification and country distribution for a completed upgrade run.
  • Audit timestamps to determine when specific bank records were processed.

Related Objects

The most significant relationships center on the parent staging table and the upgrade identifiers that connect them.

  • CE_UPG_BANK_REC — the source staging table this object audits; join on CE_UPGRADE_ID / PARENT_UPGRADE_ID.
  • CE_UPGRADE_ID — the primary key column linking audit rows to upgrade records.
  • PARENT_UPGRADE_ID — self-referencing candidate for hierarchical traceability.
  • Bank and branch master tables in Cash Management (for example CE_BANKS and CE_BANK_BRANCHES) that the upgrade ultimately populates.
  • Clearing and EFT references (CLEARING_HOUSE_ID, EFT_USER_NUM) that connect to Cash Management payment and clearing configuration.