Results for “user_status_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AHL_USER_STATUSES_TL is a translation table in the AHL schema, the Oracle E-Business Suite module for Complex Maintenance Repair and Overhaul (CMRO). It stores the language-specific, translated content for user-defined statuses used throughout the maintenance and overhaul process. In Oracle EBS, the "_TL" suffix denotes a translation table that holds a row for each installed or enabled language. This pattern enables Oracle's Multi-Language Support (MLS) architecture, in which descriptive attributes such as names and descriptions are maintained separately from the base transactional record so that operators in different locales can view status labels in their own language.
The object is documented as VALID in the ETRM repository and belongs to the AHL product family. Although only a brief description is provided, the presence of the translation table implies a corresponding base table — AHL_USER_STATUSES_B — that holds the actual status records, workflow flags, and configuration settings, while AHL_USER_STATUSES_TL holds the human-readable text that accompanies them.
From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. In other words, AHL_USER_STATUSES_TL functions like a descriptive satellite attached to the base status entity, carrying descriptive attributes (translated NAME and DESCRIPTION) keyed by the parent business key plus a language discriminator. This classification is a modeling suggestion rather than a physical constraint.
Key Information Stored
The table contains ten documented columns. The most important are:
- USER_STATUS_ID — The surrogate primary key and the join key to the base table. It is part of AHL_USER_STATUSES_TL_PK and is a foreign key to AHL_USER_STATUSES_B.USER_STATUS_ID.
- LANGUAGE — The language code for the translated row. The combination of USER_STATUS_ID and LANGUAGE forms the unique business key candidate AHL_USER_STATUSES_TL_U1.
- SOURCE_LANG — Indicates the source language from which the translation was derived or entered.
- NAME — The translated display name of the user status.
- DESCRIPTION — The translated descriptive text for the user status.
- CREATED_BY, CREATION_DATE — Audit columns identifying who created the translation row and when.
- LAST_UPDATED_BY, LAST_UPDATE_DATE — Audit columns identifying who last modified the row and when.
- LAST_UPDATE_LOGIN — The login identifier associated with the most recent update.
The primary key is the surrogate USER_STATUS_ID, while the unique index AHL_USER_STATUSES_TL_U1 (USER_STATUS_ID, LANGUAGE) represents the true business-key candidate. This distinction matters because a single status can appear in multiple languages, whereas the base configuration row is unique.
Common Use Cases and Queries
Typical usage involves resolving a status identifier to its translated label for reporting, OAF pages, or concurrent program output. A common reporting pattern joins the translation table to the base table and filters by the session or requested language:
- Retrieve translated status names for a specific language:
SELECT b.user_status_id, t.name, t.description FROM ahl.ahl_user_statuses_b b, ahl.ahl_user_statuses_tl t WHERE b.user_status_id = t.user_status_id AND t.language = USERENV('LANG'); - List all available translations for a given status:
SELECT language, name FROM ahl.ahl_user_statuses_tl WHERE user_status_id = :status_id; - Audit translation coverage by comparing languages present in the table against the set of installed languages.
- Feed lookup views or BI Publisher reports that require localized status captions.
Because the table is maintained by the AHL application, direct DML is not recommended. Translators should use the standard CMRO setup interface to add or revise translations.
Related Objects
The following objects are most significant in relation to AHL_USER_STATUSES_TL:
- AHL_USER_STATUSES_B — The base table holding the actual user status records; joined on USER_STATUS_ID. It is the parent entity to this translation satellite.
- AHL_USER_STATUSES_TL_PK — The primary key constraint on USER_STATUS_ID.
- AHL_USER_STATUSES_TL_U1 — The unique index on (USER_STATUS_ID, LANGUAGE), enforcing one translation per language per status.
- FND_LANGUAGES — The EBS language reference table, used to validate LANGUAGE and SOURCE_LANG values.
- FND_USER — Referenced indirectly through CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for audit traceability.
- AHL status lookup views — Application views and OAF pages that surface translated status labels depend on this table for display text.
Together these objects form the configuration backbone for user-defined statuses in Oracle CMRO.
-
This table stores translated information for user statuses
-
Translation columns for User Statuses
-
This is a surrogate table to QP_LIST_HEADERS_B for Price List related information. QP_LIST_HEADER_ID is the foreign key to QP_LIST_HEADERS_B. This table will capture status, owner and other attributes specifice to Trade Management Requir
-
Stores User status information
-
View: AMS_P_CELLS_V 12.1.1
APPS.AMS_P_CELLS_V·↳ AMS_CELLS_VL·↳ AMS_JTF_RS_EMP_V·Explore AMS module →
-
Table To store the Net Accrual Rule sets
-
Table To store the Net Accrual Rule sets
-
Translation columns for User Statuses
-
View: AMS_USER_STATUSES_V 12.1.1
This view returns information on User statuses defined for System Statuses for Marketing Objects(Event,Registration,Campaign etc..)
APPS.AMS_USER_STATUSES_V·↳ AMS_LOOKUPS·↳ AMS_USER_STATUSES_VL·↳ FND_LOOKUP_TYPES_VL·Explore AMS module →
-
This is a surrogate table to QP_LIST_HEADERS_B for Price List related information. QP_LIST_HEADER_ID is the foreign key to QP_LIST_HEADERS_B. This table will capture status, owner and other attributes specifice to Trade Management Requir
-
This table stores user status information
-
View: AMS_CELLS_SEL_ALL_V 12.1.1
Segment selection view definition
APPS.AMS_CELLS_SEL_ALL_V·↳ AMS_ACT_DISCOVERER_ALL·↳ AMS_CELLS_VL·↳ AMS_LIST_QUERIES_ALL·Explore AMS module →
-
This is a surrogate table to QP_LIST_HEADERS_B for Price List related information. QP_LIST_HEADER_ID is the foreign key to QP_LIST_HEADERS_B. This table will capture status, owner and other attributes specifice to Marketing Online Requir
-
View: AMS_USER_STATUSES_VL 12.1.1
This view returns information on User statuses defined for System Statuses for Marketing Objects(Event,Registration,Campaign etc..)
APPS.AMS_USER_STATUSES_VL·↳ AMS_USER_STATUSES_B·↳ AMS_USER_STATUSES_TL·Explore AMS module →
-
Stores User status information
-
View: BIM_DIMV_CAMPAIGNS 12.1.1
Shows all campaigns.
APPS.BIM_DIMV_CAMPAIGNS·↳ AMS_CAMPAIGNS_VL·↳ AMS_SOURCE_CODES_DETAILS_V·↳ BIM_I_SOURCE_CODES·Explore BIM module →
-
This table stores the definition of marketing cells (Segments). A cell is made up of one to many discoverer workbooks/worksheets. It is better known as Segments in Oracle Marketing.
-
Stores all requests that have been submitted to Oracle Workflow inside Oracle Marketing for the apprkoval Process.
-
Stores all requests that have been submitted to Oracle Workflow inside Oracle Marketing for the apprkoval Process.
-
View: AMS_PRODUCT_PRICING_V 12.2.2
APPS.AMS_PRODUCT_PRICING_V·↳ AMS_ITEM_ATTRIBUTES·↳ AMS_UTILITY_PVT·↳ FND_PROFILE·Explore AMS module →
-
View: AMS_CELLS_VL 12.2.2
This view returns the cells ( segment ) information.
APPS.AMS_CELLS_VL·↳ AMS_CELLS_ALL_B·↳ AMS_CELLS_ALL_TL·Explore AMS module →
-
View: AMS_P_CELLS_V 12.2.2
APPS.AMS_P_CELLS_V·↳ AMS_CELLS_VL·↳ AMS_JTF_RS_EMP_V·Explore AMS module →
-
Target Groups could be subdivided into many small groups. This table stores the information regarding them.
-
This view returns the general information about marketing event headers agenda.
APPS.AMS_EVENT_HEADERS_AGENDA_V·↳ AMS_EVENT_HEADERS_VL·↳ AMS_USER_STATUSES_VL·↳ FND_LANGUAGES_VL·Explore AMS module →
-
This view returns the general information about marketing event headers agenda.
APPS.AMS_EVENT_HEADERS_AGENDA_V·↳ AMS_EVENT_HEADERS_VL·↳ AMS_USER_STATUSES_VL·↳ FND_LANGUAGES_VL·Explore AMS module →
-
This table is obsoleted and no longer in use.
-
View: AMS_USER_STATUSES_V 12.2.2
This view returns information on User statuses defined for System Statuses for Marketing Objects(Event,Registration,Campaign etc..)
APPS.AMS_USER_STATUSES_V·↳ AMS_LOOKUPS·↳ AMS_USER_STATUSES_VL·↳ FND_LOOKUP_TYPES_VL·Explore AMS module →
-
View: AHL_USER_STATUSES_V 12.2.2
This view stores user status information along with lookup type and meaning
APPS.AHL_USER_STATUSES_V·↳ AHL_USER_STATUSES_VL·↳ FND_LOOKUP_TYPES_VL·↳ FND_LOOKUP_VALUES_VL·Explore AHL module →
-
Container for the model definition in the model building process.
-
View: AMS_DM_SCORES_VL 12.2.2
Multi-lingual view for data mining scoring runs.
APPS.AMS_DM_SCORES_VL·↳ AMS_DM_SCORES_ALL_B·↳ AMS_DM_SCORES_ALL_TL·Explore AMS module →
-
Interface table for Event level .
-
Stores the definition of a Marketing Event. (Master Event or Event Template)
-
View: BIM_DIMV_USER_STATUSES 12.2.2
Shows all user-defined statuses.
APPS.BIM_DIMV_USER_STATUSES·↳ AMS_USER_STATUSES_VL·Explore BIM module →
-
View: BIM_DIMV_USER_STATUSES 12.1.1
Shows all user-defined statuses.
APPS.BIM_DIMV_USER_STATUSES·↳ AMS_USER_STATUSES_VL·Explore BIM module →
-
This view is created for giving general information about progam Components
APPS.AMS_PROGRAM_COMPONENTS_V·↳ AMS_CAMPAIGNS_ALL_B·↳ AMS_CAMPAIGNS_VL·↳ AMS_EVENT_HEADERS_VL·Explore AMS module →
-
View: AMS_USER_STATUSES_VL 12.2.2
This view returns information on User statuses defined for System Statuses for Marketing Objects(Event,Registration,Campaign etc..)
APPS.AMS_USER_STATUSES_VL·↳ AMS_USER_STATUSES_B·↳ AMS_USER_STATUSES_TL·Explore AMS module →
-
View: AST_LM_EVENTS_V 12.2.2
APPS.AST_LM_EVENTS_V·↳ AMS_EVENT_HEADERS_VL·↳ AMS_EVENT_OFFERS_VL·↳ AMS_EVENT_REGISTRATIONS·Explore AST module →
-
View: AMS_DM_SCORES_V 12.1.1
View of data mining scoring runs with denormalized reference objects.
APPS.AMS_DM_SCORES_V·↳ AMS_DM_MODELS_ALL_B·↳ AMS_DM_MODELS_ALL_TL·↳ AMS_DM_SCORES_ALL_B·Explore AMS module →
-
Source List Level Table .
-
View: AHL_USER_STATUSES_VL 12.2.2
This view stores user status information
APPS.AHL_USER_STATUSES_VL·↳ AHL_USER_STATUSES_B·↳ AHL_USER_STATUSES_TL·Explore AHL module →
-
This table stores translated information for user statuses
-
View: AST_PLIST_NAMES_UWQ_V 12.1.1
APPS.AST_PLIST_NAMES_UWQ_V·↳ AMS_LIST_HEADERS_VL·Explore AST module →
-
View: AST_PLIST_NAMES_UWQ_V 12.2.2
APPS.AST_PLIST_NAMES_UWQ_V·↳ AMS_LIST_HEADERS_VL·Explore AST module →
-
Interface table for Event Offering Level in Event Dimension
-
This table stores the definition of marketing cells (Segments). A cell is made up of one to many discoverer workbooks/worksheets. It is better known as Segments in Oracle Marketing.
-
Stores information about an Event Offering. .This table also holds the data for all the Agenda Items for the Event Offerings.
-
View: AMS_EVENT_HEADERS_V 12.2.2
This view returns the general information about marketing events (headers).
APPS.AMS_EVENT_HEADERS_V·↳ AMS_EVENT_HEADERS_VL·↳ AMS_LOOKUPS·↳ AMS_USER_STATUSES_VL·Explore AMS module →
-
View: AMS_CELLS_VL 12.1.1
This view returns the cells ( segment ) information.
APPS.AMS_CELLS_VL·↳ AMS_CELLS_ALL_B·↳ AMS_CELLS_ALL_TL·Explore AMS module →
-
Stores all Campaign Schedules
-
Stores all enrollment information for an event, who got registered, who will be attending and their status.