APPS.OE_COMMITMENT_UTIL dependencies on OE_ORDER_LINES

Line 14: -- Note: The sql is selecting from oe_order_lines instead of oe_payments

10: -- This procedure is provided to be called by OTA team.
11: -- Abstract: given a line id, return the
12: -- commitment id, number, start date and end date.
13: -- Return NULL when there is no commitment on the line.
14: -- Note: The sql is selecting from oe_order_lines instead of oe_payments
15: -- This is fine for now while we're still storing the commitment id
16: -- in oe_order_lines. This is done to avoid having odf files in
17: -- the patch.
18: ----------------------------------------

Line 16: -- in oe_order_lines. This is done to avoid having odf files in

12: -- commitment id, number, start date and end date.
13: -- Return NULL when there is no commitment on the line.
14: -- Note: The sql is selecting from oe_order_lines instead of oe_payments
15: -- This is fine for now while we're still storing the commitment id
16: -- in oe_order_lines. This is done to avoid having odf files in
17: -- the patch.
18: ----------------------------------------
19:
20: PROCEDURE Get_Commitment_Info

Line 48: FROM oe_order_lines oe

44: , x_commitment_number
45: , x_commitment_start_date
46: , x_commitment_end_date
47:
48: FROM oe_order_lines oe
49: , ra_customer_trx_all ra
50:
51: WHERE oe.commitment_id = ra.customer_trx_id
52: AND line_id = p_line_id