Error editing flow dimension

Hello xperts, when i tryediting FLOW dimension in SAP BPC 7 NW, the following error triggers up:
Exception from HRESULT:0x800a03EC , , what could i check ?
thaks in advance

Hi,
This error might occur while procssing dimensions. You can implement the SAP Note: 1471431 for the same. Here are the excerpts:
"This problem was resolved by reinstalling the Primary Assembly Interop for Office 2007. This can be downloaded from the following Microsoft web site:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=59daebaa-bed4-4282-a28c-b864d8bfa513
Do not use the interop.excel.dll which is in the BPC installation folder."
Hope this resolves your issue.
Regards,
Poonam

Similar Messages

BPC 7.5 NW - BPF: validation error the CV dimension is management ?

Hi, some know this error in BPF for SAP BPC 7.5 NW ?
BPF: validation error the CV dimension is management
BPF: Error de validación; la dimensión CV CUENTA no es de gestión
BPF: Error de validación; la dimensión CV Category no es de identificación
BPF: Error de validación; la dimensión CV CentroDeCosto no es de gestión
BPF: Error de validación; la dimensión CV Moneda_Ppto no es de gestión
BPF: Error de validación; la dimensión CV PARAMETRO no es de gestión
BPF: Error de validación; la dimensión CV RptCurrency no es de gestión
BPF: Error de validación; la dimensión CV Sociedad no es de gestión
BPF: Error de validación; la dimensión CV Sucursales no es de gestión
BPF: Error de validación; la dimensión CV Tipo_vta no es de gestión
I am reading "How to configure and execute Business Process Flows in SAP BusinessObjects Planning and Consolidation 7.5 version for SAP NetWeaver"
Thank you.

Hi Vitoto,
Each step should have a driver dimension. This dimension needs to have the OWNER property. So, in each step, you need to select which is the driver dimension. And you need to select the member as well.

AWM - error duirng maintain dimension process

I get the following error when selecting the maintain option on the product dimension (PROD):
An error has occurred on the server
Error class: Express Failure
Server error descriptions:
INI: Error creating a definition manager, Generic at TxsOqConnection::generic<BuildProcess>
INI: XOQ-01711: Aggregation path for hierarchies on a dimension "PROD" is inconsistent, Generic at TxsOqStdFormCommand::execute
I am running awm11.1.0.7.0B on db version 11G 11.1.0.7.0.
Any ideas on what this means?
Thanks,
Frank
Edited by: bmwrider on Sep 18, 2009 11:54 AM
Edited by: bmwrider on Sep 18, 2009 11:57 AM

The error indicates that there are some loops in your hierarchy (e.g: circular loop within same hierarchy) or inconsistencies in the definition of a specific member across hierarchies (e.g: each hierarchy is well defined on its own but one or more members of the dimension, present in multiple hierarchies, are defined inconsistently, in terms of its descendants, across hierarchies).
If you have enabled the create dimension Materialized View option, try disabling it and rebuild/maintain the dimension. The build process for the dimension with "create MV" option enabled enforces stricter data quality checks than if this option is disabled (dimension MV not required/not created/not used for Query Rewrite).
Also see links:
[Thread: problem maintaining cube |http://forums.oracle.com/forums/thread.jspa?messageID=3507124&#3507124]
[Thread: Error while populating Dimension |http://forums.oracle.com/forums/click.jspa?searchID=-1&messageID=3270334]

Re: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns

Hello Everyone.
I've run into something quite strange and am hoping you can help me.
I am using Apex 4.0.1 and Oracle version 10.2.0.5. I've created a "classical" report in which the underlying SQL is a very simple:
select * from pvtabThe Oracle table pvtab consists of 419 columns, all of which are varchar2(88) and number type. That's it.
When I run the report, al of the columns show up as expected.
However, when I go into the "Report Attributes" tab and click on one of the fields (any of them, it doesn't matter which one), I immediately get the following error:
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "598CAA7B68746A66F4B99E1512C36DED" application checksum = "0"If if replace the "*" with a few actual column names, then I am able to access any of these columns without problem.
If I put back the "*", I then encounter this error again.
I have never seen this error with other SQL SELECT statements in which I use the "*" qualifier to retrieve all columns from the table.
And so, I am wondering if the error is caused because of the large number of columns (419) in my table.
I've seen this same error mentioned in connection with forms but never with a report.
So, is there some limit to the number of columns one can have in a "classic" or interactive report?
Any idea why I would be getting this error?
Here is the DDL for my table pvtab:
CREATE TABLE "PVTAB"
   (     "MICRO" VARCHAR2(4),
     "PRIM" VARCHAR2(4),
     "UNIT" NUMBER,
     "SEC_REF_1" NUMBER,
     "SECN_1" VARCHAR2(88),
     "SEC_REF_2" NUMBER,
     "SECN_2" VARCHAR2(88),
     "SEC_REF_3" NUMBER,
     "SECN_3" VARCHAR2(88),
     "SEC_REF_4" NUMBER,
     "SECN_4" VARCHAR2(88),
     "SEC_REF_5" NUMBER,
     "SECN_5" VARCHAR2(88),
     "SEC_REF_6" NUMBER,
     "SECN_6" VARCHAR2(88),
     "SEC_REF_7" NUMBER,
     "SECN_7" VARCHAR2(88),
     "SEC_REF_8" NUMBER,
     "SECN_8" VARCHAR2(88),
     "SEC_REF_9" NUMBER,
     "SECN_9" VARCHAR2(88),
     "SEC_REF_10" NUMBER,
     "SECN_10" VARCHAR2(88),
     "SEC_REF_11" NUMBER,
     "SECN_11" VARCHAR2(88),
     "SEC_REF_12" NUMBER,
     "SECN_12" VARCHAR2(88),
     "SEC_REF_13" NUMBER,
     "SECN_13" VARCHAR2(88),
     "SEC_REF_14" NUMBER,
     "SECN_14" VARCHAR2(88),
     "SEC_REF_15" NUMBER,
     "SECN_15" VARCHAR2(88),
     "SEC_REF_16" NUMBER,
     "SECN_16" VARCHAR2(88),
     "SEC_REF_17" NUMBER,
     "SECN_17" VARCHAR2(88),
     "SEC_REF_18" NUMBER,
     "SECN_18" VARCHAR2(88),
     "SEC_REF_19" NUMBER,
     "SECN_19" VARCHAR2(88),
     "SEC_REF_20" NUMBER,
     "SECN_20" VARCHAR2(88),
     "SEC_REF_21" NUMBER,
     "SECN_21" VARCHAR2(88),
     "SEC_REF_22" NUMBER,
     "SECN_22" VARCHAR2(88),
     "SEC_REF_23" NUMBER,
     "SECN_23" VARCHAR2(88),
     "SEC_REF_24" NUMBER,
     "SECN_24" VARCHAR2(88),
     "SEC_REF_25" NUMBER,
     "SECN_25" VARCHAR2(88),
     "SEC_REF_26" NUMBER,
     "SECN_26" VARCHAR2(88),
     "SEC_REF_27" NUMBER,
     "SECN_27" VARCHAR2(88),
     "SEC_REF_28" NUMBER,
     "SECN_28" VARCHAR2(88),
     "SEC_REF_29" NUMBER,
     "SECN_29" VARCHAR2(88),
     "SEC_REF_30" NUMBER,
     "SECN_30" VARCHAR2(88),
     "SEC_REF_31" NUMBER,
     "SECN_31" VARCHAR2(88),
     "SEC_REF_32" NUMBER,
     "SECN_32" VARCHAR2(88),
     "SEC_REF_33" NUMBER,
     "SECN_33" VARCHAR2(88),
     "SEC_REF_34" NUMBER,
     "SECN_34" VARCHAR2(88),
     "SEC_REF_35" NUMBER,
     "SECN_35" VARCHAR2(88),
     "SEC_REF_36" NUMBER,
     "SECN_36" VARCHAR2(88),
     "SEC_REF_37" NUMBER,
     "SECN_37" VARCHAR2(88),
     "SEC_REF_38" NUMBER,
     "SECN_38" VARCHAR2(88),
     "SEC_REF_39" NUMBER,
     "SECN_39" VARCHAR2(88),
     "SEC_REF_40" NUMBER,
     "SECN_40" VARCHAR2(88),
     "SEC_REF_41" NUMBER,
     "SECN_41" VARCHAR2(88),
     "SEC_REF_42" NUMBER,
     "SECN_42" VARCHAR2(88),
     "SEC_REF_43" NUMBER,
     "SECN_43" VARCHAR2(88),
     "SEC_REF_44" NUMBER,
     "SECN_44" VARCHAR2(88),
     "SEC_REF_45" NUMBER,
     "SECN_45" VARCHAR2(88),
     "SEC_REF_46" NUMBER,
     "SECN_46" VARCHAR2(88),
     "SEC_REF_47" NUMBER,
     "SECN_47" VARCHAR2(88),
     "SEC_REF_48" NUMBER,
     "SECN_48" VARCHAR2(88),
     "SEC_REF_49" NUMBER,
     "SECN_49" VARCHAR2(88),
     "SEC_REF_50" NUMBER,
     "SECN_50" VARCHAR2(88),
     "SEC_REF_51" NUMBER,
     "SECN_51" VARCHAR2(88),
     "SEC_REF_52" NUMBER,
     "SECN_52" VARCHAR2(88),
     "SEC_REF_53" NUMBER,
     "SECN_53" VARCHAR2(88),
     "SEC_REF_54" NUMBER,
     "SECN_54" VARCHAR2(88),
     "SEC_REF_55" NUMBER,
     "SECN_55" VARCHAR2(88),
     "SEC_REF_56" NUMBER,
     "SECN_56" VARCHAR2(88),
     "SEC_REF_57" NUMBER,
     "SECN_57" VARCHAR2(88),
     "SEC_REF_58" NUMBER,
     "SECN_58" VARCHAR2(88),
     "SEC_REF_59" NUMBER,
     "SECN_59" VARCHAR2(88),
     "SEC_REF_60" NUMBER,
     "SECN_60" VARCHAR2(88),
     "SEC_REF_61" NUMBER,
     "SECN_61" VARCHAR2(88),
     "SEC_REF_62" NUMBER,
     "SECN_62" VARCHAR2(88),
     "SEC_REF_63" NUMBER,
     "SECN_63" VARCHAR2(88),
     "SEC_REF_64" NUMBER,
     "SECN_64" VARCHAR2(88),
     "SEC_REF_65" NUMBER,
     "SECN_65" VARCHAR2(88),
     "SEC_REF_66" NUMBER,
     "SECN_66" VARCHAR2(88),
     "SEC_REF_67" NUMBER,
     "SECN_67" VARCHAR2(88),
     "SEC_REF_68" NUMBER,
     "SECN_68" VARCHAR2(88),
     "SEC_REF_69" NUMBER,
     "SECN_69" VARCHAR2(88),
     "SEC_REF_70" NUMBER,
     "SECN_70" VARCHAR2(88),
     "SEC_REF_71" NUMBER,
     "SECN_71" VARCHAR2(88),
     "SEC_REF_72" NUMBER,
     "SECN_72" VARCHAR2(88),
     "SEC_REF_73" NUMBER,
     "SECN_73" VARCHAR2(88),
     "SEC_REF_74" NUMBER,
     "SECN_74" VARCHAR2(88),
     "SEC_REF_75" NUMBER,
     "SECN_75" VARCHAR2(88),
     "SEC_REF_76" NUMBER,
     "SECN_76" VARCHAR2(88),
     "SEC_REF_77" NUMBER,
     "SECN_77" VARCHAR2(88),
     "SEC_REF_78" NUMBER,
     "SECN_78" VARCHAR2(88),
     "SEC_REF_79" NUMBER,
     "SECN_79" VARCHAR2(88),
     "SEC_REF_80" NUMBER,
     "SECN_80" VARCHAR2(88),
     "SEC_REF_81" NUMBER,
     "SECN_81" VARCHAR2(88),
     "SEC_REF_82" NUMBER,
     "SECN_82" VARCHAR2(88),
     "SEC_REF_83" NUMBER,
     "SECN_83" VARCHAR2(88),
     "SEC_REF_84" NUMBER,
     "SECN_84" VARCHAR2(88),
     "SEC_REF_85" NUMBER,
     "SECN_85" VARCHAR2(88),
     "SEC_REF_86" NUMBER,
     "SECN_86" VARCHAR2(88),
     "SEC_REF_87" NUMBER,
     "SECN_87" VARCHAR2(88),
     "SEC_REF_88" NUMBER,
     "SECN_88" VARCHAR2(88),
     "SEC_REF_89" NUMBER,
     "SECN_89" VARCHAR2(88),
     "SEC_REF_90" NUMBER,
     "SECN_90" VARCHAR2(88),
     "SEC_REF_91" NUMBER,
     "SECN_91" VARCHAR2(88),
     "SEC_REF_92" NUMBER,
     "SECN_92" VARCHAR2(88),
     "SEC_REF_93" NUMBER,
     "SECN_93" VARCHAR2(88),
     "SEC_REF_94" NUMBER,
     "SECN_94" VARCHAR2(88),
     "SEC_REF_95" NUMBER,
     "SECN_95" VARCHAR2(88),
     "SEC_REF_96" NUMBER,
     "SECN_96" VARCHAR2(88),
     "SEC_REF_97" NUMBER,
     "SECN_97" VARCHAR2(88),
     "SEC_REF_98" NUMBER,
     "SECN_98" VARCHAR2(88),
     "SEC_REF_99" NUMBER,
     "SECN_99" VARCHAR2(88),
     "SEC_REF_100" NUMBER,
     "SECN_100" VARCHAR2(88),
     "SEC_REF_101" NUMBER,
     "SECN_101" VARCHAR2(88),
     "SEC_REF_102" NUMBER,
     "SECN_102" VARCHAR2(88),
     "SEC_REF_103" NUMBER,
     "SECN_103" VARCHAR2(88),
     "SEC_REF_104" NUMBER,
     "SECN_104" VARCHAR2(88),
     "SEC_REF_105" NUMBER,
     "SECN_105" VARCHAR2(88),
     "SEC_REF_106" NUMBER,
     "SECN_106" VARCHAR2(88),
     "SEC_REF_107" NUMBER,
     "SECN_107" VARCHAR2(88),
     "SEC_REF_108" NUMBER,
     "SECN_108" VARCHAR2(88),
     "SEC_REF_109" NUMBER,
     "SECN_109" VARCHAR2(88),
     "SEC_REF_110" NUMBER,
     "SECN_110" VARCHAR2(88),
     "SEC_REF_111" NUMBER,
     "SECN_111" VARCHAR2(88),
     "SEC_REF_112" NUMBER,
     "SECN_112" VARCHAR2(88),
     "SEC_REF_113" NUMBER,
     "SECN_113" VARCHAR2(88),
     "SEC_REF_114" NUMBER,
     "SECN_114" VARCHAR2(88),
     "SEC_REF_115" NUMBER,
     "SECN_115" VARCHAR2(88),
     "SEC_REF_116" NUMBER,
     "SECN_116" VARCHAR2(88),
     "SEC_REF_117" NUMBER,
     "SECN_117" VARCHAR2(88),
     "SEC_REF_118" NUMBER,
     "SECN_118" VARCHAR2(88),
     "SEC_REF_119" NUMBER,
     "SECN_119" VARCHAR2(88),
     "SEC_REF_120" NUMBER,
     "SECN_120" VARCHAR2(88),
     "SEC_REF_121" NUMBER,
     "SECN_121" VARCHAR2(88),
     "SEC_REF_122" NUMBER,
     "SECN_122" VARCHAR2(88),
     "SEC_REF_123" NUMBER,
     "SECN_123" VARCHAR2(88),
     "SEC_REF_124" NUMBER,
     "SECN_124" VARCHAR2(88),
     "SEC_REF_125" NUMBER,
     "SECN_125" VARCHAR2(88),
     "SEC_REF_126" NUMBER,
     "SECN_126" VARCHAR2(88),
     "SEC_REF_127" NUMBER,
     "SECN_127" VARCHAR2(88),
     "SEC_REF_128" NUMBER,
     "SECN_128" VARCHAR2(88),
     "SEC_REF_129" NUMBER,
     "SECN_129" VARCHAR2(88),
     "SEC_REF_130" NUMBER,
     "SECN_130" VARCHAR2(88),
     "SEC_REF_131" NUMBER,
     "SECN_131" VARCHAR2(88),
     "SEC_REF_132" NUMBER,
     "SECN_132" VARCHAR2(88),
     "SEC_REF_133" NUMBER,
     "SECN_133" VARCHAR2(88),
     "SEC_REF_134" NUMBER,
     "SECN_134" VARCHAR2(88),
     "SEC_REF_135" NUMBER,
     "SECN_135" VARCHAR2(88),
     "SEC_REF_136" NUMBER,
     "SECN_136" VARCHAR2(88),
     "SEC_REF_137" NUMBER,
     "SECN_137" VARCHAR2(88),
     "SEC_REF_138" NUMBER,
     "SECN_138" VARCHAR2(88),
     "SEC_REF_139" NUMBER,
     "SECN_139" VARCHAR2(88),
     "SEC_REF_140" NUMBER,
     "SECN_140" VARCHAR2(88),
     "SEC_REF_141" NUMBER,
     "SECN_141" VARCHAR2(88),
     "SEC_REF_142" NUMBER,
     "SECN_142" VARCHAR2(88),
     "SEC_REF_143" NUMBER,
     "SECN_143" VARCHAR2(88),
     "SEC_REF_144" NUMBER,
     "SECN_144" VARCHAR2(88),
     "SEC_REF_145" NUMBER,
     "SECN_145" VARCHAR2(88),
     "SEC_REF_146" NUMBER,
     "SECN_146" VARCHAR2(88),
     "SEC_REF_147" NUMBER,
     "SECN_147" VARCHAR2(88),
     "SEC_REF_148" NUMBER,
     "SECN_148" VARCHAR2(88),
     "SEC_REF_149" NUMBER,
     "SECN_149" VARCHAR2(88),
     "SEC_REF_150" NUMBER,
     "SECN_150" VARCHAR2(88),
     "SEC_REF_151" NUMBER,
     "SECN_151" VARCHAR2(88),
     "SEC_REF_152" NUMBER,
     "SECN_152" VARCHAR2(88),
     "SEC_REF_153" NUMBER,
     "SECN_153" VARCHAR2(88),
     "SEC_REF_154" NUMBER,
     "SECN_154" VARCHAR2(88),
     "SEC_REF_155" NUMBER,
     "SECN_155" VARCHAR2(88),
     "SEC_REF_156" NUMBER,
     "SECN_156" VARCHAR2(88),
     "SEC_REF_157" NUMBER,
     "SECN_157" VARCHAR2(88),
     "SEC_REF_158" NUMBER,
     "SECN_158" VARCHAR2(88),
     "SEC_REF_159" NUMBER,
     "SECN_159" VARCHAR2(88),
     "SEC_REF_160" NUMBER,
     "SECN_160" VARCHAR2(88),
     "SEC_REF_161" NUMBER,
     "SECN_161" VARCHAR2(88),
     "SEC_REF_162" NUMBER,
     "SECN_162" VARCHAR2(88),
     "SEC_REF_163" NUMBER,
     "SECN_163" VARCHAR2(88),
     "SEC_REF_164" NUMBER,
     "SECN_164" VARCHAR2(88),
     "SEC_REF_165" NUMBER,
     "SECN_165" VARCHAR2(88),
     "SEC_REF_166" NUMBER,
     "SECN_166" VARCHAR2(88),
     "SEC_REF_167" NUMBER,
     "SECN_167" VARCHAR2(88),
     "SEC_REF_168" NUMBER,
     "SECN_168" VARCHAR2(88),
     "SEC_REF_169" NUMBER,
     "SECN_169" VARCHAR2(88),
     "SEC_REF_170" NUMBER,
     "SECN_170" VARCHAR2(88),
     "SEC_REF_171" NUMBER,
     "SECN_171" VARCHAR2(88),
     "SEC_REF_172" NUMBER,
     "SECN_172" VARCHAR2(88),
     "SEC_REF_173" NUMBER,
     "SECN_173" VARCHAR2(88),
     "SEC_REF_174" NUMBER,
     "SECN_174" VARCHAR2(88),
     "SEC_REF_175" NUMBER,
     "SECN_175" VARCHAR2(88),
     "SEC_REF_176" NUMBER,
     "SECN_176" VARCHAR2(88),
     "SEC_REF_177" NUMBER,
     "SECN_177" VARCHAR2(88),
     "SEC_REF_178" NUMBER,
     "SECN_178" VARCHAR2(88),
     "SEC_REF_179" NUMBER,
     "SECN_179" VARCHAR2(88),
     "SEC_REF_180" NUMBER,
     "SECN_180" VARCHAR2(88),
     "SEC_REF_181" NUMBER,
     "SECN_181" VARCHAR2(88),
     "SEC_REF_182" NUMBER,
     "SECN_182" VARCHAR2(88),
     "SEC_REF_183" NUMBER,
     "SECN_183" VARCHAR2(88),
     "SEC_REF_184" NUMBER,
     "SECN_184" VARCHAR2(88),
     "SEC_REF_185" NUMBER,
     "SECN_185" VARCHAR2(88),
     "SEC_REF_186" NUMBER,
     "SECN_186" VARCHAR2(88),
     "SEC_REF_187" NUMBER,
     "SECN_187" VARCHAR2(88),
     "SEC_REF_188" NUMBER,
     "SECN_188" VARCHAR2(88),
     "SEC_REF_189" NUMBER,
     "SECN_189" VARCHAR2(88),
     "SEC_REF_190" NUMBER,
     "SECN_190" VARCHAR2(88),
     "SEC_REF_191" NUMBER,
     "SECN_191" VARCHAR2(88),
     "SEC_REF_192" NUMBER,
     "SECN_192" VARCHAR2(88),
     "SEC_REF_193" NUMBER,
     "SECN_193" VARCHAR2(88),
     "SEC_REF_194" NUMBER,
     "SECN_194" VARCHAR2(88),
     "SEC_REF_195" NUMBER,
     "SECN_195" VARCHAR2(88),
     "SEC_REF_196" NUMBER,
     "SECN_196" VARCHAR2(88),
     "SEC_REF_197" NUMBER,
     "SECN_197" VARCHAR2(88),
     "SEC_REF_198" NUMBER,
     "SECN_198" VARCHAR2(88),
     "SEC_REF_199" NUMBER,
     "SECN_199" VARCHAR2(88),
     "SEC_REF_200" NUMBER,
     "SECN_200" VARCHAR2(88),
     "SEC_REF_201" NUMBER,
     "SECN_201" VARCHAR2(88),
     "SEC_REF_202" NUMBER,
     "SECN_202" VARCHAR2(88),
     "SEC_REF_203" NUMBER,
     "SECN_203" VARCHAR2(88),
     "SEC_REF_204" NUMBER,
     "SECN_204" VARCHAR2(88),
     "SEC_REF_205" NUMBER,
     "SECN_205" VARCHAR2(88),
     "SEC_REF_206" NUMBER,
     "SECN_206" VARCHAR2(88),
     "SEC_REF_207" NUMBER,
     "SECN_207" VARCHAR2(88),
     "SEC_REF_208" NUMBER,
     "SECN_208" VARCHAR2(88)
   );Thank you for any help/advice.
Elie
Edited by: EEG on Jun 12, 2011 2:09 PM

So, is there some limit to the number of columns one can have in a "classic" or interactive report?Yes. See Oracle® Application Express Application Builder User's Guide Release 4.0, Appendix B: Oracle Application Express Limits.
Any idea why I would be getting this error?No, but I've replicated it in APEX 4.0.2.00.07 on 11.2.0.1.0 EE using a table of 420 <tt>varchar2(88)</tt> columns:
>
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "50C9BDC0AA1AEF0EB272E9158B2117B4" application checksum = "0"
>
Happens whether using <tt>select *</tt> or including all column names in the query. (I know you don't want to type all the column names, but I'd never use <tt>select *</tt> in a production application: always use a proper column list. You can get one without typing by drag-and-drop of a table in most IDEs, or a query from <tt>user_tab_columns</tt>.)
I hit the problem at 274 columns. Such an arbitrary number leads me to think that the problem is not one of the number of columns per se, but is due to some other limit (possibly a 32K VARCHAR2/RAW buffer somewhere).
Workaround:
Updates to the report column attributes are actually being saved, and you can navigate them using the Page Definition tree view as described in Appendix B.
Getting More Help:
This is probably a bug. If you have a support agreement with Oracle raise an SR with Oracle Support.
Also:
<li>Search the forum using the "ORA-20503" code and other possible terms to see if there's anything relevant. I had a quick look but the only thread in this context recommended an upgrade on an Oracle 9 DB version that's not compatible with APEX 4.0.
<li>To get the attention of the Oracle APEX team or anyone else who may know more about this problem than we do, edit your original post and change the Subject to be more specific about the actual nature of the problem: <em>BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns</em>, and include your database version/edition and the definition of the <tt>PVTAB</tt> table.
Finally:
Somebody's bound to ask, so we might as well get started:
<li>Why so many columns?
<li>What requirement is this trying to fulfil?

Error editing task sequence: Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" From XML into WMI

I've started getting an intermittent error editing my Windows 7 OSD task sequence. Sometimes I can open the TS to edit, but when I try to apply changes I get the error. Other times I get the error when trying to open the TS. If I try again
right away, I still get the error, but if I wait a few minutes and try again sometimes it will open the TS.
The error reads:
ConfigMgr Error Object:instance of SMS_Extended Status{Description = "Failed to load dynamic properties for class \"SMS_TaskSequence_ApplyWindowsSettingsAction\" from XML into WMI";Error Code = 2147943746;File = "e:\\qfe\\nts\\sms\\siteserver\\sdk_provider\\smsprov\\ssptspackage.cpp";Line = 3454;Operation = "ExecMethod";ParameterInfo = "SMS_TaskSequencePackage";ProviderName = "WinMgmt";StatusCode = 2147749889;}
Coinciding with this error, I show the following entries in the TaskSequenceProvider.log file:
[PID: 7608] Invoking method SMS_TaskSequence.LoadFromXml
TaskSequenceProvider
Failed to protect memory buffer, hr=0x80070542
TaskSequenceProvider
Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load node Apply Windows Settings from XML into WMI 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "PostInstall" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "Execute Task Sequence" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load children steps for node "" from XML 0x80070542 (2147943746)
TaskSequenceProvider
Failed to load XML for the task sequence into WMI 0x80070542 (2147943746)
TaskSequenceProvider
[PID: 7608] Done with method SMS_TaskSequence.LoadFromXml
TaskSequenceProvider
Setting status complete: status code = 0x80070542; Failed to load dynamic properties for class "SMS_TaskSequence_ApplyWindowsSettingsAction" from XML into WMI
TaskSequenceProvider
I exported the task sequence and checked in "object.xml" for the "ApplyWindowsSettingsAction", to see if there was something odd in the xml, but I don't find anything that jumps out as being wrong. Here's the section of XML for
that step. I've removed identifying info, and replaced it with a generic term in bold.
<step type="SMS_TaskSequence_ApplyWindowsSettingsAction" name="Apply Windows Settings" description="" runIn="WinPE" successCodeList="0" runFromNet="false"><action>osdwinsettings.exe /config</action><defaultVarList><variable name="OSDLocalAdminPassword" property="AdminPassword"></variable><variable name="OSDComputerName" property="ComputerName">%_SMSTSMachineName%</variable><variable name="OSDProductKey" property="ProductKey"></variable><variable name="OSDRandomAdminPassword" property="RandomAdminPassword">false</variable><variable name="OSDRegisteredOrgName" property="RegisteredOrgName">COMPANY NAME</variable><variable name="OSDRegisteredUserName" property="RegisteredUserName">COMPANY NAME</variable><variable name="OSDServerLicenseConnectionLimit" property="ServerLicenseConnectionLimit">5</variable><variable name="OSDTimeZone" property="TimeZone">Central Standard Time</variable></defaultVarList></step><step type="SMS_TaskSequence_ApplyNetworkSettingsAction" name="Apply Network Settings" description="" runIn="WinPEandFullOS" successCodeList="0" runFromNet="false"><action>osdnetsettings.exe configure</action><defaultVarList><variable name="OSDDomainName" property="DomainName">DOMAIN.COM</variable><variable name="OSDJoinPassword" property="DomainPassword"></variable><variable name="OSDJoinAccount" property="DomainUsername">DOMAIN ACCOUNT</variable><variable name="OSDEnableTCPIPFiltering" property="EnableTCPIPFiltering" hidden="true">false</variable><variable name="OSDNetworkJoinType" property="NetworkJoinType">0</variable><variable name="OSDAdapterCount" property="NumAdapters" hidden="true">0</variable></defaultVarList></step>
Is there any other log I should check for a clue on this issue? What could be causing this error?

Thanks for sharing that! I tend to save contacting MS support until after I've exhausted other options. I'm always afraid that I'll spend the $500 to open a case and then it turns out to be something simple that I would have found if I had just
kept working on it myself a little longer.
It looks like that link is for an update released in February as KB3023562. I downloaded and installed it. I'll try opening/editing/saving the task sequence a few times today to see if the issue is resolved.
After I had already installed it, I thought to look up that update in configmgr. The update is listed as superseded by 2 other updates. The newest of those is KB3046049, which just installed last night with the other March patches, so it's possible
that I didn't need to install KB3023562 after all.

Roles for the user to Edit the Dimension without being an administrator

Dear Users,
I have a query based on Planning security.
I want the user to edit the dimensions and members in planning application. However, the user cannot be administrator.
I have created a user and assigned the role of "Interactive User" on Planning roles and of "Dimension Editor" on Shared Services access. With this provisioning user the "Administration-->Dimension" is grayed out for the user.
Please suggest if roles can be assigned to the user in order to Edit the Dimension without being an administrator?
Regards,
Praveen.

I am sure this question gets asked over and over, they need to be an administrator.
Cheers
John
http://john-goodwin.blogspot.com/

Error:Insert flow into I$ table

Hi,
While implementing scd2 type,I am getting an error"Insert flow into I$ table"
ODI-1228: Task int1 (Integration) fails on the target ORACLE connection twitter.
Caused By: java.sql.SQLSyntaxErrorException: ORA-00936: missing expression.
Please help!!
Thanks.

Hi,
code generated is:
insert /*+ APPEND */ into ODIWR.I$_EMP_SCD_TARGET
     ENAME,
     EMAIL,
     PHNUM,
     SALARY,
     JOB_ID,
     START_DATE,
     IND_UPDATE
select *
from (
     select
          EMP_SCD_SRC.FIRST_NAME     ENAME,
     EMP_SCD_SRC.EMAIL     EMAIL,
     EMP_SCD_SRC.PHONE_NUMBER     PHNUM,
     EMP_SCD_SRC.SALARY     SALARY,
     EMP_SCD_SRC.JOB_ID     JOB_ID,
          SYSDATE     START_DATE,
     'I' IND_UPDATE
     from     ODIWR.EMP_SCD_SRC EMP_SCD_SRC
     where     (1=1)
) S
where NOT EXISTS (
     select 'x'
     from     ODIWR.EMP_SCD_TARGET T
     where
     and     ((S.ENAME = T.ENAME) or (S.ENAME IS NULL and T.ENAME IS NULL))
          and     ((S.EMAIL = T.EMAIL) or (S.EMAIL IS NULL and T.EMAIL IS NULL))
          and     ((S.PHNUM = T.PHNUM) or (S.PHNUM IS NULL and T.PHNUM IS NULL))
          and     ((S.SALARY = T.SALARY) or (S.SALARY IS NULL and T.SALARY IS NULL))
          and     ((S.JOB_ID = T.JOB_ID) or (S.JOB_ID IS NULL and T.JOB_ID IS NULL))
     and     CURRENT_FLAG     = 1
     and     END_DATE     = to_date ('01-01-2400', 'mm-dd-yyyy')
Ikm used is IKM Oracle Slowly Changing Dimension

Error:No Flows Exist for processing (TCODE: TBB1)

Hi All,
In TBB1 i have maintained the below Parameters.
Application:
Money Market
General Settings:
Company Code
Transaction
Product Type
Transaction Type
Business Partner
Currency
Flow Classification
Up to and including Due Date
Posting Control:
Posting date
Posting Period
Document date
after maintaining the above parameters i have ticked the Test run and tried to execute but i am getting the below error
Error:No Flows Exist for processing.(Message no. T0917)
Please help me to solve this issue.
Thanks in advance,
Sana

Hi,
There can be multiple reasons for this. Check whether there are any flows which are relevant for posting for the transaction and whether your due date parameter in TBB1 encompasses all the flows. In case if you use settlement option, then check whether the transaction is settled and the cash flow of the transaction shows the flows are flagged for posting.
Regards,
Ravi

Sub-tables/Flow dimension - NETVAR

Hi all
Does anybody know what it means if a particular value in the the Sub-tables/Flow dimension has a FLOW_TYPE of NETVAR ?
Regards
Byron

Hi pmyahoo,
According to your description, you want to use T-SQL to create a relational view contains fact table with dimension tables. Right?
In Analysis Services, a data source view (DSV) is an abstraction of a relational data source that becomes the basis of the cubes and dimensions you create in a multidimensional project. It contains the logical model of the schema used by Analysis Services
multidimensional database objects—namely cubes, dimensions, and mining structures. It is the metadata definition, stored in an XML format, of these schema elements used by the Unified Dimensional Model (UDM) and by the mining structures. So it's a virtual
table like the View we create via T-SQL. Please refer to links below:
Data Source Views (Analysis Services - Multidimensional Data)
Defining a Data Source View (Analysis Services)
When designing data source views, to determine if using a bridge table depends on the relation ship between dimension table and fact table. If it's a many-to-many relationship, it's better to use a bridge. Please refer to an article below:
SSAS/KIMBALL: modeling a N:M relation between dimensions (part I)
If you have any question, please feel free to ask.
Best Regards,
Simon Hou
TechNet Community Support

FLOW_TYPE property. Accdetail or flow dimension

Hi experts,
I'm analizing FLOW TYPE property of Accdetail or flow dimension, but I don't know the useful for this property. I mean, what is the purpose of this property or where I can use it. I know I can introduce some values like OPENING, CLOSING.
I'm setting up a Legal Consolidation application.
Could any one could explain me something? because guides show anyhing
Thank you very much in advance
Gabrie Garcia

Hello Gabriel,
We are also working with the variation in scope which needs to customized on the FLOW_TYPE property of the flow and even though I have issues (its not performing how it should) here are some comments on how the system should performe.
For example a new company joining the consolidation group. It was not there last year, therefore at the consolidation level the opening balance should be cero, right?
In this case we would need to reclassify the opening balance flow of the new entity/trading partner to the flow VARSCPNEW as well as performing the "automatic adjustments" on this flow.
As in the previous messages there are three additional cases, changes in the method, changes in the percentage and companies leaving the consolidation hierarchy.
If you download the information of BPC10 of the IFRS starter kit, there are some cases for each one of this scenarios
Regards
Dani

ERROR:- ENT-09671 ERROR WHILE EXTRACTION DIMENSION METADATA FOR DIMENSION

Hello all,
i am working on OWB 10gR2 while i try to validate & Deploy according to the following process it was successful but as i tried to view data from dimension i am getting an error which i have mentioned below
Source Table = CUST_MST
Destination Table = CUSTOMER
Dimension = CUSTOMER
Mapping = CUSTOMER_MAP
Validate Table CUST_MAP.
Validate Table CUSTOMER.
Validate Dimension CUSTOMER.
Validate Mapping CUSTOMER_MAP.
Deploy table CUSTOMER.
Deploy mapping CUSTOMER_MAP.
Deploy dimension CUSTOMER (configured => Deploy All).
Deploy table CUSTOMER.
Deploy sequence <CUSTOMER_SEQ>
Deploy mapping CUSTOMER_MAP.
Deploy dimension CUSTOMER (configured => Deploy All).
Start mapping to load table CUSTOMER.
After this i am getting an error while i tried to view the data in the dimension
ERROR:- ENT-09671 ERROR WHILE EXTRACTION DIMENSION METADATA FOR DIMENSION DATAVIEWER
Thanks & Regards
Pratik Lakhpatwala
Jr Oracle DBA

Not sure if it's valid to have a dimension with 1 hierarchy and 1 level in that hierarchy. The hierarchy may have to have at least 2 levels. If you want the configuration of a dimension with 1 hierarchy and 1 level, CWM2 may want you to omit the hierarchy, thus creating the dimension with only 1 level.

Cannot reverse GR. Error: "Document flow for delivery cannot be updated"

An STO has GI, GR and invoice verification. However, it appears the delivery was deleted such that when trying to reverse the GR, there is an error: "Document flow for delivery not be updated".
According to OSS Note 1499411, solution is:
Change your process so that the goods receipt (in stock transport order scenarios with replenishment deliveries) is always posted with reference to the replenishment delivery and never with reference to the purchase order.
If this is not possible and you have to work with the restrictions of a goods receipt with reference to the purchase order instead of the replenishment delivery, implement the attached corrections to be able to correctly post the GR reversal with reference to the stock transport order.
However, it does not say anything on how the GR of the existing STO will be reversed.
How will i reverse the GR in this case?
Thanks!
Best Regards,
Armie

Unfortunately, when I use MB0A and I input the delivery number under Find POs for Preceeding Document, it errors out as well as the delivery does not exist.
Any other option to reverse the GR?

How handle Add Media Failure Error: File Video Dimensions (Width/Height) Too Large?

I am a brand new user of Premiere Elements. I am using it for stop gap animation, bringing in digital still photos from my Nikon D3200. I just attempted to bring in the first set of photos from the SD card. I'm running Windows 7. After loading the photos, an "Add Media Failure" box came up with the message "Error: File Video Dimensions (width/height) too large". Is something wrong with the width and height of the photos and if so what do I need to do to make it work? There were 763 photos, but the message seems to refer to the height/width of each photo and not the total file size so to speak - right? During the import process, the program prompted us to bring the photos in as images and not as videos -- so that is what we selected. Thank you for any assistance.

Photo Scaling for Video http://forums.adobe.com/thread/450798
-Too Large May = Crash http://forums.adobe.com/thread/879967
-And another crash report http://forums.adobe.com/thread/973935

Syslog error: ERROR getting flow policy details

I just RMA'ed an inline wae-7371 and now both inline devices are throwing the below error. Traffic is being optimized if I look at active connections.
WAAS-STATS-3-600023: populate_flow_policy_details: ERROR getting flow policy details, Policy details have changed or are unavailable
Any help would be good, even a good listing of WAAS syslogs would be helpful, before calling TAC

Version is 4.1.3b we didnt upgrade with the RMAed device (but we are planing on upgrading to fix a AAA problem we are having with our ACS express)
Our policies have reciently been appied to the default device group and there are only 6 listed.
Application Policies
Classifier
Application
Action
Enabled
Type - Position
   NEODIN_Transactions-classifier
NEODIN_Transactions
Optimize(DRE,LZ)
Enabled
Basic 1
   DICOM_Classifier
DICOM
Optimize(DRE,LZ)
Enabled
Basic 2
   CIFS
WAFS
Optimize(DRE,LZ)
Enabled
Basic 3
   HTTP
Web
Optimize(DRE,LZ),Accelerate(HTTPAccelerator)
Enabled
Basic 4
   LDAP
Directory-Services
Optimize(DRE,LZ)
Enabled
Basic 5
   N/A
N/A
Optimize(DRE,LZ)
Enabled
Other 1
I thought this was strange, that our backups went from 24k to 4k after centrally managing the policies.
Are you saying that all the 162 polcies need to be listed, even if you dont have that type of traffic (IE Novell traffic)? We are currently just auditing the traffic we have between these two datacentres (95% of the traffic is our DICOM classifier on port 104) and are adding classifiers as needed.
I can try during our next "service window" to restore the default policies and add our two custom ones back (plus the http accelerator)
We are not using netflow on the devices.

Error when maintaining dimension in AWM 10.1.0.4

Hi,
I am running AWM 10.1.0.4 on a 10.1.0.4 database. Have set up dimension, levels, hierarchy, and mappings. Everything OK, but when trying to maintain this dimension I get the following error message:
oracle.AWXML.AWException: Action BUILDDATABASE failed on object OLAP_DBA1.TEST1
at oracle.AWAction.BuildDatabase.Execute(BuildDatabase.java:414)
at oracle.olap.awm.wizard.awbuild.BuildWizardHelper$1.construct(BuildWizardHelper.java:175)
at oracle.olap.awm.ui.SwingWorker$2.run(SwingWorker.java:109)
at java.lang.Thread.run(Unknown Source)
Caused by: oracle.AWXML.AWException: oracle.express.ExpressServerException
java.sql.SQLException: Ikke flere data å lese fra porten (No more data to read from the port)
at oracle.AWXML.AWConnection.executeCommand(AWConnection.java:248)
at oracle.AWAction.BuildDatabase.Execute(BuildDatabase.java:397)
... 3 more
Caused by: oracle.express.ExpressServerException
java.sql.SQLException: Ikke flere data å lese fra porten (No more data to read from the port)
at oracle.express.spl.SPLExecutor.executeCommand(SPLExecutor.java:155)
at oracle.AWXML.AWConnection.executeCommand(AWConnection.java:244)
... 4 more
Any clues?
Sverre

There are posts on the OLAP forum covering this problem. Anthony Waite from the OLAP Product Management team has provided the following information:
e new, default Model View in AWM 10.1.0.4.0 is based upon the OLAP Analytic Workspace API (a.k.a. AW/XML). Just to recap and further clarify my earlier post, you must pass the following requirements in order to use it:
1) Be sure to be using the Enterprise Edition of the Oracle Database 10g.
SQL> select banner from v$version where banner like 'Oracle%';
You should see Oracle Database 10g Enterprise Edition.
2) Be sure to have the Data Warehouse database configuration or the OLAP Option enabled.
SQL> select parameter, value from v$option where parameter='OLAP';
You should see OLAP TRUE.
3) Be sure that the RDBMS 10.1.0.4 patch set has been completely installed. Users often miss the required Post-Installation Steps such as running catpatch.sql.
SQL> select comp_name, version, status from dba_registry;
You should see VALID and 10.1.0.4.0 for the OLAP components.
4) The Oracle Database must have the compatibility mode of 10.1 to use the Model View as it relies on the unique features found in Oracle Database 10g.
SQL> select name, value, description from v$parameter where name ='compatible';
You should see 10.1, not 9.2 or earlier.
5) Please refer to the patchnote.htm that is bundled with 10.1.0.4.0 patch set. Only you are aware of what type of database configuration you have. You will want to pay close attention to "7.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters" and "7.2.2 Upgrade the Release 10.1 Database".
Basically, I believe you have missed these required steps after installing the 10.1.0.4.0 patch set from the OUI: (pasted from the patchnote.htm)
For the full discussion please refer to this link:
Re: Error trying to Analytic Workspace using latest version AWM 10.1.0.4
Hope this helps
Keith
Oracle Business Intelligence Product Management
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Beans http://www.oracle.com/technology/products/bib/index.html
Discoverer: http://www.oracle.com/technology/products/discoverer/
BI Software: http://www.oracle.com/technology/software/products/ias/devuse.html
Documentation: http://www.oracle.com/technology/documentation/appserver1012.html
BI Samples: http://www.oracle.com/technology/products/bi/samples/
Blog: http://oraclebi.blogspot.com/

Error editing flow dimension

Similar Messages

Maybe you are looking for