DateTrans Error: Unparseable date: ""

hello,
I've a source field datesource type date and
a target field datetarget type string
datesource = yyyymmdd and i need in datetarget = ddmmyyyy.
i'm using the function dateTtrans, however the follow error occurs:
Runtime exception during processing target field mapping /ns1:file/Inv/InvSum/EDate. The message is: Unparseable date: "" com.sap.aii.mappingtool.tf3.MessageMappingException: Runtime exception during processing target field mapping /ns1:file/Inv/InvSum/EDate. The message is: Unparseable date: ""
thanks very much

If you feel that 00000000 is not passed properly to the target then instead of the DateTransform function why dont you try for multiple substring functions in the mapping logic for the target date.......looking at your req you will need three substring functions and two concat functions....
Ultimately your requirement is to convert yyyymmdd to ddmmyyyy then it can be even achieved using substring functions....the reason for using DateTransform function is that it is simple, has capability to insert date separator.....
So if you feel for 0s the o/p is wrong then you can consider substring logic (it works for date ---> date mapping and have just tested it)....and it works for 20090630 as well as 00000000
Regards,
Abhishek.

Similar Messages

Error: Unparseable date with OracleXMLSave

Hi,
Error:
oracle.xml.sql.OracleXMLSQLException: java.text.ParseException: Unparseable date: "03/18/2099"
int oracle.xml.sql.dml.OracleXMLSave.insertXML(org.w3c.dom.Document)
void b2b.RcvQueueListener.saveCsmToTso(oracle.xml.parser.v2.XMLDocument)
void b2b.RcvQueueListener.<init>()
void b2b.RcvQueueListener.main(java.lang.String[])
I've tried to save a row in the database with OracleXMLSave:
I use JDeveloper 3.1.1.2 with XDK 2.? and a local Oracle 8.1.6 unde NT.
// XML Doc:
<ROWSET>
<ROW NUM="1">
<CSM_NO>A29912</CSM_NO>
<CRE_DAY_CSM>03/18/2099</CRE_DAY_CSM>
<CSM_VOL_GRO_FRZ>59.89</CSM_VOL_GRO_FRZ>
</ROW>
</ROWSET>
// Set java enviroment:
Locale.setDefault(java.util.Locale.US);
// Save Data with XSU like:
OracleXMLSave sav =
new OracleXMLSave(cn.getConnection(), "consignment_t");
sav.insertXML(csmData);
Same Error when trying to...
(1) set date format for OracleXMLSave:
> sav.setDateFormat("DD/MM/YYYYY");
(2) set database parameter:
> nls_date_format='DD/MM/YYYY';
> nls_language='AMERICAN';
(3) set registry (winnt)
> nls_lang=AMERICAN_AMERICA.WEISO8859P1
Help would be appreciated.
Thanks in advance!
Matthias.

setDateFormat() is expecting a format mask that is valid for the java.text.SimpleDateFormat object.
So, just do:
setDateFormat("d/M/yyyy");
null

Error Unparseable date: "1999-05-03"

Hi All,
I am getting an unparseable date error. The database returns date of format "1999-05-03". I would like to format the date to yyyyMMdd format. My code is as follows
Date effectiveDt = new Date();
String dateFormat = "yyyyMMdd";
DateFormat format = new SimpleDateFormat(dateFormat);
          format.setLenient(false);
effectiveDt = (Date)format.parse(rs.getDate("ear_date_fr").toString());I tried another way by converting the date returned by the databse to SQL date and it still gives problem...
effectiveDt = (Date)format.parse(formUtil.returnSqlDate(rs.getDate("ear_date_fr").toString()).toString());formUtil.returnSqlDate code is actually as follows:
public static java.sql.Date returnSqlDate(String formDate) {
     java.util.Date utilDt = null;
     SimpleDateFormat df1 = new SimpleDateFormat("yyyyMMdd");
     try {
          utilDt = df1.parse(formDate);
     catch (ParseException pxp) {
          return null;
     return new java.sql.Date(utilDt.getDate());
}any help appreciated..
hepzi leon soon

If i use the following:
effectiveDt = rs.getDate("ear_date_fr");it returns the date good... like: 1999-05-03
but I just wanted to change the format to 19990503
that is where it is giving me error
at this moment i am settling down for the above mentioned format... i will appreciate of it could format the way I wanted it..
thanks a million
Hepzi

UNPARSEABLE DATE "0"

Hi,
when I Go to Operator,it gives me an error UNPARSEABLE DATE "0" and then the operator window opens.
what is this error unparseable date "0"? How i can solve this?
Thanx,
katukota

Hi katukota,
Its coz you have a filter defined in Operator that ODI doesn't recoginze. Please follow the below steps.
1. Open ODI Operator.
2. Click on the "Filter" button under the menu bar to open a window called "Define Filter".
3. In this window, clear the 2 "From" and "To" fields.
4. Close ODI Operator and all other open ODI GUI applications.
5. Reopen ODI Operator.
6. Uncheck the "Filter" checkbox in order to disable filtering.
7. Close ODI Operator and all other open ODI GUI applications.
8. Reopen ODI Operator.
Thanks,
G

Unparseable date: "" error in pi

Hi Experts,
Can anyone please help me for the below query
On the receiver side I need to get value as ' 2010-12-30TO8.00:00 '.
To achive this in graphical mapping i used date trans but i am geting error as unparseable date..
Regards
Akhil

Hi,
This error Usually Comes .,. when Ur Transform(Date Function) is expecting Date in Some Specific format and your are Providing Input Date in some Other format .
So Please Check , what is the format of Actual Coming Date and then Double Click on DateTransform Function and Match the format of source Date Format.
if both Not same , make both format same,
INPUT DATE - TRANSFORM DATE FUNCTION - OUTPUT DATE
TRANSFORM DATE Has 2 values ( Source Date and Target Date)
So INPUT date format and Source date format of DateTrans Function should match.
similarly
So OUTPUT date format and target date format of DateTrans Function should match.
Regards
Prabhat Sharma.

BI4.1 SP3 unparseable date error while scheduling

Hi,
We currently updated BI4.0 sp4 to BI4.1 sp3 on our test environment.
Im getting "Unparseable date" error only with scheduling on reports with a date prompt on BI4.1 SP3. On refreshing reports with date prompts without error.
The same report with date prompt scheduled on BI4.0 SP4 version. It schedules without error.
Could anyone help on this.
Thanks,
Youqin

Hi,
looks a little bit like this:
http://service.sap.com/sap/support/notes/1981477
Maybe you should open an Incident with the SAP Support to take a closer look into the issue and maybe to confirm that this is the Bug from above.
Regards
-Seb.

Date Transformation - "Unparseable date error"

Hi,
I am getting an "Unparseable date error", my source date format (from IDOC) is 27102006, in the target format it should be along with the time stamp like 27102006132010. I tried using the date transformation function and I am getting the following error:
RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /SiebelMessage/ListOfAssetManagement/ListOfAssetMgmt-Asset/AssetMgmt-Asset/InstallDate. The message is: Unparseable date: "27102006" .
solicit ur inputs!!!
Thanks & Regards
Viji

Hi,
Check your java code in Message Mapping, Check out whether you have declared the data typr exactly and again import the java code and activate the objects.
Regards
Agasthuri Doss

Unparseable date Error in Mapping in PI 7.1

I am working on Proxy to SOAP in PI 7.1 version
I have input date as 2009-05-14T17:00:00-07:00 from ECC and I need to split the date as 2009-05-14 and time as 17:00
please find the error in mapping below
Compilation of MM_ECC_to_ISO_ClaimSearch_Req successful Unparseable date: "2009-05-14T17:00:00-07:00" com.sap.aii.mappingtool.tf7.FunctionException: Unparseable date: "2009-05-14T17:00:00-07:00" at com.sap.aii.mappingtool.flib7.DateTransformer.convertDate(DateTransformer.java:72) at com.sap.aii.mappingtool.flib7.DateTransformer.getValue(DateTransformer.java:37) at com.sap.aii.mappingtool.flib7.If.getValue(If.java:35)
Please let me know how can I get rid of this error
Thanks
PR

>
PR wrote:
> I am working on Proxy to SOAP in PI 7.1 version
>
> I have input date as 2009-05-14T17:00:00-07:00 from ECC and I need to split the date as 2009-05-14 and time as 17:00
>
> please find the error in mapping below
>
> Compilation of MM_ECC_to_ISO_ClaimSearch_Req successful Unparseable date: "2009-05-14T17:00:00-07:00" com.sap.aii.mappingtool.tf7.FunctionException: Unparseable date: "2009-05-14T17:00:00-07:00" at com.sap.aii.mappingtool.flib7.DateTransformer.convertDate(DateTransformer.java:72) at com.sap.aii.mappingtool.flib7.DateTransformer.getValue(DateTransformer.java:37) at com.sap.aii.mappingtool.flib7.If.getValue(If.java:35)
>
>
> Please let me know how can I get rid of this error
>
> Thanks
> PR
You need to convert the source date format into that of target date format....you need to use standard DateTransform function available in Messaeg Mapping......

"Unparseable date" Error at reconciliation

Hi,
I am running recconiciliation task using
9.1. GTC DatabaseAppTable connector.
In the trusted source table (MS SQL) I have a column containing a date field in the following format: "10/31/1983 12:00:00 AM"
In the Connector configuration page, I have the following values set:
- Database Date format : MM/dd/yyyy
- Source Date Format : MM/dd/yyyy
When I run the Recon task , I get the following errors in the logs:
ERROR,18 Sep 2008 11:29:26,367,[XELLERATE.GC.FRAMEWORKRECONCILIATION],Reconciliation Encountered error:
Thor.API.Exceptions.tcAPIException: java.text.ParseException: Unparseable date: "10/31/1983"
Any idea on how I can resolve this issue ?
Thank you in advance

Hi,
Your Source Date Format should look like "MM/dd/yyyy hh:mm:ss a".
It should be same as your target system date format.If "MM/dd/yyyy hh:mm:ss a" didn't work then try to find out correct format for "10/31/1983 12:00:00 AM" .
Hope this will help.
Regards
Nitesh
Edited by: kunwar.nitesh on Sep 18, 2008 4:27 AM

Unparseable date error

hi,
i 've developed and application, in which at some point it compares dates. i have used win2k (english) version for development evn.
when the qa is testing it on non english w2k, they are getting unparseable date error.
===========
WARNUNG: java.text.ParseException: Unparseable date: "Fri Feb 01 10:04:25 CET 2003"
===========
the formatter i have used is "EEE MMM d HH:mm:ss z yyyy". so could this error be just because of non enlish version of w2k??? or something else??
thanks a in advance.
ri

Ok, so now I have found out where the problem was and I was able to correct it... here is how it went...
What was the code doing and why the error was there...
1. Code was stording a String as returned by new Date.toString(), which is always with locale en_US
2. When comparing the dates code was retreving the date from the file.
3. It was parsed using new SimpelDateFormate(String pattern).parse(dateobjcreatedfromStringobj) which returns the date with default OS Locale.
4. So now I had en_US date string being parsed by default OS Locale.
new SimpelDateFormate(String Pattern, new Locale("en","US")).parse(dateobjcreatedfromStringobj)5. This is what was generating unparseable date exception.
6. This was making the development comp to generate no exception as it is of locale en_US. And making the testing comp generate exception.
Hope this help out all the readers.
Thank you all.
Ri

Unparseable date error in 10.3.4.1

I have a report which is having Date Range Input parameters.
While running the report with the Date Range Input Parameter as NULL. It gives error on commnad prompt
[012810_052358158][][EXCEPTION] java.text.ParseException: Unparseable date: ""
at java.text.DateFormat.parse(DateFormat.java:335)
at oracle.apps.xdo.servlet.data.bind.AdvancedQueryBoundValue11.setBindVariables(AdvancedQueryBoundValue11.java:600)
at oracle.apps.xdo.servlet.data.bind.AdvancedQueryBoundValue11.getXML(AdvancedQueryBoundValue11.java:477)
at oracle.apps.xdo.servlet.ReportContextImplV11.getReportXMLData(ReportContextImplV11.java:408)
at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:231)
at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:82)
at oracle.apps.xdo.servlet.ReportImpl.renderBodyHTTP(ReportImpl.java:552)
at oracle.apps.xdo.servlet.ReportImpl.renderReportBodyHTTP(ReportImpl.java:255)
at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:270)
at oracle.apps.xdo.servlet.XDOServlet.writeReport(XDOServlet.java:250)
at oracle.apps.xdo.servlet.XDOServlet.doGet(XDOServlet.java:178)
at oracle.apps.xdo.servlet.XDOServlet.doPost(XDOServlet.java:201)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.apps.xdo.servlet.security.SecurityFilter.doFilter(SecurityFilter.java:94)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:621)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Same report is working fine is Date Input parameters have some date value.

fix the query to handle the null parameter for Date.
use NVL and use the columns from the table
or sysdate
or put a default value in the BIP report parameter.

Unparseable Date when Provisioning User from OIM to EBS HR

Hi expert,
I'm integrating E-Business Application using 'Oracle EBS HR Foundation User Management Connector version 9.1.0.4.0
with OIM version 11.1.1.5.0 (plus BP06) and I also set value of 'Manage HR record' to 'Yes'.
While provisioning user to EBS. It has some error occur about 'Unparseable date: "2013-05-24 00:00:00" '
############ ERROR ###########
[OIMCP.EBSUM] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: da74dbf2fbfe8d95:7819efa0:13eca22628a:-8000-0000000000012282,0] [APP: oim#11.1.1.3.0] oracle.iam.connectors.ebs.usermgmt.integration.EBSUserManagement : updatePerson
[2013-05-24T09:50:36.911+07:00] [wls_oim1] [ERROR] [] [OIMCP.EBSUM] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: da74dbf2fbfe8d95:7819efa0:13eca22628a:-8000-0000000000012282,0] [APP: oim#11.1.1.3.0] Failed to create employee
[2013-05-24T09:50:36.912+07:00] [wls_oim1] [ERROR] [] [OIMCP.EBSUM] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: da74dbf2fbfe8d95:7819efa0:13eca22628a:-8000-0000000000012282,0] [APP: oim#11.1.1.3.0] Description : Unparseable date: "2013-05-24 00:00:00"
[2013-05-24T09:50:36.912+07:00] [wls_oim1] [ERROR] [] [OIMCP.EBSUM] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: xelsysadm] [ecid: da74dbf2fbfe8d95:7819efa0:13eca22628a:-8000-0000000000012282,0] [APP: oim#11.1.1.3.0] java.text.ParseException: Unparseable date: "2013-05-24 00:00:00"
May it has some bug?
Thanks
Noraset.

Could you please write down what you have given in ITResource?
May be you are giving some wrong value in IT Resource.
Have you made chnages to OID Prov Lookup. If no check this link :
Re: Problem with OID Connector
And give a try !

Parse Exception : java.text.ParseException: Unparseable date

I have inherited a UDF in some mapping that on the whole, works okay...
but it throws an error after mapping a few dates:
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-18T00:00:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-23T23:59:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-18T00:00:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-23T23:59:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-18T00:00:00.000Z"
Parse Exception : java.text.ParseException: Unparseable date: "2010-03-23T23:59:00.000Z"
the first few map okay... then i get the exception.
the UDF is as follows:
public String convertDateTimeToUTC(String strDate, Container container) throws StreamTransformationException{
AbstractTrace trace = container.getTrace();
Date date=null;
SimpleDateFormat sdfSource = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ssZ");
try{
String dt = strDate;
date = sdfSource.parse(dt);
trace.addInfo("Local Date:"+date);
SimpleDateFormat sdfDestination = new SimpleDateFormat("yyyy-MM-dd'T'HH:mm:ss");
strDate = sdfDestination.format(date);
catch(ParseException pe){
trace.addInfo("Parse Exception : " + pe);
return strDate;
can anyone see why this fails after successfully mapping a few fields???

the first mapping works correctly...
then we reuse the same fields to map to the additional segments.
the context is correct as it is trying to pull the same fields in... it just throw the error with the same data in the same UDF/Function Library but for different segments! :o(
http://img199.imageshack.us/img199/3104/dateconversion.jpg
as you can see from the screenshot above, the mapping works in the first instance, then fails on subsequent nodes.

RFC Adapter : JCO_ERROR_CONVERSION : Unparseable date

Hi all,
We are working with RFC Adapter .
We are getting the following error in RWB -->
Component Monitoring --> Adapter Engine --> RFC
Adapter
" JCO_ERROR_CONVERSION: Date '01.12.2005' has a wrong format at field VALIDITYBEGIN: Unparseable date: "01.12.2005" "
- Error: 2006-02-03 11:17:13 IST: Message processed for interface BAPI_BANKDETAIL_CREATE: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$ConversionException: (122)
Can anyone please suggest how to resolve it .
Regards,
Shikha

Hi,
In which format the date is passed from XI?
If, it is of type Java Date there will be No conversion issue else if the it of Type <b>String</b> then the date should be in the format <b>YYYYMMDD</b>.
Hope this helps you.

Java.text.ParseException: Unparseable date: "2008-12-16 00:00:00"

Dear All WebLogic Guru,
Need your help about the error in our WebLogic Apps Server. Below is the related logs. Hope to hear from you soon.
========
Log snippet:
========
[15:48:02 ] [INFO] [NumberFormatException in TimesheetAddHandler:] null [delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAddHandler.perform(TimesheetOperatorAddHandler.java:77)]
java.text.ParseException: Unparseable date: "2008-12-16 00:00:00"
at java.text.DateFormat.parse(DateFormat.java:337)
at ejb.sessionBeans.gbms.bulkcrg.timesheet.TimesheetOperatorEJB.getOpsDttm(TimesheetOperatorEJB.java:1647)
at ejb.sessionBeans.gbms.bulkcrg.timesheet.TimesheetOperator_vn72b_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at ejb.sessionBeans.gbms.bulkcrg.timesheet.TimesheetOperator_vn72b_EOImpl.getOpsDttm(Unknown Source)
at delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAddHandler.perform(TimesheetOperatorAddHandler.java:383)
at delegate.RequestManager.perform(RequestManager.java:85)
at delegate.FrontController.processRequest(FrontController.java:241)
at delegate.FrontController.doPost(FrontController.java:378)
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:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at sg.com.jp.framework.sso.SingleSignOnFilter.doFilter(SingleSignOnFilter.java:121)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at sg.com.jp.util.xss.XssFilter.doFilter(XssFilter.java:57)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:153)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
[15:48:02 ] [INFO] [ScreenManager] Screen ID [TimesheetOperatorViewSvlt] mapped to [JSP/gbms/bulkcrg/timesheet/TimesheetOP_details.jsp] [delegate.ScreenManager.nextScreen(ScreenManager.java:60)]
[15:48:02 ] [INFO] Next Screen is : /JRPA(or ServletContext@27549577[app:47jrpa module:JRPA path:/JRPA spec-version:null],WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 Oracle WebLogic Server Module Dependencies 10.3 Thu Oct 28 06:03:12 PDT 2010 Oracle WebLogic Server on JRockit Virtual Edition Module Dependencies 10.3 Thu Sep 23 15:02:15 PDT 2010 )/JSP/gbms/bulkcrg/timesheet/TimesheetOP_details.jsp [delegate.FrontController.processRequest(FrontController.java:322)]
[15:48:02 ] [DEBUG] 2nd funcName in doFilter = TimesheetOP_details [uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:83)]
[15:48:02 ] [DEBUG] #########new admin framework ########## Function Code = [uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:92)]
[15:48:02 ] [DEBUG] Function Code = [uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:108)]
Status :S
[15:48:03 ] [DEBUG] Contains Function: true TimesheetOperatorSuperAmend [tags.ACLTag.doAfterBody(ACLTag.java:132)]
[15:48:03 ] [DEBUG] Contains Function: true TimesheetOperatorSuperDelete [tags.ACLTag.doAfterBody(ACLTag.java:132)]
[15:48:03 ] [DEBUG] Contains Function: true TimesheetOperatorClose [tags.ACLTag.doAfterBody(ACLTag.java:132)]
[15:48:31 ] [DEBUG] 2nd funcName in doFilter = TimesheetOperatorSuperAmend [uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:83)]
[15:48:31 ] [DEBUG] Function Code = F27052 [uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:108)]
[15:48:31 ] [DEBUG] Logged In?: true [delegate.helper.System.AuthenticationHandler.valid(AuthenticationHandler.java:571)]
[15:48:31 ] [INFO] [RequestManager] Request ID [TimesheetOperatorSuperAmend] mapped to [delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler] [delegate.RequestManager.perform(RequestManager.java:77)]
[15:48:31 ] [INFO] [RequestManager] delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler Created [delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler@66d4bf] [delegate.RequestManager.perform(RequestManager.java:82)]
[15:48:31 ] [INFO] performing request delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler@66d4bf [delegate.RequestManager.perform(RequestManager.java:84)]
[15:48:31 ] [INFO] [NumberFormatException in TimesheetAddHandler:] null [delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler.perform(TimesheetOperatorAmendHandler.java:96)]
[15:48:31 ] [ERROR] java.lang.StringIndexOutOfBoundsException: String index out of range: 2
at java.lang.String.substring(String.java:1934)
at delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler.perform(TimesheetOperatorAmendHandler.java:110)
at delegate.RequestManager.perform(RequestManager.java:85)
at delegate.FrontController.processRequest(FrontController.java:241)
at delegate.FrontController.doPost(FrontController.java:378)
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:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at sg.com.jp.framework.sso.SingleSignOnFilter.doFilter(SingleSignOnFilter.java:121)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at sg.com.jp.util.xss.XssFilter.doFilter(XssFilter.java:57)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at uiServlet.jponlinecharge.TxnLogFilter.doFilter(TxnLogFilter.java:153)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
[delegate.helper.gbms.bulkcrg.timesheet.TimesheetOperatorAmendHandler.perform(TimesheetOperatorAmendHandler.java:526)]
[15:48:31 ] [INFO] errorMessage ::: There are some error with your request. Please contact administrator if problem persists. [delegate.FrontController.processRequest(FrontController.java:311)]
=================
Application Server Specs:
=================
OS: Solaris10 x86
cat /etc/release
Oracle Solaris 10 9/10 s10x_u9wos_14a X86
Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
Assembled 11 August 2010
RAM: 8GB
HDD: 70GB
Apps Server: WebLogic Server Version: 10.3.4.0
Thank you and have a blessed day.
Best regards,
Albert

Hi,
Try this
The reason for this error is that the time format entered is not correct. It should be a date and 24-hour format expressed as mm/dd/yy hh:mm:ss. For example: 07/15/10 14:30:00.
The WebLogic Server 11g documentation gives instructions for Date/Time format. For details, please refer to
http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/pagehelp/Diagnosticsdiagnosticsviewmetricslogtabletitle.html
Solution
However, since you cannot open the Domain Log page again because the console hangs or reports a "Redirect Loop" error, you cannot modify this wrong time format on the console. To resolve this issue, please follow these steps:
Stop WebLogic Server.
Go to directory <Domain>/servers/<Server_Name>/data/console
Either open ConsolePreferences.xml and modify the value of startrange (and/or endrange) to a correctly formatted time, e.g. 07/15/10 14:30:00
OR
Delete ConsolePreferences.xml entirely.
Start Weblogic Server again.
Regards,
Kal

DateTrans Error: Unparseable date: ""

Similar Messages

Maybe you are looking for