Search Results pjm_seiban_numbers

Overview

The table PJM_SEIBAN_NUMBERS is a core data object within the Project Manufacturing (PJM) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the master repository for Seiban numbers, a critical concept in project-centric manufacturing. A Seiban number, or project number, is a unique identifier used to tag, track, and segregate all materials, components, work orders, and costs associated with a specific manufacturing project or customer order. This table's primary role is to define and maintain the valid list of these project identifiers, enabling the system to enforce project-level control and visibility throughout the manufacturing and supply chain processes.

Key Information Stored

While the provided ETRM metadata does not list all columns, the documented primary and foreign key relationships establish the foundational data structure. The table's primary key is the PROJECT_ID column, which stores the unique identifier for each Seiban number. This is the key value referenced throughout the manufacturing lifecycle. Based on standard PJM data models, this table typically also stores descriptive information for each project, such as the project name, status, start and end dates, and associated project attributes that govern manufacturing and costing rules. The existence of a primary key constraint (PJM_SEIBAN_NUMBERS_PK) on PROJECT_ID ensures data integrity and uniqueness for all Seiban definitions.

Common Use Cases and Queries

This table is central to reporting and transactional integrity in project manufacturing environments. Common use cases include validating a Seiban number during sales order entry or work order creation, generating project-specific material requirement reports, and reconciling project costs. A fundamental query involves joining this table to transaction data to report on all activities for a given project. For example, to list all active Seiban numbers, a query might be: SELECT project_id, name FROM pjm_seiban_numbers WHERE NVL(disable_date, SYSDATE+1) > SYSDATE;. Another critical pattern is using this table as a filter or lookup in reports joining to tables like WIP_DISCRETE_JOBS or MTL_MATERIAL_TRANSACTIONS to analyze project-specific production or material movements.

Related Objects

The documented foreign key relationship explicitly defines a key dependency for this table. The PJM_PROJECT_PARAMETERS table references PJM_SEIBAN_NUMBERS via its PROJECT_ID column. This relationship means that project-specific manufacturing parameters (PJM_PROJECT_PARAMETERS) cannot be defined without a valid, pre-existing Seiban number in the PJM_SEIBAN_NUMBERS table. This enforces referential integrity, ensuring that all configured projects are based on master Seiban definitions. In practice, this table is also extensively referenced by numerous other PJM and manufacturing tables (such as those for costs, schedules, and allocations) that use PROJECT_ID as a key dimension, though those specific relationships are not detailed in the provided excerpt.