DBA Data[Home] [Help]

APPS.ICX_CAT_CNTNT_SCRTY_UPG_PVT dependencies on POR_NONCAT_TEMPLATES_ALL_B

Line 2203: -- there is little data migration, as por_noncat_templates_all_b is still

2199: END migrate_isrc_with_realms;
2200:
2201:
2202: -- Migrates all info-templates over to Smart Forms for R12. In actuality,
2203: -- there is little data migration, as por_noncat_templates_all_b is still
2204: -- being used. So, only the relationship to the store is considered, where
2205: -- the smart form must be added to the new R12 store if the smart form
2206: -- via is org_id field is accessible via the old store's operating units
2207: -- restrictions, if any. The default template is skipped.

Line 2235: FROM icx_cat_store_catalogs sc, por_noncat_templates_all_b templates,

2231: BEGIN
2232:
2233: SELECT templates.template_id, sc.store_id
2234: BULK COLLECT INTO l_template_ids, l_old_store_ids
2235: FROM icx_cat_store_catalogs sc, por_noncat_templates_all_b templates,
2236: icx_cat_store_org_assignments orgs
2237: WHERE templates.template_id = sc.item_source_id
2238: AND sc.store_id = orgs.store_id
2239: AND orgs.org_id IN (templates.org_id, -2)

Line 2953: -- being migrated (they say in por_noncat_templates_all_b), so no need for

2949: -- That is, for each index, the smart form at that index will be added to
2950: -- the store add that index. This is used to quickly add multiple
2951: -- smart forms to multiple stores. This is handled by a FORALL statement.
2952: -- Unlike content zones, smart forms keep the same ID since they are not
2953: -- being migrated (they say in por_noncat_templates_all_b), so no need for
2954: -- a corresponding "old_template_id" as with the content zones.
2955: --
2956: -- @param p_zone_ids List of Smart Form IDs to add to the stores.
2957: -- @param p_r12_store_ids The R12 Stores IDs to which the zones are to be added.