DBA Data[Home] [Help]

APPS.RCV_AVAILABILITY dependencies on RCV_TRANSACTIONS_INTERFACE

Line 34: FROM rcv_transactions_interface

30: WHERE processing_status_code = 'PENDING';
31:
32: CURSOR get_rti_rows IS
33: SELECT *
34: FROM rcv_transactions_interface
35: WHERE processing_status_code = 'PENDING';
36: BEGIN
37: IF (g_rti_normalized IS NOT NULL) THEN --because this is expensive, we only want to run it once per session
38: RETURN;

Line 236: to receipts/shipments in RCV_TRANSACTIONS_INTERFACE that apply

232: get_rcv_ship_row, get_rcv_po_row are all the same query, but
233: with different driving where clauses. The cursor used is
234: determined by p_supply_demand_type_id. The cursors return all
235: the rows in RCV_SHIPMENT_LINES and all the receipts/+correction
236: to receipts/shipments in RCV_TRANSACTIONS_INTERFACE that apply
237: to the backing doc
238:
239: The parameters p_organization_id, p_item_id, p_revision,
240: p_lot_number, p_subinventory_code, p_locator_id, p_project_id,

Line 273: FROM rcv_transactions_interface rti,

269: rti.item_id,
270: rti.unit_of_measure,
271: rti.primary_unit_of_measure,
272: rti.to_organization_id
273: FROM rcv_transactions_interface rti,
274: rcv_transactions rt
275: WHERE rti.parent_transaction_id = rt.transaction_id(+)
276: AND rti.quantity > 0
277: AND ( rti.transaction_type IN('RECEIVE', 'SHIP', 'DELIVER')

Line 360: FROM rcv_transactions_interface rti,

356: rti.item_id,
357: rti.unit_of_measure,
358: rti.primary_unit_of_measure,
359: rti.to_organization_id
360: FROM rcv_transactions_interface rti,
361: rcv_transactions rt
362: WHERE rti.parent_transaction_id = rt.transaction_id(+)
363: AND rti.quantity > 0
364: AND ( rti.transaction_type IN('RECEIVE', 'SHIP', 'DELIVER')

Line 458: FROM rcv_transactions_interface rti,

454: rti.item_id,
455: rti.unit_of_measure,
456: rti.primary_unit_of_measure,
457: rti.to_organization_id
458: FROM rcv_transactions_interface rti,
459: rcv_transactions rt
460: WHERE rti.parent_transaction_id = rt.transaction_id(+)
461: AND rti.quantity > 0
462: AND ( rti.transaction_type IN('RECEIVE', 'SHIP', 'DELIVER')

Line 568: FROM rcv_transactions_interface rti,

564: rti.item_id,
565: rti.unit_of_measure,
566: rti.primary_unit_of_measure,
567: rti.to_organization_id
568: FROM rcv_transactions_interface rti,
569: rcv_transactions rt
570: WHERE rti.parent_transaction_id = rt.transaction_id(+)
571: AND ( rti.quantity > 0
572: OR (rti.quantity < 0 AND rti.transaction_type = 'CORRECT')

Line 754: rcv_transactions_interface (RTI) and rcv_shipment_lines (RSL).

750:
751: /*
752: The logic below first defaults x_rcv_order_quantity from the
753: backing docs. It then loops through all the rows in
754: rcv_transactions_interface (RTI) and rcv_shipment_lines (RSL).
755: If the row is in RSL then it increases the running value of
756: x_rcv_quantity by shipped_quantity for non-wms orgs and increases the value
757: of x_rcv_quantity by received_quantity for wms orgs. We know that RSL's
758: shipped_quantity and receipt_quantity are an accurate summation of all rcv_transaction