Impact of Changing the Size of a Standard Data Dictionary Item

This document details the impact of changing the size on a standard EnterpriseOne Data Dictionary data item. The document includes the impact and some examples of the results when making this type of change.

Scope

Details

Overview

Making a change to a standard EnterpriseOne data dictionary item is not recommended or supported. Tables, business views, applications and business functions are designed with the standard size of the data item and making a change to this size can result in errors within the applications and data integrity issues. If a data item size is changed, all tables using the data item would need to be generated, any data entered would need to be manually converted, all business functions that use the data item in their data structures would need the header files updated and business functions rebuilt, all business functions that reference tables that contain this data item would need to be rebuilt, and so forth. This is a widespread change that impacts all objects across the system that use the data item. In addition, this type of change is not supported in an upgrade.

NOTE: Based on the above implications of this type of change, we do not recommend making any changes to the size of standard EnterpriseOne data dictionary items. We recommend that the additional information be contained within another field, within a custom data dictionary item in a custom table or some other logic be used to achieve the needed results. By default, changing a Data Dictionary item affects all environments as the recommended configuration is to have one Data Dictionary F9210 in the Data Source 'Data Dictionary'

Issues that Can Occur when Changing the Size of String Data Dictionary Alias DL01

In EnterpriseOne, thousands of objects including Tables, Business Views, Business Functions, Data Structures, etc. make use of the Data Dictionary item DL01 as a member, column, or parameter.

The following are some discrepancies that can occur as a result of a size change of this standard DD item.

Based on the above implications of this type of change, we do not recommend making any changes to the size of standard EnterpriseOne data dictionary items. We recommend that the additional information be contained within another field, within a custom data dictionary item in a custom table or some other logic be used to achieve the needed results. In case the existing size does not meet your legal requirement, then inquire with Oracle Global Support for further clarification

Consequences of String Data Dictionary Size Change to Unit of Measure

The following example shows the results of a string data dictionary size change. In this example, the size of the standard EnterpriseOne Data Dictionary item with DD Alias 'UOM1' UnitOfMeasurePrimary (Unit of Measure - Primary) was changed by a developer at the customer's site from a size of 2 to a size of 3.

Symptoms

After building a full package, multiple errors across EnterpriseOne are occurring.

Some examples of the errors are:

Cause

This issue is caused by the change of the standard EnterpriseOne string Data Dictionary item UOM1 from the shipped size of '2' to a size of '3' digits. This type of size change is NOT supported and results in widespread errors throughout the system.

Calling Business function VerifyAndGetItemMaster
from Level 1 for UserID. Application Name [P3002], Version [ZJDE0001] (BSFNLevel = 1)
IN->[ 1] szPrimaryItemNumber [4418-0031-000]
IN->[ 2] szBranchPlant []
IN->[ 3] szDescription [ ]
IN->[ 4] szDescription2 [ ]
IN->[ 5] cSymbolidentifier [ ]
IN->[ 6] idF4101LongRowPtr [0]
IN->[ 7] mnShortItemNumber [0]
IN->[ 8] cErrorcode [ ]
IN->[ 9] szLanguagepreference [ ]
IN->[ 10] mnAddressnumber [0]
IN->[ 11] szSystemcode [ ]
IN->[ 12] szLongItemNumber [ ]
IN->[ 13] szThirdItemNumber [ ]
IN->[ 14] szItemFlashMsg [ ]
IN->[ 15] cReturnPtr [1]
...
Entering JDB_FetchKeyed
SELECT * FROM PRODDTA.F4101 WHERE ( IMLITM = '4418-0031-000' )
Fetched the record
OUT->[ 1] szPrimaryItemNumber [4418-0031-000 ]
OUT->[ 2] szBranchPlant []
OUT->[ 3] szDescription [D1 - FRAME ]
OUT->[ 4] szDescription2 [ ]
OUT->[ 5] cSymbolidentifier [2]
OUT->[ 6] idF4101LongRowPtr [1001]
OUT->[ 7] mnShortItemNumber [1517]
OUT->[ 8] cErrorcode [ ]
OUT->[ 9] szLanguagepreference [ ]
OUT->[ 10] mnAddressnumber [0]
OUT->[ 11] szSystemcode [ ]
OUT->[ 12] szLongItemNumber [4418-0031-000 ]
OUT->[ 13] szThirdItemNumber [AFC-FR-D1-001~999 ]
OUT->[ 14] szItemFlashMsg [Y 10 ]
OUT->[ 15] cReturnPtr [1]
...
Return value is 0 for VerifyAndGetItemMaster. (BSFNLevel = 1)

imlitm	...	imuom1	...	imback	imifla	imtfla
4418-0031-000		EA		Y		10

imlitm

...

imuom1

...

imback

imifla

imtfla

4418-0031-000

To resolve this issue:

NOTE:

To avoid these type of errors, never change the size of a Standard EnterpriseOne Data Dictionary Item. This change is not supported and can have widespread system ramifications.
Unless you have deleted TAMSpec for DDDICT and GLBLTBL globally the change made from the Data Dictionary will take effect only when the full package is built. That is why issue is described as occurring after deploying a Full Package.
By default, changing a Data Dictionary item affects all environments as the recommended configuration is to have one Data Dictionary F9210 in the Data Source 'Data Dictionary'