Retail MM Pricing

Hi Experts,
I am new to retail.
I had a issue with respect to Retail price.
We are maintain price with respect to Vendor in article master, For the first time where we maintain or update price with respect to one Vendor an info-record is created.
The major Constraint is my client wants
1) The same price needs to be updated or extended even for other vendors without maintaining an Info-record.
Second Major issue:
2) When we are extending the article master with respect to other stores all the views get extended automatically by using the Listing B1, except Purchase View.
For this we need to extend enter the distribution Centre as Vendor and with respect to single store we need to extend the Unit price of that vendor.
And we need to do the number of times the stores are there.
My Client wants when we create an article with respect to external vendor, the same price needs to be extended for other vendors without maintain an additional info record.
Apart from this they want same price to be extended for other stores which has been maintained in distribution centre without maintaining any additional inforecord.
Is it Possible ?
Please guide me with your valuable inputs.
Best Regards
Javeed

Could u tell me why we required Stock Transport Order for this ? Cant we use Normal Purchase order Document type ? raised from Store ?
- if your DC and store belongs to different company code, then just use 'normal purchase order' (better create a new order type, eg. ZNB), but we normally also call it 'stock tranport order' as the DC is an internal vendor.
Secondly How it will transfer the Price from Distribution Centre to Store ? Because store has to raise a Purchase Order and price needs to be picked Up rite ?
- Retail Pricing: "DC sales price" could be created via MM41/MM42/VKP5
- Purchasing Pricing Schema assigned to Stock Transport Order (DC->Store): contains the condition type of 'DC sales price"

Similar Messages

AFS-Retail Interface-Pricing Conditon Proces (Sales Condition - INFORECORD)

Hi Experts,
We are working on Integration between AFS and RETAIL systems.
We are facing Issue in Sending Sales conditions (VK13-VKP0) from the AFS side, Transfer over to the Retail side as INFOREORD.
What settings (Configurations) are required in AFS & Retail system ?.
When Sales conditions (VK13) are sent in AFS what is the Message Type to be Used ?.
Any Input is highly appreciated.
Thanks and Regards,
Selvakumar. M

Hello Marat,
Did you meant Pricing Info records. If yes, it need to be maintained at the AFS side. When interfacing the materials from AFS to Retail using BD10, you can use the option 'Send Material in Full' to send the prices also.
The prices can be maintained using the transaction VK11. It can be maintained on the material level and also on SKU level. When interfacing as mentioned before, INFREC and COND_A IDocs will also be generated.
Hope this address your query.
Regards
Sudha

IS-Retail Competetor Pricing and Pricing Rules

Hello ,
Can any one give more insight in to Competetor pricing. It is delfined in IMG - Logistics-general - Retail Pricing - Competitive pricing .
Also It is defined in article master MM42 under sales tab. I would like to know how the process flow works and also how pricing rules is defined in relation with competitive pricing.
Thanks in Advance
Karthik

Hi,
You can use single-step or two-step sales price calculation, depending on whether a single-step or two-step logistics process used in your system.
Single-step: Single-step price calculation is performed when a store procures articles directly from a vendor, that is, if there is no upstream organizational unit assigned to the store. Calculating sales prices for the stores is based on the purchase price for external vendors. For example, DSP products... I mean Daily Supplied Products like Milk, Curds, Bakery Products so on.
*Two-step" : Two-step calculating sales prices for the stores is based on the transfer price for distribution centers.
http://help.sap.com/erp2005_ehp_04/helpdata/en/12/085147470311d1894a0000e8323352/content.htm
Bye,
Muralidhara

Retail: Maintain pricing conditions at general article level in PO

Hi,
I create a seasonal purchase order. In this purchase order I enter a general article with several variants. Is there a possibility to maintain pricing conditions at the header item level which will be copied to the variants.
NB: these surcharges and discounts, so they are not in the info record.
Kind regards,
Rudy

Your issue can be solved with header condition.
Header Conditions are referring to entire document. You may not able to use automatic price determination for header condition.
A header condition can be a percentage or a fixed amount. If you define a header condition as a percentage markup or markdown, the defined percentage applies automatically for all document items. If the header condition is a fixed amount
and if this condition is not additionally flagged as a group condition, the condition amount of the header condition is assigned for each item.
Header conditions are created manually at header level in a purchasing document.

Retail Sales Pricing - Hour based promotions "happy hour"

Hello experts,
One business requirement pricing is to have store pricing depending on hour interval for a given period of dates, example:
+ Sales Org. X / Store Y;
+ Article W;
+ from 01.01.2011 to 01.02.2011;
+ and from 20h00 to 21h00;
= new price Z
I've managed to find fields "start time" and "end time" in condition tables, but I guess this fields work on a "one time only" and not "Weekly".
Does anyone know the best way to manage this requirement? This is a functionality to use both in pricing and in promotions (for the same example, the result, instead of "price Z" could be: 2nd Article W for free).
Any input welcomed, thanks!

Hi Goncola,
The same requirement has been catered for one of my clients using a complete "Z" program through which a customised screen should be created with an option of introducing a new field "Valid Week day" with the following options(checkbox provided)
1.all week
or
2.Mon to sunday(with individual check boxes)
For this everything right from program,transaction,interface logic need to be taken care which means it requires a lot of development work.(Z txn,Z program,Zidocs etc)
I would suggest you can convey the complexity of the requirement and the amount of effort after consulting with ABAPers and functional consultants.
Hope it helps
Best Regards,
Aram.

IS-Retail: Incorrect pricing by store in WP_PLU

Dear experts,
I have a problem at Tcode WPMA (prog. RWDPOSAN), at prices, when transferring materials to POS interface (Idoc WP_PLU).
We need to maintain different prices for some specific stores. We do it in VKP0 condition in A071 table condition. But when executing WPMA for a store range with different prices, in IDoc WP_PLU the same price is assigned for every store. If we execute it store by store individually, prices are correct.
Is it a customizing problem? Do we have to execute WPMA for each store individually to make it work properly or is it a program bug? (I couldn't find anything at SAP notes).
Thanks very much in advance.
Maite.

Definitely it's not a customizing problem. I did an initialization with Tcode WPMI and prices for these stores where correct. There must be some bug at manual selection in WPMA. Someone is facing the same problem?

Activating Pricing for Sales Order in Retail

Hi All/Vijay/KK,
Please tell me how activate the pricing for sales order, actually in SD we do Pricing Determination, what has to be done for Retail pricing

Hi,
To do sales order pricing
Goto IMG>Sales & Distribution>Basic Functions>Pricing>Pricing Control
Either Follow Standard, condition type PR00
or in case of Custom
1. Use condition table 406 Site/article
2. Define Access Sequences ZPR0
Enter accesses:10 406 Site/article Exclusive x
3. Define Condition Types (ZPR0 assign newly defined access sequence)
4. Define And Assign Pricing Procedures (assign condition types ZPR0..etc. to it)
Then maintain condition record , go to VK11 --> Enter your Z condition type (eg. ZPR0)., enter the amounts.
Add the pricing procedure , to sales document type.
For Retail Sales Pricing
For Retail Sales Pricing based on Purchase pricing you can follow the following method:
The retail price is always based on the purchase net/net price. This purchase net price is built up from the purchasing pricing elements or condition types defined to be included in the purchase net price. A planned mark-up is applied to the purchase net/net to calculate the proposed retail price. The planned mark-up can be set by merchandise category and for exceptions, more specifically by article.
You can perform Two-step calculation for retail pricing, for example, for stores that are supplied by a distribution center (internal vendor). Calculating sales prices for the stores is based on the transfer price for distribution centers (preceding organizational unit).
1. Set up Master Data (WB02) - Relevant Fields should be maintained
2. Set up Article Master Data - Logistics DC and Store View (MM42)
Relevant Fields should be maintained
3. Maintain Mark up for DC(VK11) -Markup % at Distribution channel distribution chain level
Mark ups maintained at two levels:
For DC: At distribution chain level
Condition type used: AUFS
For Stores: At article level
New condition type ZUFS created.
4. Maintain Mark up for Stores (VK11) Markup % at Store distribution chain level
5 Create Pricing Procedures (IMG) -Pricing Procedures created
6. Carry out Price calculation for DC(VKP5) - Pricing Document created - DC Transfer price calculated
7. Carry out Price calculation for Stores (VKP5) - Pricing Document created - Final Retail Price Calculated
The final retail price that is calculated is stored in the condition type VKP0.
Hope it helps,
Regards,
Anirban Roy

Maintaining Price Record for Different Stores and Distribution Centers

Hi expert
I want to maintain price condition record for condition type ZPR0 for one article
for different store and different Distribution Center
what is t.code and path
if sales price should copy from purchase price what are setting
thanks

Hi Hanumant,
To do sales pricing
Goto IMG>Sales & Distribution>Basic Functions>Pricing>Pricing Control
1. Use condition table 406 Site/article
2. Define Access Sequences ZPR0
    Enter accesses:10 406 Site/article Exclusive x
3. Define Condition Types (ZPR0 assign newly defined access sequence)
4. Define And Assign Pricing Procedures (assign condition types ZPR0..etc. to it)
Then maintain condition record , go to VK11 --> Enter your Z condition type (eg. ZPR0)., enter the amounts.
Add the pricing procedure , to sales document type.
For Retail Sales Pricing based on Purchase pricing you can follow the following method:
The retail price is always based on the purchase net/net price. This purchase net price is built up from the purchasing pricing elements or condition types defined to be included in the purchase net price. A planned mark-up is applied to the purchase net/net to calculate the proposed retail price. The planned mark-up can be set by merchandise category and for exceptions, more specifically by article.
You can perform Two-step calculation for retail pricing, for example, for stores that are supplied by a distribution center (internal vendor). Calculating sales prices for the stores is based on the transfer price for distribution centers (preceding organizational unit).
1. Set up Master Data (WB02) - Relevant Fields should be maintained
2. Set up Article Master Data - Logistics DC and Store View (MM42)
Relevant Fields should be maintained
3. Maintain Mark up for DC(VK11) -Markup % at Distribution channel distribution chain level
Mark ups maintained at two levels:
For DC: At distribution chain level
        Condition type used: AUFS
For Stores: At article level
     New condition type ZUFS created.
4. Maintain Mark up for Stores (VK11) Markup % at Store distribution chain level
5 Create Pricing Procedures (IMG) -Pricing Procedures created
6. Carry out Price calculation for DC(VKP5) - Pricing Document created - DC Transfer price calculated
7. Carry out Price calculation for Stores (VKP5) - Pricing Document created - Final Retail Price Calculated
The final retail price that is calculated is stored in the condition type VKP0.
Hope it helps,
Regards,
Anirban Roy

Upgrade Status Questions

My upgrade status says I'm eligible for an upgrade now and an additional upgrade in May. So does that mean if I upgrade my phone now, I have to renew my contract for two years and then another two years if I upgrade it (like change to another phone) again in May so the total would be 4 years? Is there a time limit to the upgrade discount offer? I don't upgrade it now or in May, when will it expire? I think the second upgrade has an expiration.

I've been told the exact opposite, both on the phone and via email from customer service. That they are not taking away a current upgrade, but after you use it, you will be enrolled in the new plan.
In other words, you get to use the one you have as long as you're enrolled prior to the 16th.
1. All customers who activate / upgrade on a qualifying plan prior to January 16th, 2011 are enrolled in NE2 (New Every 2) and eligible to use the NE2 discount for up to six months from the date they become eligible.
2. Any customer who uses an NE2 credit or Annual Upgrade after January 16, 2011 will no longer be eligible for either program. On March 6, 2011, VZW systems will be updated to reflect this.
3. All customers who exercise the NE2 or Annual Upgrade option on or after January 16th will receive a letter notifying them that it was their last NE2 or Annual Upgrade.
4. Business customers continue to receive either the two-year corporate matrix tiered device pricing or two-year retail device pricing per contract.
5. Customers will now be eligible for promotional pricing after 20 months on a 2-year contract and 10 months on a 1-year contract.

Pricing in SAP Retail: Basic Purchase Price in UOM for the VKP5

Dear Community,
We need that in the SAP Retail pricing (VKP5 transaction), the Basic Purchase Price can be transferred to condition record for PB00 in the Purchase Order Unit of Measure instead of Sales Unit of Measure.
Thanks in advance for your help,
Gabriela Ramirez.

Dear Community,
We need that in the SAP Retail pricing (VKP5 transaction), the Basic Purchase Price can be transferred to condition record for PB00 in the Purchase Order Unit of Measure instead of Sales Unit of Measure.
Thanks in advance for your help,
Gabriela Ramirez.

Free Issue - condition in purchasing pricing & GRN - IS-Retail

I am having following scenario in IS-Retail.
Whenever my client is purchasing articles, he is getting some free issue materials also from vendor alongwith actual po qty.
Say, if he is ordering 100 Boxes of Tiles, he is getting 10 boxes free from vendor. So total qty is 110 Boxes against PO qty 100 Boxes.
Stock needs to be updated thru' GRN as 110 Boxes whereas value need to be considered for 100 Boxes in same PO.
Client is not ready to go for "FREE ISSUE" PO for this qty 10 Boxes ( Free issue from vendor ) and he wants to track it in the same/actual PO.
How to handle this in IS-Retail in calculation Schema/Pricing Procedure?

Hi,
Go to SPRO > Materials Management > Purchasing > Discount in Kind (Discount in Form of Bonus Goods) > Perform following steps;
Maintain Discount-in-Kind Dependencies (Cond. Table)
> Field Catalog
> Create Free Goods Tables
> Display Free Goods Tables
Define Access Sequence And Discount-in-Kind Types
> Maintain Access Sequence
> Define Free Goods Types
Define And Assign Discount-in-Kind Schema
> Maintain Free Goods Schema
> Determine Free Goods Schema
XK02 - Under "Purchasing" Data of Vendor, activate "Grant discount in kind" field.
MM02 - Under "Purchasing" view of Material, specify indicator "2" for field "Qual.f.FreeGoodsDis."
Now Go to Purchase Info Record (ME11/ME12), under "Conditions" Tab, click on "Free Goods" Button (Ctrl+F1), and click on "EXCLUSIVE" button and maintain condition record for material, if Qty is 100 then 10 is fre of same material.
Now create PO for 100 qty, it will add a new line item of additional 10 qty auto with free indicator.

IS-Retail EAN based pricing

Hi!
Could somebody suggest me the process to configure EAN based retail pricing in IS-RETAIL system(ECC 5.0) as the business requirement.Currently the system has been configured on article basis.
Genuine help will be rewarded.
kind regards.
Little Angle

Hi,
Pl go to TCode <b>VK11</b> and choose combination
<b>EAN PER SITE</b> Fill up the details viz., Sales Orgn,Dist Channel,ite,Article,EAN
If this solution helps pl acknowledge.
Regards,
Mani

Pricing list - Retail

Hi all,
For pricelist pricing i have maintained the following settings,
WB02 merchandise catagory level pricelist is activated
Maintained PB00 pricelist condition record(Sales org/dc/pricelist condition table)
Basic data retail(IMG) Distribution chain level pricelist price is activated
Maintained Pricing type determination for price list
Maintained control data pricing table data backup maintained the relevant condition table which is maintained for the PB00.
*Error is:* "No basic purchase price relevant to pricing found with schema RMISR0"
Please let me know where i am going wrong for the pricelist pricing to solve the above
Regards,
Kumaravel

Hi ,
In IS-Retail Sales Price calculation is happening from your Purchase Price. There is a link between Purchase Pricing Procedure and Sales Pricing Procedure.
For your Purchase Pricing Procedure refer RMISRO (TCode M/08)and for every purchase condition type which will affect your Sales Price tick Relevant to Pricing under Tab Sales Pricing.
For Sales Pricing Procedure refer the following link:
http://help.sap.com/bp_bblibrary/600/html/R12_EN_DE.htm
Regards
CSM Reddy

IS-Retail:1 step pricing

Hi All,
         Can anyone explain me what is 1 step pricing.in IS-Retail.tell me with full details the IMG and Easy Access settings.and any other settings required.Explain me clearly.
reply soooooon
Thanks
mahi

Hi Mahi
Single Step Pricing is arriving Retail Price from "Vendor" to "Store" or "DC"
Two Step Pricing is Arriving Retail Price from "Vendor " to "DC" First & from "DC" to " Store"
1. One Step - Purchase Price + markup = Sales Price
2. Two Step - Purchase Price + markup1 = Sales Price ( DC )
                    Sales Price (DC) (Transfer price to Store ) + markup2 = Final Sales Price retail
Follow the steps for Cuatomization
1     Define Schema Group: Purchasing Organizations
IMG - Materials Management - Purchasing - Conditions - Define Price Determination Process - Define Schema Group -Schema Groups for Purchasing Organizations - Maintain say X
2.        Define Schema Group: Vendor
IMG - Materials Management - Purchasing - Conditions - Define Price Determination Process - Define Schema Group -Schema Groups for Vendor - Maintain say Y
3.      Assignment of Schema Group to Purchasing Organization
IMG - Materials Management - Purchasing- Conditions - Define Price Determination Process - Define Schema Group - Assignment of Schema Group to Purchasing Organization
Assign PO to X
4. ASSIGN CALC. SCHEME TO PURCHASING ORG.
IMG - Materials Management - Purchasing  Conditions - Define Price Determination Process - Define Schema Determination-Assignment of Calculation Schema to Purch. Org
Assign Schema Group PO ( X )& Schema Group Vendor (Y) to RMISR0 ( Purchase calculation schema )
5. T.code XK02 - Assign Schema Group Vendor Y on Purchasing Tab
6.      Maintain Pricing Type
IMG - Logistics - General - Retail Pricing - Sales Price Calculation - Maintain Pricing Type
Maintain Pricing Type .say .X001 - Retail , X002 - DC, X003 - Whole Sale and maintain Sales pr. schema ( WWS001, WWS002 & WWS003 Respectively ),Doc. creation,Pricing doc. type,Data held,Pricing crcy and Exch. Rate typ
7.Define Price List Categories for Customers
IMG - Sales and Distribution - Basic Functions - Pricing - Maintain Price-Relevant Master Data Fields - Define Price List Categories for Customers
Maintain Price List .Say P1
8. Assign Pricing Type/Reference Site to Organizational Level
IMG - Logistics - General - Retail Pricing - Sales Price Calculation - Assign Pricing Type/Reference Site to Organizational Level
Assign "Retail Distribution Chain " to "Pricing Type" X001 to Reference retail Site
Assign "DC Distribution Chain " to "Pricing Type" X002 to Reference DC Site
Assign "Wholesale Distribution Chain " to "Pricing Type" X003 to Reference DC Site
Also Assign "Whole Distribution Chain " to "Pricing Type" X003 with "Price List" P1 to Reference retail Site
9. Define List Variants for Pricing
IMG Logistics - General - Retail Pricing - Sales Price Calculation - Define List Variant and Assign Items
Maintain List variant Say.01 ..Save it and assign Items ( List fields ) like LIFNR,WAERSL,EKPGR,HWAER,EKPNN,AUFSG,PAUFS,VKPBR,VORPR,ENDPR,SPABR,ENDPA & SPABA
You can see this List filed in VKP5 Transaction
10. Control Data for Pricing Table and Data Backup
IMG - Logistics - General - Retail Pricing - Sales Price Calculation - Control Data for Pricing Table and Data Back - Control per Sales Price Calculation Schema and List Field
Here assign the "List Field to the Calculation Schema here
11.      Assignment of Condition Tables
IMG - Logistics - General - Retail Pricing - Sales Price Calculation - Control Data for Pricing Table and Data Back - Assignment of Condition Tables
Sales pr. schema     Appl.     Condition type     Pricing level     Table
WWS001     M     PA00     01     18
WWS001     M     PA00     02     17
WWS001     M     PB00     01     18
WWS001     M     PB00     02     17
WWS001     V     VKA0     01     73
WWS001     V     VKA0     02     71
WWS001     V     VKP0     01     73
WWS001     V     VKP0     02     71
WWS001     V     VKP0     03     6
WWS002     M     PA00     01     18
WWS002     M     PA00                                  02     17
WWS002     M     PB00     01     18
WWS002     M     PB00     02     17
WWS002     V     VKA0     01     73
WWS002     V     VKA0     02     71
WWS002     V     VKP2     01     73
WWS002     V     VKP2                                  02     71
WWS003     M     PA00     01                                  18
WWS003     M     PA00     02                                  17
WWS003     M     PB00     01                                  18
WWS003     M     PB00     02                                  17
WWS003     V     PR00     01                                  304
WWS003     V     PR00     03                                  306
WWS003     V     PRA0     01                                 4
WWS003     V     PRA0                                 03     6
Assign like above
12.      Assign Sales Price Calculation Schemas to Distribution Chains
T.code OVKKAssign Sales Area ( Retail ), Customer PP , document PP to the Pricuing Procedure VKP002 - Condition Type VKP2
Assign Sales Area ( DC ), Customer PP , document PP to the Pricuing Procedure VKP001 - Condition Type VKP0
Assign Sales Area ( Wholesale), Customer PP , document PP to the Pricuing Procedure VKP003 - Condition Type PR00
Assign as per your requirement of Conditions
Now you price will flow from RMISR0 to WWS00.. to VKP00...
13.Go to VK11 -Maintain Markup Condition AUFS for Distribution Chain.
14. Create Article MM41 ..Enter Purchase price , Sales Price will flow automatically ..Save it
15. Go to VKP5 , enter article , Distibution chain & site , you can see One Step , Two Step Prices.
Regards
Anis

Pricing issues in IS-Retail

Hai guys,
ECC 6.0 (IS-Retail)
In the same client we have created two different org structures for demo purpose. The articles created in the first one (say 9000) is working fine in respect to Pricing. The prices we maintain in the various orgn levels in the Article Master is flowing into the SO/PO docs fine. But articles of another another org. in the same client (say 4000) behave differently whereas the prices are not flowing into documents. We have to create individual records for VKP2, AUFS and other condition types to get the documents working.
The IMG settings have been checked again and again and found very similiar to finely working 9000.
Can somebody suggest me where we could have gone wrong?
Regards,
Maheshwaran. I

wrong question

Retail MM Pricing

Similar Messages

Maybe you are looking for