Search Results scheduled_code

Overview

WIP_OPERATION_RESOURCES_INQ_V is a Work in Process (WIP) inquiry view owned by the APPS schema. As its documented description states, it supplies "additional data for WIP_OPERATION_RESOURCES," the base table that stores the resource requirements assigned to individual operations on discrete jobs and repetitive schedules. The view enriches the raw resource rows with decoded and denormalized attributes drawn from related WIP, BOM, and costing entities.

Its principal reporting role is to present operation-level resource information in a form that is directly consumable by inquiry screens, concurrent reports, and integration extracts. It resolves foreign-key lookups to human-readable values — status meanings, resource type and basis meanings, department and line codes, activity names, and autocharge codes — and it computes derived quantities that would otherwise require application logic. Because the view exposes internal identifiers such as ORGANIZATION_ID, WIP_ENTITY_ID, and REPETITIVE_SCHEDULE_ID together with descriptive columns, it serves equally well as a reporting source and as a data source for interfaces that must traverse from an entity to its operation resources.

Underlying Base Objects

The view text is defined with an ORDERED hint over WIP_OPERATION_RESOURCES (aliased WOR), which supplies the driving rows. It joins WIP_OPERATIONS (WO) on the operation sequence of the parent entity, and WIP_ENTITIES (WE) to obtain the job name and description, which are suppressed via DECODE when the entity is a repetitive schedule (ENTITY_TYPE = 2). WIP_DISCRETE_JOBS (WDJ) contributes status and scheduled start date for discrete jobs, while WIP_REPETITIVE_SCHEDULES (WRS) supplies the corresponding attributes for repetitive schedules, with NVL logic combining the two. WIP_LINES (WL) provides the line code, BOM_DEPARTMENTS (BD) the department code, BOM_RESOURCES (BR) the resource code, type, and description, CST_ACTIVITIES (CA) the activity name, and MFG_LOOKUPS (MF1 through MF5) the decoded meanings. The view therefore sits one logical layer above WIP_OPERATION_RESOURCES, consolidating its many parent and lookup relationships into a single flattened row per operation resource.

Key Columns

• ROW_ID — the ROWID of the underlying WIP_OPERATION_RESOURCES row, used as a stable row handle.
• ORGANIZATION_ID, WIP_ENTITY_ID, REPETITIVE_SCHEDULE_ID — the owning entity keys.
• JOB_NAME, JOB_DESCRIPTION, PRIMARY_ITEM_ID — entity identification, null for repetitive schedules.
• STATUS_TYPE, STATUS_CODE, LINE_ID, LINE_CODE, ENTITY_START_DATE, SCHEDULED_QUANTITY — job or schedule context.
• OPERATION_SEQ_NUM, OPERATION_DESCRIPTION, DEPARTMENT_ID, DEPARTMENT_CODE — the operation to which the resource is attached.
• RESOURCE_SEQ_NUM, RESOURCE_ID, RESOURCE_CODE, RESOURCE_TYPE, RESOURCE_TYPE_NAME — resource identity and classification.
• UOM_CODE, BASIS_TYPE, BASIS_CODE, USAGE_RATE_OR_AMOUNT, INVERSE — the usage basis and rate, with a reciprocal value where the rate is non-zero.
• SCHEDULED_UNITS — usage rate multiplied by scheduled quantity when the basis is per-item (BASIS_TYPE = 1).
• APPLIED_RESOURCE_UNITS — the quantity of resource units actually charged to the operation, nulled via DECODE when zero.
• REMAINING_UNITS — scheduled units less applied resource units, giving the outstanding resource balance.
• ACTIVITY_ID, ACTIVITY, SCHEDULED_FLAG, SCHEDULED_CODE, AUTOCHARGE_TYPE, AUTOCHARGE_CODE, STANDARD_RATE_FLAG — costing, scheduling, and charging attributes.

Common Use Cases and Queries

A frequent requirement is to inspect applied versus scheduled resource usage for open work orders, which directly answers searches on applied_resource_units:

• SELECT WIP_ENTITY_NAME, OPERATION_SEQ_NUM, RESOURCE_CODE, SCHEDULED_UNITS, APPLIED_RESOURCE_UNITS, REMAINING_UNITS FROM WIP_OPERATION_RESOURCES_INQ_V WHERE ORGANIZATION_ID = :org AND WIP_ENTITY_NAME = :job;
• Reporting by resource and department: aggregate USAGE_RATE_OR_AMOUNT and APPLIED_RESOURCE_UNITS grouped by DEPARTMENT_CODE and RESOURCE_CODE to review labor or machine loading.
• Filtering by entity type: use REPETITIVE_SCHEDULE_ID IS NULL to isolate discrete jobs, or LINE_CODE for repetitive schedules.
• Integration extracts: retrieve RESOURCE_ID, BASIS_TYPE, UOM_CODE, and AUTOCHARGE_TYPE for the resource requirements of a job to feed planning or cost simulation logic.
• Variance analysis: compare REMAINING_UNITS against zero to identify under- or over-applied resources before closing an operation.

Because the view resolves lookups and computes derived columns at query time, consumers should apply organization and entity predicates to limit the row set, and should not expect to update data through it.