Error while creating billing document using VF04 transaction

Hi All,
User is trying to create billing document using VF04 with ference to delivery number. When pressing save in invoice creation system SAP gives invoice document number (No accouting document generated). but no documents are actually created. When user trying for second time log is showing this sales order is currently processed by the user(user is same who is trying to create invoice)
Please let us know what is causing this issue since this issue is happening in production and we can not debug this.
We checked for number range also but its not.
Waiting for your inputs.
Regards,
Jyothi CH.

When pressing save in invoice creation system
SAP gives invoice document number (No accouting document generated).
but no documents are actually created
Check there is any clash with internal number range of billing type vs other billing types ?
Try to create billing document using VF01,see any messages were poping while saving ?
Check for abap dump in ST22 ?
Edited by: Jeyakanthan A on Feb 9, 2011 9:52 PM

Similar Messages

  • Create Excise invoice(J1IIN) document while creating billing document using bapi BAPI_BILLINGDOC_CREATEMULTIPLE

    Dear Experts,
    My scenario is:
    We have batch split scenario, where the parent line item of billing document has 0 quantity and its subsequent item (item with batch number) holds actual quantity data.
    When we create billing document using VF01 against delivery document, system creates billing document along with excise invoice document (J1IIN Document). And in excise document contain same number of line items that of billing document. Please see the below attachment: 
    Biiling document screen shot:
    While creating billing document, the J1IIN Document created automatically. Below is the screen-shot for the same.
    Now the issue is:
    When we create billing document using BAPI: BAPI_BILLINGDOC_CREATEMULTIPLE system creating only billing document and not creating excise invoice document.
    When we create excise document manually using J1IIN the zero quantity line items are excluded in excise invoice document.
    Please see the below screen-shot for the same; The z quantity line items are missing.
    We want excise document to be created while creating billing document using BAPI BAPI_BILLINGDOC_CREATEMULTIPLE. Or is there any other BAPI for the same purpose.
    Customization is also maintained for creating excise invoice document automatically.
    Regards,
    Rajesh Sadula.

    HI
      Pricing will be carried basing on the pricing
    procedure.
    Case1: Prices will be carried out automatically if
    necessary condition records are maintained for the
    condition type.
      For this you can go to Sales Order-> Item Conditions
    In the screen you can click on command button Analysis,
    which gives you the list of condition types associated
    to the pricing procedure. By clicking on the condition
    type you can know the action that has taken place.
    Case2: Manually forcing prices for Items.
      To do this, you have to populate ORDER_CONDITIONS_IN &
    ORDER_CONDITIONS_INX. Also note to identify the item
    numbers, you manually pass the item number for each item
    in the sales order, use the same item number for
    populating conditions.
      Parameters required:
    ORDER_CONDITIONS_IN:
      ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
    ORDER_CONDITIONS_INX:
      ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
       Hope the above info helps you. Do revert back if you
    need more info.
    Kind Regards
    Eswar

  • Error while creating billing documents

    Hi,
      While creating billing documents I am getting error message as 
    Maintain customizing for excise and series group determination
    Message no. 8I619
    I have check the setting for CIN it is OK excise and series group are maintain properly so what can be the proble,
    regards,
    zafar

    Hi,
    Check once again customizing
    Maintain Series Group - In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents. Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
    - Define excise series groups based on type of outgoing document
    - Assign series group to excise registration ID
    - If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
    - If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' Iindicator. Example - You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
    - No account postings for CENVAT in sales cycle
    - No utilization Flag
    If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
    If the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
    Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
    If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
    Thanks
    Chidambaram

  • Error while creating Billing doc using VF01 for Debit memo req. from RRB

    Hi,
    I am creating billing doc for my Debit memo req. which is created using RRB(DP90, DP95).
    Error message - Item 000010 does not exist.
    When I debugged and looked into code it seems following lines are causing problem.
    Program
    LV60AA28
    Line u2013 734
      IF  vbap-vkgru EQ vkgru_dyn_posten.
        IF vbap-aufnr IS INITIAL .
    set AUBEL because it was overwritten by VBAP-VBELN
          vbrp-aubel = vbap-vgbel.
          vbrp-aupos = vbap-vgpos.
          vbrp-autyp = vbap-vgtyp.
    This code was not in 4.6 system.
    We have just migrating from 4.6 to 6.0 and facing this issue while testing.

    First of all you should try to learn how to express in a public forum like this. 
    On your comments
    Do some ground work from your end
    why should I ??  if you want you can do ground work or any work.  If you post a question, you have to hear patiently all suggestions and dont scribble whatever you want.
    You should have some basic
       understanding of SAP ABAP.
    You should have posted this question ABAP forum !!!!   Why without any sense you have posted in sales forum ??

  • Error while creating Billing Document in Tcode VF01

    Hi all,
    When i want to create a Billing document with single document number i'm able to move on to the overview of billing items.....for instance if 9000004568 is a document with 10 and 20 as items and when i try an create a billing document for the concern document with VF01 t-code its populating only one item in the overview of billing document screen....why is it sooo
    And most importantly when i give two documents like 9000004568 and 6700000000 in the first screen and process them to see the overview of this then it populates Information message 'Reference document 9000004568 000020 (Error during INSERT)' .This is for the second item of the corresponding document number ie item 20 and when processed with single document number it shows only one item number 10 in the preceding screen......Why this is happing...
    Thanks in Advance.

    Younis
    are you trying to create 1 single billing document?
    If yes, you need have to same payer, payment terms and invoice date.
    if you are planning to create separate billing documents, you need to make sure that "billing type" is same.
    let me know if you need more info.
    pl reward points if u find this info useful.
    thx
    ramesh

  • Error while creating Billing document

    Hi Gurus,
    Actually we are doing asset sale scenario. Asset sold from FI but for invoice and excise invoice we have to sell it from SD as well.
    So we created one material with standard material type for non valuated materials. we have created sales order and delivery but when we are doing billing system is giving the following error "Item category ZOR TAN cannot be invoiced with billing type ZF2"
    Please help me in solving this issue.
    Thank You

    Dear gverma
    Go to VTFL, select the combination of your delivery type and delivery type and see whether the item category TAN is maintained.  I feel it is missing and hence the error.
    thanks
    G. Lakshmipathi

  • Error while posting billing documents

    Hi,
    I am trying to post billing documents for accounting , but I am getting some error related to number range.
    I have checked number range assignments, where else I can check to find out error.
    Regards
    Nidhi

    If you are getting error while creating billing document -
    Check your number range status assignment in T-Code - VN01
    If any userexit is used then check in Userexit MV60AFZZ. There could be a Z-table where the number range may not be properly defined for the Billing Type/ plsnt/etc. as per the settings.
    If Billing document is created and you get this error while posting-
    Then it would be error with the number range for Accounting Document. Pls. ask the FI person to fix this.
    If the above does not solve - pls. mention the exact error with error code.
    Thanks

  • Error while creating delivary document

    Hi
    i got error while creating delivary document
    "Delevivary documents could not be created"
    Thanks&regards
    kishore kumar

    Hi Kishore,
    Please check the sales order is this relevent for the delivery or not.
    Check the copy control settings between your sales document type and delivery document type in VTLA transaction.
    Check the incompletion log for the sales order.
    I hope it will help you,
    Regards,
    Murali.

  • Heap space error while creating XML document from Resultset

    I am getting Heap space error while creating XML document from Resultset.
    It was working fine from small result set object but when the size of resultset was more than 25,000, heap space error
    I am already using -Xms32m -Xmx1024m
    Is there a way to directly write to xml file from resultset instead of creating the whole document first and then writing it to file? Code examples please?
    here is my code:
    stmt = conn.prepareStatement(sql);
    result = stmt.executeQuery();
    result.setFetchSize(999);
    Document doc = JDBCUtil.toDocument(result, Application.BANK_ID, interfaceType, Application.VERSION);
    JDBCUtil.write(doc, fileName);
    public static Document toDocument(ResultSet rs, String bankId, String interfaceFileType, String version)
        throws ParserConfigurationException, SQLException {
            DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = factory.newDocumentBuilder();
            Document doc = builder.newDocument();
            Element results = doc.createElement("sims");
            results.setAttribute("bank", bankId);
            results.setAttribute("record_type", "HEADER");
            results.setAttribute("file_type", interfaceFileType);
            results.setAttribute("version", version);
            doc.appendChild(results);
            ResultSetMetaData rsmd = rs.getMetaData();
            int colCount = rsmd.getColumnCount();
            String columnName="";
            Object value;
            while (rs.next()) {
                Element row = doc.createElement("rec");
                results.appendChild(row);
                for (int i = 1; i <= colCount; i++) {
                    columnName = rsmd.getColumnLabel(i);
                    value = rs.getObject(i);
                    Element node = doc.createElement(columnName);
                    if(value != null)
                        node.appendChild(doc.createTextNode(value.toString()));
                    else
                        node.appendChild(doc.createTextNode(""));
                    row.appendChild(node);
            return doc;
    public static void write(Document document, String filename) {
            //long start = System.currentTimeMillis();
            // lets write to a file
            OutputFormat format = new OutputFormat(document); // Serialize DOM
            format.setIndent(2);
            format.setLineSeparator(System.getProperty("line.separator"));
            format.setLineWidth(80);
            try {
                FileWriter writer = new FileWriter(filename);
                BufferedWriter buf = new BufferedWriter(writer);
                XMLSerializer FileSerial = new XMLSerializer(writer, format);
                FileSerial.asDOMSerializer(); // As a DOM Serializer
                FileSerial.serialize(document);
                writer.close();
            } catch (IOException ioe) {
                ioe.printStackTrace();
            //long end = System.currentTimeMillis();
            //System.err.println("W3C File write time :" + (end - start) + "  " + filename);
        }

    you can increase your heap size..... try setting this as your environment variable.....
    variable: JAVA_OPTS
    value: -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m

  • Changing billing document date while creating billing document from vf01

    Hi gurus,
    I have requirement to change billing doc date while creating billing document from VF01.
    here I have to consider goods issue date eq billing date.
    caluculating billing date = Goods Issue + Goods in Transit duration time.
    I have done everu thing but I cant update the caluculated date, iam using the following enhancement
    Enhancement:SDVFX001
    Function Module:EXIT_SAPLV60B_001
    Include:ZXVVFU01 which are part vf01.
    here iam sending the calculated date to VBRK-FKDAT
    move cal_date to vbrk-fkdat.
    need help how to update the calculated date to VBRK-fkdat i.e billing document date
    Regards
    Bhaskar

    Hi
    No! That exit is not good for your issue
    U can use the user-exit USEREXIT_NUMBER_RANGE_INV_DATE  defined in RV60AFZC
    Max

  • Change in document type while creating billing document from sales order

    While creating billing document from Sales order it is creating with document type RV which is standerd one but i want to change Document type.
    How can i change it?
    Regards
    Raj

    Hi
    If you use another existing document type, check that it has a number range suitable to you.  Else create a new 'z' type and assign an entirely new number range, not used in the other doc types.
    It is useful to make the FI document number the same number.  If I understand from the forums, the FI number range must be external.  Search the forum for this.  It is very useful for the Finance people.
    Kind regards
    Dawn
    Edited by: Dawn Verrell on Sep 9, 2010 4:10 PM

  • Error while creating resource group using non-globalzones.

    Dear all,
    Hi techs please guide me how to create failover resource group in nongloablzones.
    I'm getting error while creating resource group using non-globalzones.
    My setup:
    I have two node cluster running sun cluster 3.2 configured and running properly.
    node1: sun5
    nide2: sun8
    I have create non-globalzone "zone1" in node:sun5
    I have create non-globalzone "zone2" in node:sun8
    node:sun5# clrg create -n sun5:zone1,sun8:zone2 zonerg
    *(C160082) WARNING: one or more zones in the node list have never been fully booted in the cluster mode,verify that correct zone name was entered.*
    kindly guide me how to create Apache resource group using non-glabalzones, i'm new to sun cluster 3.2. please guide me step by step information.
    Thanks in advance,
    veera
    Edited by: veeraa on Dec 19, 2008 1:54 AM

    Hi Veera,
    Actually you are getting a warning message where one of two things could have happened. Either you specified an incorrect zone name or one of the zones has not been fully booted. It's likely that you haven't booted the zones, so please follow this:
    zoneadm list -iv
    If zone1 or zone2 are not running then boot and configure them
    zoneadm -z <zone> boot
    zlogin -C <zone>
    After that you can continue to follow the step by step instructions at
    http://docs.sun.com/app/docs/doc/819-2975/chddadaa?a=view
    These may also help
    http://blogs.sun.com/Jacky/entry/a_simple_expample_about_how
    http://blogs.sun.com/SC/en_US/entry/sun_cluster_and_solaris_zones
    Regards
    Neil

  • Error while creating logical file using transaction FILE

    Hello there,
    I am facing an error while creating Logical File name definition using transaction FILE
    This is the input which I'm trying to give
    Logical file name: ZTEST
    Name : ZTEST
    Physical file : ZTEST_1<DATE><TIME>.csv
    Data format: ASC
    Application area: BW
    Logical path:ZTEST_1_DATAOUT
    when I tried to save it throws me an error like  ASSIGN_SUBSTRING_NOT_ALLOWED
    Please help.

    Hi,
    Please check the OSS Notes :
    Note 792061 - SP Case Locator: Dump: ASSIGN to a substring isn't allowed.
    SAP Note 1297989 - Short dump ASSIGN_SUBSTRING_NOT_ALLOWED
    Hope this solves the problem.
    -Vikram

  • 'update was terminated' while creating billing document VF01

    Hi all,
             i need a solution urgently ..except for paticular document no all documents that i post using VF01 create successfully document no.
    but for a paticular document no(may be it is of some type that i am unable to) while creaing billing document no it gives a message 'document created successfully' ,but when i try to click any button after that e.g BACK it shows a messge 'Update was terminated  for author ....' in my inbox. and vf03 shows the documentdoesn't exist.
    in st22 i checked one dump . when i gave a break point at that point the cursor never reached the code.
    I also checked SM13 and it showed all fms as init. and one fm 'RV_MESSAGE_UPDATE ' as error . i aws unable find the fm in the main program .
    one more thing when i create bill document for other document type it shows messge 'Document saved ....(no accounting document created)' but for this one i am getting messge 'document saved.......' .
    I asked one collegue he told me might be some OSS notes required for it . i am working on a unicoded system ECC 6.0  version.but he is not sure .
    Has any body faced the same problem..and what was the soln....if oss notes are required than how could i find it..and what was the no...........
    THANKS IN ADVANCE ...................

    THANKS  for the reply.
    i am new to sap .can u tell me in detail where actually i can check for number range of the document . one more when i checked the sm13 and  started debugging it gave me for a certain character set  (may be in chineses) present in the table ,the transfer command gives a dump. now the problem is it is too long 132 and don't no forwhich character it gives an  dump.how can i check the characters maintained in the system. it gives a dump   CX_SY_CONVERSION_CODEPAGE   ,At the conversion of a text from codepage '4102' to codepage '4110':      
    i am not sure this causes the mesages 'Updation was terminated' . what u people think.
    thanks ..

  • Error while creating new crosstab using

    I am getting the following error while creating a new crosstab object within Swing application. This error has started coming after we applied Oracle patch 9206 on database. The error originates from one of the classes in the olap_api_92.jar.
    ==========================================================
    Wed Feb 02 09:13:51 CST 2005 In BuilderWizardValidateAdapter::wizardValidatePage
    oracle.express.idl.util.OlapiException: No more data to read from socket
         at oracle.express.idl.ExpressOlapiDataSourceModule.DefinitionManagerInterfaceStub.crtCurMgrs2(DefinitionManagerInterfaceStub.java:927)
         at oracle.express.olapi.data.full.DefinitionManagerSince9202.createOLAPICursorManagers(DefinitionManagerSince9202.java:611)
         at oracle.express.olapi.data.full.ExpressDataProvider.createCursorManagers(ExpressDataProvider.java:1325)
    =========================================================
    Please check the BIcheckconfig output. It does not show any errors.
    =========================================================
    <?xml version="1.0" encoding="UTF-8" ?>
    <BICheckConfig version="1.0.2.0">
    <Check key="JDEV_ORACLE_HOME" value="C:\Mohan\Installs\Jdev904"/>
    <Check key="JAVA_HOME" value="C:\Mohan\Installs\Jdev904\jdk"/>
    <Check key="JDeveloper version" value="9.0.4.0.1419"/>
    <Check key="BI Beans release description" value="BI Beans 9.0.4 Production Release"/>
    <Check key="BI Beans component number" value="9.0.4.23.0"/>
    <Check key="BI Beans internal version" value="2.7.5.32"/>
    <Check key="host" value="db03schgefage"/>
    <Check key="port" value="1521"/>
    <Check key="sid" value="biolapp"/>
    <Check key="user" value="nairs5"/>
    <Check key="Connecting to the database" value="Successful"/>
    <Check key="JDBC driver version" value="9.2.0.4.0"/>
    <Check key="JDBC JAR file location" value="C:\Mohan\Installs\Jdev904\jdev\lib\patches"/>
    <Check key="Database version" value="9.2.0.6.0"/>
    <Check key="OLAP Catalog version" value="9.2.0.6.0"/>
    <Check key="OLAP AW Engine version" value="9.2.0.6.0"/>
    <Check key="OLAP API Server version" value="9.2.0.6.0"/>
    <Check key="BI Beans Catalog version" value="N/A; not installed in nairs5"/>
    <Check key="OLAP API JAR file version" value="9.2"/>
    <Check key="OLAP API JAR file location" value="C:\Mohan\Installs\Jdev904\jdev\lib\ext"/>
    <Check key="OLAP API Metadata Load" value="Successful"/>
    <Check key="Number of metadata folders" value="3"/>
    <Check key="Number of metadata measures" value="569"/>
    <Check key="Number of metadata dimensions" value="5"/>
    <Check key="OLAP API Metadata">
    <![CDATA[==============================================================================
    Type Name (S=Schema, C=Cube, M=Measure, D=Dimension)
    ========= ====================================================================
    Folder... ROOT
    Folder... Auto Claim Measures
    Folder... Service Measures
    Folder... Claim Counts
    Folder... Cell Summary Cube
    Folder... Actual Measures
    Measure.. Actual Acceptance Rate
    Measure.. Actual Annualized Bill amt
    Measure.. Actual Application Count
    Measure.. Actual Avg Annual Billing
    Measure.. Actual Contacts Count
    Measure.. Actual Commission Amt
         at oracle.express.olapi.data.full.ExpressDataProvider.internalCreateCursorManager(ExpressDataProvider.java:680)
         at oracle.express.olapi.data.full.ExpressDataProvider.createCursorManager(ExpressDataProvider.java:586)
         at oracle.olapi.data.source.DataProvider.createCursorManager(DataProvider.java:268)
         at oracle.dss.dataSource.QueryUtilities.setUpCursors(QueryUtilities.java:559)
         at oracle.dss.dataSource.QueryServer._setUpCursorsForMainQuery(QueryServer.java:7039)
         at oracle.dss.dataSource.QueryServer._getCursorForCube(QueryServer.java:4098)
         at oracle.dss.dataSource.QueryServer._updateCube(QueryServer.java:4055)
         at oracle.dss.dataSource.QueryServer._applySelections(QueryServer.java:2661)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at oracle.dss.util.Operation.execute(Operation.java:69)
         at oracle.dss.dataSource.OperationQueue.update(OperationQueue.java:68)
         at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:176)
         at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:146)
         at oracle.dss.dataSource.QueryServer.queueOperation(QueryServer.java:7076)
         at oracle.dss.dataSource.QueryServer.applySelection(QueryServer.java:2192)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at oracle.dss.util.Operation.execute(Operation.java:69)
         at oracle.dss.dataSource.QueryManagerServer.sendQueue(QueryManagerServer.java:1549)
         at oracle.dss.dataSource.common.OperationQueue.update(OperationQueue.java:198)
         at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:176)
         at oracle.dss.dataSource.common.BaseOperationQueue.addOperation(BaseOperationQueue.java:146)
         at oracle.dss.dataSource.common.OperationQueue.addOperation(OperationQueue.java:127)
         at oracle.dss.dataSource.client.QueryClient.applySelection(QueryClient.java:970)
         at oracle.dss.dataSource.common.QueryQueryAccess$SelCursor.getDataAccess(QueryQueryAccess.java:1133)
         at oracle.dss.dataSource.common.QueryQueryAccess.getDataAccess(QueryQueryAccess.java:278)
         at oracle.dss.datautil.QueryAccessUtilities._getValues(QueryAccessUtilities.java:639)
         at oracle.dss.datautil.QueryAccessUtilities._getValues(QueryAccessUtilities.java:705)
         at oracle.dss.datautil.QueryAccessUtilities.getValues(QueryAccessUtilities.java:608)
         at oracle.dss.queryBuilder.QueryBuilderUtils.getSelectedMeasures(QueryBuilderUtils.java:623)
         at oracle.dss.queryBuilder.SelectedItemsPanel.populateTree(SelectedItemsPanel.java:298)
         at oracle.dss.queryBuilder.SelectedItemsPanel.refreshTree(SelectedItemsPanel.java:333)
         at oracle.dss.queryBuilder.SelectedItemsPanel.setActive(SelectedItemsPanel.java:366)
         at oracle.dss.queryBuilder.ItemsPanel.setActive(ItemsPanel.java:251)
         at oracle.dss.datautil.gui.DefaultBuilderDialog.setActive(DefaultBuilderDialog.java:1072)
         at oracle.dss.datautil.gui.DefaultBuilderDialog.validateNextPreviousEvent(DefaultBuilderDialog.java:1396)
         at oracle.dss.datautil.gui.DefaultBuilderDialog$BuilderWizardValidateAdapter.wizardValidatePage(DefaultBuilderDialog.java:2113)
         at oracle.bali.ewt.wizard.WizardPage.processWizardValidateEvent(Unknown Source)
         at oracle.bali.ewt.wizard.WizardPage.validatePage(Unknown Source)
         at oracle.dss.datautil.gui.CustomImageWizardPage.validatePage(CustomImageWizardPage.java:81)
         at oracle.bali.ewt.wizard.BaseWizard.validateSelectedPage(Unknown Source)
         at oracle.bali.ewt.wizard.BaseWizard.doNext(Unknown Source)
         at oracle.dss.datautil.gui.CustomWizard.doNext(CustomWizard.java:415)
         at oracle.bali.ewt.wizard.BaseWizard$Action.actionPerformed(Unknown Source)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
         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:245)
         at java.awt.Component.processMouseEvent(Component.java:5100)
         at java.awt.Component.processEvent(Component.java:4897)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
         at java.awt.Container.dispatchEventImpl(Container.java:1613)
         at java.awt.Window.dispatchEventImpl(Window.java:1606)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:141)
         at java.awt.Dialog$1.run(Dialog.java:540)
         at java.awt.Dialog.show(Dialog.java:561)
         at java.awt.Component.show(Component.java:1133)
         at java.awt.Component.setVisible(Component.java:1088)
         at oracle.bali.ewt.wizard.WizardDialog.runDialog(Unknown Source)
         at oracle.dss.datautil.gui.DefaultBuilderDialog.runDialog(DefaultBuilderDialog.java:489)
         at oracle.dss.datautil.gui.DefaultBuilderDialog.run(DefaultBuilderDialog.java:466)
         at oracle.dss.queryBuilder.QueryBuilder.run(QueryBuilder.java:2401)
         at gecf.pmg.PmgBiOlapApp.newCrosstabWiz(PmgBiOlapApp.java:1622)
         at gecf.pmg.PmgBiOlapApp.mNewCrosstab_ActionPerformed(PmgBiOlapApp.java:1563)
         at gecf.pmg.PmgBiOlapApp$5.actionPerformed(PmgBiOlapApp.java:696)
         at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786)
         at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839)
         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:245)
         at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
         at java.awt.Component.processMouseEvent(Component.java:5100)
         at java.awt.Component.processEvent(Component.java:4897)
         at java.awt.Container.processEvent(Container.java:1569)
         at java.awt.Component.dispatchEventImpl(Component.java:3615)
         at java.awt.Container.dispatchEventImpl(Container.java:1627)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483)
         at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128)
         at java.awt.Container.dispatchEventImpl(Container.java:1613)
         at java.awt.Window.dispatchEventImpl(Window.java:1606)
         at java.awt.Component.dispatchEvent(Component.java:3477)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:456)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)

    I suspect that you have either not fully applied the patch or alternatively the patching process did not complete.
    If you are using an analytic workspace, connect as OLAPSYS account and run the following commands:
    exec CWM2_OLAP_METADATA_REFRESH.MR_REFRESH
    exec CWM2_OLAP_METADATA_REFRESH.MR_AC_REFRESH
    If this does not resolve the error, and assuming your system worked prior to applying the 9206 patch, then the patch may need to be reapplied.
    Hope this helps
    Business Intelligence Beans Product Management Team
    Oracle Corporation

Maybe you are looking for