Employee job title field length and valid values

[babs]

Question for the HR group:

E1 Employee Job Title YAJBCX is a short, free form field. The length is not sufficient for our titles so we have to shorten the title which is not ideal. With it being free form there is no validation on data entry so there are lots of variations on the same title. We need to increase the field length and would like the field to function like a UDC with only valid values allowed to be chosen/entered.

Has anyone done something like this in E1. A custom/field table is likely required but wondering how others have dealt with one or both of these issues in E1.

Any input is appreciated.

 

[Zaki Ahmed]

Wrong forum: you might get more responses if you put this question in JD Edwards® EnterpriseOne Developers section.

To answer your question, you can either attach UDC at data dictionary level (not recommended) or at form/application level. Unless it is already a custom data dictionary, I wouldn't recommending changing size of it. Rather create a new Data Dictionary and use it in the forms where you need it.

 

[paypal]

The Job Title field is normally used to store alternate job titles that are more meaningful to the employee or for example business card purposes. The main job title field is the Job Type/Step field on the Organizational Assignment form. The description field is also only 30 characters, but the entry point for this code/description is the job information program P08001 which populates UDC table 06/G and/or 06/GS if using step. The user then can only choose the codes that are in the table which then provides the uniformity and continuity you are looking for.

 

[SarahMaeMills]

We had this requirement for some time (longer description/limit to list for JBCX), but determined that 1) we didn't want to mod the DL01 in the DD, and 2) keeping up Working Title (JBCX) in addition to Position Title and Job Title was too cumbersome. We created a custom UBE that copies the employee's Position Title from F08101 to the JBCX field, and we run it on a scheduler. You could do the same using the Job Title to copy to the JBCX, thereby forcing the data value to match, without creating a custom field or customizing the application. Hope that helps in some way.

 

[babs]

Thanks Sarah

We are not currently using Job Types, however, your suggestion is helpful. Think we are going to have to forfeit the extended length to avoid a lot of customization.

May use an EE CC and set trigger to populate JBCX with CC. This may work for us as we will get 2/3 items on wish list, ie; drop down/valid values and history.

Thanks for the input!

Was going to ask this on the SIG call but time ran out!

...barb