Provide a setting to disable the location validation in sequence screen

Issue No: CT-2650
Created 10/24/2018 6:33:31 AM
Type Bug-QC
Priority Blocker
Status Closed
Resolution Fixed
Fixed Version 18.1
Description For a user in the user role tab if the location is not configured, currently contract sequence screen it is not allowing to select the location. This is restricting users from creating contracts from their central offices at JDE. Provide a setting which can control this feature that will allow all locations or not in contract sequence screen.   * How it worked in 17.1 ** Users can see all the locations that are configured in i21 while creating the contract ** Users select the location for which they are creating the contract ** This location has no relationship to user's location level access as they are only creating contracts from their central offices for their locations (manufacturing plants) * How it is working in 18.1? ** Contract screen is showing only the locations to which they the access rights ** This restricts users from creating contracts for their manufacturing plants from their central offices since all planning and purchasing happnes from their central offices. ** JDE has flagged this as a critical defect since it is impacting their basic contract creation process * How customers such as JDE use this? ** Customers like JDE, Struass, etc have their central offices that do all the sourcing on behalf of their manufacturing plants (locations) ** This gives them better purchasing and negotiating power, vendor relationship, discounts, etc ** The central offices will create contracts for all their manufacturing plants (locations) based on the need plan that individual plants communicate to their central office periodically. ** That is the reason why we cannot expect the users at central offices to be permissioned for all their locations in order to create contracts * Expected result: ** User should be in a position to create contract for any location without restricting them based on their location level permissioning ** It should basically work they way it worked in 17.1 - this is a critical feature for JDE