Friday, September 07, 2007

Tips for Searching Trace Logs

Application data: Start at the bottom.  Search up for "|  DM:"
Outbound EDI: Search down from the top for "errcode (number)"
Inbound EDI: Start at the top.  Search down for "Error# "

Other trace log items to look for:
Map Component filename or data model name
"ARRAY VAL"
"get_source"
"put_target"
"VALUE STACK" or "vstk"
Last error at the bottom of the trace log.

Wednesday, September 05, 2007

Look for VAR->OTTmpErr or OTCodeErr in the trace to find out if there are any errors

Look for VAR->OTTmpErr or ARRAY->OTCodeErr  in the trace log to find out if there are any errors during the translations when the get_source and put_target doesn't find the maps that should be called and doesn't produce the output.
For example when the trading partner doesn't exist in the Trade Partner Database, one would get a 303 error in variable VAR->OTTmpErr.