We have OneWorld and employees may me assigned to ...
# administration
m
We have OneWorld and employees may me assigned to one of three Subsidiaries. I just had an urgent request to force all newly created Requisitions to one specific Subsidiary. I looks that the Subsidiary defaults from the Employee. I tried to force this using a Workflow and it didn't work. I will appreciate any information you can share. Thank you
s
turn on the centralized purchasing and billing in the enable features > items & inventory. It will allow you to create PO and Req from any sub. This does have other implications on inventory though - better check that out before turning it on. Consult suiteanswers
m
Thank you for the information. I will investigate and test, but at this moment, it is urgent I do something to default all new Reqs and PO to be created under one Subsidiary only, and I was wondering if there is anything that can be done via Workflows.
s
Note that subsidiary is defined by the employee subsidiary and it cannot be changed no other way around not even by workflow because subsidiary has to be exposed to the entity (employee). Only option is to use the centralized ordering and receiving feature. They promised that multi sub employee type is coming just like vendor and customer eventually then it could be possible
m
They keep promising that and never deliver. Thanks a lot for the information.
s
Multi entity employee is not that easy to implement too many underlying tables and objects tied to it.
k
You cannot have multi-subsidiary employees for tax reasons. Cannot be an employee of UK and US at the same time, different laws, etc. So it will be one sub until….
👍🏼 1
to limit POs and Reqs to just one sub - easiest is to limit all vendors to just that one sub. Worst come to worst have a separate vendor for Sub X called Vendor for Sub X (vs Vendor), Still you cannot disable already existing sub X on the vendor record if transactions on that sub took place. Perhaps a script would work forcing just one sub for POs and Reqs?
👍🏼 1