Using Reports for Condition Records

Objective

After completing this lesson, you will be able to work with pricing reports

Price Lists

A price list is a report that can be used to show or maintain condition records across various characteristics (like material and/or customer).

The standard delivery includes recommended fields for creating price lists (for example, the fields for material and product hierarchy). Additionally, you can use the Customizing for price lists to change the fields in the report. You can add to the selection criteria by including fields using enhancement spot implementations.

  • You enter :
  • the sales area (sales organization, distribution channel, and division).
  • one or more (or a range of) customer numbers for sold-to parties.
  • one or more (or a range of) material numbers, product hierarchies, and material pricing groups.

Control Data:

You enter the pricing date and the sales document type. Note that you must enter a sales document type so that the system can determine a pricing procedure to calculate the price.

Output:

You can have choices for the price list output. You can:

  • Display price lists directly in the system:

    If you have entered a layout, the system uses this layout to determine how the price list is displayed.

  • Upload price lists to an FTP server.

  • E-mail price lists as Microsoft Excel spreadsheets or character separated values (including in the ZIP file format) to sold-to parties.

Pricing Reports

You can configure your own pricing reports: they contain a page header, a group header and items.

You can generate a list of conditions for analysis that provides an overview of the existing condition records.

Some queries based on which you can create pricing reports are as follows:

  • What customer-specific price agreements are made within a certain period?
  • Which Incoterms condition records are stored in the system?
  • Which price lists were created with scale prices?

In Customizing, you determine how the lists must be structured and which condition records must be evaluated.

Pricing Reports – Tables

When configuring a pricing report, you start by selecting the condition tables you need. Next, you assign the table fields to the elements page header, group header and items.

When you create a new program for pricing reports, you first decide the views in which you want to analyze the condition records. To define the views, select specific fields from the existing condition tables.

The system generates a list of tables depending on which fields are selected. Each table contains at least one of the selected fields. From this list of tables, you can select specific tables that will appear in the report.

The list layout is specified by positioning and sorting the fields.

The fields in the selected table appear in one of the following report sections:

  • Page header

    The system provides a page break when a value changes.

  • Group header

    The system generates a new line heading for each table that is analyzed.

  • Items

    The system provides the detailed information on the records.  ​

Condition Records Maintenance by Using Pricing Reports

Note

See the following video to learn about the various options for maintaining condition records:

Note

Condition maintenance via transactions VK31, VK32, VK33 has become less important with the introduction of the SAP Fiori app called Manage Prices - Sales.

Use Pricing Reports

Manage Prices - Sales

With this app, you can flexibly set prices that you offer to your customers by managing all relevant condition records in one place. You can create, edit, copy, or delete multiple condition records simultaneously.

Features of the app Manage Prices - Sales are shown. They are also explained in the text below.

As as pricing specialist you have several options when using the Manage Price - Sales app.

You can search for condition records in the table by specifying filter values as required. The app provides the dynamic filters, which means that the specified condition type and the key combination dynamically determine the relevant key fields and add them as available filters. If you specify more than one condition type in the filter, the key fields relevant for any of the specified condition types are displayed.

You can create condition records directly in the table. First, specify the condition type and the key combination to determine the relevant key fields. The relevant key fields are then displayed as columns in the table dynamically.

You can create condition records by copying the existing ones.

You can edit the validity period and the condition amount of existing condition records simultaneously.

You can create condition records by importing a template-based spreadsheet. Before downloading the template, you must first specify the relevant condition types in the app filter. This helps the system pre-fill the relevant key combinations in the template for you to start with. You can update existing condition records by importing a spreadsheet. To do so, use the app filter to search for the condition records that need updating and export them to a spreadsheet. From there, you can change the fields that are editable and then import the changes back to the app. You can also create new condition records in the same spreadsheet. In the import history, you can view details of your imports.

You can track the status of large imports that are running in the background. You can correct import errors or view imported data by downloading them to a spreadsheet.

Be aware when the validity period of the created or updated condition records overlaps with the validity periods of existing condition records, the existing condition records are updated with the new validity periods or replaced and therefore deleted.

Maintain Description

With this functionality you can simplify the pricing configuration and reduce the number of condition types.

One condition type can be used with different descriptions for various use cases, like a regular customer discount and a VIP discount.

Instead of creating and maintaining new condition types you can simply change the default description of the condition type. You can use the same condition type with different descriptions .

For each condition record for pricing you can define an individual description. This overrules the default from the condition-type definition.

This way you reduce the need for new condition types and simplify the pricing configuration and save costs.

You can maintain the different description with the help of the Manage Prices - Sales app or Set Material Prices – Sales app / transaction VK12.

Maintain Condition Records by using the Manage Prices App

Maintain Condition Description

Log in to track your progress & complete quizzes