Diego79
04-03-2007, 01:42 AM
You are performing an inventory transfer between two warehouses belonging to two different OPM Organizations, but all belonging to same Operating Units. While making the inventory transfer the organization code is not validated against the source warehouse and target warehouse. For example, the Organization 'LWB' belongs to a particular Operating Unit OU1. This Organization comes from the setting in session parameter form
The Source Warehouse: 'KWC ' belongs to a different OPM organization belonging to a second Company (other Operating Unit OU2)
Destination warehouse can be chosen only from the list under the second Company OU2
You expect the following restriction: validate the source warehouse code with the Organization code LWB in the header because you expect the source warehouse code should belong to the OPM Organization code used in the Transfer header form.
However, this is not the intended functionality of this feature. The source warehouse should be limited to the warehouses to which the user has access (whole organization access list in user organizations form), not only the warehouses from the current session default Organization
You can then create and release transfers only from those source warehouses that they have access to.
But then you cannot enter a Target warehouse that you do not have access to (so preventing from inter operating Unit transfer).
Also a you should be allowed to complete (receive) the transfer ONLY in the organizations that are in your organization access list i.e. user organizations. But you can receive such a transfer from any organization irrespective of the access to the source organization of the transfer.
In the inventory transfer form the users will be able to:
create transfers from and to any warehouse that they have access to (providing they belong to same OU)
release transfers only from those source warehouses that they have access to
receive transfers only to those target warehouses that they have access to
The source and target warehouse list of values are restricted to the warehouses that user has access to. User access is validated during create, release and receive of transfers. If the receiving user does not have access to the target warehouse then the transfer will have to be cancelled and a new transfer will have to be created with the correct target warehouse that the user has access to.
The Source Warehouse: 'KWC ' belongs to a different OPM organization belonging to a second Company (other Operating Unit OU2)
Destination warehouse can be chosen only from the list under the second Company OU2
You expect the following restriction: validate the source warehouse code with the Organization code LWB in the header because you expect the source warehouse code should belong to the OPM Organization code used in the Transfer header form.
However, this is not the intended functionality of this feature. The source warehouse should be limited to the warehouses to which the user has access (whole organization access list in user organizations form), not only the warehouses from the current session default Organization
You can then create and release transfers only from those source warehouses that they have access to.
But then you cannot enter a Target warehouse that you do not have access to (so preventing from inter operating Unit transfer).
Also a you should be allowed to complete (receive) the transfer ONLY in the organizations that are in your organization access list i.e. user organizations. But you can receive such a transfer from any organization irrespective of the access to the source organization of the transfer.
In the inventory transfer form the users will be able to:
create transfers from and to any warehouse that they have access to (providing they belong to same OU)
release transfers only from those source warehouses that they have access to
receive transfers only to those target warehouses that they have access to
The source and target warehouse list of values are restricted to the warehouses that user has access to. User access is validated during create, release and receive of transfers. If the receiving user does not have access to the target warehouse then the transfer will have to be cancelled and a new transfer will have to be created with the correct target warehouse that the user has access to.