Results for “wsh_report_printers”

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

Overview

WSH_REPORT_PRINTERS is a Shipping Execution (WSH) configuration table that defines the printer destinations used when shipping-related concurrent programs and reports are submitted. Each row associates a specific concurrent program with a printer name, scoped by a level type and level value, allowing Oracle EBS to resolve the correct output device for a report request based on organizational or hierarchical context. The table carries a composite primary key, WSH_REPORT_PRINTERS_PK, defined over APPLICATION_ID, CONCURRENT_PROGRAM_ID, LEVEL_TYPE_ID, and LEVEL_VALUE_ID, which enforces uniqueness of a printer assignment per program per level instance.

From a data modeling perspective, the metadata classifies this object heuristically as standalone, meaning it does not participate in a rigid hub/link/satellite constellation. Where a modeling suggestion is warranted, the composite key behaves as a business hub combining program and level identifiers, and the descriptive printer attributes (printer name, enablement flag, default flag, and format type) behave as satellite attributes dependent on that key. The column LEVEL_TYPE_ID is central to this object: it determines the granularity at which a printer assignment applies, such as an organization, subinventory, or other hierarchical level maintained within the shipping model.

Key Information Stored

The table contains 39 documented columns. The most significant are described below.

• APPLICATION_ID — Identifies the application owning the concurrent program; part of the primary key.
• CONCURRENT_PROGRAM_ID — The concurrent program for which the printer assignment is defined; part of the primary key.
• LEVEL_TYPE_ID — The level type at which the assignment applies, such as organization or subinventory; part of the primary key and the column most directly relevant to level-based printer resolution.
• LEVEL_VALUE_ID — The specific value instance of the level type; part of the primary key. Together with LEVEL_TYPE_ID it defines the scope of the printer rule.
• PRINTER_NAME — The target printer to which report output is routed.
• DESCRIPTION — Free-text description of the assignment.
• ENABLED_FLAG — Indicates whether the printer assignment is active.
• DEFAULT_PRINTER_FLAG — Marks the assignment as the default printer for the given program and level.
• FORMAT_TYPE — The output format associated with the printer, such as a print style or format classification.
• ORGANIZATION_ID — The inventory organization in scope, where applicable.
• SUBINVENTORY — The subinventory in scope, where applicable.
• LABEL_ID — Reference to label history; the documented foreign key targets GMO_LABEL_HISTORY.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns recording who created and last modified each row and when.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID — Standard concurrent manager request context columns populated when the row is created or updated through a concurrent process.

The surrogate-style unique identifier is the composite primary key WSH_REPORT_PRINTERS_PK. Business-key candidates correspond to the same columns, since no separate single-column unique index is documented. The remaining ATTRIBUTE1 through ATTRIBUTE15 columns provide descriptor flexibility.

Common Use Cases and Queries

Typical scenarios include auditing printer configurations per concurrent program, identifying disabled or default printer rules, and resolving the effective printer for a submission. Sample patterns:

• List active printers for a program: SELECT CONCURRENT_PROGRAM_ID, LEVEL_TYPE_ID, LEVEL_VALUE_ID, PRINTER_NAME FROM WSH.WSH_REPORT_PRINTERS WHERE ENABLED_FLAG = 'Y';
• Find default assignments: filter on DEFAULT_PRINTER_FLAG = 'Y'.
• Scope by level: join LEVEL_TYPE_ID to the relevant level-type lookup to interpret granularity, then join LEVEL_VALUE_ID to the corresponding entity (for example organization or subinventory).
• Organizational reporting: group by ORGANIZATION_ID and SUBINVENTORY to review coverage.

Related Objects

• GMO_LABEL_HISTORY — referenced via WSH_REPORT_PRINTERS.LABEL_ID → GMO_LABEL_HISTORY, linking printer rules to label history.
• FND_CONCURRENT_PROGRAMS — join on APPLICATION_ID and CONCURRENT_PROGRAM_ID to resolve program names.
• FND_APPLICATION — resolves APPLICATION_ID to the owning application.
• ORG_ORGANIZATION_DEFINITIONS — interprets ORGANIZATION_ID scope.
• MTL_SECONDARY_INVENTORIES — supports SUBINVENTORY resolution.
• Shipping label and printer setup concurrent programs that read and write these rows.

Because the object is classified as standalone, dependencies are primarily inbound lookups to concurrent program, organization, subinventory, and label-history reference data rather than enforced child relationships.