The Oracle General Services Administration (GSA) capability allows the creation of a minimum price level and alerts
the user when this minimum level is exceeded. The alert can include placing an order on hold for review and possible correction when the limit is exceeded.
The minimum or GSA price for an item may be set on
- a special GSA minimum price list,
- a discount list with the minimum price specified or
- as a new (fixed) price type of discount.
A GSA discount is created when the regular item price is reduced to the GSA price for a GSA customer, enabling the discount cost to be recognized. The GSA discount list is available only to GSA customers, who are automatically qualified by checking the GSA box on the Order Management Tab when entering customer information.
GSA pricing is only used if the system profile option QP: Verify GSA is set to YES. If GSA pricing is enabled and the customer is not a GSA customer, then pricing automatically determines whether the selling price for an item violates the minimum allowed price for this item. If the selling price violates the minimum price, then the pricing engine will either alert the user or place the order on hold, based on the profile option OM: GSA Discount Violation Action.
In a non-GSA environment, this functionality can be used to prevent pricing below the allowable minimum price: the GSA price list would list all items and their lowest possible selling prices. The calculation engine would automatically check whether the selling price of an item had fallen below the minimum for all customers.
Creating a GSA price listFirst determine which items are eligible for GSA pricing, and what the prices are. One method is to create a new price list, (probably named "GSA" and something like "GSA_2002") based on a corporate or other price list, then adjust the new price list for the GSA prices. Once this price list is created, use the GSA price sist form to setup GSA pricing to recognize the prices. Note: you will still need to ensure that each GSA priced item is on one of the GSA modifier lines.
Alternatively, you could simply use the GSA price list form to create a GSA price list by entering each item to be priced on the price list line.
A GSA price list has three components:
- Header information
- Price list lines
Example header information is shown below:
The GSA price list is a special form of discount.
Number: an alphanumeric field and a unique identifier
Name: an alphanumeric field which also must be unique
A good practice is to have the name and the number be the same. This makes it easier if someone has to look at the information from SQL.
Currency: the currency unit in which the operation is transacted
Description: a longer text description of the price list
Note that the fields Active and Automatic are grayed out. GSA pricing, once initiated by setting the GSA Verify profile ON is automatically checked.
The list qualifiers button has two allowable options, Customer and Modifier List:
Customer: For this qualifier context, you can select either Customer name (GSA customers only) or site as a Qualifier Attribute.
Modifier List: For this qualifier context, you select Price List as the Qualifier Attribute.
Adding lines to the price listAdding lines to a GSA price list is very similar to adding lines on a modifier. One limitation is that incompatibility levels default to "Level 1 incompatibility" and bucket information defaults to 1. The diagram below shows the Modifiers Summary tab.
You cannot assign line level qualifiers. Do not change the qualifier flexfield sequence for the GSA qualifier in flexfield setup.
Setting GSA profilesGSA is turned off by default in Oracle. To enable it, as Sysadmin, navigate to Setup -> Profiles. The FIND screen will appear, as shown below.
Set the QP: Verify GSA profile to YES to enable GSA pricing.
The possible values for this profile option are:
Yes: Pricing calculation engine tests for GSA violations, any violating request lines are returned to the calling application with a status of GSA violation.
No: Do not test for GSA violations.
This indicates whether the pricing calculation engine should test for GSA violations. The evaluation is performed if a request is for a non-GSA customer, and GSA rules are violated if the selling price of an item is calculated to be less than the price of the item on any GSA price list.
If you wish to be alerted via a warning, select "Issue a warning when GSA rules violated." This will result in a warning, but will not place the order on hold. If you select "Prevent GSA violations by causing error," when a non-GSA customer places an order for an item where the price is less than the GSA minimum, the order is placed on a GSA Hold and must be released for completion.
The screen shot below shows the profile value set for preventing GSA errors (i.e., putting the order on hold).
Releasing GSA holds
When a GSA violation occurs, and the order is placed on hold, and a message is displayed, the user can release the hold as follows:
Starting from the Order Management Super User Responsibility:
1. Navigate to the ordered item which is on hold: OM -> Order Organizer -> Order Number
2. Select Open Order
3. Select the LINES tab and traverse to the order line that is on hold
4. Select the ACTIONS button at the lower left of the screen, and select RELEASE HOLDS from the pull down list
5. Select a reason from the list pulldown, and add any relevant comments.
6. Select RELEASE. A message indicating the hold is released will appear.
This material is copyright 2003 by Carol Francum. It may not be used in whole or part for commercial purposes without the express permission of the author.
Ask the author: Do you have a question regarding Oracle Applications for Carol Francum? Click here to ask her for help.