12-11-2014 2:36 PM
Dear all,
I need to find out a way to introduce a second sales price for an article in addition to the standard one. This price has to be lower and is needed when a product can be bought with both money and loyalty card points.
Can anyone tell how such a price can be created and transferred via message type WBBDLD? Condition type VKK0 (promo club sales price) is intended to be used for the purpose of buying with loyalty points but I cannot get a second condition type for a sales price transferred.
Any input will be appreciated.
Thank you!
Regards,
Miro
12-11-2014 3:01 PM
Hi Miro,
if I'm not mistaken, for both WP_PLU and WBBDLD the condition type export is managed by the POS outbound profile that is assigned in the store master data.
From my experience with WP_PLU, all conditions that should be exported need to be 1.) defined in the Condition Type Group (SPRO > Sales & Distr. > POS Interface > Outbound > Maintain POS Condition Group) and 2.) present in the POS pricing procedure VKP001.
In default this works prefectly fine for VKP0 / VKA0 combination.
Hope this helps!
Cheers,
Tomas
12-11-2014 3:01 PM
Hi Miro,
if I'm not mistaken, for both WP_PLU and WBBDLD the condition type export is managed by the POS outbound profile that is assigned in the store master data.
From my experience with WP_PLU, all conditions that should be exported need to be 1.) defined in the Condition Type Group (SPRO > Sales & Distr. > POS Interface > Outbound > Maintain POS Condition Group) and 2.) present in the POS pricing procedure VKP001.
In default this works prefectly fine for VKP0 / VKA0 combination.
Hope this helps!
Cheers,
Tomas
12-12-2014 8:41 AM
Hi Tomas,
Thank you for your input!
The above mentioned settings have already been done but it's still impossible to get another sales price transferred. Exceptions are all promotional condition types like VKH0, VKA0 and VKK0 and I presume there is a hard-coded logic for them since their condition class is also Prices.
Regards,
Miro
12-15-2014 2:21 PM
Hi Tomas,
I have found out the problem was the access sequence and, respectively, the condition table. I used A070 (EAN per site) and as soon as I switched to A071 (Article per site), the condition type popped up in the idoc.
I presume the problem is the missing field VRKME (Sales unit) in table A070 which makes no sense in case of setting up a sales price.
Any comment on that?
Thank you!
Regards,
Miro
12-16-2014 8:15 AM
Hi Miro,
as for POS price download in relation to a specific condition table there are few more relevant parameters;
1. Store-dependent prices in A071 indicator on POS outbound profile and especially
2. Condition Types Filter Settings (transaction OWS2) where you can define additional condition types and condition tables; this might be the config that you need to update in order to download additional prices out of the system (irf not already done)
Cheers,
Tomas