Use this routine to configure and maintain a Price List that defines the selling methods, involving one or more products or specific sales terms, applying distinct criteria such as region and price range.
The suggested sales price for a Price List is initially based on the Sales Price (Field B1_PRV1 of table SB1 - Product Register). You should only enter the percentage or discount value in the Price List if the sales price suggested by the Product Register has already been registered. Otherwise, it will not be applied.
Example of Price List application:
Item | Product Code | Product Disc. | Base Price | Sale Price | Discount Val. | Factor | State | Range |
001 | 000001 | Computer | 1,000.00 | 900.00 | 100.00 | 0.90 | SP | 500.00 |
002 | 000001 | Computer | 1,000.00 | 850.00 | 150.00 | 0.85 | SP | 999,999.99 |
In the example above, the Computer product has a 10% discount on its base price when 500 units are sold to the State of Sao Paulo, and a 15% discount when exceeding 500 units.
Besides defining List items as shown above, you can also use the system to determine the validity periods, by date and time intervals, as well as specify a payment term.
Price Lists are marked by a caption, as follows:
In this diagram, the data refer to the features of the routine:
In the main page of the routine, the following options are available:
In the main page of the routine, the following options are available:
486px522
Field: | Description |
| List Code | Alphanumeric field for specifying a code for the Price List being added. When the option is Copy using the option by Others Actions, the system assumes the next available code for the copy. Example: A12 |
| Description | Descriptive field that identifies the list added and/or yet to be added. Example: Default list for the month. |
| Start Date / End Date | In these fields, set the start and end dates of price list validity. Example: 1/1/2016 to |
| Start Time/End Time | In these fields, enter validity schedule of the Price List registered. This information is often used by companies that practice Flash Sales. Example: A given company has decided on a promotion valid on 9/20/2003, from 9:00 AM to 10:00 AM, must set field Start Time to 09:00 and field End Time to 10:00. Sales made from 10:01 AM forward would no longer use this Price List. |
| Paymt Term | Enter the payment term valid for applying this price list. Thus, when adding the Sales Order, the system only checks the payment terms entered in the Price List; otherwise, it notifies that the terms are not valid for the List selected. Use the magnifying glass next to the field or the F3 key to access the default query and thus select the payment term. Example: Prompt payment. |
Group | Use this field to control the price list by product or by product group. To control it by group, in the Product register, enter the group to which the product belongs. If you enter, in the list, the price of the product as well as the price for the group to which it belongs, the system assumes the price of the product, not that of the group. Be mindful that the field has a trigger. If you fill out the group, the product is erased. You must enter either one or the other. |
Type of Schedule | Use the down arrow beside the field to select between: 1-Single - The Price List is valid from the start date (start time) to the end date (end time). In this case, if you register the Price List to be valid from 10:00 AM on 9/17 to 8PM on 9/20, then all sales orders entered in this period can use this list. 2-Recurring - The list is valid between the two dates only between the start time and the end time. Using the previous example, the orders can only use the list during the days of the period, within the time entered; that is, from 10:00 AM on 9/17 to 8:00 PM on 9/20. If the order is issued for 9/18 at 9:00 PM, the system does not accept it for this Price List. |
| Active List | Use the down arrow to select between:
Tip The system lets you apply the factor or the discount value, but never one atop the other. |
| Base Price | The base sale price of a product is defined in its register, through field Sales Price. When you add a Price List, the system offers the base price entered, and fields Sales Price and Discount Value always use the base price of the product as reference. However, if it has not been registered, enter it directly in field Sales Price. |
| Sales Price | Enter the sales price used for a product in the Price List, from the applied factors and discounts. Example: A price list is registered in the following situation: Product Computer; Base Price $1,000.00 and Discount Value $100.00. In this situation the Sales Price is $900.00 (Base Price - Discount Value) |
Discount Value | Enter the discount value to be applied to the Base Price of the product. When you fill out this field, the system automatically calculates the Sales Price field. Tip The system lets you apply the factor or the discount value, but never one atop the other. Example: A price list is registered in the following situation: Product Computer; Base Price $1,000.00; Discount Value $100.00; Factor 0.90 (10% discount on the base price); Sales Price $900.00 (Base Price - Discount Value) The discount value determines the sales price, because it is calculated on the Base Price of the product. |
| Factor | This field determines the factor on the Base Price of the product. The system enters or calculates it when you fill out the field Discount Value. When entered, the system calculates the sales price based on the factor. When the factor is entered, the sales price is calculated. |
State | Enter the State in which the Price List registered is valid. Tip For fields State and Operation Tp., a priority rule exists. When you enter the State, the system disregards field Operation Tp., regardless of its contents. Therefore, for the data found in field Operation Tp. to have value, leave field State blank. |
| Type of Operation | In this field, select the type of operation performed: 1-State - Determines that the Price List is only valid for customers inside the State defined in parameter MV_ESTADO. 2-Interstate - Determines that the Price List is valid for all States, except the State set in parameter MV_ESTADO. 3-North and Northeast Indicates that the Price List is valid only for regions North and Northeast. 4-All - Indicates that the Price List is valid for all States of table 12 - Federative Unit. Tip For fields State and Operation Tp., a priority rule exists. When you enter the State, the system disregards field Operation Tp., regardless of its contents. Therefore, for the data found in field Operation Tp. to have value, leave field State blank. |
| Range | Enter the maximum quantity of products for a given price list. This information is useful to link the price to a given sales quantity. Example: The higher the number of products sold, the lower the price. |
| Activation and Deactivation of Records | The purpose of the reserved field called Status is to allow the activation or deactivation of records, preventing the application from using the inactive ones. 1. Field initialization is always as Active and shows the options Active and Inactive. 2. When the content of the field is set to Inactive, it means the record is blocked, and it is shown in the browser with a different color. |
| E-commerce | The option to send multiple price lists to CiaShop E-commerce, is implemented by marking the field e-commerce Tip The header registration, in which the rules for using the list in the sale are set, is made in the Cia Shop E-Commerce. The integration sends products related to the list as well as their respective prices. Use this feature to have a price list differentiated by rule. The procedures for registering the Promotional and Default Price list remain the same. |
| Product Code | Use the magnifying glass or the F3 key to view the default query and set the product code. Example: Default Product |
| Group | Use the magnifying glass or the F3 key to view the default query and set the product code. Example: 0002 Be mindful that the field has a trigger. If you fill out the group, the product is erased. You must enter either one or the other. |
| Grid Ref./CFG | The Grid Reference family code lets you use the routine practically, reducing the need to repeatedly register products with the same Grid Reference / Configurator. |
| Validity | Use the calendar next to the field or enter the date in format DD/MM/YYYY with the validity date of the pricelist in use. |
| Maximum Price | Enter the maximum price for the specified price list. |
Use this routine to configure or perform maintenance on a Price List and compose various sales types, considering specific sales terms for one or for multiple products, using distinct criteria, such as region and price range.
To compose the discounts and sales price to be applied, the System refers to the product price, set in its register through field Sales Price.
Item | Product Code | Product Disc. | Base Price | Sales Price | Discount Val. | Factor | State | Range |
001 | 000001 | Computer | 1,000.00 | 900.00 | 100.00 | 0.90 | SP | 500.00 |
002 | 000001 | Computer | 1,000.00 | 850.00 | 150.00 | 0.85 | SP | 999,999.99 |
In the above example, the Computer product gets a 10% discount on its base price when 500 units are sold, in the State of Sao Paulo. Above 500 units, it gets a 15% discount.
Besides defining List items as shown above, you can also use the System to determine the validity periods, by date and time intervals, as well as specify a payment term.
Price Lists are identified on the grid, Active Tab column, as follows:
The price list (DA0 and DA1) can register the following information:
DA0 – Header
DA1 – Items
As the payment method and terms are only set at the end of the concomitant sales process, in modules Store Control and Point of Sales, only price lists that lack definitions for these data are taken into account. The fields for payment method and terms become hidden in the Store Control module on the Price List registration screen.
In Assisted Sales and Point of Sales, only the State operation type is handled.
Possible Scenarios | |
Description | Action |
A single price list with product being entered at sale. | The rule set in the price list is used and applied to the value of the product item. |
The product exists in more than one active price list. | It is set by the parameter that defines whether the product value must be selected by the criterion of highest or of lowest value found in the search and applied to the value of the product item. |
No active price list is found for the product. | The sale value of the product is the one registered in the product (field Sale Price). |
There is no price list available for the product and the sale price registered in the product is 0 (zero). | The application notifies that this product cannot be registered, because it lacks a set sale value. |
IMPORTANT!
The grid resource speeds up the registration of products that vary only in a few aspects, keeping their main characteristics.
Thus, you do not need to register the same product multiple times only because the product has various characteristics; that is, you only need to register the main product and all its variants, such as: color, model, etc. This enables Protheus to automatically register all product variants.
IMPORTANT!
The purpose of the reserved field called Status is to allow the activation or deactivation of records, preventing the application from using the inactive ones.
The option to send multiple price lists to CiaShop E-commerce, is implemented by marking the field E-commerce.
IMPORTANT!
Use this feature to identify the relationship between the records created in CRM, which are Suspect, Prospect, Customer, Contacts, Competitors, Suppliers, Partners, Opportunities, Proposals, Sales Orders, Invoices, Products, Price Lists, Sales Process, Sales Representatives, Business Unit, Sales Team, Promotions and Events.
The connection centralizes data on the relationship between an entity and another, making it easier to query them. Through this feature, you can, for example, link data from one Customer to the other, entering the function of the connection. For example: partner, associate, influencer, etc.
If you cannot find a feature that best fits your needs, you can register other connection features and associate them with the corresponding features; that is, when you register the feature "Uncle/Aunt", the corresponding feature will be "Nephew/Niece".
In the Connections Register you can also set the start and end dates of the connection.
You can edit the Price List for quick editing of prices of a specific product.
IMPORTANT!
IMPORTANT!
IMPORTANT!
Action | Description |
Add | Allows access to the screen Price List - Add, in which you can add a new record. |
Edit | Allows access to the screen Price List - Edit, in which you can edit the parameters set for the record selected. |
Search Product in List | Use this feature to search a given record in Lists having a large number of items, through any field of the screen. |
Notes | Use this feature to add, edit or delete comments or notes related to records of the following entities: |
Other Actions > View | Allows access to the screen Price List - View, which displays the parameters set for the record selected in detail. |
Other Actions > Delete | Use this feature to delete the record selected. |
Other Actions > Copy | You can access the Price List - Copy, in which you can create new Price Lists from the List selected, when these have items in common. This option enables registration of Lists with similar characteristics like common items, to avoid having to retype them. The system displays all the fields that were configured for a specified list, earlier selected in the maintenance Price List screen, thereby enabling registration of a new list. In this option you may duplicate List items, which requires adjusting the List header at each duplication. |
Other Actions > Generate | Use this feature to access the screen Price List - Generate, in which you can use a record as reference to create another. When you select products on the routine's Parameters screen, the System displays, in Price List items, all product data already entered; however, you must enter the List header items. In the Validity field you can set the date from which the item on the list is valid, though this field is not required. For price list validity purposes, the System always takes into account the data found in fields Start Date/Time and End Date/Time; however, the List items may have later validity dates. |
Other Actions > Adjustment | Use this option to apply a multiplication factor to adjust the prices of products from lists specified in parameters. |
| Field | Description |
|---|---|
| List Code | Use this code to identify the Price List you are registering. |
| Description | Use this description to identify the Price List you are registering. |
Start Date/Time | These fields determine the Price List validity schedule and are often used in companies that have Flash Sales. Example:
Important! When you add the Sales Order, the date used for Price List validation is the issue date of the Sales Order, not the base date of the System. |
| Paymt Term | Payment term valid for application to the Price List being registered. Thus, when you add the Sales Order, only the payment term entered in the Price List is used. Otherwise, a warning is issued notifying that the term is not valid for the List selected. |
| Schedule Type | Type of schedule to be applied to the Price List, which can be: 1-Single: the Price List is valid from the start date (start time) to the end date (end time). 2-Recurring: the Price List is valid between the two dates only between the start time and the end time. |
| Active List | Enter whether the List is active in the system: 1 - Yes2 - No |
| E-Commerce | Enter whether multiple lists will be sent to the CiaShop E-commerce, by marking this field: 1 - Active Important!
|
| Product Code | Product Code for Price List composition. |
| Group | Use this field to control the Price List by product or by product group. To control it by group, in the Product register, enter the group to which the product belongs. If you enter, in the List, the price of the product as well as the price for the group to which it belongs, the System assumes the price of the product, not that of the group. |
Base Price | The base sale price of a product is defined in its register, through field Sales Price. When you add a Price List, the system offers the base price entered, and fields Sales Price and Discount Value always use the base price of the product as reference. However, you can fill out field Sales Price directly, if it has not been registered already. |
| Grid Ref./CFG | Code of grid reference family, which lets you use the routine practically, reducing the need to repeatedly register products with the same reference of grid/configurator. |
| Sales Price | Sales price used for a product in the Price List, from the applied factors and discounts. Example:
|
| Discount Val. | Discount value to be applied on the base price of the product. Example:
The discount value determines the sales price, because it is calculated on the base price of the product. Important!
|
| Factor | Specifies the factor to be applied on the base price of the product and can be entered or calculated by the system when the field Discount Value is filled out. When entered, the System calculates the Sales Price based on the Factor. |
| Active | Enter whether the factor at issue is: 1 - Active |
| State | Federation Unit in which the Price List registered is in effect. Important!
|
| Tipo Operac. | The type of operation in which the price is valid: 1 - State: the Price List is valid only for customers within the State, as set in parameter MV_ESTADO. Important!
|
| Range | Maximum quantity of products for which the Price List is valid. Example: Important! This information is useful when the price needs to be linked to a sale quantity. |
| Currency | Code of valid currency for the Price List. |
| Validity | Validity date of item that composes the Price List. |
| Maximum Price | Maximum price of product. |
| Price Type | Identification of price type, which can be: 1 - Sales Price2 - Consumer Sale |