Search Results fm_department_code

Overview

The APPS.WIP_MOVE_TRANSACTIONS_V view is a denormalized reporting object within the Work in Process (WIP) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its stated purpose, per the ETRM metadata, is to supply "foreign-key data for WIP_MOVE_TRANSACTIONS." In practical terms, the view presents each move transaction row from the base table enriched with the descriptive, human-readable values that the base table stores only as numeric identifiers. Rather than returning ORGANIZATION_ID, WIP_ENTITY_ID, LINE_ID, department IDs, or reason IDs alone, the view resolves these into organization codes, entity names, line codes, department codes, and reason names.

Because move transactions are the mechanism by which material is moved from one operation to the next on a discrete job or repetitive schedule, this view is central to shop-floor reporting, transaction auditing, and downstream integration extracts. It is owned by APPS and carries a VALID status.

Underlying Base Objects

The view is defined over the following documented referenced objects:

• WIP_MOVE_TRANSACTIONS (SYNONYM) — the driving base table, aliased WMT.
• WIP_ENTITIES (SYNONYM) — aliased WE, joined on WIP_ENTITY_ID to supply the entity name.
• WIP_LINES (SYNONYM) — aliased WL, supplying the production line code.
• BOM_DEPARTMENTS (SYNONYM) — joined twice as BD1 and BD2 to resolve the from (FM) and to (TO) department codes.
• MFG_LOOKUPS (VIEW) — joined twice as ML1 and ML2 to resolve intraoperation step types into meanings.
• MTL_TRANSACTION_REASONS (SYNONYM) — aliased MTR, resolving REASON_ID to a reason name.
• MTL_PARAMETERS (SYNONYM) — aliased MP, providing the organization code.
• HR_ALL_ORGANIZATION_UNITS (SYNONYM) — aliased HAOU, providing the organization name.

Joins are keyed on WIP_ENTITY_ID and ORGANIZATION_ID, with the department and lookup tables joined by their respective foreign keys on the move transaction row.

Key Columns

The view carries all transactional columns of WIP_MOVE_TRANSACTIONS plus the following resolved descriptive columns of particular reporting value:

• ROW_ID — the ROWID of the base row, useful for correlated updates.
• ORGANIZATION_CODE and ORGANIZATION_NAME — from MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS.
• WIP_ENTITY_NAME — job or schedule identifier.
• LINE_CODE — repetitive line code.
• FM_DEPARTMENT_CODE — the department code for the "from" department, resolved from BOM_DEPARTMENTS via FM_DEPARTMENT_ID. This is the column most commonly sought when users search on this view.
• TO_DEPARTMENT_CODE — the destination department code.
• FM_INTRAOPERATION_STEP_MEANING and TO_INTRAOPERATION_STEP_MEANING — decoded step types (for example, Queue, Run, To Move, Scrap) from MFG_LOOKUPS.
• REASON_NAME — scrap or rejection reason text.
• TRANSACTION_QUANTITY, PRIMARY_QUANTITY, transaction and primary UOMs, and overcompletion quantities.

Common Use Cases and Queries

Typical uses include shop-floor movement history, scrap analysis by department, WIP reconciliation, and feeder extracts into data warehouses. A representative query resolving department movement follows:

SELECT t.wip_entity_name,
  t.organization_code,
  t.fm_department_code,
  t.to_department_code,
  t.fm_intraoperation_step_meaning,
  t.transaction_quantity,
  t.transaction_date
FROM apps.wip_move_transactions_v t
WHERE t.organization_id = :org_id
  AND t.transaction_date >= :from_date
  AND t.fm_department_code = :department_code
ORDER BY t.transaction_date;

Because the view performs several outer-style lookups over dimension tables, it is best queried with selective filters on ORGANIZATION_ID, WIP_ENTITY_ID, or date to constrain the driving set. For high-volume extracts, filtering on the base table first and joining the view by TRANSACTION_ID often yields better performance than scanning the view directly.