Results for “physical_adjustment_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CSP_PICK_TRANSACTIONS_V is a read-only reporting view owned by the APPS schema within the CSP (Spares Management) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. As its documented description states, the view exposes "Material Transactions and Picklist information," consolidating transactional material movement data with the picklist context used during spares fulfillment and shipping operations. Because CSP integrates with Oracle Inventory and Oracle Shipping, this view serves as a convenient single source for pick-confirm activity, transaction reconciliation, and downstream accounting review. It is a view, not a table, so no direct DML is permitted; consumers must treat it strictly as a query surface for reporting, extracts, and interface validation. Its role is particularly relevant to transportation and freight accounting, since it surfaces the TRANSPORTATION_ACCOUNT and TRANSPORTATION_COST columns alongside the originating picklist line information.

Underlying Base Objects

Per the 12.2.2 ETRM metadata, the view is defined over four referenced base objects:

• CSP_PICKLIST_HEADERS (synonym) — supplies picklist header context, including organizational and status attributes.
• CSP_PICKLIST_LINES (synonym) — provides picklist line detail, including PICKING_LINE_ID.
• MTL_MATERIAL_TRANSACTIONS_TEMP (synonym) — the material transaction staging table (aliased MMTT in the view text), which is the dominant source of columns.
• MTL_SECONDARY_INVENTORIES (synonym) — supplies subinventory-level attributes for the material being transacted.

The view text confirms the primary alias MMTT and returns the physical ROWID of the underlying material transaction row, enabling correlated updates or diagnostics against MTL_MATERIAL_TRANSACTIONS_TEMP where permissible.

Key Columns

The view projects a broad set of MTL_MATERIAL_TRANSACTIONS_TEMP columns. Notable columns include:

• TRANSACTION_HEADER_ID / TRANSACTION_TEMP_ID — identifiers linking the transaction to its header and temporary staging record.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, SUBINVENTORY_CODE, LOCATOR_ID — the inventory coordinates of the movement.
• TRANSACTION_QUANTITY, PRIMARY_QUANTITY, TRANSACTION_UOM — the quantity transacted and its unit of measure.
• TRANSACTION_DATE, ACCT_PERIOD_ID — the effective date and the accounting period for costing.
• DISTRIBUTION_ACCOUNT_ID — the inventory distribution account charged.
• TRANSPORTATION_COST, TRANSPORTATION_ACCOUNT, FREIGHT_CODE, TRANSFER_COST — freight and transfer costing elements, including the transportation account referenced frequently in freight reconciliation queries.
• SHIP_TO_LOCATION, SHIPMENT_NUMBER — shipping destination and shipment reference.
• PICKING_LINE_ID — the link back to the picklist line that generated the transaction.
• LOT_NUMBER, SERIAL_NUMBER, REVISION — item instance controls for controlled inventory.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, REQUEST_ID, PROGRAM_ID) — audit and concurrent program traceability.

Common Use Cases and Queries

Typical scenarios include reconciling pick-confirmed transactions to picklist lines, validating freight account postings, and auditing material movement by period or organization. A representative query isolating transportation charges is shown below.

• Review transportation cost and account by organization:
  SELECT organization_id, inventory_item_id, transaction_quantity, transportation_cost, transportation_account FROM apps.csp_pick_transactions_v WHERE transportation_account IS NOT NULL;
• Reconcile picklist lines to transactions:
  SELECT picking_line_id, transaction_header_id, transaction_date FROM apps.csp_pick_transactions_v WHERE picking_line_id = :p_picking_line_id;
• Period-based freight analysis:
  SELECT acct_period_id, SUM(transportation_cost) FROM apps.csp_pick_transactions_v GROUP BY acct_period_id;

Because the view is unsupported for DML and built on transaction staging data, queries should be scoped by organization and date to limit result volume in high-volume spares environments.