Date Parsing

Hi,
I have a string in mm/dd/yyyyy format.
I want to convert this string in yyyy-mm-dd format.
I am using simpledateformat to convert it into a Date object.
It gives me "Thu Jan 26 00:00:00 EST 2006" this object.
When i parse it again using SimpleDateFormat to convert it into yyyy-mm-dd format it gives me
2006-00-26 it makes the month 00.
Please let me know whats the problem or any other better solution to achieve the same

public static String FORMAT = "MM/dd/yyyy";
     public static String YEAR_FORMAT = "yyyy-mm-dd";
     public static java.util.Date parseDate(String date){
          java.util.Date dateParsed = null;
          try{
               DateFormat date_formatter = new SimpleDateFormat(FORMAT);
               date_formatter.setLenient(false);
               dateParsed = date_formatter.parse(date);
               System.out.println("Inside the sco****************"+dateParsed);
          catch(ParseException e){
               e.printStackTrace();
          return dateParsed;
     public static String parseDateYear(String date){
          String dateParsed = null;
          try{
               SimpleDateFormat date_formatter = new SimpleDateFormat(YEAR_FORMAT);
               dateParsed = date_formatter.format(parseDate(date));
               System.out.println("Inside the sco****************"+dateParsed);
          catch(Exception e){
               e.printStackTrace();
          return dateParsed;
Thats how i m doing it

Similar Messages

  • Date parse error while importing users from OIM to OIA (SRM 5.0.3)

    Hi All,
    Env Details:
    OIA (SRM 5.0.3), Weblogic and Oracle 10g DB
    We have integrated OIM to OIA with extended attributes mapping by modifying iam-context.xml file to load users. Its done successfully. But when we map "Date" related attribute, its giving "Date Parsing error" and its not loading the users.
    We have tried loading users using flatFile mechanism, its also giving same result.
    Please suggest me. Thanks in Advance !!!
    Regards,
    Ravi G.

    Hi,
    Its a problem with OOB's OIMIAMSolution.class file, which is called while importing users from OIM. It used DateParse () conversion method only for all attributes which OIA attributes' name is ends with "Date". It defined, the conversion of date from (yyyy-MM-dd). So its expecting the input value should be in defined format(yyyy-MM-dd), if not, it gives a parse error.
    We found work around for this as follows,
    We have used other related OIA attribute which name ends other than "Date" string.
    Thanks,
    Ravi G.

  • Customer Data Parser

    Hi everyone,
    I'm trying to execute a CDP process but I get this error:
    02070E ERROR: Missing required field names in the input DDL. Occurred in Customer Data Parser - (CCDParser::CheckInputFieldNames).
    Does anyone knows what the problem could be?
    Thanks!

    This is best accomplished in the data reconstructor. The customer data parser willl break apart the house number, street name and all the addition address information into their own buckets. Then use the data reconstructor to rebuild the address, taking only the parts you need.
    Keep in mind that the additional information is crucial for correct delivery and postal discounts. You may want to think about the long-term uses of this data before you strip that information out.
    Steve Sarsfield

  • Input agent date parsing error

    Hi all,
    I am using input agent which points to documents which are exported from IPM 10g.in IPM 11g when i pass sample file for that documents which contain 18 fields one of which is date field.so when i pass input file through input agent which contain date value then i get date parsing error .
    please experts help me.
    Thanks in advance
    Edited by: 862821 on Oct 12, 2012 12:01 AM
    Edited by: 862821 on Oct 12, 2012 12:04 AM
    Edited by: 862821 on Oct 12, 2012 12:09 AM
    Edited by: 862821 on Oct 12, 2012 1:18 AM

    Hi srinath,
    I am using input agent which points to documents which are exported from IPM 10g.in IPM 11g when i pass sample file for that documents which contain 18 fields one of which is date field.so when i pass input file through input agent which contain date value then i get date parsing error . please suggest me solution.
    Thanks
    Edited by: 862821 on Oct 12, 2012 1:18 AM

  • Date parsing anyone?

    i am trying to parse this date string:
    "09:35:59 Aug 29 2005"
    using this code:
                                  SimpleDateFormat SDF = new SimpleDateFormat("hh:mm:ss MMM dd yyyy");
                                  Date time = SDF.parse(line,new ParsePosition(0));
                                  System.out.println("Date: " + time.toString());However, i keep getting a NULL value back for the Date Object time. What am I
    doing wrong? Anyone?? Bueller? Bueller?
    thanks!

    From the API:
    public Date parse(String text, ParsePosition pos)
    The method attempts to parse text starting at the index given by pos. If parsing succeeds, then the index of pos is updated to the index after the last character used (parsing does not necessarily use all characters up to the end of the string), and the parsed date is returned. The updated pos can be used to indicate the starting point for the next call to this method. If an error occurs, then the index of pos is not changed, the error index of pos is set to the index of the character where the error occurred, and null is returned.
    Maybe your Locale isn't English?
    Try this:
    System.out.println("Locale: " + java.util.Locale.getDefault());
    String line = "09:35:59 Aug 29 2005";
    SimpleDateFormat SDF = new SimpleDateFormat("hh:mm:ss MMM dd yyyy");
    ParsePosition parsePos = new ParsePosition(0);
    Date time = SDF.parse(line, parsePos);
    if (time == null)
       System.out.println("errorIndex is: " + parsePos.getErrorIndex());
    else
       System.out.println("Date: " + time.toString());
    }

  • BI services error "Data parsing failed, premature end of file".

    Hi all,
    we are facing issue while using BI services whenever we are trying to drill data its showing the error as "Data parsing failed contact your system administrator,premature end of file".
    please share with me if anyone has faced the same error anytime.
    thank in advance for your valuable suggestions.
    Thanks,
    karan.

    Hi,
    Please check whether the RFC imported by you contain the exact elements of XML.  I feel the RFC generated does not contain proper XML schema.
    Regards
    Krish

  • 3D data parsing error in Adobe Reader X 10.1.2

    Hello,
    I'm getting the annoying (and once fixed in version 9) 3D data parsing error with reader X 10.1.2 (on Windows 7 64bit), reading files that used to have no issues with previous versions (Italian locale). Anyone is having the same problem - or is able to give some suggestions? I've already tried to repair the installation, with no result. Any comment is greatly appreciated - this issue is causing major problems.
    Best regards,
    SV

    Hello,
    unfortunately it's a reserved document. I'll try to reproduce the issue with a different design and, if possible, I'll post a link to it.
    Thank you!
    Best regards,
    SV

  • 3D PDFs in Adobe Reader - "3D Data Parsing Error"

    Hi,
    I have just updated my adobe reader to 9.4.2 and I am regreting it already.  I use 3D PDFs on a regular basis and the ones I have that worked perfectly fine in 9.4.1 now do not work.  They come up with:
    "A 3D Data Parsing Error has occured"
    Does anyone know why this happens and particularly how to fix it, preferablly without going back to the older version of adobe reader.
    Many thanks.

    hey mark,
    i've got the same problem after updating to 9.402 this message appears and i cannot open the 3d scene.
    I found this (http://forums.adobe.com/message/2537356#2537356) thread and this link in it (http://communities.bentley.com/communities/everything_else_community/f/289/p/47047/106414. aspx#106414).
    hope that these can help you.
    regards frank

  • Applescript date parsing has changed

    i have been using a script i wrote 7 years ago to convert a string in mm/dd/yyyy format to an a/s date object, and as of last week it was working perfectly.
    tonite i just tried it and "11/05/2012" is parsed as 11may rather than 5nov...something changed the a/s parser's fmt...i suspect the xcode update i just did whenever it came out...
    <Edited by Host>

    yes, and apparently the xcode updte CHANGED MY LOCALIZATION SETTINGS without telling me:-P
    i've fixed the problem by avoiding a/s string2date coersion(what i shoulda done in the 1st place)-:
    -- dtp = [yyyy,mm,dd,hh,mm,ss]
    set dt to (current date)
    set day of dt to 1
    set year of dt to ((item 1 of dtp) as integer)
    set month of dt to ((item 2 of dtp) as integer)
    set day of dt to ((item 3 of dtp) as integer)
    set hours of dt to ((item 4 of dtp) as integer)
    set minutes of dt to ((item 5 of dtp) as integer)
    set seconds of dt to ((item 6 of dtp) as integer)

  • Date parsing problem inside java

    Hi,
    I'm passing a date string in format yyyy-MM-dd and trying to convert into a date value using below code by parsing the string. But, interestingly the output that i'm getting from dateVal is coming as - Tue Apr 17 00:00:00 GMT 2012 instead of 2012-04-17
    Not able to understand why so.
    String s1 = "2012-04-17";
    SimpleDateFormat outFmt = new SimpleDateFormat("yyyy-MM-dd");
    Date dateVal = outFmt.parse(s1);
    Please help.
    Regards,
    prodyut

    927428 wrote:
    String statement="select * from TIMINGTABLE WHERE COUNTRY = 'USA' AND ";
    statement=statement+"RE_DATE >= '"+dateVal+"'" ;
    df.format(dateVal) // will give you "2012-04-17"FYI : Use tags in start and end of your codes to post codes in this forum                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

  • 01.01.0000 date parse and format

    Could somebody explain is wrong here?
    SimpleDateFormat frm = new SimpleDateFormat("yyyyMMddHHmmss");  // formatter
    frm.setTimeZone(TimeZone.getTimeZone("UTC"));   // UTC time zone
    // --- No problem for the next code ---
    String inDate = "19700101000000";  // 01.01.1970 input date
    long stamp;
    try {
        stamp = frm.parse(inDate).getTime();   // input date in long
    } catch (ParseException ex) {
        System.out.println("Interruption");
        stamp = 0;
    String outDate = frm.format(stamp);  // output date
    System.out.println("inDate=>" + inDate + "_longDate=>" + stamp + "_outDate=>" + outDate);
    // --- No idea why next code is working wrongly ---
    inDate = "00000101000000";  // 01.01.0000 input date
    try {
        stamp = frm.parse(inDate).getTime();   // input date in long
    } catch (ParseException ex) {
        System.out.println("Interruption");
        stamp = 0;
    outDate = frm.format(stamp);  // output date
    System.out.println("inDate=>" + inDate + "_longDate=>" + stamp + "_outDate=>" + outDate);I try to parse and format the time stamp 01.01.0000 00:00:00. On the finish I have 01.01.0001 instead of the correct 01.01.0000
    inDate=>19700101000000_longDate=>0_outDate=>19700101000000
    inDate=>00000101000000_longDate=>-62167392000000_outDate=>00010101000000

    You are calling format with a long parameter. The only format that matches that signature that I can see would be Format.format(Object) assuming autoboxing is changing the long to a Long.
    Format.format(Object) eventually calls DateFormat.format(Object, StringBuffer, FieldPosition). I have never used this method so I am not sure what it does.
    Was your intention to actually call this method?
    See the following example:
    System.out.println("Test 1: " + frm.format(new Long(0l), new StringBuffer(), new FieldPosition(0)));  
    System.out.println("Test 2: " + frm.format(new Long(-62167392000000l), new StringBuffer(), new FieldPosition(0)));  
    Test 1: 19700101000000
    Test 2: 00010101000000Edited by: jbish on Apr 26, 2013 12:43 PM
    Edited by: jbish on Apr 26, 2013 1:09 PM

  • (non-lenient) date parse fails on specific day

    Hi,
    I need help figuring out his problem. I tried running code below using 1.5 and I always get an "unparseable date" exception.
    String DATE_FORMAT = "yyyy-MM-dd HH:mm:ss";
    String date = "2008-03-09 02:00:00";
    SimpleDateFormat sdf = new SimpleDateFormat(DATE_FORMAT);
    sdf.setLenient(false);
    Date d = sdf.parse(date);
    System.out.println(d);If the call to setLenient is omitted, the parse succeeds but the prints out "Sun Mar 09 03:00:00 EDT 2008" instead of the expected "Sun Mar 09 02:00:00 EDT 2008".
    Interestingly enough, the parse succeeds for other dates (with lenient set to false). Examples I tried were ""2008-03-09 01:00:00", "2008-03-09 03:00:00", "2008-02-09 02:00:00", ""2008-04-09 02:00:00".
    I need help in figuring this out. Is this a bug in the jdk itself or am I missing something.
    Btw, I'm using 1.5.0_13.
    Thanks.
    -Anthony

    Wow, that was dumb of me to not think of that. I verified it and you're right. DST change was on Mar-09-2008 02:00:00.
    Thanks masijade. One less headache for me.
    - Anthony

  • SAP ER Connector 9.1.2.2  IDOC Data Parser Error to read custom segments

    Hi,
    We are in the trouble to find out the root cause of the issue in SAP Employee Reconciliation Connector 9.1.2.2 for processing idoc. As per our requirment, we need to retreive the field values in the custom segments(ZHR) other than the base segments(E2P). As we tried a lot for the couple of days and identified the custom segment filednames are not parsing by SAP HRMS Listener (in tRFC mode of communication).. The same idoc file works properly to retreive the value in the reconciliation event at "SAP User Reconciliation" (in file port). Its strange why it is not reading the idoc through listener. Will there be any db refresh or any configuration on SAP system required to do in tRFC mode of idoc file transfer?
    OIM Log :-
    INFO,11 Apr 2013 12:16:53,513,[OIMCP.SAPH:info],oracle.iam.connectors.sap.common.parser.HRMDAParser : parse() : process_IDOC ROOT:General root segment
    DEBUG,11 Apr 2013 12:16:53,514,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: STARTED
    DEBUG,11 Apr 2013 12:16:53,515,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue() : returned value is: 12507708
    DEBUG,11 Apr 2013 12:16:53,516,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: FINISHED
    DEBUG,11 Apr 2013 12:16:53,516,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isValidRecord():: FINISHED
    DEBUG,11 Apr 2013 12:16:53,517,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isValidRecord():: FINISHED
    DEBUG,11 Apr 2013 12:16:53,518,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isValidRecord() : return value is TRUE
    DEBUG,11 Apr 2013 12:16:53,518,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isDeletedUser():: STARTED
    DEBUG,11 Apr 2013 12:16:53,519,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isDeletedUser():: FINISHED
    DEBUG,11 Apr 2013 12:16:53,520,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
    DEBUG,11 Apr 2013 12:16:53,520,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
    DEBUG,11 Apr 2013 12:16:53,521,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : Personnel Number set to 12507708
    DEBUG,11 Apr 2013 12:16:53,522,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: FINISHED
    DEBUG,11 Apr 2013 12:16:53,522,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
    DEBUG,11 Apr 2013 12:16:53,523,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
    DEBUG,11 Apr 2013 12:16:53,524,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: FINISHED
    DEBUG,11 Apr 2013 12:16:53,524,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
    DEBUG,11 Apr 2013 12:16:53,525,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: STARTED
    DEBUG,11 Apr 2013 12:16:53,526,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue() : returned value is: Sat May 25 00:00:00 PDT 1985
    DEBUG,11 Apr 2013 12:16:53,527,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: FINISHED
    DEBUG,11 Apr 2013 12:16:53,529,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
    DEBUG,11 Apr 2013 12:16:53,529,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : First Name set to SRI
    DEBUG,11 Apr 2013 12:16:53,530,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : Middle Name set to RAM
    DEBUG,11 Apr 2013 12:16:53,531,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : Last Name set to RAM
    DEBUG,11 Apr 2013 12:16:53,531,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: FINISHED
    DEBUG,11 Apr 2013 12:16:53,532,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
    DEBUG,11 Apr 2013 12:16:53,533,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: STARTED
    INFO,11 Apr 2013 12:16:53,534,[OIMCP.SAPH:info],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue() : (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "BEGDA" is not a member of IDocRecord "ZHR_OIM000".
    DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=BEGDA
    DEBUG,11 Apr 2013 12:16:53,534,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
    ERROR,11 Apr 2013 12:16:53,535,[OIMCP.SAPH:error],====================================================
    ERROR,11 Apr 2013 12:16:53,536,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
    DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
    ERROR,11 Apr 2013 12:16:53,537,[OIMCP.SAPH:error],====================================================
    ERROR,11 Apr 2013 12:16:53,538,[OIMCP.SAPH:error],================= Start Stack Trace =======================
    ERROR,11 Apr 2013 12:16:53,539,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord()
    ERROR,11 Apr 2013 12:16:53,539,[OIMCP.SAPH:error],(5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
    DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
    ERROR,11 Apr 2013 12:16:53,540,[OIMCP.SAPH:error],Description : (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
    DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
    ERROR,11 Apr 2013 12:16:53,541,[OIMCP.SAPH:error],com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
    DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
    at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
    at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
    at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
    at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
    at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
    at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
    at java.lang.Thread.run(Thread.java:662)
    ERROR,11 Apr 2013 12:16:53,542,[OIMCP.SAPH:error],================= End Stack Trace =======================
    ERROR,11 Apr 2013 12:16:53,542,[OIMCP.SAPH:error],====================================================
    ERROR,11 Apr 2013 12:16:53,543,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :
    ERROR,11 Apr 2013 12:16:53,544,[OIMCP.SAPH:error],====================================================
    ERROR,11 Apr 2013 12:16:53,545,[OIMCP.SAPH:error],================= Start Stack Trace =======================
    ERROR,11 Apr 2013 12:16:53,546,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment()
    ERROR,11 Apr 2013 12:16:53,546,[OIMCP.SAPH:error],
    ERROR,11 Apr 2013 12:16:53,547,[OIMCP.SAPH:error],Description :
    ERROR,11 Apr 2013 12:16:53,547,[OIMCP.SAPH:error],oracle.iam.connectors.common.ConnectorException:
    at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
    at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
    at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
    at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
    DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
    at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
    at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
    ... 18 more
    ERROR,11 Apr 2013 12:16:53,548,[OIMCP.SAPH:error],================= End Stack Trace =======================
    ERROR,11 Apr 2013 12:16:53,549,[OIMCP.SAPH:error],====================================================
    ERROR,11 Apr 2013 12:16:53,550,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :
    ERROR,11 Apr 2013 12:16:53,550,[OIMCP.SAPH:error],====================================================
    ERROR,11 Apr 2013 12:16:53,552,[OIMCP.SAPH:error],================= Start Stack Trace =======================
    ERROR,11 Apr 2013 12:16:53,552,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment()
    ERROR,11 Apr 2013 12:16:53,553,[OIMCP.SAPH:error],
    ERROR,11 Apr 2013 12:16:53,554,[OIMCP.SAPH:error],Description :
    ERROR,11 Apr 2013 12:16:53,554,[OIMCP.SAPH:error],oracle.iam.connectors.common.ConnectorException:
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
    at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
    at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
    at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: oracle.iam.connectors.common.ConnectorException:
    at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
    ... 17 more
    Caused by: com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
    DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
    at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
    at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
    ... 18 more
    ERROR,11 Apr 2013 12:16:53,555,[OIMCP.SAPH:error],================= End Stack Trace =======================
    ERROR,11 Apr 2013 12:16:53,556,[OIMCP.SAPH:error],====================================================
    ERROR,11 Apr 2013 12:16:53,556,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :
    ERROR,11 Apr 2013 12:16:53,557,[OIMCP.SAPH:error],====================================================
    ERROR,11 Apr 2013 12:16:53,558,[OIMCP.SAPH:error],================= Start Stack Trace =======================
    ERROR,11 Apr 2013 12:16:53,559,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment()
    ERROR,11 Apr 2013 12:16:53,559,[OIMCP.SAPH:error],
    ERROR,11 Apr 2013 12:16:53,560,[OIMCP.SAPH:error],Description :
    ERROR,11 Apr 2013 12:16:53,561,[OIMCP.SAPH:error],oracle.iam.connectors.common.ConnectorException:
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
    at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
    at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
    at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
    at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
    at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
    at java.lang.Thread.run(Thread.java:662)
    Caused by: oracle.iam.connectors.common.ConnectorException:
    at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
    ... 16 more
    Caused by: oracle.iam.connectors.common.ConnectorException:
    at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
    ... 17 more
    Caused by: com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
    DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
    at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
    at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
    ... 18 more
    ERROR,11 Apr 2013 12:16:53,561,[OIMCP.SAPH:error],================= End Stack Trace =======================
    ERROR,11 Apr 2013 12:16:53,562,[OIMCP.SAPH:error],====================================================
    ERROR,11 Apr 2013 12:16:53,563,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :

    Now i am able to configure but i am seeing this error
    java.lang.UnsatisfiedLinkError: /opt/Oracle/jco/libsapjco3.so: /opt/Oracle/jco/libsapjco3.so: ELF file data encoding not little-endian (Possible cause: endianness mismatch)
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807)
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1732)
    at java.lang.Runtime.loadLibrary0(Runtime.java:823)
    at java.lang.System.loadLibrary(System.java:1028)
    at com.sap.conn.jco.rt.DefaultJCoRuntime.loadLibrary(DefaultJCoRuntime.java:444)
    at com.sap.conn.jco.rt.DefaultJCoRuntime.registerNativeMethods(DefaultJCoRuntime.java:310)
    at com.sap.conn.jco.rt.JCoRuntime.registerNatives(JCoRuntime.java:1027)
    at com.sap.conn.rfc.driver.CpicDriver.<clinit>(CpicDriver.java:956)
    at com.sap.conn.rfc.engine.DefaultRfcRuntime.getVersion(DefaultRfcRuntime.java:43)
    at com.sap.conn.rfc.api.RfcApi.RfcGetVersion(RfcApi.java:261)
    at com.sap.conn.jco.rt.MiddlewareJavaRfc.<clinit>(MiddlewareJavaRfc.java:198)
    at com.sap.conn.jco.rt.DefaultJCoRuntime.initialize(DefaultJCoRuntime.java:75)
    at com.sap.conn.jco.rt.JCoRuntimeFactory.<clinit>(JCoRuntimeFactory.java:23)
    at com.sap.conn.jco.rt.About.<init>(About.java:42)
    at com.sap.conn.jco.rt.About.main(About.java:81)

  • Date parsing with Arabic Locale returning null

    Hi all,
    We are encountering a strange problem with Java SimpleDateFormat class when the Locale is set to Arabic.Here is the code.
    Calendar cal = null;
    java.util.Date dt = null;
    Locale locale = new Locale("ar","SA");
    System.out.println(locale.getDisplayCountry());
    System.out.println(locale.getDisplayLanguage());
    Locale.setDefault(locale) ;
    SimpleDateFormat dateFmt = new SimpleDateFormat("yyyy-MM-dd HH:mm");
    ParsePosition parsePos = new ParsePosition(0);
    String tzID = "PST";
    dt = dateFmt.parse("1999-01-01 00:00:00.0"+ " " + tzID, parsePos);
    System.out.println("TimeZoneID is"+tzID);
    System.out.println("Date is"+dt);
    here we get dt as null.Can any one plz give me a solution for this.
    Thanx in advance.
    Regards,
    Ashok

    In the pattern "yyyy-MM-dd HH:mm" the part "-" seems not to be parsed. Did you search the Bug Database?
    (Try using the following modified version of the code to see where the parsing error occurs.)
    Calendar cal = null;
    java.util.Date dt = null;
    Locale locale = new Locale("ar","SA");
    System.out.println(locale.getDisplayCountry());
    System.out.println(locale.getDisplayLanguage());
    Locale.setDefault(locale) ;
    SimpleDateFormat dateFmt = new SimpleDateFormat("yyyy-MM-dd HH:mm");
    ParsePosition parsePos = new ParsePosition(0);
    String tzID = "PST";
    dt = dateFmt.parse("2003-02-20 00:00", parsePos);
    if (parsePos.getErrorIndex()==-1){
    System.out.println("TimeZoneID is "+tzID);
    System.out.println("Date is "+dt);
    }else{
      System.out.print("Parsing Error at ");// in this case error occurs at 5, i.e., the place immediately after the first appearance of '-'.
      System.out.println(String.valueOf(parsePos.getErrorIndex()));
    }

  • Date parsing problem

    Hello!
    I am trying to parse stock-csv data from finance.yahoo.com.
    One line looks like this one:
    13-May-05,95.00,96.30,94.10,96.19,34627,87.50
    I extracted the date "13-May-05" and now I want to parse it.
    I tried:
    x = "13-May-05";
    - DateFormat df = DateFormat.getDateInstance(DateFormat.MEDIUM,Locale.US);
    df.parse(x);
    - DateFormat df = new SimpleDateFormat("d-MMM-yy");
    df.parse(x);
    Both things did not work ("Unparseable date: "13-May-05"").
    Can someone see what's wrong?
    Thank you,

    yeah,, true, but there also seem to be some here
    otherwise (many times I found a better solution on my
    own,, but I usually go late at night.) At any rate,
    the parsing is basically what I said, only my system
    is-if it don't work, hard code it. It's stupidity at
    its finest, and total lack of confidence.
    hey-you guys really should look into what I posted on
    the 'skins' post--you would find it interesting-and
    also give you insight into finding out about java and
    ms-and why ms actually hates java-including why they
    made their own vm for java, and why they developed a
    java-like VB language, called VJ++, for their
    VisualStudio, in an attempt to drive java programmers
    from here to there. (unsuccessfully so far)Dude, I have no idea what you're saying, but pass me the bong and the Doritos.

Maybe you are looking for