DD Item Glossary Text and Upgrades

[aimeeb]

Hi all,

As usual, any help would be greatly appreciated.

I have recently completed the upgrade of our B7332 system to Xe. We have a heavily customised installation and generally testing has been very successful.

However I have one problem I haven't been able to fix. As I say above all of our bespoke objects have been merged successfully. Also all our bespoke Data Dictionary items have been been preserved and merged. Except they are no longer displaying any Glossary text. Priously all items that we have added have been given associated text. This has disappeared. The same thing has also happened to the the glossary text for our custom error messages.

Does anyone have any idea what has happenned and how I can retrieve the text for these data items and messages?

Many thanks in advance for any assistance,

Rob Boden
OneWorld Xe
Intel NT 4.0 sp6a Enterprise with SQL 7.0 sp3

 

[Zoltan_Gyimesi]

Hi Rob,

Extract your Data Dictionary texts from F9202, F9203, F00165 (all in Data Dictionary Data Source) on your B7332 system and append/update the same tables with these records under XE (also in Data Dictionary Data Source).

I didn't checked that did these tables change from B7332 to XE, supposly did not, but you can easily print out the definitions of these tables from TDA on both system and compare them.

Let us know that how did it work if you have tried this method.

Good luck,
Zoltán

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)<P ID="edit"><FONT SIZE=-1>Edited by Zoltan_Gyimesi on 10/29/01 10:27 AM.</FONT></P>

 

[mtrottier]

If you haven’t upgraded PROD yet you can compare how B7332 is accessing the Glossary Text as opposed to XE. My guess is that it is related to the keys in the F00165 table.

I recently upgraded a client from B733 to XE and had a number of issues regarding the F00165 (media objects) table. This table contains, among other things, Glossary Text. In this customers case they reported missing attachments. During my investigation I found that there were some changes to the way some of the new XE applications retrieved records from this table. These changes should have required a table conversion program be written for historical records in the F00165 but this fell through the cracks at JDE.
Example:
1. F00165 Records where GDOBNM = ‘BUDGETGT’ needed to be stet to ‘GT14102’
BUDGETGT was an obsolete key that was replaced with GT14102

2. The same was true when GDOBNM = JEDTLGT it was replaced with ‘GT0911A’

3. Another one was more interesting. I found that in B733 where GDOBNM = JEDTLGT that the GDTXKY field stored and retrieved records following the format of:
'X7|152873|00060|1.0|20010708'
'X7|152873|00060|2.0|20010708'
'X7|152873|00060|3.0|20010708'

After the upgrade I found that XE was storing and retrieving records following the format of:

'X7|152873|00060|20010708|1.0'
'X7|152873|00060|20010708|2.0'
'X7|152873|00060|20010708|3.0'

Note the moving of line number from the 4th position to the 5th.

JDE help desk had no explanation for these discrepancies and no conversion programs available so I ended up writing my own.

I know these are not related to your issue but it may give you an idea of what to look for. I tracked these down by turning on debug for both B733 and XE and comparing the SQL statements against the F00165 table.

Please let me know what you find so I can alert my client to a potential issue.







Mike Trottier
Independent CNC Consultant
Onsite and Dial-up Support
B731,B732,B733,XE
AS400,Unix,NT
Oracle,SQL
#801 557-8368