Search Results fnd_application_u1

Overview

APPLSYS.FND_APPLICATION is the Oracle Application Object Library registration table that defines every application known to an E-Business Suite instance. Each row represents a registered Oracle EBS product — such as General Ledger, Payables, Order Management, or a custom application — and establishes the identity (numeric identifier and short name) by which that product is referenced throughout the schema. The table resides in the APPS_TS_SEED tablespace, reflecting its role as seeded, installation-level reference data rather than transactional data, and is backed by the FND design data object FND.FND_APPLICATION.

Because nearly every EBS framework table (responsibilities, concurrent programs, profile options, flexfields, and lookups) carries an application identifier, FND_APPLICATION functions as a foundational reference hub. Under the heuristic Data Vault classification provided in the relationship metadata, it is modeled as a hub: a stable, uniquely keyed list of business entities (applications) from which numerous dependent tables draw their foreign keys. This classification is a modeling suggestion derived from the foreign-key topology, not an Oracle-imposed constraint.

The object is documented with a status of VALID and is present in both Oracle EBS 12.1.1 and 12.2.2. In 12.2.2 the physical schema includes an additional ZD_EDITION_NAME column, reflecting the editioning infrastructure introduced with Online Patching.

Key Information Stored

The table contains 10 documented columns. The most significant are:

• APPLICATION_ID (NUMBER) — The surrogate primary key and application identifier. It is the value propagated as a foreign key into virtually every framework table in the EBS data model.
• APPLICATION_SHORT_NAME (VARCHAR2, 50) — The business-key short name (for example, SQLGL, AP, AR, INV) used pervasively in profile option values, FNDLOAD configuration files, and API calls instead of the numeric ID.
• BASEPATH (VARCHAR2, 20) — Stores the variable name of the TOP directory for the application (for example, the path variable that resolves to the product's installation directory), supporting file and report path resolution.
• PRODUCT_CODE (VARCHAR2, 50) — The online help base application short name, used when help content is shared with another application.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide audit and concurrency tracking for each row.
• ZD_EDITION_NAME — Present in the 12.2.2 schema, this column participates in editioning and is included in both unique indexes.

Two unique indexes constitute the business-key candidates: FND_APPLICATION_U1 on (APPLICATION_ID, ZD_EDITION_NAME) and FND_APPLICATION_U3 on (APPLICATION_SHORT_NAME, ZD_EDITION_NAME). The separate primary key constraint FND_APPLICATION_PK is defined on APPLICATION_ID. The short name is therefore the principal alternate key, enforcing uniqueness of product identity across the instance.

Common Use Cases and Queries

The most frequent use of this table is resolving an application identifier to its human-readable short name, or vice versa, and joining that value to other framework tables. A canonical query lists all registered applications:

• SELECT APPLICATION_ID, APPLICATION_SHORT_NAME, BASEPATH, PRODUCT_CODE FROM APPLSYS.FND_APPLICATION ORDER BY APPLICATION_SHORT_NAME;
• Resolving responsibilities to applications: join FND_RESPONSIBILITY.APPLICATION_ID = FND_APPLICATION.APPLICATION_ID to report which application each responsibility belongs to.
• Auditing concurrent programs by product: join FND_CONCURRENT_PROGRAMS.APPLICATION_ID to FND_APPLICATION to group scheduled programs by owning application.
• Analyzing profile option values scoped at the application level, using FND_PROFILE_OPTION_VALUES.LEVEL_VALUE = FND_APPLICATION.APPLICATION_ID where LEVEL_ID identifies the application level.
• Identifying custom or third-party registrations by filtering out known Oracle short names, useful during upgrades and impact assessments.

Reports frequently substitute APPLICATION_SHORT_NAME for the numeric identifier to produce readable output, since the short name is stable across environments while numeric IDs may differ.

Related Objects

FND_APPLICATION does not reference any other database object; it is a pure parent. It is referenced by a very large number of tables, of which the most significant include:

• FND_APPLICATION_TL — The translated (language) table, joined on APPLICATION_ID, holding the application display name per language.
• FND_RESPONSIBILITY — Joins on APPLICATION_ID; every responsibility belongs to an application.
• FND_CONCURRENT_PROGRAMS and FND_EXECUTABLES — Join on APPLICATION_ID; concurrent programs and executables are owned by an application.
• FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES — Join on APPLICATION_ID (and LEVEL_VALUE) to scope profile settings by application.
• FND_AUDIT_SCHEMAS and FND_TABLES — Join on APPLICATION_ID for audit and table registration.
• FND_PRODUCT_INSTALLATIONS and FND_MODULE_INSTALLATIONS — Join on APPLICATION_ID to record installed products.
• ALR_ORACLE_MAIL_ACCOUNTS and ALR_DISTRIBUTION_LISTS — Join on APPLICATION_ID for the Oracle Alert mail framework.
• FND_LOOKUP_TYPES — References FND_APPLICATION through VIEW_APPLICATION_ID.

Additional product-level consumers — including OZF/AMS marketing tables, JTF CRM tables, IBY payments, and ZX tax tables — carry APPLICATION_ID or APPLICATION_SHORT_NAME foreign keys to this hub, confirming its central position in the EBS reference model.