eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.OTA_CLASSIC_UPGRADE dependencies on OTA_BOOKING_DEALS

Line 695: -- 1. Updates ota_booking_deals.category with category_usage_id

691: -- ----------------------------------------------------------------------------
692: -- |---------------------------< Upgrade_Category >----------------------------|
693: -- ----------------------------------------------------------------------------
694: -- This procedure does the following :
695: -- 1. Updates ota_booking_deals.category with category_usage_id
696: -- 2. Updates ota_category_usages.Category with Meaning from
697: -- lookup table (earlier it stores lookup code)
698: -- 3. Populates the category translation table ota_category_usages_tl
699: -- 4. Migrates the customer defined lookup codes(not seeded) from FREQUNCY to

Line 732: /* In Ota_booking_deals table Category field was the equivalent lookup_code

728: l_process_date ota_upgrade_log.process_date%Type;
729:
730: begin
731:
732: /* In Ota_booking_deals table Category field was the equivalent lookup_code
733: for the lookup_type 'ACTIVITY_CATEGORY'. Now Category_usage_id is being stored in this field
734: */
735: --Should this check be included here?
736: begin

Line 737: UPDATE ota_booking_deals tbd

733: for the lookup_type 'ACTIVITY_CATEGORY'. Now Category_usage_id is being stored in this field
734: */
735: --Should this check be included here?
736: begin
737: UPDATE ota_booking_deals tbd
738: SET tbd.category = (select ocu.category_usage_id
739: from ota_category_usages ocu
740: where tbd.category = ocu.category
741: and tbd.business_group_id = ocu.business_group_id