Results for “eft_user_num”

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

Overview

CE_UPG_CONT_POINT_REC is a Cash Management (CE) module table in the Oracle E-Business Suite, owned by the CE schema. It stores contact point information used during bank and bank branch upgrades, capturing the EDI, email, EFT, telephone, and fax contact details associated with banking entities. The table functions as a staging structure that supports upgrade processing for banking partner setup data, and its validity status indicates active use within the 12.1.1 and 12.2.2 code lines.

The table participates in the broader banking upgrade framework, in which external bank entity master data is migrated and reconciled across releases. Each record flattens contact channel attributes — EDI routing identifiers, EFT program references, SWIFT codes, telephone numbers, and email addresses — against a bank entity and a contact point type, keyed throughout by the upgrade run identifier.

Under the heuristic Data Vault classification mined from the foreign key structure, CE_UPG_CONT_POINT_REC is modeled as a standalone object. This suggests it functions as a satellite-style staging surface rather than a hub or link, because it does not expose outbound foreign key relationships to other tables. Consumers should treat it as an upgrade-scoped detail table rather than a master-data reference.

Key Information Stored

The documented physical schema contains 25 columns. The most significant are listed below, distinguishing identifying keys from attributes.

• Primary key: CE_UPG_CONT_POINT_REC_PK is a composite of BANK_ENTITY_TYPE, CONTACT_POINT_TYPE, and CE_UPGRADE_ID.
• Business key candidate: CE_UPG_CONT_POINT_REC_U1 covers CE_UPGRADE_ID, BANK_ENTITY_TYPE, CONTACT_POINT_TYPE, and PHONE_LINE_TYPE, indicating that a phone line type discriminator further subdivides records per contact point.
• CE_UPGRADE_ID: Identifies the specific upgrade run that produced the contact point record.
• UPGRADE_STATUS: Tracks processing state of the row within the upgrade cycle.
• BANK_ENTITY_TYPE / CONTACT_POINT_TYPE / PHONE_LINE_TYPE: Classify the banking entity, the contact channel (EDI, email, EFT, phone, fax), and the specific phone line.
• OWNER_TABLE_NAME / OWNER_TABLE_ID: Reference the source record that owns the contact point, supporting traceability back to the originating banking setup.
• EDI_ID_NUMBER / EDI_TP_HEADER_ID / EDI_ECE_TP_LOCATION_CODE: Store EDI trading partner routing and location identifiers.
• EFT_TRANSMISSION_PROGRAM_ID / EFT_PRINTING_PROGRAM_ID / EFT_SWIFT_CODE / EFT_USER_NUM: Hold EFT payment routing, program, and SWIFT packaging details.
• PHONE_AREA_CODE / PHONE_NUMBER / ORG_PRIMARY_PHONE_FLAG / EMAIL_ADDRESS: Capture telephony and electronic contact data, with the flag denoting the organization's primary number.
• CONTACT_POINT_ID: Surrogate reference to the contact point entity.
• Audit columns: CREATION_DATE, CREATED_BY, CREATED_BY_MODULE, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard multi-user auditability.

Common Use Cases and Queries

Typical usage centers on banking partner upgrade diagnostics, contact channel reporting, and validation of EDI/EFT routing data prior to cutover.

• Enumerate contact points by upgrade run and entity type:

SELECT bank_entity_type, contact_point_type, phone_line_type,
       edi_id_number, eft_swift_code, email_address
FROM   ce.ce_upg_cont_point_rec
WHERE  ce_upgrade_id = :p_upgrade_id
  AND  bank_entity_type = :p_entity_type;

• Identify EFT-enabled bank entities with transmission programs defined:

SELECT owner_table_id, eft_transmission_program_id, eft_printing_program_id
FROM   ce.ce_upg_cont_point_rec
WHERE  contact_point_type = 'EFT'
  AND  eft_transmission_program_id IS NOT NULL;

• Validate primary contact phone numbers per organization:

SELECT org_primary_phone_flag, phone_area_code, phone_number
FROM   ce.ce_upg_cont_point_rec
WHERE  bank_entity_type = :p_entity_type
  AND  contact_point_type = 'PHONE';

Because the table is upgrade-scoped and standalone, reports should always filter by CE_UPGRADE_ID to avoid conflating records from separate migration cycles.

Related Objects

The mined relationship data classifies CE_UPG_CONT_POINT_REC as standalone, meaning no outbound foreign keys are documented. As a result, related objects must be inferred from shared columns rather than declared constraints.

• CE_UPG_BANK_ENTITY (or equivalent banking upgrade parent): Joins via BANK_ENTITY_TYPE and CE_UPGRADE_ID to resolve the owning bank entity.
• CE_BANK_BRANCHES: Linked through OWNER_TABLE_NAME and OWNER_TABLE_ID when the owner is a bank branch record.
• CE_BANK_ACCOUNTS: Referenced where contact points attach to bank account EFT setups.
• IBY_EXT_BANK_ACCOUNTS / IBY_PAYEE_INSTRS: Payment-side counterparts used to reconcile upgraded EFT and EDI contact data.
• AP_BANK_BRANCHES: Payables bank branch definition used when the upgrade targets AP banking entities.
• HR_LOCATIONS / PER_PHONES: Potential source objects for phone and fax attributes carried into the upgrade staging table.
• CE_UPG_* companion tables: Sibling upgrade staging tables sharing CE_UPGRADE_ID for holistic upgrade reporting.

These relationships are best validated at implementation time, since the metadata documents a standalone classification rather than enforced referential integrity.