Search Results level_value_id

Overview

The WSH_REPORT_PRINTERS table is a configuration table within the Oracle E-Business Suite Shipping Execution (WSH) module. Its primary role is to define and manage printer assignments for shipping-related concurrent reports. The table stores rules that determine the specific printer to be used when a shipping document, such as a packing slip, bill of lading, or commercial invoice, is submitted for printing. These assignments can be configured at various organizational levels, enabling granular control over report output based on the user, responsibility, organization, or other criteria. This functionality is critical for high-volume shipping operations that require documents to be printed at specific physical locations, such as warehouse packing stations.

Key Information Stored

The table's structure is defined by its composite primary key, which establishes the uniqueness of each printer assignment rule. The key columns are APPLICATION_ID, CONCURRENT_PROGRAM_ID, LEVEL_TYPE_ID, and LEVEL_VALUE_ID. The APPLICATION_ID links to the specific EBS application (e.g., Shipping Execution). The CONCURRENT_PROGRAM_ID identifies the exact report or program being printed. The LEVEL_TYPE_ID and LEVEL_VALUE_ID columns work together to define the context or scope of the printer assignment. LEVEL_TYPE_ID indicates the type of entity (e.g., user, responsibility, organization, site) for the rule, while LEVEL_VALUE_ID holds the specific identifier for that entity instance. Additional columns, implied by the table's purpose, would typically store the printer name or destination.

Common Use Cases and Queries

A primary use case is troubleshooting report printing issues or auditing printer configurations. For instance, an administrator may need to identify all printer assignments for a specific shipping report across different warehouses. A common query pattern involves joining to FND_CONCURRENT_PROGRAMS to get the report name and interpreting the LEVEL_TYPE_ID and LEVEL_VALUE_ID against reference tables like PER_USERS or HR_ORGANIZATION_UNITS.

• Sample Query: To find printer assignments for a specific concurrent program, one might use: SELECT * FROM WSH.WSH_REPORT_PRINTERS WHERE CONCURRENT_PROGRAM_ID = <program_id>;
• Reporting Use Case: Generating a master list of all configured shipping document printers, showing the report name, assignment level (User, Responsibility, etc.), and the assigned printer destination.

Related Objects

The table's primary key, WSH_REPORT_PRINTERS_PK, is its central relationship. The key columns are foreign keys to other core EBS tables, though the provided metadata does not explicitly name them. Based on standard EBS schema design:

• APPLICATION_ID and CONCURRENT_PROGRAM_ID would reference the FND_CONCURRENT_PROGRAMS table, which defines all executable concurrent programs in the system.
• LEVEL_VALUE_ID's reference table depends entirely on the LEVEL_TYPE_ID. LEVEL_TYPE_ID acts as a foreign key to a lookup table defining entity types (e.g., FND_LOOKUP_VALUES), and LEVEL_VALUE_ID would then point to the primary key of the table for that type (e.g., USER_ID in FND_USER, ORG_ID in HR_OPERATING_UNITS).

The table is primarily referenced by the shipping document submission and printing logic within the WSH module's packages and forms.