Reg: On System outage Interface doesnot execute

[Former Member]

hi Experts ,

your suggestions are important here.

As per the requirement we have built an interface to send SAP-R/3 data to third party system. Now the interface executes as a daily Job (Daily execution) .

We are just pondering on the fact that if any of the day there is a system outage then do we need to handle that situation while developing the interface at the technical level...

Or is it like the day there is a system outage there is no need to send across the master data (Cost Centers and Project Codesi.e WBS Elements) to third party system. The interface will get executed for the next possible day.

Which amongst the above approach will be suggestible ?

Any suggestions will be beneficial in our process of understanding.

thanks

Kylietisha

[Former Member]

How could anybody except you, your management and the third party possibly answer this question for you??

Rob

[brad_bohn]

It's up to you as to how you want to handle it - you have to make the decision. There is a 'no start after' option on the job definition. If you have a system outage during a timeframe when a job is scheduled to run, the job will start once the system is restored unless you have set that option.

[Former Member]

Let me summarize your question

You are sending Master data on daily basis to third party system. What happens to changes that incur to master data if system is down?

If that is your question, then create parameter in TVARVC table with parameter say MASTER_LAST_EXEC_DATE and update the value with last execution timestamp. When the program is process read the timestamp from the parameter and pick the changes from that timestamp onwards.

[Former Member]

please ignore this post,

thanks for your replies