Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Old Batch Input Sessions – what is the risk ?

Former Member

‎09-15-2014 2:48 PM

0 Kudos

We have a system that contains some old Batch Input sessions, that have not been processed.

Looking in SM35 I find sessions with status New, Errors, In processing, In Background or Creating. Some of the sessions are locked, but most of them are unlocked.

I would appreciate your help to answer the below questions:

1)  What is the risk of having these old Batch Input Sessions ?

2) What is the best approach to mitigate the risk ?

3) What is best practice for governance of Batch Input ?

1 REPLY 1

MartinMaruskin
Active Contributor

‎09-15-2014 4:31 PM

0 Kudos

Hi Peter,

keeping those old batch input session in the system is

1/ risk because some one can process them and maybe they are already not needed. So it may cause you inconsistency in your system.

2/ Best approach is to go session by session contact responsible user/requestor from business of the data and ask him what shall be done with it.

3/ From governance point of view an organization should have an rule in place (kind of house keeping task) that those batch input session are reviewed on regular basis and appropriate task is taken within reasonable time frame.

cheers

m./