Results for “track_multi_usage_dates”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WSM_PARAMETERS is the organization-level control table for Oracle Shop Floor Management (OSFM), a module within the WSM product family. It stores the configuration flags, accounting defaults, and lot-handling behavior that govern how OSFM processes jobs, lot-based transactions, split/merge operations, and shop-floor movements for a given organization. Every OSFM transaction executed against an organization is implicitly constrained by the parameters defined in this table.

Per the ETRM documentation, an organization must satisfy specific prerequisites before an OSFM parameter record can be defined: it must be a Standard Costing organization, the Lot Number Uniqueness inventory parameter must be set to NONE, and the Lot Number Default Type WIP parameter must be configured appropriately. These conditions establish that WSM_PARAMETERS is not merely a preference store but a gate that legitimizes OSFM functionality for an organization.

From a Data Vault modeling perspective, the mined FK classification identifies this table as hub-leaning. Because its primary key is ORGANIZATION_ID, which is a natural business key rather than a generated surrogate, WSM_PARAMETERS behaves as a hub-like entity that anchors a wide constellation of dependent transaction and interface tables. A satellite would carry the descriptive attribute columns (flags, separators, accounting identifiers) keyed to that hub.

Key Information Stored

The table contains 25 documented columns. The single-column primary key is WSM_PARAMETERS_PK on ORGANIZATION_ID, and the unique index WSM_PARAMETERS_U1 (also ORGANIZATION_ID) confirms that ORGANIZATION_ID is both the surrogate and the business-key candidate. This design enforces exactly one parameter row per inventory organization.

• ORGANIZATION_ID — primary key and foreign key to MTL_PARAMETERS; uniquely identifies the OSFM-enabled organization.
• NEW_LOT_SEPARATOR and JOB_COMPLETION_SEPARATOR — delimiters used when the system auto-generates new lot numbers and job completion identifiers.
• ALLOW_BACKWARD_MOVE_FLAG and DELETE_BACKWARD_FROM_FLAG — control whether backward moves are permitted and how prior operations are handled when a move is reversed.
• TRANSACTION_ACCOUNT_ID — the default account applied to OSFM transaction accounting.
• PLAN_CODE and OP_SEQ_NUM_INCREMENT — drive planning behavior and the increment used when sequencing operations.
• LAST_OPERATION_SEQ_NUM — tracks the last operation sequence number assigned.
• COPRODUCTS_SUPPLY_DEFAULT and DEFAULT_ACCT_CLASS_CODE — determine default supply behavior and account class for coproducts.
• INV_LOT_TXN_ENABLED — indicates whether inventory lot transactions are enabled for the organization.
• ESTIMATED_SCRAP_ACCOUNTING and HONOR_KANBAN_SIZE — govern scrap valuation handling and whether kanban size limits are respected.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Additional flow-control columns such as MOVE_IN_OPTION, MOVE_TO_NEXT_OP_OPTION, SHOW_NEXT_OP_BY_DEFAULT, CHARGE_JUMP_FROM_QUEUE, TRACK_MULTI_USAGE_DATES, and REUSE_JOBNAME refine operator experience and job-numbering behavior.

Common Use Cases and Queries

The most frequent requirement is auditing which organizations are OSFM-enabled and how their lot separators and flags are set. A typical query joins WSM_PARAMETERS to MTL_PARAMETERS to retrieve the organization code and name:

• SELECT wp.organization_id, mp.organization_code, wp.new_lot_separator, wp.allow_backward_move_flag FROM wsm_parameters wp, mtl_parameters mp WHERE wp.organization_id = mp.organization_id;
• Reporting on lot-generation formatting by inspecting NEW_LOT_SEPARATOR and JOB_COMPLETION_SEPARATOR for downstream label-printing or integration logic.
• Validating transaction accounting defaults by reviewing TRANSACTION_ACCOUNT_ID and DEFAULT_ACCT_CLASS_CODE before period close.
• Diagnosing failure of OSFM setup by confirming the organization meets the Standard Costing and lot-uniqueness prerequisites described in the documentation.

Because WSM_PARAMETERS acts as a hub, parameter changes have cascading effects on all OSFM transaction flows for that organization, making it a frequent target of change-control and configuration review reports.

Related Objects

WSM_PARAMETERS sits at the center of the OSFM schema. Its only outbound foreign key references MTL_PARAMETERS, while eleven tables reference it via ORGANIZATION_ID:

• MTL_PARAMETERS — parent master table; join on ORGANIZATION_ID to obtain organization code and costing method.
• WSM_SM_STARTING_LOTS and WSM_SM_RESULTING_LOTS — starting and resulting lot records for split/merge operations.
• WSM_SPLIT_MERGE_TRANSACTIONS and WSM_SPLIT_MERGE_TXN_INTERFACE — executed and interface split/merge transaction data.
• WSM_LOT_SPLIT_MERGES and WSM_LOT_SPLIT_MERGES_INTERFACE — lot-level split/merge definitions and staging.
• WSM_LOT_JOB_INTERFACE and WSM_LOT_MOVE_TXN_INTERFACE — interfaces importing lot job and move transactions.
• WSM_STARTING_LOTS_INTERFACE, WSM_RESULTING_LOTS_INTERFACE, and WSM_SECTOR_EXTENSIONS — additional interface and extension tables keyed to the organization.

All of these depend on WSM_PARAMETERS.ORGANIZATION_ID, reinforcing its role as the governing hub for Oracle Shop Floor Management configuration.