Results for “ce_ap_pm_doc_categories”

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

Overview

CE_AP_PM_DOC_CATEGORIES is a Cash Management (CE) application table that stores the payment document categories and payment methods associated with specific bank account uses. It functions as a configuration bridge between a bank account use (BANK_ACCT_USE_ID) and the Payment Management operations performed against that account, defining which payment methods (for example, check, wire, or electronic) and which payment document categories (for example, check stock or electronic payment formats) are valid for a particular account use. The table is owned by the CE schema and is marked VALID in the EBS 12.1.1 and 12.2.2 environments.

From a Data Vault modeling perspective, the documented relationship heuristic classifies this table as standalone. It has no mined foreign key dependencies beyond its own primary key, so it is best modeled as a hub-like reference entity rather than a link or satellite. This classification is a modeling suggestion based on the FK structure documented in ETRM; the table is treated as a static reference of payment configuration rather than as a transactional fact.

Key Information Stored

The table contains ten documented columns. The surrogate primary key AP_PM_DOC_CATEGORY_ID, enforced by the unique index CE_AP_PM_DOC_CATEGORIES_U1, uniquely identifies each configuration row. The remaining substantive attributes define the business meaning of that row:

• AP_PM_DOC_CATEGORY_ID — Surrogate primary key; system-generated unique identifier for each payment document category record.
• BANK_ACCT_USE_ID — The bank account use (the account and its assigned use) to which this payment method and document category configuration applies.
• PAYMENT_METHOD_CODE — The payment method code assigned to the bank account use (for example, check or electronic).
• PAYMENT_DOC_CATEGORY — The payment document category associated with the bank account use and payment method.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Forms/ADF framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns that capture audit and row-level change history.

The metadata does not document any alternate unique index, so the business-key candidate is effectively the combination of BANK_ACCT_USE_ID, PAYMENT_METHOD_CODE, and PAYMENT_DOC_CATEGORY rather than a single natural key column.

Common Use Cases and Queries

This table is typically queried during Payment Management setup and when diagnosing why a particular payment method or document category is unavailable for a bank account. Common reporting scenarios include listing all document categories configured for a given bank account use, validating that the intended payment method is set up, and reconciling payment configuration between environments.

A typical join pattern retrieves the account use context from CE_BANK_ACCT_USES_ALL and the payment configuration from this table:

• SELECT d.PAYMENT_METHOD_CODE, d.PAYMENT_DOC_CATEGORY, u.BANK_ACCOUNT_ID, u.ACCOUNT_USE_CODE FROM CE_AP_PM_DOC_CATEGORIES d, CE_BANK_ACCT_USES_ALL u WHERE d.BANK_ACCT_USE_ID = u.BANK_ACCT_USE_ID;
• Filter by d.BANK_ACCT_USE_ID to return the payment methods configured for a single account use.
• Filter by d.PAYMENT_METHOD_CODE or d.PAYMENT_DOC_CATEGORY to find all account uses sharing a category or method.
• Order by d.CREATION_DATE or d.LAST_UPDATE_DATE to audit recent setup changes using the WHO columns.

Because the FK to the bank account use is not enforced as a documented constraint, join results should be validated for orphaned rows where BANK_ACCT_USE_ID no longer exists in the account uses table.

Related Objects

The table is standalone under the ETRM FK heuristic and has no documented foreign keys pointing elsewhere. Its most significant related objects are joined through the BANK_ACCT_USE_ID business column:

• CE_BANK_ACCT_USES_ALL — Master view of bank account uses; joined on BANK_ACCT_USE_ID.
• CE_BANK_ACCOUNTS — Bank account definitions; reached indirectly through the account use identifier.
• CE_PAYMENT_METHODS — Reference of payment method codes referenced by PAYMENT_METHOD_CODE.
• CE_PAYMENT_DOCUMENTS — Payment document definitions cross-referenced by PAYMENT_DOC_CATEGORY.
• IBY_PAYMENT_METHODS and IBY_PAYMENT_PROFILES — Payments-wide counterparts that share payment method and profile semantics.
• AP_PAYMENT_SCHEDULES_ALL / AP_CHECKS_ALL — Payment execution tables whose document categories align with the configuration stored here.

These relationships are inferred from the business columns documented in ETRM rather than from enforced database constraints, so consumers should treat them as semantic joins to be validated at the application level.