- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
pricing
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 06-08-2007 11:42 PM
Hi,
I need to work on pricing in my job.
I would like to know what are the tables and fields that we mostly work with in pricing .
I would appreciate any tips on this topic.
Thanks
Sara J
- SAP Managed Tags:
- SD (Sales and Distribution)
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Refer the link
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDBFPR/SDBFPR.pdf
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
Step 5:
Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure, ... are in place.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Answers (7)
Answers (7)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
<b>Pricing Procedure:</b>
 Pricing procedure: A sequential list of condition types and subtotals.
 All condition types permitted in pricing are contained in the pricing procedure.
 You determine how the system is to use conditions by specifying requirements for each condition.
 The sequence in which the system accesses conditions in the business document is also determined here.
 The reference level provides a method to specify a different basis for the condition type calculation and for grouping conditions for subtotals.
 The pricing procedure can contain any number of subtotals between gross and net price.
 You can mark a condition type in the pricing procedure as being:
--> a mandatory condition
--> a manually entered condition
--> for statistical purposes only
<b>Pricing Procedure Determination & Overview</b>:
 In this example, an order for 120 pieces of a material is created. The system must determine the price automatically.
 First, the relevant pricing procedure is determined based on the sales area, customer, and sales document type.
 The system reads the condition type of the first step. It determines the assigned access sequence for this condition type.
 The system reads the access sequence. The sequence of condition tables represents the search strategy for finding the relevant condition record.
 Each condition table represents one access which can be made for a condition record with the specified key.
 The system searches for valid condition records with the key specified by the condition table (accesses).
 If the first access does not find a valid condition record, then the system searches for the next access using the next condition table.
 Once the system finds a valid condition record for an access, it reads the condition record and copies the value that corresponds to the scale into the sales document.
 The whole process is repeated for each condition type until the system has finished the entire pricing procedure.
<b>Pricing Configuration</b>:
 The <b>condition table</b> contains the keys that can be used for creating dependent condition records.
 You can add your own condition tables using table numbers 501 through 999.
 An <b>access sequence</b> is composed of one or more condition tables.
 After creating the access sequence, it is assigned to a condition type.
 You can also create your own <b>condition types</b>. You determine the characteristics of each condition type, for example, whether it is for surcharges or discounts and whether it should be dependent on values or quantities.
 The condition types are combined in the required sequence in the <b>pricing procedure</b>.
 Finally, you need to maintain the procedure determination table for the pricing program.
The pricing procedure is determined according to:
>> Sales area
>> Customer pricing procedure field in the customer master
>> Document pricing procedure field in the sales document type.
<u><b>condition table</b></u>
 Condition records are always created using a specific key.
 Use tables for help in defining the structure of condition record keys.
 The most important fields used in pricing at header and item level are available in the standard system.
 The key fields of a condition table must appear at the start of the table, in other words, non-key fields must not appear between any two key fields.
 A condition table is a combination of fields, which form the key for a condition record.
 Condition table: The definition of the key of the condition record.
<u><b>Access Sequence</b></u>
 The access sequence determines the sequence in which the condition records for a condition type are found and read.
 An access sequence (search strategy) is defined for each condition type (with the exception of header and manual only condition types) in the pricing procedure.
 This search strategy defines the sequence in which the system reads the condition records for a condition type.
 Each access performed during the access sequence is made using a condition table.
 You can make an access dependent on certain requirements.
 You can define prices, discounts, and surcharges at various levels.
 Each level is defined by a combination of fields or by a field in a condition table.
 Using the access sequence, you can define the sequence of the different levels.
The system attempts to determine the condition records in the sequence specified.
 Within each access of an access sequence, you can specify the specific document field (source field) with which an access is carried out.
 Examples:
> Material or pricing material?
> Document currency or local currency?
> Sold-to party or ship-to party?
 Make accesses dependent on requirements to avoid unnecessary accesses. This reduces the system load.
 Access sequence: A search strategy to locate the proper condition record.
<u><b>Condition Types</b></u>:
 The condition type determines the category of a condition and how it is used.
 The calculation type and the scale base type can be controlled for each condition type.
For Example: Scale for Condition Type PROO
1 pieces 800 uni
10 pieces 750 uni
100 pieces 700 uni
 Possible scale base types - Possible calculation types
Value - Percentage from an initial value Fixed amount
Quantity - Amount per unit of measure
Weight - Amount per unit of weight
Volumes - Amount per unit of volume
Time period - Quantity per unit of time
 Each condition type can be set as an automatic surcharge, discount or either.
 Condition types: A calculation or formula used for a component of pricing.
Regards,
Rajesh Banka
Reward points if helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
KONV - Condition for Transactional Data
KONP - Condition for Items
Regards,
Rajesh Banka
Reward points if helpful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hi,
check in SE11 for,
KONV
KOMV
KONP
Structures
KOMG
KOMK
KOMP
pl reward if it helps.
Thanks
Sadhu Kishore
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
Similarly in MM Module we have Pricing Schema.
Regards,
Rajesh Banka
Reward points if helpful.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hi
look at
Pricing tables
Posted: May 17, 2007 9:11 PM
hans
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi sarj,
give you id.. i will send you the complete tables ... ok.. most important tables are KOMP/KOMK...
Reward if it helps
Ramki
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
hi ,
KOMG is the document structure and KOMK and KOMP are the two most important table which are used for pricing in SD.
thanks
madhan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- In the sales order header prices are getting zero or not able to see the conditons in Enterprise Resource Planning Q&A
- How to update UoM Price for item where pricing unit isn't the same as UoM Group default unit? in Enterprise Resource Planning Q&A
- Cost in the Pricing tab when creating Customer Return wo reference in Enterprise Resource Planning Q&A
- Wrong Translation Date in billing document in Enterprise Resource Planning Q&A
- MRN2 does not change material price in Enterprise Resource Planning Q&A
| User | Count |
|---|---|
| 100 | |
| 11 | |
| 11 | |
| 6 | |
| 6 | |
| 5 | |
| 4 | |
| 3 | |
| 3 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.