Outbound idoc stuck in que

[Former Member]

Hi All,

we are sending outbound idocs from shipment documents in ECC. The issue is the idoc is  successfully processed (green ). But it does not reach PI.

for one shipment, we trigerred one outbound idoc but  when we see in SMQ1 for que SAP_ALE_EDIQUEUE  .we find 10 entries  with one entry at 14.20 saying an idoc exception ocured in pink.

the other nine entries shows that the transaction is recorded (all the nine entries have time 14.21 ). my questions are

1) what is SMq1. what it shows.

2) why there are ten entries shown for one outbound idoc from ECC.

3) Any reason why it is getting stucked. The above issue does not happen every time. only sometimes the idoc stuck.

4) in partner profile, we have "trigger immedtiately option " selected.

5) in the que entries in SMQ1, the FN name shown is "idoc inbound asynchronous". Our abap team  put a break point in this FM and try to trigger another idoc for same shipment but the system is not going into the FM ?

regards

Pamela

[Former Member]

Hi,

As QRFC is being used, If one of the request gets struck in the Q then the later ones for the same messages will not be processed and move out.

The message can be due to an error in the setting either in PI or in ECC. Lets say if there are any custom segments in the extended IDoc type and if those are not in release status, then it can get struck in Q. Ask your PI counter part to check if any log has been created in their system and try to reactivate the settings.

Also try to reprocess the error record and click F6 (Execute LUW). If not reprocessed successfully and if you are not checking in Production system, then delete the entry and then try to process the other requests.

Because of the settings in partner profile (controlled by packet size parameter), it can be 1 Q request for 1 IDoc creation, or 1 request for multiple IDoc's, you might me seeing 10 separate requests in Q.

For each request you can find the corresponding IDoc number by double clicking on each Q entry.

Regards,

Dwaraka

[Former Member]

Hi Dwaraka, thanks for the reply.iam functional and so these questions

Iam confused by your below statement.

1 ) "If one of the request gets struck in the Q then the later ones for the same messages will not be processed and move out ".....What does it mean ? does this mean that for every outbound idoc there will be one request in que.  Then if another idoc for the same shipment document is sent , then that will aslo stuck in the que ? is this what you mean,

or do you mean that if another idoc is trigrred from another shipment B and since an existing idoc from some  other shipment document A is already stuck up, the   request from idoc for shipment B will also get stuck up ?

2) we do not have extended idoc segments. Further is it normal to have idoc's stuck in que. If yes, then our intergration will suffer with external application.

3) is it possible for abap team to debug the reason of errors in que ?

4) Why ques are required. what they do ? do we also have inbound ques and what for ?

regards

Pamela

[nabheetscn]

What is the status of the struck entry and what message does it show. Please add a screen shot

[Former Member]

This message was moderated.