Search Results class_type




Overview
Explore in AI Chat

Overview

APPS.WIP_REPETITIVE_CLASSES_VAL_V is a validation view in the Oracle E-Business Suite Work in Process (WIP) module. Its purpose is to expose a filtered subset of accounting class definitions that are valid for repetitive manufacturing schedules. The view is defined over the WIP_ACCOUNTING_CLASSES table and applies a WHERE clause that excludes disabled classes and restricts the result set to a single class type, identified by the literal CLASS_TYPE = 2.

Because the view filters on both an effective-date condition and the class type, it functions as a validation source for value sets and list-of-values (LOV) definitions attached to repetitive scheduling concurrent programs, forms, and integrations. Rather than presenting the complete accounting class catalog, it returns only those records that are currently active and of the repetitive class category, ensuring that downstream validation and defaulting logic cannot select an obsolete or non-repetitive class.

Underlying Base Objects

The view is documented, per ETRM 12.2.2 metadata, as being defined over a single referenced base object: WIP_ACCOUNTING_CLASSES (accessed through a synonym). WIP_ACCOUNTING_CLASSES is the master table that stores accounting class definitions for discrete, repetitive, and (where applicable) other WIP class types. Each accounting class carries a CLASS_TYPE discriminator that distinguishes its usage.

APPS.WIP_REPETITIVE_CLASSES_VAL_V performs no joins and no aggregation. It is a pure projection-and-filter view: it selects the accounting columns from the base table and restricts rows using two predicates. The first predicate, NVL(DISABLE_DATE, SYSDATE+1) > SYSDATE, retains classes whose DISABLE_DATE is null (never disabled) or is still in the future. The second predicate, CLASS_TYPE = 2, retains only repetitive class records. The owner of the view is APPS.

Key Columns

Common Use Cases and Queries

The principal use case is validating user-entered or defaulted accounting class values for repetitive schedules. Because the view already excludes disabled and non-repetitive classes, it is commonly registered as the table-validated source of a value set. A typical query returns all currently valid repetitive classes for reporting or LOV display:

  • SELECT CLASS_CODE, DESCRIPTION, ORGANIZATION_ID FROM APPS.WIP_REPETITIVE_CLASSES_VAL_V ORDER BY CLASS_CODE;
  • SELECT CLASS_CODE, MATERIAL_ACCOUNT, RESOURCE_ACCOUNT FROM APPS.WIP_REPETITIVE_CLASSES_VAL_V WHERE ORGANIZATION_ID = :org_id;
  • SELECT COUNT(*) FROM APPS.WIP_REPETITIVE_CLASSES_VAL_V WHERE CLASS_CODE = :class_code; for existence/validation checks.

In integration and reconciliation scenarios, the view is used to retrieve the full account set for a repetitive class so that cost postings can be verified against WIP accounting distributions. Analysts should note that the view reflects only active classes as of the current system date; historically disabled classes are not returned, and historical reporting must query WIP_ACCOUNTING_CLASSES directly with appropriate date handling.