714_BPP_EN_US
-
Upload
ritesh0416770 -
Category
Documents
-
view
215 -
download
0
Transcript of 714_BPP_EN_US
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 1/23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 2/23
Germany
© SAP AG Page 2 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 3/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
Copyright
© Copyright 2008 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission 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.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9,z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+,OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide WebConsortium, 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 andimplemented by Netscape.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All other product andservice names mentioned are the trademarks of their respective companies. Data contained in this documentserves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, andSAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the express warranty statements accompanyingsuch products and services, if any. Nothing herein should be construed as constituting an additional warranty.
© SAP AG Page 3 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 4/23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 5/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
Contents
1 Purpose............................................................................................................................................ 6
1.1 Process Flow............................................................................................................................. 6
2 Prerequisites.....................................................................................................................................7
2.1 Related Master Data................................................................................................................. 7
3 Process Overview Table...................................................................................................................9
4 Scenario..........................................................................................................................................10
4.1 Maintain Site Specific Prices...................................................................................................10
4.2 Price Calculations for Generic Articles and Variants...............................................................11
5 Manual Price Change................................................................................................................... .. 13
5.1 Assign Price Planner Groups ............................................................................................. ....13
5.2 Creation of a Manual Price Plan in the Price Planning Workbench.........................................145.2.1 Header Data General........................................................................................................14
5.2.2 Organization Sets ............................................................................................................ 15
5.2.3 Article Selection................................................................................................................16
5.2.4 Releasing a Price Plan..................................................................................................... 19
5.2.5 Creation of Conditions in SAP ECC..................................................................................21
5.2.6 Activation of the Price Plan ..............................................................................................22
5.2.7 Download of Price Changes to POS ................................................................................23
© SAP AG Page 5 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 6/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
Manual Price Changes in the Price PlanningWorkbench
1 PurposeThe Price Planning Workbench (PPW) provides a uniform working environment for price planning. Inrule-based markdown controlling, markdown proposals that have been created in slow seller management in SAP Business Intelligence (SAP BI) are processed and then transferred to SAPECC in a special work list. For the creation of promotions and manual price changes via the PricePlanning Workbench, articles and organizational levels have to be selected manually by the user.Functional integration of the sales price calculation allows the use of the information from the pricecalculation.
A connected budget function enables the user to monitor sales deductions in the PPW that resultfrom planned price changes. To calculate the sales deduction, the system takes both into account,the price differences and the current stock and planning quantities. The system displays the effectsof the price changes on different budgets in the Budget Monitor.
The relevant price planning data is saved in a price plan. Once planning is completed, the price planhas to be released for subsequent processing. An approval procedure can be used to preventunwanted price changes if a budget overruns. Only specified approvers can then release the priceplan. In subsequent processing, the system creates the sales conditions maintained in the price planand updates the budgets.
This process covers the creation of a manual price plan in the Price Planning Workbench (PPW)which can be used to make price changes for articles and organizational levels.
1.1 Process Flow
Manual Price Plan Creation
© SAP AG Page 6 of 23
PPW Price Plancreation
Release of Price Plans
Creation of Conditionsfor Price Plans
Activation of PricePlans
Download of pricechanges to POS
wnload POS
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 7/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
2 Prerequisites
2.1 Related Master Data
The articles are single articles and generic articles
Fashion Hard Goods Food
Article PCS-01-ART112
PCS-01-ART113
PCS-01-ART451
PCS-01-ART452
Vendor PCS-V111 PCS-V451
Storage Location 1 1000 1000
All articles are listed in the following sites. The merchandise categories and price lists are assignedto the site master data.
Site Price List MerchandiseCategories
Site M001 P4 MC11142
MC11151
MC11152
MC11422
MC11441
MC14501
Site M002 P4 MC11142
MC11151
MC11152
MC11422MC11441
MC14501
Site M004 P5 MC11142
MC11151
MC11152
MC11422
MC11441
MC14501
Site M005 P5 MC11142
MC11151
MC11152
MC11422
MC11441
MC14501
Site M007
Site M008
© SAP AG Page 7 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 8/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
In order to run through this scenario, the articles must have stock available in the sites. Please usethe transaction code MB1C with movement type 501 (in background the SAP ECC system creates apurchase order) to create the inventory posting. With transaction RWBE you can check whether stock is available or not. Enter article number and site number in the selection screen.
© SAP AG Page 8 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 9/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
3 Process Overview TableStep Step Name External
ProcessReference
BusinessCondition
Role TransactionCode
ExpectedResults
4.1 Maintain Site Specific Prices Retail Pricing
Manager
VKP5
4.2 Price Calculations for Generic Articles and Variants
Retail Master DataManager
MM42
5.1 Assign Price Planner Group Retail MarkdownPlanner - Manager
WRF_PPW12
5.2 Creation of a Manual Price Planin the Price PlanningWorkbench
Retail MarkdownPlanner
WRF_PPW01
5.2.4 Releasing a Price Plan Retail MarkdownPlanner
WRF_PPW01
5.2.5 Creation of Conditions Retail MarkdownPlanner - Manager
WRF_PPW03
5.2.6 Activation of Price Plan Retail MarkdownPlanner
WRF_PPW04
5.2.7 Download of price changes toPOS
© SAP AG Page 9 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 10/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
4 Scenario
4.1 Maintain Site Specific Prices
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Logistics→ Retailing→ Master Data → Pricing→ Price calculation
Transaction code VKP5
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Retail Pricing Manager (SAP_BP_RT_PRICING-S)
Business role menu Pricing → Price calculation → Create Calculation
2. Please check if the following settings have been made.
3. Make the following entries:
Selectioncriteria
Input
Article PCS-01-ART112* for Fashion or
PCS-01-ART451 for Hard Goods
Sales org 1000
Distribution Channel 10
Site M001
Validity date No change
List Group B
4. Choose Execute.
5. Choose the Next Item button to display the site-specific prices.
6. Go to the Final Price field and decrease the price by 2 USD for the following article:
For Fashion For Hard Goods
PCS-01-ART112001
PCS-01-ART112004
PCS-01-ART112006
PCS-01-ART451
© SAP AG Page 10 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 11/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
7. Make all entries and save. Confirm the message that appears.
4.2 Price Calculations for Generic Articles and Variants
This section applies only to Fashion.
Use
Generic articles and variants can a lot of work when maintaining identical master data for articlesthat only differ in one or two characteristics such as different sizes or colors.
This simplified process can also be used for maintaining sales prices. This involves the variants of ageneric article inheriting the sales price of the generic article or that of another variant. This isdefined via pricing reference articles in the article master data. If a variant inherits a sales price fromanother variant, you cannot create a separate sales price for it in a sales price calculation. A salesprice can only be maintained for the pricing reference article itself. In this way it is possible for example to maintain the same sales price for all sizes of a certain color of an article.
PrerequisitesIn order to run through this scenario the pricing reference article of all generic articles mentionedbefore must be changed.
You must maintain the following settings in the master data of the generic article and the variants.
Pricing reference article maintenance
Whether and how a sales price is to be copied to a variant is controlled by the Pricing Reference Article field in the master record for each variant.
The pricing reference article can be specified in the basic data view (if you create a new article) or the sales view of the variant’s master data (if you change a maintained article). If the pricing
reference article is changed in the basic data view, this change is transferred automatically to thesales view for the distribution chains maintained for new articles.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Logistics→ Retailing→ Master Data → Article Data → Article→
Change
Transaction code MM42
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Retail Master Data Manager (SAP_BP_RT_MASTERDATA-S)
Business role menu Article → Article Master → Change Article
2. Enter the following data:
© SAP AG Page 11 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 12/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
Article Sales Organization Distribution Channel
PCS-01-ART112 1000 10
3. Select the Sales view.
4. Press Enter .
5. In the Sales view, choose the Variant Prices button.
6. Go to the PrcRefArt tab.
7. Choose the Maintain PR Art button.
8. If there are article variants displayed in the first column, pricing reference articles exist. Inthis case perform steps 9 to 15.
9. Check for the first reference article variant if the price is calculated by doing the following:
• Use transaction MM42. In the Article field, enter the pricing reference article.
• In the Areas of Validity, enter the following data:
Sales Org. Distr. Channel
1000 10
10. Select the Sales view.
11. Choose the button and choose Enter .
12. If the field Curr.FinalPrc in the Current Price section is not zero, the prices are calculated.If the field Curr.FinalPrc in the Current Price section is zero, flag the Save calculated Price field.
13. Choose the Save button. Exit and go to transaction MM42.
14. Repeat steps 9 to 14 for the other pricing reference articles that were displayed in step 8. If there are no article variants in the first column, pricing reference articles do not exist. Createthem as described below:
15. Choose the Characteristics button
16. Choose the characteristic PCS Colours Basic
17. Choose the Characteristic Values button.
18. With the F4-help choose for each color the variant that should be used as pricing referencearticle.
19. Choose the Adopt button.
20. Choose the Adopt button again.
21. In the same screen select the checkbox for saving sales priceconditions.
22. Choose the Back button.
© SAP AG Page 12 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 13/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
23. Save your entries.
5 Manual Price Change
5.1 Assign Price Planner Groups
Prerequisites
Price Planner Groups are defined in the system.
Procedure
A user can only run through this scenario if the user’s name is assigned to the price planner group.Otherwise the user has no authorization to access the budgets in the Price Planning Workbench.Thus the following assignment is a prerequisite to continue with the process.
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Logistics → Retailing → Master Data → Price Planning →
Budgets → Authorization Administration for Budget Access →
Assign Users to Price Planner Group
Transaction code WRF_PPW12
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Retail Markdown Planner - Manager (SAP_BP_RT_MARKDOWNPLANNER-EC-E)
Business role menu Markdown Execution→
PPW Authorization→
Budget: AssignPrice Planner Group
2. Assign your user name to Price Planner Group PPW1 by choosing the New Entries buttonand entering the following data:
Price Planner Group User name
PPW1 Your user name
3. Save your entries by selecting the Save button.
© SAP AG Page 13 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 14/23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 15/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
Field Value
Distribution Channel 10
5.2.2 Organization Sets
Here the price levels and attributes, which are supposed to be assign to the articles can bemaintained. This process only allows Organization Sets with type 01 Organization. Thus thefollowing price levels can be defined:
• Distribution Chain
• Price List
• Site
Prior to using any combination of price levels and attributes in a price plan an Organization Set hasto be defined.
1. Choose the Organization Sets tab.
2. Choose the Create Organization Set button to create a new Organization Set.
3. Specify a description for the Organization Set.
4. Select the newly created row.
5. Choose the Detail View: Org. Levels button .
6. Choose the Insert Blank Line button to add a combination and enter the following data:
Sales Organization Distribution Chain Site
1000 10
7. Choose the Copy button to adopt the data.
8. Repeat steps 2-7 to create a second Organization Set. Choose any combination from thefollowing:
SalesOrganization
DistributionChain
Price List Site
1000 10
1000 10 P4
1000 10 P5
1000 10 M007
1000 10 M008
You can save your Organization Sets so you can reuse them easily in a different price plan:
9. Select the organization sets just created and choose the Save button in the OrganizationSets tab. Save the Organization Set user-specific via the dropdown box.
10. You can check your permanent organization sets in the tree on the left hand side using thedropdown menu Manual Price Changes and selecting the entry Organization Sets.
© SAP AG Page 15 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 16/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
11. Choose the Refresh button and all created Organization Sets and their details will bedisplayed.
You can define an Organization Set as default-value (set default flag to . Thiscan only be done for one row). All articles that will be transferred afterwards to the work area willautomatically be assigned to this Organization set. If a default Organization Set is not defined, it willhave to be selected manually for every article transferred to the work area.
5.2.3 Article Selection
Articles for the price plan can be selected in the tree on the left hand side.
1. Change the selection from Organization Sets to Manual Price Changes with the dropdownmenu on the left.
2. Choose the Select Material(s) button to select the articles.
Selection criteria Entry
Sales Organization 1000
Distribution Chain 10
Article For Fashion:
PCS-01-ART112
PCS-01-ART113
For Hard Goods:
PCS-01-ART451
PCS-01-ART452
3. Choose the Execute-button to display the articles.
4. Expand the tree on the left hand side completely.
5. For generic articles, all pricing reference articles are displayed. Single articles are their ownpricing articles.
6. Mark your article numbers or the whole node in the tree and choose the Copy to Work Area
button to adopt the article in the work area.
7. Now the adopted articles can be seen in the work area.
5.2.3.1 Work Area – Overview
Organization sets have to be assigned to the pricing articles.
1. Mark the first two pricing articles and choose the Assign Organization Set button .
2. Select the first Organization Set.
3. Choose the Execute button.
4. Mark all other pricing articles and choose the Assign Organization Set button .
© SAP AG Page 16 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 17/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
5. Choose the second Organization Set.
6. Choose the Execute button.
7. Check the additional information that is now being displayed in each line.
The fields which are displayed are defined in layouts. It is possible to change these layouts, adding
additional fields or changing the order of the fields.
5.2.3.2 Work Area – Detail
In the detail view of the article the calculated sales prices for the individual price activationlevels can be displayed and changed. Further, price levels and the amount of the pricechange are indicated. Price changes are possible on the following price levels:
• Distribution Chain
• Price List
• Sites
1. Select the first four pricing articles (depends on the prior article selection).
2. Choose the Details button.
3. One line is displayed for each level defined in the Organizational Set for this pricing article.
4. Check the data displayed.
5.2.3.3 Changes in the Work Area – Overview
The field Sales Price from Condition displays the actual current final price of the article at themoment.
Via the Price Planning Type it has been determined in general whether price increases are allowedor not. In case a price increase is not allowed, the system generates a message.
The configuration of the price planning type is described in Configuration Guide 716 available on thedocumentation DVD under \BBLibrary\Documentation.
To change the proposed new Final Price the following fields can be used among others:
1. Percentage Price Change to Orig. Price: A percentage change from the current price.
2. Percentage Price Change to Current Final Price: A percentage change from the pricemaintained in the Final Price field.
3. Absolute Price Change to Original Price: Absolute change from current final price.
4. Final Price: A new final price can be maintained directly.
5. Price point group: A different rounding rule can be maintained.
These changes can be done one article at the time, changing the entries in the relevant fieldsmanually or using mass maintenance. Using mass maintenance is recommended even if only onesingle lines is changed since the negative sign for a percentage change is automatically set and thethe rounding by price point group can be activate or deactivate.
© SAP AG Page 17 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 18/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
1. Select one or more lines.
2. Choose the Mass Change button .
3. Test different possibilities of changing the price of the article.
Example for a price change:
Field Entry
Change final price Set Flag
Amount 25
Change type Percentage change
Base price Current final price
4. Choose the Execute button to execute the price changes.
5. Check that other price relevant fields are changing as well.
5.2.3.4 Check Dependent Articles
To check if dependent articles exist for a pricing reference articles, select one article and choose the
Article for Pricing Reference button .
5.2.3.5 Budget CheckThe budget is calculated according to the following formula:
(Old sales price - new final price) * stock considered.
In the budget monitor the data is displayed cumulated to a single budget number.
Procedure
1. Choose the Budget Monitor tab in the header data.
2. Select the Budget Overview button and select Budget for Price Plan.
3. If a green icon is displayed, it is possible to release the price plan immediately without anapproval procedure.
4. Check the figures which are shown for your budget.
5. Check whether the cumulated budget sum from all articles in the work area is the same as inthe field Planned Price Plan Current in the budget monitor.
6. Change the prices in the work area again and see how the budget monitor reacts.
7. Check the details of your budget. Use the detail button to take a look at what has alreadybeen planned with this budget.
© SAP AG Page 18 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 19/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
5.2.3.6 Deactivate Price Variances
The icon is displayed in the field Own Prices Exist in the work area (detail view or overview). Theicon indicates that prices at a more specific level exist.
1. Mark at least one of the pricing articles for which the icon is displayed.
2. Choose the Organization Levels with Own Prices button in the header toolbar of thework area.
3. Check the price variances displayed.
4. A red, yellow or green icon in the ID column indicates whether or not it is possible todeactivate the prices.
5. To deactivate a price, highlight the line and select the Deactivate Prices button.
5.2.3.7 Save Price Plan
Procedure
1. Save your data by choosing the Save button. A message appears to confirm that the priceplan was saved.
2. Note down the number of your price plan.
3. To check the status of your price plan, go to the Header Data - General tab. The statusshould now be In Process.
5.2.3.8 Selection of the Price Plan in the Tree
1. On the left hand side of the screen change the selection back to Price Plans by using thedrop down menu behind the button now labeled Manually.
2. Expand the price plan tree.
3. The price plan just saved appears with status In Process.
5.2.4 Releasing a Price Plan
A direct release of the price plan is only possible if the budget is in green status. If the status is redand marked for workflow the document will have to be forwarded to the person responsible for approval. If the budget has been approved, the price plan goes to status Released . Otherwise it
changes to status Resubmission and the price plan has to be revised. It is possible to implement aworkflow, so that the respective user will be notified via a message:
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Logistics Retailing Master Data Price Planning
© SAP AG Page 19 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 20/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
Price Plans Edit
Transaction code WRF_PPW01
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Retail Markdown Planner (SAP_BP_RT_MARKDOWNPLANNER-EC-S)
Business role menu Markdown Execution → PPW Execution → Price Planning
Workbench
1. Choose the Select Price Plans button to select the price plan just created.
2. Mark the price plan and use the Copy to Work Area button to open the price plan.
3. Use the Display/Change button to switch to change mode.
4. Choose the Release button and confirm the message with Yes.5. Select the Header Data - General tab: the status of your price plan is now Released .
6. Use the Refresh Display button on the left hand side to update the tree with the price plan.Now you can check whether the price plan is displayed under the node Released .
7. In case the Price Plan goes to status For Release instead of Released the price plan willhave to be approve as discribed in steps 7 – 11.
8. Open a second mode.
9. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Logistics Retailing Master Data Price Planning Price Plans Approve
Transaction code WRF_PPW02
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Retail Markdown Planner - Manager (SAP_BP_RT_MARKDOWNPLANNER-EC-E)
Business role menu Markdown Execution → PPW Execution → Price Plan: Approve
10. Select the Price Plan number via the F4 help or enter the price plan document number (PPD) directly.
11. Choose the release price plan button .
12. The status of the price plan will change now from For Release to Released.
13. Return to the first mode.
© SAP AG Page 20 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 21/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
14. Use the Refresh Display button on the left hand side to update the tree with the price planagain. The price plan should now appear under the node Released .
5.2.5 Creation of Conditions in SAP ECC
After the release, the relevant conditions for the articles in the price plan can be created with areport. The conditions are created for the organizational levels defined in the Organization Sets.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Logistics Retailing Master data Price Planning PricePlans Create Condition
Transaction code WRF_PPW03
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Retail Markdown Planner - Manager (SAP_BP_RT_MARKDOWNPLANNER-EC-E)
Business role menu Markdown Execution → PPW Execution → Price Plans: Create
Conditions
2. Start the report by selecting your price plan and choose F8 or the Execute button. The user can see that the conditions have been created.
3. Access the log by choosing the Application log button.
4. Check the created conditions VKP0 using one of the following options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Logistics Retailing Master data Price Planning Environment Price Overview
Transaction code VKP2
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Retail Markdown Planner – Power User (SAP_BP_RT_MARKDOWNPLANNER-EC-K)
Business role menu Markdown Planning → Overview → Display POS Conditions
Example:
© SAP AG Page 21 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 22/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
Field Entry
Article For Fashion:
PCS-01-ART112001
PCS-01-ART113001
For Hard Goods:
PCS-01-ART451
PCS-01-ART452
Sales Organization 1000
Distribution Chain 10
Site (depends on the price levels of the articlesthat have been defined in the price plan)
M007; M008
Price list P4 and P5
Display distribution chain and site/price listprices separately
flag
List group B
Validity period Today’s date – 31.12.9999
Display price origin flag
5. Choose F8 or the Execute button.
6. Check the created conditions and the amount on the correct organizational levels. Thisdepends on the organization sets that were used in the price plan.
7. If existing, take a look at the different price levels with the next screen button .
8. Follow the description in section 5.2 to go back to the Price Planning Workbench to take alook at the status of your price plan. Choose the Select Price Plan button and select your price plan. The status should be Conditions Created .
5.2.6 Activation of the Price Plan
With this report, the relevant budget amount as well as stock changes are updated in the price plan.
Procedure
1. Access the activity using one of the following navigation options:
Option 1: SAP Graphical User Interface (SAP GUI)
SAP ECC Menu Logistics → Retailing → Master data → Price Planning → Price
Plans → Activate
Transaction code WRF_PPW04
Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role
Business role Retail Markdown Planner
© SAP AG Page 22 of 23
7/30/2019 714_BPP_EN_US
http://slidepdf.com/reader/full/714bppenus 23/23
SAP Best Practices 714: Price and Revenue Management - Manual Price Changes - BPD
(SAP_BP_RT_MARKDOWNPLANNER-EC-S)
Business role menu Markdown Execution → PPW Execution → Price Plans: Activate
2. Select your price plan in the appropriate field or enter it manually and choose F8 or theExecute button. The user can see that the price plan has been activated.
3. Take a look at the application log by choosing the Display log button . Here, an entryexists that the price plan was activated successfully.
4. Follow the description in section 5.2 to go back to the Price Planning Workbench and check
the status of the price plan. Choose the Select Price Plan button and select your priceplan. The status should be Active.
5.2.7 Download of Price Changes to POS
After the conditions have been created, the price changes will be downloaded to the POS system.