Answered

Retroactively assigning Party ID to a worker

(0) Share

Report

Posted on by ON-16052045-0

Hello,

This may be more of a HR related question but I will try it here in the Finance forum as well as tangents on position hierarchies and approval flow for 3rd party solutions in AP.

I have an environment in which I have created an assortment of workers and assigned them to a position. Each position in turn is added to a position hierarchy (under the relationships tab) which determines the approval flow in a 3rd party solution.

Now, after having created all the setup (quite extensive) I have discovered that no party IDs were created for the workers, which prevents us from assigning a User to the person (that should be the same as the worker).

Is there a way of retroactively creating party IDs and assigning them to a worker after the worker is already created? I would hope there is a way of avoiding having to create the workers again by creating a Party ID first and then creating a new employee from that.

Any input is appreciated. Thanks in advance,

Oskar

Categories:

Administration and Setup

All responses (2)

Answers (1)

ON-16052045-0 12 on at

Like (1)

Report

Retroactively assigning Party ID to a worker

Hello Andre,

Thanks for the swift response.

It seems as if magically, the workers and their related persons Party ID is now available in the global address book. They were missing the other day, I am not sure of what, if any steps were taken to resolve this or if it was always there but I was unable to see them for some reason. But it does indeed now look as if tho I can associate a user with a person, and that person is derived from the worker that was created.

Appologies for the wasted time and effort.
Verified answer

André Arnaud de Cal... 290,142 Super User 2024 Season 2 on at

Like (0)

Report

Retroactively assigning Party ID to a worker

Hi Oskar,

It is not possible to create workers in the application without having a Party linked to it. The party itself has the name of the worker, not the worker record itself. Can you share a screenshot to illustrate your issue?