MySQL timestamp formatting errors

I'm continuing to have odd formatting errors when pulling data out of a MySQL database.  The one I'm currently having is with time values. 
The screenshot shows that the error is being generated in the Variant to Data.vi  The actual time stored in the database is 8:30AM  But when converted to timestamp, I get 8:29:59.999  Unfortunately, there doesn't seem to be an easy way to 'round' this value back to what I want either.  
I could go back to string outputs, since that particular error doesn't seem to propagate into a string.  But that messes with the rest of my application.  Going back to string output undoes a couple of days work, and leaves me with the problem of having to convert string 'time' back into timestamp that LabVIEW can understand.
The really odd thing is that 12:30 comes out as 12:30 just fine.  I'm not sure why this would be.  Any ideas?  
Patrick Allen
Solved!
Go to Solution.

There's no difference at all.  Changing the properties of the constant doesn't seem to effect the output at all. 
I'm trying to figure a way to convert the string back into a timestamp now via these instructions. http://zone.ni.com/reference/en-XX/help/371361B-01/glang/scan_from_string/ (example at the bottom of the page)  
But my string out put is in the form 7/7/2009 8:30:00 AM  and there doesn't seem to be a way at all to use the scan from string tool to covert that back into a time stamp.  
Even if I manipulate my string output to be exactly 8:30:00 AM 7/7/2009, the example and any variation I can think of simply won't work.  I always get the error that the data is not in the expected format.   
Message Edited by pallen on 07-07-2009 12:05 PM
Patrick Allen

Similar Messages

  • Timestamp format error

    Hi,
    While using the Oraclexml classes to
    write an XML document to an 8.1.5 DB I get an error oracle.xml.sql.OracleXMLSQLException: Exception
    'java.lang.IllegalArgumentException:Timestamp format must be yyyy-mm-dd
    hh:mm:ss.fffffffff' encountered during processing ROW element 0All prior XML
    row changes were rolled back. in the XML document. The data format in the file is
    09/18/00 12:00:00.

    If you're using it through the commandline, use the "dateFormat" option in putXML or getXML.
    If you're using the OracleXMLSave class, there is the method "setDateFormat()" that you could use. OracleXMLQuery also has one.

  • URGENT - Timestamp Format Error

    Hi Experts,
    In my REGUC table,
    I have timestamp values in a format that I cannot read.
    For eg, current display is showing timestamp values as '3KOBYi(38AP(OH'
    I am not sure if that is a display error or a reading error.
    I think it is a display error.
    If so, how can I change it to display for eg in the typical format '11121011124555'
    I have to resolve this issue ASAP.
    Urgent Please help

    Hi Kiran,
    REGUC is a cluster table.
    TIMESTMP field is of data type CHAR and Length 14.
    The technical information (F1) for the REGUC table is:
    GUI Data:
    Program Name: SAPLSD_DD_STATUS
    Status: STAT_X
    Field Data:
    Table Name: DD06D
    Field Name: SQLTAB
    Data Element: SQLTABLE
    List of Filed in REGUC table:
    LAUFD, LAUFI, XVORL, ZBUKR, LIFNR, KUNNR, VBLNR, TIMESTMP
    Please let me know if you need more information.

  • Convert MySQL timestamp field to a Unix timestamp

    I have a process where I want to compare the current date with an expiration date that is so many months after a registration date. The registration date is stored in a MySQL timestamp format. I want to convert this to a Unix timestame so I can do the comparison with Time(). I have tried both the MySQL UNIX_TIMESTAMP and the PHP getTimestamp() functions and cannot get them to work. I have tried UNIX_TIMESTAMP both in  the original SELECT statement and as a stand alone one. I also get a divide-by-zero error with the date_default_timezone_set function. I have enclosed screenshots of the code and the result of the echo at the bottom. THANKS!

    You're making it far too complicated.
    SELECT TO_DAYS(reg_date) - TO_DAYS(CURDATE()) AS daysleft
    FROM ssregis
    WHERE. . .
    That will give you the number of days left until the registration expires. If it's less than 0, redirect to the renewal page.
    By the way, you're laying yourself wide open to SQL injection attacks by failing to escape the input from the query string. At the very least, you should be doing this:
    $entered_ss_id = mysql_real_escape_string($_GET['record_id']);
    $entered_email = mysql_real_escape_string($_GET['email_address']);
    However, since it looks as though you're hand-coding the script, you should be using MySQL Improved rather than PHP's deprecated MySQL functions. See http://docs.php.net/manual/en/mysqlinfo.api.choosing.php.

  • Timestamp/Date format error with Java 1.6

    I'm getting this error trying to getObjects from a ResultSet query for an Oracle Lite 10G table that has colums of the TIMESTAMP or DATE type. This works fine under java 1.5. Java 1.6 seems to have broken TIMESTAMP/DATE compatibility with Oracle Lite. Are there any plans to make 10G compatible with Java 1.6? We would like to port our application from Java 1.5 to 1.6, but this is an obstacle. I suppose one work-around would be to use TO_CHAR on all the DATE fields and convert them back to java Dates programatically, but that would be a hassle.
    Update: I changed the column types of the table from TIMESTAMP to DATE. The same exception occurs when calling POLJDBCResultSet.getObject() on the DATE columns. Again, this works fine under Java 1.5, but not 1.6.
    java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss[.fffffffff]
         at java.sql.Timestamp.valueOf(Timestamp.java:194)
         at oracle.lite.poljdbc.LiteEmbResultSet.jniGetDataTimestamp(Native Method)
         at oracle.lite.poljdbc.LiteEmbResultSet.getVal(Unknown Source)
         at oracle.lite.poljdbc.POLJDBCResultSet.getTimestamp(Unknown Source)
         at oracle.lite.poljdbc.POLJDBCResultSet.getObject(Unknown Source)
         at oracle.lite.poljdbc.POLJDBCResultSet.getObject(Unknown Source)

    I just found a pretty easy java work-around for this that doesn't involve changing the table column types or the SQL:
    Check the column type from the ResultSetMetaData before calling ResultSet.getObject(). If the type is DATE, TIMESTAMP or TIME, call ResultSet.getString() which doesn't throw an exception. Then convert the string to a java.util.Date using java.text.SimpleDateFormat. That can then be used to instantiate a Timestamp.
    This seems to work.
    Message was edited by:
    user490596

  • Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff exception

    Hi,
    I am running a web application that connects to oracle 9i database server. I am getting the following exception whenever I access Timestamp.valueOf(object)..
    java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff
    at java.sql.Timestamp.valueOf(Timestamp.java:160).
    JDK version 1.4.
    Oracle client : Oracle 10 g instant client.
    Oracle server: Oracle 9i.
    Can somebody help me out.
    Thanks.

    Hi homero,
    Thanks for your inputs.
    XL.DefaultDateFormat = yyyy/MM/dd hh:mm:ss z
    unlike the date format mentioned in the exception (yyyy-mm-dd hh:mm:ss.fffffffff)
    Moreover, yyyy-mm-dd hh:mm:ss doesnot make much sense to me; It should be yyyy-MM-dd hh:mm:ss;
    I concatenated the nanoseconds precision to the formatted date string and a different exception occurred this time in system validation stage.
    ERROR,02 Dec 2008 11:48:11,455,[XELLERATE.SERVER],Class/Method: tcDataObj/eventPreInsert Error :Insert permission is denied
    ERROR,02 Dec 2008 11:48:11,471,[XELLERATE.SERVER],Class/Method: tcUSR/eventPreInsert Error :Mandatory fields are blank or null.
    BR
    Edited by: user10478011 on Dec 1, 2008 10:24 PM

  • Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff

    We have a project using TopLink 10.1.3 with WAS 6.0 and Oracle 9i. The project is experiencing the following exception. Could someone provide an insight on what could cause the error? We greatly appreciate your help.
    [7/20/07 10:00:32:718 EDT] 00000023 SystemOut     O [TopLink Finer]: 2007.07.20 10:00:32.718--ServerSession(120755866)--client acquired
    [7/20/07 10:00:32:718 EDT] 00000023 SystemOut     O [TopLink Finest]: 2007.07.20 10:00:32.718--ClientSession(1697994439)--Execute query ReadAllQuery(com.ford.gpd.plm.fos.bo.RepSolvedRules)
    [7/20/07 10:00:32:718 EDT] 00000023 SystemOut     O [TopLink Finest]: 2007.07.20 10:00:32.718--ServerSession(120755866)--reconnecting to external connection pool
    [7/20/07 10:00:32:718 EDT] 00000023 SystemOut     O [TopLink Fine]: 2007.07.20 10:00:32.718--ServerSession(120755866)--Connection(2023118535)--select a.fos005_ftr_C, a.fos007_rule_d, a.fos011_column_d, a.fos001_option_c, a.fos009_report_k, a.FOS002_PROD_TYPE_C, a.FOS002_VEH_LINE_C, a.FOS002_MODEL_YEAR_R
    from  FFOSV01_REP_OPT_SOLVE_RULE_VW a, FFOS020_REP_SOLVE_QUALIFIER b
    where a.fos009_report_k = 3
    and a.fos011_column_d in (3, 4, 5, 8, 9, 14)
    and UPPER(b.fos005_qualifier_ftr_c) like UPPER('a3%')
    and a.fos009_report_k = b.fos009_report_k
    and a.fos013_group_d = b.fos013_group_d
    and a.fos011_column_d = b.fos011_column_d
    and a.fos007_rule_d = b.fos007_rule_d
    --and a.fos013_report_date_s = b.fos013_report_date_s
    order by a.fos005_ftr_C, a.fos011_column_d, DECODE(a.fos001_option_c, 'S', 1, 'L', 2, 'M', 3, 'O', 4, 'P', 5, 'I', 6, 'A', 7)
    [7/20/07 10:00:32:749 EDT] 00000023 SystemOut     O [TopLink Warning]: 2007.07.20 10:00:32.749--ClientSession(1697994439)--java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff
         at java.sql.Timestamp.valueOf(Timestamp.java:304)
         at oracle.jdbc.driver.OracleStatement.getTimestampValue(OracleStatement.java(Compiled Code))
         at oracle.jdbc.driver.OracleResultSetImpl.getTimestamp(OracleResultSetImpl.java(Compiled Code))
         at com.ibm.ws.rsadapter.jdbc.WSJdbcResultSet.getTimestamp(WSJdbcResultSet.java(Compiled Code))
         at oracle.toplink.oraclespecific.Oracle9Platform.getObjectFromResultSet(Oracle9Platform.java(Compiled Code))
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.getObject(DatabaseAccessor.java(Compiled Code))
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.fetchRow(DatabaseAccessor.java(Compiled Code))
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java(Compiled Code))
         at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:442)
         at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:453)
         at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:117)
         at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:103)
         at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeSelectCall(DatasourceCallQueryMechanism.java:174)
         at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.selectAllRows(DatasourceCallQueryMechanism.java:481)
         at oracle.toplink.queryframework.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:458)
         at oracle.toplink.queryframework.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:800)
         at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:603)
         at oracle.toplink.queryframework.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:768)
         at oracle.toplink.queryframework.ReadAllQuery.execute(ReadAllQuery.java:436)
         at oracle.toplink.publicinterface.Session.internalExecuteQuery(Session.java:2062)
         at oracle.toplink.publicinterface.Session.executeQuery(Session.java:981)
         at oracle.toplink.publicinterface.Session.executeQuery(Session.java:953)
         at com.ford.it.persistence.impl.toplink.AbstractQueryStrategy.execute(AbstractQueryStrategy.java:324)
         at com.ford.it.persistence.impl.toplink.QueryImpl.execute(QueryImpl.java:138)FFOSV01_REP_OPT_SOLVE_RULE_VW is a VIEW and the reference b FFOS020_REP_SOLVE_QUALIFIER is a table with a to b as one-to-many mapping. View has a reportDate filed as DATE and the same with the b table. Java side descriptors are using the java.sql.Timestamp.
    The problem is when joining the View with the Table(like in the above SQL), the Exception occurs. If we run a select from the View then we don't see this exception.
    -- Haiwei

    Thanks for your responses.
    The developer changed the query in the Workbench to be:
    SELECT DISTINCT t0.FOS001_OPTION_C, t0.FOS007_RULE_D, t0.FOS009_REPORT_K, t0.FOS011_COLUMN_D, t0.FOS013_GROUP_D, t0.FOS003_EFF_PT_IN_C, t0.FOS003_EFF_PT_OUT_C, t0.FOS013_REPORT_DATE_S, t0.FOS005_FTR_C, t0.FOS002_PROD_TYPE_C, t0.FOS002_MODEL_YEAR_R, t0.FOS002_VEH_LINE_C
    FROM FFOSV01_REP_OPT_SOLVE_RULE_VW t0, FFOS020_REP_SOLVE_QUALIFIER t1
    WHERE (((t0.FOS009_REPORT_K = 3)
    AND (t1.FOS005_QUALIFIER_FTR_C LIKE 'A3%'))
    AND (t0.FOS011_COLUMN_D in (1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14))
    AND ((t1.FOS002_VEH_LINE_C = t0.FOS002_VEH_LINE_C)
    AND ((t1.FOS013_GROUP_D = t0.FOS013_GROUP_D)
    AND ((t1.FOS007_RULE_D = t0.FOS007_RULE_D)
    AND ((t1.FOS009_REPORT_K = t0.FOS009_REPORT_K)
    AND ((t1.FOS013_REPORT_DATE_S = t0.FOS013_REPORT_DATE_S)
    AND ((t1.FOS002_PROD_TYPE_C = t0.FOS002_PROD_TYPE_C)
    AND ((t1.FOS011_COLUMN_D = t0.FOS011_COLUMN_D)
    AND (t1.FOS002_MODEL_YEAR_R = t0.FOS002_MODEL_YEAR_R)))))))))
    order by t0.FOS005_FTR_C, t0.FOS011_COLUMN_D, DECODE(t0.FOS001_OPTION_C, 'S', 1, 'L', 2, 'M', 3, 'O', 4, 'P', 5, 'I', 6, 'A', 7)and it worked.
    What happened was that when the application defined a similar join using Expression, with simplified where clause, between the View and table in the Workbench, the join worked fine. So the applicaiton updated its original query (the select part) based on the SQL generated by TopLink runtime for the join.
    The project uses Oracle9Platform.
    Regarding "Query executes in JDBC and returns expected result": the original query executed fine with Oracle SQL Developer.
    Regarding "Does the date column you are trying to read have any time portion or is it just a date with no time portion?": the date column is of DATE database type, and has time portion.
    Thanks again for your responses.
    Haiwei

  • Timestamp Format

    Hi Gurus,
    I have a double field which stores date values and i have another double fiels which stores time.Now i need to concat both these and cast it to timestamp.The problem which i am facing is with the Format of timestamp.I am unable to specify the format neither in answers nor in RPD.Thw syntax which i am using is as follows cast(cast("date value"||"time vale") as char ( 18 ) ) as timestamp format 'yyyymmddhhmmss').If i dnt specify any format answers return an error saying Invalid timestamp.please help

    "set nls_timestamp_format = 'YYYY-MM-DD
    HH24:MI:SS.FF1'"
    Could this be done at database level.If this can be
    done using some parameter files,what exactly has to
    be done?yes, it is done at the database level when you create your database. it is done at the instance level with the NLS_TIMESTAMP_FORMAT parameter and it is modifyable at the session level too.
    SQL> select type,parameter,value from (
      2  select 'NLS_DATABASE_PARAMETERS' type,parameter,value from NLS_DATABASE_PARAMETERS
      3  union all
      4  select 'NLS_INSTANCE_PARAMETERS',parameter,value from NLS_INSTANCE_PARAMETERS
      5  union all
      6  select 'NLS_SESSION_PARAMETERS',parameter,value from NLS_SESSION_PARAMETERS
      7  )
      8  where parameter='NLS_TIMESTAMP_FORMAT'
    TYPE                    PARAMETER                      VALUE
    NLS_DATABASE_PARAMETERS NLS_TIMESTAMP_FORMAT           DD.MM.RR HH24:MI:SSXFF
    NLS_INSTANCE_PARAMETERS NLS_TIMESTAMP_FORMAT
    NLS_SESSION_PARAMETERS  NLS_TIMESTAMP_FORMAT           DD.MM.YYYY HH24:MI:SS.FFMessage was edited by:
    Laurent Schneider
    you cannot change the "database" level after db creation, but you can modify the "instance" level by specifying the parameter in your parameter file

  • Timestamp formats that include literal data in quotes

    Is there an alternate way to specify literal text in timestamp formats, other than to quote it with double quotes? I am trying to work around a bug in SQLDeveloper (described below).
    The formats I am using are:
    timestamp: YYYY-MM-DD"t"HH24:MI:SS.FF6
    timestamp tz: YYYY-MM-DD"t"HH24:MI:SS.FF6TZH:TZM
    These formats work fine in sqlplus and in my application:
    SQL> alter session set nls_timestamp_format = 'YYYY-MM-DD"t"HH24:MI:SS.FF6';
    Session altered.
    But when I use these them in the Database->NLS Parameters section in Preferences, I get the following error:
    ORA-02248: invalid option for ALTER SESSION
    If I remove the "t" from the middle, there are no errors in SQLDeveloper and the formats work correctly in the sql worksheet.
    SQLDeveloper: 1.1.2.25 on Windows XP Pro
    Oracle server: 9.2.0.5.0, 64bit running on Solaris
    Thanks,
    Philip

    Hi JW,
    if you want to track changes, implement the how-to paper about "line-items" (see SAP Service Marketplace). BPS layout will always show the latest data (price) and to show the history, you can use a simple BW query with drill-down on the timestamp.
    Regards
    Marc
    SAP NetWeaver RIG

  • SEVERE: Message: [-3050]: Invalid timestamp format:ISO(input position 2)

    Hello!
    I'm installing a AS JAVA 2004S with EP/EP-CORE and BI_JAVA and got following error during Java Load step.   (The installation successfully creates and loads about 1000 tables prior the error).
    Regards,
    Fredrik
    serverXX:/usr/sap/TPQ/ciinst # more jload.java.log
    java version "1.4.2"
    Java(TM) 2 Runtime Environment, Standard Edition (build 2.2)
    IBM J9SE VM (build 2.2, J2RE 1.4.2 IBM J9 2.2 Linux amd64-64 j9xa64142-20061124 (JIT enabled)
    J9VM - 20061121_1035_LHdSMr
    JIT  - r7_level20061020_1803)
    May 24, 2007 11:39:52 AM com.sap.inst.jload.Jload main
    INFO: Jload -sec TPQ,jdbc/pool/TPQ,/usr/sap/TPQ/SYS/global/security/data/SecStore.properties,/usr/sap/TPQ/SYS/global/security/data/Se
    cStore.key -dataDir /a_stage/51032257/JAVA_EXPORT/JDMP -job /usr/sap/TPQ/ciinst/IMPORT.XML -log jload.log
    May 24, 2007 11:39:53 AM com.sap.inst.jload.db.DBConnection connectViaSecureStore
    INFO: connected to TPQ on jdbc/pool/TPQ
    May 24, 2007 11:39:53 AM com.sap.inst.jload.JobStatus readStatus
    INFO: trying to read status file /usr/sap/TPQ/ciinst/IMPORT.sta
    May 24, 2007 11:39:53 AM com.sap.inst.jload.JobStatus readStatus
    INFO: commencing restart
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
    INFO: trying to delete from table BC_UDDI_PARAM
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
    INFO: BC_UDDI_PARAM deleted
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
    SEVERE: DB Error during import of BC_UDDI_PARAM
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
    SEVERE: Message: [-3050]: Invalid timestamp format:ISO(input position 83)
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
    SEVERE: SQLState: I3050
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
    SEVERE: ErrorCode: -3050
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
    INFO: trying to delete from table BC_XMLA_COL
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
    INFO: BC_XMLA_COL deleted
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload dbImport
    SEVERE: DB Error during import of BC_XMLA_COL
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
    SEVERE: Message: [-3050]: Invalid timestamp format:ISO(input position 2)
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
    SEVERE: SQLState: I3050
    May 24, 2007 11:39:53 AM com.sap.inst.jload.Jload printSQLException
    SEVERE: ErrorCode: -3050
    May 24, 2007 11:39:53 AM com.sap.inst.jload.db.DBConnection disconnect
    INFO: disconnected
    serverXX:/usr/sap/TPQ/ciinst #

    Hi
    yes, I had the same issue and I found a solution.
    You need to request a patch for BUG 9212862 (already corrected in WLS 10.3.3) and do the follwing:
    javax.xml.ws.BindingProvider provider = (javax.xml.ws.BindingProvider)port;
    java.util.Map context = provider.getRequestContext();
    context.put(weblogic.wsee.jaxrpc.WLStub.POLICY_COMPATIBILITY_PREFERENCE, weblogic.wsee.jaxrpc.WLStub.POLICY_COMPATIBILITY_MSFT);      
    This will cause the SecurityMessageArchitect class of WLS to not send the SecurityTokenReference in the Soap security header.
    Please note that is evidently a non-comformity to the specs of microsoft:
    Please give a look at
    http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf (8.3 Signing Tokens)
    and also at:
    http://www.oasis-open.org/committees/download.php/16768/wss-v1.1-spec-os-SAMLTokenProfile.pdf
    (3.4 Identifying and Referencing Security Tokens)
    A SAML key identifier reference MUST be used for all (local and remote) references to SAML 1.1
    assertions. [...]
    All conformant implementations MUST be able to process SAML assertion references occurring in a
    <wsse:Security> header or in a header element other than a signature to acquire the corresponding
    assertion. A conformant implementation MUST be able to process any such reference independent of the
    confirmation method of the referenced assertion.
    It follows that the .NET 3.5 is a non conformat implementation: I would gladly know which is the position of Microsoft on that.
    ciao
    carlo

  • Bex Analyser : Date Format error.

    Hi All,
    We are facing date format error, while running the query in Bex analyzer.
    We have one column in report i.e Net Payment Date, so when we run the query in analyzer the single date like "5-6-2010 is getting swapped like 6-5-10 & year also showing two digits i.e instead of 2010 it shows 10" & date like "12-09-2010 is coming perfectly."
    Means the date which is in single digit we are facing this problem like 1 to 9 & the dates which are 10 & above showing perfectly.
    In RSRT the query showing proper result, so i don't think it's BI problem.
    The regional setting is DD-MM-YYYY & Date separator is '-' & we don't want to change this format.
    Is there any SAP note or any solution for this..??
    All the replays are gr8ly appreciated.
    Thanks,
    Santosh

    Hi Santosh,
    how about web display? is it ok? for me it seems more an Excel problem, so maybe you should check if there is special formatingin this.
    Regards,
    Anass

  • IDC File name format -  customaize TIMESTAMP format

    Hi.
    Can we change the default TIMESTAMP format in IDC as we want to deliver the filename as yyyymmddhhmiss.dat?
    Is there any provision in Oracle B2B?
    Regards
    Jawah

    Please refer -
    Re: IDC  format -   customize  TIMESTAMP format
    Do not run two parallel threads for the same problem please.
    Regards,
    Anuj

  • Trying to convert a pdf to a word doc using Acrobat XI Pro. I am getting formatting errors and scrambled text, especially right below headings. Not all headings affected, just some, but all the same paragraph tag. Any ideas?

    I am trying to convert a pdf  to a word doc. The pdf was created in Framemaker. I am using Acrobat XI Pro and getting formatting errors and scrambled (or missing) text, especially below a heading. Any fixes?

    Hi pakbecker,
    Please try updating to Acrobat 11.0.7 and check.
    In case you still face issues,  i would like to have a look at th doucment.
    Send me an email at [email protected]
    Regards,
    Rave

  • FF_5 - Import Bank Statement, Err: Formatting error in the field COBL-KOSTL

    Hi
    When importing the bank statement I'm getting the error
    Error: (00 298) Formatting error in the field COBL-KOSTL ; see next message
    Why is it doing this? In OKB9 I have the GL Account and the cost center assigned. It is the ne GL that is giving this problem, in the classic GL I do not have this problem.
    Thanks in advance

    Hi
    No, it is not that. For some reason in the new GL it does not seem to determine the cost centers and profit centers as usual.
    For exampl to allocate the Profit Center for Balance Sheet Account I used to use 3KEH in the classic gl but in the New gl we must use FAGL3KEH.
    Now with cost center i'm having the same problem, does not determine the cost center when importing the bank statement.
    Can someone help me.
    Thanks in advance
    Edited by: Louis De Gouveia on Mar 3, 2009 7:07 AM

  • To convert date dd/mm/yyyy in Timestamp format

    hi
    I want to convert date of format dd/MM/yyyy, which get from user by PropertyUtils.getSimplePropetrty(form, "startDate"); , into Timestamp format...........
    please help me in this regard.......
    1904

    ya mean it from java.sql.Timestamp
    and also I am using getTime() method but giving
    root cause:
    org.apache.commons.beanutils.ConversionException: Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff
    and
    Caused by: java.lang.IllegalArgumentException: Timestamp format must be yyyy-mm-dd hh:mm:ss.fffffffff
    at java.sql.Timestamp.valueOf(Timestamp.java:160)
    at org.apache.commons.beanutils.converters.SqlTimestampConverter.convert(SqlTimestampConverter.java:157)

Maybe you are looking for