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
Similar Messages
-
User Exit/Badi on save of WAK2(retail promotions))
Hi can anyone please tell me if there is any user exit or badi on save of WAK2 (retail promotions).I tried but i cant see any user exit or badi for same.
Hello
In program SAPMWAKA (tcode WAK2) you will find routine MWAKAF03_CALL_PROMOTION_U in which fm PROMOTION_UPDATE is called.
Within this fm you find at the end the coding:
* BADI Aufruf
PERFORM CALL_BADI_INTERF_PROM_UPD USING FXWAKHD.
ENDFUNCTION.
This routine check for implementation of BAdI WAKT_BADI_001. The BAdI method INTERFACE_PROMOTION_DATA is used to "Make Update Data Available to External Applications".
In addition, you should look through the manyfold BAdIs and enhancement spots within package WAKT.
Regards
Uwe -
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
BrettHi
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 -
Controlling of retail promotion for particlar site/Plant
Hi
I would want to give the promotion only for particular site only , how could i control it ,I have created the Retail promotion and assigned the site group
I have created site group through CL01 and Assigned the charteristic ,
I have created a charteristic for the through CT01 and given value as the particular site or plant
Am i missing any other, when i create sales order, the promotion is applied for the all site .plant in the sales order
Appreciate your timely help
Regards
DineshIf you want only one purchase organisation for the palnts in different company codes,assigne the purchase organisation to plants across the company code and don't assign the porg to company code.
If we assigne the porg to company code then that porg can be used only fof rthat compnay 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 PaulHi 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 -
Sap retail - promotion by email
Hello there,
we need to send promotion announcement through email.
Can anybody advice us how to go about that?
we have implemented note no. 879034.
Best Regards,
ChandanHi Chandan,
As per SAP Note 879034....This functionality is not contained in the standard SAP. To do this, you have to implement the source code corrections, the retail promotion is sent to the email address defined in the site master.
Bye,
Muralidhara -
Campaign Management - Retail Promotion Integration
Hi CRM Gurus,
I am working on a CRM implementation project for a retail company.
They already have SAP IS Retail ECC6. They use the SAP IS retail system to create promotions in SAP.
CRM system will be used for campaign management. The campaigns in CRM need to be linked to promotions in SAP IS Retail.
Any sugessions on how we can achieve this.
Cheers
BarryHi Pratheek,
I am facing same problem, as you have already idea about this issue can u please
help me in solving my problem. Actually i need to add 3 fields(WBS element is
one of them) in standard component CPGOE_DETAILS of CRM. Do i also need
to make some configuration (in campaign) before adding these fields. I don't have much idea about it but i need the solution at earliest. Therefor if could be possible for you then please reply back on my gmail id. [email protected] else you can also reply on this forum.
regards
Subir -
IS Retail: Promotions...what is the idoc..
HI,
would like to know what is the basic data type and message type for WPDREB01.
This is idoc is used to flow promotions data from SAP IS RETAIL to POS.HI,
start Transation WPMA and enter all needed information in the selection-block "Promotions".
We sure that all ALE Customizing(WE20,WE21, SM59,..) is already done !
Regards,
Gordon -
Hello Friends,
I am trying to create a sales promotion that influences in MRP, but I cannot.
I guess I am doing something wrong.
I create the promotion, plan quantities, and follow on activities, but when I execute MD03 it does appear nothing.
Help says that an exception may occur, but I am not succesful.
What is it necessary to get the promotions included in planification?
Thank you very much,
RosanaHi ,
The sales promotion in IS retail is created through T-code WAK1..and the same is send to the POS through outbound Idoc...u can test the same through T-code WPUK..POS simulation
Regards..
Jonk -
Published Folio retail (promote as FREE for only 3 weeks) #IMPORTANT for @Bob
My client want promote a published retail folio for only 3 weeks as free (there is an important fashion event...)
What is the best way to do this?
1) from iTunes Connect? Is it possible to do a variation of inapp purchase cost using Price Schedule?
In this way the folio label in library will shown -- FREE -- for the 3 weeks that i set?
2) unpublish as retail folio and then publish as public/free (after 3 week unpublish as as public/free and publish as retail folio).
NB: in the next months I will have to publish many folios that will be free for 1/2 days and then become retail - what is the best workflow to do this?
Thanks!Yes Bob, the inapp Android work as Apple but with 2 great and bad difference:
1- you can not set price 0 (or free) This is a problem that force me to unpublish retail folio/publish as free and after 7 days republish as retail (this is a very bad and nonsense workflow!).
2- you can not schedule price variation!
Really many thanks. -
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,
HonghaiHi
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 -
WAK1 - SAP retail promotion for a specific variant only.
Hi Retail Experts,
Scenario from the fashion retailer: Run promotion only on a certain variant from a generic article.
Do you know how to create a promotion (WAK1) and enter the variant directly without having to enter the generic article?
Problem: When entering the generic article, all related variants appear in the promotion. To be able to to delete some of the variants not included in the promotion, I have to remove the price reference articel on the variant first.
Greatful to hear if you have found a way around this.
Thank you all in advance.
Regards,
Tove
Edited by: Tove Sangnes on Nov 22, 2010 11:46 AMHi Tove,
Unforunately only by entering the generic article number,you can get the list of attached variants and then you can delete the unwanted ones from the list.
As per SAP error analysis,the diagnosis and procedure are given below
Diagnosis
A variant of a generic material is to be included in the promotion. The generic material is not assigned to the promotion.
A variant of a generic material can only be included in the promotion if the generic material is assigned to the promotion.
Procedure
First assign the generic material to the promotion. When you do this, all the associated variants will be assigned as items.
You can then delete any of the variants of the generic material which are not to be included in the promotion, providing no pricing reference material is entered in the material master for the variant, or the variant itself is entered as a pricing reference material.
Hope it helps
Best Regards,
Aram K. -
Retail promotions - idoc download free goods
Hello,
Regarding promotions it seems the information can flow in several idoc's: WP_PLU, WBBDLD, WPDREB, and eventually others.
In the specific case of free goods promotions I cannot find this information in any of this idoc's.
(the example on WAK* is: for each 5 EAN sale you'll giveaway 1 EAN extra)
Any info on this?
Regards!Thanks a lot Gnana,
To sum up the client needs regarding promotion data download, can you confirm:
- Promo header data (no matter what kind of promotion) - always flows on WPDREB;
- promotional pricing or promotional discount - WP_PLU and WBBDLD (here we use only WP_PLU and I can see promo code on "AKTIONSNR" in pricing condition segment E1WPA04);
- free goods and bonus buy - WPDBBY;
- Cupons are also in WPDBBY?;
Thanks a lot! -
IS Retail, Promo Discounts, KA02, WGRU1
I am trying to set up a promotional discount at Merchandise Category 1 (WGRU1) level. The promotion discount condition (KA02) requires a table containing the field WGRU1 in order to hold the % discount. Even though this field is in the field catalogue, it isn't available when creating the condition table. I tried creating a copy of this field (ZZWGRU1) but there isn't an appropriate user exit to populate this field from the standard one through WAK1. I also looked at the promotion BADI but had the same problem.
Does anyone know how best to resolve this?
Thank you,
Stephen ParsonsHi
Have you tried these 2 standard BADIs using SE18 Transaction ?
WAKT_BADI_001
or
WAKT_BADI_002
Documenatation of BADI - WAKT_BADI_001 -
*</u>
Use
You use this Business Add-In (BAdI) to change how the system responds to customer-specific requirements when you enter new items in the retail promotion.
You can use the following methods: SUGGEST_ITEM_DATA, SUGGEST_STANDARD_SALES_PRICE, SUGGEST_PLANTGROUP_DATA, and INTERFACE_PROMOTION_DATA.
The method, SUGGEST_ITEM_DATA, allows you to preassign item data that is ready to be entered in the promotion processing to customer-specific requirements and to change the standard assignment determined by the system.
The method, SUGGEST_STANDARD_SALES_PRICE, is used to adjust the standard sales price defaulted by the system for customer-specific needs. The method <DS:IO.IF_EX_WAKT_BADI_001 SUGGEST_PLANTGROUP_DATA>SUGGEST_PLANTGROUP_DATA enables you to preassign plant group data ready for input in promotion processing according to customer-specific needs or change the standard assignment determined by the system. The method <DS:IO.IF_EX_WAKT_BADI_001 INTERFACE_PROMOTION_DATA>INTERFACE_PROMOTION_DATA transfers certain data that are due for update within the promotion to external applications or systems.
The methods: SUGGEST_ITEM_DATA and <DS:IO.IF_EX_WAKT_BADI_001 SUGGEST_STANDARD_SALES_PRICE>SUGGEST_STANDARD_SALES_PRICE are called if new items are included in a promotion in transactions WAK1, WAK2 or WAK12, or if a promotion is created with reference to a reference promotion. The method, SUGGEST_STANDARD_SALES_PRICE, is also called in the BAPI methods, Promotion.CreateFromData and Promotion.Change. It is also called if the user allows the system to determine the standard sales price again.
The method SUGGEST_PLANTGROUP_DATA is called if new plant groups are included in the transactions WAK1 or WAK2 or if a promotion is created in reference to a reference promotion. The method is called for all transactions that subsequently call a database change.
The standard procedure is run before the BAdI is called. The results can be changed in the BAdI implementation.
Standard settings
This BAdI is not active in the standard system. In the standard procedure, the system preassigns some of the item data from the header data in the retail promotion. When copying a promotion, selected item data is copied from the reference promotion. The standard sales price is determined in accordance with the settings in Customizing for the promotion type.
Example
You want to preassign the planned sales quantity to a promotion item.
Sample code for BADI - WAKT_BADI_001
method if_ex_wakt_badi_001~interface_promotion_data .
*** SAP implementation ***
data l_s_wsaf_artmast_rem type wsaf_artmast_rem.
data l_s_wsaf_promo_delta type wsaf_promo_delta.
data l_t_wsaf_promo_delta type
standard table of wsaf_promo_delta.
data l_s_d_waled type waled.
data l_s_d_wagud type wagud.
data l_s_x_waled type waled.
data l_s_x_wagud type wagud.
data l_s_db_wagu type wagu.
data l_werks type t001w-werks.
data l_timestampl type timestampl.
data l_datum_min type date.
data l_datum_max type date.
data l_datum_min_1 type date.
data l_datum_min_2 type date.
data l_datum_max_1 type date.
data l_datum_max_2 type date.
* Bei Aufrufen mit Kennzeichen '2' Änderungen an Aktionen
* wird die Delta-Tabelle für Aktionen versorgt ...
if pi_selkz <> '2'.
exit.
endif.
* Löschsätze verarbeiten ...
loop at pi_t_d_waled into l_s_d_waled.
* .. für die Filiale
clear l_s_wsaf_promo_delta.
select single werks from t001w into l_werks
where kunnr = l_s_d_waled-kunnr.
* Prüfung ob Artikel an SAF übertragen wurde ..
select single * from wsaf_artmast_rem into l_s_wsaf_artmast_rem
where werks = l_werks
and matnr = l_s_d_waled-artnr.
if sy-subrc = 0.
* Gültigkeitsdatum bestimmen ..
read table pi_t_d_wagud into l_s_d_wagud
with key clint = l_s_d_waled-clint.
if sy-subrc = 0.
l_datum_min_1 = l_s_d_wagud-avkvo.
l_datum_max_1 = l_s_d_wagud-avkbi.
else.
l_datum_min_1 = '99999999'.
l_datum_max_1 = '00000000'.
endif.
read table pi_t_db_wagu into l_s_db_wagu
with key clint = l_s_d_waled-clint.
if sy-subrc = 0.
l_datum_min_2 = l_s_db_wagu-avkvo.
l_datum_max_2 = l_s_db_wagu-avkbi.
else.
l_datum_min_2 = '99999999'.
l_datum_max_2 = '00000000'.
endif.
if l_datum_min_1 < l_datum_min_2.
l_datum_min = l_datum_min_1.
else.
l_datum_min = l_datum_min_2.
endif.
if l_datum_max_1 > l_datum_max_2.
l_datum_max = l_datum_max_1.
else.
l_datum_max = l_datum_max_2.
endif.
get time stamp field l_timestampl.
* Delta-Satz für Filiale schreiben ..
l_s_wsaf_promo_delta-mandt = sy-mandt.
l_s_wsaf_promo_delta-werks = l_werks.
l_s_wsaf_promo_delta-aktnr = pi_wakhd-aktnr.
l_s_wsaf_promo_delta-matnr = l_s_d_waled-artnr.
l_s_wsaf_promo_delta-timestampl = l_timestampl.
l_s_wsaf_promo_delta-aktyp = pi_wakhd-aktyp.
l_s_wsaf_promo_delta-validfrom = l_datum_min.
l_s_wsaf_promo_delta-validto = l_datum_max.
l_s_wsaf_promo_delta-predictval = '0'.
append l_s_wsaf_promo_delta to l_t_wsaf_promo_delta.
endif.
* .. für das Verteilzentrum
check not l_s_d_waled-vzwrk is initial.
* Prüfung ob Artikel an SAF übertragen wurde ..
select single * from wsaf_artmast_rem into l_s_wsaf_artmast_rem
where werks = l_s_d_waled-vzwrk
and matnr = l_s_d_waled-artnr.
if sy-subrc = 0.
clear l_s_wsaf_promo_delta.
get time stamp field l_timestampl.
* Delta-Satz für Verteilzentrum schreiben ..
l_s_wsaf_promo_delta-mandt = sy-mandt.
l_s_wsaf_promo_delta-werks = l_s_d_waled-vzwrk.
l_s_wsaf_promo_delta-aktnr = pi_wakhd-aktnr.
l_s_wsaf_promo_delta-matnr = l_s_d_waled-artnr.
l_s_wsaf_promo_delta-timestampl = l_timestampl.
l_s_wsaf_promo_delta-aktyp = pi_wakhd-aktyp.
l_s_wsaf_promo_delta-validfrom = pi_wakhd-alivo.
l_s_wsaf_promo_delta-validto = pi_wakhd-alibi.
l_s_wsaf_promo_delta-predictval = '0'.
append l_s_wsaf_promo_delta to l_t_wsaf_promo_delta.
endif.
endloop.
insert wsaf_promo_delta from table l_t_wsaf_promo_delta[].
* Änderungssätze verarbeiten ...
loop at pi_t_x_waled into l_s_x_waled.
check not l_s_x_waled-updkz is initial.
* .. für die Filiale
clear l_s_wsaf_promo_delta.
select single werks from t001w into l_werks
where kunnr = l_s_x_waled-kunnr.
* Prüfung ob Artikel an SAF übertragen wurde ..
select single * from wsaf_artmast_rem into l_s_wsaf_artmast_rem
where werks = l_werks
and matnr = l_s_x_waled-artnr.
if sy-subrc = 0.
* Gültigkeitsdatum bestimmen ..
read table pi_t_x_wagud into l_s_x_wagud
with key clint = l_s_x_waled-clint.
if sy-subrc = 0.
l_datum_min_1 = l_s_x_wagud-avkvo.
l_datum_max_1 = l_s_x_wagud-avkbi.
else.
l_datum_min_1 = '99999999'.
l_datum_max_1 = '00000000'.
endif.
read table pi_t_db_wagu into l_s_db_wagu
with key clint = l_s_x_waled-clint.
if sy-subrc = 0.
l_datum_min_2 = l_s_db_wagu-avkvo.
l_datum_max_2 = l_s_db_wagu-avkbi.
else.
l_datum_min_2 = '99999999'.
l_datum_max_2 = '00000000'.
endif.
if l_datum_min_1 < l_datum_min_2.
l_datum_min = l_datum_min_1.
else.
l_datum_min = l_datum_min_2.
endif.
if l_datum_max_1 > l_datum_max_2.
l_datum_max = l_datum_max_1.
else.
l_datum_max = l_datum_max_2.
endif.
get time stamp field l_timestampl.
* Delta-Satz für Filiale schreiben ..
l_s_wsaf_promo_delta-mandt = sy-mandt.
l_s_wsaf_promo_delta-werks = l_werks.
l_s_wsaf_promo_delta-aktnr = pi_wakhd-aktnr.
l_s_wsaf_promo_delta-matnr = l_s_x_waled-artnr.
l_s_wsaf_promo_delta-timestampl = l_timestampl.
l_s_wsaf_promo_delta-aktyp = pi_wakhd-aktyp.
l_s_wsaf_promo_delta-validfrom = l_datum_min.
l_s_wsaf_promo_delta-validto = l_datum_max.
if l_s_x_waled-updkz = 'U'.
l_s_wsaf_promo_delta-predictval = '0'.
else.
l_s_wsaf_promo_delta-predictval = '1'.
endif.
append l_s_wsaf_promo_delta to l_t_wsaf_promo_delta.
endif.
* .. für das Verteilzentrum
check not l_s_x_waled-vzwrk is initial.
* Prüfung ob Artikel an SAF übertragen wurde ..
select single * from wsaf_artmast_rem into l_s_wsaf_artmast_rem
where werks = l_s_x_waled-vzwrk
and matnr = l_s_x_waled-artnr.
if sy-subrc = 0.
clear l_s_wsaf_promo_delta.
get time stamp field l_timestampl.
* Delta-Satz für Verteilzentrum schreiben ..
l_s_wsaf_promo_delta-mandt = sy-mandt.
l_s_wsaf_promo_delta-werks = l_s_x_waled-vzwrk.
l_s_wsaf_promo_delta-aktnr = pi_wakhd-aktnr.
l_s_wsaf_promo_delta-matnr = l_s_x_waled-artnr.
l_s_wsaf_promo_delta-timestampl = l_timestampl.
l_s_wsaf_promo_delta-aktyp = pi_wakhd-aktyp.
l_s_wsaf_promo_delta-validfrom = pi_wakhd-alivo.
l_s_wsaf_promo_delta-validto = pi_wakhd-alibi.
if l_s_x_waled-updkz = 'U'.
l_s_wsaf_promo_delta-predictval = '0'.
else.
l_s_wsaf_promo_delta-predictval = '1'.
endif.
append l_s_wsaf_promo_delta to l_t_wsaf_promo_delta.
endif.
endloop.
insert wsaf_promo_delta from table l_t_wsaf_promo_delta[].
endmethod.
Hope this will help.
Regards
- Atul -
Promotion Planning Key Figures
Hi,
How many key figures are recommend to support the promotion planning process?
Should I have one key figure for past promotions and another one for future promotions?
Thanks a lotHi,
The key figure Promotions is the sum of costs for promotions that cannot be assigned directly to a product.Technical Name: 0PROMOTIONS.
In a scenario like, if you are comparing two promotions on the promotion planning screen, when you view a single promotion, you can see the various key figures such as promotion history, promotion forecast, promotion stockouts, and released promotion demand for the relevant products. When you compare two promotions, all these key figures are displayed for both promotions.
Some of the typical key figures used in promotion planning are
1) The Key figure with technical name 0CMNUMPRRT determines the number of promotions in which products belonging to a segment are sold.
2) Key Figure: 0RPA_PRMQTY key figure contains the quantity to be assigned from sales for a promotion.
3) Key Figure: 0RT_PRDCAMT key figure describes an absolute amount by which a sales price is reduced as part of a retail promotion
Regards
R. Senthil Mareeswaran.
Maybe you are looking for
-
Will all my files transfer over (or stay) automatically right after upgrading to Yosemite or do I have to backup every single desired program or document? Question is do I HAVE to please if you can answer if its mandatory or not. Not looking for reco
-
I have an iBook G4 and it will not power off. the screen is just black and the sleep light is on. I held down the power button, but this will not switch the laptop off. i removed the battery, and the sleep light went off, but as soon as i put the bat
-
Table REGUH and relation to Payment Details
Hi Forums, I have a task that I am to create an outbound interface that will simulate 'similar' functions as t code f110v. I have found that table REGUH contains much of the 'HEADER' information I require, is there a table that would have the correla
-
Hi, I would like to open a specific Word Document when the user selects this option but I am not able to; I have the 5.1 version of Labview. Earlier I was able to open an Excel File and write execute a macro ... Attached is my VI code for the Word co
-
How can I create my BW system in EP6.0
Hello, I am trying to set up the connection for BW system(BW7.0) in EP6.0 but when I open the object editor 'User Management' I can see 'User Management Path', 'User Management Desc', 'User Management Protocol', 'User Management Hostname' instead of