Search Results sequence_dependent_usage

Overview

GME_BATCH_STEP_RESOURCES_V is a supplementary view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2, defined in the Process Manufacturing Process Execution (GME) module. It is built on the gme_batch_step_resources base table and exposes resource assignments at the batch step level, joined to the resource master to supply descriptive text. The view adds display-formatted date columns derived through FND_DATE and FND_TIMEZONES, making it suitable for operational reporting, batch execution inquiries, and integration extracts where resource consumption, capacity limits, and scheduling data are needed for a manufacturing batch.

Because the view is marked VALID and its referenced objects include package calls (FND_DATE, FND_TIMEZONES), consumers should treat it as a reporting and inquiry layer rather than a transactional interface. The presence of the MIN_CAPACITY and MAX_CAPACITY columns is directly relevant to users searching on "min_capacity," as these fields express the lower and upper capacity bounds defined for a resource within a batch step.

Underlying Base Objects

The view is defined over the following documented base objects:

• GME_BATCH_STEP_RESOURCES (SYNONYM) — the primary source of all resource-level attribute columns, aliased GBSR in the view text.
• CR_RSRC_MST (SYNONYM) — joined on RESOURCES to provide RESOURCE_DESC.
• FND_DATE (PACKAGE) — supplies DATE_TO_DISPLAYDT for converting stored dates into display format.
• FND_TIMEZONES (PACKAGE) — supplies GET_SERVER_TIMEZONE_CODE, used as the conversion argument.

The join condition is CRM.RESOURCES = GBSR.RESOURCES, meaning every row returns a batch step resource record enriched with its master resource description. Four derived date columns are produced by wrapping PLAN_START_DATE, ACTUAL_START_DATE, PLAN_CMPLT_DATE, and ACTUAL_CMPLT_DATE in FND_DATE.DATE_TO_DISPLAYDT using the server time zone code.

Key Columns

• BATCHSTEP_RESOURCE_ID / BATCHSTEP_ACTIVITY_ID / BATCHSTEP_ID — keys identifying the resource assignment, its activity, and its parent batch step.
• BATCH_ID / ORGANIZATION_ID — links the record to the batch and the inventory organization.
• RESOURCES / RESOURCE_DESC — resource identifier and its descriptive text from CR_RSRC_MST.
• MIN_CAPACITY / MAX_CAPACITY / CAPACITY_TOLERANCE / CAPACITY_UM — capacity bounds and tolerance for the resource, with unit of measure.
• PLAN_RSRC_COUNT / ACTUAL_RSRC_COUNT, PLAN_RSRC_USAGE / ACTUAL_RSRC_USAGE, PLAN_RSRC_QTY / ACTUAL_RSRC_QTY — planned versus actual resource counts, usages, and quantities.
• PLAN_START_DATE, ACTUAL_START_DATE, PLAN_CMPLT_DATE, ACTUAL_CMPLT_DATE — raw dates, plus corresponding _DT display-formatted columns.
• PRIM_RSRC_IND, SCALE_TYPE, OFFSET_INTERVAL, CALCULATE_CHARGES, FIRM_TYPE, TEXT_CODE — resource behavior and scheduling attributes.
• GROUP_SEQUENCE_ID / GROUP_SEQUENCE_NUMBER, SEQUENCE_DEPENDENT_ID / SEQUENCE_DEPENDENT_USAGE — grouping and sequence dependency information.

Common Use Cases and Queries

Typical scenarios include batch resource inquiry screens, capacity validation reports, and extract programs feeding scheduling or cost analysis. The MIN_CAPACITY column is frequently queried to identify resources whose lower capacity bound must be respected during execution.

Example: retrieve capacity-bound resources for a batch.

• SELECT BATCH_ID, RESOURCES, RESOURCE_DESC, MIN_CAPACITY, MAX_CAPACITY, CAPACITY_UM
• FROM APPS.GME_BATCH_STEP_RESOURCES_V
• WHERE BATCH_ID = :p_batch_id
• ORDER BY BATCHSTEP_ID;

Example: compare planned and actual usage with capacity limits.

• SELECT BATCHSTEP_RESOURCE_ID, RESOURCES, PLAN_RSRC_USAGE, ACTUAL_RSRC_USAGE, MIN_CAPACITY, MAX_CAPACITY
• FROM APPS.GME_BATCH_STEP_RESOURCES_V
• WHERE ORGANIZATION_ID = :p_org_id
• AND ACTUAL_RSRC_USAGE > MIN_CAPACITY;

Because the view calls FND_DATE and FND_TIMEZONES per row, queries spanning large batch ranges should be filtered on BATCH_ID or ORGANIZATION_ID to limit the display-date conversion overhead.