AGRIS Customer Documentation

How to setup Validate Minimum and Maximum price allowed during Booking and Prepay entry

Item Specific Prepay and Booking price to validate from Minimum and Maximum price allowed (AGR-15724)

If you need to ensure that Bookings and Prepay pricing is enforced within a specific selling range, here are the steps to do it!

There are three security features that control the behavior of the min/max checking:


  1. Navigation: Maintenance>Dataset Maintenance:

Figure "A": System security can be enabled in Dataset Maintenance so the override min/max functionality can be controlled down to the user level.


2. Navigation: INV>Setup Information>Invoicing Setup Options:

Figure "B": General Information screen 1 allows the user to indicate whether or not pricing is allowed outside the Minimum/Maximum range in this current dataset.  If the dataset is unsecured, this is the only setting that is checked to allow the min/max override.

       


3. Navigation: Customize>System Security:

Figure "C": Override Min/Max Pricing security setting can be set for each user in System Security. This will only be checked if the INV setup option allows for the override of min/max values.


Security combinations and behaviors once configured:

The behavior and messages are the same as those in the invoicing application.  When the user enters a price outside of the allowed range for the item the user will be presented with several possible messages based on the scenario.

Scenario 1:

Database is unsecured (Figure A).

Invoicing setup is “N” (Figure B).

User security is irrelevant (Figure C).

 User must correct the condition before continuing.

Scenario 2:

Database is unsecured (Figure A).

Invoicing setup is “Y” (Figure B).

User security is irrelevant (Figure C).

User may choose whether to accept the price or go back and change it.

Scenario 3

Database is secured (Figure A).

Invoicing setup is “Y” (Figure B).

User security is irrelevant (Figure C).

 

User may choose whether to accept the price or go back and change it.

Scenario 4:

Database is secured (Figure A).

Invoicing setup is “N” (Figure B).

User security is sufficient (Figure C).

User may choose whether to accept the price or go back and change it.

Scenario 5:

Database is secured (Figure A).

Invoicing setup is “N” (Figure B).

User security is not sufficient (Figure C).

User may choose whether to accept the price or go back and change it. 

If they accept the price they must provide a user id and password with sufficient security level.

Related Content:


3820 Mansell Road, Suite 350 ✦ Alpharetta, GA 30022 ✦ www.GreenstoneSystems.com
© 2011 - 2024 Cultura Technologies LLC. All Rights Reserved Worldwide.  Products and company names mentioned herein may be trademarks or registered trademarks of their respective owners.