craz
+1
тут и тут

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.

построить, и задеплоить пакет на рабочие станции
либо варварски прибить файлы датадикшенари

ONYX,Deploying Data Dictionary Changes to Client Workstations

To deploy data dictionary changes to a client workstation, delete the global table specs and data dictionary table specs - glbltbl, dddict, ddtext (.ddb and .xdb) under each pathcode. This is a total of six files. They are located in the /pathcode/spec directory. The next time the user signs-on to the EnterpriseOne software, these table specs will JITI (Just in Time Install) to the workstation from the data dictionary master table when the data dictionary items are referenced in interactive or batch applications. This will bring the current data dictionary information from the master table to the local workstation specifications.


Deploying Data Dictionary Changes to the Enterprise Server

Data Dictionary JITI is enabled on the server; therefore it is not necessary to run R92TAM and TAMFTP a new set of data dictionary specs to the server. Instead, on the server, end services, delete the global and data dictionary table specs (glbltbl, dddict, ddtext - .ddb and .xdb) under each pathcode, and restart services. The global and data dictionary table specs will be recreated through JITI as UBEs or business functions run on the server and reference data dictionary items.


Deploying Data Dictionary Changes to the Terminal Server

In a TSE environment, for performance reasons, it is recommended that JITI be disabled. Therefore, a full set of global and data dictionary table specs must be installed on the Terminal Server. Once a full set of data dictionary and global table specs have been created, copy these tables specs (glbltbl, dddict, ddtext - .ddb and .xdb) from the fat client workstation where they were created to the Terminal Server for each pathcode. See below for details on creating a full set of data dictionary and global table specs.



Deploying Data Dictionary Changes for the Web (HTML) Client

To deploy data dictionary changes for the web client environment for releases prior to EnterpriseOne 8.12, a full set of the data dictionary and global table specs should be created and installed on the generation machine.

In the HTML environment, data dictionary information is built into the serialized object information for the applications that use the data dictionary items. Therefore, when making a data dictionary change, it is not enough in the HTML environment to generate only the data dictionary. The related objects that use the data dictionary item must be generated as well. Therefore, rather than attempting to identify all the affected objects, it is easiest to do a full generation or full package build depending on the release level.