Search Results wip_parameters




Overview

The WIP_PARAMETERS table is a fundamental setup and control table within the Oracle E-Business Suite Work in Process (WIP) module. It stores organization-specific manufacturing parameters that define default behaviors, control policies, and system-wide settings for discrete and repetitive manufacturing. Each manufacturing organization has a single corresponding record in this table, making it the central repository for WIP configuration at the organizational level. Its settings govern critical processes such as job and schedule creation, transaction processing, costing, and supply consumption, ensuring operational consistency across the WIP module.

Key Information Stored

The table's primary key is ORGANIZATION_ID, which ties each record to a specific inventory organization. Key columns define essential operational defaults and flags. These include DEFAULT_DISCRETE_CLASS, which specifies the standard accounting class for new discrete jobs, and DEFAULT_PULL_SUPPLY_SUBINV along with DEFAULT_PULL_SUPPLY_LOCATOR_ID, which define the default subinventory and locator for component material supply. Other significant columns control system behavior, such as flags for enforcing shop floor status, allowing negative component balances, enabling lot and serial number control, and setting defaults for job start dates and completion subinventories. The parameters essentially codify the manufacturing policies for the organization.

Common Use Cases and Queries

This table is primarily referenced during setup, transaction processing, and reporting. A common use case is validating or auditing an organization's WIP setup. Technical consultants and DBAs often query this table to verify default values before major data conversions or to troubleshoot transaction errors. A typical diagnostic query retrieves the core parameters for a specific organization:

  • SELECT organization_id, default_discrete_class, default_pull_supply_subinv FROM wip_parameters WHERE organization_id = :org_id;

Another frequent scenario involves integrating custom programs with WIP, where developers must read the default supply subinventory or accounting class from WIP_PARAMETERS to correctly populate interface tables like WIP_MOVE_TXN_INTERFACE or WIP_JOB_SCHEDULE_INTERFACE, ensuring data aligns with organizational policy.

Related Objects

As indicated by its foreign keys, WIP_PARAMETERS has a central relationship with numerous core WIP tables. It is referenced by transactional and interface tables, including WIP_ENTITIES (jobs/schedules), WIP_LINES (repetitive schedules), WIP_MOVE_TXN_INTERFACE, and WIP_COST_TXN_INTERFACE. Its columns also enforce referential integrity with master data tables: DEFAULT_DISCRETE_CLASS references WIP_ACCOUNTING_CLASSES, and DEFAULT_PULL_SUPPLY_SUBINV references MTL_SECONDARY_INVENTORIES. This web of relationships underscores its role as a foundational control point, ensuring that all WIP transactions and entities adhere to the defined organizational parameters.