Search Results wms_db_objects_parent_pk

Overview

The WMS_DB_OBJECTS_PARENTS table is a core data dictionary object within the Oracle E-Business Suite Warehouse Management (WMS) module. It functions as a relational mapping table, defining hierarchical parent-child relationships between various database objects that are managed and tracked by the WMS system. Its primary role is to maintain metadata integrity, enabling the system to understand dependencies and structures among WMS entities. This table is essential for operations that require navigating object hierarchies, validating configurations, and ensuring referential integrity during complex warehouse transactions and setup processes in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to capture the essential elements of a parent-child link. Its primary key is a composite of two columns: DB_OBJECT_ID and TYPE_CODE. The DB_OBJECT_ID column stores the unique identifier of the child database object. The TYPE_CODE column is a critical field that categorizes the nature or type of the parent relationship, allowing for different hierarchical contexts to be managed within the same table. While the specific list of TYPE_CODE values is not detailed in the provided metadata, this column is key to interpreting the relationship. The table's foreign key constraint indicates it references the WMS_DB_OBJECTS table via the DB_OBJECT_ID, ensuring that every record in WMS_DB_OBJECTS_PARENTS corresponds to a valid, defined object in the master WMS objects table.

Common Use Cases and Queries

This table is predominantly used in backend validations and hierarchical data retrieval. A common use case is during the setup or modification of a warehouse layout, where the system must verify that a child object (like a subinventory location) is correctly assigned to a valid parent object (like a warehouse zone). For reporting, it enables queries to list all child objects for a given parent or to trace the lineage of a specific object. A typical SQL pattern would involve joining this table with WMS_DB_OBJECTS to get descriptive names. For example, to find all parent relationships for a specific object type, one might use: SELECT wdo.OBJECT_NAME, wdop.TYPE_CODE FROM WMS_DB_OBJECTS wdo JOIN WMS_DB_OBJECTS_PARENTS wdop ON wdo.DB_OBJECT_ID = wdop.DB_OBJECT_ID WHERE wdop.TYPE_CODE = '<TYPE>';. This supports configuration audits and impact analysis.

Related Objects

• WMS_DB_OBJECTS: This is the primary master table referenced by WMS_DB_OBJECTS_PARENTS. A foreign key constraint exists where WMS_DB_OBJECTS_PARENTS.DB_OBJECT_ID references WMS_DB_OBJECTS. This relationship ensures that every child object recorded in the parents table is a valid entity defined in the WMS system's object registry.
• WMS_DB_OBJECTS_PARENT_PK: This is the primary key constraint on the table, enforcing uniqueness on the combination of the DB_OBJECT_ID and TYPE_CODE columns. This prevents duplicate parent relationships for the same object and relationship type.