Results for “purpose_default_code”
36 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FND_BUSINESS_PURPOSES_B is a foundational configuration table within the Oracle E-Business Suite Application Object Library (FND) product group, owned by the APPLSYS schema. It stores the seeded and user-defined business purposes that drive function security, menu assignment, and data access behavior across the EBS application stack. Business purposes are the mechanism by which Oracle classifies the functional intent of an application entity, most notably the segregation between system administration functions and normal transactional or inquiry functions performed by end users.
Under a heuristic Data Vault classification, FND_BUSINESS_PURPOSES_B behaves as a standalone reference entity — effectively a hub-like table with no dependent satellite structure of its own. Because it does not carry a natural parent foreign key relationship in the documented schema, it is best modeled as an independent reference or lookup hub rather than a link or satellite. The table is keyed at the business level by PURPOSE_CODE, the sole unique index candidate (FND_BUSINESS_PURPOSES_B_U1), and is further constrained by SECURITY_GROUP_ID as a foreign key to FND_SECURITY_GROUPS, which scopes purpose definitions across security group partitions.
Key Information Stored
The table defines 27 documented columns. The most functionally significant are listed below.
- PURPOSE_CODE — the business-key identifier, uniquely indexed by FND_BUSINESS_PURPOSES_B_U1. This is the value applications and queries reference when determining the intended use of a function or menu entry.
- APPLICATION_ID — the owning application, mapping the purpose to a specific EBS product within the FND application registry.
- SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; partitions business purpose definitions by security group.
- SEEDED_FLAG — distinguishes Oracle-delivered seeded purposes from customer-defined records. Seeded rows are generally protected from modification.
- PURPOSE_DEFAULT_CODE — identifies the default purpose assigned when no explicit purpose is specified, supporting fallback logic in function and menu configuration.
- OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent DML control, referencing the table's transactional integrity model.
- CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN — the standard EBS who-columns and audit trail columns, populated automatically by the application framework.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) segment columns, available for customer extension without schema change.
No separate surrogate numeric primary key is documented beyond PURPOSE_CODE; the unique index on PURPOSE_CODE serves as the effective business identifier. The combination of PURPOSE_CODE and SECURITY_GROUP_ID governs scoping.
Common Use Cases and Queries
FND_BUSINESS_PURPOSES_B is queried most commonly when resolving why a function or menu entry behaves as administrative versus transactional, and when auditing the security group partitioning of purpose definitions. A typical pattern lists all purposes for a given application and security group:
SELECT p.PURPOSE_CODE, p.APPLICATION_ID, p.SEEDED_FLAG, p.SECURITY_GROUP_ID FROM FND_BUSINESS_PURPOSES_B p WHERE p.APPLICATION_ID = :app_id AND p.SECURITY_GROUP_ID = :grp_id;SELECT p.PURPOSE_CODE, p.PURPOSE_DEFAULT_CODE FROM FND_BUSINESS_PURPOSES_B p WHERE p.SEEDED_FLAG = 'Y' ORDER BY p.PURPOSE_CODE;SELECT p.* FROM FND_BUSINESS_PURPOSES_B p WHERE p.PURPOSE_CODE = 'ADMINISTRATION';
Additional reporting scenarios include isolating all customer-extended DFF attributes for controlled purposes (ATTRIBUTE_CATEGORY IS NOT NULL), auditing seeded versus custom records, and reconciling default purpose assignments across security groups. Because the table is small and stable, it is frequently joined to security group membership and function definition views to produce access reports.
Related Objects
The principal documented relationship is the foreign key from SECURITY_GROUP_ID to FND_SECURITY_GROUPS, which links purpose definitions to their security partition context. This join is the primary path for access-control and provisioning reporting.
- FND_SECURITY_GROUPS — referenced via FND_BUSINESS_PURPOSES_B.SECURITY_GROUP_ID; defines the security grouping under which purposes are scoped.
Beyond the documented FK, FND_BUSINESS_PURPOSES_B participates indirectly with function security and menu tables such as FND_FORM_FUNCTIONS, FND_MENUS, and FND_MENU_ENTRIES, and with the application registry in FND_APPLICATION, all of which reference purpose codes during access evaluation. The purposes are typically administered through the System Administrator responsibility against the Security Groups and Business Purposes setup forms, which write to this table through the standard FND table-handler APIs rather than direct DML.
-
APPS.FND_BUSINESS_PURPOSES_VL·↳ FND_BUSINESS_PURPOSES_B·↳ FND_BUSINESS_PURPOSES_TL·Explore FND module →
-
APPS.FND_BUSINESS_PURPOSES_VL·↳ FND_BUSINESS_PURPOSES_B·↳ FND_BUSINESS_PURPOSES_TL·Explore FND module →
-
eTRM - FND Tables and Views 12.2.2
No longer used
-
eTRM - FND Tables and Views 12.1.1
No longer used