Results for “cat_segment1”

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

Overview

FA_BUDGET_INTERFACE is a standard Oracle Assets (OFA) interface table in the FA schema, present and valid in both EBS 12.1.1 and 12.2.2. It serves as the staging area for capital budget information that is uploaded into Oracle Assets. Rather than posting budget amounts directly, external systems, feeder programs, or spreadsheet loaders populate this table and then invoke the Oracle Assets budget upload process, which validates the rows and moves them into the permanent budget tables. The table stores fifty columns: a book identifier, category segment columns, twelve period amount columns, and a substantial set of accounting flexfield segment columns (ACCT_SEGMENT1 through ACCT_SEGMENT30).

From a Data Vault modeling perspective, the heuristic classification is standalone; the metadata does not expose a foreign key relationship to another table. In practice, it behaves as a raw staging satellite keyed by a composite natural business key rather than a surrogate identifier. There is no sequence-generated surrogate key; the primary key is entirely composed of business attributes.

Key Information Stored

The primary key constraint FA_BUDGET_INTERFACE_PK is defined across eight columns: BOOK_TYPE_CODE, CAT_SEGMENT1, CAT_SEGMENT2, CAT_SEGMENT3, CAT_SEGMENT4, CAT_SEGMENT5, CAT_SEGMENT6, and CAT_SEGMENT7. This composite key uniquely identifies one budget row per asset book and per asset category flexfield combination. Because the key is built from real business attributes rather than a generated number, it functions as a natural business key — there is no separate surrogate primary key column in the documented schema.

The most significant columns are:

• BOOK_TYPE_CODE — identifies the target asset book (for example, a corporate or tax book); part of the primary key.
• CAT_SEGMENT1 through CAT_SEGMENT7 — the asset category flexfield segments defining which category the budget applies to; all seven are part of the primary key.
• PERIOD1_AMOUNT through PERIOD12_AMOUNT — the twelve monthly budget amounts for the fiscal year, holding the capital budget figure for each period.
• ACCT_SEGMENT1 through ACCT_SEGMENT30 — the accounting flexfield segments that determine the general ledger account distribution for the budget entry. Only the segments relevant to the chart of accounts are populated; the remainder are left null.

Common Use Cases and Queries

The principal use case is bulk loading capital budgets. A feeder process inserts rows specifying book, category, account distribution, and the twelve period amounts, then the Oracle Assets budget upload is executed to validate and transfer the data. Typical supporting queries include reconciling staged amounts against the permanent budget tables, detecting duplicate or conflicting rows on the primary key, and confirming that category and account combinations are complete before upload.

A representative query totals budgeted amounts by book and category:

• SELECT book_type_code, cat_segment1, cat_segment2, SUM(period1_amount + period2_amount + ... + period12_amount) total_budget FROM fa_budget_interface GROUP BY book_type_code, cat_segment1, cat_segment2;
• Duplicate detection: SELECT book_type_code, cat_segment1, ... , COUNT(*) FROM fa_budget_interface GROUP BY book_type_code, cat_segment1, ... HAVING COUNT(*) > 1;
• Null-check for account distribution: SELECT * FROM fa_budget_interface WHERE acct_segment1 IS NULL;

Related Objects

The metadata classifies the table as standalone, so no explicit foreign keys are documented. Conceptually, the columns join to the following significant objects:

• FA_BOOK_CONTROLS — joined on BOOK_TYPE_CODE to validate the target book.
• FA_CATEGORIES / FA_CATEGORY_BOOKS — joined on CAT_SEGMENT columns to resolve the asset category.
• FA_BUDGETS — the permanent budget table that receives validated rows after upload.
• FA_BUDGET_INTERFACE — loaded via the Oracle Assets budget upload concurrent program / ADI (Application Desktop Integrator) interface.
• GL_CODE_COMBINATIONS — joined on the ACCT_SEGMENT columns to validate accounting flexfield combinations.

Because the interface is a staging object, dependent processing revolves around the upload program rather than declarative constraints, and rows are typically purged after successful transfer to the production budget tables.