Quantcast
Channel: SCN : Discussion List - SAP for Retail
Viewing all articles
Browse latest Browse all 1380

Triggering Pricing & Promotion data to third party system

$
0
0


Hi SAP Guru´s,

 

Currently we are sending the pricing, promotions & article master data delta load to 3rd party system from SAP ECC via SAP XI through IDOCS using daily scheduled batch jobs. IDOC segment - WP_PLU.

 

Here the issue is the promotion & pricing data are sent to 3rd party system one day before the actual start date.

 

Eg: Promotion 123456 which has start date as 15/05/2014 & ending on 30/05/2014 & was created & activated on 13/05/2014.

 

This promotion 123456 is getting triggered from SAP ECC through batch job on 14/05/2014 morning & 3rd party system receives the data on 14/05/2014 & the promotion are getting activated at 3rd party system end on 14/05/2014 itself which actually gets active from 15/05/2014.

 

Same in the case for Standard Pricing data which needs to be active from 31/05/2014 once the promotion 123456 ends on 30/05/2014.

 

The standard pricing data gets triggered from SAP ECC on 30/05/2014 through batch job & reaching 3rd party system on 30/05/2014 & getting activate on 30/05/2014 itself.

 

This creates more issues at the store end as well as affecting business.

 

We checked at 3rd party system end & they replied that their system considers the updated time stamp & date to activate the prices & it does not considers the actual active from & active to date. They need the data to be sent from SAP ECC on the effective date of the pricing & promotions.

 

Can any one help me how to change the batch job triggereing date in SAP ECC based on the actual promotion & pricing start date or is there any other process to trigger the data through the batch job on the actual promotion & pricing data activation date.

 

Thanks in Advance.

 

Thanks & Regards,

P.P.Shankar


Viewing all articles
Browse latest Browse all 1380

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>