HCS Position Manager and Lawson

Margie,

We use PM. Technically, we open reqs for everything, but the recruitment team does post some "dummy" reqs for high applicant volume positions and hires onto a req that was approved but posted/on hold. We interface back and forth... positions, Hiring managers, and Approvers to PM. Then we get back hired applicants (hires or internal transfers), filled reqs, and closed onboarding documents (mapped to ImageNow).

We use this process for employed team members and for most non-employed team members (like students and trainees).

Let me know if you have any other questions or if I have not answered yours completely.

Thank you for the response. To clarify, the recruitment team is actually opening reqs for positions that actually exist. Ours want to open a req to be the equivalent of the old days of paper apps when a candidate would fill out the app and apply for "any open position". Do you have anything like that? I can create a Lawson position with phony values but wondered if others do the above and there was a better way.

No, we do not. I'm not certain how people would keep up with that since there has to be a responsible recruiter assigned to the open job. I guess if your recruitment team is centralized and small they may benefit from an applicant pool like that. Our teams are somewhat centralized, but work with specific business groups as Generalists. They would probably never see those applicants so it would become a point of frustration for the applicants, I would think. Feel free to let me know what you come up with, because I have a feeling our team would like something like this just to assuage applicants who reeeeaaaallly want to get their foot in the door here.

I did create a generic position code and job code in Lawson. Time will tell if this works out for them or not.