Results for “cst_reconciliation_codes”

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

Overview

CST_RECONCILIATION_CODES is an Oracle E-Business Suite view owned by the APPS schema and registered under the Bills of Material (BOM) product family. Despite its name, the object does not perform reconciliation itself; it functions as a filtered lookup repository that exposes the accrual-related lookup codes used by Oracle's cost reconciliation and receiving accrual reporting processes. The view is delivered with a status of VALID in both EBS 12.1.1 and 12.2.2 and is documented as "Holds Accrual Lookups."

In practice, CST_RECONCILIATION_CODES provides report and concurrent program developers with a single, pre-filtered source of the code values required to interpret accrual transactions, receiving transaction types, accrual write-off actions, and the ordering criteria applied to certain Supply Chain Financial Orchestration (SRS) accrual extracts. Because it filters the shared PO_LOOKUP_CODES repository rather than maintaining its own data, the view remains synchronized automatically with any lookup maintenance performed through the standard application lookup maintenance forms.

Underlying Base Objects

The documented metadata identifies two referenced objects. The primary source is PO_LOOKUP_CODES, itself a view in the APPS schema that presents general-purpose lookup code definitions. The second is the FND_GLOBAL package, which is referenced within the view definition (typically for session context such as ORG_ID or USER_ID) rather than contributing business rows.

Functionally, CST_RECONCILIATION_CODES is a restricted projection of PO_LOOKUP_CODES. Its defining predicate retains rows where LOOKUP_TYPE equals 'ACCRUAL TYPE', or where LOOKUP_TYPE is one of 'RCV TRANSACTION TYPE', 'ACCRUAL WRITE-OFF ACTION', or 'SRS ACCRUAL ORDER BY'. All other lookup types present in PO_LOOKUP_CODES are excluded. Because no aggregation, join, or grouping is applied, the cardinality of the view matches the union of rows for those four lookup types in the underlying lookup repository.

Key Columns

• LOOKUP_CODE — The functional code value stored for the lookup, such as a specific accrual type or write-off action. This is the value written into transactional columns and compared during reporting.
• LOOKUP_TYPE — Identifies which of the four accrual-related lookup categories the row belongs to. This column is the primary means of segmenting the view's contents and is the basis of the view's filter predicate.
• DISPLAYED_FIELD — The user-facing or displayed value associated with the code, suitable for presentation on reports where the raw LOOKUP_CODE would be unintelligible to business users.
• DESCRIPTION — The descriptive text maintained against the lookup code, providing additional business context for the value.

Note that the view does not expose enablement flags, date ranges, or language attributes; consumers requiring only currently enabled lookups or multi-language descriptions must join to the broader lookup infrastructure.

Common Use Cases and Queries

The view is most frequently used to populate parameter lists and report headers in accrual reconciliation reporting. A typical query returns all codes for a single lookup type:

• Reporting accrual types: SELECT LOOKUP_CODE, DISPLAYED_FIELD, DESCRIPTION FROM CST_RECONCILIATION_CODES WHERE LOOKUP_TYPE = 'ACCRUAL TYPE';
• Receiving transaction types: SELECT LOOKUP_CODE, DISPLAYED_FIELD FROM CST_RECONCILIATION_CODES WHERE LOOKUP_TYPE = 'RCV TRANSACTION TYPE' ORDER BY LOOKUP_CODE;
• Write-off actions: SELECT LOOKUP_CODE, DESCRIPTION FROM CST_RECONCILIATION_CODES WHERE LOOKUP_TYPE = 'ACCRUAL WRITE-OFF ACTION';
• Full inventory of supported codes: SELECT LOOKUP_TYPE, LOOKUP_CODE, DISPLAYED_FIELD FROM CST_RECONCILIATION_CODES ORDER BY LOOKUP_TYPE, LOOKUP_CODE;

Because the view is a thin, read-only projection, it presents no maintenance risk and is safe to reference from custom reports, BI Publisher data templates, and integration extracts. Custom code should not insert into or update this view, as lookup maintenance must be performed through the standard lookup maintenance forms for the applicable lookup type.