APPS.OE_CANCEL dependencies on CS_CUSTOMER_PRODUCTS

Line 347: -- CS_CUSTOMER_PRODUCTS (products)

343: -- cancelled. This procedure contains the required checks that
344: -- are not covered by security rules.
345: -- Specifically it handles service checks
346: --
347: -- CS_CUSTOMER_PRODUCTS (products)
348: -- /|\
349: -- CS_CP_SERVICES (service)
350: -- /|\
351: -- CS_CP_SERVICE_TRANSACTIONS (sort of history)

Line 357: -- by a join on CS_CUSTOMER_PRODUCTS and CS_CP_SERVICES.

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
356: -- and checks to see if the service is still active. This is done
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.

Line 360: -- record in CS_CUSTOMER_PRODUCTS and hence the need to join

356: -- and checks to see if the service is still active. This is done
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

Line 389: CS_CUSTOMER_PRODUCTS CPS

385:
386: SELECT COUNT(*)
387: INTO DUMMY
388: FROM CS_CP_SERVICES SER,
389: CS_CUSTOMER_PRODUCTS CPS
390: WHERE SER.CUSTOMER_PRODUCT_ID = CPS.CUSTOMER_PRODUCT_ID
391: AND CPS.ORIGINAL_ORDER_LINE_ID IN
392: (SELECT LINE_ID FROM SO_LINES
393: WHERE PARENT_LINE_ID = V_REAL_PARENT_LINE_ID