Need sequence and object - where to put them

Question

Hello:
I am also learning ORACLE coming from MS SQL - lost of interesting new points of views and that is where i am stuck.
Inside a stored procedure, I need to create a temporary space to hold records returned from other stored procedures.
It appears that I should create a TEMPTABLE TYPE AS OBJECT() and a CREATE SEQUENCE unid start with 1 on the TEMPTABLE column...
I seem to recall in one of the numerous articles I have been reading that for the stored procedure to compile, these OBJETCS AND SEQUENCE must exist PRIOR to stored procedure compilation.
If that is true, is that the purpose of creating a package, a space where I can create objects and other sequences and types so that the Stored Procedures know about them before compilation...
So the following wont work.....
create or replace PROCEDURE REP_CS_DETACT_MASTER
DIVISION     IN VARCHAR,
BEGINDATE IN VARCHAR,
ENDDATE IN VARCHAR,
MyResultset OUT SYS_REFCURSOR
AS
CREATE SEQUENCE unid start with 1
BEGIN
CREATE TYPE TEMPTABLE AS OBJECT
unid integer,
smid varchar(100),
sm varchar(200),
AssignedCases integer,
ClosedCases integer,
OnHand integer,
RecoveryDollars Money
<++++++++++++++>
END REP_CS_DETACT_MASTER;
Thank you
T

Answer 1

So I asked
>
Perhaps if you explain what you are trying to achieve, instead of how you are going about it,
>
GADOI wrote:
My MS - stored procedure currently creates two temporary tables - if you will - one a toptable and one is temptable.This is how you are doing <something>
In the toptable, I insert a bunch of peoples names that come from what is returned as a result of calling another stored procedure.This is how you are doing <something>
The structure of the TOPTABLE in MSSQL is...
create table #temptable (unid integer identity(1,1), smid varchar(100), sm varchar(200), AssignedCases integer, ClosedCases integer, OnHand integer, RecoveryDollars Money)
so essentially, calling the first stored procedure will result in unid incrementing and smid being populated.This is how you are doing <something>
Then I want to do a series of updates to the following columns as resulting from data called by other procedures.This is how you are doing <something>
So the next stored procedure will populate sm..
update #temptable set sm = <> where smid = ....
unitl all the columns are populatedThis is how you are doing <something>
then the contents are returned to the client and the tables are destroyed.This is how you are doing <something>
there.... There we now have a lot more how and not any more what that <something> that you are doing is.
unless some of you brillant engineers/architects out there have a different approach...I would write a query that returns whatever the <something> is that is needed by the client.