Unparsable date exception

Hi,
I am getting exception "Unparseable date: "Thu May 21 18:16:42 IST 2009"" while changing my regional setting to turkey
Exception occured by following statement
SimpleDateFormat myDateFormat = new SimpleDateFormat(sFormat,Locale.getDefault());
myDate = myDateFormat.parse(sDateValue);
what would be the problem, can any body help me
Thanks
Tej Kiran

TejKiran wrote:
i am using sFormat is "E MMM dd hh:mm:ss z yyyy"I don't know if you're still around. But for what it's worth:
"MMM" means "month in text format, abbreviated".
When you use that with a turkish locale, then the turkish names for the months will be used. So your english-language dates won't be parsed correctly.

Similar Messages

SimpleDateFormat.parse() causes Unparsable date exception

I am using SimpleDateFormat to both format and parse date strings. The format is working properly, but parse results in the following exception:
java.text.ParseException: Unparseable date: "2007-08-31T12:05:05.651-0700"
at java.text.DateFormat.parse(Unknown Source)
Here is my code:
SimpleDateFormat dateFormatter = new SimpleDateFormat("yyyy-MM-dd'T'kk:mm:ss.SZ");
String dateTime = dateFormatter.format(new Date());
Date test = dateFormatter.parse(dateTime);
For testing purposes, I am formatting a date string, and then passing it right back into parse() and I get the exception.
I am using jre1.5.0_10.
Thank you for your help.
-Karen

You have specified the milliseconds (S) to have a minimum of 1 letter.
From the API:
Number: For formatting, the number of pattern letters is the minimum number of digits, and shorter numbers are zero-padded to this amount. For parsing, the number of pattern letters is ignored unless it's needed to separate two adjacent fields.
If you specify it like this:SimpleDateFormat dateFormatter = new SimpleDateFormat("yyyy-MM-dd'T'kk:mm:ss.SSSZ");
// or like this
SimpleDateFormat dateFormatter = new SimpleDateFormat("yyyy-MM-dd'T'kk:mm:ss.S Z");it will work.
Message was edited by:
dwg

I have just installed the latest software for iphone4 - I have retained all data except my Contacts have disappeared - how can I get back ?

I have just installed the latest software for the iphone4 - I have retained all the data EXCEPT the Contacts have all disappeared - can I get back ?

Maybe on outlook application if you use it with pc. If not try to restore your iPhone with a old backup from iTunes.
http://support.apple.com/kb/ht1414

Use of error page resulting in could not deserialize session data exception

          We have recently converted classes that store objects in the HTTP Session to implement
          serializable.
          Our application uses an error page set up in our web.xml for 500 errors.
          It also uses filters.
          When our application throws an exception and allows the server to handle it
          via the error page setup, we end up with the exception we threw, plus a number
          of
          "Could not deserialize session data" exceptions in the stack trace.
          In general, the exceptions can be traced to lines in code that attempt to reference
          one of our "serializable" session objects to get user info for logging purposes.
          Problem is, other applications that do not use error pages to handle exceptions
          do not throw these types of exceptions in the wl-domain.log and they use the same
          classes.
          Does anyone know why this happens when using error pages and what we need to do
          to correct it?
          We are using Weblogic 8.1sp2.
          Thanks!!
          Example of the stack trace messages:
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: weblogic.servlet.internal.FilterConfigImpl
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:67)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: java.util.Vector$1
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurHTML.<init>(OurHTML.java:57)
               at doh.stuff.OurFilter.startLog4j(OurFilter.java:513)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:75)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >


          We have recently converted classes that store objects in the HTTP Session to implement
          serializable.
          Our application uses an error page set up in our web.xml for 500 errors.
          It also uses filters.
          When our application throws an exception and allows the server to handle it
          via the error page setup, we end up with the exception we threw, plus a number
          of
          "Could not deserialize session data" exceptions in the stack trace.
          In general, the exceptions can be traced to lines in code that attempt to reference
          one of our "serializable" session objects to get user info for logging purposes.
          Problem is, other applications that do not use error pages to handle exceptions
          do not throw these types of exceptions in the wl-domain.log and they use the same
          classes.
          Does anyone know why this happens when using error pages and what we need to do
          to correct it?
          We are using Weblogic 8.1sp2.
          Thanks!!
          Example of the stack trace messages:
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: weblogic.servlet.internal.FilterConfigImpl
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:67)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >
          ####<May 5, 2004 2:52:17 PM EDT> <Error> <HTTP Session> <machinexyz> <cgServer>
          <ExecuteThread: '11' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-100028>
          <Could not deserialize session data.
          java.io.NotSerializableException: java.util.Vector$1
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)
               at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1330)
               at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1302)
               at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1245)
               at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
               at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
               at weblogic.servlet.internal.AttributeWrapper.convertObjectToBytes(AttributeWrapper.java:136)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:112)
               at weblogic.servlet.internal.AttributeWrapper.getObject(AttributeWrapper.java:69)
               at weblogic.servlet.internal.session.SessionData.getAttribute(SessionData.java:431)
               at doh.stuff.OurHTML.<init>(OurHTML.java:57)
               at doh.stuff.OurFilter.startLog4j(OurFilter.java:513)
               at doh.stuff.OurFilter.doFilter(OurFilter.java:75)
               at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
               at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:305)
               at weblogic.servlet.internal.ServletResponseImpl.sendError(ServletResponseImpl.java:523)
               at weblogic.servlet.internal.WebAppServletContext.handleException(WebAppServletContext.java:3908)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3683)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          >

Java.util.Data Exception when Testing Function

Hi All,
using VC I'm tring to test fuction HRPWC_RFC_AS_OVERVIEW. The field ViewId is the only one mandatory. When I've executed function I've obtained java.util.Date exception.
What does that mean? What should I set properly to test the function?
Regards,
Marek

Hi Marek,
I suppose you meant HRWPC_RFC_AS_OVERVIEW. This is an HR rfc that displays employees absence. I tested it in my VC and it works fine. Ill need some more details on how youve created the model in order to help you.
Regards,
Lisi

UNPARSABLE Date

Hi i am using JDEV 11.1.1.3
i have a rich input date in my form....
i getting the value in my backing bean in string format
String ProjStartDate = getId4().getValue().toString();
getting value in this format
"Sun Mar 06 00:00:00 IST 2011
want 2 covert into java.util.date,i tried
DateFormat dateFormat = new SimpleDateFormat("yyyy-MM-dd");
java.util.Date ConvProjStartDate = dateFormatset.parse(ProjStartDate);
i tried different format also....
but i am getting error as UNPARSABLE DATE
please suggest me a solution
Edited by: Venkat L Naidu on Mar 22, 2011 11:32 PM

try this:
SimpleDateFormat formatter=
new SimpleDateFormat("MM-dd-yyyy");
String strDate = formatter.format(this.id1.getValue());

Upon transferring to the cloud, all my previous mail says the same date, except for today and yesterday. The rest says it came in on the same date I had to replace the hard drive 3 years ago. Totally stumped. It didn't do this on my mac...

Upon transferring to the cloud, all my previous mail says it entered my box on the same date, except for today and yesterday. Everything else says it came in on the same date on which I had to replace the hard drive 3 years ago. Totally stumped. It didn't do this on my mac...only when I moved. I have bad feelings about being to fix this...Any suggestions?

Get the new keyboard at eBay and replace by yourself may be cheaper way, though you're required higher skill and well know about MacBook Air.
http://www.ebay.com/sch/i.html?_from=R40&_trksid=p2050601.m570.l1313.TR0.TRC0.H0 .Xmacbook+air+2011+keyboard&_nkw=macbook+air+2011+keyboard&_sacat=0
https://www.youtube.com/watch?v=gLbasVD69xo

Found Stale Data Exception while Editing User form & process form

Found Stale Data Exception only when I try to edit a set of 40 users that I created long ago. The other users are fine - they are getting provisioned and created in OIM. Has any body has an idea as to why this error is coming? and how to resolve as it is coming only for a limited set of users. ???
ERROR [ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' XELLERATE.WEBAPP - Class/Method: tcManageUserAction/editUser encounter some problems: {1}
Thor.API.Exceptions.tcStaleDataUpdateException
     at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.updateUserData(Unknown Source)
     at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.updateUser(Unknown Source)
     at com.thortech.xl.ejb.beans.tcUserOperationsSession.updateUser(Unknown Source)
     at com.thortech.xl.ejb.beans.tcUserOperations_voj9p2_EOImpl.updateUser(tcUserOperations_voj9p2_EOImpl.java:3474)
     at Thor.API.Operations.tcUserOperationsClient.updateUser(Unknown Source)
     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:597)
     at Thor.API.Base.SecurityInvocationHandler$1.run(Unknown Source)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.security.Security.runAs(Security.java:41)
     at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
     at Thor.API.Base.SecurityInvocationHandler.invoke(Unknown Source)
     at $Proxy59.updateUser(Unknown Source)
     at com.thortech.xl.webclient.actions.tcManageUserAction.editUser(Unknown Source)
     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:597)
     at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
     at com.thortech.xl.webclient.actions.tcLookupDispatchAction.execute(Unknown Source)
     at com.thortech.xl.webclient.actions.tcActionBase.execute(Unknown Source)
     at com.thortech.xl.webclient.actions.tcAction.execute(Unknown Source)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at com.thortech.xl.webclient.security.SecurityFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
     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:2180)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
ERROR [ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)' XELLERATE.WEBAPP - Class/Method: tcManageUserAction/editUser encounter some problems: {1}
Thor.API.Exceptions.tcStaleDataUpdateException
     at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.updateUserData(Unknown Source)
     at com.thortech.xl.ejb.beansimpl.tcUserOperationsBean.updateUser(Unknown Source)
     at com.thortech.xl.ejb.beans.tcUserOperationsSession.updateUser(Unknown Source)
     at com.thortech.xl.ejb.beans.tcUserOperations_voj9p2_EOImpl.updateUser(tcUserOperations_voj9p2_EOImpl.java:3474)
     at Thor.API.Operations.tcUserOperationsClient.updateUser(Unknown Source)
     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:597)
     at Thor.API.Base.SecurityInvocationHandler$1.run(Unknown Source)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManage
Thanks,
- oidm

Stale data exception means something has changed about the user when you are updating them. So if you get a result set that has 50 users in it, then you go through each row and update, you will get this error because you have modified the over all result set.
You need to do a findUsers for each user row, and then perform the update on that result set. Then move on to the next user and do the same thing. Don't update a result set that has more than 1 row.
-Kevin

Data detector detects all dates except Oct.

Received email with dates. When pointer hovers over dates in mail app the data is detected and option to add to ical is offered for all dates except Oct.

Got it!
=IIF(Fields!Completion_Date.Value = "1900-01-01 00:00:00.000", "", Fields!Completion_Date.Value)

Plugin container shutsdown with data exception v13.0

Since going to v13, I have been getting the pop up error saying that the plugin container has been shutdown with a data exception error.
It doesn't give an indication as to what plugin it was trying to execute or service. I can't be doing the window blind imitation. So I deleted v13 and installed an earlier version.
Is there a way to find out what plugin / extension is causing this?

Knock knock firefox. there is a problem. many many people are having this same issue. it is not us. It is YOU. Fix FF or work with Adobe to fix the problem.

Date exception for ora-01839 in my procedure

Hi All!
I am writing a new procedure for validation of date. There I mentioned like below.
select to_date(v_attrValue, 'yyyymmdd') into v_date from dual;
if sql%rowcount<=0 then
gnvPrdError.raiseErrorMsg(gnvInvalidEventDate,
'gnvInvalidEventDate');
end if;
It is raising oracle exception. I would like to catch that exception and thru in my format so that the calling procedure should raise exception.
Please help me on this.
Thanks in advance.
Jai

Paul's solution of having a function that just returns 0 or 1 is an option. Having a WHEN OTHERS clause means that you'll catch every possible exception. Alternately, you could add separate exception handlers for the exceptions you actually expect to get, i.e.
DECLARE
exc1 exception;
pragma exception_init( exc1, -1830 );
exc2 exception;
pragma exception_init( exc2, -1847 );
BEGIN
dt := to_date( <<string>>, <<format mask>> )
EXCEPTION
WHEN exc1 THEN
    <<do something>>
WHEN exc2 THEN
    <<something else>>
WHEN exc3 THEN
    <<something else>>
END;Whether you should use a WHEN OTHERS or explicitly declare and catch individual exceptions depends on whether you want to do something different depending on the exception and how comfortable you are enumerating the "valid" exceptions vs. having a catch-all that might catch too much. Personally, I tend to prefer the explicit exceptions approach for production code.
Justin

Orgstructure data (except persons) from one server to another

Hi all,
we have two SAP ECC servers, say serverA and serverB.
in serverA, we maintain all the OM data using PP01, PP02, PPOM_OLD, etc.
as a result of this, the data gets stored in OM infotypes, as we see in hrp tables hrp1000, hrp1001 etc.
on serverA, PA is also implemented, so position objects are related to persons.
in serverB, the exact org data of serverA needs to be synchronized into serverB. (daily once), so that all the org units, positions, jobs, relationships, etc. with org chart appear in serverB.
PA is not implemented in serverB, so person objects is not required to be uploaded to serverB.
what is the best way, to upload OM data of serverA to serverB.
from serverA, we can download the data from HRPtables, or we can access table data using custom RFCs with RFC destinations.
except BDCs, is there any easy and effective way to upload the org data from serverA to serverB.
thanks,
Madhu_1980

Yes, there is ALE messagetype HRMD_A which deals with OM Infotypes as well.
You can filter the object types, so that otype P will not be distributed.
BR - Jörg

ESS - Chnage Own Data Exception

Hello All,
We have installed and configured ESS MSS Business package. Under ESS when I click on Change own data, and if I enter the values like say Extension, Building Number, Room Number, etc. and click on review and save then I am getting following error message:
An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE:
Then I checked the dump in ECC system. It is as below:
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_HRPA_INVALID_SUBTYPE
Date and Time          02/04/2008 07:28:51
Short text
                                                                                An exception occurred that was not caught.
What happened?
                                                                                The exception 'CX_HRPA_INVALID_SUBTYPE' was raised, but it was not caught
     anywhere along
                                                                                the call hierarchy.
                                                                                Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
     'CL_HRPA_READ_TIMECONSTRAINT===CP' has to be
    terminated.
                                                                                What can you do?
                                                                                Note down which actions and inputs caused the error.
                                                                                To process the problem further, contact you SAP system
    administrator.
                                                                                Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
                                                                                An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_HRPA_INVALID_SUBTYPE', was not
     caught in
                                                                                procedure "HRXSS_COD_SAVE_PERSONAL_DATA" "(FUNCTION)", nor was it propagated by
     a RAISING clause.
                                                                                Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    Subtype 0005 Not Permitted for Infotype 0105 &TCLAS&
                                                                                How to correct the error
                                                                                If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
                                                                                "UNCAUGHT_EXCEPTION" "CX_HRPA_INVALID_SUBTYPE"
    "CL_HRPA_READ_TIMECONSTRAINT===CP" or "CL_HRPA_READ_TIMECONSTRAINT===CM002"
    "IF_HRPA_READ_TIMECONSTRAINT~COMPUTE_TIMECONSTRAINT"
                                                                                If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
                                                                                1. The description of the current problem (short dump)
                                                                                To save the description, choose "System->List->Save->Local File
    (Unconverted)".
                                                                                2. Corresponding system log
                                                                                Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
                                                                                3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
                                                                                4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
                                                                                The exception must either be prevented, caught within proedure
    "HRXSS_COD_SAVE_PERSONAL_DATA" "(FUNCTION)", or its possible occurrence must be
     declared in the
                                                                                RAISING clause of the procedure.
Please suggest the solution.

Hi,
The problem was the result, because we identified that the infotype 105 subtypes within the source code are "hard" standard service "change own data". Some of these subtypes were modified by the customer definition, a situation that generated the error, therefore, we proceeded to carry back the standard server tables 000 to 100. Fixed issue.
I hope it helps someone

Unparsable date "yyyy-MM-dd" in Windows Arabic OS

Hi Guys,
I have one problem. Plese help me regarding in this. I am not able to parse the date format like "yyyy-MM-dd" in Windows XP Arabic OS environment.
But the same thing is working fine in Windows XP English OS. I am using jdk version is j2sdk1.4.2_15. My sample program like below:
import java.text.*;
import java.util.*;
public class DatePro2{
public static void main(String[] args)throws Exception{
SimpleDateFormat format = new SimpleDateFormat("yyyy-MM-dd");
System.out.println(format.parse("2008-02-21"));
This is the exception i am getting java.text.ParseException: Unparseable date: "2008-02-21"
Is this the problem with JDK installed in Windows XP Arabic Operating System? or JDK Bug?. Please explain me clearly
Thanks in advance

sureshpatike wrote:
Please help anybody to me regarding the problem of date issue in arabic windows OS environment. problem description is on top. please help help...Construct the SimpleDateFormat for a Western Locale (England, France, USA etc) and make sure you specify the TimeZone for which the date applies.
Edited by: sabre150 on Feb 25, 2008 11:07 AM

IT 581 not taking end date except 31.12.9999

PA 30>IT 581>Create
start date is 01.04.2012
If end date is 31.07.2012
System not considering date before 31.12.9999.
System showing following error-
End date before leaving date (31.12.9999)
Message no. PG211
Diagnosis
The end date entered falls before the employee's leaving date (31.12.9999).
The infotype has time constraint 1. This means that it must always be available during the employee's activity (employment status other than 0)
System Response
The infotype operation cannot be carried out.
Procedure
Control the validity period of the infotype record currently being processed and the employee's employment status in the Actions (0000) infotype for this period.

Dear Sarika,
Info-type 0581 works as the start date as the hiring date or the date your are opting for HRA exception with the end date as 31.12.9999. When you create another record from a particular date it will delimit the old record and create a new record from that date to end date 31.12.9999.
It is not different for different PSA, might be there is another record which will be valid after the end date you are trying to give. But the end date will always be 31.12.9999 till the record is delimited or the person is terminated.
Regards,
Prateek

Unparsable date exception

Similar Messages

Maybe you are looking for