Sap pricing procedures

Sap pricing procedures DEFAULT

What is Pricing Procedure?

Pricing procedure in MM module is a way to determine prices in purchasing documents. It give us functionality to assign different calculation types for different needs. Defining a pricing procedure can be done by creating an access sequence, and assigning it to condition types. Access sequence tells the system where to look for the condition values. It can search multiple condition tables based on our settings. Tables have different priority, and different key fields. Determination of the SAP MM or SAP SD Pricing Procedure is practically assigning the calculation schema to a combination of vendor schema group and purchasing organization schema group. So, you need to enter the vendor schema group on vendor master, and assign schema group to purchasing organization, in order for the system to find the calculation schema to be used in the document.

Price Determination in SAP MM

Price Determination in SAP MM

In order to setup a Price Procedure in purchasing documents, you need access to the customizing features.

IMG path to the available functions for Pricing in SAP SD:

Transaction SPRO => Materials Management => Purchasing => Conditions => Define Price determ.process

Pricing Procedure in SAP MM

Pricing Procedure in SAP MM

Following functions can be used to maintain the Pricing in SAP MM. There are more settings concerning the Pricing Procedure determination in SAP SD & SAP MM, but we will cover the most used ones.

SAP MM Pricing Procedure

SAP MM Pricing Procedure

Sours: https://www.guru99.com/overview-of-pricing-procedure.html


In this post we will configure all aspects of SAP S4 HANA MM Pricing Procedure. Before starting S4 HANA MM pricing procedure , we will have a look at the pre-requisite configuration, which is required before configuring Pricing Procedure in SAP S4 HANA

Pre-Requisite Configurations

Below diagram is showing the configuration (& related posts) required to complete before starting configuration of S4 HANA pricing procedure.

Link to each post is given below

1. Configure SAP Finance Organization Structure in 5 Minutes

2. Configure SAP S4 HANA Material Management Organization Structure in 5 Minutes

Once we have completed all the above configurations, we are ready to configure MM Pricing Procedure.


Understanding of SAP S4 HANA MM Pricing Procedure


SAP S4 HANA MM Pricing Procedure can be Bifurcated in Two Parts


Technique behind S4 HANA MM Pricing Procedure (Condition Technique)

To understand SAP S4 HANA MM Pricing Procedure, We need to first have an overview of the working of the pricing conditions in the MM. To understand this we need to understand condition technique. Pricing is broadly used to describe the calculation of price & costs. During Purchase Order processing, the system uses the condition technique to determine automatically the various cost components like discounts, surcharges, freight etc.


Determination of Pricing Procedure

In this section we will see how to Configure MM Pricing in 5 easy steps.

Let’s start with technique behind working of pricing procedure


Condition Technique in S4 HANA MM Pricing Procedure

Condition technique involves the following below elements in sequence.

  • Condition Types
  • Access Sequences
  • Condition Tables
  • Calculation Schemas

Let,s review all the four elements of condition technique one by one


Condition Type


In SAP S4 HANA MM Pricing Procedure, the first step in defining pricing is configuration of condition types.

We create different type of condition types representing discounts, surcharges, freight, cost, taxes etc. to complete our pricing schema.

Let’s review the configuration of condition type and all the fields associated with it.


Fields in “Control Data 1” Section of Condition Type Configuration


Below fields are available in control data 1 section of condition type configuration

Condition Class


This field determines the category of condition type like : Price, Tax. Discount or surcharge etc.

The most common classes are as follows

Condition Class “B”


If a condition type is being configured for gross pricing then condition class “B” will be used.


Condition Class “A”


If a condition type is being configured for Quantity or weight discount then condition class “A” will be used.


Condition Class “D”

If a condition type is being configured for taxes then condition class “D” will be used.


Calculation Type


This field determines how the condition type will be calculated.

The most common used calculation types are

“B”-For Fixed Amount,

“A”-For percentage

“C”-For quantity

“G” for our own formula

if we use calculation type “G” in a pricing procedures, a condition basis formula and a condition value formula must be assigned to this calculation type.

Note : The formula define here (in MM pricing procedure) works the same way in SD. We use VOFM for the same.


Condition Category


Condition Category is the classification of condition types such as FREIGHT, TAX, PRICE, DISCOUNT.

The condition categories are always hardcoded.


Condition Category “F -Freight” vs “B -Delivery costs”


If the vendor is same for Main Purchase Order & Freight then we can select the F category

But if the transportation vendor is different then the Purchase order vendor then we need to select the “B” delivery cost condition category

With condition category “B – Delivery Cost”, we will have the option of entering delivery vendor (other than main vendor) for that condition type in PO and also option of posting this cost to different G/L account based on account key setting in Accrual column in MM pricing procedure and G/L account assignment in OBYC for that account key.

Hint

Condition types are differentiated broadly using the condition class and more definitively using the condition category.

Rounding Rule


Rounding rule determines the rounding up value of the condition type. If the value is set up as “Commercial” then value is rounded off, for example $9.364 round off to $9.36


Plus/Minus Value


This configuration determines if condition type value is treated as positive value or negative value.

Negative values are discounts and positive values are surcharges.

Note : A blank value represents a positive.


Fields in “Group Condition” Section of Condition Type Configuration


Below three fields are present in this section of condition type configuration

Group Condition


if this field is checked , then such condition type is determined based on the cumulative value of the line item. for a group condition, all the values of the relevant items (price, order quantities etc) are added and then total is used as condition bases.

For example : a PO has several line items . There is a discount group condition in our PO which gives 10% discount if PO value is exceeds by 1000$ for a particular material group items. in this case if total value of this material distributed in several line item is calculated and compared against 100$ in order to arrive on discount decision, though individually such PO line item may not qualify for discount being less than $1000 order value.


Rounding Difference Comparison


if this field is checked then system compares the total of line items condition values to the condition value at the header level and difference is added to the largest item.


Group Condition Routine


This is used to calculate any alternative value as base to determine the scale value. For example – Group condition base can be a total of all line items weight which belongs to a particular material groups.


Fields in “Changes which can be made” Section of Condition Type Configuration


Below fields are given in this section of condition type configuration. Let’s review all the fields one by one

Manual Entries


This fields controls the priority of a condition type between manual entries and determined automatically .

Options available are “No Limitations”, or “Automatic entry has priority” which means cannot be entered manually, or “Manual Entry has priority” which means if entered manually, system does not check if a condition record exists and final option “Can not be processed manually”.

Header Condition/Item Condition

The selection of these checkbox determines if the condition type is a header condition type or item condition type.


Delete

This specifies if deletion of this condition type is allowed from the documents


Value


This field controls whether the value can be overwritten on the sales/purchase documents


Calculation Type


This field controls whether we can change the calculation type while processing the document


Amount/Percentage


Controls whether amount or percentage can be changed during document processing.


Quantity Relation


This field controls if conversion factor for the unit of measure of this condition type can be changed during document processing.


Fields in “Master Data” Section of Condition Type Configuration


This section has below fields.


Ref. Condition Type, Ref. Application & Pricing Procedure

A pricing condition type sometimes can have a reference to another pricing condition type. We will understand the use of all the above fields through a real scenario

Our requirement is that a pricing condition should flow from PO to Billing for a STO.

In Billing Type, the Pricing Procedure will be SD Pricing Procedure with normal Price Determination settings. But we will not maintain condition Records (through VK11) but we will set Reference Condition , Reference application & reference pricing procedure while configuring this Condition Type (V/06) under “Master Data” Section of Condition Type Configuration as shown in above screenshot.

Now System will access the Condition Record of the Referred Condition Type & reference Application (M – Purchasing).

The other example is a requirement that the Freight paid to Shipment Vendor should be exactly same as one charged to Customer in Sales Order / Invoice. Thus we will use Reference Condition to fulfil this requirement.


Condition Index


This field controls if condition index will be updated or not. we can select this for faster searches.


Fields in “Scales” Section of Condition Type Configuration


This section of the condition type configuration has several scales related fields. We will review all the fields here.


Scale Basis


if no scale type is entered (if this field is blank then it means Scale “Can be maintained in condition record”), then we can specify scale related to money value (scale basis B) or qty (scale basis C) or a weight (Scale basis D or E).


Check Value


This field controls if the scale can be maintained in ascending or descending order.


Scale Type (with Real time examples)


The possible values for scale type are

Blank-Can be maintained in condition records


A : Base Scale

Example of Scale type A

From 1 Unit Price is $10

From 11 units price is $9

From 21 price is $8

So if we create a PO for 30 unit then per unit price would be at a discount of $8


B : To Scale

Example of Scale type B

Up to 10 Unit Price is $10

Up to 20 units price is $9

Up to 30 unit price is $8

So if we create a PO for 30 unit then per unit price would be at a discount of $8

C : Not Used


D : Graduated Scale

in normal scales , system determines one price. while in graduated scale, multiple prices are possible in the pricing screen of an individual item.

Example of a graduated scale

From 1 unit to 10 Unit Price is $10

From 11 to 20 units price is $9

From 21 to 30 unit price is $8

So if we create a PO for 30 unit then first 10 units will be$100, next 10 units will be $90 and the last 10 units will be $80 so PO value will be $270.


Scale Routine

if standard scale bases are not sufficient then we can write our own formula to determine alternate scale basis value. Scale formulas are created through VOFM.


Scale Unit (Unit of Measure)


This unit of measure is used for group conditions that are weight or volume dependent.


Fields in “Control Data 2” Section of Condition Type Configuration


There are several important fields in “Control Data 2” Section of Condition Type Configuration. Let,s review them

Currency Conversion


If we select this indicator then currency conversion happens after the multiplications of the quantity.

Example – Our company is purchasing some components from abroad, main PO is in INR but freight is in USD so to avoid rounding errors, freight condition type will have this indicator checked so that freight is calculated after the quantity is multiplied.


Promotion Condition


Specifies that the condition type is valid only for promotions. Conditions for which this indicator has been set can only be maintained via the ‘Promotion’ menu – not via the Purchasing menu.


Accruals


This field controls if Condition is Relevant for Accrual (e.g. Freight)

Indicates that the system posts the amounts resulting from this condition to financial accounting as accruals. This appears as statistical on documents i.e. not taken into account in the calculation of net price.


Used for Variant Configuration


This indicators indicates that condition is relevant for variant configuration.


Inter-company Billing


Indicator that defines a condition as relevant for the inter-company process.

Inter-company conditions are usually statistical in the sales order and the customer invoice and not statistical in the inter-company invoice.


Condition Exclusion Indicator


This field controls whether the system automatically excludes the discounts that are proposed during pricing. For example- if a customer is already receiving a favourable price then the discount should be excluded.

We can use exclusion for a particular condition record or for all records of a particular condition type (the field appears on the screen where you define the condition type).


Relevant for Acct. Assignment


If field is blank then condition type is relevant for account assignment.

If “B” is chosen , then the accounting indicator is taken into account for the account assignment.


Condition for Invoice List


Indicates that the condition type is relevant for internal costing


Quantity Conversion


This field controls the quantity conversion during determination of the condition basis.

The field is only relevant for calculation rule ‘C’ (quantity- dependent).

It is relevant if the sales quantity unit and the condition quantity unit are identical (and is different to the basis quantity unit).
•Deactivated: The condition basis quantity is converted via the quantity to the stock keeping unit. This means that the condition quantity is determined for planned factors. This means that a change to the conversion factors in the delivery or the order are not taken into account.
Rounding errors can occur during quantity conversion.
•Activated: If the sales quantity unit and the condition quantity unit are identical, the quantity of the document item is used, i.e. the actual quantity.


Fields in “Sales Pricing” Section of Condition Type Configuration


This section has two fields as given below.

Relevant to Pricing


Indicates that a condition is taken into account during purchase price determination in the sales price calculation function.

The indicator can be maintained during definition of condition types and is taken as a default value when condition records are generated. This default can be changed when the “Pricing relevance can be changed” indicator is set.

In scales, the indicator is used to select the scale line used for price determination in Sales Price Calculation.


Pricing On/Off


if this indicator is set, whether each individual condition record is to be taken into account in the sales price calculation function.


Click HERE to read more on condition technique on SAP help


Access Sequence


An access sequence may be assigned to a condition type. The access sequence is a search strategy that enables you to specify the order in which condition tables are to be searched for relevant entries for a condition type.

Silent features of Access Sequence

  • The order of the accesses is determined by the order of the condition tables in the access sequence.
  • The Exclusive indicator determines that the search for further valid entries in (other) condition tables is interrupted if an access was successful and a relevant entry was found.
  • A condition type must have an access sequence assigned to it if you want to maintain conditions with their own validity periods(for example, condition type PB00).
  • No access sequence assigned to header conditions, discounts, or surcharges


Requirements in Access Sequence


An access sequence is a search strategy to find the valid data for a condition type. Access sequence outlines the sequence in which system searches for the data.

Every access has a requirement associated with it and every requirement has a routine associated with it. Routines are ABAP codes that perform validation when the particular condition type is associated.


Exclusion Indicator


If we check this indicator then as soon as valid condition record is found , system stop the further searches for condition records.


Condition Table


In a condition table, we specify the combination of fields for which we create condition records.


Screenshot of a condition table

Note : Field catalog consists of all the available fields , from which condition table is created.

Calculation Schema


Calculation schema is used to calculate costs, prices, period-end rebates, and taxes. This concept is referred to in the Sales and Distribution (SD) area as a pricing procedure.

Calculation schema (pricing procedure) specifies which condition types are to be taken into account in which sequence.

We have configured below schema for our car company.


Similar schema is configured for Elect car company too.

Let,s review all the components of calculation schema


Manual


We check this checkbox if we need to input the value of a pricing condition manually. For example – unplanned freight or a special discount based on the quality complaint of the customer.


Required


This field is selected if a condition is mandatory i.e. document (sales order/purchase order)should not be completed if this pricing condition is not entered.


Statistics


This is used when this pricing condition is not required to be included in total value of PO, but only displayed in PO. For example – Rebate condition types. The rebate value is calculated but does not add to the value of PO. When rebate agreement is settled at that time these conditions are used.


Subtotals


This configuration Controls whether and in which fields condition amounts or subtotals are stored. For example-a customer discount or the cost of a material.

Example

These condition amounts or subtotals are used as a starting point for further calculations. For example – a subtotal of all the discounts included in the pricing of a sales order.


Requirements


Most of the time pricing needs can not be met by just defining condition type, access sequence, condition table & condition records.

For this SAP has given VOFM routines. These routines are customizable if standard routine is not capable of meeting the requirements. For example – distribution of discount among line item according to the volume instead of value.

Requirements in pricing procedures are used to validate certain conditions before a condition type is activated. For example – a condition need to be activated only if material belongs to a specific material group. We can define our own requirements starting from 900.


Alternative Calculation of Condition (Formula Condition Value)


Sometimes pricing conditions needs to be calculated by special formula. We can do this through small ABAP code and inputting this routine into the pricing procedure here.


Alternative Calculation of Condition Base Value


Routine for determining the condition basis as an alternative to the standard.

For Example : An absolute header discount is, for example, distributed in the standard system according to the cumulative value of the items.


Account Key


Through this key , pricing condition type is linked to GL account. We use this key in OBYC transaction to link this to the respective GL where the value of this condition type need to be posted. This represents MM-FI integration.


Account Key – Accruals / Provisions


With this account key, the system can post amounts to certain types of accruals accounts. For example, rebate accruals


Pricing Procedure Determination


In this section we will see how pricing procedure is determined in our purchasing documents. Pricing is determined by a combination of schema groups defined by vendors & purchasing organizations.

We need to understand Purchasing info record (PIR) to understand the pricing determination.


PIR


PIR maintains the relationship between material and vendor. Prices in PIR are defined at material level or purchase organization level. Prices from the last created PO stored in PIR is automatically proposed in the PO.


Configure MM Pricing determination in 5 easy steps

Below are the steps in brief to determine pricing procedure in 5 easy steps

Time needed: 10 minutes.

How to Configure MM Pricing in 5 easy steps

  1. Define Schema Group for Purchasing Organizations

    (PA10-IC Car Puchase.org. Schema Group, PP10-Elect Car Purchase.org. Schema Group)

  2. Assignment of Schema Group to Purchasing Organization

    (PA10->PA10, PP10->PP10)

  3. Define Schema Group for Suppliers

    (I1-PA10 IC Car Vendor Schema Grp, E1-Elect Car Vendor Schema Grp, I2-PA20 C Car Vendor Schema Grp)

  4. Define Calculation Schema

    ICCAR001-Schema for IC Car, ELCAR001-Schema for Elec Car

  5. Define Schema Determination

    Check the respective section for details on schema determination

Step 1 : Define Schema Group for Purchasing Organizations


These allows us to group together purchasing organizations that use the same calculation schema.

|Here SAP has given flexibility if we want to have separate scheme for different purchase org like service purchase organization & Material purchasing organization or export purchasing organization

|
for our car business, we have created two Schema groups for both the Purchasing Organization

Step 2 :Assignment of Schema Group to Purchasing Organization

Step 3 :Define Schema Group for Suppliers


Here through this we can assign different pricing determination procedure to different suppliers.

Step 4 :Define Calculation Schema

Step 5 : Define Schema Determination


We will define Standard Purchase Order Schema determination. For STOs we will do it later in special post.

At present we are assigning same schema for the vendors of PA10 & PA20 Plants. Please note that, if require, we have made provisions to have separate schema for the vendors of PA10 or PA20 through different vendor schema group as per above step

In the next post we will see price calculation in PO as per our schema


Image courtesy : Sale vector created by jcomp – www.freepik.com

Sours: https://www.saplogisticsexpert.com/ultimate-guide-to-sap-s4-hana-mm-pricing-procedure/
  1. Sunflower eucalyptus bouquet
  2. 2016 action anime
  3. Lee pai long
  4. Nsfw reddit wiki
  5. Ikea chesapeake va

How to Define Pricing Procedure Determination in SAP SD

In this SAP tutorials, you will learn how to define pricing procedure determination in SAP SD module step by step using transaction code OVKK.

Pricing Procedure Determination in SAP SD

During sales documents processing, the SAP system automatically determines a corresponding pricing procedure. Pricing procedure determination is based on combination of sales area, document pricing procedure and customer pricing procedure.

Navigation

SAP R/3 Role MenuPricing Procedure Determination
Transaction CodeOVKK
SAP IMG PathSPRO (Tcode) => Implementation Guide for R/3 Customizing (IMG) => Sales and distribution => Basic functions => Pricing => Pricing control => Define and assign pricing procedure => Define pricing procedure determination

Step 1: – Execute tcode “SPRO”

SAP Reference IMG Tcode

Step 2 : – Choose SAP Reference IMG (F5).

SAP Reference IMG Screen

Step 3 : – Follow the IMG menu path and click on img activity”define and assign pricing procedure”

define and assign pricing procedure in SAP

Step 4 : – Choose activity screen displays, double click on “Define pricing procedure determination”.

Define pricing procedure determination SAP

Step 5 : – On change view “Pricing Procedures: Determination in sales docs”: overview screen, click on new entries button.

Pricing Procedure determination in sales documents SAP

Step 6 : – On new entries pricing procedure determination screen, update the following details.

How to Define Pricing Procedure Determination in SAP

After maintaining all the required details, click on save button and save the configuration details of pricing procedure determination in SAP.

Note : – As per per clients requirement, you need to define separate pricing determination with in a group of customers (For e.g. whole sellers, Online sellers, etc). Different pricing procedure for a customers depending on the sales documents. However you can configure pricing procedure determination with combination of sales organization, distribution channel, divisions, pricing procedure, condition types based on the requirement of clients.

Successfully we have created pricing procedure determination in SAP SD.

❮ PreviousNext ❯

➥ PDF Download - How to Define Pricing Procedure Determination in SAP SDSours: https://www.tutorialkart.com/sap-sd/define-pricing-procedure-determination-in-sap/

Define Pricing Procedure

16 Fields in Pricing Procedure and Their Description

  • A pricing procedure is a procedure by where in which you control the execution of condition tyoes in a sequence you would like . It not only executes the condition types but also controls the execution of condition type by the use of requirements , altcv. altcbv, account key.
  • In other words, Pricing procedure is a systematic and sequential use of condition types to arrive at a right value of the product.
    To determine the pricing procedure SALES AREA (Sales Organization + Distribution Channel + Division) + CUSTOMER PRICING PROCEDURE (from Customer master) + DOCUMENT PRICING PROCEDURE (from Sales Doc type)
    To view a select the pricing procedure in SPRO which is the standard and copy it and create our own pricing procedure.
  • Highlight it and double click the Control icon in the LHS screen.
  • We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
  • The detail description of each column is given below:

1. Step:

  • Number that determines the sequence of the conditions with in a procedure.
  • It indicates the position of the condition type in pricing procedure.
  • Ex.: 10, 15 etc.

2. Counter:

  • System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
  • Access number of the conditions with in a step in the pricing procedure.
  • During automatic pricing, the system takes into account the sequence specified by the counter.

3. Condition Type:

  • It represents pricing element in pricing procedure as a base price, discount, freight and tax.
  • The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
  • Ex.: PR00 - Price, K004 - Material Discount, K005 - Customer/Material Discount, K007 - Customer Discount.

4. Description:

  • System copies description of condition type from its description (V/06).

5. From and 6. To:

    1.This can be used as a base to the condition type for calculating further value.

    2.The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.

7. Manual:

  • This indicator specifies whether the specific condition type can be determined manually during sales order processing.
  • If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
  • For Base Price and Taxes, the entry should be automatic.
  • For Discounts and Freights, The entry should be manual.
  • If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
  • If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.

8. Mandatory:

  • This indicator specifies that particular condition type is mandatory in the pricing procedure.
  • If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
  • If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
  • Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
  • If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.

9. Statistical:

  • This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
  • It is used only for information purposes only.
  • This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
  • This is commonly used for condition types
    • SKTO - Cash Discount
    • VPRS - Cost (Moving average price/Standard Price).

10. Print:

  • The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.

11. Subtotal:

  • The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
  • Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
  • If the same fields are used to store different condition amounts, the system totals the individual amounts.
  • These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.

12. Requirement:

  • It is a routine that is written by an ABAP consultant according to the business requirement.
  • By defining Requirement in condition technique we can restrict the access of condition type.
  • To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
  • For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
  • This Requirement will ensure that these condition types will appear only during the billing document processing.
  • If new Requirements are to be defined we follow the procedure given below.
    • Go to T.Code: VOFM. - Maintain Requirements & Formulas
    • Click on the "Requirements" in the top menu and then click on "pricing".
    • We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
    • And we assign the application type like V - Sales/Distribution etc.

14. AltCty - Condition formula for alternative calculation type:

  • It is again a Routine that is written by ABAP Consultant.
  • It is an alternative formula for the condition type that can be used instead of standard formulas.
  • For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
  • Ex.: 950 0 Profit Margin 11.
  • So we assign 11 - Profit Margin.
  • If new routines are to be defined we follow the procedure given below.
    • Go to T.Code: VOFM. - Maintain Requirements & Formulas
    • Click on the "Formulas" and then on the "Condition Values".
    • We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
    • And we assign the application type.

15. AltCBV - Alternative formula for condition base value:

  • Formula for determining the condition basis as an alternative to the standard.
  • It is again a Routine that is written by ABAP Consultant.
  • It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
  • Ex.: Freight - KF00.
  • Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
  • In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
  • During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
  • Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.

16. AcyKy - Account Key/ Accrls - Accruals:

  • The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
  • In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
    • ERB Rebate sales deduct.
    • ERF Freight revenue
    • ERL Revenue
    • ERS Sales deductions
    • ERU Rebate accruals
  • For Ex.,
    • For all Price condition types like PR00 etc. we assign ERL - Revenue.
    • For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
    • For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
    • For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
  • This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
  • This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
Sours: https://sites.google.com/site/sapipcdeveloper/16-fields-in-pricing-procedure-and-their-description

Procedures sap pricing

Pricing procedure is a way to determine prices in purchasing documents. Pricing procedure gives functionality to assign different calculation types for different requirements. Pricing procedure used to determine all conditions into one procedure where the sub-total finds for net amount.

The prices are calculated based on the condition methods used in. The condition method is a procedure of defining condition records in to the sales document while processing.

Creating an access sequence and assigning it to condition types can define pricing procedure. Pricing procedure determination is assigning the calculation schema to a combination of vendor schema group and purchasing organization schema group.

The pricing procedure structure is –

  • Condition technique contains condition records
  • Condition records are stored in condition tables
  • Condition tables places in access sequences
  • Access sequence assigns to condition type
  • Condition types placed in pricing procedure

Define Pricing Procedure: -

Below process is to define pricing procedure TCPP01 TC Pricing Procedure –

Step-1: Enter the transaction code V/08 in the SAP command field and click Enter to continue.

Define pricing procedure

(OR)

Enter the transaction code SPRO in the SAP command field and click Enter to continue.

Define pricing procedure

Click on SAP Reference IMG.

Define pricing procedure

Expand SAP Customizing implementation guide → Sales and Distribution → Basic Functions → Pricing → Pricing Control → Define and assign pricing procedure. Click on Execute.

Define pricing procedure

In the next screen, select Maintain Pricing Procedure and click on Choose button.

Define pricing procedure

Step-2: In the next screen, click on New Entries button.

Define pricing procedure

Step-3: Enter the below details and click on Enter.

  • Procedure - Enter 6-digit alphanumeric procedure code
  • Descript. - Enter the procedure description
Define pricing procedure

Step-4: Select the newly added procedure row and double click on Control/Control Data.

Define pricing procedure

Step-5: In the next screen, click on New Entries button to add tables.

Define pricing procedure

Step-6: Enter the below details and click on Enter.

  • CTyp - Specify the required condition types.
  • Description - Description automatically updated by the system.
  • Manual - Check this option if required. If the option is checked, it specifies that the entry is manual.
  • Required - Check this option if required. If the option is checked, the entry is required for pricing.
  • Reqt - Select the requirement from the list. It specifies the condition type has to be determined during the pricing in sales document.
Define pricing procedure

Step-7: Once all the details entered, click on the Save button to save the changes.

Define pricing procedure

Step-8: It prompt for the Change Request. Create/Select the change request and Click on right mark to proceed.

Define pricing procedure

Step-9: Status bar displays the below message once the pricing procedure created successfully.

Define pricing procedure

Technical details: -

  • Transaction: V/08
  • Menu Path: SPRO → SAP Reference IMG → SAP Customizing implementation guide → Sales and Distribution → Basic Functions → Pricing → Pricing Control → Define and assign pricing procedure
Sours: https://www.tutorialscampus.com/sap-sd/define-pricing-procedure.htm
SAP SD Pricing complete class along with Routines and Condition records.

What is Pricing Procedure – Define Pricing Procedure in SAP

In this SAP tutorials, you will learn what is pricing procedure and how to define pricing procedure in SAP SD using transaction code V/08.

What is Pricing Procedure in SAP

Pricing Procedure determines the price of goods and services in SAP system. When you are processing sales documents the system calculates the documents price by considering the condition types. Each pricing procedure in sap consists its own set of condition types to determines the prices of goods and service for the respective customer categories.

Purpose of configuration

In this activity you define customer pricing procedure to calculate the value of goods & service. We need to place the condition types in a sequence order. The SAP system determines the pricing procedure on the basis of

  • Customer master data
  • Sales data
  • Sales document.

How to define pricing procedure in SAP

Navigation

SAP R/3 Role MenuMaintain pricing procedure
Transaction CodeV/08
SAP IMG PathSPRO -> Implementation Guide for R/3 Customizing (IMG) > Sales and distribution > Basic functions > Pricing > Pricing control > Define and assign pricing procedure.

Note : – You define new customer pricing pro

Step 1 : – Execute tcode “V/08”.

maintain pricing procedure tcode SAP

Step 2 : – On change view procedures overview screen, click on new entries for creation of  pricing procedure in SAP.

what is pricing procedure in SAP

Step 3: – On new entries pricing procedures screen, update the following details.

  • Procedure : – Enter the key that defines as pricing procedure in SAP.
  • Description : – Enter the description of pricing procedure.
Define Pricing Procedure in SAP SD

Now click on save button and save the configured pricing procedure details in SAP system.

Step 4 : – Select the pricing procedure and double click on control tab.

SAP Pricing procedure control data

Click on new entries button and specify the required condition types in required order.

Pricing Procedure control new entries SAP

Update the following details.

Step : – It specifies the sequential number of condition type in pricing order.

CTyp : – Update the required condition types

Description : – The description of condition type will be automatically updated by SAP system.

Manual : – It enables to determine conditions during pricing in sales documents either if they are entered manually or from other application.

Required : – If you check this option for condition type, it becomes mandatory during pricing in sales documents.

Reqt : – The requirement specifies condition type has to be determined during pricing in the sales document. If a condition type to be determined in to sales document, the requirement specified here must be specified.

create pricing procedure in SAP SD

After maintaining all the required details, click on save button and save the configured details.

Successfully we have maintained pricing procedure in SAP SD.

❮ PreviousNext ❯

➥ PDF Download - What is Pricing Procedure - Define Pricing Procedure in SAPSours: https://www.tutorialkart.com/sap-sd/what-is-pricing-procedure-define-pricing-procedure-in-sap/

Similar news:

Come on, confess immediately. Otherwise, I will definitely get up now. Very much, I love you. Of course, I love you Zhenya.



1815 1816 1817 1818 1819