Results for “ce_transaction_codes_v”

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

Overview

CE_TRANSACTION_CODES_V is an APPS-owned view in the Cash Management (CE) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It is documented in ETRM as "Retrofitted," indicating that the definition was carried forward across release boundaries with adjustments for newer underlying APIs and multi-organization constructs. The view presents bank transaction codes — the configurable categories a bank account uses to classify statement lines for reconciliation — joined to descriptive context such as the owning bank account, branch, bank, currency, receipt method, receivables activity, and payroll payment format. In effect, it is a denormalized, human-readable projection of CE_TRANSACTION_CODES with decoded lookup meanings, intended for reporting, inquiry, and integration consumers that cannot or should not resolve the many foreign keys themselves.

The view is read-oriented. The primary configuration table remains CE_TRANSACTION_CODES (exposed here as a synonym); this view layers on decoded meanings from CE_LOOKUPS, FND_LOOKUPS, and HR_LOOKUPS so that columns such as TYPE, CREATE_MISC_TRX_FLAG, RECONCILE_FLAG, and the payroll matching order appear as displayable text rather than codes.

Underlying Base Objects

The documented base objects span several products. Cash Management supplies CE_BANK_ACCOUNTS_V, CE_BANK_BRANCHES_V, CE_LOOKUPS, and CE_TRANSACTION_CODES. Receivables supplies AR_RECEIVABLES_TRX_ALL and AR_RECEIPT_METHODS, resolving the receivables activity and receipt method tied to a code. Payroll supplies PAY_PAYMENT_TYPES and PAY_PAYMENT_TYPES_TL for payroll payment formats. Lookup decoding draws on FND_LOOKUPS and HR_LOOKUPS.

Several packages appear as referenced objects, which is significant: FND_GLOBAL, FND_PROFILE, FND_ACCESS_CONTROL_UTIL, MO_GLOBAL, HR_API, and XTR_USER_ACCESS. Their presence indicates that the view applies function security, profile-driven access control, and possibly multi-org (MO) filtering or HR security at runtime. This has practical consequences — query performance and row visibility can vary by responsibility and session context, and direct SQL outside the application may return a different set of rows than an EBS form.

Key Columns

• TRANSACTION_CODE_ID — primary key of the underlying transaction code record.
• BANK_ACCOUNT_ID, BANK_ACCOUNT_NAME, BANK_ACCOUNT_NUM, BANK_ACCOUNT_CURRENCY_CODE — the owning account and its currency.
• BANK_NAME, BANK_BRANCH_NAME — bank and branch identification.
• TYPE / TYPE_DSP — the transaction code type code and its decoded meaning.
• TRX_CODE, DESCRIPTION — the user-defined code and its description.
• CREATE_MISC_TRX_FLAG / CREATE_MISC_TRX_FLAG_DSP — whether a miscellaneous transaction is created, with decoded display.
• RECONCILE_FLAG / RECONCILE_FLAG_DSP — reconciliation behavior indicator and decoded value.
• FLOAT_DAYS — float period applied to the code.
• MATCHING_AGAINST — the field the transaction is matched against during reconciliation (for example, a specific reference). This is the attribute users most often search for; note the view also exposes PAYROLL_MATCHING_ODER (decoded as L4.MEANING), which governs payroll matching order.
• RECEIVABLES_ACTIVITY, RECEIVABLES_TRX_ID — linked Receivables activity.
• PAYMENT_METHOD, RECEIPT_METHOD_ID — linked receipt method.
• PAYROLL_PAYMENT_FORMAT_ID, PAYROLL_PAYMENT_FORMAT_DSP — payroll payment format linkage.
• CORRECTION_METHOD, START_DATE, END_DATE, RECONCILIATION_SEQUENCE, REQUEST_ID — reconciliation sequencing, validity window, and the concurrent request that created or updated the record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard flexfield-enabled descriptive columns.
• ROW_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns, with ROW_ID supporting updatable-view semantics.

Common Use Cases and Queries

Typical uses include reconciliation setup reporting, auditing which transaction codes exist per bank account, validating matching and float configuration before go-live, and feeding downstream cash-position or integration extracts.

• List all codes for a specific account: SELECT TRX_CODE, TYPE_DSP, MATCHING_AGAINST, RECONCILE_FLAG_DSP FROM CE_TRANSACTION_CODES_V WHERE BANK_ACCOUNT_ID = :p_account_id ORDER BY TRX_CODE;
• Find codes matched against a particular reference: SELECT BANK_ACCOUNT_NAME, TRX_CODE, MATCHING_AGAINST FROM CE_TRANSACTION_CODES_V WHERE MATCHING_AGAINST = :p_value;
• Audit receivables and receipt method linkage: SELECT BANK_ACCOUNT_NUM, TRX_CODE, RECEIVABLES_ACTIVITY, PAYMENT_METHOD FROM CE_TRANSACTION_CODES_V WHERE BANK_ACCOUNT_ID = :p_account_id;
• Review audit and validity windows: SELECT TRX_CODE, START_DATE, END_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM CE_TRANSACTION_CODES_V WHERE SYSDATE BETWEEN NVL(START_DATE, SYSDATE) AND NVL(END_DATE, SYSDATE + 1);

Because the definition references FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS, results are subject to session context and function security; callers should initialize the EBS environment (for example, fnd_global.apps_initialize) before querying to obtain consistent, responsibility-aware results.