0 Replies Latest reply on Aug 24, 2018 1:08 PM by LPNO

    OWB import/deploy view without import of dependant objects

    LPNO

      Just gaining my first taste of OWB-deployment. I have imported some views in the source module. All veryifies ok. Then while deploying, OWB gets a bunch full of errors.

      Problem seems to be, that OWB tries to generate the view without wrapping the dependent object with a DB-Link to the sourcesystem. Just the motivation for me of using views is information hidding. I don't wan't to import all those other views and tables from the sourcesystem, the view is dependant of. OWB should just ask me for a DB-Link to the source system. add that DB-Link to all dependent objects that remain in the source system and then just deploy happily to the target sytem. Therefore such a DDL-code should generate the view that refers to dependant object on the source system.

       

      Sample DDL - as generated from OWB by it's imported metadata, I just added the DB-LInks manually. to hilight the indented target-DDL intended to be generated by OWB

       

      CREATE OR REPLACE  VIEW  "XXX_MTL_CAT_CATEGORIES_V"
      AS select cs.CATEGORY_SET_ID
      ,cs.STRUCTURE_ID
      ,cs.CATEGORY_SET
      ,mc.CATEGORY_ID
      ,cs.DESCRIPTION CS_DESCRIPTION
      ,cs.VALIDATE_FLAG
      ,mc.DESCRIPTION  CAT_DESCRIPTION
      ,mcl.DESCRIPTION
      ,mc.DISABLE_DATE
      ,mc.SEGMENT1
      ,mc.SEGMENT2
      ,mc.SEGMENT3
      ,mc.SEGMENT4
      ,mc.SEGMENT5
      ,mc.SEGMENT20
      ,mc.SUMMARY_FLAG SUMMARY_FLG
      ,mc.ENABLED_FLAG ENABLED_FLG
      ,mc.SUPPLIER_ENABLED_FLAG SUPPLIER_ENABLED_FLG
      ,mc.START_DATE_ACTIVE
      ,mc.END_DATE_ACTIVE
      ,mc.ATTRIBUTE_CATEGORY
      ,mc.ATTRIBUTE1
      ,mc.ATTRIBUTE2
      ,mc.ATTRIBUTE3
      ,mc.ATTRIBUTE4
      ,mc.ATTRIBUTE5
      ,mc.ATTRIBUTE15
      ,mc.LAST_UPDATE_DATE
      ,mc.LAST_UPDATED_BY
      ,mc.CREATION_DATE
      ,mc.CREATED_BY
      ,mc.LAST_UPDATE_LOGIN
      ,mc.WEB_STATUS
      ,mcl.LANGUAGE
      ,mcl.SOURCE_LANG
       from mtl_categories_b@XXXP01.WORLD mc, mtl_categories_tl@XXXP01.WORLD mcl, XXX_MTL_CAT_category_sets_v@XXXP01.WORLD cs
                where 
       mc.category_id = mcl.category_id
                AND mcl.LANGUAGE = SYS_CONTEXT ('USERENV', 'LANG')
                and mc.structure_id = cs.structure_id;
      
      
      
      
      

       

       

      Do I muss something?

      How can I get OWB to act and deploy in this direction of my indention?

       

      My DEV-Plattform

      OWB Version 11.2.0.4 Sourcesystem:

      Oracle APPS ERP 12.1

      Targetsystem Oracle 12c Enterprise Edition