DATE value in a STORED PROC becoming incorrect?

Question

I have a PL SQL script that creates a TABLE on the fly with a DATE column in it. I then have a FUNCTION that queries this table. The FCN is called from within a SP. In these three steps the date becomes a BOGUS value.... I am seeing things like this:
2/5/0009 12:00:00.000 AM
6/4/0009 12:00:00.000 AM
4/16/0009 12:00:00.000 AM
7/9/0008 12:00:00.000 AM
5/7/0007 12:00:00.000 AM
Obviously the 0009 should be 2009 and 0008 2008 etc..... ANy idea what is causing this?????
Here is my code:
DROP TABLE MAXIMO.MAX411_TEMP_REG_DATE
create table
   MAXIMO.MAX411_TEMP_REG_DATE
as
SELECT  ITEMNUM,
        DESCRIPTION,
        LOCATION,
        BINNUM,
        REG_DATE + (trunc(rownum / ((select count(*) from inventory)/100))*7) REG_DATE
FROM ( SELECT   I.ITEMNUM,
                I.DESCRIPTION,
                N.LOCATION,
                N.BINNUM,
                TO_DATE(SYSDATE,'DD-MON-YYYY') REG_DATE
        FROM ITEM I, INVENTORY N
        WHERE I.ITEMNUM = N.ITEMNUM
        ORDER BY N.LOCATION, N.BINNUM)
COMMIT
CREATE OR REPLACE FUNCTION MAXIMO.FCN_GET_REGDATE (item_in IN VARCHAR2)
  RETURN DATE
IS
  new_regdate   DATE;
  var_problem_indicator   number;
  BEGIN
          SELECT reg_date
           INTO new_regdate
           FROM MAXIMO.MAX411_TEMP_REG_DATE
           WHERE itemnum = TRIM(item_in) AND ROWNUM = 1;
  END;
RETURN new_regdate;
END;
/ STORED PROC CALL
var_regdate             DATE;
var_regdate := MAXIMO.FCN_GET_REGDATE (rec.ITEMNUM);Thanks for any help I can get.....
Miller

Answer 1

Looking at this code I find two items very disturbing:
ORDER BY N.LOCATION, N.BINNUM
... and ...
WHERE itemnum = TRIM(item_in) AND ROWNUM = 1;
It looks a lot like you are trying to rely on a sort order imposed on the data as it is inserted into the table to identify a particular record for a given item_in. If so, that's very dangerous, but it's nothing that can't be fixed. Let us know ...