Karun Gaur

Table of Contents
Retail Pricing in Depth.............................................................................................. 2
Pricing Worklist ....................................................................................................... 2
Use ............................................................................................................................... 2
Prerequisites.................................................................................................................. 2
Features ........................................................................................................................ 3
Example ........................................................................................................................ 4
Worklist Generation ................................................................................................. 5
Direct Creation of Worklist Entries ............................................................................ 7
Use ............................................................................................................................... 7
Integration .................................................................................................................... 8
Features ........................................................................................................................ 8
Activities ....................................................................................................................... 9
In System: ............................................................................................................. 12

1
 Karun Gaur

Retail Pricing in Depth

Direct work list conversion, this is used if you don’t want to generate worklist manually
using the worklist generation report RMEBEIN4 Tcode: MEI4

<<<<<<<<<<
Some more information from SAP

Pricing Worklist
Use

Sales prices are generally calculated on the basis of the purchase price, which is in turn
calculated using the purchase price calculation schema on the basis of condition types affecting
pricing (the basic purchase price, vendor discount, for example). Other pricing-relevant
parameters including the regular vendor indicator in the purchase info record and the source of
supply indicator in the article master data are evaluated in supply source determination.

If the purchase price or the above parameters for source determination change, it is advisable to
check the existing sales prices with respect to the new margin.

The pricing worklist function allows you to determine all calculations affected by parameter
changes.

Prerequisites

If you want to use the pricing worklist function, you must make sure that when you save a sales
price a pricing document is created with a document index. This setting is made under Pricing
type.

You make the settings necessary for using the pricing worklist function under Pricing Worklist in
Customizing for Pricing.

2
 Karun Gaur

Features

When a pricing worklist is created, new calculations are carried out for those articles and
organizational levels with calculations that are affected by changes.

Note
These recalculations are managed as pricing documents in pricing document type 0002.

To determine the validity periods for the new calculations, the system takes the validity periods
both of the changed conditions and of the original calculations into account.

You can select documents from the pricing worklist to process separately.

For more information, see Processing the Pricing Worklist.

If you process an item but neither save nor delete it, it has status B (changed, not saved).

Note
Pricing documents are created with the pricing document type 0001 from the items you save in
the sales price calculation.

Source data for determining changes relevant to price calculations

The following are used as source data for determining which calculations are affected by pricing-
relevant changes:

 Change pointers for the changed conditions or the parameters for supply source determination.

 Document indexes for pricing documents

Document indexes are secondary indexes for selecting documents according to a particular
criterion. Generating pricing documents with document indexes prevents you having to evaluate
every single document. Document indexes allow you to find documents affected by changes in
purchase prices quickly and thus to efficiently create a pricing worklist of sales prices to be
recalculated.

3
 Karun Gaur

You can make settings for creating pricing documents with document indexes under Pricing
type in Customizing for Pricing. Here, you can choose between:

 Pricing documents with adjustments for changes in conditions

This document index determines only those calculations affected by a change in purchase price.

 Pricing documents with adjustments for changes in conditions and master data

With this document index, calculations that are affected by changes to the source of supply
parameters are entered, in addition to those affected by changes in purchase prices.

The Business Add-In (BAdI) SPC_DOCINDEX_CONTROL allows you to change document index
creation for an item in the pricing worklist according to your own requirements. The BAdI is used
as a filter for the document indexes that are to be created on the basis of the pricing worklist
settings in Customizing. You can exclude individual or all of the document indexes from the
update.

Example
No document indexes should be created when you are pricing perishable articles, as the pricing
worklist function is not used for these articles. This is because the purchase and sales prices
change very regularly for perishables.

Example

The following graphic shows how a change to the basic purchase price and the vendor discount
generates three items in the pricing worklist.

4
 Karun Gaur

For more information, see Automatic Document Update After Condition Changes.

Rules for Changing the Regular Vendor Indicator

If you set the regular vendor indicator in a purchase info record for a specific vendor for the first
time, all that article’s sales price calculations that were not calculated with this vendor will be
altered. However, if you change the regular vendor indicator, those sales price calculations that
were calculated with the original regular vendor will be altered. Sales price calculations that were
neither calculated with the old nor with the new regular vendor will not be altered, as you are
intentionally changing the regular vendor.

Worklist Generation
Use
If updating of change pointers to table BDCP for message type CONDBI has been
activated, this setting applies to all condition types defined in the system. However, only a
certain part of the condition changes is relevant for the different applications. For this
reason, it is advisable to further restrict the change pointers from table BDCP , based on
the requirements of the individual application areas. This is carried out for the relevant
applications using worklist generation (transaction ME14 ).
Such filtered change pointers (worklist) are updated to table WIND for all applications. The
distinction between individual worklists for different applications is made at the same time
as document indices are created for the document category:

5
 Karun Gaur

Application area and corresponding document category

Application Area Document Category

Purchase order (purchasing documents) 01

Pricing 10

Order optimizing/investment buying 02

Assortment list 50

POS outbound 55

Change pointers are filtered from table BDCP using Customizing settings stored in
table T6I1. In table T6I1 you specify which condition types and condition tables the worklist
is to be created for.

The following transactions for making these settings are defined in Customizing for the
individual application areas:

Application Area Transaction in Transaction Description

Customizing

Purchase order OMHJ Adjusting purchasing

documents

Pricing OWV2 Adjusting pricing documents for

OWV4 external reference
Adjusting pricing documents for
internal reference

Order optimizing/investment OWIA Change-specific condition types

buying for investment buying

POS outbound OWS2 Maintaining document indices

Note
Table T6I1 also controls the updating of document indices in the application
areas Purchase Order and Pricing . This ensures that worklist generation and document
index updating are reconciled with one another. For more information see Updating of
Change Pointers and Document Indices .

6
 Karun Gaur

Procedure
The following graphic illustrates the procedure for worklist generation.

1. If condition changes occur, change pointers are updated to table BDCP.

2. When a worklist is generated, these change pointers are filtered according to the
entries in table T6I1, and updated to table WIND.

Result
The filtered change pointers are separated in table WIND according to document
category/application area.

Direct Creation of Worklist Entries

Use

In the procedure described in Worklist Generation the entries in the worklist are created on the
basis of the change pointer for condition changes (message category CONDBI ) within worklist
creation (transaction MEI4 ). However, when creating worklist entries directly, change pointers
are no longer needed. When you change a condition, and create new conditions entries are now

7
 Karun Gaur

created directly in the worklist. This means that the previous performance-intensive process step
of creating a worklist from change pointers is now eliminated. You also no longer need to update
change pointers for condition pointers if these are not going to be used in other processes.

Integration

If change pointers for condition changes are eliminated, the dataset for change pointers is
reduced considerably. A change pointer generally consists of several entries in
table BDCP or BDCP2.

The following differences occur:

 The table width of table WIND grows due to the extra fields from 45 bytes to 262 bytes.

 The number of table entries in the worklist can decrease due to the extra filter criteria.

 Change pointers for message category CONDBI are no longer required.

Customizing for worklist creation described above, which determines which condition types are
to be included in the worklist (table T6I1), is also valid for direct creation.

Features

 Direct creation of entries in the worklist according to condition changes.

 Inclusion of extra data for an entry in the worklist

The extra data for a worklist entry consists of header data for the conditions, which improve
performance in subsequent processing and variable customer fields, which enable selective
subsequent processing. The filling of customer fields is determined by the system tableT6I2S.
The filling of customer fields can, however, also be manipulated using the BAdI WIND_UPDATE.

 Additional filter options

For each document type, you can determine the types of condition changes (amount change,
validity, relevancy to costing etc.) for which worklist entries are created. Customer-specific filter
criteria can also be created using the BAdI WIND_UPDATE, which is dependent on the filter
criterion Document type.
8
 Karun Gaur

The following example illustrates the possibilities of the BadI:

Example

Due to changing purchasing conditions, perishable articles are recalculated at regular intervals
therefore sales prices do not need to be updated using the pricing worklist process. In this case,
use the article type as an additional filter criterion for the Pricing application (document category
10). When you change the basic purchase price for a perishable article, the system does not
generate a worklist for this document category because of the filter criteria set in place.

Activities

If you want to use the worklist in conjunction with the procedure for direct creation of worklist
entries, there are two different cases to distinguish between:

 In the case of a new installation or if you have not used document adjustment for a certain
document category yet, set the indicator for direct entry directly in Customizing.

 If you already use the worklist with creation on the basis of change pointers, you need to switch
to the new procedure. Report RMEBEMIG belongs to the conversion procedure and is used to
extend existing worklist entries to include condition header data and to extend the data in the
customer fields. This report sets the migration indicator, which signals the extension and is
visible in Customizing when you activate direct entry. The report can also be used to set the
direct entry indicator automatically. For more detailed information on the conversion procedure,
see SAP Note 519685.

For each document category, determine the types of condition changes for which you want
worklist entries to be created as filter criteria. Different types of condition changes (scope of
change) relevant for this application are delivered as standard for the individual document
categories. The scope of change delivered for direct entry is identical to the scope of change for
updating change pointers for this application.

The filling of variable customer fields for the worklist entries is preset by system table T6I2S in
the delivery status. If you want to proceed differently to the default setting, you need to create a
suitable implementation for the BadI.

9
 Karun Gaur

The check for existing document indices (table S111) that is possible in the worklist creation
procedure using change pointers, now needs to be implemented in the BadI WIND_UPDATE as
an additional filter criterion (see Sample Coding for the BadI).

If direct creation of worklist entries is set for all document categories used, you do not need to
create change pointers from the message category CONDBI. Deactivate the message
category CONDBI in ALE Customizing.

Processing the Pricing Worklist - Procedures

Use

This business process shows you how to create and process a worklist comprising all those price
calculations affected by changes to parameters relevant to pricing.

Parameters such as the basic purchase price or vendor discounts, which form the basis for the
calculation of sales prices (that is retail prices or warehouse transfer prices), can change during
the validity period of a sales price. To be able to update sales prices to reflect these changes,
you must be able to find all the relevant price calculations.

This function enables you to compile a pricing worklist, which is a list of all price calculations that
have been stored in the form of pricing documents and that are affected by the parameter
changes, taking the validity period of each price calculation into account.

Prerequisites

You can only use the pricing worklist function if a pricing document with a document index is
created when you save a sales price.

Procedure

1. Create a buffer of data out of the changed parameters (known simply as a "worklist") which forms
the basis for generating the pricing worklist.

10
 Karun Gaur

You do not have to perform this Customizing activity if you have made the settings for the direct
entries in the worklist for condition changes in Retail Pricing (document category 10)
under Logistics - General Retail Basic Data Activation of the Direct Entry for Creating the
Worklist.

1. Generate the pricing worklist from the worklist of price calculations you wish to update.

2. When a change is made to the master data concerned in the pricing worklist function (regular
vendor indicator and vendor subrange in the info record, source of supply indicator in the article
master), you no longer have to perform IMG activities 1 and 2. This is because when the master
data change is saved, the pricing that is affected by this is determined at the same time and the
appropriate entries are created in the pricing worklist.

3. Process the pricing worklist for specific articles and organizational units.

4. The new prices that are calculated are stored, as before, in pricing documents. You can change
the results by setting certain parameters, such as the article mark-up rate, the margin, the sales
price or the final price.

5. Save new sales prices that you are happy with and delete any price calculations that you do not
want.

Creating a Pricing Worklist Item

A pricing item in the pricing worklist is created in much the same way as a pricing item in the
sales price calculation. The following 2 activities are all you need to do:

1. Perform pricing for purchasing based on the conditions that have been changed to determine the
purchase price (net/net).

2. Calculate the mark-up based in the purchase price you determined in the first step.

Once you have completed the first step, the system checks whether a purchase price change
has been made at all and whether it is necessary to make an entry in the pricing worklist. Such a
situation normally arises when you create a purchase condition with a validity period in the future
that overlaps with existing conditions. In the period, up to the validity start date of the new
conditions, there are no changes. The original condition is taken into consideration in the
creation of worklist entries, however, due to the validity end date having been brought forward.

11
 Karun Gaur

You can use the Business Add-In (BAdI) PWL_SP_DETERMINATION when a pricing worklist
item is being created to control how the pricing worklist is structured so that it fits the needs of
your company.

Method PROCESSCHECK_AND_SP_DETSEQ_SET, which is called after the first activity is

completed, has 2 functions. Based on the purchase price determination for the new purchase
conditions, you can also check - in addition to the standard check described – whether an entry
needs to be made in the pricing worklist at all. This way you can determine a lower (percentage)
threshold value for a purchase price change of which no entry should fall short.

You can also determine with which sales price determination sequence the pricing in sales
should be performed in the second activity. You can use sales price determination
sequence 02 as a default if you do not want to change the sales price, for example, for articles
with a lot of competition.

The second method, CALCULATION_ITEM_MODIFY, which is called after the second activity is
complete, fulfils 2 functions. A check can also be run here to see whether an entry has to be
made in the pricing worklist. The same price point may have been found in a markdown pricing
despite purchase price conditions having changed, and this would make an entry unnecessary.
You can also make changes to the pricing item in this method. This would therefore be useful in
a scenario where, for example, only part of the increase in the purchase price for certain articles
should be transferred to the customer via a sales price increase.

>>>>>>>>>>>>>>>>>>

In System:
As the work list were create before using MEI4, so we had to Migrate the BDCP2 table to wind
table using the migration program RMEBEMIG.

For document Category 10 Pricing: Pricing worklist

12
 Karun Gaur

This will make the entry in:

Also after doing this we can turn off the change pointer for COND_BI so that the entry in BDCP2
table will not generate

Now change the info record for some article & vendor this must create entry in WIND table

13
 Karun Gaur

Table used
WKBK: Pricing document: Header
WKBP: Pricing document: item

T-codes

VKP3 - pricing document for material

VKP5 - Create Calculation

VKP2 - Display POS Conditions

VKP5 Create Price Calculation
WPMA Direct Request For POS Outbound
WMB1 Create Price Entry
WKK1 Create Market-basket Price Calculation
SPRO Assign Price Point Group to Org. Level/Merchandise Category
WVA3 Display VKP Calculation Sur
WVA7 Display VKP Calculation Sur
WEV3 Display Ret. Mark-up SP Ca
MEKE Conditions By Vendor
ME21N Create Purchase Order
V-61 Create Customer Discount Condition
V-64 Display Customer Discount
VK13 Display Condition Records
V/LD Execute Pricing Report
VA01 Create Sales Order

14
 Karun Gaur

MEI4 Create Automatic Document worklist

BD22 Delete Change Pointers
WVN0 Generate Pricing Worklist
WVN1 Release Worklist

15