E1P transaction FBL5N default date

Hi specialists
ok, this seems a stupid question even to me...but I have forgotten this. When opening FBL5N
in dynamic values there is a date selection. What do I have to do to keep this value always
as a current date; so when I save this as a variant and I open it again I want date to be always as a current date.
Hope you understood what i ment..
thanks in advance...

Gordon,
They will change the date once or twice per day.
If formatted search is the only way to go then I shall do that !
Thanks !
Yves B.

Similar Messages

  • Updating the database by the transaction SU01 defaults data

    Hi All,
    Is there any Function Module, or method , or any other way to update the database when i change the data of defaults ( tab )
    Log on data like time format, date format and decimal notation.
    Regards,
    Lakshmi.

    you can use the BAPI
    BAPI_USER_CHANGE

  • Text in Transaction FBL5N gets overwritten

    Hello expert,
    When text has been entered in field BSEG-SGTXT in transaction FBL5N, this text is overwritten with the reason code description when I enter a reason code.
    I entered the reason code in transaction FBL5N- Additional data - field BSEG-RSTGR.
    How can I prevent that the original text is overwritten?
    I want to keep both texts.
    Thank you to help me out.
    Kind regards,
    Linda

    How can I prevent that the original text is overwritten? - Follow path below and activate the check box 'Do not copy text ' for that reason code.
    Financial Accounting > Accounts Receivable and Accounts Payable>Incoming Payments>Incoming Payments Global Settings>Overpayment/Underpayment>Define Reason Codes.

  • BADI or Exits for Transaction FBL5N

    HI All,
    I want any BADI or Exits for transaction FBL5N.
    Please help me out asap.
    <<Text removed>>
    Thanks in advance.
    Regards,
    Seevangi
    Edited by: Matt on Jan 13, 2009 11:25 AM - do not offer points

    hi,
    There is one user exit available for this Transaction code:
    F1040001  Reserve for bad debt - calculate percentages
    BADI'S,
    Below Badis are available for the Tcode.
                                                                                    FI_ITEMS_MENUE01     Menu Enhancement                                            
    FI_ITEMS_MENUE02     Menu Enhancement                                            
    FI_TAX_BADI_015      RFUMSV00: Event "END-OF-SELECTION" before Data File Creation
    FI_TAX_BADI_016      RFUMSV00: Transfer of All Tax Data                                                                               
    if you require more details let me.
    regards,
    Dwaraka.

  • Data S Default data transfer Options

    Hi
    What do the below mentioned terms mean in infopackage-Schedular--Data S Default data transfer
    1Max size of datapakcet in kbytes
    2Max no of dailogues process for sending data
    3No of data packet per info idoc
    Please help me with an example and what importance it has when we increase/ decrease the lengh of the above 3 mentioned do we have any interconnection in all three or they are all independent.
    Thanks
    Puneet

    Hello Puneet,
    These are some standard BW Settings done in transaction SPRO.
    SPRO ->SAP Customizing Implementation Guide->SAP NetWeaver->SAP Business Information Warehouse->Links to Other Systems->Maintain Control Parameters for the data transfer
    Maximum size of a data packet in kilo bytes.
    The individual records are sent in packages of varying sizes in the data transfer to the Business Information Warehouse. Using these parameters you determine the maximum size of such a package and therefore how much of the main memory may be used for the creation of the data package.
    SAP recommends a data package size between 10 and 50 MB.
    Frequency with which status Idocs are sent
    With this frequency you establish how many data IDocs should be sent in an Info IDoc.
    Maintain Control Parameters for the data transfer
    Standard settings
    For SAP source systems, you change the control parameter settings in the transaction SBIW (Customizing for Extractors), under Business Information Warehouse -> General Settings -> Control Parameters -> Maintain Control Parameters for Data Transfer .
    Activities
    1. Maximum size of data packages
    For data transfer into BW, the individual data records are sent in packages of variable size. You use these parameters to control how large such a data package typically is. If no entry is maintained, the data is transferred with a standard setting of 10,000 kbytes per data package. The memory requirement depends not only on the setting for data package size, but also on the width of the transfer structure, and the memory requirement of the  relevant extractor.
    2. Frequency
    With the specified frequency, you detemine after how many data IDocs an Info IDoc is sent, or how many data IDocs are described by an Info IDoc.
    The frequency is set to 1 by default. This means that an Info IDoc follows every data IDoc. Generally, choose a frequency of between 5 and 10, but not greater than 20.
    The larger the package size of a data IDoc, the lower you must set the frequency. In this way you ensure that, when loading data, you receive information on the current data load status at relatively short intervals.
    In the BW Monitor you can use each Info IDoc to see whether the loading process is running without errors. If this is the case for all the data IDocs in an Info IDoc, then the traffic light in the Monitor is green. One of the things the Info IDocs contain information on, is whether the current data IDocs have been loaded correctly.
    3. Size of a PSA partition
    Here, you can set the number of records at which a new partition is generated. This value is set to 1.000.000 records as standard.
    When you are integrating with Other SAP Components then
    SPRO ->SAP Customizing Implementation Guide->Integration with Other SAP Components->Data Transfer to the SAP Business Information Warehouse->General Settings->Maintain Control Parameters for the data transfer
    Maintain Control Parameters for Data Transfer
    Activities
    1. Source System
    Enter the logical system of your source client and assign the control parameters you selected to it.
    You can find further information on the source client in the source system by choosing the path Tools -> Administration -> Management -> Client Maintenance.
    2. Maximum Size of the Data Package
    When you transfer data into BW, the individual data records are sent in packages of variable size. You can use these parameters to control how large a typical data packet like this is.
    If no entry was maintained then the data is transferred with a default setting of 10,000 kBytes per data packet. The memory requirement not only depends on the settings of the data package, but also on the size of the transfer structure and the memory requirement of the relevant extractor.
    3. Maximum Number of Rows in a Data Package
    With large data packages, the memory requirement mainly depends on the number of data recrods that are transferred with this package. Using this parameter you control the maximum number of data records that the data package should contain.
    By default a maximum of 100,000 records are transferred per  data package.
    The maximum main memory requiremen per data package is approximately 2'Max. Rows'1000 Byte.
    4. Frequency
    The specified frequency determines the number of IDocs that an Info IDoc is to be sent to, or how many data IDocs an Info Idoc describes.
    Frequency 1 is set by default.. This means that an Info Idoc follows every data Idoc. In general, you should select a frequency between 5 and 10 but no higher than 20.
    The bigger the data IDoc packet, the lower the frequency setting should be. In this way, when you upload you can obtain information on the respective data loading in relatively short spans of time .
    With the help of every Info IDoc, you can check the BW monitor to see if there are any errors in the loading process. If there are none, then the traffic light in the monitor will be green. The Info IDocs contain information such as whether the respective data IDocs were uploaded correctly.
    5. Maximum number of parallel processes for the data transfer
    An entry in this field is only relevant from release 3.1I onwards.
    Enter a number larger than 0. The maximum number of parallel processes is set by default at 2. The ideal parameter selection depends on the configuration of the application server, which you use for transferring data.
    6. Background job target system
    Enter the name of the application server on which the extraction job is to be processed.
    To determine the name of the application server, choose Tools -> Administration -> Monitor -> System monitoring -> Server. The name of the application server is displayed in the column Computer.
    7. Maximum Number of Data Packages in a Delta Request
    With this parameter, you can restrict the number of data packages in a delta request or in the repetition of a delta request.
    Only use this restriction when you expect delta requests with a very high data volume, so that, despite sufficiently large data package sizes, more than 1000 data packages can result in a request.
    With an initial value or when the value is 0, there is no restriction. Only a value larger than 0 leads to a restriction in the number of data packages. For reasons of consistency, this number is not generally exactly adhered to. The actual restriction can, depending on how much the data is compressed in the qRFC queue , deviate from the given limit by up to 100.
    Thanks
    Chandran

  • Getting the Transaction/Transaction Code Usage data

    Hello, I wonder if anyone could help me?
    The requirement given by the client calls for a report that displays the usage of a transaction code, specifically the following:
    1. given the transaction code, the date/time it was last used and the user who used it;
    2. given a key date (default current), the list of transaction codes used in the last three months, the user who last used it, also with date and time.
    I have looked at the tcode ST03, but it only gives me the list of transaction codes and users who accessed the transaction code.  I need the access date and time in order to meet the requirement.
    Thanks in advance. Ü

    chk this from other thread
    also chk the structure   MYLIST for the required informatiuon
    report abc.
    DATA : MYLIST LIKE UINFO OCCURS 0 WITH HEADER LINE.
    PARAMETERS : TCODE LIKE TSTC-TCODE.
    CALL FUNCTION 'TH_USER_LIST'
    TABLES
    LIST = MYLIST.
    LOOP AT MYLIST WHERE TCODE = TCODE.
    WRITE : / MYLIST-BNAME , MYLIST-TCODE.
    ENDLOOP.

  • Fbl5n default screen?

    Subject: FW: FLB5N - DEFAULT SCREEN
    Please assist with the query as per below.  This will not require a service request as it is just for clarification purposes only.
    What is required to have the following screen as my default screen (layout) for Tcode  FBL5N.  When using T-code FBL5N today the default layout had changed and the screen was blank.  This now happens every time this t-code is used.  When the layout is changed and saved there does not seem to be a way to make the saved layout become the default layout

    Dear Kishore,
    Execute the transaction FBL5n and then go to Settings > Layout > Administration......
    Here select the layout which you want as default and then go to "EDIT" and "Define default settings"
    Assign points if useful
    regards
    Venkatesh
    Edited by: Venkatesh A K on Apr 16, 2008 9:12 AM

  • Return default data if no data is returned by sql query

    Hi,
    I have a requirement.
    I have an inner query that returns no data. However I still want to return default data (say 'abc'). The below sql does not return anything inspite of using nvl . Please advise .
    select nvl( x.vencode,'abc') vencode
    from
    -- below sql returns no data!
              SELECT a.vencode vencode,
                     a.mid mid,
                     a.title title,
                      ROW_NUMBER() OVER (PARTITION BY a.vencode ORDER BY a.title) rnk
               FROM (
                     SELECT *
                     FROM    (SELECT vencode FROM vendor where login is not null and vencode = 'BKFI'
                                        and login > (sysdate - 90) )
                          CROSS JOIN
                             (SELECT mid, title, ROWNUM num FROM tcommmemos where mid is not null)
                    ) a,        
                   (SELECT * FROM (
                    SELECT v.vencode, tc.mid, tc.title
               FROM
               (select  * from vendor
                     where login is not null and vencode = 'BKFI'
                     and login > (sysdate - 90)) v,
                tcommmemosviewed tcv, tcommmemos tc
               WHERE     v.vencode = tcv.vencode
                     and tc.mid is not null
                     --AND tc.post_date > v.hiredate
                     AND tc.mid = tcv.mid)
                   ) b
                   where a.vencode = b.vencode(+)
                     and a.title   = b.title(+)
                     and a.mid     = b.mid(+)
                     and b.mid is null                               
    ) x              

    Use any aggregate function it'll always return a value even if there no data in the table
    create table r_dummy_1 (a number);
    SQL> select * from r_dummy_1;
    no rows selected
    SQL> select nvl(max(a),1) from r_dummy_1;
    NVL(MAX(A),1)
    1

  • How to change the default date in Person assignment tab?

    Hi experts,
    Does anyone know how to change the default date in person assignment tab in cj20n? Currently, the system always take the scheduled finish date to the date of the person assignment tab. Can I change it to the start date?
    Thanks and rgs,
    Michelle

    Hi Michelle,
    Goto SPRO->Project system->Dates->Scheduling->Specify Parameters for Network Scheduling, Here you can control the workforce planning dates.
    Hope this is useful...
    Regards
    Aatish

  • How to change default Date format in BO 6.5 SP4

    A problem with date display has been reported to me by one of our users -  in BO 6.5 - since installing SP4.
    The default date format is now MM/DD/YYYY
    I have tried to recreate this on my PC and have been able to confirm that this is the case.
    Most of our PC's will have two versions of Business Objects on them - for 5.1.6 and for 6.5 - that is the case for my PC.
    If I create a new BO document based on a spreadsheet with three entries in the spreadsheet as follows:-
    20/01/2009    20-Jan-2009  20th January 2009
    This displays in BO 6.5 as
    1/20/2009   1/20/2009    20th January 2009
    My PC regional setting is UK and the time displays DD/MM/YYYY
    Can you advise how to correct this problem please.

    Hi Sebastien
    Thank you for your response.
    I haven't checked Dimension in universe because this is happening even when datasource is an Excel spreadheet - as per details in previous post.
    I have looked for *.sbo files and found one for ODBC.sbo in the Version 5 folders on PC - with date format details in it which I've changed - that doesn't make any difference.
    Any other ideas?
    Regards
    Linda

  • Problem with customer open items. Transaction FBL5N and F-30

    Hi all,
    I have a little problem with a customer.
    When I see transaction FBL5N, I can see 3 open items, but, when I go to clear then in F-30, no appears.
    Anybody can help me.
    Thanks in advance

    Hi all,
    I have solved the problem
    The problem was that exits a proposal where these open items were.
    I have  deleted this proposal, and then, I could create a post with clearing.
    Thanks everybody

  • How to get the default date as current date in input filed in VC

    Hi
    In my VC application i have two date fields. we are allowing the end user to select the From Data and Todate though Data pickers, But the client asking to make the today's date as default date in Todate field , rather picking up from the data picker,
    Unless the  user wants change the todate from the current date. It should display today's date as default date.
    can any body tell me how to do it.
    Regards
    Vijay

    Hi All,
    I have an issue an implementing the "Exporting the Table data to Excel."
    My VC version is 7.0
    Portal version NW 2004s.
    By refering the following link, i have implemented Export To Excell functionality in VC.
    2) Another one that's in the Visual Composer WIKI:
    https://wiki.sdn.sap.com/wiki/display/VC/Exportingdatafrom+VC
    By refering to 7th page in the document. It is explained to add the data source object from the 'info' port and add the field called 'RAPTNAME'to the DATA source object.
    But the RFC object which i added to the story board, i havent find any 'info' port in my added RFC. But still i have added the data store object and added field. then
    copied the following given formula in the document in respective formula window ,Formula showin as valid. when i click on check button.
    copied formula :
    "pcd!3aportal_content!2fcom.sap.pct!2fplatform_a
    dd_ons!2fcom.sap.ip.bi!2fiViews!2fcom.sap.ip.bi.b
    ex?QUERY=" & STORE@REPTNAME &
    "&BI_COMMAND_1-
    BI_COMMAND_TYPE=EXPORT&BI_COMMAND
    1-EXPORTFORMAT=XLS&BI_COMMAND_1-
    null="
    i am able to run the application. After i run the application . once i click on the button 'ExportToExcel' i am getting the following error.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView : N/A
    Component Name : N/A
    Could not find portal application com.sap.ip.bi.service.generic.
    Exception id: 05:32_01/05/07_0001_18800950
    See the details for the exception ID in the log file
    Can u please tell me what is the problem
    Regards
    Vijay

  • How to give specific default date with expression in SSRS

    Hi,
    I have to pass some specific kind of dates in "Default Values" section of parameter.
    1st is whenever SSRS report run for any year in default date I want to pass value 1/1/(Current Year), for this I tried many way like , = "1/1/" + DatePart("Y",Now())  also = "1/1/" + Year(Now()) but it
    is giving me error. When I tried both part individually "1/1/" and  DatePart("Y",Now()) , it is working but when I join them with + sign it is giving me error that "input string is not in correct format"
    2nd I want to set up like when package run in month of April, it takes default date as "(Previous Month, which is May)/1/(current Year)" so if I am running report on 4/5/2013 then it in default date it should take 3/1/2013.
    Please help me with the expression. Thanks in advance. 
    Vicky

    Hi Visakh,
    Thanks again.
    I have one more question, I also have start date and end date. In start date I can put your expression as you gave me as below,
    =DateAdd(DateInterval.Month,DateDiff(DateInterval.Month,CDate("01/01/1900"),Now())-1,CDate("01/01/1900"))
    But can you please help me with End date expression?
    In End date I want to put previous month's last date. For example, if active batch is running package on
    12/16/2013 then for End Date parameter it should value "11/30/2013" 
    For  1/16/2014 then for End Date parameter it should value "12/31/2013" 
    For  3/16/2013 then for End Date parameter it should value "2/28/2013" 
    Thanks for your help in advance.
    Vicky

  • Default data adaptor error when deploying a war file in weblogic

    Hi All,
    Newbie here with a few questions regarding the deployment of OPA 10.1. Really hoping you guys can help...
    1) I'm attempting to deploy an unexploded web-determinations.war file on WebLogic. Thanks to this forum I've got past the issues of "rulebase directory not found" etc. However, i'm now faced with an issue which I can't find any info on. Please see below.
    3672074 [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN com.or
    acle.determinations.web.platform.controller.actions.StartSessionAction - Could not instansate defau
    lt data adaptor
    java.lang.NullPointerException
    at java.io.File.<init>(File.java:194)
    at com.oracle.determinations.web.platform.plugins.data.XDSDataAdaptor.<init>(XDSDataAdaptor.
    java:55)
    at com.oracle.determinations.web.platform.controller.actions.StartSessionAction.createInterv
    iewSession(StartSessionAction.java:173)
    at com.oracle.determinations.web.platform.controller.actions.StartSessionAction.getResource(
    StartSessionAction.java:66)
    at com.oracle.determinations.web.platform.servlet.WebDeterminationsServlet.doGet(WebDetermin
    ationsServlet.java:67)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.
    java:226)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at com.oracle.determinations.web.platform.util.CharsetFilter.doFilter(CharsetFilter.java:46)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
    ontext.java:3393)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2
    140)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    I've got the following entry in the application.properties file too...
    # Default XDS data adaptor file path
    #xds.file.path =data
    From what we can see we believe the code is getting a null pointer because of the following method in the WebDeterminationsServletContext class.
    public String resolveFullPath(String path)
    File f = new File(path);
    return f.isAbsolute() ? f.getAbsolutePath() : this.servletContext.getRealPath(path);
    We believe the getRealPath(path), highlighted in red, is returning null. Any ideas how we can resolve this?
    2) The second issue I'm facing is with regards the plugins.libraries property in the application.properties file. I've got the entry as
    plugin.libraries =DataAdaptor.DA;
    which should point to our customised data adaptor. However I'm getting the following error.
    4242994 [[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN com.or
    acle.determinations.web.platform.servlet.WebDeterminationsServletContext - Can not find class: Data
    Adaptor.DA
    4243025 [[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN com.or
    acle.determinations.interview.engine.local.LocalInterviewEngine - Can not find class: DataAdaptor.D
    A
    3) Also, does anyone know if it's possible to deploy a web-determinations.war file containing additional internal application code? What we're attempting to do is deliver a single war file which not only holds the web determination code but also all the code for an application which wraps the OWD within it. At present this just isn't working. I'm not sure what the conflict is exactly. The only way i seem to be able to get this working is by deploying the code in two seperate war files.
    Any help on these issues would be greaty appreciated.
    Thanks,
    Taj

    (2) is being caused because your data adaptor plugin is not installed properly. The jar that contains your plugin needs to go in the WEB-INF/lib directory and you must specify the fully qualified class name in the plugin.libraries property of the application.properties file.
    If you haven't provided a custom data adaptor, Web Determinations will configure and attach the default one for use instead, which is file based. If you are deploying to WebLogic as an unxeploded war, you must configure the directory the default data directory the plugin will uses by specifying an absolute path that your instance of Web Determinations has read/write permissions to in the xds.file.path property of the application.properties file. In your case (1) is basically being caused by (2) since if the your data adaptor was loaded correctly the default one wouldn't load at all.
    As for (3) yes it's likely possible, provided you don't have library conflicts. How it's done really depends on what these additional customisations consist of.

  • Error while saving default data type

    When I try to save system wide Default Data Format of any of the columns, an error pops out. Seems like an XML error:
    The current xml is invalid with the following errors:
    Bad xml instance!
    <?xml version="1.0"?> <sawsavedformat:metadata xmlns:sawsavedformat="com.siebel.analytics.web/savedformat/v1.1"><sawsavedformat:columnSavedFormats><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Division Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Group Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Dept Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Class Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Item As Was&quot;.&quot;Subclass Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Chain Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Area Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Region Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;District Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Organization As Was&quot;.&quot;Store Number&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="right" vAlign="top"><saw:dataFormat xsi:type="saw:number" commas="false" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Business Calendar&quot;.&quot;Fiscal Week&quot;"><saw:displayFormat><saw:formatSpec suppress="suppress" wrapText="true" visibility="visible" hAlign="left" vAlign="top"><saw:dataFormat xsi:type="saw:text" textFormat="plain"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat><sawsavedformat:columnSavedFormat xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="sawsavedformat:regularColumnSavedFormat" columnName="&quot;HT Catalog&quot;.&quot;Unit Inventory&quot;.&quot;U BOP&quot;"><saw:displayFormat><saw:formatSpec suppress="repeat" wrapText="true" visibility="visible" hAlign="right" vAlign="top" imagePlacement="right"><saw:dataFormat xsi:type="saw:number" whistlerFormat="#,##0" commas="true" negativeType="minus" minDigits="0" maxDigits="0"/></saw:formatSpec></saw:displayFormat><saw:tableHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:tableHeading><saw:columnHeading><saw:displayFormat><saw:formatSpec/></saw:displayFormat></saw:columnHeading></sawsavedformat:columnSavedFormat></sawsavedformat:columnSavedFormats></sawsavedformat:metadata>
    Line:2, Col:8982, Attribute 'whistlerFormat' is not declared for element 'dataFormat'
    Any suggestions?
    Thanks

    HI,
    Its known bug in obiee11.1.1.5. version try to apply obiee11.1.5.5.BP bug fixes version.
    fyi,
    bug 13370386 - 'THE CURRENT XML IS INVALID WITH THE FOLLOWING ERRORS: BAD XMLINSTANCE!' OCCURS
    bug 13249783 - OBIEE 11G THROWS BAD XML INSTANCE
    Thanks
    Deva

Maybe you are looking for