Package in owb views

In OWB 10.2 views, all_iv_functions,for a particular function, we get the package names as a function library name.
These packages are created in a project,but the schema id for the packages in the the above view is blank.
How can we get the information as to which module the package belongs to.
Thanks ...

you should be able to find this in owb_repowner schema

Similar Messages

Package and class viewer

Hello,
Is there an equivalent of a menu item or short-cut key to bring up package and class viewer? A similar feature exists in Eclipse which builds the indexes and Ctrl-Shift-T will bring up all the classes in your workspace / project. I have seen something similar in Jdeveloper while running in debug mode, if it cannot find a file that is need for trace options, it throws up a window that says "Package and Class Viewer". It would be useful to access that during development as well.
Thanks
Farooq.

Thanks for the repose. Ctrl+ , along with Ctrl= is doing the same thing. Also discovered Ctrl- will bring up java classes. Only thing remains is the remaining files in the project e.g XML or JSP files
Thanks for you, got me in the right direction.

How to change the package name of View or Window

Hi all,
i have created the Webdynpro Application.i have some Views and Windows in the WebDynpro Peoject.i want to change the package Names of Views.is it possible???
thanks in advance
regards
Naidu

Hi Naidu
Though you rename the package name, the view in that package refers to the old package and hence that view can be used in other views by including the old package name only. Renaming doesn't have significance that you expect. You can create a new package and views in it and copy the implementation of views from the old package to the views in the new package.
Regards
Vijayakhanna Raman

To Generate Oracle Package from OWB *.mdl file

Hi,
I want to generate an Oracle Package from OWB *.mdl file. I know this can be done using the OWB GUI. But is there a way to automate this using a script for a given set of mappings?
Such a thing is required because I have a large number of mappings and i need to create the Oracle package scripts for the same.

Hi borkur,
As you told I tried the same in OMBPlus. I created a file called "comp_src.txt" with the following code:
proc compile_mappings {} {
OMBCONNECT owbrepos/owbrepos@blrkec20974d:1521:FDMD1B
OMBCC 'FDM/BOE'
OMBCOMPILE MAPPING 'BOE_EXPN_POPULATE_IU_1' OUTPUT VALIDATION_RESULT TO '/nav' WRITE
SUCCESS
OUTPUT GENERATION_SCRIPTS TO '/nav'.
OMBCOMPILE TABLE 'T1' OUTPUT GENERATION_SCRIPTS TO '/nav'
But i am getting an error message as below:
OMB+> source C:/oracle/ora93/owb/bin/win32/comp_src.txt
OMB+> compile_mappings
Cannot establish connection in single-user mode!
OMB+>
I am new to OMBPlus and i came to know that Multi-user mode is default. Then why i am getting this error (Cannot establish connection in single-user mode!)
Regards,
Naveen

Importing a package into OWB repository.

Hi,
there is a package existing in my OWB repository.
Package ABC
Procedure PQR(pram1 varchar2,param2 varchar2)
now i have modified this package in my target schema, an extra parameter is added to the procedure PQR.
Procedure PQR(pram1 varchar2,param2 varchar2,param3 number).
now when I re import this package to my OWB repository module. it shows both versions of the procedures.
Package ABC
PQR(pram1 varchar2,param2 varchar2)
PQR(pram1 varchar2,param2 varchar2,param3 number)
PQR(pram1 varchar2,param2 varchar2) is still vsible in OWB repository though it is replaced with PQR(pram1 varchar2,param2 varchar2,param3 number) in target schema.
Is there any way I can replace the old version of procedure with the new version in OWB repository.
Regards
RD_RBS

Hi
Standard approach to be followed for any object modification
1. If you have created your package from OWB and deployed it into your DB, always do it that way i.e. Design center -->DB . Do not make any modifications on DB level and import in back to your Design center. OWB manages Ids for all objects on the repository and this will confuse it. That is why you see two versions of the same package . Any modifications should be done on Design center level and then do a replace on the package from control center
2. If an object (package or procedure) is created on DB directly and is imported into design center, follow the same norm everytime you make any changes to that object. The status of that object will appear as "New" or "Not deployed" on control center but that is fine because OWB has no ID on its repository to maintain this information.
3. If you need to rename any object already deployed from OWB, always drop it first, then rename it and then deploy it. That way OWB will maintain the name and ID on its end and not get confused.
4. For your case, you can drop the older version of the package from OWB, delete the one imported from Database into OWB, make the changes on OWB level (adding parameter etc) and then redeploy the same package as replace from control center.
Hope these tips help
birdy

Argument Order Reversed Importing Package into OWB

I'm having a problem importing Packages into OWB. It recognizes the Functions contained in the Package, however the order of the arguments for each Function are reversed after I complete the import into OWB. This causes execution of the mapping to fail... Additionally, after importing into OWB, OWB doesn't seem to recognize any optional parameters or default values in the signature of the Function. I must be doing something wrong... Can anyone help...
Thanks
Alan

Hi
Standard approach to be followed for any object modification
1. If you have created your package from OWB and deployed it into your DB, always do it that way i.e. Design center -->DB . Do not make any modifications on DB level and import in back to your Design center. OWB manages Ids for all objects on the repository and this will confuse it. That is why you see two versions of the same package . Any modifications should be done on Design center level and then do a replace on the package from control center
2. If an object (package or procedure) is created on DB directly and is imported into design center, follow the same norm everytime you make any changes to that object. The status of that object will appear as "New" or "Not deployed" on control center but that is fine because OWB has no ID on its repository to maintain this information.
3. If you need to rename any object already deployed from OWB, always drop it first, then rename it and then deploy it. That way OWB will maintain the name and ID on its end and not get confused.
4. For your case, you can drop the older version of the package from OWB, delete the one imported from Database into OWB, make the changes on OWB level (adding parameter etc) and then redeploy the same package as replace from control center.
Hope these tips help
birdy

OWB View validation??

OWB View validation??
We are using OWB repository 10.2.0.2.0 and OWB client 10.2.0.2.8. The Oracle version is 10 G (10.2.0.2.0). OWB is installed on Sun 64 bit server.
We created view in OWB mapping. The validation was successful. As we deploy the view, we are getting errors such as Table/view does not exist, numeric errors etc.
Why does not view validation pick upuch errors?
Did any one in this forum face such issues?
Any idea?
Thanks in advance.
RI

Hello RI,
Creating views as a target in a mapping is only available from 10.2.0.3 and i thougt not in your version!
You could create views in your version, but not in a mapping and you would have to paste the self developed sql in your view definition!

OWB View Issue.

am having a mapping which contains a view. The view is run on a
remote database and the mapping uses the view data as a source.
When i execute the mapping, i get 0 rows from the view.
However when i execute the view on the remote database
i get data from it.
I have deleted the view in the remote DB to see whether the
DB link was pointing to the correct view or source or not.
Infact the mapping package gives an error which shows that
its poining to the right view.
I have created a temp table in the remote DB and i source the
view to this temp table. In this case the data is captured.
I am not sure why the view is not running in the view format.
Any mapping configuration to be altered.
I am on OWB 9.2.0.4

Have you tried to use "generate intermediate results" on your source view in your mapping and copied the SQL statement in a tool like TOAD to verify the correct SQL is executed?
Regards,
Jörg

Mapping Code ( packages in owb)

hi all,
Kindly any body to clarify this question
I had experience in informatica 1+yrs only mapping exp But right now i am working in owb 10g Here i am getting mapping code as a pacages but informatica where i will get the information of the code information. Please any one try to explain or otherwise any body experience on this ask them and send a mail.
Regards
Vijayan

Hopefully, I have understood this question correctly. OWB generates all the code via PL/SQL packages as PL/SQL is the most performant way to interact with the database. You can control the type of code generated using various data object properties as well as generation properties that let you create either:
Set based
Set based fail over to row
Set based fail over to row based target only
Row based
Row based target only
Within the mapping editor you can view the generated code directly within the "Generation Results" window once you select the "Generate" option from the Mapping menu. This is the code that will get deployed to your target schema.
Hopefully this answers your question
Keith

How to use the Table Function defined in package in OWB?

Hi,
I defined a table function in a package. I am trying to use that in owb using Table function operator. But I came to know that, owb R1 supports only standalone table functions.
Is there any other way to use the table function defined in a package. As like we create synonyms for functions, is there any other way to do this.
I tryed to create synonyms, it is created. But it is showing compilation error. Finally I found that, we can't create synonyms for functions which are defined in packages.
Any one can explain it, how to resolve this problem.
Thank you,
Regards
Gowtham Sen.

Hi Marcos,
Thank you for reply.
OWB R1 supports stand alone table functions. Here what I mean is, the table fucntion which is not inculded in any package is a stand alone table function.
for example say sample_tbl_fn is a table function. It is defined as a function.It is a stand alone function. We call this fucntion as "samp_tbl_fn()";
For exampe say sample_pkg is a package. say a function is defined in a package.
then we call that function as sample_pkg.functionname(); This is not a stand alone function.
I hope you understand it.
owb supports stand alone functions.
Here I would like to know, is there any other way to use the functions which are defined in package. While I am trying to use those functions (which are defined in package -- giving the name as packagename.functionname) it is throwing an error "Invalid object name."
Here I would like know, is there any other way to use the table functions which are defined in a package.
Thank you,
Regards,
Gowtham Sen.

Import package and create view object

Hi,
How can i import package from another project and create a new view object with my package and with the imported package.
Thanks
null

Hi,
How can i import package from another project and create a new view object with my package and with the imported package.
Thanks
null

R12 - Compile Invalid objects (Fast Formula, Package Body and View) Urgent

Invalid objects about 43, in this Fast Formula 2 AP Package object, and 1 view
OWNER     OBJECT_TYPE     COUNT(*)
APPS     PACKAGE BODY     37.00
APPS     PROCEDURE     1.00
SCOTT     PACKAGE BODY     1.00
APPS     VIEW     1.00
APPS     FUNCTION     3.00
any one can give idea to make it valid.
Awaiting for your reply.
FYI
the object list is below.
OWNER     OBJECT_NAME
APPS     FFP52474_01010001
APPS     FFP61059_01010001
APPS     FFP56168_01010001
APPS     FFP56167_01010001
APPS     FFP58579_01052004
APPS     FFP56169_01010001
APPS     FFP56170_01010001
APPS     FFP56171_01010001
APPS     FFP56172_01010001
APPS     FFP56173_01010001
APPS     FFP60309_01010001
APPS     FFP60306_01010001
APPS     FFP60308_01010001
APPS     FFP60310_01010001
APPS     FFP60307_01010001
APPS     AP_IMPORT_VALIDATION_PKG
APPS     FFP58576_01011951
APPS     FFP60357_01011951
APPS     FFP57511_01010001
APPS     FFP57510_01010001
APPS     FFP52473_01010001
APPS     FFP60305_01010001
APPS     FFP60545_01042004
APPS     FFP60342_01010001
APPS     FFP58887_01042004
APPS     FFP58888_01042004
APPS     FFP58870_01042004
APPS     FFP58885_01042004
APPS     FFP58907_01010001
APPS     FFP58906_01010001
APPS     FFP58861_01042004
APPS     FFP61122_01010001
APPS     FFP58871_01042004
APPS     FFP58857_01042005
APPS     FFP60917_01032006
SCOTT     MK_PLS_XML_REP_TEST
APPS     MK_PLS_XML_REP_TEST
APPS     AP_FSX_PAYMENT_ADVICE
APPS     RA_SITE_USES
APPS     ZDBAR_CONTACT
APPS     ZDBAR_FAX
APPS     ZDBCLOAD
APPS     ZDBAP_DV_PAYMENT_TYPE
Advanced thanks for reading and giving solution for this.
Thamaraiselvan

any one can give idea to make it valid.Run "Compile APPS Schema" from adadmin.
For Fast Formulas, refer to:
Note: 155737.1 - How To Compile Oracle Fast Formulas
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=155737.1

Importing Database Package into OWB changes position of parameters .. Nasty

Hi all,
Anyone else having the same problem ? Any solutions ? Or is this a bug.
When a package is imported from a DB schema, OWB kindly changes the order in which the parameters are listed.
The effect is that any mapping using the procedure or function will not have the correct parameters passed to.
For example.
DB_Test_proc
io_name_in in out varhar2,
o_clean_name_out out varchar2
After importing in OWB the parameter positions are reversed .... very nasty.
Anyone can help or do I raise a bug ?
Regards
Nick

Hi Borkur,
Dropping and re-importing the package would work well (works for another module) but this is a package whose procedures and functions are heavily referenced in several mappings and process flows (supports the custom job management). So, I would be forced to re-synchronize them all which I want to avoid. The other way would be to modify the package manually (only the signature is needed not the code since I will not deploy it from OWB, in fact, I deployed it from Oracle Designer !!!). But OWB Paris doesn't allow this. Once imported, always imported. You can modify imported tables, procedures, functions but not packages. Or is there a way ???
regards
Thomas

Import PLSQL procedure or package into OWB

Here's a simple question. In schema X, I created a procedure and a package. If I try to import them into OWB (10g R2), connecting to schema X and clicking on transformations and "import" doesn't show the newly created objects for import. I tried granting execute to OWB10GR2, but no luck. Closed and re-started design center with no luck.
Creating a procedure in Design Center and then deploying it to schema X works and is a workaround, but it's awkward to write code there (compile is deploy, which takes a lot longer than normal compile).
What am I missing so that I can't import a procedure into design center?

OK, so I'm going to answer my own question. Maybe someone else can use the info...
The problem is that I have development and production configurations.
Procedure or package defined only in one (dev or prod) schema won't show up on the import list. Apparently, in order to import the object into OWB you need to define it in all environments. Otherwise it doesn't show up on the import list.

Uploading/Installing procedure for device packages in Cisco View/RME

Hi,
Running LMS3.2 with HUM 1.2.
In cisco view when we tried for below mwntioned devices it says "Device Package for these device is not available".
WS-C2960S
CISCO2921
CISCO3945E.
Please let me know the link to download the device packages for above devices and the procedure to install it on LMS.
Thanks & Regards,
Krishna

Hi Krishna,
Replace the attached file (vds.properties) in the below location :
NMSROOT\CSCOpx\lib\classpath\com\cisco\nm\xms\vds
then Restart the Daemon Manager ..
NOTE : Please take the Bcakup of your Existing file (vds.properties)
--Then go to common service > software center > device update >> check for the Device Pcakages , you will be able to see the Device Packages now..
Thanks--
Afroj
If this post answers your question, please click the "Correct Answer" button"

Package in owb views

Similar Messages

Maybe you are looking for