Our data loading software runs in the background, with each particular run set as a separate batch. It doesn't matter if this data comes from a program generated on site, or via a data feed interfaced from another system. With the transaction, SM35, I can look at each run and know immediately if any entry within that run did not post correctly, as well as those that did. I can view each transaction and get a detailed log on all that happened. If an entry failed to post, I can see exactly where within the posting process the transaction failed and why it failed. When we have a problem with a new - or recently changed, interface, SM35 is the tool I use to debug the problem fast. Another benefit of this batch input session is when a user tells me her/his interface failed. Often it didn't; someone just ran off with their interface report. In those cases, I don't have to restore & re-run anything. I just reprint the run to the relief - and gratitude, of the user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.