CAST MULTISET...is it supported by BI

Question

In a precedent POst i explained the problems we had with multiple queries to display data as a hierarchical manner, with more than 2 levels
We'd like to explore the way with CAST MULTISET...but before to spend time, we'd like to assure that it is supported by BI Publisher.
As an example ( with one level):
We prepared the Object Types as is :
create or replace TYPE ETAG_T AS OBJECT("@S_NUME_OBJE" NUMBER,
                    S_NUME_ETAG NUMBER,
                    C_TYPE_ETAG VARCHAR2(4 CHAR),
                    L_DESC_ETAG VARCHAR2(50 CHAR),
                    N_NOMB_PIEC NUMBER,
                    N_SURF_TOTA NUMBER,
                    D_MODI DATE,
                    R_FONC CHAR(5),
                    R_UTIL CHAR(20),
                    C_CODE_LANG VARCHAR2(4 CHAR)
create or replace TYPE etaglist_t AS TABLE OF etag_t
create or replace TYPE obje_t as Object (
"@S_NUME_OBJE" NUMBER,
N_NUME_IMME VARCHAR2(5) ,
N_NUME_OBJE VARCHAR2(5) ,
etag_list etaglist_t
Then the data query is (Statement is named Q1):
SELECT
obje_t(s_nume_obje, n_nume_obje, n_nume_imme,
CAST (MULTISET (SELECT S_NUME_OBJE,
                    S_NUME_ETAG,
                    C_TYPE_ETAG,
                    L_DESC_ETAG,
                    N_NOMB_PIEC,
                    N_SURF_TOTA,
                    D_MODI,
                    R_FONC,
                    R_UTIL,
                    C_CODE_LANG
FROM imm.b12_0 eta
WHERE eta.s_nume_obje = obj.s_nume_obje)
AS etaglist_t))
AS "obj"
FROM pointi.b02_v obj
WHERE obj.s_nume_obje= :sNumeObje
As a result , we get only the <obj> element like this :
<LIST_Q1>
<Q1>
<obj/>
</Q1>
</LIST_Q1>
We tried too :
SELECT XMLElement("Object",
obje_t(s_nume_obje, n_nume_obje, n_nume_imme,
CAST (MULTISET (SELECT S_NUME_OBJE,
                    S_NUME_ETAG,
                    C_TYPE_ETAG,
                    L_DESC_ETAG,
                    N_NOMB_PIEC,
                    N_SURF_TOTA,
                    D_MODI,
                    R_FONC,
                    R_UTIL,
                    C_CODE_LANG
FROM imm.b12_0 eta
WHERE eta.s_nume_obje = obj.s_nume_obje)
AS etaglist_t))
AS "obj" ) as "objXML"
FROM pointi.b02_v obj
WHERE obj.s_nume_obje= :sNumeObje
And we get :
<Q1>
<objXML/>
</Q1>
Seems to be not supported isn't it...
Laurent

Answer 1

Ok thanks,
I already checked your blog before to speak about pl/sql tables ;-)
I think , for maintenance, it will better too , than having a single query with many cast...Multiset , which could have more than 500 lines :-(
But in our case, as we should have kind of hierarchies in the XML (with levels) and collections, i think we should have a mix :
store pl/sql tables in a package, that will be reused from the main query, and certainly continue to use cast multiset to manage theses nested collections.
As you said, i think we could remove the use of Object Types as we do today.