Results for “ozf_sd_request_headers_all_tl”
48 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OZF_SD_REQUEST_HEADERS_ALL_TL is the translation (language) table for the Trade Management "sd request headers" entity in the Oracle E-Business Suite OZF schema. The suffix conventions are significant: the _ALL segment indicates the table holds rows across multiple operating units, and the _TL segment identifies it as the translation layer that stores the language-specific descriptive text associated with each base record. Its documented description states its role directly: "Translations for ozf_sd_request_headers_all_b."
The object is maintained in the OZF – Trade Management product and is marked VALID in the ETRM 12.1.1 / 12.2.2 object catalog. Translations in EBS are conventionally paired with a _B base table, which in this case is OZF_SD_REQUEST_HEADERS_ALL_B. The _TL table carries the install base plus every installed language, joined back to the base table by the primary key of the base entity.
From a Data Vault modeling perspective, the mined classification for this object is satellite-leaning. That is a heuristic suggestion rather than a declaration of database design: the table behaves like a descriptive satellite attached to a hub-like base record, keyed by language plus the base entity identifier, and holding non-key descriptive attributes (notably REQUEST_DESCRIPTION) plus auditing and context columns. It does not resolve many-to-many relationships like a link, and it does not identify a business entity on its own like a hub.
Key Information Stored
The documented physical schema exposes 16 columns. The most important, in terms of interpretation and joining, are the following.
- REQUEST_HEADER_ID – Identifier of the parent request header record; this is the join column to the base table and part of the primary key.
- LANGUAGE – The language code for the translation row; the second component of the primary key.
- SOURCE_LANG – The language of the source (base) record, used by the translation framework to determine which rows require translation.
- REQUEST_DESCRIPTION – The translated descriptive text for the request header; this is the principal business-facing payload of the table.
- REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE – Concurrent program request context and last program-driven update information.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard EBS auditing columns, shared with the base table by convention.
- CREATED_FROM – Origin indicator for the row (for example, whether it was created through a UI or an interface).
- SECURITY_GROUP_ID – Security group reference, documented as a foreign key to FND_SECURITY_GROUPS; relevant in multi-org and access-control contexts.
- ORG_ID – Operating unit identifier supporting the
_ALLmulti-org designation.
The surrogate/primary key is defined by OZF_SD_REQUEST_HDRS_ALL_TL_PK on (LANGUAGE, REQUEST_HEADER_ID). A unique index, OZF_SD_REQUEST_HDRS_ALL_TL_U1, is documented on the same column pair, confirming it as the business-key candidate for the table. Note that the primary key is composite: the base identifier alone is not unique here, because one row exists per installed language.
Common Use Cases and Queries
The dominant use case is retrieving the translated request description for a given request header in the user's current session language. A typical pattern joins the translation table to the base table and filters by language:
- Reporting that lists request headers with their translated descriptions for a specific operating unit.
- Extracts and feeds that must emit descriptions in a fixed language rather than the session default.
- Audits confirming that a translation row exists for every required installed language.
- Diagnostics when a description displays blank in one language, indicating a missing or untranslated
_TLrow.
A representative query shape is a join on REQUEST_HEADER_ID between the _B and _TL tables, constrained by LANGUAGE = USERENV('LANG') (or a literal language code for fixed-language output), selecting REQUEST_DESCRIPTION alongside the base table's identifying attributes. Because the primary key is (LANGUAGE, REQUEST_HEADER_ID), queries should always constrain language to avoid returning multiple rows per header.
Related Objects
The following objects are the most significant for working with this table, based on the documented foreign-key and primary-key relationships.
- OZF_SD_REQUEST_HEADERS_ALL_B – The base table. Join on OZF_SD_REQUEST_HEADERS_ALL_TL.REQUEST_HEADER_ID = OZF_SD_REQUEST_HEADERS_ALL_B.REQUEST_HEADER_ID; this is the documented foreign-key relationship.
- OZF_SD_REQUEST_HDRS_ALL_TL_PK – Primary key constraint/index on (LANGUAGE, REQUEST_HEADER_ID).
- OZF_SD_REQUEST_HDRS_ALL_TL_U1 – Unique index on (LANGUAGE, REQUEST_HEADER_ID), the business-key candidate.
- FND_SECURITY_GROUPS – Referenced by SECURITY_GROUP_ID; used to resolve security group context.
- FND_LANGUAGES – Though not documented as a foreign key here, this is the standard reference for interpreting LANGUAGE and SOURCE_LANG values in EBS translation tables.
- FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS – Logical references for REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID, useful for tracing which process last updated a translation row.
These relationships position OZF_SD_REQUEST_HEADERS_ALL_TL as a dependent, language-scoped satellite of the request header entity, retrievable only in conjunction with its base table.
-
Translations for ozf_sd_request_headers_all_b
-
Translations for ozf_sd_request_headers_all_b
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - OZF Tables and Views 12.2.2
OZF_XREF_MAP table created for SIebel TPM Integration
-
eTRM - OZF Tables and Views 12.1.1
Table to store the Market eligibilty for a Offer Worksheet
-
12.2.2 DBA Data 12.2.2
-
eTRM - OZF Tables and Views 12.2.2
OZF_XREF_MAP table created for SIebel TPM Integration
-
eTRM - OZF Tables and Views 12.1.1
Table to store the Market eligibilty for a Offer Worksheet
-
12.1.1 DBA Data 12.1.1