Run Extended Analtytics / Create Star Schema based on Process Management Level Status

Dear HFM Gurus,
I have come across a requirement where I would need to automate extended analytics extraction based on Review Level / Approve Status of Entities. Once the Process Management Status changed to Approve status from Review Level 3 or they are in Review Level 3, corresponding 3-4 extracts will run for various levels of data (can be base level, parent level, adjustments etc. for various Scenarios). Also another requirement is that whatever process is built, it should run every hour to check the Process Management Status and extract accordingly, it should not extract if already extracted in the last run (that is if the extraction was already run in the last hour for RL3, and the Entity is still in RL3 in the next hour, it should not run the extract, if the RL3 is changed to Approved state, then the extract should be run. I know this is a lot of ask, request your guidance as to how to proceed with the same. Any help would be highly appreciated.
Warm Regards,
Sidd.

Hi Thanos,
I was able to accomplish this using excel and HFM API's. What I did was to dynamically create a process management grid in excel, dynamically refresh the data, check this data against the previous review level status which gets dynamically copied from the old refresh, generate the list of entities which are in RL3 / Approved (changed Status) and then based on that generate the extracts using HFM API's. I was able to generate this in both 11.1.2.3 and 11.1.2.1 using the corresponding API libraries which the version supports.
Thanks and Regards,
Sidd.

Similar Messages

Extended Analytics for star schema creation from HFM application

Hi,
I'm trying to create star schema via extended analytics from HFM application but facing below error
3/21/2013 12:30:07 PM : Status : Extracting Metadata
Schema did not previously exist.
Metadata update has failed. : (-2147217900) (One or more errors occurred during processing of command.)
Processing status change: (-2147217900)
Data processing failed. : (-2147217900) (One or more errors occurred during processing of command.)
3/21/2013 12:30:10 PM : Status : Processing completed with errors
Extended Analytics export completed with errors for Application GCS using Label GCS CON.
What could be the possible reason for it?
Also can someone please provide any suitable references or links to learn this EA for star schema creation.
Thanks,
Ravi Agrawal

The error you pasted here is incomplete. Look in the system messages and you will find more complete information that will lead you to the error's cause. Very often this is an error in the database, though sometimes it is caused by a metadata member with an invalid character. To determine whether it is data or metadata that causes the error, you could generate a schema with metadata only and see if the error appears.
-- Chris

Error with creating star schema using HsvStarSchemaACM

Hi,
I am trying to create a star schema using the API HsvStarSchemaACM. But when calling the create function of API, i get the below exception. Exception from HRESULT: 0x80040251 (A general error occurred while trying to obtain a database Reader/Writer lock). Is this something to do with the parameters passed and its connections(connection works fine and createstarschema is running thru workspace).
Any solutions to this is more welcome.
Thanks,
Logu

Can you provide details on HsvStarSchemaACM API? How is it related to ODI?

Star Schema and Cubes

Hi,
I'm learning the basic concept of data warehousing and I've some question in this regards.
1) I want to know, are we have to first create star schema and tables according to that star schema in dbms, from that star schema we have to built cubes OR we directly build cubes from extracted data through OLTP systems.
2) secondly, when we create cubes, in which formate they are store in dbms and are they directly load in the memory at run time?
Please clarify me in these concepts as new to data warehouse I've certain concept misunderstanding in this regards. Answers will be highly appreciated
Regards,
D.Abbasi

1) I want to know, are we have to first create star schema and tables according to that star schema in dbms, from that star schema we have to built cubes OR we directly build cubes from extracted data through OLTP systems. Star schema is the Dimensional Modeling Technique and that need to considered while creating Dimension and not cubes.
So you need to create first design your database either in Start schema or Snow flag and then need to create dimension tables and after wards Cubes.
2) secondly, when we create cubes, in which format they are store in dbms and are they directly load in the memory at run time?Cubes and Dimensions are stored in Database in some different format.
This is the nice article regarding how the data is store in DB,
http://www.dba-oracle.com/t_olap_dimensions_cubes.htm
Cheers
Nawneet
Edited by: Nawneet on Mar 29, 2010 5:47 AM
Edited by: Nawneet on Mar 29, 2010 5:50 AM

Can't insert schema-based xmltype into binary xmltype table

I'm having issues trying to use binary storage along with the ALLOW ANYSCHEMA clause. I can't use the XMLSchema-instance mechanism for creating my schema-based XMLType instances, so I'm using CreateSchemaBasedXml. When I try to insert the XMLType into the table, however, it seems to think it's not schema-based and throws an error. I trimmed down my schema for the purposes of this example. Here's the schema (schematest.xsd):
<?xml version="1.0" encoding="Windows-1252"?>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="FORMINFO">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="SUBJECT">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="ADDR">
                <xs:complexType>
                  <xs:sequence>
                    <xs:element name="STREET" type="xs:string" />
                    <xs:element name="CITY" type="xs:string" />
                    <xs:element name="STATEPROV" type="xs:string" />
                    <xs:element name="ZIP" type="xs:string" />
                  </xs:sequence>
                </xs:complexType>
              </xs:element>
            </xs:sequence>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:complexType>
</xs:element>
</xs:schema>Here's the instance file (schema testinst.xml):
<?xml version="1.0" encoding="utf-8"?>
<FORMINFO>
   <SUBJECT>
      <ADDR>
         <STREET>123 Main St</STREET>
         <CITY>Las Vegas</CITY>
         <STATEPROV>NV</STATEPROV>
         <ZIP>12345</ZIP>
      </ADDR>
   </SUBJECT>
</FORMINFO>I registered the schema and created the test table:
BEGIN
DBMS_XMLSCHEMA.registerschema(
   schemaurl => 'http://localhost/schematest.xsd',
   schemadoc => bfilename('XMLDIR','schematest.xsd'),
   gentables => false,
   gentypes => false,
   csid => nls_charset_id('AL32UTF8'),
   options => DBMS_XMLSCHEMA.REGISTER_BINARYXML);
END;
CREATE TABLE BINARYTEST OF XMLType
XMLTYPE STORE AS BINARY XML
ALLOW ANYSCHEMA;But trying to insert gives me an ORA-44422 error (this is on Oracle 11.1.0.7.0 Enterprise):
SQL> SET SERVEROUTPUT ON
SQL> declare
2    x XMLType;
3    xschema XMLType;
4 begin
5    x := XMLType(bfilename('XMLDIR', 'schematestinst.xml'), nls_charset_id('AL32UTF8'));
6    xschema := x.CreateSchemaBasedXml('http://localhost/schematest.xsd');
7    xschema.SchemaValidate();
8    DBMS_OUTPUT.PUT_LINE('Schema: ' || xschema.GetSchemaURL() || ' Validated: ' || xschema.IsSchemaValidated());
9
10    INSERT INTO BINARYTEST
11    VALUES (xschema);
12    commit;
13 end;
14 /
Schema: http://localhost/schematest.xsd Validated: 1
declare
ERROR at line 1:
ORA-44422: nonschema XML disallowed for this column
ORA-06512: at line 10You can see from my put_line statement that the XMLType object is reporting its schema URL correctly and thinks it's been validated. Changing the table to "ALLOW NONSCHEMA" allows the insert, but it inserts it as a non-schema-based document. Am I skipping a step here?
Thanks,
Jim

It might be a bug, but I am not yet sure...
See the following examples...
c:\>C:\oracle\product\11.1.0\db_1\bin\sqlplus.exe /nolog
SQL*Plus: Release 11.1.0.7.0 - Production on Mon Mar 23 22:14:41 2009
Copyright (c) 1982, 2008, Oracle. All rights reserved.
SQL> drop user otn cascade;
User dropped.
SQL> create user otn identified by otn;
User created.
SQL> grant xdbadmin, dba to otn;
Grant succeeded.
SQL> conn otn/otn
connected.
SQL> var schemaPath varchar2(256)
SQL> var schemaURL varchar2(256)
SQL>
SQL> begin
2    :schemaURL := 'http://localhost/schematest.xsd';
3    :schemaPath := '/public/schematest.xsd';
4 end;
5 /
PL/SQL procedure successfully completed.
SQL>
SQL> declare
2    res boolean;
3    xmlSchema xmlType := xmlType('<?xml version="1.0" encoding="Windows-1252"?>
4 <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
5    <xs:element name="FORMINFO">
6      <xs:complexType>
7        <xs:sequence>
8          <xs:element name="SUBJECT">
9            <xs:complexType>
10              <xs:sequence>
11                <xs:element name="ADDR">
12                  <xs:complexType>
13                    <xs:sequence>
14                      <xs:element name="STREET" type="xs:string" />
15                      <xs:element name="CITY" type="xs:string" />
16                      <xs:element name="STATEPROV" type="xs:string" />
17                      <xs:element name="ZIP" type="xs:string" />
18                    </xs:sequence>
19                  </xs:complexType>
20                </xs:element>
21              </xs:sequence>
22            </xs:complexType>
23          </xs:element>
24        </xs:sequence>
25      </xs:complexType>
26    </xs:element>
27 </xs:schema>');
28 begin
29 if (dbms_xdb.existsResource(:schemaPath)) then
30      dbms_xdb.deleteResource(:schemaPath);
31 end if;
32   res := dbms_xdb.createResource(:schemaPath,xmlSchema);
33 end;
34 /
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
SQL> call dbms_xmlschema.deleteSchema(:schemaURL,4);
Call completed.
SQL> BEGIN
2   DBMS_XMLSCHEMA.registerSchema(
3    SCHEMAURL => :SchemaURL,
4    SCHEMADOC => xdbURIType(:SchemaPath).getClob(),
5    LOCAL     => FALSE, -- local
6    GENTYPES => FALSE, -- generate object types
7    GENBEAN   => FALSE, -- no java beans
8    GENTABLES => FALSE, -- generate object tables
9    OPTIONS   => DBMS_XMLSCHEMA.REGISTER_BINARYXML,
10    OWNER     => USER
11   );
12 END;
13 /
PL/SQL procedure successfully completed.
SQL> commit;
Commit complete.
SQL> var schemaDoc varchar2(256)
SQL>
SQL> begin
2    :schemaDoc := '/public/schematest.xml';
3 end;
4 /
PL/SQL procedure successfully completed.
SQL>
SQL> ----------------------------------------------------------
SQL>
SQL> -- Create an XML Document in the repository
SQL>
SQL> ----------------------------------------------------------
SQL>
SQL> declare
2    res boolean;
3    xmlDoc xmlType := xmlType('<?xml version="1.0" encoding="utf-8"?>
4 <FORMINFO>
5     <SUBJECT>
6        <ADDR>
7           <STREET>123 Main St</STREET>
8           <CITY>Las Vegas</CITY>
9           <STATEPROV>NV</STATEPROV>
10           <ZIP>12345</ZIP>
11        </ADDR>
12     </SUBJECT>
13 </FORMINFO>');
14 begin
15 if (dbms_xdb.existsResource(:schemaDoc)) then
16      dbms_xdb.deleteResource(:schemaDoc);
17 end if;
18   res := dbms_xdb.createResource(:schemaDoc,xmlDoc);
19 end;
20 /
PL/SQL procedure successfully completed.
SQL>
SQL> ----------------------------------------------------------
SQL>
SQL> -- Ready to test
SQL>
SQL> ----------------------------------------------------------
SQL>
SQL> select * from tab;
no rows selected
SQL> CREATE TABLE BINARYTEST OF XMLType
2 XMLTYPE STORE AS BINARY XML
3 ALLOW ANYSCHEMA;
Table created.
SQL> set long 100000
SQL> select dbms_metadata.get_ddl('TABLE','BINARYTEST',user) from dual;
DBMS_METADATA.GET_DDL('TABLE','BINARYTEST',USER)
CREATE TABLE "OTN"."BINARYTEST" OF "SYS"."XMLTYPE"
OIDINDEX ( PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS" )
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS"
XMLTYPE COLUMN OBJECT_VALUE STORE AS BASICFILE BINARY XML (
TABLESPACE "USERS" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSION 10
NOCACHE LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT))
DISALLOW NONSCHEMA
ALLOW ANYSCHEMA
1 row selected.
SQL> SET SERVEROUTPUT ON
SQL> declare
2    x XMLType;
3    xschema XMLType;
4 begin
5    x := XMLType(xdbUriType(:SchemaDoc).getClob());
6    xschema := x.CreateSchemaBasedXml('http://localhost/schematest.xsd');
7    xschema.SchemaValidate();
8    DBMS_OUTPUT.PUT_LINE('Schema: ' || xschema.GetSchemaURL() || ' Validated: ' || xschema.IsSchemaValidated());
9
10    INSERT INTO BINARYTEST
11    VALUES (xschema);
12    commit;
13 end;
14 /
Schema: http://localhost/schematest.xsd Validated: 1
declare
ERROR at line 1:
ORA-44422: nonschema XML disallowed for this column
ORA-06512: at line 10
-- ORA-44421: cannot DISALLOW NONSCHEMA without a SCHEMA clause
-- Cause: If no SCHEMA clause (explicit schema or ANYSCHEMA) was specified, nonschema data cannot be disallowed.-
-- Action: Remove DISALLOW NONSCHEMA or add some SCHEMA clause.
SQL> drop table binarytest;
Table dropped.
SQL> CREATE TABLE BINARYTEST OF XMLType
2 XMLTYPE STORE AS BINARY XML
3 ALLOW NONSCHEMA;
Table created.
SQL> select dbms_metadata.get_ddl('TABLE','BINARYTEST',user) from dual;
DBMS_METADATA.GET_DDL('TABLE','BINARYTEST',USER)
CREATE TABLE "OTN"."BINARYTEST" OF "SYS"."XMLTYPE"
OIDINDEX ( PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS" )
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "USERS"
XMLTYPE COLUMN OBJECT_VALUE STORE AS BASICFILE BINARY XML (
TABLESPACE "USERS" ENABLE STORAGE IN ROW CHUNK 8192 PCTVERSION 10
NOCACHE LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT))
ALLOW NONSCHEMA
DISALLOW ANYSCHEMA
1 row selected.
SQL> declare
2    x XMLType;
3    xschema XMLType;
4 begin
5    x := XMLType(xdbUriType(:SchemaDoc).getClob());
6    xschema := x.CreateSchemaBasedXml('http://localhost/schematest.xsd');
7    xschema.SchemaValidate();
8    DBMS_OUTPUT.PUT_LINE('Schema: ' || xschema.GetSchemaURL() || ' Validated: ' || xschema.IsSchemaValidated());
9
10    INSERT INTO BINARYTEST
11    VALUES (xschema);
12    commit;
13 end;
14 /
Schema: http://localhost/schematest.xsd Validated: 1
PL/SQL procedure successfully completed.
SQL> select * from binarytest;
SYS_NC_ROWINFO$
<?xml version="1.0" encoding="UTF-8"?>
<FORMINFO>
<SUBJECT>
    <ADDR>
      <STREET>123 Main St</STREET>
      <CITY>Las Vegas</CITY>
      <STATEPROV>NV</STATEPROV>
      <ZIP>12345</ZIP>
    </ADDR>
</SUBJECT>
</FORMINFO>
1 row selected.
SQL> SET SERVEROUTPUT ON
SQL> declare
2    x XMLType;
3    xschema XMLType;
4 begin
5    x := XMLType(xdbUriType(:SchemaDoc).getClob());
6
7    dbms_output.put_line(x.getstringval());
8
9    xschema := x.CreateSchemaBasedXml('http://localhost/schematest.xsd');
10
11    dbms_output.put_line(xschema.getstringval());
12
13    xschema.SchemaValidate();
14    DBMS_OUTPUT.PUT_LINE('Schema: ' || xschema.GetSchemaURL() || ' Validated: ' || xschema.IsSchemaValidated());
15
16    INSERT INTO BINARYTEST
17    VALUES (xschema);
18    commit;
19 end;
20 /
<?xml version="1.0" encoding="UTF-8"?>
<FORMINFO>
<SUBJECT>
    <ADDR>
      <STREET>123 Main St</STREET>
      <CITY>Las
Vegas</CITY>
      <STATEPROV>NV</STATEPROV>
      <ZIP>12345</ZIP>
    </ADDR>
</SUBJECT>
</FORMINFO>
<?xml version="1.0" encoding="UTF-8"?>
<FORMINFO>
<SUBJECT>
    <ADDR>
      <STREET>123 Main St</STREET>
      <CITY>Las
Vegas</CITY>
      <STATEPROV>NV</STATEPROV>
      <ZIP>12345</ZIP>
    </ADDR>
</SUBJECT>
</FORMINFO>
Schema: http://localhost/schematest.xsd Validated: 1
PL/SQL procedure successfully completed.
SQL> create table ORtest of xmltype
2 xmlschema "http://localhost/schematest.xsd" element "FORMINFO"
3 ;
Table created.
SQL> declare
2    x XMLType;
3    xschema XMLType;
4 begin
5    x := XMLType(xdbUriType(:SchemaDoc).getClob());
6
7    dbms_output.put_line(x.getstringval());
8
9    xschema := x.CreateSchemaBasedXml('http://localhost/schematest.xsd');
10
11    dbms_output.put_line(xschema.getstringval());
12
13    xschema.SchemaValidate();
14    DBMS_OUTPUT.PUT_LINE('Schema: ' || xschema.GetSchemaURL() || ' Validated: ' || xschema.IsSchemaValid());
15
16    INSERT INTO ORTEST
17    VALUES (xschema);
18    commit;
19 end;
20 /
<?xml version="1.0" encoding="UTF-8"?>
<FORMINFO>
<SUBJECT>
    <ADDR>
      <STREET>123 Main St</STREET>
      <CITY>Las
Vegas</CITY>
      <STATEPROV>NV</STATEPROV>
      <ZIP>12345</ZIP>
    </ADDR>
</SUBJECT>
</FORMINFO>
<?xml version="1.0" encoding="UTF-8"?>
<FORMINFO>
<SUBJECT>
    <ADDR>
      <STREET>123 Main St</STREET>
      <CITY>Las
Vegas</CITY>
      <STATEPROV>NV</STATEPROV>
      <ZIP>12345</ZIP>
    </ADDR>
</SUBJECT>
</FORMINFO>
Schema: http://localhost/schematest.xsd Validated: 1
PL/SQL procedure successfully completed.
SQL> declare
2    x XMLType;
3    xschema XMLType;
4 begin
5    x := XMLType(xdbUriType(:SchemaDoc).getClob());
6
7    dbms_output.put_line(x.getstringval());
8
9    xschema := x.CreateSchemaBasedXml('http://localhost/schematest.xsd');
10
11    dbms_output.put_line(xschema.getstringval());
12
13    xschema.SchemaValidate();
14    DBMS_OUTPUT.PUT_LINE('Schema: ' || xschema.GetSchemaURL() || ' Validated: ' || xschema.IsSchemaValid());
15
16    INSERT INTO BIN_ONE_SCHEMA
17    VALUES (xschema);
18    commit;
19 end;
20 /
<?xml version="1.0" encoding="UTF-8"?>
<FORMINFO>
<SUBJECT>
    <ADDR>
      <STREET>123 Main St</STREET>
      <CITY>Las
Vegas</CITY>
      <STATEPROV>NV</STATEPROV>
      <ZIP>12345</ZIP>
    </ADDR>
</SUBJECT>
</FORMINFO>
<?xml version="1.0" encoding="UTF-8"?>
<FORMINFO>
<SUBJECT>
    <ADDR>
      <STREET>123 Main St</STREET>
      <CITY>Las
Vegas</CITY>
      <STATEPROV>NV</STATEPROV>
      <ZIP>12345</ZIP>
    </ADDR>
</SUBJECT>
</FORMINFO>
Schema: http://localhost/schematest.xsd Validated: 1
PL/SQL procedure successfully completed.
SQL> ----------------------------------------------------------
SQL>
SQL> -- Create an XML Document in the repository
SQL>
SQL> ----------------------------------------------------------
SQL>
SQL> declare
2    res boolean;
3    xmlDoc xmlType := xmlType('<?xml version="1.0" encoding="utf-8"?>
4 <FORMINFO>
5     <SUBJECT>
6        <ADDR>
7           <STREET>123 Main St</STREET>
8           <CITY>Las Vegas</CITY>
9           <STATEPROV>NV</STATEPROV>
10           <ZIP>12345</ZIP>
11           <ONE_TO_MANY>say what?</ONE_TO_MANY>
12        </ADDR>
13     </SUBJECT>
14 </FORMINFO>');
15 begin
16 if (dbms_xdb.existsResource(:schemaDoc)) then
17      dbms_xdb.deleteResource(:schemaDoc);
18 end if;
19   res := dbms_xdb.createResource(:schemaDoc,xmlDoc);
20 end;
21 /
PL/SQL procedure successfully completed.
SQL> declare
2    x XMLType;
3    xschema XMLType;
4 begin
5    x := XMLType(xdbUriType(:SchemaDoc).getClob());
6
7    dbms_output.put_line(x.getstringval());
8
9    xschema := x.CreateSchemaBasedXml('http://localhost/schematest.xsd');
10
11    dbms_output.put_line(xschema.getstringval());
12
13    xschema.SchemaValidate();
14    DBMS_OUTPUT.PUT_LINE('Schema: ' || xschema.GetSchemaURL() || ' Validated: ' || xschema.IsSchemaValid());
15
16    INSERT INTO BIN_ONE_SCHEMA
17    VALUES (xschema);
18    commit;
19 end;
20 /
<?xml version="1.0" encoding="UTF-8"?>
<FORMINFO>
<SUBJECT>
    <ADDR>
      <STREET>123 Main St</STREET>
      <CITY>Las
Vegas</CITY>
      <STATEPROV>NV</STATEPROV>
      <ZIP>12345</ZIP>
      <ONE_TO_MANY>say what?</ONE_TO_MANY>
    </ADDR>
</SUBJECT>
</FORMINFO>
<?xml version="1.0" encoding="UTF-8"?>
<FORMINFO>
<SUBJECT>
    <ADDR>
      <STREET>123 Main St</STREET>
      <CITY>Las
Vegas</CITY>
      <STATEPROV>NV</STATEPROV>
      <ZIP>12345</ZIP>
      <ONE_TO_MANY>say what?</ONE_TO_MANY>
    </ADDR>
</SUBJECT>
</FORMINFO>
declare
ERROR at line 1:
ORA-31154: invalid XML document
ORA-19202: Error occurred in XML processing
LSX-00213: only 0 occurrences of particle "ADDR", minimum is 1
ORA-06512: at "SYS.XMLTYPE", line 354
ORA-06512: at line 13
SQL>

Star Schemas with designer 6.0

How can I easily create star schemas for a Datawarehouse in Designer6? Where can I still find documentation for such release?
Mauro

Mauro,
You should be able to create start schemas - search in the online help for all references to data warehousing
and star schemas. There should be a few topics.
Regards,
Dominic
Designer Product Management
Oracle Corp

Design help - incorporating Budget information into star schema

I currently have a star schema.
At the fact level the data is broken down to be as grannular as possible, one row per order line Item with the line price being the main measure.
There is a DimDate
The DimProduct Dimension has ProductCode & Product Category ( I may break this up into two dimensions)
I have now been given a budget that contains Monthly and annual estimates of each test category and expected sales and sale prices, and asked to produce a report that:
On a monthly basis, shows if the actual sales match up with estimates in budget, and if not, lists if its due to insufficient quantity sold, discounted pricing or a combo of the two.
Im not sure how to implement this budget data. Should i:
Create a Budget Dimension that has a row for each month of the budget that contains the estimates?
Should this be imported directly into the fact table without a budget dimension?
Create a seperate new fact table that is a Periodic Snapshot . Would contain One row for each test category per month, with measures for expected and actual amounts.
Any advice on the best way of adding a budget to my model would be appreciated.
Thanks a mil

I was posting in the public forum as someone who may have tackled this before might be able to advise on a solution that may be better than what i come up with. I will try another public forum like sql server central. Thanks
I think what you can do is this
Populate budget info by reducing to day level granularity ie while putting in fact table make date as first day of the month ie datekey corresponding to start of the month from DimDate
This will you can use the existing DimDate itself for relating within the cube
While analysing because you analyze it at month level it will work fine
ie for actuals it will aggregate every transaction (sales) from day level to month and compare it with month level budget (single entry at start of the month)
so you'll get % attained and you can find reasons for that from other sales attributes like discounts etc
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Unable to run a star schema in HFM. Error message below.

We are currently unable to run an existing star schema in our HFM 9.3.3 application. This has never caused an issue in the past and is causing a disruption in our montly close process.
Any assitance would be greatly appreciated!
I've attempted to delete the Star Schema but still receive same error message.
Error message below:
Thank you,
Brian Riedel
==================================================================================================================
8/1/2012 1:34:24 PM : Status : Extracting Metadata
Metadata update has failed. : (-2147220903) (Attention: One or more processes are currently using the Star Schema specified by the DSN and Prefix. You must wait until all other processing is completed before attempting to create the specified Star Schema.)
Processing status change: (-2147220903)
Data processing failed. : (-2147220903) (Attention: One or more processes are currently using the Star Schema specified by the DSN and Prefix. You must wait until all other processing is completed before attempting to create the specified Star Schema.)
8/1/2012 1:34:24 PM : Status : Processing completed with errors
Extended Analytics export completed with errors for Application BSCPROD using Label PL. Error code is:

The message means another process has a lock on the EA tables, so you have to wait until that processis complete before proceeding. This could happen if you are trying to execute more than 1 concurrent EA exports.
--Chris

Regarding Extended star schema

Hi Friends,
In Extended star schema,master data will load separately ,which will connect through sid's to dimension table .
My question is.. This master data tables can be used other than this cube ?
Please tell me i am in confusion.
Thanks in advace,
Regards,
ramnaresh.

Hi
InfoCubes are made up of a number of InfoObjects. All InfoObjects (characteristics and key figures) are available independent of the InfoCube. Characteristics refer to master data with their attributes and text descriptions.
An InfoCube consists of several InfoObjects and is structured according to the star schema. This means there is a (large) fact table that contains the key figures for the InfoCube, as well as several (smaller) dimension tables which surround it. The characteristics of the InfoCube are stored in these dimensions.
An InfoCube fact table only contains key figures, in contrast to a DataStore object, whose data part can also contain characteristics. The characteristics of an InfoCube are stored in its dimensions.
The dimensions and the fact table are linked to one another using abstract identification numbers (dimension IDs) which are contained in the key part of the particular database table. As a result, the key figures of the InfoCube relate to the characteristics of the dimension. The characteristics determine the granularity (the degree of detail) at which the key figures are stored in the InfoCube.
Characteristics that logically belong together (for example, district and area belong to the regional dimension) are grouped together in a dimension. By adhering to this design criterion, dimensions are to a large extent independent of each other, and dimension tables remain small with regards to data volume. This is beneficial in terms of performance. This InfoCube structure is optimized for data analysis.
The fact table and dimension tables are both relational database tables.
Characteristics refer to the master data with their attributes and text descriptions. All InfoObjects (characteristics with their master data as well as key figures) are available for all InfoCubes, unlike dimensions, which represent the specific organizational form of characteristics in one InfoCube.
Integration
You can create aggregates to access data quickly. Here, the InfoCube data is stored redundantly and in an aggregated form.
You can either use an InfoCube directly as an InfoProvider for analysis and reporting, or use it with other InfoProviders as the basis of a MultiProvider or InfoSet.
See also:
Checking the Data Loaded in the InfoCube
If the above info is useful, please grant me points

APEX How do I create a Form based on a Database Table from other schema

My APEX schema is WISEXP. I have a database table that resides in WISDW schema on the same database. I want to create Tabular form based on this table.
I am not able to create a FORM based on the table from WISDW schema. I am able to create a FORM based on SQL though from this table in WISDW schema - but it does not do any action on Update/Insert rows.
Appropriate Synonyms and grants are created. Is there a limitation or am I missing something? Please advise.
thanks
Rupen

If Rupen is using 2.2 or 2.2.1, it is likely he is running into the bug described here: Re: Workspace to Schema Assignments
In that case, it may be a necessary and sufficient workaround to assign the foreign schema to the workspace.
Scott
Message was edited by:
sspadafo

Extended Star Schema doubt

Hi ALL,
Fact table --- Dimension table -
Sid Table -- master data values.
Fact table:
Contains Key Figures and Dimensional id's
Dimension table:
Contains Dim Id & SID
SID table:
SID and Master object ID ( eg: Customer ID)
Master Data Table:
contains Customer Attributes , Texts , Hierarchies for that Customer ID.
THis is the Extended Star Schema design.
MY DOUBT:
1)In Dimension table itself if we place that Customer ID(No SID table next) what will happen?
Fact table --> Dimension table --> Master data Table
2)Instead of that SID table we can directly place that CustomerID in Dimension table , so we can reduce one layer inbetween Dimendion table and Master data table.Is it correct or not?
Any one can clarify my doubt.
Regards,
Arun.M.D

SID means 'surrogate ID'. That is an system created id as you know. Main purpose is fastening the search.
Mostly, there exists a rule for Customer or Material ID's.
Like it should be CHAR 10 or CHAR 16.
This kind of alpha-numeric fields are harder to search when compared to integers. Moreover, your customer id can be 10 digits but, this does not mean you will have 1000000000 customers. This is the main reason that, an internal ID is produced. If you have 10000 customers, your SID will be at most 10000.
However, if your customer ID's are starting from 1 and growing up like integers, then your argument would be true. ( but still no way to skip SID creation and direct usage of characteristic ID in fact table)
Also, as mentioned by other friends, there exist the Line Item dimension property if you have only one characteristic in one dimension. That simply does skip the DIM ID creation step, and puts your SID into the Fact table. ( Since you have only one char in the dimension, no combination is possible)
Hope this helps.
Derya

Creating a Report based on different schema objects

Hi,
I have a situation in creating Reports for my database performance.
Let me explain my requirment.
There are 2 schemas in my database called X, Y
X owns all the performance related data. But Y has read access on X objects.
Now in APEX I have a developer DEV1 is mapped to database schema Y through WS1.
I cannot map DEV1 to database schema X for security reasons.
When I am trying to create a report as DEV1, it is allowing me to create based on the objects owned by schema Y.
However it is not allowing me to create a report based on objects owned by X though Y has SELECT privileges on X's objects.
Can any one help in this?
Regards
Balaji

This is the query which I am using to build a report
SELECT
rollup_timestamp "Date",
max(decode(target_guid,'199F0B201A3D71A63040BADFAA4F9E90',average,0)) host1,
max(decode(target_guid,'3FB1329F59339C07E11304B69DC4E594',average,0)) host2
FROM "sysman.MGMT$METRIC_DAILY"
WHERE
(target_guid='199F0B201A3D71A63040BADFAA4F9E90'
or
target_guid='3FB1329F59339C07E11304B69DC4E594')
AND
metric_name='Load'
AND
metric_column='memUsedPct'
AND
rollup_timestamp >= to_date('01-10-2009','dd-mm-yyyy') and rollup_timestamp <= sysdate
GROUP BY rollup_timestamp
ORDER BY "Date"
And for your previous question I couldn't even create a page.
Regards
Balaji
Edited by: user7290747 on 6/01/2010 16:17

How to create table for XML schema-based Interface form

Hi All,
With tcode SFP to crate a XML schema-based Interface form, how to create a defined table can be listed in "Data View"?
Just like APAP Dictonary- Based Interface form, that we can drag a defined table from data view to the panel.

Hi,
Just follow these steps:
1. Create interactive form UI element in your view.
2. Now provide Datasource and PDFSOURCE to it in form properties.
3. Now give a template name prefix with 'Z' or 'Y'.
4. Double click on it. It will prompt for interface name.
5. Provide interface name prefixed with 'Z' or 'Y'.
6. Click on Context button in the Pop up window and provide the node you have selected as DATASOURCE.
7. Click ok and it will open the form designer.
8. In this way you can create a XML Schema based Form.
9. Activate the interface and design the form providing layout type and other details.
Hope it will help.
Regards,
Vaibhav

Wat is the use of sid in extended star schema rather than linking masterdat

hi bw gurus,
wat is the use of sid in extended star schema rather than linking masterdata with dimention tables?
thanx in advace,
i will assign points,
srinivas

hi,
the sid are used instead of the data in order to avoid the redunduncy of data.
and reduce the datastorage size.
the data will be present in the sid table and the data is linked used the corerponding sid in the dimension.
regards

Extended Star Schema

Hi
Right now I'm trying to implement SAP HR Infotypes into SAP BW. I try to combine 10 infotypes (all Personal Administration) into one infocube. The confusing one is that when I see my dimension, there something strange (please see below)
Dimension 1 (from PA0016)
ZDATEFROM16
ZDATETO16
ZXXX (60 character, don't have master date attribute or text)
ZYYY (30 character, don't have master date attribute or text)
ZAAA(3 character, only master data text)
Dimension 2 (from PA0023)
ZDATEFROM23
ZDATETO23
ZCCC (60 character, don't have master date attribute or text)
ZBBB (30 character, don't have master date attribute or text)
ZDDD (20 character, don't have master date attribute or text)
If i see my dimension, it seems strange because most of them don't have master data (text,attr,hierarchy).
Is this violate the extended star schema design? Thank you.
Regards,
Satria

You can use characteristics such as ZXXX without master data (text, attr, hier) in extended star schema. It is not a violation. This means in business, for this characteristic you really don't need its text, attribute or hierarchy.
When perform data modeling for you HR cube, please do consider the design, can some characteristic be attribute of another one? Will you use hierarchy such organization level for some characteristic? characteristic with text, attribute or hierachy can provide more flexibility in reporting.

Run Extended Analtytics / Create Star Schema based on Process Management Level Status

Similar Messages

Maybe you are looking for