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 191: to receipts/shipments in RCV_TRANSACTIONS_INTERFACE that apply

187: get_rcv_ship_row, get_rcv_po_row are all the same query, but
188: with different driving where clauses. The cursor used is
189: determined by p_supply_demand_type_id. The cursors return all
190: the rows in RCV_SHIPMENT_LINES and all the receipts/+correction
191: to receipts/shipments in RCV_TRANSACTIONS_INTERFACE that apply
192: to the backing doc
193:
194: The parameters p_organization_id, p_item_id, p_revision,
195: p_lot_number, p_subinventory_code, p_locator_id, p_project_id,

Line 228: FROM rcv_transactions_interface rti,

224: rti.item_id,
225: rti.unit_of_measure,
226: rti.primary_unit_of_measure,
227: rti.to_organization_id
228: FROM rcv_transactions_interface rti,
229: rcv_transactions rt
230: WHERE rti.parent_transaction_id = rt.transaction_id(+)
231: AND rti.quantity > 0
232: AND ( rti.transaction_type IN('RECEIVE', 'SHIP', 'DELIVER')

Line 315: FROM rcv_transactions_interface rti,

311: rti.item_id,
312: rti.unit_of_measure,
313: rti.primary_unit_of_measure,
314: rti.to_organization_id
315: FROM rcv_transactions_interface rti,
316: rcv_transactions rt
317: WHERE rti.parent_transaction_id = rt.transaction_id(+)
318: AND rti.quantity > 0
319: AND ( rti.transaction_type IN('RECEIVE', 'SHIP', 'DELIVER')

Line 413: FROM rcv_transactions_interface rti,

409: rti.item_id,
410: rti.unit_of_measure,
411: rti.primary_unit_of_measure,
412: rti.to_organization_id
413: FROM rcv_transactions_interface rti,
414: rcv_transactions rt
415: WHERE rti.parent_transaction_id = rt.transaction_id(+)
416: AND rti.quantity > 0
417: AND ( rti.transaction_type IN('RECEIVE', 'SHIP', 'DELIVER')

Line 523: FROM rcv_transactions_interface rti,

519: rti.item_id,
520: rti.unit_of_measure,
521: rti.primary_unit_of_measure,
522: rti.to_organization_id
523: FROM rcv_transactions_interface rti,
524: rcv_transactions rt
525: WHERE rti.parent_transaction_id = rt.transaction_id(+)
526: AND ( rti.quantity > 0
527: OR (rti.quantity < 0 AND rti.transaction_type = 'CORRECT')

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

700:
701: /*
702: The logic below first defaults x_rcv_order_quantity from the
703: backing docs. It then loops through all the rows in
704: rcv_transactions_interface (RTI) and rcv_shipment_lines (RSL).
705: If the row is in RSL then it increases the running value of
706: x_rcv_quantity by shipped_quantity for non-wms orgs and increases the value
707: of x_rcv_quantity by received_quantity for wms orgs. We know that RSL's
708: shipped_quantity and receipt_quantity are an accurate summation of all rcv_transaction