It is a fact, that the tendering error messages we get are not precise and don’t really explain the problem. In many of the TM systems, F1 help doesn’t work properly on the web browser. To understand the problem was a big nightmare for me, until I found this, thought to share here and make life easier for similar people out there.

1) In TM system – go to transaction SAAB

2) Enter checkpoint group “/SCMTMS/TEND_LOG” & Press “activate”

3) Switch to tab “Activation” & Press button “server”

4) Double click global settings, a window will pop up. In the popup, match the settings as in below screenshot:

5) Once you match the above settings, save the checkpoint group. There will be a popup asking maximum validity period of the activation, set a suitable end date for the activation (I don’t recommended to activate the logging longer than required, it might be sufficient to activate the log for a couple of days)

This setups the log. Now to view the log follow below steps:

1) Once the log is active, whenever an error or unexpected situation occurs in the tendering process it is logged in keys(as shown below). If you want to look up a specific instance log then copy the key highlighted below and go to step 2 or else go to step 2 ignoring the copying of key.

2) In TM – box go to transaction SE38. Execute report /SCMTMS/DISPLAY_LOG

3) If you have copied the key in step 1, insert it in the yellow marked fields below, else keep them blank and execute.

4) The log details will provide (1) The callstack of the running program at the point in time when the error or unexpected situation

occured (2) Context information, which is created at the point in time when the error or unexpected situation occured

5) You can also see the error message numbers like “/SCMTMS/TEND175” – to get further information on this, you can go to SE91, enter “/SCMTMS/TEND” as message class and hit display

5) You now look for the message number, which is last three digits of error message (eg:- for error “/SCMTMS/TEND175”, you should lookup 175)

Once you find the message, and you understand or can figure the problem, well and good. Or else a experienced ABAPer can easily help you now using “Where used” list to trace the problem using breakpoints.

All the best!

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply