Inconsistent Purchase Prices in Retail Promotions (transaction WAK1)

Hi guys
I have an issue on my current project whereby purchase prices are not being pulled into the Purchase Price fields in the Retail Promotion correctly. Currently the system pulls Purchase prices as follows
When the user creates Retail Promotions SAP pulls purchase prices as follows.
If a List Price exists and no Deal Price then it doesnu2019t pull anything into the Purchase Price Fields
If a Deal Price exists which has discounts maintained against it SAP pulls the gross Deal price, i.e. it doesnu2019t take off the discounts
If a Deal Price exists without discounts, it pulls this correctly.
If anyone has encountered this before your advise would be warmly received.
Thanks
Brett

Hi
This will work for POS but the actual purchase price pulled into the promotion is still not consistent with the condition record price. What the system does is it looks in the price schema, picks the first condition type (in this case the deal price condition) and just pulls the price from this ignoring any discounts maintained as supplements. If no deal price exists it pulls nothing rather than looking further down the schema and pulling the list price. Anyone know if I can make this work so it acts like pruchasing document pricing, i.e. includes supplements and keeps looking until it finds a condition record

Similar Messages

Adding columns to Fast Entry tab in Promotion transactions (WAK1/2/3)

Hi everyone,
I have a requirement to add additional columns (using custom Z* fields) to the Fast Entry tab from transaction codes WAK1, WAK2 or WAK3. I have tried to search for BADI's that may accomplish this (including those associated with the main program from those tcodes), but with no luck. Does anyone know if something like this can be done at all?
Thanks in advance.

Hi Andrew,
The only way to do this currently is via a small modification to standard code. Of course you will also probably need to include your new fields in your extract to BI for reporting and extend your IDOC if you need to send the extra fields to a POS system.
Hope this helps,
David

WAK1 - Promo with reference - set Purchase Price

Hi,
When we create promotion in WAK1 in SAP Retail, in standard it will choose as Purchase price, lowest price set for entered article.
As we do not like this behaviour, we implemented our own logic using impelemntation for BADI WAKT_BADI_001 in interface SUGGEST_ITEM_DATA.
But now we have a "problem":
when we create promotion with reference to other promotion and want to copy Purchase price set in original promotion (mark in WAK1 Planned Purchase Price (RWAKA-KPLEKP) , it is copied, but then overwriten with our BADI implementation.
And I don't have idea, how and where set, that in case RWAKA-KPLEKP is checked do not run our BADI (if price is copied, we do not need to choose it).
In SUGGEST_ITEM_DATA field RWAKA-KPLEKP is not accessible (checked in debbuging).
Any ideas how to solve it?

Hello
Try to search SCN for EVO
You will find this: PR price in PO

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.

Reg: IS Retail Promotions Confguration

Hi Gurus,
           Could anyone provide useful links for IS- Retail Promotions Configuration apart from SAP Help Library links ?
I need documents for Configuring Retail Promotions Coupons,Bonus Buy and Free Goods for my Client.
Thanks and Regards,
R.K

Hi Ravi
find promotion config doc of IS Retail
2.3     Retail Promotion
2.3.1     Number Ranges, Promotions
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Number Ranges, Promotions
Details of the configuration     Standard Settings Maintained
2.3.2     Promotion Category
Table     V_TWTY, TWTY, TWTYT
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Promotion Category
Details of the configuration     Standard Settings Maintained
2.3.3     Promotion Type
Table     V_TWAA, TWAA, TWAAT, TVKO, TVKOT, TVTW, TVTWT, KNA1, T001W
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Promotion Type
Details of the configuration     Following Promotion Types Created
     BC01     Barista Promotion Type
Select entries & click on Magnifying glass icon
1.     BC01
    Promotion - DC Price
    Following Settings Maintained
     Promotion Category = BC01
     Create SP conditions Activated
     Without Calculation Activated
             Price Activation Type 2 (Site Group)
     List Group A
     List Variant 02
     Cond Group Purch
     Cond Type Group SP BC01
     SP Sales Org
     SP dis Channel
     CondType % Discount KA02
     CondType Abs Discount KA04
     No Range Int assgt 01
     No Range ext assgt AA
     Lead time Purch 10
     Follow-on time Purch 02
     Lead Time Listing 30
     List. Follow Up time 30
     Announcement Lead Time 5
     Lead Time Store Gr 3
     Alloc Table Type 1000
     Announcement Category F
     Message Schema RTBN01
2.3.4     Promotion Themes
Table     V_TWAT, TWAT, TWATT
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Promotion Themes
Details of the configuration     Standard Setttings Made
2.3.5     Control for Condition Tables for Promotion Discount
Table     V_TWREB, TWREB
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Control for Condition Tables for Promotion Discount
Details of the configuration     Settings Made for condition type KA02 & KA04.
ConditionType     Organization Level     Article Disc Lvl     Table
KA02     02     01     4
KA02     02     02     359
KA02     02     03     359
KA02     02     04     359
KA04     02     02     677
KA04     02     03     677
KA04     02     04     677
2.3.6     Promotion Determination in Sales Order Processing
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Promotion Determination in Sales Order Processing
Details of the configuration     No Settings Made.
2.3.7     Condition Type Groups For Promotions in Purchasing
a.     Assign Condition Type/Table to Condition Type Groups
Table     V_T6B2F, T6B2F, T681A, T6B2, T681B, T6B2T
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Condition Type Groups For Promotions in Purchasing  Assign Condition Type/Table to Condition Type Groups
Details of the onfiguration     No Settings made.
b.     Assign Condition Type Groups and Arrangement Types
Table     V_T6BM_ZU, T6B1, T6B1T
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Condition Type Groups For Promotions in Purchasing  Assign Condition Type Groups and Arrangement Types
Details of the configuration     No settings maintained
2.3.8     Condition Type Groups For Promotions In SD
a.     Define Condition Type Groups for Promotions
Table     V_T6B2, T6B2, T6B2T
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Condition Type Groups For Promotions In SD  Define Condition Type Groups for Promotions
Details of the configuration     Standard Settings Maintained
b.     Assign Condition Type/Table to Condition Type Groups
Table     V_T6B2, T6B2, T6B2T
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Condition Type Groups For Promotions In SD  Assign Condition Type/Table to Condition Type Groups
Details of the configuration     Settings maintained for Condition Type Group 0007
Cond Typ Grp     Cond Type Grp     Cntr     CnTy     Condition Type     Number     Table
0007     Promo Conditions 2     10     VKA0     Promo SP        IS-R     6     Price List Type/Currency/Article
0007     Promo Conditions 2     11     VKA0     Promo SP        IS-R     73     Article per SOrg/DstCh
0007     Promo Conditions 2     12     VKA0     Promo SP        IS-R     71     Article per Site
0007     Promo Conditions 2     20     KA03     Promo Discount % 2     71     Article per Site
0007     Promo Conditions 2     21     KA03     Promo Discount % 2     155     Sales Org./Dist. Channel/Price List/
Article/Sales Unit
0007     Promo Conditions 2     22     KA03     Promo Discount % 2     73     Article per SOrg/DstCh
0007     Promo Conditions 2     30     KA05     Promo Discount MD 2     71     Article per Site
0007     Promo Conditions 2     31     KA05     Promo Discount MD 2     155     Sales Org./Dist. Channel/Price List
/Article/Sales Unit
0007     Promo Conditions 2     32     KA05     Promo Discount MD 2     73     Article per SOrg/DstCh
c.     Assign Condition Type Groups and Arrangement Types
Table     V_T6B2, T6B2, T6B2T
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Condition Type Groups For Promotions In SD  Assign Condition Type Groups and Arrangement Types
Details of the configuration     Standard Settings Maintained
2.3.9     Message Determination
a.     Single Messages
1.     Create Condition Table
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Single Messages  Create Condition Table
Details of the configuration     No Settings Maintained
2.     Change Condition Table
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Single Messages  Change Condition Table
Details of the configuration     No Settings Maintained
3.     Display Condition Table
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Single Messages  Display Condition Table
Details of the configuration     No Settings Maintained
4.     Access Sequence
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Single Messages  Access Sequence
Details of the configuration     Standard Settings Maintained
5.     Message Type
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Single Messages  Message Type
Details of the configuration     Standard Settings Maintained
6.     Message Schema
Table     V_T683S_XX, T683S, T683T
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Single Messages  Message Schema
Details of the configuration     Standard Settings Maintained
Select entry & click on Control Data
7.     Assign Schema to Document Type
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Single Messages  Assign Schema to Document Type
Details of the configuration     No Settings Maintained
8.     Assign Program/Form to Message Types
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Single Messages  Assign Program/Form to Message Types
Details of the configuration     No Settings Maintained
9.     Requirements for Message Types
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Single Messages  Requirements for Message Types
Details of the configuration     Standard Settings Maintained
b.     Group Messages
1.     Number Ranges, Group Message
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Group Messages  Number Ranges, Group Message
Details of the configuration     Standard Settings Maintained
2.     Message Type
Table     VN_T685B, T685, T685B, T685T, T682, T682T, TCSTR, TCSTRT, T681Z, T681A, T681B
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Group Messages  Message Type
Details of the configuration     Standard Settings Maintained
3.     Assign Program/Form to Message Types
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Message Determination  Group Messages  Assign Program/Form to Message Types
Details of the configuration     No Settings Maintained
2.3.10     Business Add-In for Promotion
Transaction Code     SPRO
Menu Path     IMG  Logistics - General  Retail Promotion Business Add-In for Promotion
Details of the configuration     No Settings Maintained
Thnaks
Amit Shivhare
PS Reward Point
Edited by: Amit Shivhare on Mar 10, 2008 3:44 PM

Purchase Price Equivalent of VKP2

Hi all,
I was wondering if there is a transaction that displays standard (PB00) and promotional (PA00) purchase prices in a format like transaction VKP2. I can use MEK3 to list the condition records but I can only display the prices one at a time.
I also understand I can view the amount set in the condition records by a combination of A018 and KONP but would like to avoid querying tables.
Regards,
Mondoni

Hi Kaizad,
Thanks but I cannot join table A018 using SQVI, it's not permitted.
I'll have to find another alternative.
Thanks all for the replies.
Regards,
Mondoni

Retail Promotion condition type can be different from VKA0

Dear expert,
You may know that when we create promotion through WAK1 and active price through WAK5, SAP will create condition and store to condition type VKA0.
My question is "Is this condition type VKA0 hard code by SAP, can we have different condition type other than VKA0"?
Here client wants to have different condition type, for example ZKA1, ZKA2 to store different condition for different promotion type / purpose.
Any soluiton or suggestion?
Best Regards,
Honghai

Hi
Please check you customize settings in the IMG under retail sales price calculation.
Spro>logistics general>retail pricing>sales price calculation>control data for pricing table and data backup>control per sales price calc schema and list field
In your schema under list field ENDPR set the condition type for promotion and normal when saving list fields in master conditions.
Don't forget to then maintain the assignment of condition tables for your schema as well.
I hope this works.
Regards

Retail Promotion T-code

Hi Expert,
Can anybody provide me a full cycle T-code and config document for Retail promotions in SAP - SD. I want to know the cycles for making sales order as well as purchase order and how the promotion number can be included in the same.
A full cycle with t-code will be of great help.
Thanks in advance.
Regards,
Uddhab Paul

Hi Uddhab Paul,
I don't have much idea on this, but i can give you some links go through it.
http://www.slideshare.net/arun_bala1/sap-sd-sales-deal-promotion
Few t-code which i know are:
VB25 List of Sales Deals
VB31 Create Promotion
VB32 Change Promotion
VB23 Display Sales Promotion
WEV5 Create pl.retail markup (price list)
Thanks,
Swamy H P

Open Purchase Orders at Retail Value

Hi
I need to show Open Purchase Orders at Retail Value in one of my reports and I am using the key figure - "Open Purchase Orders (Retail Price) - 0RTOPDVSV".
I am using this KF in the cube ZRT_STWK which is part of a multiprovider. Data to this cube is being pulled from 2LIS_03_BF. I couldn't find a probable field in ECC to which I can map the field 0RTOPDVSV in the cube.
Any idea what the likely field could be in ECC which I can map to the key figure 0RTOPDVSV?
Any help is appreicated.
Thank you.
Pavan.

Hi,
To prepare the Open PO report:
Take all the purchase order details from EKKO and EKPO tables by writing a JOIN based on the selection screen paramters:(into ITAB)
Then fetch the related GR and GI data from the table MSEG for each PO Item (using for all entries of ITAB passing EBELn and EBELP to MSEG).
Here based on the movement type you have to consider the GR or GI.
generally for 101 movement types it is fresh GR(goods receipt).
so in this table MSEG you have many entries with different movement types for each PO items, so summing up the correct quanitities(ERFMG) for GR and other s is importants.So from ITAB you know the PO qty for a particular PO and from MSEG you know the qty received(GR QTY), if the both qty's are equal then that order is closed, if bothe qty's are not equal then that order is OPEN.
Fetch the invoice related data from EKBE or RSEG tablse passing EBELN and EBELP fields for them.
GR dat is in MSEG
and Invoice data is in EKBE or RSEG.
Hope this is useful.
regards,
Anji

How to find out what is the purchase price keyed in Initial Quantity

Dear Experts,
The stock valuation is Standard Costing.
Before this, someone else keyed in initial quantity and the purchase price in the Initial Quantities module.
Now when I issued a PO to a vendor (price list tagged with Last Purchase Price), the price shown is different.
How do I find out if the price keyed in initial quantity is correct or not? Any tables I can refer to?
I tried to track from the Inventory Posting List and the smartlink only bring me to the journal entry for the initial quantity posting. I don't have the details like item no., qty, price.\
Thanks in advance.

Hi Joyce,
Go to Inventory->Inventory transactions->Initial Quantities, Inventory Tracking, and Inventory Posting. Open Inventory Posting Tab and select your price list and items if you want or check you can see there Item quantity and old price also price list wise.
Thanks
Sachin

Goods Issues done with Purchase Price and not MAP

I would like to know on the inventory valuation from moving average price (MAP)/ average the inventory value to First In First Out (FIFO) basis.
FIFO basis is where assumption made that inventory being sold is based on first come first serve basis i.e.
For example you have 1 pc of pen valued at RM 1 and then you buy another pen valued at RM 1.50, your total inventory value would be RM 2.50.
In FIFO basis, if you sold 1 pc of pen then the product cost will be RM 1.00 (i.e. purchase price) as it deemed that the first pen make a way first.
However, in MAP basis, if you sold 1 pc of pen, the product cost would be RM 1.25 as it average cost of both pen.
I have tried using the FIFO rules but it will only take the purchase price if the issuance/sales were done within the same posting period as the GR. If I were to make a GI in the current period, it will not take the purchase price but instead it will be MAP. And then there will be concern if the stocks were available across periods.
Really appreciate any ideas that you may be it standard customizing or enhancements required.

Hi
If you want to apply FIFO rules in real-time basis (day to day operation), then my advice is you should use Batch Management and Batch Valuation features in SAP
If you activate Batch Management with Valuation, then every GR will be valuated differently
For example,
GR 1 on July 01, 2011 - 100 pcs @RM1.00 (batch 001)
GR 2 on July 03, 2011 - 100 pcs @RM1.50 (batch 002)
Then there is GI happening, for example :
GI 1 on July 04, 2011 - 10 pcs
In normal circumstances (without Batch Management), SAP will take the MAP (which is RM1.25) as the price of GI
But if you activate Batch Management with valuation, then you need to specify that you will do GI for batch 001, and SAP will take the price of RM1.00 as the GI price
To ensure FIFO principle, you can also use Batch Determination feature, and make SAP to propose the oldest batch when doing GI transaction in MIGO
Hope that helps
rgds

Purchase price variance in subcontracting order

Our customer has the following scenario:
     Purchase account is posted with the value of stock subsequently purchase price variance is a legal account
     Material ledger is active
     Inventories are managed with standard price for each material code
     Latin method management of inventories post stock values on managerial account
In good receipt with a subcontracting order, in case of purchase price variance, legal account of purchase price variance is posted generating a wrong reconciliation between managerial and legal posting.
Example
The subcontractor is a co packer that assembles material A to produce material B
Material A has a standard price of   3
Material B has a standard price of     5
If Co packer fees have a value     of     2 no purchase price variance occurs during good receipt, as a matter of fact :
(Co packing fees) 2 + (Material A) 3 = (Material B) 5
Else if co packer fees have a value of 3 a purchase price variance of 1 occurs and itu2019s posted using transaction key u201CPRDu201D. On FI the following document is posted:
Legenda : L stands for legal account , M stands for managerial account
(L) Co packing Fees                                         3
(L) Invoice to receive                                     3
(L)Purchase price variance                            1
(M) Consumption Material A                           3
(M) Stock Material              A                            3
(M) Stock Material               B                            5
(M) Production Confirmation Material B       6
In this scenario Purchase price variance should be a managerial account, but transaction key is PRD and changing the account would affect every posting.

This is the answer from OSS
Dear Customer,
the system works as designed.
When Material Ledger is activated, price differences are always
generated under the circumstances you have described. The reason is
that when material ledger is activated, price differences must not be
included into the stock changes value, otherwise the system would
not be able to calculate an actual price.
When Material Ledger is activated, the customizing setting
for handling price differences in the subcontracting process has no
effect.
Best regards,
Santiago Lorite
AGS Primary Support, Business Suite & Technology u2013 Logistics

Purchase Price Variances

Hi,
I am new to SAP. What is the best way to look at all the purchase price variances for a whole month?
Thanks

HI,
Use transaction FBL3N and enter the Purchase Price variance GL Account with period for month and execute....
Regards,
Chintan Joshi

Purchase price to have 4 digits after decimal point

Hi Friends,
Would you please help me out with this issue?
The purchase price needs to have 4 digits after the decimal point, because the product/component would be packed and sold in other unit, which may give huge value difference.
The price can be set for the product/component per 100, but is there any setting in SAP Reference IMG?
Thanks for your help.
Regards,
JT

Hi,
In material Master (MM01) which unit you maintain for that material. Go to MM02 and keep Base Unit of Measure as storing unit as earlier and maintain Sales unit (unit of measure in which the material is sold) or Order Unit (Specifies the unit of measure in which the material is ordered) in the Purchase Order according to your requirement and Enter the factor for converting the alternative unit to the base unit. In your case product/component would be packed in a Different unit.
OR
In your case product/component would be packed in a Different unit.
Maintain the (BOM) Bill of Material for the finished product you are selling and its component.Create Finished Product as material type as FERT and Components as material type as HALB or ROH.
Now try your transaction with Finished Product only and sale.
Hope the above will help.
Regards,
Biju K

Purchase price variance

Hi
I want to to drill down the purchase price variance.Say I have PPV of 10K. I want to drill down to details of 10k.How to proceed.What is the transaction code for that?
Thanks in advance.
SN

Hi Satya,
Variances are based around the standard values that are set up in the Material Master file. These standard values represent what it "should" cost to produce (or purchase) a unit of the product. Variances are calculated automatically when settlement jobs are ran in SAP
purchase price variances are caused by a difference between the standard cost in the MM file and the actual price on the purchase order.
The entries will b something like this
Debit Inventory XXXXX
Credit Accounts Payable XXXXX
Credit Price Variance XXXXX
Regards
Genie

Inconsistent Purchase Prices in Retail Promotions (transaction WAK1)

Similar Messages

Maybe you are looking for