Delete Table Maintainence View

I need to delete a table maintainence view. How can I go about doing so, please be specific. Thanks.

hi,
If the few values are required to be deleted,and if the data base maintainence is allowed... then you can go to SE11 and can selected those field and delete it....
Otherwise if the value sets are large in number it has to be done programatically, using ABAP....
Hope it helps....
Regards
Priyanka.P

Similar Messages

Maintainence View Problem

I have created a ztable, and have used that table in maintainence view, but when i use that view in sm30 for entering the data, one of the field description is not coming it is just showing '+' ., what would be the problem .

in the ztable for that field u might have used a data element which has no description. If there is no description for a field then in SM30 it will be shown as +.
To solve this, for this field create a new dataelement and assign the dataelement to the field. Then goto table maintenance, delete the one existing, create a new one and activate it.
Now, when U go to SM30, u will see the description instead of +.
Award Points...Useful...

How to use table maintenance view in module pool screen

hi ,
want to use table maintenance view in a module pool screen so that i can edit, insert, delete and update date in to the ztable.please help.

You can simply call it via SM30.   Or you can call the table maintence view from any program(report or module pool) using a function module.
call function 'VIEW_MAINTENANCE_CALL'
       exporting
            action                       = 'U'
            view_name                    = 'Z_Table_Name'
       exceptions
            client_reference             = 1
            foreign_lock                 = 2
            invalid_action               = 3
            no_clientindependent_auth    = 4
            no_database_function         = 5
            no_editor_function           = 6
            no_show_auth                 = 7
            no_tvdir_entry               = 8
            no_upd_auth                  = 9
            only_show_allowed            = 10
            system_failure               = 11
            unknown_field_in_dba_sellist = 12
            view_not_found               = 13
            others                       = 14.
Regards,
RIch Heilman

How to retreive data from a maintainence view?

Hi all,
I have used select query to retreive data from a maintainence view. But it gave me a syntactical error that XYZ is not in abap dictionary , it's a database / projection view?
So can't we get data from a view using select query?
Please share if u have answers.
Thanks & regards,
Chandru

Hi,
Maintenance view will be created for database tables only.
Just display the maintainence from SE11 and click Tables tab in the screen
Here you can find the list of tables used to created for Maintainence view.
YOu can use these tables to write SELECT.
If you give us the maintainence table, we will help you.
Thanks,
Ramakrishna

Com.sap.sql.log.OpenSQLException: table or view not exists

Hi!.
I'm developing a Portal Component over NW EP 2004s (7.0) which access to SQL Server database. I have created three tables on the system db (EPD). Connection is Ok, over datasource object, but i can't make a SELECT operation to my new tables.
Hovewer, making a SELECT operation over older system tables is OK.
I have adjusted permissions on my new tables, similar to the older tables. The table's owner is the same too.
The exception i get is:
**Exception of type com.sap.sql.log.OpenSQLException caught: The SQL statement "SELECT * FROM "SAPEPDDB"."UME_EP_UNLOCKUSERS"" contains the semantics error[s]: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist**
[EXCEPTION]
*com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM "SAPEPDDB"."UME_EP_UNLOCKUSERS"" contains the semantics error[s]: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist*
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:38)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.CommonStatementImpl.executeQuery(CommonStatementImpl.java:114)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeQuery(StatementWrapper.java:172)
at com.uralita.database.DbManager.executeQuery(DbManager.java:105)
at com.uralita.ListaSistemas$ListaSistemasDynPage.getSystemsR3(ListaSistemas.java:184)
at com.uralita.ListaSistemas$ListaSistemasDynPage.doInitialization(ListaSistemas.java:93)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:105)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:534)
Caused by: com.sap.sql.sqlparser.CommonSQLParserException: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:171)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
... 19 more
caused by
com.sap.sql.sqlparser.CommonSQLParserException: - 1:24 - the table or view >>UME_EP_UNLOCKUSERS<< does not exist
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:171)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.CommonStatementImpl.executeQuery(CommonStatementImpl.java:114)
at com.sap.engine.services.dbpool.wrappers.StatementWrapper.executeQuery(StatementWrapper.java:172)
at com.uralita.database.DbManager.executeQuery(DbManager.java:105)
at com.uralita.ListaSistemas$ListaSistemasDynPage.getSystemsR3(ListaSistemas.java:184)
at com.uralita.ListaSistemas$ListaSistemasDynPage.doInitialization(ListaSistemas.java:93)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:105)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable$1$DoDispatchRequest.run(AsyncIncludeRunnable.java:377)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.core.async.AsyncIncludeRunnable.run(AsyncIncludeRunnable.java:390)
at com.sapportals.portal.prt.core.async.ThreadContextRunnable.run(ThreadContextRunnable.java:164)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:729)
at java.lang.Thread.run(Thread.java:534)
Someone has been getting this problem? Any idea?
Thanks!

I have tried that.
[EXCEPTION]
*com.sap.sql.log.OpenSQLException: The SQL statement "SELECT * FROM EPD.SAPEPDDB.UME_EP_SLD" contains the syntax error[s]: - Open SQL syntax error: table names must not specify a catalog name (delete "EPD". before "SAPEPDDB"."UME_EP_SLD")*
Database name must be Ok, because i can access to other tables which are in the same DB...
Thanks for your help

ORA 01792 maximum number of columns in a table or view is 1000

Hello every1, I wish to register a large xmlschema doc, I am using the command
begin
dbms_xmlschema.registerschema(
schemaurl=>'xxxx',
schemadoc=>bfilename('XMLDIR','xxxxxx.xsd'),
csid=>nls_charset_id('AL32UTF8'));
end;
But the schema file exists 1000 col and it gives me the error msg of
ORA-01792: maximum number of columns in a table or view is 1000
is there anyway to solve the problems without edit the original schema document?
Thanks for your help

First create this package
create or replace package XDB_ANALYZE_XMLSCHEMA_10200
authid CURRENT_USER
as
function analyzeStorageModel(P_COMPLEX_TYPE_NAME VARCHAR2) return XMLTYPE;
function analyzeComplexType(COMPLEX_TYPE VARCHAR2) return XMLTYPE;
procedure renameCollectionTable (XMLTABLE varchar2, XPATH varchar2, COLLECTION_TABLE_PREFIX varchar2);
function printNestedTables(XML_TABLE varchar2) return XMLType;
function getComplexTypeElementList(P_SQLTYPE VARCHAR2, P_SQLSCHEMA VARCHAR2) return XDB.XDB$XMLTYPE_REF_LIST_T;
procedure scopeXMLReferences;
procedure indexXMLReferences(INDEX_NAME VARCHAR2);
function generateSchemaFromTable(P_TABLE_NAME varchar2, P_OWNER varchar2 default USER) return XMLTYPE;
function showSQLTypes(schemaFolder varchar2) return XMLType;
function generateCreateTableStatement(XML_TABLE_NAME varchar2, NEW_TABLE_NAME varchar2) return CLOB;
end XDB_ANALYZE_XMLSCHEMA_10200;
show errors
create or replace package body XDB_ANALYZE_XMLSCHEMA_10200
as
G_DEPTH_COUNT NUMBER(2) := 0;
TYPE BASETYPE_T is RECORD
SUBTYPE varchar2(128),
SUBTYPE_OWNER varchar2(32),
BASETYPE varchar2(128),
BASETYPE_OWNER varchar2(32)
TYPE BASETYPE_LIST_T IS TABLE OF BASETYPE_T;
BASETYPE_LIST BASETYPE_LIST_T := BASETYPE_LIST_T();
function findStorageModel(P_TYPE_NAME VARCHAR2, P_TYPE_OWNER VARCHAR2, P_INCLUDE_SUBTYPES VARCHAR2 DEFAULT 'YES') return XMLType;
function getLocalAttributes(P_TYPE_NAME varchar2, P_TYPE_OWNER VARCHAR2) return XMLType;
function makeElement(P_NAME varchar2)
return xmltype
as
V_NAME varchar2(4000) := P_NAME;
begin
-- -- dbms_output.put_line('Processing : ' || P_NAME);
if (P_NAME LIKE '%$') then
 V_NAME := SUBSTR(V_NAME,1,LENGTH(V_NAME) - 1);
end if;
if (P_NAME LIKE '%$%') then
 V_NAME := REPLACE(V_NAME,'$','_0x22_');
end if;
return XMLTYPE( '<' || V_NAME || '/>');
end;
function getPathToRoot(SUBTYPE VARCHAR2, SUBTYPE_OWNER VARCHAR2)
return varchar2
as
TYPE_HIERARCHY varchar2(4000);
begin
 SELECT sys_connect_by_path( OWNER || '.' || TYPE_NAME , '/')
 INTO TYPE_HIERARCHY
 FROM ALL_TYPES
 WHERE TYPE_NAME = SUBTYPE
 AND OWNER = SUBTYPE_OWNER
 CONNECT BY SUPERTYPE_NAME = PRIOR TYPE_NAME
 AND SUPERTYPE_OWNER = PRIOR OWNER
 START WITH SUPERTYPE_NAME IS NULL
 AND SUPERTYPE_OWNER IS NULL;
 return TYPE_HIERARCHY;
end;
function expandSQLType(ATTR_NAME VARCHAR2, SUBTYPE VARCHAR2, SUBTYPE_OWNER VARCHAR2)
return XMLType
as
STORAGE_MODEL XMLTYPE;
ATTRIBUTES XMLTYPE;
EXTENDED_TYPE XMLTYPE;
ATTR_COUNT NUMBER := 0;
CURSOR FIND_EXTENDED_TYPES
is
select TYPE_NAME, OWNER
 from ALL_TYPES
 where SUPERTYPE_NAME = SUBTYPE
 and SUPERTYPE_OWNER = SUBTYPE_OWNER;
begin
-- dbms_output.put_line('Processing SQLType : "' || SUBTYPE_OWNER || '.' || SUBTYPE || '".' );
STORAGE_MODEL := makeElement(ATTR_NAME);
select insertChildXML(STORAGE_MODEL,'/' || STORAGE_MODEL.getRootElement(),'@type',SUBTYPE)
 into STORAGE_MODEL
 from dual;
select insertChildXML(STORAGE_MODEL,'/' || STORAGE_MODEL.getRootElement(),'@typeOwner',SUBTYPE_OWNER)
 into STORAGE_MODEL
 from dual;
ATTRIBUTES := getLocalAttributes(SUBTYPE, SUBTYPE_OWNER);
ATTR_COUNT := ATTR_COUNT + ATTRIBUTES.extract('/' || ATTRIBUTES.getRootElement() || '/@columns').getNumberVal();
select appendChildXML(STORAGE_MODEL,'/' || STORAGE_MODEL.getRootElement(),ATTRIBUTES)
 into STORAGE_MODEL
 from DUAL;
for t in FIND_EXTENDED_TYPES loop
 EXTENDED_TYPE := expandSQLType('ExtendedType',T.TYPE_NAME,T.OWNER);
 ATTR_COUNT := ATTR_COUNT + EXTENDED_TYPE.extract('/' || EXTENDED_TYPE.getRootElement() || '/@columns').getNumberVal();
 select appendChildXML(STORAGE_MODEL,'/' || STORAGE_MODEL.getRootElement(),EXTENDED_TYPE)
 into STORAGE_MODEL
 from DUAL;
end loop;
select insertChildXML(STORAGE_MODEL,'/' || STORAGE_MODEL.getRootElement(),'@columns',ATTR_COUNT)
 into STORAGE_MODEL
 from dual;
return STORAGE_MODEL;
end;
function getLocalAttributes(P_TYPE_NAME varchar2, P_TYPE_OWNER VARCHAR2)
return XMLType
as
V_ATTRIBUTE_COUNT NUMBER := 0;
V_TOTAL_ATTRIBUTES NUMBER := 0;
V_TEMP_RESULT NUMBER;
V_COLLECTION_TYPE varchar2(32);
V_COLLECTION_OWNER varchar2(32);
CURSOR FIND_CHILD_ATTRS
is
select ATTR_NAME, ATTR_TYPE_OWNER, ATTR_TYPE_NAME, INHERITED
 from ALL_TYPE_ATTRS
 where TYPE_NAME = P_TYPE_NAME
 and OWNER = P_TYPE_OWNER
 and INHERITED = 'NO'
 order by ATTR_NO;
V_ATTR DBMS_XMLDOM.DOMATTR;
V_ATTRIBUTE_LIST XMLTYPE;
V_ATTRIBUTE_LIST_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_ATTRIBUTE_LIST_ROOT DBMS_XMLDOM.DOMELEMENT;
V_ATTRIBUTE XMLTYPE;
V_ATTRIBUTE_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_ATTRIBUTE_ROOT DBMS_XMLDOM.DOMELEMENT;
V_TYPE_DEFINITION XMLTYPE;
V_TYPE_DEFINITION_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_TYPE_DEFINITION_ROOT DBMS_XMLDOM.DOMELEMENT;
begin
V_ATTRIBUTE_LIST := makeElement('Attributes');
V_ATTRIBUTE_LIST_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_ATTRIBUTE_LIST);
V_ATTRIBUTE_LIST_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_ATTRIBUTE_LIST_DOCUMENT);
for ATTR in FIND_CHILD_ATTRS loop
 -- Finding Element / Attribute Name could be tricky. Use SQLName
 V_ATTRIBUTE := makeElement(ATTR.ATTR_NAME);
 V_ATTRIBUTE_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_ATTRIBUTE);
 V_ATTRIBUTE_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_ATTRIBUTE_DOCUMENT);
 begin
 -- Check for Attributes based on collection types, With Nested Table storage each Collection will cost 2 columns.
 select ELEM_TYPE_NAME, ELEM_TYPE_OWNER
 into V_COLLECTION_TYPE, V_COLLECTION_OWNER
 from ALL_COLL_TYPES
 where TYPE_NAME = ATTR.ATTR_TYPE_NAME
 and OWNER = ATTR.ATTR_TYPE_OWNER;
 -- -- dbms_output.put_line('Adding "' || ATTR.ATTR_NAME || '". Collection of "' || ATTR.ATTR_TYPE_OWNER || '"."' || ATTR.ATTR_TYPE_NAME || '".');
 -- Attribute is a Collection Type.
 -- Collection will be managed as a NESTED TABLE
 -- Each Collection cost 2 columns.
 -- May want to count the number of columns in the NESTED_TABLE at a later date.
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_DOCUMENT,'SQLCollType');
 DBMS_XMLDOM.SETVALUE(V_ATTR,ATTR.ATTR_TYPE_NAME);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_ROOT,V_ATTR);
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_DOCUMENT,'SQLCollTypeOwner');
 DBMS_XMLDOM.SETVALUE(V_ATTR,ATTR.ATTR_TYPE_OWNER);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_ROOT,V_ATTR);
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_DOCUMENT,'SQLType');
 DBMS_XMLDOM.SETVALUE(V_ATTR,V_COLLECTION_TYPE);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_ROOT,V_ATTR);
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_DOCUMENT,'SQLTypeOwner');
 DBMS_XMLDOM.SETVALUE(V_ATTR,V_COLLECTION_OWNER);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_ROOT,V_ATTR);
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_DOCUMENT,'columns');
 DBMS_XMLDOM.SETVALUE(V_ATTR,2);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_ROOT,V_ATTR);
 exception
 when no_data_found then
 -- Attribute is not a collection type.
 begin
 -- Check for Attributes based on non-scalar types.
 select 1
 into V_TEMP_RESULT
 from ALL_TYPES
 where TYPE_NAME = ATTR.ATTR_TYPE_NAME
 and OWNER = ATTR.ATTR_TYPE_OWNER;
 -- Attribute is based on a non-scalar type. Find the Storage Model for this type.
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_DOCUMENT,'SQLType');
 DBMS_XMLDOM.SETVALUE(V_ATTR,ATTR.ATTR_TYPE_NAME);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_ROOT,V_ATTR);
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_DOCUMENT,'SQLTypeOwner');
 DBMS_XMLDOM.SETVALUE(V_ATTR,ATTR.ATTR_TYPE_OWNER);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_ROOT,V_ATTR);
 V_TYPE_DEFINITION := findStorageModel(ATTR.ATTR_TYPE_NAME, ATTR.ATTR_TYPE_OWNER, 'YES');
 V_TYPE_DEFINITION_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_TYPE_DEFINITION);
 V_TYPE_DEFINITION_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_TYPE_DEFINITION_DOCUMENT);
 V_ATTRIBUTE_COUNT := DBMS_XMLDOM.GETATTRIBUTE(V_TYPE_DEFINITION_ROOT,'columns');
 V_TYPE_DEFINITION_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.IMPORTNODE(V_ATTRIBUTE_DOCUMENT,DBMS_XMLDOM.MAKENODE(V_TYPE_DEFINITION_ROOT),TRUE));
 V_TYPE_DEFINITION_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(V_ATTRIBUTE_ROOT),DBMS_XMLDOM.MAKENODE(V_TYPE_DEFINITION_ROOT)));
 DBMS_XMLDOM.FREEDOCUMENT(V_TYPE_DEFINITION_DOCUMENT);
 if (ATTR.ATTR_TYPE_NAME = 'XDB$ENUM_T' and ATTR.ATTR_TYPE_OWNER = 'XDB') then
 -- The cost of a XDB$ENUM_T is 2 columns
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_DOCUMENT,'columns');
 DBMS_XMLDOM.SETVALUE(V_ATTR,2);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_ROOT,V_ATTR);
 else
 -- The cost of a non scalar Type is the number of attributes plus one for Type and one for the TYPEID.
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_DOCUMENT,'columns');
 DBMS_XMLDOM.SETVALUE(V_ATTR,V_ATTRIBUTE_COUNT + 2);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_ROOT,V_ATTR);
 end if;
 exception
 when no_data_found then
 -- Attribute is based on a scalar type
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_DOCUMENT,'SQLType');
 DBMS_XMLDOM.SETVALUE(V_ATTR,ATTR.ATTR_TYPE_NAME);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_ROOT,V_ATTR);
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_DOCUMENT,'columns');
 DBMS_XMLDOM.SETVALUE(V_ATTR,1);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_ROOT,V_ATTR);
 end;
 end;
 V_TOTAL_ATTRIBUTES := V_TOTAL_ATTRIBUTES + DBMS_XMLDOM.GETATTRIBUTE(V_ATTRIBUTE_ROOT,'columns');
 V_ATTRIBUTE_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.IMPORTNODE(V_ATTRIBUTE_LIST_DOCUMENT,DBMS_XMLDOM.MAKENODE(V_ATTRIBUTE_ROOT),TRUE));
 V_ATTRIBUTE_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(V_ATTRIBUTE_LIST_ROOT),DBMS_XMLDOM.MAKENODE(V_ATTRIBUTE_ROOT)));
 DBMS_XMLDOM.FREEDOCUMENT(V_ATTRIBUTE_DOCUMENT);
 if (V_TOTAL_ATTRIBUTES > 25000) then
 exit;
 end if;
end loop;
V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_ATTRIBUTE_LIST_DOCUMENT,'columns');
 DBMS_XMLDOM.SETVALUE(V_ATTR,V_TOTAL_ATTRIBUTES);
V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ATTRIBUTE_LIST_ROOT,V_ATTR);
return V_ATTRIBUTE_LIST;
end;
function getSubTypes(P_TYPE_NAME VARCHAR2, P_TYPE_OWNER VARCHAR2)
return XMLType
as
CURSOR FIND_SUBTYPES
is
select TYPE_NAME, OWNER
 from ALL_TYPES
 where SUPERTYPE_NAME = P_TYPE_NAME
 and SUPERTYPE_OWNER = P_TYPE_OWNER;
CURSOR FIND_SUBTYPE_HEIRARCHY
is
select LEVEL, TYPE_NAME, OWNER
 from ALL_TYPES
 where TYPE_NAME <> P_TYPE_NAME
 and OWNER <> P_TYPE_OWNER
 connect by SUPERTYPE_NAME = PRIOR TYPE_NAME
 and SUPERTYPE_OWNER = PRIOR OWNER
 start with TYPE_NAME = P_TYPE_NAME
 and OWNER = P_TYPE_OWNER;
V_SUBTYPE_LIST XMLType;
V_SUBTYPE_LIST_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_SUBTYPE_LIST_ROOT DBMS_XMLDOM.DOMELEMENT;
V_TYPE_DEFINITION XMLType;
V_TYPE_DEFINITION_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_TYPE_DEFINITION_ROOT DBMS_XMLDOM.DOMELEMENT;
V_SUBTYPE_DEFINITIONS XMLType;
V_SUBTYPE_DEFINITIONS_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_SUBTYPE_DEFINITIONS_ROOT DBMS_XMLDOM.DOMELEMENT;
V_ATTRIBUTE_LIST XMLType;
V_ATTRIBUTE_LIST_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_ATTRIBUTE_LIST_ROOT DBMS_XMLDOM.DOMELEMENT;
V_SUBTYPES_EXIST BOOLEAN := FALSE;
V_TOTAL_columns number;
V_ATTRIBUTE_COUNT number;
V_ATTR DBMS_XMLDOM.DOMATTR;
V_COMPLEX_TYPE VARCHAR2(256);
begin
V_SUBTYPE_LIST := makeElement('SubTypeDefinitions');
V_SUBTYPE_LIST_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_SUBTYPE_LIST);
V_SUBTYPE_LIST_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_SUBTYPE_LIST_DOCUMENT);
V_TOTAL_columns := 0;
for t in FIND_SUBTYPES() loop
 V_SUBTYPES_EXIST := TRUE;
 V_TYPE_DEFINITION := makeElement(t.TYPE_NAME);
 V_TYPE_DEFINITION_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_TYPE_DEFINITION);
 V_TYPE_DEFINITION_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_TYPE_DEFINITION_DOCUMENT);
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_TYPE_DEFINITION_DOCUMENT,'SQLTypeOwner');
 DBMS_XMLDOM.SETVALUE(V_ATTR,t.OWNER);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_TYPE_DEFINITION_ROOT,V_ATTR);
 begin
 select x.XMLDATA.NAME
 into V_COMPLEX_TYPE
 from XDB.XDB$COMPLEX_TYPE x
 where x.XMLDATA.SQLTYPE = t.TYPE_NAME
 and x.XMLDATA.SQLSCHEMA = t.OWNER;
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_TYPE_DEFINITION_DOCUMENT,'type');
 DBMS_XMLDOM.SETVALUE(V_ATTR,V_COMPLEX_TYPE);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_TYPE_DEFINITION_ROOT,V_ATTR);
 -- Consider adding Schema URL Attribute
 exception
 when no_data_found then
 null;
 when others then
 raise;
 end;
 V_ATTRIBUTE_LIST := getLocalAttributes(t.TYPE_NAME, t.OWNER);
 V_ATTRIBUTE_LIST_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_ATTRIBUTE_LIST);
 V_ATTRIBUTE_LIST_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_ATTRIBUTE_LIST_DOCUMENT);
 V_ATTRIBUTE_COUNT := DBMS_XMLDOM.GETATTRIBUTE(V_ATTRIBUTE_LIST_ROOT,'columns');
 V_ATTRIBUTE_LIST_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.IMPORTNODE(V_TYPE_DEFINITION_DOCUMENT,DBMS_XMLDOM.MAKENODE(V_ATTRIBUTE_LIST_ROOT),TRUE));
 V_ATTRIBUTE_LIST_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(V_TYPE_DEFINITION_ROOT),DBMS_XMLDOM.MAKENODE(V_ATTRIBUTE_LIST_ROOT)));
 DBMS_XMLDOM.FREEDOCUMENT(V_ATTRIBUTE_LIST_DOCUMENT);
 V_SUBTYPE_DEFINITIONS := getSubTypes(t.TYPE_NAME,t.OWNER);
 if (V_SUBTYPE_DEFINITIONS is not NULL) then
 V_SUBTYPE_DEFINITIONS_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_SUBTYPE_DEFINITIONS);
 V_SUBTYPE_DEFINITIONS_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_SUBTYPE_DEFINITIONS_DOCUMENT);
 V_ATTRIBUTE_COUNT := V_ATTRIBUTE_COUNT + DBMS_XMLDOM.GETATTRIBUTE(V_SUBTYPE_DEFINITIONS_ROOT,'columns');
 V_SUBTYPE_DEFINITIONS_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.IMPORTNODE(V_TYPE_DEFINITION_DOCUMENT,DBMS_XMLDOM.MAKENODE(V_SUBTYPE_DEFINITIONS_ROOT),TRUE));
 V_SUBTYPE_DEFINITIONS_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(V_TYPE_DEFINITION_ROOT),DBMS_XMLDOM.MAKENODE(V_SUBTYPE_DEFINITIONS_ROOT)));
 end if;
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_TYPE_DEFINITION_DOCUMENT,'columns');
 DBMS_XMLDOM.SETVALUE(V_ATTR,V_ATTRIBUTE_COUNT);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_TYPE_DEFINITION_ROOT,V_ATTR);
 V_TYPE_DEFINITION_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.IMPORTNODE(V_SUBTYPE_LIST_DOCUMENT,DBMS_XMLDOM.MAKENODE(V_TYPE_DEFINITION_ROOT),TRUE));
 V_TYPE_DEFINITION_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(V_SUBTYPE_LIST_ROOT),DBMS_XMLDOM.MAKENODE(V_TYPE_DEFINITION_ROOT)));
 V_TOTAL_columns := V_TOTAL_columns + V_ATTRIBUTE_COUNT;
end loop;
if (V_SUBTYPES_EXIST) then
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_SUBTYPE_LIST_DOCUMENT,'columns');
 DBMS_XMLDOM.SETVALUE(V_ATTR,V_TOTAL_columns);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_SUBTYPE_LIST_ROOT,V_ATTR);
 return V_SUBTYPE_LIST;
else
 return NULL;
end if;
end;
function findSuperTypeModel(P_TYPE_NAME VARCHAR2, P_TYPE_OWNER VARCHAR2)
return XMLType
as
begin
-- dbms_output.put_line('Processing Super Type : "' || P_TYPE_OWNER || '"."' || P_TYPE_NAME || '"');
return findStorageModel(P_TYPE_NAME, P_TYPE_OWNER,'NO');
end;
function getStorageModel(P_TYPE_NAME VARCHAR2, P_TYPE_OWNER VARCHAR2, P_INCLUDE_SUBTYPES VARCHAR2 DEFAULT 'YES')
return XMLType
as
V_TYPE_DEFINITION XMLTYPE;
V_ATTRIBUTE_COUNT NUMBER := 0;
SUBTYPE_STORAGE_MODEL XMLTYPE;
V_SUPERTYPE_DEFINITION XMLTYPE;
V_SUPERTYPE_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_SUPERTYPE_ROOT DBMS_XMLDOM.DOMELEMENT;
V_SUBTYPE_DEFINITION XMLTYPE;
V_SUBTYPE_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_SUBTYPE_ROOT DBMS_XMLDOM.DOMELEMENT;
V_ATTRIBUTE_LIST XMLTYPE;
V_ATTRIBUTE_LIST_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_ATTRIBUTE_LIST_ROOT DBMS_XMLDOM.DOMELEMENT;
cursor FIND_SUPERTYPE_HEIRARCHY
is
select TYPE_NAME, OWNER
 from ALL_TYPES
 where TYPE_NAME <> P_TYPE_NAME
 and OWNER <> P_TYPE_OWNER
 connect by TYPE_NAME = PRIOR SUPERTYPE_NAME
 and OWNER = PRIOR SUPERTYPE_OWNER
 start with TYPE_NAME = P_TYPE_NAME
 and OWNER = P_TYPE_OWNER
 order by LEVEL;
V_COMPLEX_TYPE varchar2(256);
V_SUPERTYPE_NAME varchar2(256);
v_SUPERTYPE_OWNER varchar2(256);
V_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_ROOT DBMS_XMLDOM.DOMELEMENT;
V_ATTR DBMS_XMLDOM.DOMATTR;
begin
-- dbms_output.put_line('Generating Storage Model for : "' || P_TYPE_OWNER || '"."' || P_TYPE_NAME || '"');
V_TYPE_DEFINITION := makeElement(P_TYPE_NAME);
V_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_TYPE_DEFINITION);
V_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_DOCUMENT);
V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_DOCUMENT,'SQLTypeOwner');
 DBMS_XMLDOM.SETVALUE(V_ATTR,P_TYPE_OWNER);
V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ROOT,V_ATTR);
begin
 select x.XMLDATA.NAME
 into V_COMPLEX_TYPE
 from XDB.XDB$COMPLEX_TYPE x
 where x.XMLDATA.SQLTYPE = P_TYPE_NAME
 and x.XMLDATA.SQLSCHEMA = P_TYPE_OWNER;
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_DOCUMENT,'type');
 DBMS_XMLDOM.SETVALUE(V_ATTR,V_COMPLEX_TYPE);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ROOT,V_ATTR);
 -- Consider adding Schema URL Attribute
exception
 when no_data_found then
 null;
 when others then
 raise;
end;
select SUPERTYPE_NAME, SUPERTYPE_OWNER
 into V_SUPERTYPE_NAME, V_SUPERTYPE_OWNER
 from ALL_TYPES
 where TYPE_NAME = P_TYPE_NAME
 and OWNER = P_TYPE_OWNER;
-- Process SuperType.
if (V_SUPERTYPE_NAME is not null) then
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_DOCUMENT,'SQLParentType');
 DBMS_XMLDOM.SETVALUE(V_ATTR,V_SUPERTYPE_NAME);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ROOT,V_ATTR);
 V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_DOCUMENT,'SQLParentTypeOwner');
 DBMS_XMLDOM.SETVALUE(V_ATTR,V_SUPERTYPE_OWNER);
 V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ROOT,V_ATTR);
 -- Find the Definition for the super type. Do not include the definition of it's subtypes.
 V_SUPERTYPE_DEFINITION := findSuperTypeModel(V_SUPERTYPE_NAME, V_SUPERTYPE_OWNER);
 -- -- dbms_output.put_line(dbms_lob.substr(V_SUPERTYPE_DEFINITION.getClobVal(),1000,1));
 V_SUPERTYPE_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_SUPERTYPE_DEFINITION);
 V_SUPERTYPE_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_SUPERTYPE_DOCUMENT);
 V_ATTRIBUTE_COUNT := V_ATTRIBUTE_COUNT + DBMS_XMLDOM.GETATTRIBUTE(V_SUPERTYPE_ROOT,'columns');
 V_SUPERTYPE_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.IMPORTNODE(V_DOCUMENT,DBMS_XMLDOM.MAKENODE(V_SUPERTYPE_ROOT),TRUE));
 V_SUPERTYPE_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(V_ROOT),DBMS_XMLDOM.MAKENODE(V_SUPERTYPE_ROOT)));
 DBMS_XMLDOM.FREEDOCUMENT(V_SUPERTYPE_DOCUMENT);
end if;
-- Process Attributes defined directly by the Type.
V_ATTRIBUTE_LIST := getLocalAttributes(P_TYPE_NAME, P_TYPE_OWNER);
V_ATTRIBUTE_LIST_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_ATTRIBUTE_LIST);
V_ATTRIBUTE_LIST_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_ATTRIBUTE_LIST_DOCUMENT);
V_ATTRIBUTE_COUNT := V_ATTRIBUTE_COUNT + DBMS_XMLDOM.GETATTRIBUTE(V_ATTRIBUTE_LIST_ROOT,'columns');
V_ATTRIBUTE_LIST_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.IMPORTNODE(V_DOCUMENT,DBMS_XMLDOM.MAKENODE(V_ATTRIBUTE_LIST_ROOT),TRUE));
V_ATTRIBUTE_LIST_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(V_ROOT),DBMS_XMLDOM.MAKENODE(V_ATTRIBUTE_LIST_ROOT)));
DBMS_XMLDOM.FREEDOCUMENT(V_ATTRIBUTE_LIST_DOCUMENT);
if (P_INCLUDE_SUBTYPES = 'YES') then
 -- Process any Sub-Types...
 V_SUBTYPE_DEFINITION := getSubTypes(P_TYPE_NAME, P_TYPE_OWNER);
 if (V_SUBTYPE_DEFINITION is not null) then
 V_SUBTYPE_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_SUBTYPE_DEFINITION);
 V_SUBTYPE_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_SUBTYPE_DOCUMENT);
 V_ATTRIBUTE_COUNT := V_ATTRIBUTE_COUNT + DBMS_XMLDOM.GETATTRIBUTE(V_SUBTYPE_ROOT,'columns');
 V_SUBTYPE_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.IMPORTNODE(V_DOCUMENT,DBMS_XMLDOM.MAKENODE(V_SUBTYPE_ROOT),TRUE));
 V_SUBTYPE_ROOT := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(V_ROOT),DBMS_XMLDOM.MAKENODE(V_SUBTYPE_ROOT)));
 DBMS_XMLDOM.FREEDOCUMENT(V_SUBTYPE_DOCUMENT);
 end if;
end if;
V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_DOCUMENT,'columns');
 DBMS_XMLDOM.SETVALUE(V_ATTR,V_ATTRIBUTE_COUNT);
V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ROOT,V_ATTR);
-- Cache the type definition.
-- dbms_output.put_line('Cached Storage Model for "' || P_TYPE_OWNER || '.' || P_TYPE_NAME || '".');
insert into XDBPM.XDBPM_STORAGE_MODEL_CACHE (TYPE_NAME, TYPE_OWNER, EXTENDED_DEFINITION, STORAGE_MODEL) VALUES (P_TYPE_NAME, P_TYPE_OWNER, P_INCLUDE_SUBTYPES, V_TYPE_DEFINITION);
return V_TYPE_DEFINITION;
end;
function findStorageModel(P_TYPE_NAME VARCHAR2, P_TYPE_OWNER VARCHAR2, P_INCLUDE_SUBTYPES VARCHAR2 DEFAULT 'YES')
-- Find the Storage Model for the Base Type.
-- If the type is derived from another type we need the storage model of the Base Type
-- As storage models are calculated they are cached in the global temporary table XDBPM_STORAGE_MODEL_CACHE. This makes
-- the process much more efficient. A global temporary table is used to minimize memory usage.
return XMLType
as
V_STORAGE_MODEL XMLType;
V_STORAGE_MODEL_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_STORAGE_MODEL_ROOT DBMS_XMLDOM.DOMELEMENT;
V_ATTRIBUTE_COUNT VARCHAR2(10);
begin
dbms_output.put_line('findStorageModel(' || G_DEPTH_COUNT || ') : Processing "' || P_TYPE_OWNER || '"."' || P_TYPE_NAME || '".' );
begin
 SELECT STORAGE_MODEL
 into V_STORAGE_MODEL
 from XDBPM.XDBPM_STORAGE_MODEL_CACHE
 where TYPE_NAME = P_TYPE_NAME
 and TYPE_OWNER = P_TYPE_OWNER
 and EXTENDED_DEFINITION = P_INCLUDE_SUBTYPES;
 -- dbms_output.put_line('Resolved Storage Model from cache.');
exception
 when no_data_found then
 G_DEPTH_COUNT := G_DEPTH_COUNT + 1;
 V_STORAGE_MODEL := getStorageModel(P_TYPE_NAME,P_TYPE_OWNER, P_INCLUDE_SUBTYPES);
 G_DEPTH_COUNT := G_DEPTH_COUNT - 1;
 when others then
 raise;
end;
V_STORAGE_MODEL_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_STORAGE_MODEL);
V_STORAGE_MODEL_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_STORAGE_MODEL_DOCUMENT);
V_ATTRIBUTE_COUNT := DBMS_XMLDOM.GETATTRIBUTE(V_STORAGE_MODEL_ROOT,'columns');
dbms_output.put_line('findStorageModel : Attribute Count for "' || P_TYPE_OWNER || '"."' || P_TYPE_NAME || '" = ' || V_ATTRIBUTE_COUNT || '.' );
return V_STORAGE_MODEL;
end;
function analyzeStorageModel(P_COMPLEX_TYPE_NAME VARCHAR2, P_TYPE_NAME VARCHAR2, P_TYPE_OWNER VARCHAR2)
-- Generate a map showing the number of columns required to persist an instance of the SQL type.
return XMLType
as
V_STORAGE_MODEL XMLTYPE;
V_COUNT NUMBER := 0;
V_DOCUMENT DBMS_XMLDOM.DOMDOCUMENT;
V_ROOT DBMS_XMLDOM.DOMELEMENT;
V_ATTR DBMS_XMLDOM.DOMATTR;
V_MODEL DBMS_XMLDOM.DOMELEMENT;
V_TYPE_DEFINITION DBMS_XMLDOM.DOMELEMENT;
begin
V_STORAGE_MODEL := makeElement(P_COMPLEX_TYPE_NAME);
V_DOCUMENT := DBMS_XMLDOM.NEWDOMDOCUMENT(V_STORAGE_MODEL);
V_ROOT := DBMS_XMLDOM.GETDOCUMENTELEMENT(V_DOCUMENT);
V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_DOCUMENT,'SQLType');
 DBMS_XMLDOM.SETVALUE(V_ATTR,P_TYPE_NAME);
V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ROOT,V_ATTR);
V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_DOCUMENT,'SQLTypeOwner');
 DBMS_XMLDOM.SETVALUE(V_ATTR,P_TYPE_OWNER);
V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ROOT,V_ATTR);
V_TYPE_DEFINITION := DBMS_XMLDOM.GETDOCUMENTELEMENT(DBMS_XMLDOM.NEWDOMDOCUMENT(findStorageModel(P_TYPE_NAME, P_TYPE_OWNER, 'YES')));
V_TYPE_DEFINITION := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.IMPORTNODE(V_DOCUMENT,DBMS_XMLDOM.MAKENODE(V_TYPE_DEFINITION),TRUE));
V_TYPE_DEFINITION := DBMS_XMLDOM.MAKEELEMENT(DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(V_ROOT),DBMS_XMLDOM.MAKENODE(V_TYPE_DEFINITION)));
V_ATTR := DBMS_XMLDOM.CREATEATTRIBUTE(V_DOCUMENT,'columns');
 DBMS_XMLDOM.SETVALUE(V_ATTR,DBMS_XMLDOM.GETATTRIBUTE(V_TYPE_DEFINITION,'columns'));
V_ATTR := DBMS_XMLDOM.SETATTRIBUTENODE(V_ROOT,V_ATTR);
return V_STORAGE_MODEL;
end;
function analyzeStorageModel(P_COMPLEX_TYPE_NAME VARCHAR2)
return XMLTYPE
-- Generate a map showing the number of columns required to persist an instance of the complex type.
as
pragma autonomous_transaction;
V_SQLTYPE VARCHAR2(128);
V_SQLSCHEMA VARCHAR2(32);
V_RESULT XMLType;
begin
G_DEPTH_COUNT := 0;
select ct.XMLDATA.SQLTYPE, ct.XMLDATA.SQLSCHEMA
 into V_SQLTYPE, V_SQLSCHEMA
 from XDB.XDB$COMPLEX_TYPE ct, XDB.XDB$SCHEMA s
 where ct.XMLDATA.NAME = P_COMPLEX_TYPE_NAME
 and ref(s) = ct.XMLDATA.PARENT_SCHEMA
 and s.XMLDATA.SCHEMA_OWNER = USER;
delete from XDBPM.XDBPM_STORAGE_MODEL_CACHE;
-- delete from XDBPM.XDBPM_STORAGE_MODEL;
V_RESULT := analyzeStorageModel(P_COMPLEX_TYPE_NAME,V_SQLTYPE,V_SQLSCHEMA);
COMMIT;
return V_RESULT;
exception
when no_data_found then
 -- dbms_output.put_line('Unable to find SQLType mapping for complexType : "' || USER || '"."' || P_COMPLEX_TYPE_NAME || '".' );
 return null;
when others then
 raise;
end;
function analyzeSQLType(ATTR_NAME VARCHAR2, TARGET_TYPE_NAME VARCHAR2, TARGET_TYPE_OWNER VARCHAR2)
return XMLType
as
 ROOT_NODE_NAME VARCHAR2(128);
 ATTR_DETAIL XMLTYPE;
 XPATH_EXPRESSION VARCHAR2(129);
 CURSOR FIND_CHILD_ATTRS is
 select ATTR_NAME, ATTR_TYPE_OWNER, ATTR_TYPE_NAME, INHERITED
 from ALL_TYPE_ATTRS
 where OWNER = TARGET_TYPE_OWNER
 and TYPE_NAME = TARGET_TYPE_NAME
 order by ATTR_NO;
 CHILD_ATTR XMLTYPE;
 ATTR_COUNT NUMBER := 0;
 TEMP number;
 COLLECTION_TYPE_NAME varchar2(256);
 COLLECTION_TYPE_OWNER varchar2(256);
begin
-- -- dbms_output.put_line('Processing Attribute ' || ATTR_NAME || ' of ' || TARGET_TYPE_OWNER || '.' || TARGET_TYPE_NAME );
ATTR_DETAIL := makeElement(ATTR_NAME);
XPATH_EXPRESSION := '/' || ATTR_DETAIL.GETROOTELEMENT();
for ATTR in FIND_CHILD_ATTRS loop
 begin
 select ELEM_TYPE_NAME, ELEM_TYPE_OWNER
 into COLLECTION_TYPE_NAME, COLLECTION_TYPE_OWNER
 from ALL_COLL_TYPES
 where TYPE_NAME = ATTR.ATTR_TYPE_NAME
 and OWNER = ATTR.ATTR_TYPE_OWNER;
 CHILD_ATTR := analyzeSQLType(ATTR.ATTR_NAME, COLLECTION_TYPE_NAME, COLLECTION_TYPE_OWNER );
 ATTR_COUNT := ATTR_COUNT + CHILD_ATTR.extract('/' || CHILD_ATTR.GETROOTELEMENT() || '/@sqlAttrs').getNumberVal();
 select appendChildXML(ATTR_DETAIL,XPATH_EXPRESSION,CHILD_ATTR)
 into ATTR_DETAIL
 from DUAL;
 exception
 when no_data_found then
 begin
 select 1
 into TEMP
 from ALL_TYPES
 where TYPE_NAME = ATTR.ATTR_TYPE_NAME
 and OWNER = ATTR.ATTR_TYPE_OWNER;
 CHILD_ATTR := analyzeSQLType(ATTR.ATTR_NAME, ATTR.ATTR_TYPE_NAME, ATTR.ATTR_TYPE_OWNER );
 ATTR_COUNT := ATTR_COUNT + CHILD_ATTR.extract('/' || CHILD_ATTR.GETROOTELEMENT() || '/@sqlAttrs').getNumberVal();
 select appendChildXML(ATTR_DETAIL,XPATH_EXPRESSION,CHILD_ATTR)
 into ATTR_DETAIL
 from DUAL;
 exception
 when no_data_found then
 ATTR_COUNT := ATTR_COUNT + 1;
 end;
 end;
end loop;
select insertChildXML(ATTR_DETAIL,XPATH_EXPRESSION,'@sqlAttrs',ATTR_COUNT)
 into ATTR_DETAIL
 from dual;
return ATTR_DETAIL;
end;
function analyzeComplexType(COMPLEX_TYPE VARCHAR2)
return XMLType
as
RESULT xmltype;
SQLTYPE varchar2(128);
SQLTYPE_OWNER varchar2(32);
begin
select SQLTYPE, SQLTYPE_OWNER
 into SQLTYPE, SQLTYPE_OWNER
 from USER_XML_SCHEMAS,
 xmlTable
 xmlnamespaces
 'http://www.w3.org/2001/XMLSchema' as "xsd",
 'http://xmlns.oracle.com/xdb' as "xdb"
 '/xsd:schema/xsd:complexType'
 passing Schema
 columns
 COMPLEX_TYPE_NAME varchar2(4000) path '@name',
 SQLTYPE varchar2(128) path '@xdb:SQLType',
 SQLTYPE_OWNER varchar2(32) path '@xdb:SQLSchema'
 where COMPLEX_TYPE_NAME = COMPLEX_TYPE;
result := analyzeSQLType(COMPLEX_TYPE,SQLTYPE,SQLTYPE_OWNER);
select insertChildXML(RESULT,'/' || COMPLEX_TYPE,'@SQLType',SQLTYPE)
 into result
 from dual;
return result;
end;
function showSQLTypes(schemaFolder varchar2) return XMLType
is
xmlSchema XMLTYPE;
begin
select xmlElement
 "TypeList",
 xmlAgg
 xmlElement
 "Schema",
 xmlElement
 "ResourceName",
 extractValue(res,'/Resource/DisplayName')
 xmlElement
 "complexTypes",
 select xmlAgg
 xmlElement
 "complexType",
 xmlElement
 "name",
 extractValue(value(XML),'/xsd:complexType/@name',XDB_NAMESPACES.XDBSCHEMA_PREFIXES)
 xmlElement
 "SQLType",
 extractValue(value(XML),'/xsd:complexType/@xdb:SQLType',XDB_NAMESPACES.XDBSCHEMA_PREFIXES)
 from table
 xmlsequence
 extract
 xdburitype(p.path).getXML(),
 '/xsd:schema/xsd:complexType',
 XDB_NAMESPACES.XDBSCHEMA_PREFIXES
 ) xml
 -- order by extractValue(value(XML),'/xsd:complexType/@name',XDB_NAMESPACES.XDBSCHEMA_PREFIXES)
 ).extract('/*')
 into xmlSchema
 from path_view p
 where under_path(res,schemaFolder) = 1
 order by extractValue(res,'/Resource/DisplayName');
return xmlSchema;
end;
procedure renameCollectionTable (XMLTABLE varchar2, XPATH varchar2, COLLECTION_TABLE_PREFIX varchar2)
as
 SYSTEM_GENERATED_NAME varchar2(256);
 COLLECTION_TABLE_NAME varchar2(256);
 CLUSTERED_INDEX_NAME varchar2(256);
 PARENT_INDEX_NAME varchar2(256);
 RENAME_STATEMENT varchar2(4000);
begin
 COLLECTION_TABLE_NAME := COLLECTION_TABLE_PREFIX || '_TABLE';
 CLUSTERED_INDEX_NAME := COLLECTION_TABLE_PREFIX || '_DATA';
 PARENT_INDEX_NAME := COLLECTION_TABLE_PREFIX || '_LIST';
 select TABLE_NAME
 into SYSTEM_GENERATED_NAME
 from ALL_NESTED_TABLES
 where PARENT_TABLE_NAME = XMLTABLE
 and PARENT_TABLE_COLUMN = XPATH
 and OWNER = USER;
 RENAME_STATEMENT := 'alter table ' || USER || '."' || SYSTEM_GENERATED_NAME || '" rename to "' ||COLLECTION_TABLE_NAME || '"';
 -- -- dbms_output.put_line(RENAME_STATEMENT);
 execute immediate RENAME_STATEMENT;
 begin
 select INDEX_NAME
 into SYSTEM_GENERATED_NAME
 from ALL_INDEXES
 where TABLE_NAME = COLLECTION_TABLE_NAME
 and INDEX_TYPE = 'IOT - TOP'
 and OWNER = USER;
 RENAME_STATEMENT := 'alter index ' || USER || '."' || SYSTEM_GENERATED_NAME || '" rename to "' || CLUSTERED_INDEX_NAME || '"';
 -- -- dbms_output.put_line(RENAME_STATEMENT);
 execute immediate RENAME_STATEMENT;
 exception
 when NO_DATA_FOUND then
 null;
 end;
 begin
 select INDEX_NAME
 into SYSTEM_GENERATED_NAME
 from ALL_IND_columns
 where COLUMN_NAME = XPATH
 and TABLE_NAME = XMLTABLE
 and TABLE_OWNER = USER;
 RENAME_STATEMENT := 'alter index ' || USER || '."' || SYSTEM_GENERATED_NAME || '" rename to "' || PARENT_INDEX_NAME || '"';
 -- -- dbms_output.put_line(RENAME_STATEMENT);
 execute immediate RENAME_STATEMENT;
 exception
 when NO_DATA_FOUND then
 null;
 end;
end;
function processNestedTable(currentLevel in out number, currentNode in out XMLType, query SYS_REFCURSOR)
return XMLType
is
thisLevel number;
thisNode xmlType;
result xmlType;
begin
thisLevel := currentLevel;
thisNode := currentNode;
fetch query into currentLevel, currentNode;
if (query%NOTFOUND) then
 currentLevel := -1;
end if;
while (currentLevel >= thisLevel) loop
 -- Next Node is a decendant of sibling of this Node.
 if (currentLevel > thisLevel) then
 -- Next Node is a decendant of this Node.
 result := processNestedTable(currentLevel, currentNode, query);
 select xmlElement
 "Collection",
 extract(thisNode,'/Collection/*'),
 xmlElement
 "NestedCollections",
 result
 into thisNode
 from dual;
 else
 -- Next node is a sibling of this Node.
 result := processNestedTable(currentLevel, currentNode, query);
 select xmlconcat(thisNode,result) into thisNode from dual;
 end if;
end loop;
-- Next Node is a sibling of some ancestor of this node.
return thisNode;
end;
function printNestedTables(XML_TABLE varchar2)
return XMLType
is
 query SYS_REFCURSOR;
 result XMLType;
 rootLevel number := 0;
 rootNode xmlType;
begin
 open query for
 select level, xmlElement
 "Collection",
 xmlElement
 "CollectionId",
 PARENT_TABLE_COLUMN
 ) as XML
 from USER_NESTED_TABLES
 connect by PRIOR TABLE_NAME = PARENT_TABLE_NAME
 start with PARENT_TABLE_NAME = XML_TABLE;
 fetch query into rootLevel, rootNode;
 result := processNestedTable(rootLevel, rootNode, query);
 select xmlElement
 "NestedTableStructure",
 result
 into result
 from dual;
 return result;
end;
function generateSchemaFromTable(P_TABLE_NAME varchar2, P_OWNER varchar2 default USER)
return XMLTYPE
as
xmlSchema XMLTYPE;
begin
select xmlElement
 "xsd:schema",
 xmlAttributes
 'http://www.w3.org/2001/XMLSchema' as "xmlns:xsd",
 'http://xmlns.oracle.com/xdb' as "xmlns:xdb"
 xmlElement
 "xsd:element",
 xmlAttributes
 'ROWSET' as "name",
 'rowset' as "type"
 xmlElement
 "xsd:complexType",
 xmlAttributes
 'rowset' as "name"
 xmlElement
 "xsd:sequence",
 xmlElement
 "xsd:element",
 xmlAttributes
 'ROW' as "name",
 table_name || '_T' as "type",
 'unbounded' as "maxOccurs"
 xmlElement
 "xsd:complexType",
 xmlAttributes
 table_name || '_T' as "name"
 xmlElement
 "xsd:sequence",
 xmlAgg(ELEMENT order by INTERNAL_COLUMN_ID)
 into xmlSchema
 from (select TABLE_NAME, INTERNAL_COLUMN_ID,
 case
 when DATA_TYPE in ('VARCHAR2','CHAR') then
 xmlElement
 "xsd:element",
 xmlattributes
 column_name as "name",
 decode(NULLABLE, 'Y', 0, 1) as "minOccurs",
 column_name as "xdb:SQLName",
 DATA_TYPE as "xdb:SQLType"
 xmlElement
 "xsd:simpleType",
 xmlElement
 "xsd:restriction",
 xmlAttributes
 'xsd:string' as "base"
 xmlElement
 "xsd:maxLength",
 xmlAttributes
 DATA_LENGTH as "value"
 when DATA_TYPE = 'NUMBER' then
 xmlElement
 "xsd:element",
 xmlattributes
 column_name as "name",
 decode(NULLABLE, 'Y', 0, 1) as "minOccurs",
 column_name as "xdb:SQLName",
 DATA_TYPE as "xdb:SQLType"
 xmlElement
 "xsd:simpleType",
 xmlElement
 "xsd:restriction",
 xmlAttributes
 decode(DATA_SCALE, 0, 'xsd:integer', 'xsd:double') as "base"
 xmlElement
 "xsd:totalDigits",
 xmlAttributes
 DATA_PRECISION as "value"
 when DATA_TYPE = 'DATE' then
 xmlElement
 "xsd:element",
 xmlattributes
 column_name as "name",
 decode(NULLABLE, 'Y', 0, 1) as "minOccurs",
 'xsd:date' as "type",
 column_name as "xdb:SQLName",
 DATA_TYPE as "xdb:SQLType"
 when DATA_TYPE like 'TIMESTAMP%WITH TIME ZONE' then
 xmlElement
 "xsd:element",
 xmlattributes
 column_name as "name",
 decode(NULLABLE, 'Y', 0, 1) as "minOccurs",
 'xsd:dateTime' as "type",
 column_name as "xdb:SQLName",
 DATA_TYPE as "xdb:SQLType"
 else
 xmlElement
 "xsd:element",
 xmlattributes
 column_name as "name",
 decode(NULLABLE, 'Y', 0, 1) as "minOccurs",
 'xsd:anySimpleType' as "type",
 column_name as "xdb:SQLName",
 DATA_TYPE as "xdb:SQLType"
 end ELEMENT
 from all_tab_cols c
 where c.TABLE_NAME = P_TABLE_NAME
 and c.OWNER = P_OWNER
 group by TABLE_NAME;
return xmlSchema;
end;
function appendElementList(V_ELEMENT_LIST IN OUT XDB.XDB$XMLTYPE_REF_LIST_T, V_CHILD_ELEMENT_LIST XDB.XDB$XMLTYPE_REF_LIST_T) return XDB.XDB$XMLTYPE_REF_LIST_T;
function expandModel(P_MODEL XDB.XDB$MODEL_T) return XDB.XDB$XMLTYPE_REF_LIST_T;
function expandChoiceList(P_CHOICE_LIST XDB.XDB$XMLTYPE_REF_LIST_T) return XDB.XDB$XMLTYPE_REF_LIST_T;
function expandSequenceList(P_SEQUENCE_LIST XDB.XDB$XMLTYPE_REF_LIST_T) return XDB.XDB$XMLTYPE_REF_LIST_T;
function expandGroupList(P_GROUP_LIST XDB.XDB$XMLTYPE_REF_LIST_T) return XDB.XDB$XMLTYPE_REF_LIST_T;
function appendElementList(V_ELEMENT_LIST IN OUT XDB.XDB$XMLTYPE_REF_LIST_T, V_CHILD_ELEMENT_LIST XDB.XDB$XMLTYPE_REF_LIST_T)
return XDB.XDB$XMLTYPE_REF_LIST_T
as
begin
SELECT CAST
 SET
 CAST(V_ELEMENT_LIST as XDBPM.XMLTYPE_REF_TABLE_T)
 MULTISET UNION
 CAST(V_CHILD_ELEMENT_LIST as XDBPM.XMLTYPE_REF_TABLE_T)
 as XDB.XDB$XMLTYPE_REF_LIST_T
 into V_ELEMENT_LIST
 from DUAL;
 return V_ELEMENT_LIST;
end;
function expandModel(P_MODEL XDB.XDB$MODEL_T)
return XDB.XDB$XMLTYPE_REF_LIST_T
as
V_ELEMENT_LIST XDB.XDB$XMLTYPE_REF_LIST_T;
V_CHILD_ELEMENT_LIST XDB.XDB$XMLTYPE_REF_LIST_T;
begin
V_ELEMENT_LIST := XDB.XDB$XMLTYPE_REF_LIST_T();
if P_MODEL.ELEMENTS is not null then
 V_ELEMENT_LIST := P_MODEL.ELEMENTS;
end if;
if (P_MODEL.CHOICE_KIDS is not NULL) then
 V_CHILD_ELEMENT_LIST := expandChoiceList(P_MODEL.CHOICE_KIDS);
 V_ELEMENT_LIST := appendElementList(V_ELEMENT_LIST,V_CHILD_ELEMENT_LIST);
end if;
if (P_MODEL.SEQUENCE_KIDS is not NULL) then
 V_CHILD_ELEMENT_LIST := expandSequenceList(P_MODEL.SEQUENCE_KIDS);
 V_ELEMENT_LIST := appendElementList(V_ELEMENT_LIST,V_CHILD_ELEMENT_LIST);
end if;
-- Process ANYS
if (P_MODEL.GROUPS is not NULL) then
 V_CHILD_ELEMENT_LIST := expandGroupList(P_MODEL.GROUPS);
 V_ELEMENT_LIST := appendElementList(V_ELEMENT_LIST,V_CHILD_ELEMENT_LIST);
end if;
return V_ELEMENT_LIST;
end;
function expandChoiceList(P_CHOICE_LIST XDB.XDB$XMLTYPE_REF_LIST_T)
return XDB.XDB$XMLTYPE_REF_LIST_T
as
V_ELEMENT_LIST XDB.XDB$XMLTYPE_REF_LIST_T;
V_CHILD_ELEMENT_LIST XDB.XDB$XMLTYPE_REF_LIST_T;
cursor getChoices is
select c.XMLDATA MODEL
 from XDB.XDB$CHOICE_MODEL c, TABLE(P_CHOICE_LIST) cl
 where ref(c) = value(cl);
begin
V_ELEMENT_LIST := XDB.XDB$XMLTYPE_REF_LIST_T();
for c in getChoices loop
 V_CHILD_ELEMENT_LIST := expandModel(c.MODEL);
 V_ELEMENT_LIST := appendElementList(V_ELEMENT_LIST,V_CHILD_ELEMENT_LIST);
end loop;
return V_ELEMENT_LIST;
end;
function expandSequenceList(P_SEQUENCE_LIST XDB.XDB$XMLTYPE_REF_LIST_T)
return XDB.XDB$XMLTYPE_REF_LIST_T
as
V_ELEMENT_LIST XDB.XDB$XMLTYPE_REF_LIST_T;
V_CHILD_ELEMENT_LIST XDB.XDB$XMLTYPE_REF_LIST_T;
cursor getSequences is
select s.XMLDATA MODEL
 from XDB.XDB$SEQUENCE_MODEL s, TABLE(P_SEQUENCE_LIST) sl
 where ref(s) = value(sl);
begin
V_ELEMENT_LIST := XDB.XDB$XMLTYPE_REF_LIST_T();
for s in getSequences loop
 V_CHILD_ELEMENT_LIST := expandModel(s.MODEL);
 V_ELEMENT_LIST := appendElementList(V_ELEMENT_LIST,V_CHILD_ELEMENT_LIST);
end loop;
return V_ELEMENT_LIST;
end;
function expandGroupList(P_GROUP_LIST XDB.XDB$XMLTYPE_REF_LIST_T)
return XDB.XDB$XMLTYPE_REF_LIST_T
as
V_ELEMENT_LIST XDB.XDB$XMLTYPE_REF_LIST_T;
V_CHILD_ELEMENT_LIST XDB.XDB$XMLTYPE_REF_LIST_T; V_MODEL XDB.XDB$MODEL_T;
cursor getGroups is
SELECT CASE
 -- Return The MODEL Definition for the CHOICE, ALL or SEQUENCE
 WHEN gd.XMLDATA.ALL_KID is not NULL
 THEN ( SELECT a.XMLDATA from XDB.XDB$ALL_MODEL a where ref(a) = gd.XMLDATA.ALL_KID)
 WHEN gd.XMLDATA.SEQUENCE_KID is not NULL
 THEN ( SELECT s.XMLDATA from XDB.XDB$SEQUENCE_MODEL s where ref(s) = gd.XMLDATA.SEQUENCE_KID)
 WHEN gd.XMLDATA.CHOICE_KID is not NULL
 THEN ( SELECT c.XMLDATA from XDB.XDB$CHOICE_MODEL c where ref(c) = gd.XMLDATA.CHOICE_KID)
 END MODEL
 FROM XDB.XDB$GROUP_DEF gd, XDB.XDB$GROUP_REF gr, TABLE(P_GROUP_LIST) gl
 WHERE ref(gd) = gr.XMLDATA.GROUPREF_REF
 and ref(gr) = value(gl);
begin
V_ELEMENT_LIST := XDB.XDB$XMLTYPE_REF_LIST_T();
for g in getGroups loop
 V_CHILD_ELEMENT_LIST := expandModel(g.MODEL);
 V_ELEMENT_LIST := appendElementList(V_ELEMENT_LIST,V_CHILD_ELEMENT_LIST);
end loop;
return V_ELEMENT_LIST;
end;
function getComplexTypeElementList(P_COMPLEX_TYPE_REF REF XMLTYPE)
return XDB.XDB$XMLTYPE_REF_LIST_T
as
V_MODEL XDB.XDB$MODEL_T;
V_BASE_TYPE REF XMLTYPE;
V_ELEMENT_LIST XDB.XDB$XMLTYPE_REF_LIST_T := XDB.XDB$XMLTYPE_REF_LIST_T();
begin
SELECT ct.XMLDATA.BASE_TYPE,
 CASE
 -- Return The MODEL Definition for the CHOICE, ALL or SEQUENCE
 WHEN ct.XMLDATA.ALL_KID is not NULL
 THEN ( SELECT a.XMLDATA from XDB.XDB$ALL_MODEL a where ref(a) = ct.XMLDATA.ALL_KID)
 WHEN ct.XMLDATA.SEQUENCE_KID is not NULL
 THEN ( SELECT s.XMLDATA from XDB.XDB$SEQUENCE_MODEL s where ref(s) = ct.XMLDATA.SEQUENCE_KID)
 WHEN ct.XMLDATA.CHOICE_KID is not NULL
 THEN ( SELECT c.XMLDATA from XDB.XDB$CHOICE_MODEL c where ref(c) = ct.XMLDATA.CHOICE_KID)
 WHEN ct.XMLDATA.GROUP_KID is not NULL
 -- COMPLEXTYPE is based on a GROUP.
 THEN (
 -- RETURN The CHOICE, ALL or SEQUENCE for GROUP
 SELECT CASE
 WHEN gd.XMLDATA.ALL_KID is not NULL
 THEN ( SELECT a.XMLDATA from XDB.XDB$ALL_MODEL a where ref(a) = gd.XMLDATA.ALL_KID)
 WHEN gd.XMLDATA.SEQUENCE_KID is not NULL
 THEN ( SELECT s.XMLDATA from XDB.XDB$SEQUENCE_MODEL s where ref(s) = gd.XMLDATA.SEQUENCE_KID)
 WHEN gd.XMLDATA.CHOICE_KID is not NULL
 THEN ( SELECT c.XMLDATA from XDB.XDB$CHOICE_MODEL c where ref(c) = gd.XMLDATA.CHOICE_KID)
 END
 FROM XDB.XDB$GROUP_DEF gd, xdb.xdb$GROUP_REF gr
 WHERE ref(gd) = gr.XMLDATA.GROUPREF_REF
 and ref(gr) = ct.XMLDATA.GROUP_KID
-- WHEN ct.XMLDATA.COMPLEXCONTENT.RESTRICTION.ALL_KID is not NULL
-- THEN ( SELECT a.XMLDATA from XDB.XDB$ALL_MODEL a where ref(a) = ct.XMLDATA.COMPLEXCONTENT.RESTRICTION.ALL_KID)
-- WHEN ct.XMLDATA.COMPLEXCONTENT.RESTRICTION.SEQUENCE_KID is not NULL
-- THEN ( SELECT s.XMLDATA from XDB.XDB$SEQUENCE_MODEL s where ref(s) = ct.XMLDATA.COMPLEXCONTENT.RESTRICTION.SEQUENCE_KID)
-- WHEN ct.XMLDATA.COMPLEXCONTENT.RESTRICTION.CHOICE_KID is not NULL
-- THEN ( SELECT c.XMLDATA from XDB.XDB$CHOICE_MODEL c where ref(c) = ct.XMLDATA.COMPLEXCONTENT.RESTRICTION.CHOICE_KID)
-- WHEN ct.XMLDATA.COMPLEXCONTENT.RESTRICTION.GROUP_KID is not NULL
-- -- COMPLEXTYPE is based on a GROUP.
-- THEN (
-- -- RETURN The CHOICE, ALL or SEQUENCE for GROUP
-- SELECT CASE
-- WHEN gd.XMLDATA.ALL_KID is not NULL
-- THEN ( SELECT a.XMLDATA from XDB.XDB$ALL_MODEL a where ref(a) = gd.XMLDATA.ALL_KID)
-- WHEN gd.XMLDATA.SEQUENCE_KID is not NULL
-- THEN ( SELECT s.XMLDATA from XDB.XDB$SEQUENCE_MODEL s where ref(s) = gd.XMLDATA.SEQUENCE_KID)
-- WHEN gd.XMLDATA.CHOICE_KID is not NULL
-- THEN ( SELECT c.XMLDATA from XDB.XDB$CHOICE_MODEL c where ref(c) = gd.XMLDATA.CHOICE_KID)
-- END
-- FROM XDB.XDB$GROUP_DEF gd, xdb.xdb$GROUP_REF gr
-- WHERE ref(gd) = gr.XMLDATA.GROUPREF_REF
-- and ref(gr) = ct.XMLDATA.COMPLEXCONTENT.RESTRICTION.GROUP_KID
 WHEN ct.XMLDATA.COMPLEXCONTENT.EXTENSION.ALL_KID is not NULL
 THEN ( SELECT a.XMLDATA from XDB.XDB$ALL_MODEL a where ref(a) = ct.XMLDATA.COMPLEXCONTENT.EXTENSION.ALL_KID)
 WHEN ct.XMLDATA.COMPLEXCONTENT.EXTENSION.SEQUENCE_KID is not NULL
 THEN ( SELECT s.XMLDATA from XDB.XDB$SEQUENCE_MODEL s where ref(s) = ct.XMLDATA.COMPLEXCONTENT.EXTENSION.SEQUENCE_KID)
 WHEN ct.XMLDATA.COMPLEXCONTENT.EXTENSION.CHOICE_KID is not NULL
 THEN ( SELECT c.XMLDATA from XDB.XDB$CHOICE_MODEL c where ref(c) = ct.XMLDATA.COMPLEXCONTENT.EXTENSION.CHOICE_KID)
 WHEN ct.XMLDATA.COMPLEXCONTENT.EXTENSION.GROUP_KID is not NULL
 -- COMPLEXTYPE is based on a GROUP.
 THEN (
 -- RETURN The CHOICE, ALL or SEQUENCE for GROUP
 SELECT CASE
 WHEN gd.XMLDATA.ALL_KID is not NULL
 THEN ( SELECT a.XMLDATA from XDB.XDB$ALL_MODEL a where ref(a) = gd.XMLDATA.ALL_KID)

Date fields in the Maintainence View.

Hello friends,
I created a maintanence view which of 2 steps. This view contains a DATE field of data element type 'DATS". Now the problem is -"
1. In the first screen of the viewI am not able to see only the DATE field(Over view scr).
2. But I able to see the same field in the 2nd screen(Maintanence Screen).
Not only to my View I maintained ' Table Maintanence Generator" to some more tables.There also I am not able to see the date field in the first screen, unless it is a key field.
Thanks in advance.

Hi
Step 1: Create & Maintain Table (SE11)
Screen 101: ABAP Dictionary: Initial Screen
Screen 102: Maintain Table -> Delivery and Maintenance
Screen 103: Maintain Table -> Fields
[] SE11: Enter Table Name -> Create
Enter Table Description (Mandatory Field)
Select Delivery Class
Set maintenance level
Enter Fields, Assign Data Elements
Save Entries
Check Inconsistencies
Activate Table
Go To Technical Settings (SCREEN 104)
Delivery Class: The delivery class controls the transport of table data when
installing or upgrading, in a client copy and when transporting between customer
systems. The delivery class is also used in the extended table
maintenance.
There are the following delivery classes:
A: Application table (master and transaction data).
C: Customer table, data is maintained by the customer only.
L: Table for storing temporary data.
G: Customer table. The customer namespace must be defined in table TRESC. (Use
Report RDDKOR54 here).
E: System table with its own namespaces for customer entries.
S: System table, data changes have the same status as program changes.
W: System table (e.g. table of the development environment) whose
data is transported with its own transport objects (e.g. R3TR PROG, R3TR TABL,
etc.).
Data Browser/Table View Maint.: This indicator specifies
whether it is possible to display/maintain a table or view using the maintenance
tools Data Browser (transaction SE16) and table view maintenance (transactions
SM30 and SM31).
MANDT field is mandatory for Client dependant tables
Technical Settings: The technical settings control, for example, table buffering.
Indexes: To speed up data selection, you can create secondary indexes for the table
Append Structure: Append structures are used for enhancements that are not included in the standard.
Screen 104: Maintain Technical Settings
Select Data Class (Mandatory) [APPL0]
Select Size Category (Table size - No. of records - Mandatory) [1 to 6]
Specify Buffering [allowed / not allowed]
Save
Check Inconsistencies
Activate & Go Back to Maintain Table Screen
Data Class: The data class defines the physical area of the database (for ORACLE
the TABLESPACE) in which your table is logically stored. If you choose a data
class correctly, your table will automatically be assigned to the correct area
when it is created on the database.
The most important data classes
are (other than the system data):
APPL0 Master data
APPL1 Transaction data
APPL2 Organizational and customizing data
Size category: The size category determines the probable space requirement for a table in the database.
Buffering: The buffering status specifies whether or not a table may be buffered.
Screen 105: Maintain Table
Screen 106: Maintain Enhancement Category (ECC 6.0 onwards)
-> Extras -> Enhancement Category
Select Enhancement Category
Enhancement Category: Structures and tables that were defined by SAP in the ABAP
Dictionary can be enhanced subsequently by customers using Customizing includes
or append structures. The enhancements do not only refer to structures/ tables
themselves, but also to dependent structures that adopt the enhancement as an
include or referenced structure. Append structures that only take effect at the
end of the original structure can also cause shifts - in the case of dependent
structures - even within these structures.
Screen 107: Maintain Table -> Table Maintenance Generator
Screen 108: Generate Table Maintenance Dialog: Generation Environment
-> Utilities -> Table Maintenance Generator OR [] SE54
Specify Authorization Group [&NC&]
Select Maintenance type [One Step/Two Step]
Mention Screen Numbers [1/2]
Save & Go Back
Single step: Only overview screen is created i.e. the Table Maintenance Program will have only one screen where you can add, delete or edit records.Two step: Two screens namely the overview screen and Single screen are created. The user can see the key fields in the first screen and can further go on to edit further details.

Refresh data in Table Maintenance view

Hi,
I have created a table maintenance view for db table A and added my function button to this view. When I click the button I append a few records to the table A from table B. But this recoreds are not displaied in the view.
If I rerun the view I can see added records.
How I have to refresh the view to display added records?
Regards,
Ilya

Hi Jesus,
COMMIT WORK isn't help me.
I found that I have to use TOTAL and EXTRACT structures to modify data in maintenance view.
It's fine. I do something like this in my FM
MODULE 9CUSTOM_PF_BUTTON INPUT.
lt_total[] = total[].
lt_extract[] = extract[].
CASE function.
      WHEN '9DOWNSH'.
         modify lt_total from wa_total.
         modify lt_extract from wa_extract
ENDCASE.
total[]   = lt_total[].
extract[] = lt_extract[].
ENDMODULE.                 " 9CUSTOM_PF_BUTTON INPUT
But TOTL and EXTRACT tables contain data of the current maintenance view.
I work with a view cluster and I have to append or delete records from one view if I do something in other view.
How I can modify data one view from another maintenance view?
If I have modified database tables directly I don't see changes in the view cluster.
Regards,
Malnor
Edited by: Malnor on Nov 23, 2010 9:19 AM
Edited by: Malnor on Nov 23, 2010 9:38 AM

Aotu numbering in table maintenance view

Hi experts,
Can anybody help me in auto genereating serial number in table maintenance view. I have created table maintanance view for a z table for which first field is serial no. The requirement is this serial number should be auto genereted. increment by 1. I have writeen the code for the same in PAI event, but it getting incremented by number of rows. e.g for secind row counter is incremented by +2. for thrid row it is +3 and so on....
plz help to achieve consistency .
Thnks n regards,
Ashmita Singh

What happens if the user deletes a recird from the table?
Suhas,
Happy New Year
Disable delete function and provide a deletion indicator. This should be fine right.
The problem would be when the maintenance dialog is regenerated.
@OP - So as suggesgted use events.
Similar threads were discussed before many times. May be you culd search it once.

Table maintenance view Events

Hi
In My Z Table maintenance view i had implemented a new event 01- Before save. But my table entry's are not getting saved now and also i am not getting any error message.
Please help me on this.
Regards,
Naidu Vecahalapu.

Hi Naidu,
In the event code of the table maintenance view, please ensure that the SY-SUBRC is ZERO before exiting the sub-routine. Otherwise your changes (insert, update or delete) won't get updated and also you won't get any error message.
Regards
Suresh

How to Create/Modify/Delete a query view from the web template in BI 7.0

All:
In BW 3.5, the Query Selection View web item was introduced for users to create a query view to save the navigational state of a query. This web item was also available to modify and delete an existing query view.
The Query Selection View web item does not exist in BI 7.0. I see the drop down web item can be used to display the query views associated to a query.
Can anyone share how to create,modify,save or delete a query view on the web in BI 7.0
Thanks,
Kumar

Sanjay, we experienced the same issue. Below are a few pieces of information that may be of help: 1-The Save As button on the 0ANALYZER template saves the query to the portal. From Bex Web or Bex Analyzer, you have no access to these saved views. We created a ZANALYZER copy of the 0ANALYZER template and removed the Save As button. 2- If you right mouse click on any item in the query results grid of Bex Web, you get a small menu. Clicking on the menu item Save View will save the view to BI. You do not have the ability to delete the saved views from Bex Web. However, you can delete them from Bex Analyzer. This was not an option for us since most of our users are using Bex Web. 3- On the same menu, clicking on Bookmark, saves the navigation and also opens the Internet Explorer Favorites maintence window. The navigation is saved as an entry into the users Internet Explorer favorites where they can organize and delete their entries. However, deleting the favorite does not delete the entry for the bookmark in BI. The bookmarks are stored in table RSWR_DATA. Program RSWR_BOOKMARK_REORG can be used to manage the saved bookmarks. We are loading RSWR_DATA into a chracteristic so that we can query the information in order to help us manage it. I hope this helps you and others that appear to be struggling with the issue of saved views in Bex Web.

To use a maintainence view in programe.

Unlike projection and database views, i am not able to use maintainence views for getting the data using the SELECT query .
How can we get the associated data using the maintainence view.

Hi,
We can call the VIEW_MAINTENANCE_CALL function module inorder to use the maintenace view.
To this pass the view names and U for Updattion and S for display.
This maintainenance is used to update the tables and display them.
pls check this link for it's usage -
Plant , Storage Locations...
Regards
Lekha

Maintainence View-Data Selection

Hi,
    I need to update a table in Oracle with the SAP data.
    The SAP data is in a maintainence View.When I try to select the data into an internal table ,I am getting an error message that tells that the corresponding View is not defined in the DB as a table ,projection view or database view.
Can we select data from a Maintainence View??
Thanks.

Hi,
check this
MAINTENANCE VIEWS:
Maintenance View   ( SE54 )
Maintenance views enable a business-oriented approach to looking at data, while at the same time, making it possible to maintain the data involved. Data from several tables can be summarized in a maintenance view and maintained collectively via this view. That is, the data is entered via the view and then distributed to the underlying tables by the system.
Data that is distributed on more than one table often forms a logical unit, called an application object. You should be able to display, change and create the data of such an application object together. Users usually are not interested in the technical implementation of the application object, such as the distribution of the data on several tables.
You can maintain complex application objects in a simple way using a maintenance view. The data is automatically distributed on the underlying database tables.
All the tables used in a maintenance view must be linked with a foreign key. This means that the join conditions are always derived from the foreign key in the maintenance view. You cannot enter the join conditions directly as in a database view.
A maintenance interface with which the data of the view can be displayed, changed and created must be generated from the definition of a maintenance view in the ABAP Dictionary.
When the maintenance interface is created, function modules that distribute the data maintained with the view on the underlying tables are automatically generated.
The maintenance interface is generated with the Transaction Generate Table View (Transaction SE54) or from the view maintenance screen with Utilities -> Tab.maint.generator.
With thanks & regards,
Sravani yendru.

ORA-00942 - What is the table or view that not exists?

Hi,
Is there any way to identify which table or view that the error message refers, in a SQL code (select, insert, etc)?

SQL> select * from garbage;
select * from garbage
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> insert into garbage values (1);
insert into garbage values (1)
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> update garbage set a = 1;
update garbage set a = 1
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> delete from garbage ;
delete from garbage
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> drop table garbage;
drop table garbage
ERROR at line 1:
ORA-00942: table or view does not exist
SQL>

Table Maintainence generator Error Special Character '_' in generic key

Hello,
I have created a Table which contain 6 fields. All the fields of the table are primary key. The combined length of all the primary key is 163 characters. In the activation Log of the table we have a warning message which states "Key length > 120 (Restricted functionality)". Initially we are able maintain the entries using SM30. BUt now when we are making the entreis in the table an error message comes. The error is Special character "_" in generic key.and we are not able to save the entries.
I have deleted the table maintainence generator and have regenerated it. But the same error is coming.
Please provide your suggestion.
Thanks,
Mohit

Please provide your suggestions
Thanks,
Mohit

Delete Table Maintainence View

Similar Messages

Maybe you are looking for