If we take an unused field on HR11 and use it for something else such as rehire eligibility is it possible to change the title of the field in the tables without messing things up. I can change the display title in design studio, but when that field is used in personnel actions it is displayed with the original field name. so instead of Rehire Eligible it shows as Union Code. Since we are pushing termination actions out to management for completion that is too confusing. Any Ideas?

Why not use a userfield on HR11 for this instead?

We currently have so many user fields the end user would have to page dow three times to get to that field. They want it to land in thier lap not look for it.

Have you asked your DBA?

Not a good idea to change the field name on the Oracle table.

Your DBA could make the change in the test environment if you'd really like to see how much breaks.

I agree with the others, it's a really bad idea. :bonk:

I would rather see you (not that I recommend this either) add a new field to the table and maintain that rather than change an existing field.

This is a little off topic but - You said that you have too many userfields - can you create a Design Studio form to reorganize the userfields so that they all show on one page?

We have had to change the description of a field, over in AR not in HR. What a pain!

- Track down every screen where it exists and change it.
- I'm assuming that with Portal, you'd have to re-label every screen with Design Studio
- Find every reference label to that field in Screen Rules and change it.
- Find every reference label in Object Rules and change that too.

Real easy, huh? Actually, since I keep meticulous notes, not that bad. Worked like a charm. :thumb:

The one thing that we never, ever do is to change the file structure, or rename fields. Not the thing to do, will limit Lawson's support big-time! :bonk:

Good luck.

Data storage is data storage, I would add a userfield then add the field to the term action to make sure it gets entered. The win is the user interface and reporting, not in the data storage. So then I would make a query tool, using 4GL, design studio, crystal enterprise, etc. where someone can search by name to verify a rehire status.

To be even more creative, I would look into building an automated process with custom programming or Lawson process flow so that when an application is marked as a prospect in our applicant tracking system, that it checks the Lawson database for rehirability (is that a word?) and flags the recruiter/hiring manager.

Another option is to create a custom language (langdef), and use a phrase translation to translate the phrase "Union Code" to "Rehire Eligible".

Once a custom language is create, you will need to define a custom Locale (locdef) and assign it your custom language.

After creating the custom locale, create a foreign language tranmap using the "genformap" command and assign the locale to your users via LAUA or each user can assign the locale to their ID via Portal/Preferences/User Options.

We currently use a custom language for our HR users to translate over 20 HR phrases, and it's a lot easier than Design Studio because it translates the phrases everywhere: Drill Arounds, Screens, and Reports, etc...

The only on-going maintenance that is required, is to run the "genformap" command anytime a MSP or HR CTP is applied.

Can you use Design Studio to display just a specific user-field?

1) Define a new userfield "ReHire" in HR04.4, which adds the entry to table HRUserFields, note what the field_key is.

2) Add the new field to a form (HR11.1 Main?), displaying only that field from HREmpUsf where field_key = xx

Thanks I think we are going to go with the custom language option it seems to work well in our test sytme. passing the translation out to manager self service also. Thanks for all the suggestions.