APPS.CSTPPWRO dependencies on WIP_TXN_ALLOCATIONS

Line 464: -- all schedules in wip_txn_allocations tables for a given

460: -- cause schedules can have different routing (and operations).
461: -- We need to know exactly which operations of the routing
462: -- are being charged. We can only have rollforward or rollbackward
463: -- between schedules that have the same routing. In other words,
464: -- all schedules in wip_txn_allocations tables for a given
465: -- wip_transaction_id WILL HAVE THE SAME ROUTING.
466: -- WIP_MOVE_TRANSACTIONS table does not store rep schedule_id
467: -- therefore the only way to find the schedule (and thus the
468: -- routing) for which this move transaction is being done is to

Line 591: FROM wip_txn_allocations wip_alloc

587: l_stmt_num := 18;
588:
589: SELECT NVL(MAX(wip_alloc.repetitive_schedule_id),-99)
590: INTO l_rep_sched_id
591: FROM wip_txn_allocations wip_alloc
592: WHERE wip_alloc.transaction_id = l_wt;
593:
594: END IF; --check to see if it is rep sched
595: /*End of Move from l_stmt_num := 55*/

Line 1152: FROM wip_txn_allocations wip_alloc

1148: AND cdo.overhead_id = wta.resource_id
1149: AND cdo.cost_type_id = p_pac_ct_id
1150: AND NVL(wta.repetitive_schedule_id,-99) =
1151: (SELECT NVL(MAX(wip_alloc.repetitive_schedule_id),-99)
1152: FROM wip_txn_allocations wip_alloc
1153: WHERE wip_alloc.transaction_id = wt.transaction_id
1154: AND rownum = 1
1155: )
1156: AND cdo.rate_or_amount <> 0