Search Results mtl_3pl_locator_occupancy

Overview

The MTL_3PL_LOCATOR_OCCUPANCY table is a core data structure within the Oracle E-Business Suite Inventory (INV) module, specifically designed to support third-party logistics (3PL) operations. Its primary role is to serve as the foundational, seeded data source for calculating storage capacity and occupancy at the locator level within a warehouse. This capacity data is a critical input for the 3PL Billing Solution, enabling logistics providers to accurately bill their clients based on the physical space utilized by inventory over time. The table's existence underscores Oracle EBS's functionality for managing complex, multi-client warehouse environments where precise tracking of space consumption is essential for operational and financial reporting.

Key Information Stored

The table's structure is designed to uniquely identify and track occupancy metrics per client, organization, and storage locator. The primary key is a composite of CLIENT_CODE, LOCATOR_ID, and ORGANIZATION_ID, ensuring that occupancy records are distinct for each combination. The CLIENT_CODE links to the MTL_CLIENT_PARAMETERS table, identifying the specific 3PL client. The LOCATOR_ID points to a specific storage subinventory locator (typically related to MTL_ITEM_LOCATIONS), and the ORGANIZATION_ID specifies the inventory organization. While the provided metadata does not list all columns, the table's described purpose implies it stores calculated or derived metrics such as occupied volume, occupied weight, capacity thresholds, or occupancy percentages, which are used for the billing calculations.

Common Use Cases and Queries

The principal use case is generating reports and data feeds for 3PL billing cycles, where charges are based on space usage. System processes or concurrent programs likely populate this table by aggregating transactional data from material movements. Common analytical queries would involve joining this table with client and locator master data. A typical reporting pattern might resemble:

• SELECT c.client_name, l.concatenated_segments locator, o.occupied_volume, o.occupancy_percentage FROM inv.mtl_3pl_locator_occupancy o, inv.mtl_client_parameters c, inv.mtl_item_locations l WHERE o.client_code = c.client_code AND o.locator_id = l.inventory_location_id AND o.organization_id = :p_org_id;

Integration with the 3PL Billing Solution would involve queries to extract occupancy snapshots for a specific period to calculate invoice line amounts.

Related Objects

MTL_3PL_LOCATOR_OCCUPANCY has defined relationships with several key Inventory tables. Its primary foreign key constraint links the CLIENT_CODE column to the MTL_CLIENT_PARAMETERS table, which stores master information for each 3PL client. The LOCATOR_ID column is inherently related to the MTL_ITEM_LOCATIONS table (or a similar locator master), which defines the physical and logical storage locations within a subinventory. While not explicitly listed as a foreign key, the ORGANIZATION_ID column relates to the standard HR_ORGANIZATION_UNITS table. The table is central to the 3PL Billing Solution, implying dependencies from specific billing engine packages or views that consume its data for financial calculations.