Search Results mws_city

Overview

APPS.HR_WORKSITE_V is a supplementary database view in the Oracle E-Business Suite Applications schema (APPS). It presents Worksite information maintained within the Oracle HRMS (Human Resources Management System) data model, expressed in the "MWS" (Multiple Worksite / Mobile Workforce Survey) column naming convention. Its documented View Type identifies it as "A supplementary view used to simplify forms coding," with an explicit Oracle warning that customers should not query or alter data through it, as its definition may change dramatically in subsequent minor or major releases. The view carries a VALID status and is registered in FND Design Data under the identifier PER.HR_WORKSITE_V, confirming that it belongs to the Oracle Payroll (PER) product family and is intended primarily for internal form and product development use rather than for custom reporting. Although the object is technically exposed in the APPS schema, its design intent is to support Oracle-developed forms logic, particularly for statutory reporting features that consume worksite attributes.

Underlying Base Objects

The ETRM documentation records the following dependencies for APPS.HR_WORKSITE_V: HR_GENERAL (PACKAGE), HR_LOCATIONS (VIEW), HR_ORGANIZATION_INFORMATION (SYNONYM), HR_ORGANIZATION_UNITS (VIEW), and HR_SECURITY (PACKAGE). The view therefore synthesizes data from the core HR organization model. HR_ORGANIZATION_UNITS supplies the organization/worksite entity itself; HR_ORGANIZATION_INFORMATION provides descriptive flexfield and attribute-level details held against that organization; HR_LOCATIONS supplies address components such as address lines, city, state, and ZIP code; HR_SECURITY applies organization-level security filtering; and HR_GENERAL provides general HR utility logic referenced during definition or evaluation. The view is referenced by only one documented dependent object, PAY_MWS_MAGTAPE_REPORTING, confirming that its primary consumer is the Oracle Payroll Multiple Worksite magnetic tape reporting feature. Because the underlying objects are HRMS views and packages that are themselves subject to change, the composition of HR_WORKSITE_V should be regarded as unstable across releases and patching cycles.

Key Columns

The view exposes sixteen columns, each prefixed with MWS_. Principal identifiers include MWS_TAX_UNIT_ID, MWS_BUSINESS_GROUP_ID, and MWS_PRIMARY_WORKSITE_ORG_ID, which anchor the record to a tax unit, a business group, and the organization representing the worksite. Statutory and descriptive attributes include MWS_SUI_ACCOUNT_NO (state unemployment insurance account number), MWS_REPORTING_UNIT_NO, MWS_TRADE_NAME, and MWS_WORKSITE_DESCRIPTION. The column MWS_COMMENT_CODE1 — the search term associated with this object — is a VARCHAR2(150) field holding a coded comment value for the worksite, with a companion column MWS_COMMENT_CODE2 of the same datatype and length, and a free-text MWS_COMMENTS column. Address information is carried in MWS_ADDRESS_LINE_1, _2, and _3 (VARCHAR2(240) each), MWS_CITY (VARCHAR2(30)), MWS_STATE (VARCHAR2(120)), and MWS_ZIP_CODE (VARCHAR2(30)). Notably, the comment and code columns are considerably narrower than the address lines, which is a relevant consideration when mapping source values.

Common Use Cases and Queries

The documented use case is fulfillment of the Payroll Multiple Worksite reporting requirement, where worksite tax identifiers, trade names, and location addresses must be extracted and formatted for statutory filings such as magnetic tape submissions. Because Oracle explicitly discourages direct querying of supplementary views, the recommended approach for custom reporting is to replicate the underlying logic against the HRMS base objects rather than querying HR_WORKSITE_V directly. Where diagnostics or gap analysis against the standard report are required, a controlled query may be issued, for example:

• SELECT MWS_TAX_UNIT_ID, MWS_PRIMARY_WORKSITE_ORG_ID, MWS_TRADE_NAME, MWS_COMMENT_CODE1, MWS_CITY, MWS_STATE FROM APPS.HR_WORKSITE_V WHERE MWS_BUSINESS_GROUP_ID = :p_business_group_id;
• SELECT MWS_SUI_ACCOUNT_NO, MWS_REPORTING_UNIT_NO, MWS_WORKSITE_DESCRIPTION FROM APPS.HR_WORKSITE_V WHERE MWS_PRIMARY_WORKSITE_ORG_ID = :p_org_id;
• Verify whether MWS_COMMENT_CODE1 and MWS_COMMENT_CODE2 are populated for every worksite in scope before relying on them in a custom extract, since the view performs no defaulting of its own.

Any production integration should be validated against the standard PAY_MWS_MAGTAPE_REPORTING process to ensure consistency with supported Oracle functionality.