expiration dates

[cschwobe]

when we put JDE in years ago, the data dictionary value for the expiration date was 12/31/10. We have since changed this value to be 12/31/20. does anyone know if JDE has a program to go and update all these dates or even what files would all need to be updated?

thanks for any help
Carol

 

[pfd]

Oracle has 3 SARs for this issue for EnterpriseOne.

SAR 8943215 - TT- Century_Date Browser
SAR 8335534 - Update Effective-Thru Date
SAR 8946142 - Create #CYR Batch Update Pgm.
I believe that these SARS may be included in 8.98.0.3 (that will be delivered in Q2).

SAR 8505290, Create #CYR Batch Update Program, was entered for WORLD software and offers a solution. A new batch program, P4028, was created, along with two UDCs, 40/EI and 40/EF for WORLD software.

I have also attached a list of tables that may need to be updated.

Thanks,
Matt

 

[Adrian_Chimirel]

Please see Post 162367 for details about DATEUTIL = Oracle Solution.

 

[vbojan]

Hi,

We wrote DB2 stored procedure (in attachment) that get tables using following DD items: EFFT, EXDE, EXDJ, CXPJ, EEFD and EFTE from DB system tables (on AS400 it’s in SYSCOLUMNS) and run update statements for each of them. A few files (F4072, F4104, F4106, F42004) have those date columns participating in primary key so we’ve decided to first delete records with 12/31/10 if corresponding record with 12/31/20 exists.
We’ve run it 3 months ago and everything worked fine so far.

Hope this helps,

Bojan

 

[cdawes]

JD Edwards EnterpriseOne Date Utility

• The Date Utility for JD Edwards EnterpriseOne enables you to
identify and update a future expiration date value in a specified
table.

• The utility includes two modes:
– Scan to identify the tables that contain the expiration date.
– Update to change the expiration date in a specified field within a specified table.

• Two versions of the utility are available based on release:
– DateUtil for Release 8.9 or higher (Tools 8.97 or 8.98)
– DateUtilXe for Xe and ERP 8 (Tools SP 23 or SP 24)

• To learn more about the Date Utility, access the Knowledge Document
(Doc ID 882478.1) on My Oracle Support.

 

[JosephRay]

Hello,
I would like to ask you in case of a Parent manufactured item having LECM=3 and having a Shelf life days = 1825. Also this Parent item has an active ingredient component.
When we make WO Completion on a work order of this Parent item, the quantity completed will have the Expiry date of its active ingredient component. But apparently the system will add also to the expiration date of the active ingredient, the 1825 days defined as Shelf life days of this Parent item in order to calculate the real Expiry date of this same Parent item.
Is this behavior normal in JDE ? or the system should ignore the 1825 days defined as Shelf life days of this Parent item and take into consideration only the Expiry date of the Active ingredient ?

Thank you so much for your answer and help

Kind Regards
Joseph

 

[JohnDanter2]

Look into what the Based On Date does. BODJ
Or set LECM to 2???

It helps you with this very scenario. You may complete your WO today but the active ingredient was made 100 days ago, so the 'based on date' is todays date - 100 days. Not.....todays date + 365 days for example. It will be the Based On Date + 365 days