1. Cashiers had access to Price Override functionality specifically to be able to increase price.
2. Previously when the cashier reduced the price of an item, the percentage of price reduction was controlled  by the discount percentage set at user level. If cashier had "0" set as the "discount amount" then supervisor access was required if prices had to be reduced. This came in handy when prices were marked off significantly when they reached near expiry.
3. Now from version 8.18 and above, we have separated the Price override from discount. We had to remove access for price override from cashiers role as this would have given cashier access to sell at 0 price. 

1. Roopesh Gift Shop gave cashiers access to "Price Override" to sell more than RRP price to certain customers.
2. Shop fittings has set prices at Price Level 1 to 3 as well as the RRP. If customers asks for discount, cashiers could select price 1 which is a few cents cheaper than the RRP. If customer requested for more discount than price level 2 was chosen. Cashiers did not need to know the price off hand in this scenario as this was set in system. Due to Separation of the functionality, price over ride access had to be removed as Cashiers were found selling below cost. The selection of Prices from Price Level is controlled directly by the Price Override functionality.

1. We control the price reduction using the "discount amount" set at user maintenance. We don't have to display the difference between the new unit price and RRP in the discount field. The value set as "discount amount" for each user would be solely to control the percentage of price reduction by user

Hi Sanjay

Further to our development meeting dated: 21.08.2018 between Alvis, Sanjay and Rashna, please review this case. I need to give access to users for price override up only. At this moment, giving access to price override gives users to even sell at 0. We have to note that clients had this functionality before even though control was at discount percentage value. For client, we have removed an important feature from the system by resolving our price change calculating incorrect tax issue. 

Please review and if possible add it as a patch release.

Regards
Vineet Ram

Hi Vineet, this case needs to be written clearly. There is a lot of "Noise" in the paragraph. Close this case and create a new one with clear and relevant information only.

Thanks

-- Development Meeting 19.09.2018 Sanjay Alvis, Vineet --

Agreed on the following design:

1. "Allow price change" will be used to enable/disable the "Unit Price Field" in the price change form. The option to enable this field will be added based on username and password.
2. Discount Amount value will be used to determine the discount amount only. If discount amount is 0, this indicate discount is not allowed. The option to enable this field will be added based on username and password.
3. When Price Label value is 0, disable the button in the price change form.

Approved for development in version 10.1

1. Removed "Discount" from "User Maintenance". The following procedures were changed to remove "Discount" column:

• LT_SAA_User_Select
• LT_SAA_USER_Insert
• LT_SYA_USER_SELECT
• LT_UTILITY_MergeApplication

Assigned to Sanjay to complete changes as per comment 3.

1. The following changes were made(Include Database object names, Program classes and any other relevant information):|

1. Price Change field is READ ONLY when the user does not have access
2. Added User security icon to allow "price change user security" prompt
3. Changed procedure to disable "Price Label" Button when Price Label amount is zero
4. Discount is allowed based on Discount amount value rather than "Discount Allowed" field

1. The following changes were made(Include Database object names, Program classes and any other relevant information):|

1. Discount is based on user's discount limit and products configuration.
2. The security access "640-14 Allow Discount to Sale Total" was added since we did not check item properties (refer to case 1254 comment 11). Since minimum profit margin is now checked, we can remove "640-14".

1. The following changes were made(Include Database object names, Program classes and any other relevant information):|

1. Changed message to show "Price change by:". If authorisation is not required and price is changed, the note will show current user

Hi Sanjay, 

Documentation has been updated under below sections

• Systems Manager -- Master Security -- Role Menu Access -- POS Role Menu Access.
• BO Inventory -- Maintenance Setup -- Product Price

Thanks