Dimension's Members Load into Planning

Hello,
this is my first post, as I'm new to Hyperion Planning. I hope you can help me on this question.
I have several flat files (txt format) produced by the source system. Each of them is a dimension. The record is the following:
Code; Description;Parent1;Parent2;Parent3
Now, back to Planning. I have successfully created an application through EPMA. Created Shared Dimensions. How can I import those flat files into Planning?
The Importing utility in EPMA accepts only ads flat files. I have tried creating an interface in ODI following the very good procedure in John Goodwin's blog, but I found out that it works only when the Application is created through the Classic Application Administration... I have tried recreating the application this way, but then the ODI procedure worked the first time. If I make a change in the Planning application, the reverse mechanism in the ODI model fails to reimport the new tables.
please help. I'm really stuck here.
Eliodeo

Hi Alp, I'll give it a try today.
John,
the error I get is the following:
org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 41, in ?
com.hyperion.odi.common.ODIHAppException: Failed to import the models into ODI repository.
     at com.hyperion.odi.common.ODIModelImporter.importModels(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java)
     at org.python.core.PyMethod.__call__(PyMethod.java)
     at org.python.core.PyObject.__call__(PyObject.java)
     at org.python.core.PyInstance.invoke(PyInstance.java)
     at org.python.pycode._pyx17.f$0(<string>:41)
     at org.python.pycode._pyx17.call_function(<string>)
     at org.python.core.PyTableCode.call(PyTableCode.java)
     at org.python.core.PyCode.call(PyCode.java)
     at org.python.core.Py.runCode(Py.java)
     at org.python.core.Py.exec(Py.java)
     at org.python.util.PythonInterpreter.exec(PythonInterpreter.java)
     at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:144)
     at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Violation of PRIMARY KEY constraint 'PK_REV_COL'. Cannot insert duplicate key in object 'dbo.SNP_REV_COL'.
     at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(Unknown Source)
     at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(Unknown Source)
     at com.hyperion.odi.common.ODIModelImporter.importTable(Unknown Source)
     ... 32 more
com.hyperion.odi.common.ODIHAppException: com.hyperion.odi.common.ODIHAppException: Failed to import the models into ODI repository.
     at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
     at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlC.treatTaskTrt(SnpSessTaskSqlC.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)
If I delete the application and recreate a new one (I used a different application name), the same ODI model works fine again (I have to change the application name of course).
Thanks
Eliodeo

Similar Messages

How can i add the dimensions and data loading into planning apllications?

Now please let me know how can i add the dimensions and data loading into planning apllication without manuallly?

you can use tools like ODI or DIM or HAL to load metadata & data into planning applications.
The data load can be done at the Essbase end using rules file. But metadata changes should flow from planning to essbase through any of above mentioned tools and also there are many other way to achieve the same.
- Krish

Do We Need to Validate Data Before Loading Into Planning?

We are debating between whether to load data from GL to Planning using ODI or FDM. If we need some form of validity check on the data, we will have to use FDM, otherwise I believe ODI is good enough.
My question is, for financials planning, what determines whether we need validity checks or not? How do we decide that?

FDM helps in validation for data load audit options but validation is as easy as doing a comparison to totals by GL accounts from source and planning. You should be able to use ODI, FDM or load rules to load data into Hyperion and complete validation outside using any of reporting options.

Incremental load into the Dimension table

Hi,
I have the problem in doing the incremental load of the dimension table.Before loading into the dimension table,i would like to check the data in the dimnesion table.
In my dimension table i have one not null surrogate key and the other null dimension tables.The not null surrogate key, i am populating with the Sequence Generator.
To do the incremental load i have done the following.
I made lookup into the dimension table and looked for a key.The key from the lookup table i have passed to the expression operator.In the expression operator i have created one field and hard coded one flag based on the key from the lookup table.I passed this flag to the filter operator and rest of the fields from the source.
By doing this i am not able to pass the new records to the dimension table.
Can you please help me.
I have another question also.
How do i update one not null key in the fact table.
Thanks
Vinay

Hi Mark,
Thanks for your help to solve my problem.I thought i share more information by giving the sql.
I am giving below the 2 sqls, i would like to achieve through OWB.
Both the following tasks need to be accomplished after loading the fact table.
task1:
UPDATE fact_table c
SET c.dimension_table_key =
(SELECT nvl(dimension_table.dimension_table_key,0)
FROM src_dimension_table t,
dimension_table dimension_table
WHERE c.ssn = t.ssn(+)
AND c.date_src_key = to_number(t.date_src(+), '99999999')
AND c.time_src_key = to_number(substr(t.time_src(+), 1, 4), '99999999')
AND c.wk_src = to_number(concat(t.wk_src_year(+), concat(t.wk_src_month(+), t.wk_src_day(+))), '99999999')
AND nvl(t.field1, 'Y') = nvl(dimension_table.field1, 'Y')
AND nvl(t.field2, 'Y') = nvl(dimension_table.field2, 'Y')
AND nvl(t.field3, 'Y') = nvl(dimension_table.field3, 'Y')
AND nvl(t.field4, 'Y') = nvl(dimension_table.field4, 'Y')
AND nvl(t.field5, 'Y') = nvl(dimension_table.field5, 'Y')
AND nvl(t.field6, 'Y') = nvl(dimension_table.field6, 'Y')
AND nvl(t.field7, 'Y') = nvl(dimension_table.field7, 'Y')
AND nvl(t.field8, 'Y') = nvl(dimension_table.field8, 'Y')
AND nvl(t.field9, 'Y') = nvl(dimension_table.field9, 'Y')
WHERE c.dimension_table_key = 0;
fact table in the above sql is fact_table
dimesion table in the above sql is dimension_table
source table for the dimension table is src_dimension_table
dimension_table_key is a not null key in the fact table
task2:
update fact_table cf
set cf.key_1 =
(select nvl(max(p.key_1),0) from dimension_table p
where p.field1 = cf.field1
and p.source='YY')
where cf.key_1 = 0;
fact table in the above sql is fact_table
dimesion table in the above sql is dimension_table
key_1 is a not null key in the fact table
Is it possible to achieve the above tasks through Oracle Warehouse builder(OWB).I created the mappings for loading the dimension table and fact table and they are working fine.But the above two queries i am not able to achieve through OWB.I would be thankful if you can help me out.
Thanks
Vinay

Sorting a join loading into Hyperion planning

Hi,
i have Producr master data (1000+ data). I've to load into planning but i'm not able to understand how to sort (as SQL "order by 1 asc") a join of two table
MASTER_PRODUCT, DESC_PROD.
any suggestion?
Thanks in advance
DecaXD

Hi,
One method is customize the KM.
If you right click "IKM SQL to Hyperion Planning" and select "Insert Option"
Name the option something like "ORDER_OPTION" and set it to text.
Now edit "IKM SQL to Hyperion Planning" and edit command "Load data into planning"
In there should be
sql= """select <%=odiRef.getPop("DISTINCT_ROWS") %> <%=odiRef.getColList("", "[EXPRESSION] [ALIAS_SEP] \u0022[COL_NAME]\u0022", ",", "", "INS and !TRG") %> from <%=odiRef.getFrom() %> where (1=1) <%=odiRef.getFilter() %> <%=odiRef.getJrnFilter() %> <%=odiRef.getJoin() %> <%=odiRef.getGrpBy() %> <%=odiRef.getHaving() %>"""
Add to the end - <%=odiRef.getOption("ORDER_OPTION")%>
So it becomes
sql= """select <%=odiRef.getPop("DISTINCT_ROWS") %> <%=odiRef.getColList("", "[EXPRESSION] [ALIAS_SEP] \u0022[COL_NAME]\u0022", ",", "", "INS and !TRG") %> from <%=odiRef.getFrom() %> where (1=1) <%=odiRef.getFilter() %> <%=odiRef.getJrnFilter() %> <%=odiRef.getJoin() %> <%=odiRef.getGrpBy() %> <%=odiRef.getHaving() %><%=odiRef.getOption("ORDER_OPTION")%>"""
Now in your interface and the flow section for the IKM you should have an Option "ORDER_OPTION"
put in something like
ORDER BY 1 ASC
Give that a go.
Cheers
John
http://john-goodwin.blogspot.com/

Load dimensions and members in Planning application via outline load

it is a classic planning application, after I load dimensions and members into classic Planning application, I can't see new members I added in csv file.
How could I confirm whether it was successfully loaded.
This is the log. Please refer to it.
Successfully logged into "予算応用" application, Release 11.121, Adapter Interface Version 5, Workforce supported and enabled, CapEx supported and enabled, CSS Version 3
"Account" dimension properties and information:
Account, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Account Type, Time Balance, Skip Value, Exchange Rate Type, Variance Reporting, Source Plan Type, Plan Type (PL), Aggregation (PL), Plan Type (BS), Aggregation (BS), Plan Type (Plan3), Aggregation (Plan3), Plan Type (Wrkforce), Aggregation (Wrkforce), Plan Type (Capex), Aggregation (Capex)
UDA's bound to "Account" dimension: HSP_NOLINK
"Period" dimension properties and information:
Period, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Type, Start Period, End Period, Aggregation (PL), Aggregation (BS), Aggregation (Plan3), Aggregation (Wrkforce), Aggregation (Capex)
No UDA's defined on "Period"
"Year" dimension properties and information:
Year, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation
No UDA's defined on "Year"
"Scenario" dimension properties and information:
Scenario, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Start Year, Start Period, End Year, End Period, Exchange Table, Include BegBal, Process Management Enabled, Aggregation (PL), Aggregation (BS), Aggregation (Plan3), Aggregation (Wrkforce), Aggregation (Capex)
UDA's bound to "Scenario" dimension: ACTUAL
"Version" dimension properties and information:
Version, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Version Type, Process Management Enabled, Aggregation (PL), Aggregation (BS), Aggregation (Plan3), Aggregation (Wrkforce), Aggregation (Capex)
No UDA's defined on "Version"
"Currency" dimension properties and information:
Currency, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Symbol, Scale, Triangulation Currency, Reporting Currency, Thousands Separator, Decimal Separator, Negative Style, Negative Color
No UDA's defined on "Currency"
"Entity" dimension properties and information:
Entity, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Base Currency, Plan Type (PL), Aggregation (PL), Plan Type (BS), Aggregation (BS), Plan Type (Plan3), Aggregation (Plan3), Plan Type (Wrkforce), Aggregation (Wrkforce), Plan Type (Capex), Aggregation (Capex), NumericAttrib
No UDA's defined on "Entity"
"NumericAttrib" attribute dimension (on base dimension "Entity"). NO attributes defined on the "NumericAttrib" dimension.
NumericAttrib, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Operation
"Employee" dimension properties and information:
Employee, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Aggregation (Wrkforce)
No UDA's defined on "Employee"
"Line Item" dimension properties and information:
Line Item, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Aggregation (Capex)
No UDA's defined on "Line Item"
"Asset Class" dimension properties and information:
Asset Class, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Operation, Aggregation (Capex)
No UDA's defined on "Asset Class"
Exchange Rates properties:
Table, Description, To Currency, From Currency, Operation, Method, Historical, Beg Balance, Year, Period, Average, Ending
UDA properties:
Dimension, UDA, Operation
Smartlist properties:
SmartList Name, Operation, Label, Display Order, Missing Label, Use Form Missing Label, Entry ID, Entry Name, Entry Label
No Planning Unit Hierarchies are defined in this application.
Translation input file fields:
Value, Driver Member, Point-of-View, Data Load Cube Name
[Thu Oct 27 18:16:18 JST 2011]Successfully located and opened input file "C:\TEMP\PLNentityバージョンのエクスポート.csv".
[Thu Oct 27 18:16:18 JST 2011]Input file being read with UTF-8 encoding.
[Thu Oct 27 18:16:18 JST 2011]Detected a UTF-8 BOM marker in input file "C:\TEMP\PLNentityバージョンのエクスポート.csv".
[Thu Oct 27 18:16:18 JST 2011]Header record fields: Entity, Parent, Alias: Default, Alias: FromDepartment, Alias: ToDepartment, Valid For Consolidations, Data Storage, Two Pass Calculation, Description, Formula, UDA, Smart List, Data Type, Base Currency, Plan Type (PL), Aggregation (PL), Plan Type (BS), Aggregation (BS), Plan Type (Plan3), Aggregation (Plan3), Plan Type (Wrkforce), Aggregation (Wrkforce), Plan Type (Capex), Aggregation (Capex)
[Thu Oct 27 18:16:18 JST 2011]Located and using "Entity" dimension for loading data in "予算応用" application.
[Thu Oct 27 18:16:18 JST 2011]Load dimension "Entity" has been unlocked successfully.
[Thu Oct 27 18:16:18 JST 2011]A cube refresh operation will not be performed.
[Thu Oct 27 18:16:18 JST 2011]Create security filters operation will not be performed.
[Thu Oct 27 18:16:18 JST 2011]Examine the Essbase log files for status if Essbase data was loaded.
[Thu Oct 27 18:16:18 JST 2011]Planning Outline load process finished (with no data load as specified (/N)). 9 data records were read, 9 data records were processed, 9 were accepted, 0 were rejected.

Thank you for your reply.
With your help, I can verify it easier rather than creating dataform to verify it.
I have resolved the question now, the root cause is I had used the wrong parameter, shouldn't add '/N' in the command. for /N is a dry run to check whether there are error in CSV file, it won't perform metadata load.
If no error occured, run the command without /N, then the metadata load will be performed.
I refer to this artical,
http://john-goodwin.blogspot.com/2008/08/time-to-look-in-bin.html
Best regards,
Samantha
Edited by: Samantha on 2011-10-31 下午4:39

Anyone experience this error : Error in LKM COMM Load Members into Planning - Load Members to Classic Planning

When running Metadata load in ERPi it fail on step ‘Export members to planning application for dimension organization’ see error.
Error in LKM COMM Load Members into Planning - Load Members to Classic Planning
Traceback (most recent call last):
File "", line 381, in
ODIPlanningException: com.hyperion.odi.planning.ODIPlanningException: Could not connect the Planning instance on host [vmhodctau006.oracleoutsourcing.com], port [11333], check if connect information is correct.

Check if the Planning service is definitely running on Planning server. Check if port 11333 is open (using telnet) and make sure host is reachable from the ERPi system.
Regards,
Santy

How to load dimensions and members in Planning application

Hello Everyone,
I am trying to load dimensions and members in planning. I know that loading dimension is not recommended through Essbase but I wanted to give it a try. I tried to load the dimensions through rule files but it threw an error that the "members do not exist in database." Is that an indication that data cant be loaded at all in planning application through Essbase.
Thanks is advance for all the replies !!

If this is a planning application, you need to load metadata/dimension to planning first. You cannot load metadata directly to Essbase as it will be overwritten when you refresh planning.
You should read documentation to understanding how planning works. Planning is an interface which sits on top on Essbase. However, Planning metadata is stored in database tables and it is synch'd with Essbase through Hyperion Planning refresh.
In order to load metadata to planning, I would suggest to log on to planning and try to build dimensions manually first to know how planning interacts with Essbase. You could load metadata into planning through:
1. Manually
2. ODI: You will need to reverse planning application and then use it to load metadata
3. Outline load utility on planning server.
Remember, all Planning maintenance is done through planning interface and not through Essbase.

In my planning application.I have 100 members in account dimensions.Those members are used in 100 forms.suddenly my bussiness was changed.so i want replace those 100 members into new name of 100 memebers.but how i can chnage in 100 forms.how to handle

In my planning application.I have 100 members in account dimensions.Those members are used in 100 forms.suddenly my business was changed.so i want replace those 100 members into new name of 100 members.but how i can change those 100 members in 100 forms.how to handle this?

Hi joshi and jharvey,
Thanks for you are reply.I am new for this lcm.Can you explain detail.about above problem.I mean in share service i didn't find any export option.I had seen only migration.or share any blog for detail about lcm.

How will u know that a dimension can b a lineitem Dim b4 loading into Cube

Hi, Im new to this. My qury is how will u know that a dim will b a LineItem dimension bfore loading in to cube , are there anystandard to b followed. Ca u give me some realtime detailed scenarious.

Hi,
     When compared to a fact table, dimensions ideally have a small cardinality. However, there is an exception to this rule. For example, there are InfoCubes in which a characteristic Document is used, in which case almost every entry in the fact table is assigned to a different Document. This means that the dimension (or the associated dimension table) has almost as many entries as the fact table itself. We refer here to a degenerated dimension.
Generally, relational and multi-dimensional database systems have problems to efficiently process such dimensions. You can use the indicators line item and high cardinality to execute the following optimizations:
      1.      Line item: This means the dimension contains precisely one characteristic. This means that the system does not create a dimension table. Instead, the SID table of the characteristic takes on the role of dimension table. Removing the dimension table has the following advantages:
       When loading transaction data, no IDs are generated for the entries in the dimension table. This number range operation can compromise performance precisely in the case where a degenerated dimension is involved.
      A table- having a very large cardinality- is removed from the star schema. as a result, the SQL-based queries are simpler. In many cases, the database optimizer can choose better execution plans.
Nevertheless, it also has a disadvantage: A dimension marked as a line item cannot subsequently include additional characteristics. This is only possible with normal dimensions.
We recommend that you use DataStore objects, where possible, instead of InfoCubes for line items. See Creating DataStore Objects.
       2.      High cardinality: This means that the dimension is to have a large number of instances (that is, a high cardinality). This information is used to carry out optimizations on a physical level in depending on the database platform. Different index types are used than is normally the case. A general rule is that a dimension has a high cardinality when the number of dimension entries is at least 20% of the fact table entries. If you are unsure, do not select a dimension having high cardinality.
Activities
When creating dimensions in the InfoCube maintenance, flag the relevant dimension as a Line Item/ having High Cardinality.
Define lots of small dimensions rather than a few large dimensions.
     The size of the dimension tables should account for less than 10% of the fact table.
     If the size of the dimension table amounts to more than 10% of the fact table, mark the dimension as a line item dimension.
To attain good performance for a query on non-cumulative InfoCubes, you should take note of the following:
Compression:
Compress all requests in the non-cumulative InfoCube, or at least most of them.
The performance of a query based on a non-cumulative InfoCube depends heavily on how the InfoCube is compressed. If you want to improve the performance of a query of this type, first check in so far as this is possible - whether the data in the InfoCube should be compressed. You should always compress data when you are sure that the request affected will not need to be deleted from the InfoCube.
Validity Table
Use as few validity-determining characteristics as possible.
The number and cardinality of the validity-determining characteristics heavily influences performance. Therefore, you should only define characteristics as validity-determining characteristics when it is really necessary.
Time Restrictions in the Query
As far as possible, restrict queries based on non-cumulative InfoCubes to time characteristics.
The stricter the time-based restriction, the faster the query is generally executed, as the non-cumulative is reconstructed if the number of times is smaller.
Time Drilldown in the Query
If you no longer need the average, split a query on a non-cumulative InfoCube (which contains both key figures with LAST aggregation and key figures with AVERAGE aggregation) into two queries.
With non-cumulative key figures with the exception aggregation LAST, the time characteristic included in the drilldown makes a difference to performance. If, for example, both Calendar Day and Calendar Month are included in the InfoCube, drilldown by month is faster than drilldown by day, because the number of times for which a non-cumulative has to be calculated is smaller.
For the other types of exception aggregation (average, average weighted with factory calendar, minimum and maximum), this rule is not valid as in these cases, the data is always calculated on the level of the most detailed time characteristic first before exception aggregation is performed.
Totals Rows
Hide the totals row in the query when not required.
Depending on the type of aggregation being used, the calculation of totals rows can be very time-consuming.
When selecting MDC dimensions, proceed as follows:
        Select dimensions for which you often use restrictions in queries.
        Select dimensions with a low cardinality.
The MDC dimension is created in the column with the dimension keys (DIMID). The number of different combinations in the dimension characteristics determines the cardinality. Therefore, select a dimension with either one, or few characteristics and with only a few different characteristic values.
Line item dimensions are not usually suitable, as they normally have a characteristic with a high cardinality.
If you specifically want to create an MDC dimension for a characteristic with a low cardinality, you can define this characteristic as a line item dimension in the InfoCube. This differs from the norm that line item dimensions contain characteristics with a very high cardinality. However, this has the advantage for multidimensional clustering that the fact table contains the SID values of the characteristic, in place of the dimension keys, and the database query can be restricted to these SID values.
        You cannot select more than three dimensions, including the time dimension.
        Assign sequence numbers, using the following criteria:
        Sort the dimensions according to how often they occur in queries (assign the lowest sequence number to the InfoObject that occurs most often in queries).
        Sort the dimensions according to selectivity (assign the lowest sequence number to the dimension with the most different data records).
Note: At least one block is created for each value combination in the MDC dimension. This memory area is reserved independently of the number of data records that have the same value combination in the MDC dimension. If there is not a sufficient number of data records with the same value combinations to completely fill a block, the free memory remains unused. This is so that data records with a different value combination in the MDC dimension cannot be written to the block.
If for each combination that exists in the InfoCube, only a few data records exist in the selected MDC dimension, most blocks have unused free memory. This means that the fact tables use an unnecessarily large amount of memory space. Performance of table queries also deteriorates, as many pages with not much information must be read.
Example
The size of a block depends on the PAGESIZE and the EXTENTSIZE of the tablespace. The standard PAGESIZE of the fact-table tablespace with the assigned data class DFACT is 16K. Up to Release SAP BW 3.5, the default EXTENTSIZE value was 16. As of Release SAP NetWeaver 2004s the new default EXTENTSIZE value is 2.
With an EXTENTSIZE of 2 and a PAGESIZE of 16K the memory area is calculated as 2 x 16K = 32K, this is reserved for each block.
The width of a data record depends on the number of dimensions and the number of key figures in the InfoCube. A dimension key field uses 4 bytes and a decimal key figure uses 9 bytes. If, for example an InfoCube has 3 standard dimensions, 7 customer dimensions and 30 decimal key figures, a data record needs 10 x 4 bytes + 30 x 9 bytes = 310 bytes. In a 32K block, 32768 bytes / 310 bytes could write 105 data records.
If the time characteristic calendar month (0CALMONTH) and a customer dimension are selected as the MDC dimension for this InfoCube, at least 100 data records should exist for each InfoPackage, for each calendar month and for each dimension key of the customer dimension. This allows optimal use of the memory space in the F fact table. In the E fact table, this is valid for each calendar month and each dimension key of the customer dimension,dimension contains a characteristic whose value already uniquely determines the values of all other characteristics from a business-orientated viewpoint, then the dimension is named after this characteristic.
The customer dimension could, for example, be made up of the customer number, the customer group and the levels of the customer hierarchy.
The sales dimension could contain the characteristics sales person, sales group and sales office.
The time dimension could be given using the characteristics day (in the form YYYYMMDD), week (in the form YYYY.WW), month (in the form YYYY.MM), year (in the form YYYY) and period (in the form YYYY.PPP).
Use
When defining an InfoCube, characteristics for dimensions are grouped together to enable them to be stored in a star schema table (dimension table). The aforementioned business-orientated grouping can be the basis for this. With the aid of a simple foreign key dependency, dimensions are linked to one of the key fields of the fact table.
When you create an InfoCube, the dimensions data package, time and unit are already defined by default. The data package dimension contains technical characteristics. Time characteristics and units are automatically assigned to the corresponding dimensions. When you activate the InfoCube, only those dimensions that contain InfoObjects are activated.
From a technical viewpoint several characteristic values are mapped to an abstract dimension key (DIM ID), to which the values in the fact table refer. The characteristics chosen for an InfoCube are divided up among InfoCube-specific dimensions when creating the InfoCube.
Also refer to the following for specific cases arising when defining dimensions:
Line Item and High Cardinality
The methods for setting and getting data from a named range use the separation between the description of the range and the data itself. Note that the sequence must be observed both in the range description (structure soi_range_list ) and in the data (structure soi_generic_table ). This means that you must list all data from the first range before you can insert data into the second range.
Structure soi_range_list
Field
Type
Description
name
C
Name of the range
rows
C
Number of rows
columns
C
Number of columns
code
C
Function in the range:
SPREADSHEET->SPREADSHEET_CLEAR : Deletes range
SPREADSHEET->SPREADSHEET_COLUMNSHIDE : Hides columns
SPREADSHEET->SPREADSHEET_ROWSHIDE : Hides rows
SPREADSHEET->SPREADSHEET_PROTECT : Range is protected
SPREADSHEET->SPREADSHEET_UNPROTECT : Range is not protected
SPREADSHEET->SPREADSHEET_COLUMNSSHOW : Columns are displayed.
SPREADSHEET->SPREADSHEET_ROWSSHOW : Rows are displayed.
SPREADSHEET->SPREADSHEET_INSERTALL : The entire table is inserted, regardless of the size of the area
SPREADSHEET->SPREADSHEET_NEWRANGE : Creates a new range
The name identifies the range in the worksheet. This is, in effect, the key with which you always access the range. The size of the range is always given in columns and rows.
Some functions allow you to access a specific area in a worksheet. You can see from the table which functions are implemented.
Description of Data Type soi_generic_table
In this table, you can save data from the range and use the Data Provider to transfer it to or retrieve it from the frontend. The data is transferred directly as a string with no type information.
Structure soi_generic_table
Field
Type
Description
row
C(4)
Row
column
C(4)
Column
value
C(256)
Value
The sequence of the data must correspond to the sequence of the range description, for example, range1 before range2 . The data table must then contain the data for the ranges in the sequence range1 range2 .
Description of Data Type soi_format_table
Use this table to specify the format of a range. The format consists of various attributes, all of which can be set in a single line. Each variable attribute corresponds to a column of the structure.
To create a work area for this table, use the structure soi_format_item as a reference.
The entry "-1" always indicates that the existing attribute value for the range should not be changed.
Structure soi_format_table
Field
Type
Description
name
C(256)
Name of the range
front
I
Font color (see color palette)
back
I
Background color (see color palette)
font
C(256)
Name of the font family. The following values are permitted:
'Arial'
'Courier New'
'Times New Roman'
size
I
Font size
'-1' : Unchanged
bold
I
'1' : Bold
'0' : Normal
'-1' : Unchanged
italic
I
'1' : Italic
'0' : Normal
'-1' : Unchanged
align
I
Alignment:
'-1' : Unchanged
'0' : Right-justified
'1' : Centered
'2' : Left-justified
frametype
I
Control byte for setting the frame
'-1' : Unchanged
framecolor
I
Frame color (see color palette)
'-1' : Unchanged
currency
C(3)
ISO standard currency code
number
I
Specifies the format of a cell in a range.
1: Display as a simple number
2: Scientific display
3: Display as a percentage
The control byte type contains the following bits. If a bit is set, its corresponding line is drawn. You can set the thickness of the line to one of four levels using bits 6 and 7.
Bit
Description
0
Sets the left margin
1
Sets the top margin
2
Sets the bottom margin
3
Sets the right margin
4
Horizontal line
5
Sets the left margin
6
Thickness
7
Thickness
Description of Data Type soi_full_range_table
Each line of a table with the type soi_full_range_table specifies the full definition of a range. The individual lines have the data type soi_full_range_item .
Structure soi_full_range_table
Field
Type
Description
name
C(128)
Name of the range
top
I
Top row of the range
left
I
Leftmost column of the range
rows
I
Number of rows in the range
columns
I
Number of columns in the range
sheets
C(128)
Worksheet on which the range is defined
Description of Data Type soi_cell_table
Each line of a table with the type soi_cell_table specifies the attributes of a range of cells. However, no range name is used. Instead, the cell area is defined by its starting position and the number of rows and columns it contains.The individual lines have the data type soi_cell_item .
Structure soi_cell_table
Field
Type
Description
top
I
Top row of the range
left
I
Leftmost column of the range
rows
I
Number of rows in the range
columns
I
Number of columns in the range
front
I
Font color (see color palette)
back
I
Background color (see color palette)
font
C(256)
Font. The following are permitted:
Arial
Courier New
Times Roman
size
I
Font size
Use -1 if the font size is to remain unchanged.
bold
I
'1' : Bold
'0' : Normal
'-1' : Unchanged
italic
I
'1' : Italic
'0' : Normal
'-1' : Unchanged
align
I
Alignment:
'-1' : Unchanged
'0' : Right-justified
'1' : Centered
'2' : Left-justified
frametype
I
Control byte for setting the frame
'-1' : Unchanged
framecolor
I
Frame color (see color palette)
'-1' : Unchanged
currency
C(3)
ISO standard currency code
number
I
Specifies the format of a cell in a range.
1: Display as a simple number
2: Scientific display
3: Display as a percentage
decimals
I
Number of decimal places
input
I
'0' : Input off
'1' : Input on
Description of Data Type soi_dimension_table
You can use an internal table with this type to identify a range by specifying the coordinates of its top left-hand corner, its length, and its width. The lines of soi_dimension_table have the line type soi_dimension_item .
Structure soi_dimension_item
Field
Type
Decription
top
I
Topmost row of the range
left
I
Leftmost column of the range
rows
I
Number of rows
columns
I
Number of columns
Term
Definition
Board
A tabbed area in the workspace used to manipulate the model and its elements: Design board, Layout board and Source board.
Characteristic
A type of InfoObject in SAP BI systems that provides a classification such as company code, product, customer group, fiscal year, period, or region. Related to the OLAP-standard term dimension.
Component
A reusable model element, such as a UI component or a data service.
Cube
A set of data organized as a multidimensional structure defined according to dimensions and measures.
Related SAP BI terms include InfoCube and query.
Data binding
A connection between two UI components (or between a web service and a UI component) that channels identical data from the output port of one UI component to the input port of the other UI component.
Data flow
The means by which data is channeled between a data service and connected UI components, or between two UI components whose connection was changed from Data binding to Data flow.
Data mapping
Connection between two model elements, describing, for example, the data that is input to an element or the fields that are output from another element.
Data service
Any function call, business object or query imported into the model. At runtime, the data service is called and returns results.
Data store
A central data container where data of a model can be temporarily stored for future use.
Dimension
In OLAP-standard systems:
A collection of similar data which, together with other such collections, forms the structure of a cube. Typical dimensions include time, product, and geography. Each dimension may be organized into a basic parent-child hierarchy or, if supported by the data source, a hierarchy of levels. For example, a geography dimension might include levels for continent, country, state, and city.
The related term in SAP BI systems is characteristic.
In SAP BI systems:
A grouping of those evaluation groups (characteristics) that belong together under a common superordinate term.
With the definition of an InfoCube, characteristics are grouped together into dimensions in order to store them in a star schema table (dimension table).
Element
A general term indicating any item used to create a model, including: components, connectors and operators.
Enterprise service
A Web service defined to perform functions of an SAP system. Web services are published to and stored within a repository.
Field
An element of a table that contains a single piece of data. Fields are organized into rows, which contain all the data relevant for one specific entry in the table. In some databases, field is a synonym for column.
Filter
A set of criteria that restricts the set of records returned as the result of a query. With filters, you define which subset of data appears in the result set.
Hierarchy
A logical tree structure that organizes the members of a dimension into a parent-child relationship. If supported by the data source, the hierarchy consists of levels, where the top level is an aggregate of all members and each subsequent level has zero or more child members.
InfoArea
An element for grouping meta-objects in the Business Information Warehouse. Each InfoProvider is assigned to an InfoArea. The resulting hierarchy is displayed in the Administrator Workbench.
InfoCube
An SAP BI system that consists of a quantity of relational tables created according to the star schema: a large fact table in the center, with several dimension tables surrounding it. It provides a self-contained dataset which can be used for analysis and reporting.
Similar to the OLAP-standard term cube.
InfoObject
A business evaluation object (for example, customer or quantity) in SAP BI systems. Types of InfoObjects include characteristics, key figures, units, time characteristics, and technical characteristics (such as request numbers).
JDBC
Java Database Connectivity, which provides an API that lets you access relational databases using the Java programming language. This enables connectivity to a wide range of SQL databases, and also provides access to tabular data sources such as spreadsheets or flat files. The BI JDBC Connector accesses data from JDBC-compliant systems.
Join
A relationship between two tables that produces a result set that combines their contents. You create a join by indicating how selected fields in one table are related to selected fields in the other table.
Key figure
A value or quantity in SAP BI systems. Related to the OLAP-standard term measure. You may also define calculated key figures, which are derived using a formula.
Layer
A collection of UI elements that are all visible at the same time at runtime.
Level
A set of nodes (members) in a tree hierarchy in supporting data sources that are at the same distance from the root of the tree. For example, in a geography hierarchy, the top level might be all places, the second level might be continents, the third level might be countries, and the fourth level might be cities.
MDX
Multidimensional Expressions, a query language used to retrieve and manipulate multidimensional data.
Measure
One category of values usually numeric used to define a cube. These values are derived from one or more columns in the cube's fact table and are the basis for aggregation and analysis.
Related SAP BI terms include key figure and structure element.
Member
An element of a dimension that represents one or more occurrences of data. A member can be unique (it occurs only once) or non-unique (it may occur more than once in its dimension). For example, in a geography dimension that includes cities in the US, the member Portland could be non-unique, since there is a city called Portland in the state of Oregon and in the state of Maine.
In SAP BI systems, members are referred to as instances of characteristics.
Model
An object created in Storyboard. Models may contain packages, pages, iViews and any other model elements.
Multidimensional data
Data in dimensional models suitable for business analytics. In this documentation, we use the term multidimensional data synonymously with OLAP data.
Navigation line
A connection that provides event annotation, running between model layers. The source element raises the event that can be handled by the connected element. By default, a navigation line is curved.
ODBO
OLE DB for OLAP Microsofts set of objects and interfaces that extend the ability of OLE DB to provide access to multidimensional data sources on the Windows platform. Providers of OLAP data can implement the interfaces described with OLE DB for OLAP to allow all OLAP clients to access their data. The BI ODBO Connector accesses data from ODBO-compliant systems.
OLAP
Online analytical processing a system of organizing data in a multidimensional model that is suitable for decision support. SAP BI systems are OLAP systems.
Operation
A functionality provided by a Web service.
Operator
A mechanism used to manipulate data returned from the data service before it is displayed in the iView.
Package
A high-level container; it can contain any number of pages, iViews or other packages.
Port
A defined point of interface into and out of a component.
Query
In SAP BI systems, a collection of selected characteristics and key figures (InfoObjects) used together to analyze the data of an InfoProvider. A query always refers exactly to one InfoProvider, whereas you can define as many queries as you like for each InfoProvider.
Query view
In SAP BI systems, a view of a query after navigation, saved in an InfoCube. You can use this saved query view as a basis for data analysis and reporting.
Relational database
A repository for typically large amounts of information, structured in accordance with the relational model, in tables with columns. A relational database is created and administered by a relational database management system (RDBMS).
Row
A set of fields within a table that contains the data for one specific entry in the table. Each row in a given table has the same structure, predefined for a particular table. In some databases, row is a synonym for record.
SAP Query
A component that allows you to create custom reports without any ABAP programming knowledge. The BI SAP Query Connector uses SAP Query to access data from such SAP operational applications.
Storyboard
The Visual Composer client from which you design models.
Table
A set of rows, also known as a relation. The table is the central object of the relational model.
Task panel
A work area of the Visual Composer Storyboard desktop that displays a specific set of tools for building a model.
Toolbar
The horizontal row of buttons under the main menu (main toolbar) or the vertical row of buttons in the task panel (task-panel toolbar).
Toolbox
A set of board-specific tools that assist in performing tasks in the Visual Composer workspace.
Value help
The offering, typically in a pop-up dialog box, of possible valid values for an input field. Also known as input help, selection help, or F4 help.
Web service
An interface between two or more software applications that is implemented with the industry standards SOAP, WSDL and UDDI.
Workspace
The main grid area of Visual Composer that displays the model as it is built and modified. The workspace consists of boards.
XMLA
XML for Analysis, an XML-messaging-based protocol specified by Microsoft for exchanging analytical data between client applications and servers (for example, OLAP providers) using HTTP and SOAP as a service on the Web. The BI XMLA Connector accesses data from XMLA-compliant systems.
Clustering allows you to save sorted data records in the fact table of an InfoCube. Data records with the same dimension keys are saved in the same extents (related database storage unit). This means that same data records are not spread across a large memory area and thereby reduces the number of extents that the system has to read when it accesses tables. This greatly accelerates read, write and delete access to the fact table.
Prerequisites
Currently the function is only supported by the database platform DB2 for Linux, UNIX, and Windows. You can use partitioning to improve the performance of other databases. For more information, see Partitioning.
Features
Two types of clustering are available: Index clustering and multidimensional clustering (MDC).
Index Clustering
Index clustering organizes the data records of a fact table according to the sort sequence of an index. Organization is linear and corresponds to the values of the index field.
If a data record cannot be inserted in accordance with the sort sequence because the relevant extent is already full, the data record is inserted into an empty extent at the end of the table. For this reason, the system cannot guarantee that the sort sequence is always correct, particularly if you perform many insert and delete operations. Reorganizing the table restores the sort sequence and frees up memory space that is no longer required.
The clustering index of an F fact table is, by default, the secondary index in the time dimension. The clustering index of an E fact table is, by default, the acting primary index (P index).
As of release SAP BW 2.0, index clustering is standard for all InfoCubes and aggregates.
Multidimensional Clustering (MDC)
Multidimensional clustering organizes the data records of a fact table in accordance with one or more fields that you define freely. The selected fields are also marked as MDC dimensions. Only data records that have the same values in the MDC dimensions are saved in an extent. In the context of MDC, an extent is called a block. The system can always guarantee that the sort sequence is correct. Reorganizing the table is not necessary, even with many insert and delete operations.
Block indexes from within the database, instead of the default secondary indexes, are created for the selected fields. Block indexes link to extents instead of data record numbers and are therefore much smaller. They save memory space and the system can search through them more quickly. This accelerates table requests that are restricted to these fields.
You can select the key fields of the time dimension or any customer-defined dimensions of an InfoCube as an MDC dimension. You cannot select the key field of the package dimension; it is automatically added to the MDC dimensions in the F fact table.
You can also select a time characteristic instead of the time dimension. In this case, the fact table has an extra field. This contains the SID values of the time characteristic. Currently only the time characteristics Calendar Month (0CALMONTH) and Fiscal Year/Period (0FISCPER) are supported. The time characteristic must be contained in the InfoCube. If you select the Fiscal Year/Period (0FISCPER) characteristic, a constant must be set for the Fiscal Year Variant (0FISCVARNT) characteristic.
Clustering is applied to all the aggregates of the InfoCube. If an aggregate does not contain an MDC dimension of the InfoCube, or if all the InfoObjects of an MDC dimension are created as line item dimensions in the aggregate, the aggregates are clustered using the remaining MDC dimensions. Index clustering is used for the aggregate if the aggregate does not contain any MDC dimensions of the InfoCube, or if it only contains MDC dimensions.
Multidimensional clustering was introduced in Release SAP NetWeaver 2004s and can be set up separately for each InfoCube.
For procedures, see Definition of Clustering.
Screen capture input to SAP Business Graphics must adhere to certain format rules in order to be recognized correctly.
SAP Business Graphics assumes that your screen data resembles the basic SAP table structure. This structure is somewhat flexible, but the table must obey the format rules listed in this section.
Restrictions on the Format of the Data
If you use the screen capture facility to input graphics data, the input table can contain either a single list of values, or rows and columns. If the data is a single list, you can include the values themselves and labels for each value. If the data has rows and columns, you can include a label for each row, a label for each column, and the table values themselves.
You cannot use the screen capture facility to input data in multiple tables. If you want to graph data occurring in multiple tables, you must write the input values to a file using ABAP programming tools. See SAP Graphics: Programming Interfaces for more information.
Format Rules for Numerical Values
Numerical values must obey the following rules:
Within a numerical value, the screen capture recognizes only the minus sign (hyphen), the comma, and the decimal point (period) as legitimate punctuation. Exponential notation and other variations are not recognized.
Note that the functions of the period and the comma in the English system are exactly opposite to their functions in some European systems. If your numbers are not being interpreted correctly, check with the system administrator to determine how these characters should be used.
The minus sign must occur after the number, with no intervening spaces.
All numbers in a row must be separated by spaces.
A column of numbers is right-justified and identified by the position of its right-most character. Each number belonging to this column must have its right-most character in the correct position.
If you have values partially or entirely out of alignment with the given right-most character position, they will not be interpreted as belonging to the proper column. In most cases, the screen capture program assumes these are values for an entirely new column.
You may leave out values for a given row or column.
Format Rules for Text Strings
You can include labels in the table to name the rows and columns. You can also provide a title for the set of rows, for the set of columns, and for the graph as a whole.
SAP Business Graphics does not accept more than 32 elements per dimension. As a result, you cannot have more than 32 rows or 32 columns in your table.
Any string of characters not identifiable as a number is assumed to be a label. Labels may occur at the beginnings of a row, at the head of a column, as a title for the rows or columns, or as the graph main title. A non-numeric item placed in among the data values is ignored by the graphics program.
A legitimate number occurring where a label should be is interpreted as a number. If you want to use labels that look like numbers, you must modify them to contain at least one non-numeric character.
Placement of labels for row-names or column-names:
Row-names can occur only at the beginning (left side) of a row.
Column-names should line up above the columns they are heading, but do not necessarily need to begin in the same column. They should be separated by at least two spaces.
If you don't adhere to these requirements, the screen capture program attempts to pick out the labels anyway. However, the results may not be what you expect. (Check the selection bars in the Selection view to see if your headers were correctly identified.)
Placement of titles for rows or columns as a set:
The title for the rows as a set should be placed directly above the column of row-names.
The title for the columns as a set should occur directly above the first of the column-names, and begin in exactly the same position.
The main title for the graph should occur in the very first line of the highlighted area. If you have more text there than just the title, the screen capture program attempts to pick out the string in the center of the line. The longest string in the center of the line separated from other text by double spaces is assumed to be the title.
The maximum length for a text string cannot be specified exactly since this depends on the size of your window, the resolution of your monitor, and other factors.
Many strings too long for a small window are displayed correctly when you enlarge the window to full-screen size. In general, you must experiment to find the optimal length for text strings.

Warnings when loading dimension members - no members loaded

Hello,
I did the mapping and the interface for loading members for a planning dimension (from csv file), run the 'execute' and have two warnings (on step1 and step7), however no members are loaded - warning for step7:
org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 2, in ?
Planning Writer Load Summary:
     Number of rows successfully processed: 0
     Number of rows rejected: 7
     at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)
     at com.sunopsis.dwg.codeinterpretor.k.a(k.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.scripting(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execScriptingOrders(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java)
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)
No additional information is available (I did enabled both logging for IKM, however no logs are created).
Can anybody help me with this issue?
Kind regards
Marcin Stawny

Hi,
I wouldn't worry about the warning messages.
In the IKM are you saying you set the options
LOG_ENABLED     Yes
LOG_ERRORS     Yes
Did you also set up a location and file for the logs
LOG_FILE_NAME
ERROR_LOG_FILENAME
Cheers
John
http://john-goodwin.blogspot.com/

Error when loading data into Planning

Unable to load data into planning 11.1.2.3.200 using ODI 11.1.1.7
Please find the errors from below logs:
INFO [SimpleAsyncTaskExecutor-2]: Oracle Data Integrator Adapter for Hyperion Planning
INFO [SimpleAsyncTaskExecutor-2]: Connecting to planning application [xxxxxxx] on [xxxxxxxxxxx]:[xxxx] using username [admin].
INFO [SimpleAsyncTaskExecutor-2]: Successfully connected to the planning application.
INFO [SimpleAsyncTaskExecutor-2]: The load options for the planning load are
Dimension Name: Account Sort Parent Child : false
Load Order By Input : false
Refresh Database : false
INFO [SimpleAsyncTaskExecutor-2]: Begining the load process.
DEBUG [SimpleAsyncTaskExecutor-2]: Number of columns in the source result set does not match the number of planning target columns.
INFO [SimpleAsyncTaskExecutor-2]: Load type is [Load dimension member].
ERROR [SimpleAsyncTaskExecutor-2]: Record [[A603010, null, null, null, null, null, null, null, null, null, null, null, xxxxx, -100, F3E0,C011,E7172_93275,FY17,Stage 1,Current Service Level,Jul, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null]] was rejected by the Planning Server.
ERROR [SimpleAsyncTaskExecutor-2]: Record [[A601060, null, null, null, null, null, null, null, null, null, null, null, xxxxx, -250, F3E0,C011,E7172_93275,FY17,Stage 1,Current Service Level,Jul, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null]] was rejected by the Planning Server.
log.err
Account,Data Load Cube Name,Budget,Point-of-View,Error_Reason
A603010,xxxxx,-100,F3E0,C011,E7172_93275,FY17,Stage 1,Current Service Level,Jul,Cannot load dimension member, error message is: RemoteException occurred in server thread; nested exception is:
java.rmi.UnmarshalException: unrecognized method hash: method not supported by remote object
A601060,xxxxx,-250,F3E0,C011,E7172_93275,FY17,Stage 1,Current Service Level,Jul,Cannot load dimension member, error message is: RemoteException occurred in server thread; nested exception is:
java.rmi.UnmarshalException: unrecognized method hash: method not supported by remote object
FDMEE log:
ERROR [AIF]: Error: No records exist for Period 'Pd 2 - 2014-08-01'
ERROR [AIF]: Error: No records exist for Period 'Pd 3 - 2014-09-01'
FDMEE Logging Level is set to 5

Are you sure that you haven't got Planning 11.1.2.3.500 in your environment? This sounds spookily similar to the issue described in note 1678759.1 which was seen after applying Planning 11.1.2.3.500. If it's definitely Planning 11.1.2.3.500 is there any chance that someone has applied ODI patch 18687916 to the ODI home (C:\Oracle\Middleware\odi)?
If you /*are*/ running Planning 11.1.2.3.500 then you might need to apply patch 18687916 to C:\Oracle\Middleware\odi - you might need note 1683307.1 to take some of the pain out of applying this patch though.
Given the error that you're seeing though there's a mismatch in versions of JAR files between ODI and the Planning server somewhere.
Regards
Craig

Alias when loading metadata into Planning

Hi all,
We are trying to load metadata into Planning 11.1.2 using the outline load utility. We have the dimension name, parent, data storage, and alias.
We get this error when doing the dry run(with /N):
Unrecognized Column header value: Alias
Does this mean we cannot load aliases using the outline load utility? Unfortunately, all the examples in the hp-admin document only talks about loading data. Where in the 'cmd' do we specify that we are loading metadata(and not data itself)?
Thanks,
Sujani

If you are loading to the default alias table the header should be Alias: Default
Cheers
John
http://john-goodwin.blogspot.com/

Error while loading metadata into planning using ODI

Hi John,
While trying toload members into planning using ODI the following error occurred. Please suggest
java.lang.Exception
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)

Hi John,
While trying toload members into planning using ODI the following error occurred. Please suggest
java.lang.Exception
     at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
     at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java)
     at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand(DwgCommandSession.java)
     at com.sunopsis.dwg.cmd.DwgCommandBase.execute(DwgCommandBase.java)
     at com.sunopsis.dwg.cmd.e.i(e.java)
     at com.sunopsis.dwg.cmd.h.y(h.java)
     at com.sunopsis.dwg.cmd.e.run(e.java)
     at java.lang.Thread.run(Unknown Source)

I need format for data in excel file load into info cube to planning area.

Hi gurus,
I need format for data in excel file load into info cube to planning area.
can you send me what should i maintain header
i have knowledge on like
plant,location,customer,product,history qty,calander
100,delhi,suresh,nokia,250,2011211
if it is right or wrong can u explain and send me about excel file format.
babu

Hi Babu,
The file format should be same as you want to upload. The sequence of File format should be same communication structure.
Like,
Initial columns with Characteristics (ex: plant,location,customer,product)
date column (check for data format) (ex: calander)
Last columsn with Key figures (history qty)
Hope this helps.
Regards,
Nawanit

Dimension's Members Load into Planning

Similar Messages

Maybe you are looking for