Skip to Content
author's profile photo Former Member
Former Member

date format

Hello all,

I have input fields bound to context of simple type date in my web dynpro application. The default date format is MM/dd/yyyy. However the first time I select a date it turns to dd.MM.yyyy. Subsequent clicks return to MM/dd/yyyy. However when the dd.MM.yyyy format is being displayed I cannot hit the submit button to perform action(it gives me an error 'please give value in form MM/dd/yyyy') How can i fix this?

Thanks

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Dec 02, 2005 at 04:43 AM

    Hi vijay

    Send your code so that the actual problem can be found.

    Regards

    Vijayakhanna Raman

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 01, 2005 at 10:01 PM

    This is a bug, open an OSS on it. I had similar problems with date field bindings but it was to do with rendering.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 02, 2005 at 06:06 AM

    Hi Vijay,

    I got this problem when I was trying to set a date in a particular format. I also had input fields bound to context of simple type date in my web dynpro application.

    For the first time, it comes in dd/MM/yyyy but in subsequent times it changes back to MM/dd/yyyy.

    But since my requirement was to have the Date Format to a particular type dd/MM/yyyy. I fixed it by changing the user language everywhere.

    If you also want to have a fixed date format, you can refer to my reply in this post

    webas-620-wrong-database-parameters

    Thanks & Regards,

    Shubham

    Add a comment
    10|10000 characters needed characters exceeded

    • Hallo Shubham,

      The following section (extracted from the Web" target="_blank">http://help.sap.com/saphelp_nw04/helpdata/en/f4/d95664da179b4db731e21c2e470b72/frameset.htm">Web Dynpro documentation in the SAP NetWeaver Online Help) describes the mechanism used by the Web Dynpro Java Runtime to calculate the session locale:

      The session locale is the locale that is specified for the current user by the user management engine (UME). The fallback sequence is:

      <i>1) In case of an authenticated or anonymous user, the locale specified by the URL-parameter sap-locale is returned.

      <b>Note:</b>

      The URL-parameter sap-locale should only be used by the application developer for testing purposes. In live scenarios the session locale should be specified based on either the user, the browser or the application locale.

      2) In case of an authenticated user, the locale specified for this user is returned.

      3) Otherwise, the locale specified by the browser settings ("accept-language" HTTP header) is returned if existing.

      4) Otherwise the default locale specified in the application properties is returned if existing.

      5) Otherwise the default locale specified in the Web Dynpro system properties is returned if existing.

      6) Otherwise the default locale of the VM is returned.</i>

      The session locale calculated by the Web Dynpro Runtime (last column) is passed as input to the java.lang.ResourceBundle class loaded by the SAP J2EE Engine. This class uses the following fallback sequence to load a physically existing resource bundle:

      • load resource bundle for WD calculated locale

      • if not existing: load resource bundle for the default locale of the VM

      • if not existing: load resource bundle without language suffix, which always exists

      <b>Important Note</b> – <u><i>Session locale and Portal integration</i></u>

      When the Web Dynpro application is running inside the SAP Enterprise Portal the session locale is retrieved via URL-parameter. In this case the locale calculation processes described in the above table is not done by the Web Dynpro Runtime.

      <b>Note</b> – <u><i>Session locale, URL-parameter sap-locale and client session</i></u>

      The locale information is associated to the client session not to the Web Dynpro application (addressed via URL). A new client session can be created by clicking the explorer icon in the Windows toolbar. CTRL+N does not work, because in this case only a new client window instance is being created. The URL-parameter sap-locale is only read once per client session.

      Best regards, Bertram

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.