Message Scheduled on Outbound side

[former_member194677]

Hi,

I am working on scenario file->XI->SAP R/3(Using RFC). I am getting outbound status as "Message Scheduled on Outbound side". Instead of the target (check) flag there is a green flag in the column outbound status. The queue is registered, following messages were processed successfully. QRFC-Monitor is empty.

I tried for all the options which is given in Forum.

Messages for other scenarios are working fine, I mean BPM for other scenario are able to receive the messages from both the side but in my scenario BPM is not able receive the messages.

Please let me know for any possibility.

[bhavesh_kantilal · Accepted solution]

Hi,

Check if there is any dump in SM58 in XI?

Check if the RFC destination is working find in Sm 59 . Try a test connection and remote log on.

Check if the R3 system is up and running.

Regards,

Bhavesh

[former_member194677 · Accepted solution]

There is no Dump in SM58,The R/3 system is up and running and RFC destination is also working fine.

The message are getting strucked in the first step i.e. from FILE to XI (BPM).

[bhavesh_kantilal · Accepted solution]

Hi,

Looks like the problem is due to the fact that Queue's have not been registered on XI.

Make sure queues are registered in SMQ2.

Regards,

Bhavesh

[Former Member · Accepted solution]

Hi,

In the first step means, the receive step of BPM is picking the file but nothing is happening after that.

Is your other BPM scenarios working fine. If there are lot of work items some BPM scenario might not work. Check that and try after deleting some work items.

Can u see any error in the PE monitoring??

Regards,

P.Venkat

[former_member194677 · Accepted solution]

The receive step in the BPM is not picking the message.

Our other BPM scenarios are working fine. The message is getting strucked before the message comes inside the BPM.

I am not able to see PE monitoring. It is showing “qRFC Monitor(Inbound Queue)” when we click PE.

[bhavesh_kantilal · Accepted solution]

Santhosh,

Double click on your message in MONI and see if there is any error or some message ?

Check if the receievr determiantion is valid and activated?

Check the status of your BPM in SXI_CACHE. It should be 0.

Regards,

Bhavesh

[Former Member · Accepted solution]

Hi,

Also check that the input file given has the structure of the message type thst is expected by the BPM.

make sure that your file gets picked by the BPM fiest. Only two reasons for this,

Mismatch of input file and mesaage type or Communication channel or some configuration missing.

Regards,

P.Venkat

[Shabarish_Nair · Accepted solution]

hi santhosh,

your message flow is failing at the point where BPM comes into play. Are your sure your BPM is error free? Can you do a F7 check in your BPM to ensure that. Also verify if your BPM is active in the cache. In SXI_CACHE, check your BPM and maybe forcefully activate the same. Ref this blog to know more - /people/krishna.moorthyp/blog/2005/11/28/inactive-integration-process-ip-at-run-time

ShaBZ~~

[former_member194677 · Accepted solution]

Hi,

Queue’s have been already registered and activated. BPM is error free and F7 check is giving information message .The Return code in SXI_CACHE is 0.

[former_member194677 · Accepted solution]

Hi,

Messages schedule for outbound processing.and In SXMB_MONI there is no QueueID only PACKAGE is there.

waiting for valueable inputs.

Thanks

Santosh

[Former Member · Accepted solution]

Hi Santosh,

I think you have done the packaging. Can you please check the IDXP transaction and mention the job id and other details.

Thanks and Regards,

Chirag Gohil.

[former_member194677 · Accepted solution]

Hi Chirag,

Thanks for the reply.

I can see now the messages for packages in IDXP transaction.

Could you let please let me know what needs to done..to proccess the messages

Thanks

Santosh

[Former Member · Accepted solution]

Hi,

What you need to do is select that message and there is a button at the top process message.

So what it will do is it will process that message and then you can see that message been processed in SXMB_MONI with checked flag.

Thanks and Regards,

Chirag Gohil.

[former_member194677 · Accepted solution]

Hi Chirag,

I have selected message individually and tried to process it but the messages are still in package.

Your valueable inputs will be appreciated.

Thanks

Santosh

[Former Member]

It seems simply that it's a problem with the Transactional RFC. You would get this for a number of reasons but could be that your SM59 destination is not correct or there was a problem with the Server at the time of posting to R/3.

Check this via SM58. If you see your transactions in this queue there will be an message in the Status Text and if you have ensured that your SM59 destination are ok then simply execute the entry ...Select the line and select F6 Execute LUW.

[Former Member]

Hi,

1. Is the receive step in the BPM, configured to start the process?

Make sure that the receive step has the "start process" check box ticked in its properties.

2. Also recheck, if the abstract interface mentioned at the receive step represents the message that is expected to be received from the file.

Regards,

Smitha.

[former_member194677]

Hi,

The points which you have mentioned are ok,we have already configured the BPM as you said.appreciate your further idea's.

[Former Member]

Hi,

Is there a PE entry corresponding to your message in the monitor?

When the PE link is clicked, are you taken to the workflow log?

In case, the workflow log is not being displayed, it means that an instance for the BPM is not being created.

Regards,

Smitha.

[former_member194677]

Hi,

when we clicked on PE we are not able to see workflow log and its showing in QRFC monitor (Inbound Queue) empty.

As you said as there is no instance of BPM created can you please let us know how can we proceed further .....

Appreciate your help in regard......

[Former Member]

Hi,

Just to recheck:

Corresponding to your message in the monitor, check the queue name. There would be a queue name followed by a space, and then a number.

In case you have only the queue name, that means, the BPM is not instantiated.

Whenever a BPM is not instantiated, the message, remains in the queue. So you should be able to see it in the queue. In case, you cannot find the msg in the queue, it means, the message has been deleted.

Try retriggering your interface, with a new message.

In case, you are using correlations in the BPM, make sure, that the message being triggered satisfies this correlation.

Regards,

Smitha.