SCM Academy SD02 Condition Technique

BearingPoint SCM Academy

Sales Order Management

Part 2: Condition Technique

Kathrin Finn / Marc Lttringhaus

March 18, 2010

Introduction

SD Pricing Objects

Practical Approach in CPSC E26 Client 900

Overview of the Relevant Master data / Org. Structure

Interrelation of Customizing and Application

Content

2010 BearingPoint GmbH 2SCM Academy


Special Customizing Settings

Day to Day Application

Subset OSS Notes

Exercise I

Condition Technique: Definition

is a technique by which the system determines values from information stored in condition records.

Automatic determination of elements leaving open the possibility of manual changes

Possibility of data maintenance on different levels (key


Possibility of data maintenance on different levels (key combinations/ condition tables)

Flexibility

A condition is an agreement defining e.g. for a price accordingto defined influencing factors customer, customer group andmaterial. It remains valid for a specified period.

Condition Technique: Components

Condition type

Condition table

Access sequence

Procedure (scheme)


Condition Technique: Where Used in SAP SD

Pricing

Output determination

Material determination

Account determination (only customizing, no condition records)


(only customizing, no condition records)

Content

Introduction

SD Pricing Objects








Subset OSS Notes

Exercise I

Overview: Condition Technique / Pricing

The term pricing is used broadly to describe the calculation of prices (for external use by customers or vendors) and costs (for internal purposes, such as cost accounting).

Conditions represent a set of circumstances that apply when a price element is calculated.E.g. a particular customer orders a certain quantity of a particular product on a certain day. The variable factors here - the customer, the product, the order quantity, the date - determine the final price


the product, the order quantity, the date - determine the final price the customer gets. The information about each of these factors can be stored in the system as master data.

This master data is stored in the form of condition records.

Overview: Condition Technique / Pricing

The term condition technique refers to the method by which the system determines prices from information stored in condition records.

The various elements used in the condition technique are set up and controlled in customizing.

During sales order processing, the system uses this condition technique to determine a variety of important pricing information.


technique to determine a variety of important pricing information.

Pricing objects: How They Work Together (1/2)


Pricing objects: How They Work Together (2/2)

Condition

Type

Access

Sales document

Pricing

procedure

Sales

AreaCustomer

Customizing

- PR00 Price

- K007 Cust. Disc.

- MWST Output Tax

Pricing

date


Condition

Table

Access

Sequence

Customizing

Applicatio

n

10 Cust./mat. w rel.stat40 Mat. w rel. status

Key fields

Condition

Record

Price

Discount

Tax

SD Pricing: Pricing Objects (1/2)

The condition type defines the economic meaning of a pricing element.

The set of potential conditions types for a process is combined in a pricing procedure.

Condition values can be determined on different levels via a key combination of parameters. The fields on each level (accesses) are defined in condition tables.


defined in condition tables.

The levels are searched via a strategy, the access sequence.

The values for each specific set on a level can be stored as master data in the form of condition records.

SD Pricing: Pricing Objects (2/2)


SD Pricing Objects: Condition Record

Combination of key fields

Validity period


The condition record stores values for a defined set of parameters (key fields).

You define a validity period to confine a pricing agreement to a particular period of time.

Tx: VK12 never date a used price condition back.Use VK11 (create) and VK13 (display) instead

SD Pricing Objects: Condition Type (1/5)



All pricing elements used in day-to-day pricing procedures are defined as condition types.

The condition type defines e.g. the

condition class, i.e. the character of the pricing element: price, discount / surcharge, freight, tax

scale base type: How does the system interpret the scale of a condition?


scale of a condition?

calculation type: How are the price elements calculated?

Plus/ minus indicator: Does the condition result in a negative (discount), positive (a surcharge) amount or are both possible ?

Pricing date (default: document date)


It furthermore defines

if manual changes are allowed

if the condition can be entered on header or item level

Header conditions

can only be entered manually (no automatic pricing via access sequence)


access sequence)

Are broken down on item level (based on mode defined in BasType of pricing procedure)

Group condition indicator

Item conditions: marks if the system calculates the scale basis value from more than one item in the document

Header conditions: decides if the same value is broken down or if the value is divided acc. to item values


Discounts/

Pricing elements


PricingPricing Discounts/Discounts/surchargessurcharges

Customer Material Price group Material pricing group Customer/material

pricing group Customer/material Price group/material

pricing group Other

Price List Material Price Customer-specific Other

FreightFreight

Incoterms,part 1

Incoterms,parts 1+2

Other

Departurecountry/dest. cnty.

Domestic Export Other

TaxesTaxes


scale base types 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

SD Pricing Objects: Condition Table (1/2)

Defines key fields that can be used for creating dependent condition records

You can add your own condition tables using table numbers 501 through 999

The key fields must appear at the beginning of the table, i.e. non-key fields must not appear between any two key fields!

In SD key fields sales org and distr. Channel are mostly mandatory


In SD key fields sales org and distr. Channel are mostly mandatory

SD Pricing Objects: Condition Table (2/2)

Create price (PR00): X

IMGIMGIMG

...

...

...

Cond . tables004 Material :Customer / material.....

Sales organizationDistrChannelMaterial

Key Line


Sales organizationDistribution channel

Material Text Calc . type Amount ...M1

100010

Create price (PR00): X

Material

SD Pricing Objects: Access Sequence (1/2)

An access is defined by one condition table.

An access sequence contains

the hierarchy for condition record accesses

all keys that can be used for creating dependent condition records

An access sequence represents the search strategy with which the


An access sequence represents the search strategy with which the system automatically searches for valid condition records of each condition type (note: automatic determination of condition records only possible with item condition types)

Is assigned to the condition type in customizing (NOT in manual condition types)

SD Pricing Objects: Access Sequence (2/2)

The system searches from the most specific to the more general access (in compliance with the business definition). I.e. using the access sequence, you can control that first a customer-specific price and then a pricelist price is found.


SD Pricing Objects: Pricing Procedure (1/4)

Defines the max. number of condition types taken into account during pricing for a business transaction.

Defines the sequence in which the condition types are to be brought into play

Can contain any number of subtotals

Marks if a condition type is


Marks if a condition type is

Mandatory (= included automatically)

Manual (= which of the included condition types to be entered manually)

Statistical (= only for reporting purposes, w/o impact on the final price)


Requirements define if a condition type is applied or not (see tx: VOFM)

Reference level defines which steps a subtotal includes (if blank it totals all values calculated so far)

Print ID controls issue of condition lines when printing (order confirmations, invoices)


Condition formula calculates with value fields (e.g. rounding)

Alternative formula for condition base value: What is taken as the condition base?

Account key is the link to SD / FI interface (account determination)


Which pricing procedure is valid for a business transaction depends on the following criteria (= procedure determination):

Customer (customer pricing procedure in master data)

sales area

Sales document (document procedure in customizing)


Sales document (document procedure in customizing)


StepStep Condition typeCondition type DescriptionDescription Ref. levelRef. level ManualManual RequirementRequirement

1 PricePR00 2

SD documentSD document Sold-to partySold-to partyPricing procedurePricing procedure

Sales organization, distr . channel, divisionSales organization, distr . channel, division


1234567

PriceGross valueSpec. offer disc.Discount %Discount %Discount valueNet value

PR00

KA00RA01RA00

2

3-5X

2

222

89

10

HA00HD00

Header disc. %FreightNet value 2

X

111213

MWST

SKTO

Output taxCash disc. basisCash discount

Content

Introduction

SD Pricing Objects








Subset OSS Notes

Exercise I

Overview of the Relevant Master Data / Org. Structure System Demonstration

Sales Organisation Structure

Sales Org = BP01 Distr. channel = 02 Division = 01

Customer Master data

C-7003 Frstenhofklinik Bad Pyrmont

Material Master

PH-6501MM SAPyrin (20 tablets)


PH-6501MM SAPyrin (20 tablets)

Item category

YTAN Standard item

Sales order: 181

Pricing procedure YVAA01

Content

Introduction

SD Pricing Objects








Subset OSS Notes

Exercise I

Practical Approach / Customizing and ApplicationCondition Type PR00 (Price)

Customizing

Tx: SPRO / Sales and Distribution / Basic functions / Pricing / Pricing Control- Define Condition types- Define Access Sequences

Application

Menu path: Logistics / Sales and Distribution / Master Data / Conditions / Select Using condition Type

Tx: VK 13


Note: 3 tables 4 accesses!

Practical Approach / Customizing and Application Condition Type MWST (Output Tax)

Application

Tx: VA03 / item data / conditions / Analysis

Customizing

Tx: SPRO / Sales and Distribution / Basic functions / Pricing / Pricing Control- Define Condition types- Define Access Sequences


Country Tx: VD03 / General Data / Address

Tax classification customerTx: VD03 / Sales area data / Billing

documents

Tax classification materialTx: MM03View: Sales / sales org. 1

Practical approach / Customizing and Application Condition Type VPRS (Internal price): Customizing

Tx: SPRO / Sales and Distribution / Basic functions / Pricing / Pricing Control/ Define Condition types

Tx: SPRO / Sales and Distribution / Basic functions / Pricing / Pricing Control/ Define and Assign Pricing proc. / Maintain pric. proc.


Tx: SPRO / Sales and Distribution / Sales/ Sales document / Sales document item / Define item cat.

Practical approach / Customizing and ApplicationCondition Type VPRS (Internal price): Application



Tx: MM03 / Accounting 1 or Costing 2

Practical approach / Customizing and ApplicationCondition Type SKTO (Cash Discount)



Tx: VA03 / Header data / Sales

Tx: SPRO / Financial Accounting / .??

Tx: SE11Table T052

Practical approach / Customizing and ApplicationPricing Procedure Determination

Customizing

Tx: SPRO / Sales and Distribution / Basic Functions / Pricing / Pricing Control / Define And Assign Pricing Procedures / Define Pricing Procedure Determination


Content

Introduction

SD Pricing Objects








Subset OSS Notes

Exercise I

When customizing pricing procedures you also need to take the following points into account:

Pricing for a document item depends on its item category. Pricing is not activated, e.g., for free of charge items.

Check how the copying of pricing data is controlled in the SD documents (document flow).

Practical Approach / Special Customizing SettingsNew Pricing Pricing Types (1/3)


documents (document flow).

The pricing type controls how the system carries out pricing:

In the sales document there are two ways for new pricing:

For whole sales doc. (pric. type of pricing procedure)

On header/ item level you can select pricing type

In customizing via copy control on item level


Customizing

Tx: SPRO / Sales and Distribution / Billing/ Maintain Copying Control For Billing Documents


Description :pls. see F1 Help


Application

Tx: VA02 Change Standard Order


or

Tx: VA02 Change Standard Order Edit New Pricing document

Practical Approach / Special Customizing SettingsHow to Expand the Field Catalog for Pricing (1/2)

Order Pricing Configuration

All fields which are to be used for creating a condition table must be contained in the respective field catalog.

It is possible to add additional fields to this catalog


Field catalog....

...

....

Order

abcd

2. Access2. Access

3. Condition3. Condition

4. Pricing4. Pricing

.

.

.

.

.

.

Pricing Configuration

sequence

type

procedure

1. Table1. Table

Practical Approach / Special Customizing SettingsHow to Expand the Field Catalog for Pricing (2/2)

Customizing

Tx: SPRO / Sales and Distribution / System Modifications / Create New Fields (Using Condition Technique)/ New Fields For Pricing

Pls. see: IMG documentation

Relevant condition structures:

KOMK (pricing on header level)


KOMP (pricing on item level)

KOMG (all fields permitted for condition structures)

Steps:

Create new ZZ* data field

Take up ZZ* field in the include

Fill via UserExit

Expand field catalog

Practical Approach / Day to Day Application How to Find Pricing Data of a Spec. Document? (1/3)

Usual sales document data are stored in database tables VBAK, VBAP, VBUP, etc.

Information on pricing data is stored in separate tables

Specific document pricing data is accessible via a key

Table: VBAK

Key field: VBAK-KNUMV No. of the document condition


Table: KONV Conditions (transaction data)

Item wise pricing data, values on all determined items

Key field: KONV-KNUMH condition record number

Table: KONP Conditions (Item)

Values of condition records (entered with tx: VK13


Application

Menu path: Tools/ ABAP Workbench/ Development/ ABAP Dictionary (Tx: SE11)Menu path: Tools/ ABAP Workbench/ Overview/ Data Browser (Tx: SE16)

Tables: VBAK, KONV, KONP

VBAK


KONV

KONP


Application

Tx: VA03 Display order/ Item conditions/ Analysis

Customizing

Tx: SPRO / Sales and Distribution / Basic functions / Pricing / Pricing Control/ Define Access Sequences


Tx: SE11 or SE16

KONP

Content

Introduction

SD Pricing Objects








Subset OSS Notes

Exercise I

Subset OSS Notes

17217 - No access sequence for header conditions

25144 Freight conditions on billing

381348 Using User Exits and VOFM in SD

388112 Change of pricing procedures in the productive system

62536 Info: Conditions in Profitability Analysis


62536 Info: Conditions in Profitability Analysis

Introduction

SD Pricing Objects




Content





Subset OSS Notes

Exercise I

Exercise I

Exercise A: create a sold-to party with reference to customercustomer C-7002 via TC XD01 account group 0001 sold-to party customer C-7002XX (XX=initials) company code BP01 sales area BP01/02/01 reference customer C-7002 reference company code BP01 reference sales area BP01/02/01


reference sales area BP01/02/01 address data name + address of your home town pharmacy sales area data tax classification + (additional partner function CR)

Exercise B: create a price for customer C-7002XX via TC VK11 condition type PR00 key combination customer/material sales organization BP01 Distribution channel 02 customer C-7002XX (XX=initials) material PH-6501MM

Exercise I

Exercise C: create a discount for customer C-7002XX via TC VK11 condition type K007 key combination customer sales organization BP01 Distribution channel 02 customer C-7002XX (XX=initials)


SCM Academy SD02 Condition Technique

Documents

Transcript of SCM Academy SD02 Condition Technique