Results for “eft_printing_program_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CE_UPGA_CONT_POINT_REC is an audit (shadow) table owned by the CE schema within the Oracle Cash Management module. It preserves the state of records held in the working upgrade table CE_UPG_CONT_POINT_REC, capturing rows as they are processed by the Cash Management upgrade utilities during release-to-release migration, most commonly in the path from 11i to Release 12.1.1 or 12.1.1 to 12.2.2. Because bank, branch, and account contact information was restructured in Release 12 with the introduction of the bank entity model, contact point data migrated into the participating bank tables requires reconciliation and traceability; this table supplies that trail.
The unit of uniqueness is defined by the composite primary key CE_UPGA_CONT_POINT_REC_PK, whose columns are CE_UPGRADE_ID, BANK_ENTITY_TYPE, CONTACT_POINT_TYPE, and PHONE_LINE_TYPE. Under heuristic Data Vault classification, this standalone table is best modeled as a satellite: the composite key carries the descriptive context attributes and the row-level audit timestamp columns, without foreign key dependencies to other hubs or links in the documented schema. Customers performing a technical upgrade can use it to reconstruct pre-migration values or to diagnose contact point records that were rejected or partially processed.
Key Information Stored
- CE_UPGRADE_ID — Identifier of the specific upgrade batch or run that produced the audit row; part of the primary key.
- UPGRADE_STATUS — Outcome or processing state of the associated contact point record as handled by the upgrade program.
- BANK_ENTITY_TYPE — Classification of the bank-related entity (for example bank, branch, or account) to which the contact point belongs; the column the user searched on and a component of the composite key.
- CONTACT_POINT_TYPE and PHONE_LINE_TYPE — Together with BANK_ENTITY_TYPE, they form the business-key portion of the primary key that distinguishes the contact point role and telephony line classification.
- OWNER_TABLE_NAME and OWNER_TABLE_ID — Identify the source object and row from which the contact point was migrated, providing the critical link back to the bank, branch, or account record.
- CREATED_BY_MODULE — The module context in which the contact point originated, useful for filtering legacy versus target records.
- EDI_ID_NUMBER, EDI_TP_HEADER_ID, EDI_ECE_TP_LOCATION_CODE — EDI trading partner identifiers associated with electronic payment contact data.
- EFT_TRANSMISSION_PROGRAM_ID, EFT_PRINTING_PROGRAM_ID, EFT_SWIFT_CODE — Payment formatting and routing values used for electronic funds transfers, including SWIFT identification.
- PHONE_AREA_CODE, PHONE_NUMBER, ORG_PRIMARY_PHONE_FLAG, EMAIL_ADDRESS — Contact detail and flag indicating the primary phone for the organization.
- CONTACT_POINT_ID — Target identifier of the contact point record created or updated by the upgrade.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording who created and last touched the row.
Common Use Cases and Queries
Typical uses include validating that all contact points from the legacy bank entity model were converted, auditing records where UPGRADE_STATUS indicates failure or incomplete processing, and reconciling legacy phone and email data against the target bank tables. A common pattern is to group unresolved rows by the bank entity classification and upgrade batch, for example selecting BANK_ENTITY_TYPE, CONTACT_POINT_TYPE, and a count of rows from CE_UPGA_CONT_POINT_REC where UPGRADE_STATUS is not successful, grouped by CE_UPGRADE_ID. Another frequent query joins on OWNER_TABLE_NAME and OWNER_TABLE_ID to trace an audited contact point back to its source record, or filters by EFT_SWIFT_CODE or EFT_TRANSMISSION_PROGRAM_ID to verify that electronic payment formatting information survived the upgrade intact. Reporting extracts frequently target PHONE_NUMBER and EMAIL_ADDRESS for contact data quality review.
Related Objects
- CE_UPG_CONT_POINT_REC — The working upgrade table this object audits; matched by CE_UPGRADE_ID and the shared contact point key columns.
- CE_UPGA_BANK_ACCT_REC — Companion audit table for bank account migration, joined by CE_UPGRADE_ID.
- CE_UPG_BANK_ACCT_REC — Working upgrade records for bank accounts that share the same CE_UPGRADE_ID batch context.
- CE_UPGA_BANK_REC and CE_UPG_BANK_REC — Bank-level upgrade and audit records, correlated through CE_UPGRADE_ID and bank entity identifiers.
- HZ_CONTACT_POINTS — Target contact point table referenced via CONTACT_POINT_ID for reconciliation.
- IBY_BANKACCT_CONTACTS and related IBY payment tables — Consume migrated bank account contact data post-upgrade.
- FND_ID_FLEX_STRUCTURES — Referenced indirectly for EDI/EFT identifier contexts captured by the audit row.
-
This table is an audit table of CE_UPG_CONT_POINT_REC
-
This table stores contact points information for bank EDI, email, bank branch EFT, contact phone and fax
-
This table stores contact points information for bank EDI, email, bank branch EFT, contact phone and fax
-
This table is an audit table of CE_UPG_CONT_POINT_REC
-
TCA import table for HZ_CONTACT_POINTS
-
Electronic methods of communicating with parties
-
Electronic methods of communicating with parties
-
TCA import table for HZ_CONTACT_POINTS
-
VIEW: AR.HZ_CONTACT_POINTS# 12.2.2
-
VIEW: AR.HZ_CONTACT_POINTS# 12.2.2
-
TYPE: APPS.HZ_EFT_CP_BO 12.1.1
-
TYPE: APPS.HZ_EFT_CP_BO 12.2.2
-
TYPE BODY: APPS.HZ_EFT_CP_BO 12.1.1
-
TYPE BODY: APPS.HZ_EFT_CP_BO 12.2.2
-
TABLE: AR.HZ_CONTACT_POINTS 12.2.2
-
TABLE: AR.HZ_CONTACT_POINTS 12.1.1