APPS.OE_CANCEL dependencies on CS_CP_SERVICE_TRANSACTIONS

Line 351: -- CS_CP_SERVICE_TRANSACTIONS (sort of history)

347: -- CS_CUSTOMER_PRODUCTS (products)
348: -- /|\
349: -- CS_CP_SERVICES (service)
350: -- /|\
351: -- CS_CP_SERVICE_TRANSACTIONS (sort of history)
352: --
353: -- Two possible situations can occur and hence the need to have
354: -- two separate sql checks. The first sql statement takes care
355: -- of the situation in which a service is associated with a product

Line 361: -- CS_CP_SERVICES to CS_CP_SERVICE_TRANSACTIONS.

357: -- by a join on CS_CUSTOMER_PRODUCTS and CS_CP_SERVICES.
358: -- The second possiblity is that service was ordered by itself,
359: -- a standalone service if you will. This would not have any
360: -- record in CS_CUSTOMER_PRODUCTS and hence the need to join
361: -- CS_CP_SERVICES to CS_CP_SERVICE_TRANSACTIONS.
362: --
363: -- RETURNS:
364: -- 1 -> if order is not cancellable
365: -- 0 -> if order is cancellable

Line 414: CS_CP_SERVICE_TRANSACTIONS TRX

410:
411: SELECT COUNT(*)
412: INTO DUMMY2
413: FROM CS_CP_SERVICES SER,
414: CS_CP_SERVICE_TRANSACTIONS TRX
415: WHERE TRX.SERVICE_ORDER_LINE_ID = V_LINE_ID
416: AND TRX.CP_SERVICE_ID = SER.CP_SERVICE_ID
417: AND SYSDATE BETWEEN SER.START_DATE_ACTIVE AND SER.END_DATE_ACTIVE;
418: