Tscm62 en Col92 Fv Part a4

(1)

TSCM62

Order Fulfillment II

SAP ERP - Sales and Services

Date Training Center Instructors Education Website

Participant Handbook

Course Version: 92

Course Duration: 10 Days Material Number: 50094949

(2)

Copyright

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Trademarks

• Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation.

• IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. • ORACLE® is a registered trademark of ORACLE Corporation.

• INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated.

• UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. • Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®,

VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

• HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

• JAVA® is a registered trademark of Sun Microsystems, Inc.

• JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

• SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING

WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,

(3)

About This Handbook

This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions

American English is the standard used in this handbook. The following typographic conventions are also used.

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options.

Also used for cross-references to other documentation both internal and external.

Example text Emphasized words or phrases in body text, titles of graphics, and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program.

Example text Exact user entry. These are words and characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

(4)

About This Handbook TSCM62

Icons in Body Text

The following icons are used in this handbook.

Icon Meaning

For more information, tips, or background

Note or further explanation of previous point Exception or caution

Procedures

Indicates that the item is displayed in the instructor's presentation.

(5)

Management” Data Model and Optional Exercise ... 517 Appendix 2: Exercise Data ... 525 Appendix 3: Important SAP Notes about Pricing ... 527 Appendix 4: Additional Technical Information for Section 2 “Billing” ... 529 Appendix 5: Basic Accounting Principles ... 537 Appendix 6: Interface Between Sales and Distribution and Profitability Analysis (CO-PA) ... 543 Index ... 551

(8)

(9)

Course Overview

This course first provides an overview of the system configuration for pricing in sales order management.

In addition, this training course deals with the procedure and configuration of processes in billing. The unit begins with the basic principles of billing, such as the control settings, the data flow for billing, and how to create different types of billing documents and settlements. The next unit covers special business transactions, such as billing plans and down payment processing. It concludes with an in-depth discussion of the features in the interfaces for financial accounting. This course then covers complex Customizing settings that have a cross-functional use in the sales process. You will be introduced to copying control, text control, output determination, and adjustment of the system interface.

You will consolidate and develop your knowledge of the SAP system by working through an integrated case study.

Target Audience

This course is intended for the following audiences:

• Solution consultants who are responsible for implementing order fulfillment with SAP ERP.

Course Prerequisites

Required Knowledge

• Participation in the course TSCM60 or SCM600 Processes in Sales and Distribution, SCM605 Sales, and SCM610 Delivery Processes.

• Completion of the following e-learning course: – SM001 Introduction to SAP Solution Manager

(10)

Course Overview TSCM62

Course Goals

This course will prepare you to:

• Define the necessary system settings for pricing in sales order management • Use the billing function in SAP Sales and Distribution

• Configure the system to meet your company-specific billing requirements • Explain the role of the interface between billing in Sales and Distribution

and accounts receivable in Financial Accounting

• Make settings, which require knowledge of cross-application Customizing functions, to map Sales and Distribution (SD) requirements in the SAP system

Course Objectives

After completing this course, you will be able to:

• Describe the elements of the pricing condition technique and the relationships between them

• Convert your pricing requirements to the necessary pricing strategy

• Make the necessary Customizing settings to implement your pricing strategy • Describe how billing is integrated within the Sales and Distribution process

chain and how data is transferred to Financial Accounting

• Carry out the Customizing configurations for your company-specific billing requirements

• Make cross-functional Customizing settings for the copying control, text control, output control and adapting the user interface functions

(11)

Unit 1

Condition Technique in Pricing

Unit Overview

This unit is an overview of pricing and introduces the condition technique.

Unit Objectives

After completing this unit, you will be able to: • Explain how to use conditions in pricing • Demonstrate how to use condition records • Locate condition types in Customizing

• Explain the meaning of pricing procedures for pricing • Describe pricing procedures and access sequences • Describe the special features of header conditions • Control new pricing using the pricing type

Unit Contents

Lesson: Basics of Pricing ...2

Exercise 1: Condition Records ...7

Exercise 2: Condition Type Configuration... 15

Lesson: Introduction to Condition Technique... 18

Exercise 3: Condition technique terms ... 27

Exercise 4: Adding and Changing Conditions ... 29

Exercise 5: Conditions in the Document Header... 31

Exercise 6: New Pricing and Pricing Types ... 35

(12)

Unit 1: Condition Technique in Pricing TSCM62

Lesson: Basics of Pricing

Lesson Overview

This lesson describes the conditions used in pricing. It also explains how to use the condition records and locate the condition types in Customizing.

Lesson Objectives

After completing this lesson, you will be able to: • Explain how to use conditions in pricing • Demonstrate how to use condition records • Locate condition types in Customizing

Business Example

Your company produces consumer products. The project team that implements the SAP system must meet the company's pricing requirements. As a member of the project team, you have to learn about the pricing configuration options to develop solutions for your company requirements in the pricing area. In pricing, conditions such as prices, discounts, surcharges, freight, and taxes, must be determined automatically for business transactions.

Condition Master Data

Master data for conditions is stored in condition records.

The levels at which pricing is most commonly carried out have been predefined and shipped in the standard version.

(13)

TSCM62 Lesson: Basics of Pricing

Figure 1: Examples of Important Condition Groups

Generally, however, conditions can be defined at any key level. Therefore, you can add additional key levels if required. A standard field catalog containing the fields commonly used in pricing is provided within Customizing for this purpose. You can add any other fields to the field catalog release-independently.

Structure of Condition Records

Condition records are always defined for a key combination that is assigned to the respective condition type. We will learn about these key combinations later, as a condition table, when we discuss configuration. A condition type can also be assigned several possible key combinations, for example, in the standard condition type PR00, “Price”.

(14)

Figure 2: Structure of Condition Records

In addition, you can specify a validity period to limit a pricing agreement to a specific period as shown:

Example:

• Different price lists for different years

• Discounts given only for the duration of a special offer

The values in a condition record, such as price, surcharge, and discount, can be defined according to a scale. There is no limit to the number of scale levels. You can specify an upper and lower limit for each condition record. Manual changes to pricing elements determined by the system can be made only within these limits.

(15)

Condition Types: Examples

Figure 3: Condition Types

The condition type determines the category of a condition and describes how the condition is used.

The calculation type and the scale base type can be controlled for each condition type.

Possible scale bases Possible calculation types Values Percentage of an initial value

Fixed amount

Quantity Amount by unit of measure

Weight Amount per unit of weight

Volume Amount per unit of volume

Period Quantity per unit of time

(16)

Condition Maintenance

Figure 4: Condition Maintenance

An additional maintenance interface is provided for condition maintenance in SAP R/3 Release 4.6A and later.

The new interface allows mass maintenance of conditions based on characteristics, for example, for customers.

This means that condition records can now be maintained across all condition types and condition tables. You can, for example, display and maintain the material prices and the discounts and surcharges for a customer in one step. You can also call up the previous maintenance transaction for conditions by choosing Select Using Condition Type.

(17)

Exercise 1: Condition Records

Exercise Objectives

After completing this exercise, you will be able to: • Check pricing data and understand system messages • Create and use condition records with and without scales

Business Example

You will be testing the basic pricing concepts dealing with the creation and use of condition records. In addition, you need to gain familiarity with the pricing data shown in the order.

Task 1:

You need to create a simple order to determine what happens when pricing information is missing from the system.

1. From the customer purchase order shown below, create a standard sales order: TELEFAX

Customer: T-L67A##

PO number: ##-1-1

Requested delivery date: In one week

Material T-AT1##

Quantity 10

2. Why does this cause an error message? 3. What needs to be done to correct the error? 4. Exit without saving the order.

Continued on next page

(18)

Task 2:

To supply the missing pricing information, you need to create a price condition record, test the record by entering the same order as before, and check the pricing information in the order.

1. Create a material price condition record (PR00) for material T-AT1## for your sales organization 1000 and distribution channel 10. The price is 280 EUR. Use the default validity period.

Hint: In this introductory unit, use the maintenance transaction that is called through the Select using condition type node.

2. Save the condition record.

PO number: ##-1-2

Material: T-AT1##

Quantity: 10

4. Display the pricing conditions for the order item and record the gross price determined automatically during pricing.

5. Can you save the order now?

Task 3:

Occasionally, your company gives special prices and discounts to particular customers. You need to create condition records, which include the scale values for your customers. Then, you need to test these new records by creating the orders and viewing the results.

(19)

from 1 piece 250 EUR

10 pieces 240 EUR

100 pieces 230 EUR

3. Create a customer-specific discount condition record (K007) with scale values for customer T-L67A## for your sales area (1000/10/00). Use the default validity period.

Use the following scale values for the condition record:

from 100 EUR 2 %

1000 EUR 3 %

5000 EUR 5 %

PO number: ##-1-3

Quantity 10

6. Display the pricing condition for the order item and note all the conditions determined automatically during pricing.

7. Save the order and record the document number.

(20)

Solution 1: Condition Records

Task 1:

You need to create a simple order to determine what happens when pricing information is missing from the system.

PO number: ##-1-1

Quantity 10

a) To create a standard order, select

Logistics → Sales and Distribution → Sales → Order → Create.

Order Type: OR

2. Why does this cause an error message?

a) The system displays an error message because the mandatory pricing condition record PR00 is missing for the material.

3. What needs to be done to correct the error?

a) To correct the error, you need to create a material price condition record for the material.

4. Exit without saving the order. a)

(21)

Task 2:

To supply the missing pricing information, you need to create a price condition record, test the record by entering the same order as before, and check the pricing information in the order.

1. Create a material price condition record (PR00) for material T-AT1## for your sales organization 1000 and distribution channel 10. The price is 280 EUR. Use the default validity period.

Hint: In this introductory unit, use the maintenance transaction that is called through the Select using condition type node.

a) To create a material price, select:

Logistics → Sales and Distribution → Master Data → Conditions → Select Using Condition Type → Create.

Choose condition type PR00.

Choose the key combination Material with release status. 2. Save the condition record.

a) Choose Save

PO number: ##-1-2

Material: T-AT1##

Quantity: 10

a) To create a standard order, select:

4. Display the pricing conditions for the order item and record the gross price determined automatically during pricing.

a) Select the item and choose Item conditions. Pricing automatically determined the material price PR00 as EUR 280 per piece. 5. Can you save the order now?

a) Yes, you can now save the order.

(22)

Task 3:

Occasionally, your company gives special prices and discounts to particular customers. You need to create condition records, which include the scale values for your customers. Then, you need to test these new records by creating the orders and viewing the results.

1. Create a customer-specific price condition record (PR00) for material T-AT1## and customer T-L67A## for your sales organization 1000 and distribution channel 10. Use the default validity period.

Use the following scale values for the condition record:

from 1 piece 250 EUR

10 pieces 240 EUR

100 pieces 230 EUR

a) To create customer-specific price condition records, select:

Choose condition type PR00.

Choose the key combination Customer/material with release status. To enter the scale values, select the condition line and choose Scales. 2. Save the condition record.

a) Choose Save

3. Create a customer-specific discount condition record (K007) with scale values for customer T-L67A## for your sales area (1000/10/00). Use the default validity period.

(23)

from 100 EUR 2 %

1000 EUR 3 %

5000 EUR 5 %

a) To create a customer-specific discount condition record (K007), select:

Choose condition type K007.

Choose the key combination Division/Customer.

To enter the scale values, select the condition line and choose Scales. 4. Save the condition record.

a) Choose Save

PO number: ##-1-3

Quantity 10

6. Display the pricing condition for the order item and note all the conditions determined automatically during pricing.

a) Click the Item Overview button. Select the item and choose Item conditions. Pricing automatically determined the material price PR00 as EUR 240 per piece and the customer discount (K007) as 3%. 7. Save the order and record the document number.

a) a) Document number: _____________________

(24)

(25)

Exercise 2: Condition Type Configuration

Exercise Objectives

After completing this exercise, you will be able to:

• Use the IMG to access pricing settings in Customizing • View the Customizing settings for a condition type

Business Example

As a member of the pricing implementation team, you will be using the IMG to view all forms of pricing configuration.

Task:

You must verify that the configuration settings for certain condition types are appropriate.

1. Display the settings for condition type K007 in Customizing. What calculation type and scale base type are assigned to this condition type? 2. What effects do these settings have?

(26)

Solution 2: Condition Type Configuration

Task:

You must verify that the configuration settings for certain condition types are appropriate.

1. Display the settings for condition type K007 in Customizing. What calculation type and scale base type are assigned to this condition type? a) Calculation type: A Percentage

Scale base type: B Value scale

Tools → Customizing → IMG → Execute Project → SAP Reference IMG → Sales and Distribution → Basic Functions → Pricing → Pricing Control → Define Condition Types.

Choose Maintain Condition Types. Select K007 and click the Details button. 2. What effects do these settings have?

a) Effects:

The discount is calculated as a percentage of the item’s value and the discount scale entries are based on the value of the order item, instead of its weight or volume.

(27)

Lesson Summary

You should now be able to:

• Explain how to use conditions in pricing • Demonstrate how to use condition records • Locate condition types in Customizing

(28)

Lesson: Introduction to Condition Technique

Lesson Overview

This lesson first introduces the pricing procedure used in pricing and enables you to understand the task of the access sequence.

It then explains several aspects of handling conditions, for example, in the document header, and describes the significance of pricing types.

This lesson prepares you for the next unit, on configuring pricing.

Lesson Objectives

After completing this lesson, you will be able to:

Business Example

Your company produces consumer products. The project team that implements the SAP system must meet the company's pricing requirements. As a member of the project team, you have been given the task of examining the pricing configuration options, to provide solutions for your company requirements. Since requirements differ from one company to another, pricing must be configurable.

Introducing the Pricing Procedure

All condition types permitted for a transaction in pricing are contained in the pricing procedure. The pricing procedure is determined in Customizing according to:

(29)

TSCM62 Lesson: Introduction to Condition Technique

Figure 5: Pricing Procedure - Examples of Control Fields

Customizing for pricing procedures contains a variety of attributes that can influence processing of the individual condition types.

• The level in the pricing procedure determines the sequence in which the conditions are processed and placed in the sales document (where applicable). • The pricing procedure can contain any number of subtotals. To define

subtotals, leave “Condition Type” field blank and enter a name for the subtotal in the “Description” field.

• The reference level lets you define an alternative base for calculating the condition value (the default base is the current value resulting from processing the previous condition types) and for consolidating conditions for subtotals.

• You can also specify requirements to determine how the system is to use the individual condition types.

• You can mark a condition type in the pricing procedure as being: – A mandatory condition

– A condition that can only be entered manually (any existing access sequence is ignored in this case)

– A condition used for statistical purposes only

There are also several technical attributes, such as calculation formula, base formula, and print indicator, which we will learn about later in the course.

(30)

Task of the Access Sequence

An access sequence is a search strategy that the system uses to find valid condition records for a condition type. This search strategy defines the sequence in which the system reads the condition records for a condition type.

Figure 6: Access Sequence

An access sequence can be assigned to a condition type (except for condition types configured as a header condition).

Every access in an access sequence is defined using a condition table.A condition table is a combination of fields that form the key for a condition record.

If an access sequence contains more than one access, they are usually arranged from specific to general in descending order.

An access can also be made contingent on requirements in the access sequence.

(31)

Figure 8: Pricing Overview (2)

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 then determines the access sequences assigned to 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.

(32)

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.

(33)

The whole process is repeated for each condition type until the system has finished the entire pricing procedure.

Several Aspects of Using Conditions

Before we examine pricing configuration in the next unit, we will prepare first by examining a few selected aspects of using conditions.

Changing Prices Manually

Figure 13: Changing Prices Manually in Documents

The prices, surcharges, and discounts determined automatically by the system can be changed manually and are then marked as such.

In the condition records, you can specify limits within which a manual change can be made, for example, defining a discount that can only be changed between the range 1% and 3%.

In addition to determining conditions automatically, conditions can be entered manually in the sales document. Conditions are marked as having been entered manually.

You can change or create conditions on the condition screen.

You can prevent one condition type from being changed manually by making the appropriate settings in Customizing.

(34)

Maintaining Header Conditions

Figure 14: Conditions in the Document Header

Conditions can also be entered at the document header level. These are known as header conditions and are valid for all items.

These header conditions are automatically distributed among the items based on net value. The basis for distributing the header conditions can be changed in the pricing procedure by selecting the appropriate routine, for example, weight and volume, in the Alternative formula for Condition Base Value (AltCBV) field.

(35)

Figure 16: Creating Conditions in the Document Header (2)

In the second example, the header condition amount is distributed among the items based on its portion of the total net value.

New Pricing and Pricing Types

Figure 17: New Pricing and Pricing Types

You can configure the pricing behavior in the Pricing type.

(36)

You have two options to control the New pricing function in the sales document: • Update prices on the condition screens is available at the header and item

levels. You can choose the pricing type in the dialog box that appears. • To use the new pricing document function for the sales document (→ Edit

→ New Pricing Document), assign a pricing type to the pricing procedure in Customizing. If you do not maintain an entry, the system uses pricing type B (Carry out new pricing).

These functions are supported for both the sales and billing documents.

Figure 18: Pricing in the Billing Document

Copying control makes it possible to handle repricing of billing documents based on several different scenarios. While all customers will not use every pricing type, the ability to specify what will happen to pricing calculations during billing is a decision each customer must make.

(37)

Exercise 3: Condition technique terms

Exercise Objectives

• Differentiate the use of some important condition technique terms

Business Example

As a member of the project team, you have been given the task of examining the pricing configuration options.

Task:

Before viewing several configuration tables in this unit, review the use of these condition technique terms.

1. In pricing, what object stores the condition types and the sequence in which they are executed in the sales document during pricing?

2. What criteria influence pricing procedure determination during pricing? 3. What pricing element is used to control pricing so that you can specify that

a customer-specific price rather than a material price is to be used during automatic pricing?

(38)

Solution 3: Condition technique terms

Task:

Before viewing several configuration tables in this unit, review the use of these condition technique terms.

1. In pricing, what object stores the condition types and the sequence in which they are executed in the sales document during pricing?

a) The pricing procedure.

2. What criteria influence pricing procedure determination during pricing? a) The following criteria influence how pricing procedures are determined:

• The sales area, which includes the sales organization, distribution channel, and division

• The document pricing procedure code in the document type • The customer pricing procedure code in the customer master

record

3. What pricing element is used to control pricing so that you can specify that a customer-specific price rather than a material price is to be used during automatic pricing?

a) The access sequence determines the sequence in which the condition records for a condition type are found and read.

(39)

Exercise 4: Adding and Changing

Conditions

Exercise Objectives

• Explain how the system records new order conditions • Change existing order conditions

Business Example

Your company manufactures consumer goods. The project team that implements the SAP R/3 Enterprise Sales and Distribution (SD) module must meet the company's pricing requirements. As a member of the project team, you have been given the task of examining the pricing configuration options to provide solutions for your company's pricing requirements. To meet these requirements, the condition technique combines certain elements, which also perform various tasks.

Task:

Occasionally, order entry personnel need to manually adjust the pricing on an order. You can add additional conditions manually and change automatic conditions at the item level of the order.

Customer: T-L67A## PO number: ##-2-3

Requested delivery date: In one week Material Quantity

T-AT1## 10

2. Go to the condition screen for the item and manually add a quantity discount of EUR 10- per piece. Use condition type RC00.

3. In the order, change the K007 customer discount manually to a rate of 4% discount.

4. View the item condition detail screen for K007. How can you determine whether or not the condition has been edited manually?

(40)

Solution 4: Adding and Changing

Conditions

Task:

Occasionally, order entry personnel need to manually adjust the pricing on an order. You can add additional conditions manually and change automatic conditions at the item level of the order.

T-AT1## 10

2. Go to the condition screen for the item and manually add a quantity discount of EUR 10- per piece. Use condition type RC00.

a) Click the Item overview tab.

Select the line item and click the Item conditions button. Click the Insert Row button.

After entering the values, activate the condition by clicking the Enter button.

3. In the order, change the K007 customer discount manually to a rate of 4% discount.

a) To determine manually changed values:

(41)

Exercise 5: Conditions in the Document

Header

Exercise Objectives

• Enter header level conditions and see their effect on the line items of an order

Business Example

When pricing conditions apply to all the items of an order, these conditions can be entered in the header of the order. You need to test how header conditions are entered and how they are distributed among the line items of a sales document.

Task:

Header level pricing conditions apply to all the items in the order. You can create header discounts and view their effect at the item level of the order.

T-AT1## 10 T-AT2## 10

2. Go to the header condition screen of the order and create two discounts manually. The first discount is condition type HB00 with a rate of 100-. The second discount is condition type RB00 with a rate of 100-.

3. Activate the header pricing. Record the results at the item level. 4. Save the order and record the document number.

(42)

Solution 5: Conditions in the Document

Header

Task:

Header level pricing conditions apply to all the items in the order. You can create header discounts and view their effect at the item level of the order.

T-AT1## 10 T-AT2## 10

2. Go to the header condition screen of the order and create two discounts manually. The first discount is condition type HB00 with a rate of 100-. The second discount is condition type RB00 with a rate of 100-.

a) Click the Display document header details button at the top right of the screen.

Select the Conditions tab. Click the Insert Row button.

Enter the condition types and their rates.

3. Activate the header pricing. Record the results at the item level.

(43)

4. Save the order and record the document number. a) Document number: _____________________

(44)

(45)

Exercise 6: New Pricing and Pricing Types

Exercise Objectives

• Check the copy control tables to locate the pricing type field and examine its effect on pricing during billing

Business Example

In your business environment, prices for many materials change frequently. You will need to verify how you can adjust the pricing during billing to meet various requirements.

Task:

When prices or discounts change from the time the order is taken to the time the invoice is created, you require the system to handle the changes automatically in an appropriate way. You will test the effect of pricing types on pricing and view the related tables in Customizing to learn where this function is controlled. 1. From the customer purchase order shown below, create a standard sales order.

TELEFAX

T-AT1## 10

2. Enter a manual discount at item level using condition type RC00 for a rate of 100-.

4. Create an outbound delivery for this order, pick the entire quantity, and then post goods issue. Note the document number. Use shipping point 1200 and a selection date of 10 days from today. When creating the transfer order for picking, choose warehouse number 012.

5. Create an invoice for this outbound delivery, but DO NOT SAVE IT. What billing type is used by default?

6. Examine the pricing details in the invoice and determine what conditions were used to arrive at the net price. Note the net price.

(46)

7. You will implement new pricing for the item using pricing type B.

Hint: You can choose entries for your personal list of values from the variety of pricing types proposed in the dialog box.

This allows the selection screen to be structured more clearly. 8. Examine the pricing details again and note the difference in the condition

types that are used now. What is the effect on the net price of the invoice? What caused this to happen? Save the invoice and record the document number.

9. In the IMG, view the Pricing type field in the copying control table for billing types F1 and F2. View the entries for these billing documents when they are created with reference to an LF delivery document and an item category of TAN. Record your answers.

(47)

Solution 6: New Pricing and Pricing Types

Task:

When prices or discounts change from the time the order is taken to the time the invoice is created, you require the system to handle the changes automatically in an appropriate way. You will test the effect of pricing types on pricing and view the related tables in Customizing to learn where this function is controlled. 1. From the customer purchase order shown below, create a standard sales order.

TELEFAX

T-AT1## 10 a)

2. Enter a manual discount at item level using condition type RC00 for a rate of 100-.

a) Select the line item and click the Item conditions button. Click the Insert Row button.

Enter the condition type and rate.

3. Save the order and record the document number. a) Document number: ___________________

(48)

4. Create an outbound delivery for this order, pick the entire quantity, and then post goods issue. Note the document number. Use shipping point 1200 and a selection date of 10 days from today. When creating the transfer order for picking, choose warehouse number 012.

a) Creating an outbound delivery, a transfer order to do the picking, and then posting goods issue.

Logistics → Sales and Distribution → Shipping and Transportation → Outbound Delivery → Create → Single Document → With Reference to Sales Order.

Enter the Shipping point: 1200

Enter the Selection date: Today's date + 10 days. Choose Enter.

To pick the required quantity from directly within the delivery, choose:

Subsequent functions → Create transfer order.

Verify that the warehouse number is 012.

In the Adopt Pick Quantity field, choose function 2 (copy the picking quantity to the delivery and post goods issue).

Save the transfer order.

5. Create an invoice for this outbound delivery, but DO NOT SAVE IT. What billing type is used by default?

a) Creating a billing document:

Logistics → Sales and Distribution → Billing → Billing Document → Create.

If necessary, enter your delivery document number. Click the Execute button.

An F2 invoice document is created. You can see the document type in the title bar.

6. Examine the pricing details in the invoice and determine what conditions were used to arrive at the net price. Note the net price.

(49)

7. You will implement new pricing for the item using pricing type B.

Hint: You can choose entries for your personal list of values from the variety of pricing types proposed in the dialog box.

This allows the selection screen to be structured more clearly. a) Select the line item and click the Item Pricing Condtn button.

Click the Update prices button at the bottom of the screen. Choose pricing type B (carry out new pricing).

8. Examine the pricing details again and note the difference in the condition types that are used now. What is the effect on the net price of the invoice? What caused this to happen? Save the invoice and record the document number.

a) Select the line item and click the Item Pricing Condtn button. Only condition types PR00 and K007 are used to calculate the net price. The RC00 discount entered manually is not used because pricing type B discards manual discounts when recalculating pricing.

9. In the IMG, view the Pricing type field in the copying control table for billing types F1 and F2. View the entries for these billing documents when they are created with reference to an LF delivery document and an item category of TAN. Record your answers.

a) Checking the copying control:

Tools → Customizing → IMG → Execute Project → SAP Reference IMG → Sales and Distribution → Billing → Billing Documents → Maintain Copying Control For Billing Documents → Copying control: Delivery document to billing document.

Select the line with F1 as Tgt and LF as Source and double click the Item node in the Dialog Structure.

Select item category TAN and click the Details button.

Pricing type C (copy manual pricing elements and redetermine those remaining) is used.

Repeat the process for F2 as Tgt and LF as Source with item category TAN. Pricing type G (copy pricing elements unchanged and redetermine taxes) is used.

(50)

Lesson Summary

(51)

TSCM62 Unit Summary

Unit Summary

• Explain how to use conditions in pricing • Demonstrate how to use condition records • Locate condition types in Customizing

(52)

(53)

TSCM62 Test Your Knowledge

Test Your Knowledge

1. You can limit a pricing agreement to a certain period by specifying a .

Fill in the blanks to complete the sentence.

2. With the additional maintenance interface since SAP R/3 Release 4.6A, condition records can be maintained across all condition types and condition tables.

Determine whether this statement is true or false.

□ True □ False

3. You can mark a condition type in the pricing procedure as being:

Choose the correct answer(s).

□ A A mandatory condition □ B A manually entered condition □ C For statistical purposes only □ D An automatically entered condition

4. A condition table is a combination of fields, which form the key for a .

Fill in the blanks to complete the sentence.

5. The header conditions are distributed manually among the items based on the net value.

Determine whether this statement is true or false.

□ True □ False

(54)

Test Your Knowledge TSCM62

Answers

1. You can limit a pricing agreement to a certain period by specifying a validity period.

Answer: validity period

2. With the additional maintenance interface since SAP R/3 Release 4.6A, condition records can be maintained across all condition types and condition tables.

Answer: True

With the additional maintenance interface since SAP R/3 Release 4.6A, condition records can be maintained across all condition types and condition tables.

3. You can mark a condition type in the pricing procedure as being: Answer: A, B, C

You can mark a condition in the pricing procedure as being a mandatory condition, a manually entered condition, and for statistical purposes only. 4. A condition table is a combination of fields, which form the key for a

condition record.

Answer: condition record

5. The header conditions are distributed manually among the items based on the net value.

Answer: False

The header conditions are automatically distributed among the items based on the net value.

(55)

(56)

(57)

Unit 2

Pricing Configuration

Unit Overview

This unit discusses how to change and add to the different pricing elements and implement customizing settings for pricing.

Unit Objectives

After completing this unit, you will be able to:

• Create or supplement the different pricing elements • Explain pricing configuration

• Implement Customizing settings for pricing

Unit Contents

Lesson: Overview of Pricing Configuration ... 46 Lesson: Customizing Pricing Components ... 54 Exercise 7: Pricing Procedure Determination ... 57 Exercise 8: Controls in Pricing Elements... 61 Exercise 9: Comprehensive Pricing Exercise ... 65

(58)

Unit 2: Pricing Configuration TSCM62

Lesson: Overview of Pricing Configuration

Lesson Overview

This lesson enables you to create and add to the different pricing elements. You will learn how to configure pricing by creating all the basic elements needed to implement a new pricing requirement and then putting them together to form a solution.

Lesson Objectives

After completing this lesson, you will be able to:

Business Example

Your company produces consumer products. The project team that implements the SAP system must meet the company's pricing requirements. As a member of the project team, you have been given the task of examining the pricing configuration options to provide solutions for your company's pricing requirements. In pricing, price discounts, surcharges, freights, and taxes must be determined automatically for business transactions. You must also be able to alter these conditions manually.

Sequence of Configuration Steps

You carry out the configuration of pricing in the reverse order of the pricing process in the application in the sales document described in the previous unit. Therefore, when you create a new pricing procedure, you have to be aware of the ultimate objective - the condition record to be found later - from the start, to determine the necessary key components. This means the first step involves creating a new condition table if the required key combination (= condition table) is not already available in the standard system.

(59)

TSCM62 Lesson: Overview of Pricing Configuration

A condition table defines the structure of the key that can be used to create dependent condition records.

To create your own condition tables, use the customer namespace from 501 to 999.

Figure 20: Condition Tables

Condition records are always created using a specific key.

You use condition tables to define the structure of the keys for a condition record. The most important fields used in pricing at the header and item levels are available in the standard system.

(In SAP R/3 Release 4.5 and later, you can also add non-key fields to the condition tables for special purposes. This is explained in condition table 144, for example, which is used in the price book (condition type PBUD).)

The key fields of a condition table must appear at the start of the table.

In the condition table you can determine whether a field appears in the header or in the item part of the generated fast entry screen for the maintenance of condition records.

(60)

Access Sequences

Figure 21: Overview: Pricing Configuration (2)

An access sequence consists of one or more condition tables.

Figure 22: Creating an Access Sequence

You can define prices, discounts, and surcharges at various levels. Each level is defined by a condition table.

The hierarchy of the different levels is determined by the sequence of entries in an access sequence.

(61)

Special Case: Assigning Alternative Source Fields

Figure 23: Determining Source Fields for Access Sequences

Within each access of an access sequence, you can specify the document field or source field with which an access is performed.

Examples:

• Material or pricing material?

• Document currency or local currency? • Sold-to party or ship-to party?

The access sequence of standard condition type PR00, “Price”, has a third access that is only carried out when restriction 3, “Document in Foreign Currency” (that is, “document currency is not local currency”) is fulfilled. This third access involves a repeat access of the price list condition records with a different “local currency” source field.

(62)

Figure 24: Restrictions in Access Sequences

You can use restriction-dependent accesses to avoid unnecessary accesses and reduce the system load.

Condition Types

(63)

Pricing Procedures

The condition types are combined in the required sequence in the pricing procedure.

Figure 27: Impact of the Counter Field in a Pricing Procedure

(64)

Procedure Determination

You now have to maintain determination of the pricing procedure, which is determined based on the following factors:

• The sales area

• The Customer Pricing Procedure field in the customer master

• The Document Pricing Procedure field, which is assigned to the sales document type

(65)

Lesson Summary

(66)

Lesson: Customizing Pricing Components

Lesson Overview

This lesson provides an overview of how to implement pricing strategies.

Lesson Objectives

After completing this lesson, you will be able to: • Implement Customizing settings for pricing

Business Example

Your company produces consumer products. The project team that implements the SAP system must meet the company's pricing requirements. As a member of the project team, you have been given the task of examining the pricing configuration options, to provide solutions for your company requirements.

Customizing Pricing Components

As we have seen, the options for Customizing pricing are restricted through the catalog of allowed fields for condition tables. If a particular situation requires an exception to this rule, you can use the release-neutral procedure for adding additional fields to this catalog of allowed fields.

(67)

TSCM62 Lesson: Customizing Pricing Components

The information required to add new pricing fields is available in the IMG documentation. Search for Sales and Distribution → System Modification →

Create New Fields (Using Condition Technique).

• To solve particular problems, you need to build and link all the pricing components creatively. You can characterize the individual elements concisely as follows:

– Condition table – defines key fields of the condition records

– Access sequence – Contains the hierarchy for condition record access – Condition type – Represents the properties of the pricing conditions – Pricing procedure – Defines how the condition types are linked – Procedure determination – Selects the correct pricing procedure Meeting particular pricing requirements may require one or more new pricing components. Understanding the purpose and capabilities of each component and the relationships between pricing components is critical to meet pricing requirements.

• The following elements may be necessary to implement complex scenarios: – Adding new fields for pricing – Creates new fields to meet customer

requirements

– Requirements – Defines dependencies and improves performance – Formulas – Enables expanding the limits of standard configuration New fields may be added to the pricing field catalog. This allows you to use the new field to define any condition tables.

Requirement routines and formulas provide a method for modifying the standard pricing logic to meet unique user requirements.

SAP provides tools to create these pricing elements. These tools are accessed through the IMG.

(68)

(69)

Exercise 7: Pricing Procedure

Determination

Exercise Objectives

• Check all the fields that are used to determine the pricing procedure • Understand the table to determine the pricing procedure in the IMG

Business Example

Your company uses several pricing procedures, depending on the combination of customer, order type, and organizational units. You need to verify whether or not the proper pricing procedure is used in all the cases.

Task:

As a team member of the project, you need to ensure that the correct pricing procedure is being used in all cases. You need to access all the relevant data used in this process and use the IMG to view the pricing procedure determination tables. 1. In the table in exercise 1-1-3, note the value of the Customer pricing

procedure field found in the sales area data of the master record for customer T-L67A##.

2. In the table in exercise 1-1-3, note the value of the Document pricing procedure field for document type OR using the IMG.

3. What pricing procedure does the system determine if you create a standard order for the following values?

Sales organization 1000

DistrChannel 10

Divis. 00

Document pricing procedure Customer pricing procedure Pricing procedure for the order

(70)

Solution 7: Pricing Procedure

Determination

Task:

As a team member of the project, you need to ensure that the correct pricing procedure is being used in all cases. You need to access all the relevant data used in this process and use the IMG to view the pricing procedure determination tables. 1. In the table in exercise 1-1-3, note the value of the Customer pricing

procedure field found in the sales area data of the master record for customer T-L67A##.

a) To find the customer pricing procedure, select:

Logistics → Sales and Distribution → Master Data → Business Partner → Customer → Display → Sales and Distribution.

Enter the customer number and the sales area. Click Continue.

Choose Sales Area Data.

The Customer pricing procedure field is on the Sales tab and has a value of 1.

2. In the table in exercise 1-1-3, note the value of the Document pricing procedure field for document type OR using the IMG.

a) To find the document pricing procedure, select:

SAP Reference IMG → Sales and Distribution → Basic Functions → Pricing → Pricing Control → Define And Assign Pricing Procedures.

Choose the Assign document pricing procedures to order types. Use the Position button to find document type OR.

The document pricing procedure field (DoPr) has a value A.

3. What pricing procedure does the system determine if you create a standard order for the following values?

(71)

Document pricing procedure Customer pricing procedure Pricing procedure for the order a) Pricing procedure determination:

Sales organization 100

DistrChannel 10

Divis. 00

Document pricing procedure A Customer pricing procedure 1

Pricing procedure for the order RVAA01

Choose Define Pricing Procedure Determination.

Click Position and enter the appropriate data using the values in the table above.

Pricing procedure RVAA01 is determined.

(72)

(73)

Exercise 8: Controls in Pricing Elements

Exercise Objectives

• Check the various control fields in each element of the pricing condition technique

Business Example

To meet the pricing demands of your business, you need to identify and use the control fields within each pricing element.

Task:

You can view the various control fields in a pricing procedure, condition type, and an access sequence to learn what control is possible at this level.

1. How can you control whether or not a condition is determined during automatic pricing or whether or not the condition is entered manually? 2. How can you configure a condition type so that it can no longer be edited

manually in the document?

3. How can you configure a condition type during Customizing so that only discount condition records and not those yielding surcharges can be entered? 4. Which access sequence is assigned to condition type PR00?

5. Which condition tables are used by access sequence PR02?

6. What is the difference between the second and third access in the access sequence PR02?

(74)

Solution 8: Controls in Pricing Elements

Task:

You can view the various control fields in a pricing procedure, condition type, and an access sequence to learn what control is possible at this level.

1. How can you control whether or not a condition is determined during automatic pricing or whether or not the condition is entered manually? a) In Customizing, when defining the pricing procedure, you can mark

a condition type as manual only (Man). As a result, the condition is not determined automatically during pricing but can only be entered manually.

Choose Maintain pricing procedures.

Choose the standard pricing procedure RVAA01 and select the Control data node in the Dialog Structure.

2. How can you configure a condition type so that it can no longer be edited manually in the document?

a) During Customizing, you can specify whether or not a condition type can be edited manually in the Changes which can be made fields. If the Manual entries field is set to D, then the condition type cannot be manually edited in the sales document.

SAP Reference IMG → Sales and Distribution → Basic Functions → Pricing → Pricing Control → Define Condition Types.

Choose Maintain Condition Types.

Select the K007 condition type and click the Details button to view the field.

3. How can you configure a condition type during Customizing so that only discount condition records and not those yielding surcharges can be entered?