Troubleshoot Background processing error

jeff-christie

I have a 9.0 customer where I'm seeing a constant error in the background log (file SMXBLF) where it states it calls SMC600 but the next line in the log says an error occurred in SMC600 (I1) and it's for api SyncInv.  SMPUBQ for this customer has many thousands of records in it, has for days now (if not longer) and I think this file should be usually empty or close to it.  I don't see anything in SMERRS.  Any thoughts on how I can troubleshoot what the error is and then I can track down what is causing it.

Thanks, Bob

david-bradford

As a suggestion, without guarantees, the first SMPUBQ record (the one with the lowest sequence #) is holding up what is behind it (those with higher sequence #s) --- field three in SMPUBQ should tell you the key of the SOPINH record that is having a problem. If you pull up that problematic record in UTLOOK (provided it exists - if it does not exist that might be the whole problem), there is an option at the bottom of UTLOOK (once you press enter and get to the end of that SOPINH record) for "XML" - by pressing 'X' and then enter, the UTLOOK code goes into SMC600 to build and display the XML file in a notepad type output (doing just as it would for the background processor but, instead of pushing it through the background processor it builds/displays the XML for review purposes). If the error occurs in SMC600 then you won't get the XML file (but you may be able to see and/or figure out what XML data tag is that is at fault at that moment), and, if unsure/unresolvable at that moment, you can/could delve deeper into the code of UTLOOK, focusing on where it calls SMC600 to dot-step and see what you can see in SMC600 that is failing. See if that is a good place to start researching. Good Luck!