Search Results max_capacity




Overview
Explore in AI Chat

Overview

APPS.CR_RSRC_MST_VL is a valid, documented view within Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the APPS schema and associated with the GMP - Process Manufacturing Process Planning product family. It presents the Resource Master — the canonical definition of a manufacturing resource (machine, labor crew, or production line) together with its capacity, costing, and efficiency attributes. In EBS the suffix _VL denotes a "validated language" view: it joins the base table to its translation table and filters on the session language so that the descriptive text returned is always the user's current language. For reporting and integration this view is the standard read interface for resource master data. Custom reports, BI Publisher data models, interface extracts, and downstream planning integrations query CR_RSRC_MST_VL rather than the base tables because it delivers both the numeric planning attributes and the translated resource description in a single query. It is a query-only object; DML must be directed at the underlying tables.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through APPS synonyms:

  • CR_RSRC_MST_B — the base (non-translated) table holding all resource master attributes, keyed by RESOURCES.
  • CR_RSRC_MST_TL — the translation table holding the language-specific resource description, keyed by RESOURCES and LANGUAGE.

The defining SQL selects all business columns from the base table and the description from the translation table, joined on B.RESOURCES = T.RESOURCES with the predicate T.LANGUAGE = USERENV('LANG'), guaranteeing a single row per resource in the caller's session language. The column list includes B.ROWID exposed as ROW_ID, alongside audit columns (CREATION_DATE, LAST_UPDATE_DATE, DELETE_MARK, TEXT_CODE) and the capacity attributes.

Key Columns

  • RESOURCES — the primary resource key linking to routings, resource usages, and capacity requirements.
  • ROW_ID — the physical row identifier from CR_RSRC_MST_B.
  • RESOURCE_DESC — the language-specific description from CR_RSRC_MST_TL.
  • MIN_CAPACITY / MAX_CAPACITY — the minimum and maximum units of capacity that may be applied to the resource; MAX_CAPACITY is the value most frequently searched by users, since it governs the maximum load that scheduling and capacity planning will place on a resource.
  • CAPACITY_CONSTRAINT, CAPACITY_UOM, CAPACITY_UM, CAPACITY_TOLERANCE — the constraint flag, unit of measure, and tolerance controlling how capacity overloads are treated.
  • UTILIZATION / EFFICIENCY — availability and performance factors used to derate nominal capacity.
  • STD_USAGE_UM / STD_USAGE_UOM — standard usage unit of measure for the resource.
  • COST_CMPNTCLS_ID, RESOURCE_CLASS — costing component class and resource classification.

Common Use Cases and Queries

Typical uses include auditing maximum capacity values across resources, feeding capacity data into planning extracts, and validating resource setup before running a production schedule.

List resources with their maximum capacity:

  • SELECT RESOURCES, RESOURCE_DESC, MIN_CAPACITY, MAX_CAPACITY, CAPACITY_UOM FROM APPS.CR_RSRC_MST_VL WHERE DELETE_MARK = 0 ORDER BY RESOURCES;

Retrieve a single resource's capacity profile:

  • SELECT RESOURCES, RESOURCE_DESC, MAX_CAPACITY, CAPACITY_CONSTRAINT, UTILIZATION, EFFICIENCY FROM APPS.CR_RSRC_MST_VL WHERE RESOURCES = :resource_id;

Identify resources exceeding a capacity threshold:

  • SELECT RESOURCES, RESOURCE_DESC, MAX_CAPACITY FROM APPS.CR_RSRC_MST_VL WHERE MAX_CAPACITY > 100 AND DELETE_MARK = 0;

Because the view already applies the USERENV('LANG') filter, no additional language predicate is required in consuming queries.