Results for “locator_segment1”
42 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view GMF_XLA_ITEM_LOCATIONS_V is an APPS-owned database view in Oracle E-Business Suite, defined under the Process Manufacturing Financials (GMF) product. Its documented purpose is to supply Subledger Accounting (SLA) Accounting Data Reference (ADR) sources derived from Inventory Item Locations. In other words, it is an internal integration object rather than an end-user inquiry screen. It functions as one of the registered source views from which Subledger Accounting's Accounting Methods Builder (AMB) derives attribute values when processing and generating accounting entries that reference inventory locators.
Because locator information frequently underpins cost and inventory accounting events, the view standardizes the descriptive flexfield-style structure of MTL_ITEM_LOCATIONS into explicitly named, positionally indexed columns. This allows SLA to consume locator segment values as mapping sources without directly coupling to the base table's internal column conventions.
Underlying Base Objects
The view is defined over a single documented base object: MTL_ITEM_LOCATIONS, referenced as a synonym. No joins to other tables appear in the view text; the definition is a straightforward projection. The key transformation pattern is renaming: the base table's INVENTORY_LOCATION_ID is aliased to LOCATOR_ID, ORGANIZATION_ID is passed through unchanged, and the twenty flexfield segments (SEGMENT1 through SEGMENT20) are each aliased to a LOCATOR_SEGMENT<n> column.
Additionally, the view exposes a LOCATOR_CONCAT_SEGMENTS column populated as a literal NULL. This is a deliberate design choice: the concatenated description is not materialized at the view level, and SLA ADR consumers must therefore rely on the discrete segment columns or on concatenation logic defined elsewhere in the accounting configuration.
Key Columns
- LOCATOR_ID — Surrogate identifier for the inventory locator; sourced from MTL_ITEM_LOCATIONS.INVENTORY_LOCATION_ID. This is the primary join key back to locator records.
- ORGANIZATION_ID — The inventory organization to which the locator belongs; critical for multi-org context and for SLA mapping rules scoped by organization.
- LOCATOR_CONCAT_SEGMENTS — Present but hard-coded to NULL; consumers should not depend on a populated concatenated value.
- LOCATOR_SEGMENT1 through LOCATOR_SEGMENT20 — The discrete key flexfield segments of the locator structure. Locator Segment1 (LOCATOR_SEGMENT1) is the most frequently referenced, since the first segment typically denotes the primary location or subinventory storage region and is the value most commonly used as an SLA mapping source or in user-defined locator naming.
Common Use Cases and Queries
The most frequent query pattern involves resolving locator identifiers to their descriptive segment values for accounting analysis and reconciliation. A representative query is:
SELECT locator_id, organization_id, locator_segment1, locator_segment2 FROM apps.gmf_xla_item_locations_v WHERE organization_id = :org_id AND locator_segment1 = :locator_segment1;
This retrieves all locators in an organization whose primary segment matches a supplied value. Analysts also join the view to SLA journal line tables to trace which locator drove a given accounting entry, and use it to validate that ADR source mappings referencing LOCATOR_SEGMENT1 return expected results. Because LOCATOR_CONCAT_SEGMENTS is NULL, any query relying on a concatenated locator description must concatenate the individual segment columns explicitly or reconcile against MTL_ITEM_LOCATIONS. The view should be treated as a stable but internally scoped SLA artifact.
-
View for SLA ADR sources from Inventory Item Locations
APPS.GMF_XLA_ITEM_LOCATIONS_V·↳ MTL_ITEM_LOCATIONS·Explore GMF module →
-
APPS.CST_XLA_INV_ITEM_LOCS_REF_V·↳ MTL_ITEM_LOCATIONS·Explore BOM module →
-
View for SLA ADR sources from Inventory Item Locations
APPS.GMF_XLA_ITEM_LOCATIONS_V·↳ MTL_ITEM_LOCATIONS·Explore GMF module →
-
Replenishment line interface information
-
APPS.CST_XLA_INV_ITEM_LOCS_REF_V·↳ MTL_ITEM_LOCATIONS·Explore BOM module →
-
Cycle Count Entries Interface data
-
Cycle Count Entries Interface data
-
Replenishment line interface information
-
Cycle Count Entries Interface View
APPS.MTL_CC_ENTRIES_INTERFACE_V·↳ HR_GENERAL·↳ HR_ORGANIZATION_UNITS·↳ HR_SECURITY·Explore INV module →
-
Cycle Count Entries Interface View
APPS.MTL_CC_ENTRIES_INTERFACE_V·↳ HR_GENERAL·↳ HR_ORGANIZATION_UNITS·↳ HR_SECURITY·Explore INV module →
-
eTRM - GMF Tables and Views 12.1.1
Defines Third-Party software which has a supported interface to OPM.
-
eTRM - GMF Tables and Views 12.2.2
Defines Third-Party software which has a supported interface to OPM.
-
eTRM - INV Tables and Views 12.1.1
-
eTRM - INV Tables and Views 12.2.2
-
eTRM - BOM Tables and Views 12.1.1
Table to map wip transactions to their corresponding event types.
-
eTRM - BOM Tables and Views 12.2.2
Table to map wip transactions to their corresponding event types.