I have thousands of entries stuck in the outbound queue of my ERP system everyday. This is due to a failed transaction. SAP Support told me there is a problem with the P.O. associated with this transaction and that it is OK to delete the offending entry. Once that is done the remaining entries in the queue process until the queue is empty. My question is: "How do I identify the PO transaction that is not working correctly so I can fix the root cause of this problem? Can I correlate the TID from the SMQ1 tcode to a PO number in SRM?
The entry below shows the error from SQM1 in the ERP system.
Client User Queue Destination Date Time Status TID
123 Batch QUEUE1 TARGET1 04/10/2015 18:05:19 Exception condition "INVALID_POS" raised. A20915474B805528491F978BD
Host Program
ADBD123 RSM13000
Next is the partial contents of the corresponding short dump in the SRM system
Category ABAP Programming Error
Runtime Errors RAISE_EXCEPTION
ABAP Program SAPLSXAB
Application Component BC-MID-RFC
Short text
Exception condition "INVALID_POS" raised.
Information on where terminated
Termination occurred in the ABAP program "SAPLBBP_PDH_NOTIFY_FOLLOWON" -
"BBP_NOTIFY_FOLLOWON_INBOUND".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 66
of the (Include) program "LBBP_PDH_NOTIFY_FOLLOWONU01".
Source Code Extract
Line SourceCde
36 i_with_itemdata = ' '
37 IMPORTING
38 e_header = ls_po_header.
39 * check for existence and type of PO (extended)
40 IF ls_po_header IS INITIAL
41 OR ls_po_header-be_log_system IS INITIAL.
42 DELETE lt_purch_orders.
43 lv_invalid_pos = gc_yes.
44 CONTINUE.
45 ENDIF.
46
47 ls_document_tab-reqno = <fs_purch_orders>-po_
48 ls_document_tab-logsys = ls_po_header-be_log_s
49 ls_document_tab-core_key = lv_tst.
50 ls_document_tab-doc_type = gc_doc_be_po_call_off
51 ls_document_tab-guid = ls_po_header-guid.
52 ls_document_tab-entrydate = sy-datum.
