Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

SM58

Former Member

‎2006 Oct 10 8:04 PM

0 Likes
791

Hi All,

I have a problem with SM58.

My scenario is like this. we are doing material load using IDOCs. I get inbound from middle ware system and send response as an outbound.

This outbound idoc is sent by running a report that calls master_idoc_distribute which runs whenever inbound idocs are posted in the system and sends an outbound.

When i get 10 inbounds 5 or 6 responses are send back others are struck in the que SM58 with text NOT_SUPPORTED.

First the messages begin saying " TRANSACTION RECORDED",

"TRASACTION EXECUTED" AND "NOT_SUPPORTED" . When i execute these idocs manually they are processed from the que and the middle ware recieves them.I tried the program RSARFCEX, but its not working. Can anyone please explain why this is happening.

Reply
1 REPLY 1
Read only

Former Member

‎2006 Oct 10 11:09 PM

0 Likes
563

Hi Priya,

It is a bit unclear what happens exactly. The cause can be one of three.

(1)

You're IDoc control record is wrongly filled. Here are some rules:

- The IMPORT structure (MASTER_IDOC_CONTROL of type EDIDC) must NOT supply an IDoc number (DOCNUM = empty).

- The field DIRECT must be filled (DIRECT = '1'.).

- The fields starting with SND must NOT be filled.

- RCVPOR must contain the receiverport (as defined in transaction WE20 - Partnerdefinitions).

- RCVPRT must contain the partnertype (also WE20).

- RCVPRN must contain the partner.

- Both fields MESTYP (transaction WE82) and IDOCTP (transaction WE30) must be filled.

- The TABLE COMMUNICATION_IDOC_CONTROL (of type EDIDC) must be empty.

- The TABLE MASTER_IDOC_DATA (of type EDIDD) must contain the outbound IDoc data.

- IMPORTANT: Fill either the HLEVEL correctly OR leave it empty.

(2)

Your ALE layer has not been setup properly. Take a look at the transactions SM59 (RFC Destinations), WE21 (Port definitions) and WE20 (Partner definitions).

From where i'am i cannot see if there is something wrong without having more detailed information.

(3)

Insufficent authorizations for the user that will actually sent the IDoc's.

Further some advice here:

- When trying to resend (or reprocess) IDoc's, try to use transaction WE19 by making a copy. You are then able to see te content of the IDoc and IDoc control and you can modify them on the spot before sending.

- Think about the use of TRFC parameters with your RFC destination in question. Inside transaction SM59 with all types (except HTTP and via ABAP drivers) you can set TRFC options to take over the repeat sending proces in case of an error. Look for that option in the menu under Edit --> tRFC options... (select a destination first). You can set how many times an IDoc will be tried to be sent out, before it actually fails (with an interval time in minutes).

Hope this gives u some clues on what to do.

Regards,

Rob.