EPM Addin - Grey Edit Report Issue

Even after applying KB3025036  fixit for MS office 2010 or 2013, still the problem exists for SAP EPM addin. It is a big show stopper and not allowing for next steps
MSoffice 2010 and 2013 - Issue still persists.
After installing Microsoft security updates, the following issues are encountered in the EPM Add-in (10.X) and BPC for Excel (7.X) products:
'Edit Report' is grayed out
Context options are grayed out
The EPM pane shows no connection for current report
Refreshing the report has no effect
Journal options are grayed out
It is not possible to open an EPM Add-in report
The following error is displayed: EPM - General Error: Unable to get the Object property of the OLEObject class

Hi,
We have definitely heard your frustration, and Microsoft understands the position our customers are in and we are actively working to find a solution besides a FixIt that can be deployed to remedy the issue.
We can also remove the MS14-082 Microsoft Office Security Updates for December 2014 by temporary bypassing this issue.
If we have any update, I'll post in this forum and you can focus
this blog
============
Update,
Hotfixes for this issue have been released in the March 2015 Updates for Office 2007, 2010 & 2013.
http://blogs.technet.com/b/the_microsoft_excel_support_team_blog/archive/2014/12/13/forms-controls-stop-working-after-december-2014-updates-.aspx
Thanks for your understanding.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Similar Messages

  • Edit Report option freezes and Formatting Vanishes in EPM 10.0

    Hi,
    While creating a report in EPM 10.0 which i have selected as 'Use as Input form', i created Active X buttons and did dynamic formatting as well. All seems to be fine but as i Close and Reopen, or i Refresh the template, formatting vanishes and Edit Report option also gets disabled.
    I am working on EPM 10.0 SP07 Patch 02. Please guide me on this.
    Thank you.
    Rgds,
    Poonam

    Hi Poonam,
    This is probably happening because the report/input schedules is not getting connected. Please check the connections once.
    Also if you had named the report in "Edit Report" earlier, say for example "Sales Report", once the report is open you should be able to see this name on the EPM context pane, right side under Current Report: Connected to "Your Model" and below that in the drop down the default selection should be "Sales Report". This means that the report is connected and the Edit Report option is active.
    Hope this helps.
    Regards,
    Bhairavi

  • Edit Report option freezes and Formatting vanishes in EPM Excel 10.0

    Hi,
    While creating a report in EPM 10.0 which i have selected as 'Use as Input form', i created Active X buttons and did dynamic formatting as well. All seems to be fine but as i Close and Reopen, or i Refresh the template, formatting vanishes and Edit Report option also gets disabled.
    I am working on EPM 10.0 SP07 Patch 02. Please guide me on this.
    Thank you.
    Rgds,
    Poonam

    Hi Poonam,
    This is probably happening because the report/input schedules is not getting connected. Please check the connections once.
    Also if you had named the report in "Edit Report" earlier, say for example "Sales Report", once the report is open you should be able to see this name on the EPM context pane, right side under Current Report: Connected to "Your Model" and below that in the drop down the default selection should be "Sales Report". This means that the report is connected and the Edit Report option is active.
    Hope this helps.
    Regards,
    Bhairavi

  • "Edit Report" option getting disabled on saving the report in BPC 10.0

    I have created input schedules using "Edit Report" functionality in BPC 10.0 NW, added a few buttons and corresponding VB code and tested the input schedule by sending data and running data manager package. Everything is working fine. After that I saved the input schedule and closed the Excel. On reopening the excel Add-in and the input schdule, the "Edit report" option becomes disabled and refresh and other functionalities available for the report get disabled. I have faced this issue a couple of times. Has anybody else faced this issue? Can someone let me know the resolution to this problem?

    Hi Shruti,
    This is probably happening because the report/input schedules is not getting connected. Please check the connections once.
    Also if you had named the report in "Edit Report" earlier, say for example "Sales Report", once the report is open you should be able to see this name on the EPM context pane, right side under Current Report: Connected to "Your Model" and below that in the drop down the default selection should be "Sales Report". This means that the report is connected and the Edit Report option is active.
    Hope this helps.
    Regards,
    Bhairavi

  • User report issues in 1.1.0.21.97

    A couple of issues i'm experiencing with user reports on Mac OS X in the latest pre-releas build
    first off, if I am asked for a password (first time I use the connection) there is no feedback if the connection fails (worng password for instance)
    The second problem I'm facing is every time I try to rerun a certain master-detail report I'm getting an NPE
    this is the stacktrace:
    22-nov-2006 15:37:31 oracle.report.addin.ReportEditor updateContent
    INFO: ReportEditor.updateContent()
    22-nov-2006 15:37:33 oracle.dbtools.raptor.controls.display.DisplayResultTable getUI
    INFO: DisplayResultTable.getUI()
    Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
    at oracle.dbtools.raptor.controls.display.DisplayPanel.refresh(Unknown Source)
    at oracle.dbtools.raptor.controls.display.DisplayPanel.refresh(Unknown Source)
    at oracle.report.addin.ReportEditor$1.actionPerformed(Unknown Source)
    at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1882)
    at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2202)
    at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
    at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
    at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
    at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
    at java.awt.Component.processMouseEvent(Component.java:5554)
    at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
    at java.awt.Component.processEvent(Component.java:5319)
    at java.awt.Container.processEvent(Container.java:2010)
    at java.awt.Component.dispatchEventImpl(Component.java:4021)
    at java.awt.Container.dispatchEventImpl(Container.java:2068)
    at java.awt.Component.dispatchEvent(Component.java:3869)
    at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4256)
    at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3936)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3866)
    at java.awt.Container.dispatchEventImpl(Container.java:2054)
    at java.awt.Window.dispatchEventImpl(Window.java:1774)
    at java.awt.Component.dispatchEvent(Component.java:3869)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
    reloadBuffers(): 53 nodes checked in 0.006489 second(s)
    reloadBuffers(): 53 nodes checked in 0.005422 second(s)
    reloadBuffers(): 53 nodes checked in 0.004306 second(s)
    22-nov-2006 15:43:17 oracle.report.addin.ReportEditor updateContent
    INFO: ReportEditor.updateContent()
    only happens with master-detail report
    Message was edited by: Barsema
    barsema

    We have verified the connection error on the latest evaluation build is working as expected. i.e. if you supply wrong password you get alerted to that. This has been verified on the windows and Mac OS X. Please try the latest evaluation release 1.1.0.22.71.
    Your reports issue has also been addressed.
    Sue

  • APEX Database Configuration re XML / BI Publisher report issue

    Greetings,
    I have a problem that would be considered database related.
    I am attempting to implement the APEX REPORTS functionality.
    The process currently breaks for me when I have over 45 columns in an XML output in the APEX Reports framework. When I say BREAK, this is a very soft break. It just does not return any XML. The system eventually returns “no response” and then continues normally.
    Looking closer at the DB, I will see the session hanging on, and not completing with very little information. These sessions will stay active for a very long time… possibly indefinitely. They are running as “APEX_PUBLIC_USER”.
    The “current statement” shows as follows…
    BEGIN
       DECLARE
          l_bind_values   wwv_flow_global.vc_arr2;
          i               NUMBER                  := 0;
       BEGIN
          FOR c1 IN (SELECT c001, c002
                       FROM wwv_flow_collections
                      WHERE collection_name = 'SET_BIND_VALUES')
          LOOP
             i := i + 1;
             l_bind_values (i) := c1.c002;
          END LOOP;
          FOR c2 IN (SELECT owner
                       FROM wwv_flows
                      WHERE ID = :fb_flow_id)
          LOOP
             wwv_flow_render_query.print_shared_query
                                         (p_flow_id            => :fb_flow_id,
                                          p_format             => 'XML',
                                          p_xml_structure      => :p1112_xml_structure,
                                          p_query_text         => :p1110_query,
                                          p_query_name         => :p1110_name,
                                          p_query_owner        => c2.owner,
                                          p_items              => :p1111_items,
                                          p_values             => l_bind_values
          END LOOP;
       END;
    END;I have tested this on APEX.ORACLE.COM and I am un-able to reproduce the same issue. It runs fine. This leads me to believe that I have a database setup issue. The problem is that I don’t know where or how to discover.
    Steps (for me) to reproduce:
    1- Create a REPORT QUERY which has a fair number of columns (say 50 – 60)
    2- Go through the wizard steps and finish
    3- Review the Query – Option n the right (under tasks) – click on “Export Report as XML”
    Result = session hangs creating a DB session which does not complete.
    Footprint:
    Application Express: 3.0.1.00.08
    Database: 10.2.0.1.0
    Connecting via a DAD connector from Oracle Application Server
    BI Publisher connection
    Suggestions are welcome.
    Many Thanks.
    --Tim                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Just for the off chance that someone else runs into this, I am going to try to brief my findings on the subject related to this issue...
    Previously, in the 3.0.1 version of APEX, our system would generate an OS process which would not terminate. Now in 3.1, it seems as though there is an error that is generated when this issue comes into play. I can, when attempting to get the sample XML from the REPORTS definition screen, generate this output when using the DOWNLOAD button:
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    SUMMARY
    TO RECREATE:
    1- CREATE a report with a lot of "columns wide" (about 50).
    2- Create a report using the GENERIC LAYOUT setting for REPORT LAYOUT
    3- RUN or get XML by using the DOWNLOAD or TEST REPORT buttons from the designer page Report Queries>Edit Report Query
    ISSUE: The generic layout has an issue in the code with size....
    PROBLEM: When creating a new report - XML is not available in order to create the required layout. Without a layout, XML will not generate. Standard chicken and egg syndrome.
    WORKAROUND: Create a DUMMY layout and assign it to the QUERY so that the proper XML output can be created.
    --Tim St. Hilaire                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • SSRS 2012 some users are not able to edit reports in the server

    Hello All,
    I am install reporting services SharePoint native mode but some users are not able to edit reports on server error is "Application cannot be started contact your application vendor" but this users edit reports on their client machine
    using report builder 3.0.
    Please help me

    Hi harshad_mule,
    Because Report Builder in the Report Manager is a ClickOnce application, the error message means that one or more of the files listed in the application manifest cannot be found on the server, so the application cannot be started. Based on my research, frequently
    this means that the application is somehow corrupted, or that the ClickOnce store is corrupted.
    To fix this issue, we can try to refer to the following steps:
    If Report Builder is corrupted, we can update the Reporting Services to repair this.
    Check that the Report Builder application is existing
        Open the Report Server folder. By default, the folder is located in: C:\Program Files\Microsoft SQL Server\MSSQL.<X>\Reporting Services\ReportServer\ReportBuilder
        Make sure the file "ReportBuilder.application" is existing in the folder mentioned above.
    If it is existing, please use the following URL to access the Report Builder directly:
    http://<server>/ReportServer/ReportBuilder/ReportBuilder.application
    And this issue can also be caused by browser. Because not all report functionality is supported by all browsers in Reporting Services. So please use IE browser to start Report Builder to try it again.
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • EPM Addin Compatibility - NW and MS Platforms

    Hello,
    We will have a cases where we should run on the same computer Excel which should connect to Netweaver and Microsoft 10.0 versions. Does someone has a expirience with that? Do you have any issues?
    Which option we should choose when we install EPM addin for Excel?

    Emiliyan, I found the answer from EPM Add-in installation guide.  See attachment.
    It says "
    The EPM Add-in installed is the same regardless of the solution you select. However, your selection determines the pre-configuration of the EPM Add-in."
    I think pre-configuration may mean when you create the connection, the default one should be the one you selected when you install epm add-in, but anyway, at least we know regardless what you selected, BPC MS or BPC NW or even BPC Embedded, it doesn't matter.

  • Stage Analysis Report Issue

    Hi,
    I have run a stage analysis report but it says no data inspite of open opportunities being present in the system. Could anyone kindly let me know what could be the issue?
    Regards
    Sharat

    Hi Sharat,
    Welcome you to the forum. Please close your first thread.
    Regarding your Stage Analysis Report Issue, what selection has been made? This report show closed opportunity only.
    Thanks,
    Gordon

  • GR/IR GL Reporting Issue

    1. 30 documents of 2009 were matching and post with clear is perfomred. After performing post with clear also the line items are not moving from open line items. When we download the open line items as of today, these line items are appearing.
    2. When we download the ZBLRFIOI report for GRIR a/c 349100 to have the opne line items. we have some set of documents showing as " FI Open items without J2" - This is reporting issues.
    Thanks
    Mallikarjuna

    Hi
    Pls try with F.13 for that GR/IR account 349100 by selecting check box select gl accounts
    And give Company code, year and pending document numbers in selection screen
    And before that pls make sure that OB74 clearing settings maintained or not
    It will clear all the open items exists
    Reg
    Vishnu

  • BW Reporting Issue

    Hi,
    I am facing one reporting Issue relating to Display Attributes.
    Characteristic: Business Partner
    Display Attributes: Address0, Address1, Address3...etc.
    Requirement is to display mentioned Display attributes along with Business Partner.
    For this I have selected Business Partner as characteristic and mentioned above three as display attributes to Business Partner.
    But Query out put is not showing Display attributes. For this I have done all settings at reporting level, all gone vain.
    I am using Bex 7.0.
    Kindly look in to the Issue and let me know the solution.
    Regards,
    Venkat.Mahipathi.
    09886652422.
    [email protected]

    Hi,
    Check in Reporting properties or check attributes in analyzer proprties then it will display  
    ************asign points if usefull***********
    swapna

  • 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?

  • Can't edit reports in Visual Studio

    <p>I can no longer edit reports in Visual Studio 2003. The reports open properly, but I can&#39;t make any changes. Right-clicking pops up the appropriate menus, but no dialog boxes open from the menu selections. Any ideas on what I can check?</p><p> Thanx</p>

    <p>I can think of two possibilities that I was given. </p><p>1. The install of VS has some how gone bad.  You could try a repair install of Visual Studio.</p><p>2. Opening reports outside of your application can cause problems with the designer.  Make sure you are inside your application before you open your reports.  </p><p>Rob Horne<br /><a href="/blog/10">Rob&#39;s blog - http://diamond.businessobjects.com/blog/10</a></p>

  • Query Print Layout Designer: no "save" option when editing report

    No "save" option when editing report, only "save as" in  2007 A PL30

    Yes you are all correct guys, but i'm aware that i can't edit the system report.
    What I did is i assigned a template for my query, then the system will automatically assign a template with the same name as my query. but the problem is when i open the layout, and make any changes, save button is not enabled, the system requires me to "save as". I dont encounter this problem in other version, but only in 2007a.

  • SAP Note 2111087 - enhancement to PM/QM list edit reports

    Hi,
    Has anyone experience of implementing the following SAP notes which appear to give enhanced functionality within commonly used PM/QM reports:-
    2111087 - Display of row count in list edit reports
    2079317 - Preparatory note for display of row count in list edit reports
    2079318 - Display of row count in PM list reports (SAP_APPL)
    2079384 - Display of row count in PM list reports (EA_APPL)
    2079386 - Display of row count in QM list reports (SAP_APPL)
    2079387 - Display of row count in QM list reports (EA_APPL)
    The above notes appear to enhance over 90 list edit reports within PM & QM and have been created from an improvement request within the EAM Customer Connect Cycle 3.
    No business functions need to be activated to use this function.
    Regards
    Gary B

    Hi Gary,
    I have implemented the note 2111087 and its related notes
      2079317
      2079318
      2079384
      2079386
      2079387
    as per the above notes the counter field is appearing in most of the transaction, which are listed in the Note 2079318 given by SAP.
    But still, the counter field does not appear in some of the transactions like IA08,IA09,IH06,IL05,IP15,IP16 and IP17.
    I have checked the dependent notes and searched for correction notes, but couldnt find any.
    Let me know if anyone has faced similar problem.
    Thanks in advance.
    Regards. Pavan

Maybe you are looking for