ORA-01830Date format picture end before converting entire input string

Hi Guys,
we have two db env one is dev and one is qa.Both the envs are running on same data base version and in both the envs the nls_date_format parameter are same and they are 'DD-MON-YY' format only.But when I am executing the same following sequel statement my dev env is fetching proper data without any issues but my qa env is erroring out with the mentioned error.
I am enclosing the sequel I am using
SELECT TPTRJO1.JOURNAL_ENTRY_ID
FROM TRANSACTION_JOURNAL TPTRJO1,
JOURNAL_CASH_DRAWER TPJCD1
WHERE (TPJCD1.CASH_DRAWER_ID = 5010639.0)
AND (TPJCD1.DRAWER_SEQ = 5.0)
AND (TPJCD1.CASH_DRAWER_DATE = TO_DATE('2011-09-13 00:00:00','yyyy-MM-dd'))
AND (TPTRJO1.JOURNAL_ENTRY_ID = TPJCD1.JOURNAL_ENTRY_ID)
AND (TPTRJO1.TRANSACTION_ID = 595.0)
However as per the logic it should error out in both the envs due to the date format and the actual data used in the input.
What could be the possible difference in between the tow db envs?
Please share your thoughts.
Any suggestions are highly appreciated.
Thank you and expecting an early response

I guess you have different data in your dev environment.
If there is no record with TPJCD1.CASH_DRAWER_ID = 5010639.0,
the expression "TO_DATE('2011-09-13 00:00:00','yyyy-MM-dd')"
will never be evaluated.
Here is my test case where "1 = 0" prevents the date from being evaluated:SQL>SELECT *
  2    FROM all_objects
  3   WHERE created > TO_DATE('2011-09-13 00:00:00', 'yyyy-MM-dd');
WHERE created > TO_DATE('2011-09-13 00:00:00', 'yyyy-MM-dd')
ERROR at line 3:
ORA-01830: date format picture ends before converting entire input string
SQL>
SQL>SELECT *
  2    FROM all_objects
  3   WHERE 1 = 0 AND created > TO_DATE('2011-09-13 00:00:00', 'yyyy-MM-dd');
no rows selectedUrs

Similar Messages

  • ORA-01830: date format picture ends before converting entire input string at OCI call OCIStmtFetch

    Hi all,
    We are trying to create a BIP Data Model based on an Answer, but after selecting report, it hangs when I try to Apply to create a query based on Oracle BI. When I try to open the query in aswers, going to results tab I'm getting this error (OBIEE 11.1.1.6.2):
    ORA-01830: date format picture ends before converting entire input string at OCI call OCIStmtFetch
    I suppose that BIP data model is not able to create it because of this error. But this answer is working fine inside dashboards, etc. It only does not work when editing it. Query is doing something like this: "USING "- Collection Attributes"."Due Date" >= TIMESTAMPADD(SQL_TSI_DAY, -30, CAST ('01/04/2009' AS DATE))"
    Any ideas?

    Solved watching date format in generated SQL and changing default date format in presentation variables default values inside criteria according to SQL format.

  • Date Format Picture ends before converting entire input string..

    Hi all
    i am creating a report in 10g.. in which i want to convert Emp_lump_sum (number)  to character .I have created a formula column in which i have written a function in the formula column and assign that formula column to the text field in which i want the result.
    when the report run i get the following error....
    ORA-01830: date format picture ends before converting entire input string..
    i have tried with a attribute EMP_NO (Varchar2(30)), it shows the result but when i add EMP_LUMP_SUM (NUMBER) , it show the above error. on the database side i get the same error.
    Database : 11g
    OS :     Windows server 2003
    reports   : 10g
    any help will be thankful..
    Function i wrote behind the formula coloumn is..
    function CF_1Formula return CHAR is
    xy varchar2(100);
    begin
      select to_char(to_date(emp_lump_sum,'j'),'jsp') into xy from fms_111_form4_tr;
        return xy;
        --xy := f_19;
    end;

    Hello:
    Try to use a database function and call it from reports.
    Regards,

  • [b]error: date format picture ends before converting entire input string[/b

    when I insert some data into a table, which got a date field, it pops up this error.
    insert inot test
    values
    ('31-mar-2004 0:22:22')
    after i take away the time part from the string, it works ok, seems the time is not recognized
    i tried to put a line at the beginning, as below:
    alter session set nls_date_format = "dd-mm-yyyy hh24:mi:ss"
    then, it works, but it still comes out in the form "dd-mon-yyyy hh24:mi:ss"

    I would NEVER rely on implicit datatype conversion, been burnt too often.
    So go the explicit way and your are independent of global settings :
    insert into table test values (to_date('31-03-2004 00:22:22' , 'dd-mm-yyyy hh24:mi:ss') ) ;
    or
    insert into table test (timefield) values (to_date('31-mar-2004 00:22:22' , 'dd-mon-yyyy hh24:mi:ss') ) ;
    first solution is better, 'mar' is already language dependent.
    Same concept holds true for generating output from date variables, always use explicit conversion.

  • Row 78: ORA-01830: date format picture ends before converting entire input

    Hi Everyone,
    I am using SQL Developer and when i am trying to enter the date field into the a column i am getting an error as the one mentioned in the subject. I know i am entering some incorrect format of the date. But i just cant figure out what's the correct format! I checked my SQL Developer's settings where in the NLS Parameters segment I can see the date format given as DD-MON-RR HH.MI.SSXFF AM. I am trying to set a value of something like: "02-Apr-2011 07:12:55 AM". But i still see that error. Please help me in setting the correct value. I have done all the entry and only the date segment is left!

    hell_storm2004 wrote:
    Hi Everyone,
    I am using SQL Developer and when i am trying to enter the date field into the a column i am getting an error as the one mentioned in the subject. I know i am entering some incorrect format of the date. But i just cant figure out what's the correct format! I checked my SQL Developer's settings where in the NLS Parameters segment I can see the date format given as DD-MON-RR HH.MI.SSXFF AM. I am trying to set a value of something like: "02-Apr-2011 07:12:55 AM". But i still see that error. Please help me in setting the correct value. I have done all the entry and only the date segment is left!That usually means you're trying to do something like:
    to_date('12/07/2006 22:09:13', 'dd/mm/yyyy')Note that the format specified (dd/mm/yyyy) does not include the time part, so Oracle does not know what to do with that bit of it. You must make sure your date (or timestamp) format matches the string format.
    In your case, that would be:
    to_date('02-Apr-2011 07:12:55 AM', 'dd-Mon-yyyy hh:mi:ss AM')If you're not explicitly using TO_DATE or TO_TIMESTAMP to convert your string into a date/timestamp, then you should be!!
    Once you've converted your string, if you're wanting to remove the time part, you can use the TRUNC() function.
    Edited by: Boneist on 28-Aug-2009 09:21

  • SQL Loader Error : ORA-01830: date format picture ends before converting en

    I am inserting following data
    BES101706     M.E. Deals     7     10/17/2006
    through control file :
    LOAD DATA
    APPEND
    INTO TABLE abc_temp
    FIELDS TERMINATED BY ' '
    TRAILING NULLCOLS
    (BATCH_NAME               ,
    SUPPLIER_NAME          ,
    SUPPLIER_NBR          ,
    INV_DATE "to_date(substr(:INV_DATE,1,10),'MM/DD/YYYY' )"
    But I am getting this error:
    ORA-01830: date format picture ends before converting entire input string
    inv_data is a date field in the database.

    I think it has to do with data format.Exactly.
    You have
    BES101706*M.E.*Deals*7*10/17/2006
    I replace each space with an asterisk. You have 5 columns according to your spec (terminated by '<space>')
    SQL Loader doesn't know that M.E. Deals is the supplier name.
    It's trying to convert 7 as the date.

  • XML SELECT error ORA-01830: date format picture ends before converting enti

    Apologies, If I have to open a new thread. I have a similar problem and would be grateful if you can help:
    Created a view based on an xsd. View works fine. However when selecting data from the view, the xml output is scrambled. On search found there is a pretty print function which can be added when creating the view: .extract('/*') as:
    ).extract('/*')
    as RBid
    from Balit_Submissions bs
    Again the view gets created successfully. But when doing the same select from it get the error:
    ERROR:
    ORA-01830: date format picture ends before converting entire input string
    I have narrowed it down to the .xsd definition of the tag: <xsd:element name="CreationDateTime" type="ecc:MessageDateTimeType">
    In the view, CreationDateTime is selected as follows:
    ,XMLelement("CreationDateTime",xmlattributes(to_char(bs.creation_datetime,'yyyy-mm-dd"T"hh:mi:ss"Z"') as "v"))
    where the column bs.creation_datetime is Oracle data type DATE.
    The MessageDateTimeType is defined in Oracle as a timestamp.
    Any hints to overcome this.
    Using: Oracle Database 10g Enterprise Edition Release 10.1.0.5.0 - Production
    I will paste the full .xsd and view if required.
    Thanks
    James Sathiaraj

    Indeed a small test case would be great. Not sure if I could reproduce - have touched 10.1.0.5 in 4, 5 years...

  • APEX_ITEM.DATE_POPUP  and ORA-01830: date format picture ends before conver

    Hi,
    I am using apex_item.date_popup for a custom tabular form.
    When I load the form with the default sysdate it works ok. However when the user submits an invalid date I get: ORA-01830: date format picture ends before converting entire input string.
    Ex: apex_item.date_popup (2, NULL, ac.my_date, :f_date_format, LENGTH (:f_date_format), LENGTH (:f_date_format),NULL)
    Where f_date_format is 'DD-MON-YYYY'...
    If I enter 'abc' in this field and click submit, my validations find that it is an invalid date, so I reload the page with ac.my_date is the value that the user entered (ex: 'abc'). This will cause the error...
    I understand why the error occurs, but is it correct that it does happen? Any ways around this?
    Thank you.

    Hi Scott,
    I found the work around. I'll try to make this code more readable later on.
    1: Create a HTML region with the following code:
    Note: F02 is the "Column" for my date field:
    <script type="text/javascript">
    function genCalF02(pRowNum,pYyyy,pMm,pSecurityGroupId)
    elemArrLen = 0;
    if (document.forms[0].f02.length) {
    elemArrLen = document.forms[0].f02.length;
    elemArrLen = '&F_DATE_FORMAT.'.length;
    pMm = '' + pMm;
    if (pMm.length == 1)
    pMm = '0' + pMm;
    w = open("wwv_flow_utilities.show_as_popup_calendar" +
    "?p_element_index=" + escape('f02' + '['.substr(0,elemArrLen) + pRowNum + ']'.substr(0,elemArrLen)) +
    "&p_form_index=" + escape('0') +
    "&p_date_format=" + escape('&F_DATE_FORMAT.') +
    "&p_application_format=" + escape('Y') +
    "&p_bgcolor=" + escape('#666666') +
    "&p_dd=" + escape('') +
    "&p_hh=" + escape('') +
    "&p_mi=" + escape('') +
    "&p_pm=" + escape('') +
    "&p_yyyy=" + escape(pYyyy) +
    "&p_lang=" + escape('') +
    "&p_application_id=" + escape('&APP_ID.') +
    "&p_security_group_id=" + escape(pSecurityGroupId) +
    "&p_mm=" + escape(pMm),
    "winLov",
    "Scrollbars=no,resizable=no,width=258,height=210");
    // TODO "?p_element_index=" + escape('f02' + '['.substr(0,elemArrLen) + pRowNum.substr(0,elemArrLen) + ']'.substr(0,elemArrLen)) +
    if (w.opener == null)
    w.opener = self;
    w.focus();
    </script>
    In you're query (or how ever else you are calling apex_item.date_popup)... use something like this instead:
    WHEN is_valid_date(my_date) = 'Y' THEN
    apex_item.text (2,
    my_date,
    LENGTH (:f_date_format),
    LENGTH (:f_date_format),
    NULL,
    NULL,
    NULL
    ) || '<a href="javascript:genCalF02(' || (ROWNUM - 1) || ',' || TO_CHAR (TO_DATE (my_date, :f_date_format), 'YYYY') || ','
    || TO_CHAR (TO_DATE (my_date, :f_date_format), 'MM') || ',' || apex_custom_auth.get_security_group_id
    || ')"><img src="/i/asfdcldr.gif" align="middle" alt="Calendar"/></a>'
    ELSE
    apex_item.text (2,
    my_date,
    LENGTH (:f_date_format),
    LENGTH (:f_date_format),
    NULL,
    NULL,
    NULL
    ) || '<a href="javascript:genCalF02(' || (ROWNUM - 1) || ',' || TO_CHAR (SYSDATE, 'YYYY') || ','
    || TO_CHAR (SYSDATE, 'MM') || ',' || apex_custom_auth.get_security_group_id
    || ')"><img src="/i/asfdcldr.gif" align="middle" alt="Calendar"/></a>'
    END as xxx
    This creates the text box with a date popup window beside it.
    Again, this is not pretty code which can probably be done in a function etc.
    Hope this helps anyone else who has the same issue.
    Martin

  • Error when Insert with to_timestamp, data format picture ends before....

    Hy,
    I've got a problem when we insert a timestamp to a db.
    When I try to start an insert code I get this error:
    SQL-Error: ORA-01830: "data format picture ends before converting entire input string"
    Insert into ABC_123("dtstamp") values (to_timestamp('31.05.13 09:30:05,000748000 +01:00','DD.MM.RR HH24:MI:SSXFF'));
    with this language settings
    National Language Support
    National
    Language Parameter
    Value
    NLS_CALENDAR
    GREGORIAN
    NLS_CHARACTERSET
    WE8MSWIN1252
    NLS_COMP
    BINARY
    NLS_CURRENCY

    NLS_DATE_FORMAT
    DD.MM.RR
    NLS_DATE_LANGUAGE
    GERMAN
    NLS_DUAL_CURRENCY

    NLS_ISO_CURRENCY
    GERMANY
    NLS_LANGUAGE
    GERMAN
    NLS_LENGTH_SEMANTICS
    BYTE
    NLS_NCHAR_CHARACTERSET
    AL16UTF16
    NLS_NCHAR_CONV_EXCP
    FALSE
    NLS_NUMERIC_CHARACTERS
    NLS_SORT
    GERMAN
    NLS_TERRITORY
    GERMANY
    NLS_TIME_FORMAT
    HH24:MI:SSXFF
    NLS_TIMESTAMP_FORMAT
    DD.MM.RR HH24:MI:SSXFF
    NLS_TIMESTAMP_TZ_FORMAT
    DD.MM.RR HH24:MI:SSXFF TZR
    NLS_TIME_TZ_FORMAT
    HH24:MI:SSXFF TZR
    I didn't see the error. Maybe somebody can help me.
    Thx
    Felix

    ef5fe917-5142-4425-a464-94ab111ed87a wrote:
    Hy,
    I've got a problem when we insert a timestamp to a db.
    When I try to start an insert code I get this error:
    SQL-Error: ORA-01830: "data format picture ends before converting entire input string"
    Insert into ABC_123("dtstamp") values (to_timestamp('31.05.13 09:30:05,000748000 +01:00','DD.MM.RR HH24:MI:SSXFF'));
    with this language settings
    National Language Support
    National
    Language Parameter
    Value
    NLS_CALENDAR
    GREGORIAN
    NLS_CHARACTERSET
    WE8MSWIN1252
    NLS_COMP
    BINARY
    NLS_CURRENCY

    NLS_DATE_FORMAT
    DD.MM.RR
    NLS_DATE_LANGUAGE
    GERMAN
    NLS_DUAL_CURRENCY

    NLS_ISO_CURRENCY
    GERMANY
    NLS_LANGUAGE
    GERMAN
    NLS_LENGTH_SEMANTICS
    BYTE
    NLS_NCHAR_CHARACTERSET
    AL16UTF16
    NLS_NCHAR_CONV_EXCP
    FALSE
    NLS_NUMERIC_CHARACTERS
    NLS_SORT
    GERMAN
    NLS_TERRITORY
    GERMANY
    NLS_TIME_FORMAT
    HH24:MI:SSXFF
    NLS_TIMESTAMP_FORMAT
    DD.MM.RR HH24:MI:SSXFF
    NLS_TIMESTAMP_TZ_FORMAT
    DD.MM.RR HH24:MI:SSXFF TZR
    NLS_TIME_TZ_FORMAT
    HH24:MI:SSXFF TZR
    I didn't see the error. Maybe somebody can help me.
    Thx
    Felix
    Insert into ABC_123("dtstamp") values (to_timestamp('31.05.13 09:30:05,000748000 +01:00','DD.MM.RR HH24:MI:SSXFF'));
                                                          |  |  |  |  |  |             |
                                                          |  |  |  |  |  |             +--????
                                                          |  |  |  |  |  +----SS
                                                          |  |  |  |  |
                                                          |  |  |  |  +-----MI
                                                          |  |  |  |
                                                          |  |  |  +-----HH24
                                                          |  |  |
                                                          |  |  +----RR
                                                          |  |
                                                          |  +----MM
                                                          |
                                                          +----DD
    The error message means exactly what it says.  Your data format string doesn't account for everything in your data string.

  • Pls Help with date format picture ends ......error

    Hi Everyone,
       I am getting the following error when I run my crystal report.
    Failed to retrieve data from the database.
    Details: HY000:[DataDirect][ODBC Oracle driver][Oracle]ORA-01830: date format picture ends before converting entire input string
    [Database Vendor Code: 1830]
       I am using SQL Command for my report and in the command  my date fields are of "Date" datatype.
       I am using Crystal Reports XI R2,driver - CR Oracle ODBC Driver 5.1
       Any help is greatly appreciated.
    Thanks in advance
    My SQL Command is as follows:
    <
    with MAXNEWSTAT as
    (select
    /--Added by HAN--/
    HRHISTORY.COMPANY,
    HRHISTORY.EMPLOYEE,
    MAX(HRHISTORY.ACT_OBJ_ID) ACT_OBJ_ID
    FROM
    LAWSON.HRHISTORY
    WHERE
    HRHISTORY.FLD_NBR=20
    and TO_DATE(HRHISTORY.DATE_STAMP)
        >= TO_DATE((TO_CHAR((ADD_MONTHS(SYSDATE,-1)),'YYYY/MM')||'/01'),'YYYY/MM/DD') 
        AND  TO_DATE(HRHISTORY.DATE_STAMP) <= (TO_DATE((TO_CHAR((ADD_MONTHS(SYSDATE,0)),'YYYY/MM')||'/01'),'YYYY/MM/DD'))-1
    /--Added by HAN--/
        GROUP BY COMPANY,
        EMPLOYEE),
    NEWSTAT AS
    (SELECT
    /--Added by HAN--/
    HRHISTORY.COMPANY,
    HRHISTORY.EMPLOYEE,
    HRHISTORY.A_VALUE,
    HRHISTORY.DATE_STAMP,
    HRHISTORY.BEG_DATE,
    HRHISTORY.ACT_OBJ_ID NS_OBJ_ID,
    HRHISTORY.SEQ_NBR
    FROM
    LAWSON.HRHISTORY
    INNER JOIN LAWSON.MAXNEWSTAT
    ON
    /--Added by HAN--/
    HRHISTORY.COMPANY = MAXNEWSTAT.COMPANY
    /--Added by KAM--/
    AND HRHISTORY.EMPLOYEE = MAXNEWSTAT.EMPLOYEE
    AND HRHISTORY.ACT_OBJ_ID = MAXNEWSTAT.ACT_OBJ_ID
    WHERE
    HRHISTORY.FLD_NBR=20
    and TO_DATE(HRHISTORY.DATE_STAMP)
        >= TO_DATE((TO_CHAR((ADD_MONTHS(SYSDATE,-1)),'YYYY/MM')||'/01'),'YYYY/MM/DD') 
        AND  TO_DATE(HRHISTORY.DATE_STAMP) <= (TO_DATE((TO_CHAR((ADD_MONTHS(SYSDATE,0)),'YYYY/MM')||'/01'),'YYYY/MM/DD'))-1
    PREVSTATID AS
    (SELECT
    /--Added by HAN--/
    HRHISTORY.COMPANY,
    HRHISTORY.EMPLOYEE,
    MAX(HRHISTORY.ACT_OBJ_ID)OBJ_ID
    FROM
    LAWSON.HRHISTORY
        INNER JOIN LAWSON.NEWSTAT
    /--Added by HAN--/
        ON HRHISTORY.COMPANY = NEWSTAT.COMPANY
        AND HRHISTORY.EMPLOYEE = NEWSTAT.EMPLOYEE
    WHERE
    HRHISTORY.FLD_NBR=20
    AND TO_DATE(HRHISTORY.BEG_DATE)
    < to_date(NEWSTAT.BEG_DATE)
    GROUP BY
    /--Added by HAN--/
    HRHISTORY.COMPANY,
    HRHISTORY.EMPLOYEE
    PREVSTAT AS
    (SELECT
    /--Added by HAN--/
    HRHISTORY.COMPANY,
    HRHISTORY.EMPLOYEE,
    HRHISTORY.A_VALUE A_VALUE,
    HRHISTORY.DATE_STAMP DATE_STAMP,
    HRHISTORY.BEG_DATE BEG_DATE,
    HRHISTORY.ACT_OBJ_ID OBJ_ID,
    HRHISTORY.SEQ_NBR SEQ_NBR
    FROM
    LAWSON.HRHISTORY
        INNER JOIN LAWSON.PREVSTATID
    /--Added by HAN--/
        ON HRHISTORY.COMPANY = PREVSTATID.COMPANY
        AND HRHISTORY.EMPLOYEE = PREVSTATID.EMPLOYEE
    WHERE
    HRHISTORY.FLD_NBR=20 AND
    HRHISTORY.ACT_OBJ_ID = PREVSTATID.OBJ_ID
    MAXPERSACTHST AS
    (SELECT
    PERSACTHST.EMPLOYEE,
    /--Added by KAM--/
    PERSACTHST.COMPANY,
    MAX(PERSACTHST.DATE_STAMP)DATE_STAMP
    FROM
    LAWSON.PERSACTHST
    WHERE
    (PERSACTHST.ACTION_CODE='LOASTATUS' OR PERSACTHST.ACTION_CODE='STATUS')
    AND TO_DATE(PERSACTHST.DATE_STAMP)
        >= TO_DATE((TO_CHAR((ADD_MONTHS(SYSDATE,-1)),'YYYY/MM')||'/01'),'YYYY/MM/DD') 
        AND  TO_DATE(PERSACTHST.DATE_STAMP) <= (TO_DATE((TO_CHAR((ADD_MONTHS(SYSDATE,0)),'YYYY/MM')||'/01'),'YYYY/MM/DD'))-1
    GROUP BY PERSACTHST.EMPLOYEE,
    /--Added by KAM--/
    PERSACTHST.COMPANY
    CHANGELIST AS   
    (SELECT
    PERSACTHST.EMPLOYEE,
    /--Added by KAM--/
    PERSACTHST.COMPANY,
    PERSACTHST.ACTION_CODE,
    PERSACTHST.REASON_01,
    PERSACTHST.DATE_STAMP,
    PERSACTHST.EFFECT_DATE,
    PERSACTHST.REASON_02,
    PREVSTAT.A_VALUE PS_A_VALUE,
    PREVSTAT.DATE_STAMP PS_HR_DATE_STAMP,
    PREVSTAT.BEG_DATE PS_HR_BEG_DATE,
    PREVSTAT.OBJ_ID PS_HR_OBJ_ID,
    PREVSTAT.SEQ_NBR PS_HR_SEQ_ID,
    NEWSTAT.A_VALUE NS_A_VALUE,
    NEWSTAT.DATE_STAMP NS_DATE_STAMP,
    NEWSTAT.BEG_DATE NS_BEG_DATE,
    NEWSTAT.NS_OBJ_ID,
    NEWSTAT.SEQ_NBR NS_SEQ_NBR
    FROM
    LAWSON.PERSACTHST PERSACTHST
                        INNER JOIN LAWSON.PREVSTAT
                       ON PERSACTHST.EMPLOYEE=PREVSTAT.EMPLOYEE
                       /--Added by KAM--/
                       AND PERSACTHST.COMPANY = PREVSTAT.COMPANY
                       INNER JOIN LAWSON.NEWSTAT
                       ON PERSACTHST.EMPLOYEE = NEWSTAT.EMPLOYEE
                      /--Added by KAM--/
                       AND PERSACTHST.COMPANY = NEWSTAT.COMPANY
                       INNER JOIN LAWSON.MAXPERSACTHST
                       ON PERSACTHST.EMPLOYEE = MAXPERSACTHST.EMPLOYEE
                      /--Added by KAM--/
                         AND PERSACTHST.COMPANY = MAXPERSACTHST.COMPANY
    WHERE
    (PERSACTHST.ACTION_CODE='LOASTATUS' OR PERSACTHST.ACTION_CODE='STATUS')
    AND NEWSTAT.A_VALUE <> PREVSTAT.A_VALUE
    AND MAXPERSACTHST.DATE_STAMP = PERSACTHST.DATE_STAMP
    PAEMPPOSENDDATE AS
    (SELECT
      PAEMPPOS.EMPLOYEE,
      PAEMPPOS.COMPANY,
      CASE
      WHEN PAEMPPOS.END_DATE = TO_DATE('1700,01,01','YYYY,MM,DD')
             THEN to_date(SYSDATE + 1,'YYYY,MM,DD')
           ELSE PAEMPPOS.END_DATE 
      END END_DATE,
      PAEMPPOS.EFFECT_DATE
      FROM LAWSON.PAEMPPOS),
    CURRFTE AS
    (SELECT
      PAEMPPOS.EMPLOYEE,
    /--Added by KAM--/
      PAEMPPOS.COMPANY,
      PAEMPPOS.FTE CURR_FTE,
      PAEMPPOS.EFFECT_DATE,
      PAEMPPOSENDDATE.END_DATE  
    FROM
    LAWSON.PAEMPPOS
    INNER JOIN LAWSON.NEWSTAT
    ON (PAEMPPOS.EMPLOYEE = NEWSTAT.EMPLOYEE)
    /--Added by KAM--/
    AND (PAEMPPOS.COMPANY = NEWSTAT.COMPANY)
    INNER JOIN LAWSON.PAEMPPOSENDDATE
    ON PAEMPPOS.EMPLOYEE = PAEMPPOSENDDATE.EMPLOYEE
    /--Added by KAM--/
    AND PAEMPPOS.COMPANY = PAEMPPOSENDDATE.COMPANY
    AND PAEMPPOS.EFFECT_DATE=PAEMPPOSENDDATE.EFFECT_DATE
    WHERE
      (PAEMPPOSENDDATE.EFFECT_DATE <= NEWSTAT.BEG_DATE AND PAEMPPOSENDDATE.END_DATE >= NEWSTAT.BEG_DATE)
    PREVFTE AS
    (SELECT
      PAEMPPOS.EMPLOYEE,
    /--Added by KAM--/
      PAEMPPOS.COMPANY,
      PAEMPPOS.FTE PREV_FTE,
    PAEMPPOSENDDATE.END_DATE 
    FROM
    LAWSON.PAEMPPOS
    INNER JOIN LAWSON.NEWSTAT
    ON (PAEMPPOS.EMPLOYEE = NEWSTAT.EMPLOYEE)
    /--Added by KAM--/
    AND (PAEMPPOS.COMPANY = NEWSTAT.EMPLOYEE)
    INNER JOIN LAWSON.PAEMPPOSENDDATE
    ON (PAEMPPOS.EMPLOYEE = PAEMPPOSENDDATE.EMPLOYEE)
    /--Added by KAM--/
    AND (PAEMPPOS.COMPANY = PAEMPPOSENDDATE.COMPANY)
    AND (PAEMPPOS.EFFECT_DATE = PAEMPPOSENDDATE.EFFECT_DATE)
    WHERE
      PAEMPPOS.EFFECT_DATE <= (NEWSTAT.BEG_DATE-1)AND  PAEMPPOSENDDATE.END_DATE >= (NEWSTAT.BEG_DATE -1)
    SELECT DISTINCT
    EMPLOYEE.EMPLOYEE,
    EMPLOYEE.DEPARTMENT,
    EMPLOYEE.PROCESS_LEVEL,
    EMPLOYEE.EMP_STATUS,
    EMPLOYEE.FIRST_NAME,
    EMPLOYEE.LAST_NAME,
    EMPLOYEE.MIDDLE_INIT,
    EMPLOYEE.POSITION,
    PAPOSITION.DESCRIPTION,
    CHANGELIST.PS_A_VALUE,
    /--Added by KAM--/
    CHANGELIST.COMPANY,
    CHANGELIST.PS_HR_DATE_STAMP,
    CHANGELIST.PS_HR_BEG_DATE,
    CHANGELIST.PS_HR_OBJ_ID,
    CHANGELIST.NS_A_VALUE,
    CHANGELIST.NS_DATE_STAMP,
    CHANGELIST.NS_OBJ_ID,
    CHANGELIST.ACTION_CODE,
    CHANGELIST.REASON_01,
    CHANGELIST.REASON_02,
    CHANGELIST.DATE_STAMP PERSACTSDATESTAMP,
    CHANGELIST.EFFECT_DATE PERSACTEFFDATE,
    DEPTCODE.R_NAME DEPTNAME,
    PRSYSTEM.R_NAME PLNAME,
    PREVFTE.PREV_FTE,
    CURRFTE.CURR_FTE,
    CHANGELIST.NS_BEG_DATE,
    PGSELECT.GROUP_NAME,
    PAEMPLOYEE.SENIOR_DATE
    FROM
    LAWSON.CHANGELIST
                      INNER JOIN LAWSON.EMPLOYEE
                     ON (EMPLOYEE.EMPLOYEE = CHANGELIST.EMPLOYEE)
    /--Added by KAM--/
                     AND (EMPLOYEE.COMPANY = CHANGELIST.COMPANY)
                     INNER JOIN LAWSON.DEPTCODE
                     ON ((EMPLOYEE.COMPANY=DEPTCODE.COMPANY)
                     AND (EMPLOYEE.PROCESS_LEVEL=DEPTCODE.PROCESS_LEVEL)
                     AND (EMPLOYEE.DEPARTMENT=DEPTCODE.DEPARTMENT))
                     INNER JOIN LAWSON.PRSYSTEM
                     ON ((EMPLOYEE.COMPANY=PRSYSTEM.COMPANY)
                     AND(EMPLOYEE.PROCESS_LEVEL=PRSYSTEM.PROCESS_LEVEL))
                     LEFT OUTER JOIN LAWSON.PREVFTE
                       ON (CHANGELIST.EMPLOYEE=PREVFTE.EMPLOYEE)
    /--Added by KAM--/                
                     AND (CHANGELIST.COMPANY=PREVFTE.COMPANY)
                     LEFT OUTER JOIN LAWSON.CURRFTE
                     ON (CHANGELIST.EMPLOYEE=CURRFTE.EMPLOYEE)
    /--Added by KAM--/                                
                     AND (CHANGELIST.COMPANY=CURRFTE.COMPANY)
                     INNER JOIN LAWSON.PGSELECT PGSELECT
                       ON ((EMPLOYEE.COMPANY=PGSELECT.COMPANY)
                     AND (EMPLOYEE.EMP_STATUS=PGSELECT.BEGIN_VALUE))
                     LEFT OUTER JOIN LAWSON.PAPOSITION
                     ON (EMPLOYEE.POSITION=PAPOSITION.POSITION)
                     AND (EMPLOYEE.COMPANY=PAPOSITION.COMPANY)
                     INNER JOIN LAWSON.PAEMPLOYEE
                     ON (CHANGELIST.EMPLOYEE=PAEMPLOYEE.EMPLOYEE)
    /--Added by KAM--/               
                    AND (CHANGELIST.COMPANY=PAEMPLOYEE.COMPANY)
    WHERE
    (PGSELECT.GROUP_NAME='G:ACTIVE' OR PGSELECT.GROUP_NAME='G:INACTIVE')
    >

    Hi Arsh,
    The error message you receive i.e.
    ORA-01830: date format picture ends before converting entire input string
    is an Oracle error.
    The following document would be helpful:
    ORA-01830:     date format picture ends before converting entire input string
    Cause:     A valid date format picture included extra data. The first part of the format picture was converted into a valid date, but the remaining data was not required.
    Action:     Check the specifications for date format pictures and correct the statement.
    Regards,
    Alpana

  • ORA-01820: format code cannot appear in date input format

    I don't understand why I am getting the error below. That should be valid, no?
    TIA for any insight.
    Connected to:
    Oracle9i Enterprise Edition Release 9.2.0.7.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.7.0 - Production
    SQL>
    SQL> select to_date('2004 01 3','yyyy mm w') from dual;
    select to_date('2004 01 3','yyyy mm w') from dual
    ERROR at line 1:
    ORA-01820: format code cannot appear in date input format
    SQL>
    SQL> select to_char(sysdate,'yyyy mm w') from dual;
    TO_CHAR(S
    2008 08 1

    LC,
    ORA-01820:     format code cannot appear in date input format
    Cause:     A date specification contained an invalid format code. Only the following may be specified when entering a date: year, month, day, hours, minutes, seconds, Julian day, A.M./P.M. and B.C./A.D.
    Action:     Remove the invalid format code from the date specification.
    Looking at the cause,you can't use a format code like W in the date format for converting a text to date. To_date doesn't accept it.
    Aman....

  • Using substring for entire input  string

    Hi,
    I am getting values required from a FM as big string so I have to parse that string into chunks and then get flat file.
    SOURCE:
    ZXYZ_abc
    ---data
          ---abc(This abc has entire data as a big string)
    example value   sdn12345xyx789
    Target
    I have created DT type of the similar structure as source
    TG_ABC
    ---data
       ---xyz
           fd1
           fd2
           fd3
           fd4
    now I wan tto parse above string and get those parsed values into target fields fd1 ,fd2 fd3 like
    output flat file with '||' delimited
    sdn || 12345 || xyx || 789
    I am trying to do in the mapping
    abc-substring(0-3)--fd1
    abc--substring(38)--fd2
    etc...
    but I am not getting any value
    it just created empty file in the target.
    please help.
    thank you.
    Babu

    Raj,
    parsing the string,it doesnt parse the input large string to different output fields.
    I dont see any values in payload in SXMB_MONI ,it just created empty tag with Messsagetype name.infact it supposed to have values within tags with parsed values.
    i am using single source field and apply substring function on it and map to target fields as I explained in the example I gave.
    when I test the map with map testing option ,it doesnt give any value on target side,so should be prob with parsing only.

  • Format code cannot appear in date input format - IW related

    Hi,
    please explain what I'm doing wrong:
    SQL>  select to_char(sysdate, 'YYYY-IW') from  dual;
    TO_CHAR
    2010-48
    SQL>  select to_date('2010-22', 'YYYY-IW') from  dual;
    select to_date('2010-22', 'YYYY-IW') from  dual
    ERROR at line 1:
    ORA-01820: format code cannot appear in date input formatOracle 9.2 .
    Regards.
    Greg

    FIrst of all you should stay with the date format. Instead of converting it into a string you could TRUNCATE it to the first day of the Iso-Wekk.
    And to enable index usage you just have to put a certain range on your queries.
    example
    select *
    from t
    where col_date  >= trunc(sysdate, 'IW')  ;if col_date can hold values that are greater than syste. Or if you use another date value to compare than sysdate. Then you need to compare with a range. Just like this
    select *
    from t
    where col_date  >= trunc(sysdate, 'IW') 
    and col_date  < trunc(sysdate, 'IW')+7 ;If you want to input a certain WEEK and get all entries from that week you can start with the first day of the iso-Year and add the number of weeks to it.
    example using iso-Week 40
    select *
    from t
    where col_date  >= trunc(sysdate, 'IYYY')  + 7 * 40
    and col_date  < trunc(sysdate, 'IYYY')+7 * (40 +  1);However calendar arithmetic is complex. We have to be careful for special cases. For example the beginning of the ISO-Year 2011 is the 3rd Jan 2011. So if we run this logic on the first or second of January *2011* we would get the calendar week 40 from *2010*. This is probably not what you want.
    To take this into account we must make sure that we are using the proper year. There are several possibilities how to do it. In this case I choose to use the normal TRUNC to get the first day of the normal year (1.1.2011) then add a week and truncate again.
    example
    select *
    from t
    where col_date  >= trunc(trunc(sysdate,'YYYY)+7, 'IYYY')  + 7 * 40
    and col_date  < trunc(trunc(sysdate,'YYYY)+7, 'IYYY')+7 * (40 +  1);Edited by: Sven W. on Dec 3, 2010 8:52 AM

  • Convertion of the string

    I'm new user of Labview.
    The attached picture shown the string that i get from the PIC. So how can i convert the input string to the expected format?Between, it is any problem of
    the write to measurement file?
    Thanks.
    Attachments:
    temp-1.vi ‏95 KB
    string.PNG ‏14 KB

    use scan from string with format AN%2d%4d => this will split the string up in 2 parts => sensor and value.
    Kind regards,
    - Bjorn -
    Have fun using LabVIEW... and if you like my answer, please pay me back in Kudo's
    LabVIEW 5.1 - LabVIEW 2012

  • Made the mistake of upgrading to Lion before converting my Quicken file to QIF format.  Any suggestions??

    Made to mistake of upgrading to Lion before converting my QUicken File to QIF format needed to import into iBank or other similar apps. Any suggestions??
    Left high and dry by Apple and Intuit.

    moranpc wrote:
    Made to mistake of upgrading to Lion before converting my QUicken File to QIF format needed to import into iBank or other similar apps. Any suggestions??
    Left high and dry by Apple and Intuit.
    Your Quicken files should already be in the correct format.  Can't remember details because I converted some time ago and no longer have my old files.
    Can't understand your comment about being left "high and dry."  It's been common knowledge for six months that Lion won't support PPC applications and it's been common knowledge for several years that Intuit is abandoning the Mac.
    I will warn you that, even if you are able to convert now, the conversion does produce errors.

Maybe you are looking for