E9.2 Renaming fields for all labels / descriptions to reflect usage - Best Practices

sam_b_r

Member
Hi,

I've requested a few changes to our technical team as we are using F4801T WR20 for a specific purpose and I want it to be reflected properly in applications that use it so that in a few years when we're trying to find what field does what we aren't wondering which cat code we are looking for (genuine situation with another cat code elsewhere at the moment) ...

The technical team are talking about application changes - surely either a data dictionary or language description change will just do this and immediately be reflected everywhere? What is the best practice for renaming fields so that applications reflect the correct usage of the field?

Thanks
 
Correct. For global changes just change the DD then it may be necessary to build and deploy a full package.
 
Agree - If you want that DD item description to be changed globally in the system, modify the description and glossary text in the data dictionary to reflect your usage. The new description will show up in every program as long as there isn't a specific override of the description in a specific application. Category Code DD items are typically updated to reflect your custom usage.

Also, best practice is to be tracking changes to vanilla JDE objects. So, however your tech team tracks that they should add WR02 to the list. If for some reason Oracle would push out an update to the WR20 data dictionary item in the future, it would overwrite your change and you would need to re-apply it as part of your retrofit process. It is unlikely that Oracle would modify a category code DD item, but better safe than sorry.

Regards,
Ellen
 
All the above answers are correct but don't forget you are on 9.2.5, so another option for APPLs only is. that you can also use the form extensibility options to change the text everyone sees. Use Xref to get a list of APPL forms
 
Thanks all, I considered form extension, however the rename there is a one-time override and we maintain about 8 languages as is - in fact - does the languages point change anything about DD? Or would it just mean that we would add DD translations where needed as well.
 
When you create a DD item, the Domestic Language Description, Row Description, Column Titles and Glossary text are all pieces of information in the data item definition. Once the DD item exists, you can use Form Exits to work with only the translations (so you don't accidently change something else on the DD item). And yes, you can override the translations provided in the the language pack there as well.
 
Back
Top