Results for “transmission_program_id”

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

Overview

CE_UPG_AP_BANKS_TMP is a Cash Management (CE) staging table owned by the CE schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Per ETRM documentation, it is described as storing "AP purged bank branch details," indicating its role as an intermediate repository for bank and bank branch records extracted or migrated out of the Payables (AP) schema during upgrade or data conversion processing. It is not a runtime transactional table; rather, it supports the transition of legacy AP bank branch data into the Cash Management banking model introduced with the Oracle Payments (IBY) architecture.

The table carries 88 documented columns in the 12.2.2 physical schema, mirroring the wide column set of AP_BANK_BRANCHES, including descriptive, address, contact, EFT, and multi-language (ALT) attributes, plus DFF and GDF segments and concurrent program audit columns. From a Data Vault modeling perspective, the mined relationship structure is satellite-leaning: the table's primary key, BANK_BRANCH_ID, is also a foreign key to AP_BANK_BRANCHES, so it functions as a descriptive satellite keyed to the bank branch business key rather than as an independent hub or link.

Key Information Stored

The dominant column is BANK_BRANCH_ID, which serves as both the primary key (CE_UPG_AP_BANCHES_TMP_PK, implemented as CE_UPG_AP_BANKS_TMP_PK on BANK_BRANCH_ID) and the foreign key back to AP_BANK_BRANCHES. This dual role establishes it as the surrogate/join key carrying the branch identity from the source system, while BANK_NUM and BANK_NUMBER act as business-key candidates identifying the parent bank.

• BANK_BRANCH_ID — primary key and FK to AP_BANK_BRANCHES; the branch identity carried through the purge process.
• BANK_NAME, BANK_BRANCH_NAME — institution and branch names, with alternate-language equivalents BANK_NAME_ALT and BANK_BRANCH_NAME_ALT.
• ADDRESS_LINE1–ADDRESS_LINE4, CITY, STATE, PROVINCE, ZIP, COUNTRY, COUNTY — full postal address, supported by ADDRESS_STYLE and ADDRESS_LINES_ALT.
• AREA_CODE, PHONE, CONTACT_FIRST_NAME, CONTACT_MIDDLE_NAME, CONTACT_LAST_NAME, CONTACT_PREFIX, CONTACT_TITLE — branch contact details.
• BANK_NUM, BANK_NUMBER, EFT_SWIFT_CODE, EFT_USER_NUMBER, EDI_ID_NUMBER, RFC_IDENTIFIER, CLEARING_HOUSE_ID — clearing, EFT, and identification attributes needed for payment routing.
• INSTITUTION_TYPE, BANK_BRANCH_TYPE, ACTIVE_DATE, END_DATE — classification and effective-dating fields.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15, GLOBAL_ATTRIBUTE_CATEGORY, GLOBAL_ATTRIBUTE1–20 — descriptive and global flexfield segments.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard audit and concurrent-program context columns recording which request staged the row.

Common Use Cases and Queries

This table is queried principally during upgrade validation, reconciliation, and purge auditing. A typical reconciliation confirms that every purged AP branch has been staged before Cash Management records are created:

• Row-count comparison between CE_UPG_AP_BANKS_TMP and AP_BANK_BRANCHES to verify completeness of the purge extract.
• Identifying branches missing downstream CE/IBY bank or branch records by left-joining the temporary table against the target banking tables.
• Auditing which concurrent request produced a given set of rows via REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID.
• Data-quality reporting on address, SWIFT, or clearing-house values prior to conversion, using the ATTRIBUTE and GLOBAL_ATTRIBUTE columns to expose legacy flexfield content.
• Sample pattern: SELECT t.bank_branch_id, t.bank_name, t.bank_branch_name FROM ce.ce_upg_ap_banks_tmp t WHERE t.request_id = :request_id AND NOT EXISTS (SELECT 1 FROM ap.ap_bank_branches b WHERE b.bank_branch_id = t.bank_branch_id);

Related Objects

• AP_BANK_BRANCHES — the documented foreign-key parent; joined on BANK_BRANCH_ID, the source of the purged branch details.
• AP_BANKS — parent institution hosting the branch, related through BANK_NUM/BANK_NUMBER.
• CE_UPG_AP_BANKS_TMP_PK — the primary key constraint defined on BANK_BRANCH_ID.
• CE_BANK_BRANCHES / CE_BANKS — Cash Management banking tables that receive converted branch data.
• IBY_BANK_BRANCHES / IBY_BANKS — Oracle Payments banking entities in the 12.x architecture that consume migrated branch information.
• CE_UPG_AP_BANKS_TMP companion temporary tables used within the same upgrade/purge program set.
• FND_CONCURRENT_REQUESTS — the request framework identified by REQUEST_ID and PROGRAM_ID columns.