Century Change JDE
Upcoming SlideShare
Loading in...5
×
 

Century Change JDE

on

  • 1,425 views

Documentation for change of century in JDE

Documentation for change of century in JDE

Statistics

Views

Total Views
1,425
Views on SlideShare
1,418
Embed Views
7

Actions

Likes
0
Downloads
9
Comments
0

2 Embeds 7

http://www.linkedin.com 5
https://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Century Change JDE Century Change JDE Document Transcript

  • Modified 02-AUG-2010 Type ANNOUNCEMENT Status PUBLISHED In this Document What is being announced? Abstract: What do you need to do? Julian Dates and JD Edwards EnterpriseOne Century Change Year (CENTCHG) Data Dictionary Value Recommended Default Value for CENTCHG Data Considerations Other Considerations - Work Day/Shop Floor Calendars Resolution Date Utility Recommendations Scan Mode Update Mode – Proof and Final Examples: Date Utility Frequently Asked Questions References Applies to: JD Edwards EnterpriseOne Information in this document applies to any platform. What is being announced? Abstract: JD Edwards EnterpriseOne stores calendar dates in Julian date format. The system allows two- digit dates to be entered to facilitate data entry. The system uses data dictionary item CENTCHG (CenturyChangeYear) to determine the century to use for populating data tables. The system also uses this data dictionary item when automatically populating the default effective through and expiration dates in some data tables. In releases Xe and ERP8.0, the default value for CENTCHG was set to 10. Thus dates populated using the CENTCHG default value are created as ‘12/31/2010’. In release 8.9, the default value was set to 15, creating a date of ‘12/31/2015’. In releases 8.10 through 9.0, the default value was set to 40, creating a date of ‘12/31/2040’. Oracle recommends that this value be increased for users in the Xe, ERP8.0, and 8.9 releases as well as users who have upgraded from these releases to 8.10 or higher so that the software will supply new effective through dates further into the future. This document outlines the function of CENTCHG in the software and recommends a change to the CENTCHG data dictionary default as soon as possible. This document also introduces the Date Utility, a tool designed to assist users with identifying and resolving business data with potential date issues. The Date Utility is designed for use with the currently supported tools releases. What do you need to do?
  • Julian Dates and JD Edwards EnterpriseOne When a user enters dates into JD Edwards EnterpriseOne, the system enables that user to enter a two-digit year. The system has business functions that determine the correct century. For example, if the user enters the date March 7, 2011, as 03/7/11, the system uses the CENTCHG, Century Change Year (CenturyChangeYear), data dictionary item to determine whether the two- digit date being entered is 1911 or 2011. The Julian date (CYYDDD) that is updated in the table is 111066. The date conversion routines use the century change year default value to determine the century when converting to Julian format. The effective through date by default will be the last day of the year defined in this data item. JD Edwards EnterpriseOne enables various date formats such as MM/DD/YY and DD/MM/YY. The date is always entered as a Julian date within the tables. Note: Many examples in this document use the format of DD/MM/YYYY. Century Change Year (CENTCHG) Data Dictionary Value Data dictionary item CENTCHG performs two functions: • Controls how JD Edwards EnterpriseOne determines dates values. When a user enters a date value, the year associated with the date is based on the data dictionary item CENTCHG. The value in the Default Value tab of CENTCHG determines when the cutoff is between the 19th and 20th centuries. For example, when the default value is set to 10: - Dates entered with a year up to 10 are preceded by 20 for example, 2005, 2006, 2007, and so on. - Dates entered with a year after 10 are preceded by 19 and assumed to belong to that century for example, 1911, 1912, and so on. If the current value for this data dictionary item is set to 10 and a user enters a date of 01/01/11, the system compares this value to the default value for the CENTCHG data item, and because 11 is greater than the default value of 10, the system adds the value 19 and returns a date of 1/1/1911. • Concatenates with the CTRY (Century) data item and the hard coded value of December 31 (12/31/) to populate expiration date fields with the last system date. For example, if CTRY is set to 20 and CENTCHG is set to 10, and users do not enter the expired date on the Print Messages application P40162, the system enters 12/31/2010. Many applications and tables use this default value if the date is not entered by users. In releases Xe and ERP8.0, the default value for CENTCHG was set to 10. Any two-digit year entered that is less than or equal to 10 is treated as 20xx. Any two-digit year entered that is greater than 10 is treated as 19xx. In release 8.9, the default value was set to 15. In releases 8.10 through 9.0, the default value was set to 40. The system uses the CENTCHG value in many programs to supply an effective through date. This date by default is the last day of the 100-year window. For example, with the CENTCHG value of 10 the effective through default date is 12/31/2010. When the CENTCHG value is set to 15, the effective through default date is 12/31/2015. With a CENTCHG value of 40, the effective through default date is 12/31/2040. Oracle recommends that this value be increased for users in the Xe, ERP8.0, and 8.9 releases so that the software will by default supply effective through dates further into the future. Oracle provides a Date Utility to allow users to review date fields in business data. Additional information
  • regarding the Utility is included later in this document. Users who have data migrated from the Xe, ERP8.0, or 8.9 releases should also increase the value for the data dictionary item. Examples: CENTCHG Value Date Entered MM/DD/YY Julian Date Year 10 07/29/08 108210 2008 10 07/29/11 011210 1911 30 07/29/08 108210 2008 30 07/29/11 111210 2011 Recommended Default Value for CENTCHG Oracle recommends that the CENTCHG value be increased for users in the Xe, ERP8.0, and 8.9 releases. Users who have data migrated from the Xe, ERP8.0, or 8.9 releases should also increase the value for the data dictionary item. Increasing the value moves forward the floating 100-year window. The recommendation is to move the default value as far forward as practical while meeting business data needs. For example, if the CENTCHG value is changed to 40, any two-digit year entered with a value less than or equal to 40 is treated as 20xx. Any two-digit year entered that is greater than 40 is treated as 19xx. In this example, with the CENTCHG value set to 40, a date of 06/30/25 is supplied as June 30th in the year 2025. Default dates generated using the CENTCHG value would be set to 12/31/2040. Users of the JD Edwards EnterpriseOne Fixed Assets module need to take into account their data. Before changing the CENTCHG value, check the acquisition date of the oldest asset in the Fixed Assets Master Table (F1201). The system uses the century window logic in the Compute Depreciation programs. Any asset that has a date acquired prior to the new 100-year window (for example 1941) no longer appears on the Compute Depreciation report. Older assets are normally fully depreciated. Other reports can be used to list all assets regardless of acquisition date. If this consideration is of concern for Fixed Asset depreciation computations users should set the default CENTCHG value to a value that matches their depreciation schedule. Data Considerations When users change the CENTCHG data dictionary value, the system will not update existing business data in the tables. Existing date values in the tables may indicate an effective through date of 12/31/2010 (Julian Date 110365) or 12/31/2015 (Julian Date 115365). Some expiration dates may be valid. Users must evaluate the dates that should be revised. When users upgrade from older releases to new releases, the system does not update the expiration dates on existing records. After users identify the impacted tables, business data can be updated by: • Revising records in the associated application • Using a database tool to update tables • Using the Date Utility tool to update dates. Information regarding the Date Utility is provided later in this document and in the related documents section.
  • Oracle recommends that, when changing dates in tables to new values, the dates match the value created by the concatenation of the CENTCHG and CTRY data dictionary values. Note: Data Dictionary item DCYR (CenturyCutoff) shares the same default values as CENTCHG. The default value of DCYR determines the proper century for a date when entered using a 2-digit year. The Data Dictionary application makes the same default value change to DCYR when the user changes the default value of CENTCHG. If the user changes the default value of DCYR, the same change is also applied to CENTCHG. Other Considerations - Work Day/Shop Floor Calendars Many programs within JD Edwards EnterpriseOne use Work Day and Shop Floor calendars with future dates. When using these calendars users should move forward the CENTCHG value in production environments as soon as possible. Oracle recommends that the Shop Floor calendar be setup 5 years into the future for MRP calculation purposes. The standard JD Edwards EnterpriseOne Financial Calendar does not use CENTCHG logic to determine century. Resolution If the value of CENTCHG is set to 10, users must change the value prior to December 31, 2010. Oracle recommends that the value be changed now to enable effective through default dates to be supplied further into the future. Other values can be selected based on default date preference and business requirements. Existing effective through dates that were supplied with 12/31/2010 should be evaluated and may need to be updated prior to 12/31/2010. If the value of CENTCHG is already set beyond 10 it is possible the value was moved forward without consideration of how to handle the existing effective through dates in the tables. The CENTCHG data dictionary item should be set to a higher value as soon as possible. The new value should take into account business process needs. The further out the default dates are set the longer the duration is before data issues need to be re-evaluated. Updates should be performed as needed. This process should be complete prior to these dates having an effect on production systems. Date Utility JD Edwards EnterpriseOne provides a Date Utility tool to assist users with identifying business data with specific date values. The utility is a basic tool; it does not analyze business data. Instead, the tool identifies business data with a user defined date value. The Date Utility provides a Scan mode, to identify records with a user input date parameter, and Update Proof and Update Final modes to identify and update (in final mode) records in tables and fields in tables with an input date parameter and an update date parameter. The Date Utility is designed for use with the following software releases and corresponding tools releases. The name of the download corresponding to each software release is indicated in the table. Software Release Tools Release Date Utility Download Name Xe SP 23 or SP 24 DATEUTILXE
  • ERP8 SP 23 or SP 24 DATEUTILXE 8.9 8.97 or 8.98 DATEUTIL 8.10 8.97 or 8.98 DATEUTIL 8.11 8.97 or 8.98 DATEUTIL 8.11 SP1 8.97 or 8.98 DATEUTIL 8.12 8.97 or 8.98 DATEUTIL 9.0 8.97 or 8.98 DATEUTIL Installing the Date Utility: 1. Access the Update Center on My Oracle Support. 2. Filter on JDE EnterpriseOne and search for DATEUTIL*. The utility can also be found in Change Assistant by searching on DATEUTIL*. 3. Select the appropriate executable file. 1. For releases Xe and ERP8.0, select DATEUTILXE. 2. For releases later than ERP8.0, select DATEUTIL. 4. Review the Read Me First file and all associated documentation. 5. Copy the DateScan.exe file to OW_DIR_BASEsystembin32 directory. Note: OW_DIR_BASE is the base directory of the current JD Edwards EnterpriseOne installation. Using the Date Utility: 1. Create UDC table entry 98/UU. This UDC table is used to store an imported list of table names to exclude when running the date utility. 2. Import the list of table names to exclude. Oracle provides an Excel file, Date Utility – Table Scan Exclusion List.xls, that lists recommended table names to exclude. 3. Sign in to the correct JD Edwards EnterpriseOne environment. 4. Run the Date Utility in Scan mode. 5. Analyze the Scan mode results. 6. Backup the database. 7. Run the Date Utility in Update Proof mode. 8. Review the Update Proof mode results. 9. Run the Date Utility in Update Final mode. 10. Review the Update Final mode results. 11. Validate the accuracy of the updates. The Date Utility is intended to update current dates in the system, not historical dates. It is not necessary to run the Date Utility across historical tables such as Account Ledger (F0911), Item Ledger (F4111), Sales Order Header History File (F42019), Sales Order History File (F42119), PO Detail Ledger (F43119, and so on. The Date Utility is intended to update dates used for current and future transactions. Users who install the Data Utility are also instructed to create UDC table entry 98/UU and import a list of tables to exclude while running the Date Utility. Oracle provides a list of tables to exclude. Users can add or remove tables from the UDC as needed. Recommendations Oracle recommends users:
  • • Analyze the output of the utility prior to making changes to business data. Users are responsible for knowing and understanding their business data. Individuals within your organization who thoroughly understand the business use of the data should analyze the output. Only users with a thorough understanding of the business data and business processes should perform any updates. • Ensure users who execute the Date Utility in Scan and/or Update modes have open security. The Date Utility prompts the user to sign in to the JD Edwards EnterpriseOne environment. The sign in invokes EnterpriseOne security. • Create a backup of the entire database prior to making any changes to business data. Users should ensure a backup of the data is created prior to running the utility in Update Final mode. Interactive applications should be used to update business data whenever practical. • Run the Date Utility at a time when no other batch jobs or applications are modifying or adding records in the database. • Change the CENTCHG data dictionary item prior to running the Date Utility. Updating the CENTCHG data dictionary value prevents new records from being created with obsolete default values. The utility does not evaluate the CENTCHG data dictionary item. • Review all downstream processes to ensure any changed dates do not adversely affect production functions. Scan Mode Users can run the Date Utility in scan mode to identify tables containing a user identified date parameter. For example, users may wish to scan a single table or a specified group of tables for all data with the input parameter of the date December 31, 2010, 12/31/2010. The Date Utility will scan the database, minus the tables listed in UDC 98/UU, for any and all date fields. The utility produces a report, a CSV file, identifying the total number of records in the table or tables with the 12/31/2010 date. The data item containing the 12/31/2010 date value is also indicated on the output report. The utility also produces a log file, DateScanLog.txt. When running the Date Utility in scan mode the user provides the following values: • Date to query • Table range (single table or range of tables) • System code range (single system code or range of system codes) Update Mode – Proof and Final The Date Utility also provides the ability to update dates when executed in Update Final mode. Users can run the utility in Update Proof and Update Final modes. When run in Update Proof or Update Final mode, the utility will process only one table and one date field in that table with each execution. Similar to Scan mode, Update Proof and Update Final modes produce a report, a CSV file, and a log (DateScanLog.txt). Each execution of the utility will produce a new CSV file. The naming convention for the CSV file includes a date and time stamp. The log file is appended with each execution of the utility. Oracle recommends copying production data to a test environment, reviewing the utility results, and analyzing all downstream processes prior to using the Data Utility on production data. When running the Date Utility in Update Proof or Update Final modes the user provides the following values:
  • • Update Proof or Update Final mode • Date to query • Date to be updated • Table and field to be updated When running in Update Final mode, the utility performs updates on all records matching the input criteria. For example, if the utility identified ten records in table F0008 with the input date parameter of 12/31/2010 in field D12J, and the update statement indicated date parameter 03/27/2030, all ten records will be updated with 03/27/2030. The utility performs all or nothing updates. When run in Update Final mode all records meeting the input criteria are updated. If a small number of records in any table need to be revised, the interactive application should be used to update the records. When run in Update Final mode, the audit fields are updated with the value SCANUTIL. The utility does not analyze from and through logic when updating a date. If the utility is used to update an effective through date, the utility does not check to ensure the through date is subsequent to the from date. Examples: • Command used to scan for all records in the database where the date parameter is December 31, 2010, 12/31/10, in the range of tables from F0001 through F0010: o DateScan.exe 12312010 TBLE F0001 F0010 • Command used when running the utility in Update Proof mode where the user is changing the D12J value in F0008 for all records with 12/31/10 to 12/31/2065: o DateScan.exe UPDATE PROOF 12312010 12312065 F0008 D12J • Command used when running the utility in Update Final mode where the user is changing the D12J value in F0008 for all records with 12/31/10 to 12/31/2065: o DateScan.exe UPDATE FINAL 12312010 12312065 F0008 D12J Date Utility Frequently Asked Questions Question 1: Why were some tables skipped when running the utility in Scan mode? Answer 1: Tables listed in UDC 98/UU are skipped by the utility. Additionally, the utility honors EnterpriseOne security. The date utility requires the user to sign into EnterpriseOne thereby invoking EnterpriseOne security. Question 2: How can we add tables to UDC 98/UU? We have a number of custom tables that should not be included in the Scan. Answer 2: Users can add tables to UDC 98/UU similar to adding values to other UDCs. Inquire on the UDC 98/UU. Click Add. Move to the bottom of the list. Manually add values to the UDC. Question 3: Why didn’t the user receive a prompt to sign in to EnterpriseOne when running the Date Utility? Answer 3: If the user has already signed in to an EnterpriseOne environment the user will not be prompted to sign in to EnterpriseOne. To change environments the user must sign out of EnterpriseOne then sign in again. Question 4: The Date Utility, in Update Proof Mode, results show fifty records in one table with the date value we indicated. How can we use the utility to update a portion of the tables? How can we selectively update records? Answer 4: The Date Utility, when run in Update Final Mode, updates all records matching the input criteria. The Date Utility is an ‘all or nothing’ update. Oracle recommends using interactive
  • applications to update records whenever practical. The interactive applications should always be used when a portion of the records in a table need to be updated. Keywords Date Scan Utility References NOTE:626511.1 - E1: DD: Deploying Data Dictionary Changes Attachments Documentation (539.79 KB) Date Utility - Table Scan Exclusion List.xls (55 KB) Related Products • JD Edwards EnterpriseOne > Keywords DATE~SCAN~UTILITY; 98/UU; CENTCHG; CENTURY~CHANGE~YEAR; DATA~DICTIONARY; EXPIRATION~DATE; JULIAN~DATES Back to top Article Rating Comments Rate this document Excellent Good Poor Did this document help you? Yes No Just browsing How easy was it to find this document? Very easy
  • Provide some feedback Somewhat easy Not easy Cancel
  • World Software Modified 03-AUG-2010 Type ALERT Status PUBLISHED In this Document Description What is being announced? References Applies to: JD Edwards World Information in this document applies to any platform. Description What is being announced? Verify Century Date Settings Important: Verify Century Date Settings in JD Edwards World Before 2011 If you use JD Edwards World software you must take action before January 1st 2011 to check the settings for the default century dates. Calendar dates in JD Edwards World files are stored in Julian date format. To speed data entry, two digit dates are allowed. The system uses data dictionary item #CYR to determine the century that should be used in populating the file. This data dictionary item is also used when automatically populating default effective through and expiration dates in some data files. You should complete the following steps as soon as possible: 1. Review the information in the knowledge document number 656831.1. This document provides a link to detailed steps to check the century default settings, and explains how to update existing data in the JD Edwards World files. 2. Confirm that the data dictionary #CYR has a default value greater than 10. 3. Determine if any of your existing files need default dates updated. For example, if you have used a default date of 12/31/2010 in the past, you may need to update the default expiration date further into the future. Program P4028 will move these dates forward. A list of files that use default dates is available in document number 656831.1. If you do not use these files no data update is necessary. If you have questions or need additional information, please contact Oracle Customer Support for further assistance. References Document 656831.1 Effective-Through Dates and #CYR Default P4028 Document 987084.1 P4028 Expiration Date: Issue with #CYR and Processing Option Dates
  • Related Products • JD Edwards World > Keywords P4028; EXPIRATION; CALENDAR; #CYR; DATA~DICTIONARY; DATE~FORMAT; DEFAULT~VALUES; EXPIRATION~DATE Back to top Article Rating Comments Rate this document Provide some feedback Excellent Good Poor Did this document help you? Yes No Just browsing How easy was it to find this document? Very easy Somewhat easy Not easy Cancel WS: DIST Gen: Effective-Through Dates and #CYR Default P4028 [ID 656831.1] Modified 24-AUG-2010 Type PROBLEM Status PUBLISHED
  • In this Document Symptoms If you are running IBM V6R1 Cause Solution References Applies to: JD Edwards World Procurement - Version: A7.3 cume 4 and later [Release: A7.3 and later ] JD Edwards World Inventory Management - Version: A7.3 cume 4 and later [Release: A7.3 and later] JD Edwards World Sales Order Management - Version: A7.3 cume 4 and later [Release: A7.3 and later] Information in this document applies to any platform. *** Updated 24-Aug-2010 Added doublebyte update *** Symptoms JD Edwards World, default effective-through dates of 12/31/2010 will expire if not updated. If you are running IBM V6R1 You need to perform an additional step in order to install this Update. 1. Download the Update, for example A738576741, which you are going to apply on the V6R1 machine. 2. Once you have the Save file for the update on your System i, download an additional update which contains only Installation programs. The updates are: • V6R1A73INS for A7.3 • V6R1A81INS for A8.1 • V6R1A91INS for A9.1 3. Follow the instructions included with the update. You will copy the Installation programs from V6R1A73INS to the update A738576741, for example. 4. After that continue with the installation of the A738576741 update. Cause Not Applicable Solution 1. Change the default value of the data dictionary item #CYR to allow effective-through default dates to populate further into the future. Oracle recommends a default value of 30. 2. For existing effective through dates that may be populated with 12/31/2010, Oracle has created an update program P4028 to move effective dates forward. The data update program must be run prior to 12/31/2010 if the #CYR default value is 10.
  • If the P4028 attempts to process a record that is locked by another process, it will skip that locked record and will not update it. For that reason, you should run the P4028 when no one is on the system. This program is available as a software update from the Customer Connection Update Center. Software Updates: • Release A7.3: A738576741 • Release A7.3 Double Byte: A738967611 • Release A8.1: A818576750 • Release A9.1: A918576776 This program is included in release A9.2. Please refer to the attached documentation for detailed information beginning with the document Read This First. References Document 987084.1 P4028 Expiration Date: Issue with #CYR and Processing Option Dates Attachments CentryDefault #CYR.pdf (164.39 KB) P4028-Program-Helps.doc (36.5 KB) Read_this_first.doc (69.5 KB) Related Products • JD Edwards World > Supply Chain Management > Distribution > JD Edwards World Procurement • JD Edwards World > Supply Chain Management > Distribution > JD Edwards World Inventory Management • JD Edwards World > Supply Chain Management > Distribution > JD Edwards World Sales Order Management Keywords P4028; #CYR; EFFECTIVE~DATE; EXPIRATION Back to top
  • Article Rating Comments Rate this document Provide some feedback Excellent Good Poor Did this document help you? Yes No Just browsing How easy was it to find this document? Very easy Somewhat easy Not easy Cancel