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
Showing results for 
Search instead for 
Did you mean: 

Process SM35 Session without intervention

arulpugazh
Explorer
0 Kudos

We have a number of jobs scheduled in background that usually involve posting thousands of records. SM35 session is created for erroneous records and most of them are just informational messages (not "Errors"). We are currently processing these sessions in "Display Errors Only" mode and then post them manually. While this is manageable for small batches, it is not feasible for large data (sometimes we have about 20000 screens) to process manually.

Is there any way to process the records automatically, even when there are informational messages?

Note: I am not a developer, so don't have access to create/edit programs.

1 ACCEPTED SOLUTION

Sandra_Rossi
Active Contributor

Sorry, but you have to ask a developer. First, analyze the reasons of these errors, tell the developer what the issues are (with test data to reproduce), and the developer will do the changes to reduce.

Eventually, if that's really too much work, and the errors are always manually corrected the same way and not too much complicate, a temporary bizarre solution could be to make "a batch input program to correct batch input" : it would list the erroneous batch inputs, allow grouping them on some criteria (screen number, message number, etc.), and apply a given sequence of actions (enter them in an editable table, with the type BDCDATA "batch input data"), for every group of batch inputs.

2 REPLIES 2

Sandra_Rossi
Active Contributor

Sorry, but you have to ask a developer. First, analyze the reasons of these errors, tell the developer what the issues are (with test data to reproduce), and the developer will do the changes to reduce.

Eventually, if that's really too much work, and the errors are always manually corrected the same way and not too much complicate, a temporary bizarre solution could be to make "a batch input program to correct batch input" : it would list the erroneous batch inputs, allow grouping them on some criteria (screen number, message number, etc.), and apply a given sequence of actions (enter them in an editable table, with the type BDCDATA "batch input data"), for every group of batch inputs.

Thanks for the suggestion. While your solution should be the permanent one, we couldn't dedicate time for it and decided to automate the process via UFT.