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

Similar Messages

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

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.

Import business packages into the Websphere portal

Hi All,
Is there any way to import business packages into the Websphere portal. We are looking to display E Recruitment applications in Websphere Portal.Please let me know the procedure.
Regards,
Anil

If it is OK to open the e-recruitment app into a new window from Websphere portal, simply link to it and host it in SAP Portal.
If you can work out the single sign on, perhaps Websphere portal would let you use a portlet like an iframe that lets you display the SAP functionality hosted in SAP Portal. That way it looks like one interface to the end user but back end is hosted separately.
The most streamlined but also more work, would probably be to have a SOA aware Websphere developer create the front end in IBM that references SAP's remote enabled functions.
I'm not aware of any automatic way to simply import / host the SAP business packages inside Websphere, if that is what you are asking.

Import excel file into owb automatically, is it possible?

Is it possible to load several excel files in owb automatically?
I want to avoid the follow situation...
I have like 100 excel files I have to create 100 system dsn each pointing to one excel file.
Is it possible?
Thanks

The forum is how to integrate foreign databases into an oracle database using gateway. From the provided description you're trying to import an Excel file directly into OWB. OWB has its own mechanism to import these files , so better post your issue in the OWB forum:
Warehouse Builder

Importing existing dimensions into OWB

Does any body know how to import an existing Dimension, created in an Oracle database into OWB so that the dimension definition appears under the dimension tab.

Hi,
I think you can't import a dimension from data base.you have to create throught OWB.
Regards
naren

Import a package in owb 10.2. with ombplus

hi,
we have a plsql-package wich evolves over time, created by a generator...
i want to re-import a plsql-package with ombplus.
i tried it that way:
OMBDROP PACKAGE 'pckg1'
OMBCREATE TRANSIENT IMPORT_ACTION_PLAN 'I1'
OMBALTER IMPORT_ACTION_PLAN 'I1' ADD ACTION 'PCKG-IMP' SET REF SOURCE PACKAGE 'pckg1' SET REF TARGET ORACLE_MODULE 'mod1'
i got a error indicating that 'PACKAGE' isn't the right object-type:
PUB04201: Encountered an internal fatal error during processing of oracle module mod1: unsupported obj type.
the documentation did not list valid object-types.
does anyone know how to accomplish this task?
when the object-type 'PACKAGE' not exists, is there an other way to re-import a package?
thanks in advance
tr

OMB+> OMBCONNECT $connect_string
Connected.
OMB+> OMBCC $project_name
Context changed.
OMB+> OMBCREATE TRANSIENT IMPORT_ACTION_PLAN 'I1'
Import action plan I1 is created.
OMB+> OMBALTER IMPORT_ACTION_PLAN 'I1' ADD ACTION 'PCKG-IMP' SET REF SOURCE PACKAGE $package SET REF TARGET ORACLE_MODULE $module
Import action plan I1 is altered.
OMB+> OMBALTER LOCATION $loc SET PROPERTIES (PASSWORD) VALUES ($pwd)
Location LOC altered.
OMB+>
OMB+> OMBIMPORT FROM METADATA_LOCATION FOR IMPORT_ACTION_PLAN 'I1'
PUB04201: Encountered an internal fatal error during processing of oracle module mod1: unsupported obj type.
OMB+> OMBREVERT
Revert complete.
OMB+> OMBDISC
Disconnected.

How to import other package into Dictionaries in nwds web dynpro project

Hi
i'm learning JA312, in some topic, there need a method declaration in component controller, the method like this:
public void showContext(IWDContext context),
i can add method in method tab in component controller,but can not add parameter of IWDContext types,because in Dictionaries,there are only com.sap.ide.., and not include com.sap.tc.webdynpro.progmodel.api.
so,how to import package into Dictionaries, for example com.sap.tc.webdynpro.progmodel.api.
a step by step article is preferred. thank you

choose "Java Native Type".

How to import BC4J package into JDEV project without server.xml file?

Dear,
I need to bring the seeded BC4J package into my JDEV OAF project. Usually to do that, once I am sure that all I need is accessible, I open the server.xml file for the BC4J that I need and I am all set - all the items from under that BC4J are brought in.
How about if there is no server.xml file for that BC4J, for example, under oracle.apps.icx.por.req.webui, and I need to have a controller from under there in my project? Do I create this package (oracle.apps.icx.por.req.webui) manually? If I do that and then open the controller the controller is being brought into JDEV outside the package.
Thank you.
Anatoliy

Sumit,
Thank for quick response.
Yes, I agree for the controller.
But let's say I want to bring over some other xml staff, like some shared regions for example from under that webui. They are also brought outside the package. You have an idea?
Regards,
Anatoliy

How do you import a package into Forte?

I'm attempting to use a Java package from http://www.braju.com that essentially implements the standard C functions printf / sprintf, as part of an exercise to convert a C program to Java.
I can go into a (gasp!) Windows ME DOS window, set my Classpath to include C:\java\classes (where I put the hb15.zip file), and following the directions on Henrik's website I can type:java com.braju.format.Format -helpand see it work- but when I try to compile with Forte, the line...import com.braju.format.*;causes it to say, "package com.braju.format does not exist."
I just installed the early release (version 3) of Forte, which has no problem with standard Java imports such as:import java.lang.Math;Does anybody know what the problem is?

Hi.
I am using NetBeans 3.2 but I think it's pretty the same.
So here is how to set your classpath for your compiler :
1) decide what you're using as a compiler : internal or external compiler
2) go to main menu : Project - > Settings
3) Expand "Compiler Types" node
4) Select from here the compiler you're using (internal, external, fastjavac , etc )
5) click on the "Expert" tab and you'll find a "classpath" field that must be editable
6) append/add your location to the existing classpath
Now it should work.
They may be some (GUI) differences between the Forte and NetBeans main menu, but I think you've got the idea.
Regards,
Rick

Import WB_RT_GET_JOB_METRICS procedure into OWB

How do I import this procedure WB_RT_GET_JOB_METRICS into my mapping.

You can get the public transformations. After you have opened your map, you can follow this path to get to the procedure: explorer in upper left pannel --> Pulic transformation --> Pre-defined --> control_center --> WB_RT_GET_JOB_METRICS . Then you can drap it to your map.

OWB Can't Import Existing Package with Collection Data Type as Arguments

I created a package and compiled it successfully as the follows:
+++++++++++++++++++++++++++++
CREATE OR REPLACE PACKAGE PACKAGE_TEST AS
TYPE Num_LIST IS TABLE of NUMBER INDEX BY BINARY_INTEGER;
FUNCTION TEST_FUNCTION1 ( arg1 NUMBER, arg2 NUMBER) RETURN NUMBER;
FUNCTION TEST_FUNCTION2 ( args NUM_LIST) RETURN NUMBER;
END PACKAGE_TEST;
CREATE OR REPLACE PACKAGE BODY PACKAGE_TEST AS
FUNCTION TEST_FUNCTION1 ( arg1 NUMBER, arg2 NUMBER) RETURN NUMBER IS
ln_sum NUMBER;
BEGIN
ln_sum := arg1 + arg2;
     RETURN ln_sum;
EXCEPTION
WHEN OTHERS THEN
RETURN -10000;
END TEST_FUNCTION1;
FUNCTION TEST_FUNCTION2 ( args NUM_LIST) RETURN NUMBER IS
     ln_sum NUMBER;
BEGIN
ln_sum :=0;
     FOR i IN 1.. args.COUNT LOOP
     ln_sum := ln_sum + args( i );
     END LOOP;
     RETURN ln_sum;
EXCEPTION
WHEN OTHERS THEN
RETURN -10000;
END TEST_FUNCTION2;
END PACKAGE_TEST;
++++++++++++++++++++++++++++++++++++++++
Then I tried to import the package into OWB (9.2). The problem came: all the package body and
the specification of TEST_FUNCTION1 were imported, but the package specification of
TEST_FUNCTION2 couldn't be imported. The IMPORT FILTER gave an error message:
"TEST_FUNCTION2: Argument Data type is not supported".
How to resolve this problem? It is very import for our project, since we have to import some
packages with user_defined collection data types as arguments.
Thank you.
Lushu

Hi Lushu,
Unfortunately this is indeed not supported and I would not know how to work around this one. The only way I guess that this would work is to not import it, and then use Expressions to call the function with inputs.
Jean-Pierre

Re-importing a package fails

Hi,
usually, you can always re-import a package into OWB (10gR2) and synchronize it with the database. But I have the phenomenon that some (not all) packages fail in this process; after pressing Finish the import wizard dies and does almost nothing. I tracked it down to the the DebugSQL.000.log file and found as last entry:
select line, text from all_source@owb_1335 where owner = 'DWH_ADMIN' and name = 'UTIL' and type = 'PACKAGE' order by line
With other packages which do the re-import perfectly the next line would be the analogous query to read the PACKAGE BODY. This would indicate an overflow issue, but the package isn't big at all and works well when imported into another module. I cannot find any trace log of this failure. And - strange enough - the failing process is still able to drop the temporary database link owb_nnnn.
Some ideas
regards
Thomas

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

Importing packages/procedures into OWB

Is it possible to import packages or procedures into OWB that are stored on a different database?
I want to call a procedure in a mapping that is stored on a different database. I can only import tables and views (as data source ) from other databases.
I can only import PL/SQL packages into OWB if they're stored in the current database.
Does anybody have a solution?
Regards,
Maurice

Maurice,
Essentially the import uses a dblink, so you have the option to specify the dblink to another place and you should be able to see/import that pl/sql.
The most elegant and prefered way however is to import the pl/sql into the public transformations node (I'm using OWB 9.0.4). This is a bucket that holds sharable pl/sql and seems to address the need for you.
Here again you create the dblink and point at the remote db schema that owns the pl/sql.
Hope this helps,
Jean-Pierre

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

Similar Messages

Maybe you are looking for