Forums / Categories / JD Edwards EnterpriseOne Human Capital Management SIG / Use JDE Address Book # vs. Legacy HRIS system # for employee id?

    Use JDE Address Book # vs. Legacy HRIS system # for employee id?

    We are migrating from a legacy HRIS system to JDE HCM and are debating what to use for the Employee number:  a) overwrite the JDE Address Book number for staff with the old legacy HRIS employee id number or b) adopt the JDE Address Book number as the new employee id number, or c) keep the JDE Address Book number as well as the distinct employee id number in a seperate field.

    The legacy employee id is used / linked to a number of other external applications (i.e. benefit provider, legacy interfaces, etc.) so that would be advantageous.  Moving to the default Address Book number seems a simple approach for all things related to JDE (i.e. scripts, custom code, screens, etc.) but has ramifications to external systems.

    Does anyone have experience with this decision and advice on what we should think about - or what to watch out for that could cause problems for us?

    Thanks!

    Forrest Kvemshagen - District of Saanich

    When we did our conversion 10 years ago, we used the Employee Quick Hire application to create the employees, and we let it create the JDE address book number for each employee.  We put the number from the legacy system in the F060116Z column called EmployeeNumberThird (OEMP).  This populates the Alternate Number field in the Employee Master.

    One of the reasons that we did this was so we would not have conflicts with other address book numbers.  For example, if we already had a customer or vendor with the same address book number as one of the employee numbers from the legacy system, then we would have a problem if we tried to assign an employee to that number.  Whenever we have an aquisition, we let JDE assign next numbers for address book numbers, short item numbers, etc., and we put the legacy number in another field if needed.

    Travis Wendland

    Project Manager

    Little Rapids Corporation

    Hello:

    We
    chose option a) for our conversion – approximately 18 years ago. We
    had approximately 5000 employees and wanted to maintain the
    original employee number for benefit and pension reporting
    purposes.  After the import of our employee information into
    JDE, we were able to set the next numbers in JDE at a value above
    our existing employee and accounts payable numbers. We have not
    experienced any problems with this strategy.

    |

    |

    Julie Kovacs, CPA, CGA

    |
    |

    Manager, Employee Systems

    Human Resources & Corporate Services

    |
    |

    City of London

    |
    | |

    300 Dufferin Avenue, London, ON  PO Box 5035 N6A
    4L9

    Phone: 519.661.2500 x 1761  Fax: 519-661-2373

    [email protected] | www.london.ca

    This e-mail and any attachments may be confidential or legally
    privileged. If you received this message in error or are not the
    intended recipient, you should destroy the e-mail message and any
    attachments or copies, and you are prohibited from retaining,
    distributing disclosing or using any information contained herein.
    Please inform us of the erroneous delivery by return e-mail. Thank
    you for your cooperation.

    Yes. I agree to block a range of Address Book Number for Employee
    #. This is what we have now in our JDE.

    Sent from my BlackBerry 10 smartphone on the TELUS network.

    |

    From: Quest Online Community
    Sent: Thursday, April 20, 2017 10:39 AM
    To: Edgar Maung x3067
    Reply To:
    [email protected]lworldlabs.net
    Subject: Use JDE Address Book # vs. Legacy HRIS system

    for employee id?

    |

    |
    quest-logo.png |
      |
    |

    |
    Hi Edgar! |
    Instant Alert |

    You are receiving this communication because of your
    subscription settings. You can manage your site subscriptions by
    logging in and visiting your account settings on your dashboard.

    |

    [Use JDE Address Book # vs.

    Legacy HRIS system # for employee id?](https://www.questdirect.org/groups/forums/viewtopic/177/230/515?post_id=936#p936) in Discussions

    Posted
    on April 20, 2017 at 12:37 PM

    | no-image-small.png
    Julie
    Kovacs
    |

    Hello:

    We
    chose option a) for our conversion � approximately 18 years ago. We
    had approximately 5000 employees and wanted to maintain the
    original employee number for benefit and pension reporting
    purposes.  After the import of our employee information into
    JDE, we were able to set the next numbers in JDE at a value above
    our existing employee and accounts payable numbers. We have not
    experienced any problems with this strategy.

    |

    |

    Julie Kovacs, CPA, CGA

    |
    |

    Manager, Employee Systems

    Human Resources & Corporate Services

    |
    |

    City of London

    |
    | |

    300
    Dufferin Avenue, London, ON  PO Box 5035 N6A 4L9

    Phone:
    519.661.2500 x 1761  Fax: 519-661-2373

    [email protected] | www.london.ca

    This
    e-mail and any attachments may be confidential or legally
    privileged. If you received this message in error or are not the
    intended recipient, you should destroy the e-mail message and any
    attachments or copies, and you are prohibited from retaining,
    distributing disclosing or using any information contained herein.
    Please inform us of the erroneous delivery by return e-mail. Thank
    you for your cooperation.

    |   |

    [Reply By Email](mailto:[email protected]lworldlabs.net?subject=Use JDE Address Book # vs. Legacy HRIS system # for employee id? )
    |    |

    Reply On Site
    |
    |
    Unsubscribe from
    topic
    |
    New Topic |

    |

    |
    |
    Quest International Users Group
    Contact Us
    |
    � 2016 Quest International Users Group |
    |
    You are receiving this notification as a member of Quest
    International Users Group. To adjust your notification settings,
    visit your account page. Is this email going to your junk mail
    folder? Add [email protected] to your address book or
    move this message to your primary inbox. If you'd like to
    unsubscribe from the Quest Online Community emails, please click here. |

    To manage your notifications settings,
    click here: Notification
    Settings
    . To unsubscribe permanently from all site updates,
    click here: Unsubscribe

    On the many implementations I have done, we
    have always used the long address number field (ALKY) in F0101 to
    store the legacy address number.  Then we just use standard
    functionality of next number to assign the employee new JDE number
    (AN8).

    Marcia
    Holmes-Rousell

    IT
    Business Systems Analyst

    O:
    206.701.2259

    When we converted from our legacy system we had already been using JDE for several years so the legacy employee numbers could not be used, they were already used in the existing address book. We decided to use the top end of the JDE address book for our employee numbers and have used that since. All new employee numbers are keyed using 90xxxxxx as the number, not allowing the next number to assign the number. We entered the old numbers in the Alternate Employee Number field (OEMP) in the Employee Master.

     

Looks like your connection to Quest Oracle Community was lost, please wait while we try to reconnect.