Queing of messages in the outbound or inbound queues

Hi to Everybody ,
It will be better if someone can explain how the messages are queued in the Inbound and Outbound side of XI. I would like to know where and how the queueing theory is implimented.
Thanks

Hi,
Check this blog for queue understanding XI Asynchronous Message Processing: Understanding XI Queues -Part I
Thanks!

Similar Messages

SXMB_MONI - Message scheduled on outbound side (no queues)

Hi All,
I currently have a problem on one of our XI systems.
In SXMB_MONI all the process messages have the outbound status of "Message scheduled on outbound side" (green flag). The interface is going into a BPM process.
There is nothing in the QRFC-Monitor or in the tRFC - SM58.
I have already registered all the queues.
The XBQO queue for the BPM processing is not being triggered. This process used to work on this system, but has now stopped.
Any Ideas?
Thanks,
Matthew.

1. check in sxi_cache. the return code of ur IP shud be 0.
2. register q in smq2
3. anylogs seen from PE in moni?
or use from pg 46 for troublkeshooting from below link:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283 -

MB1B transfer posting Idoc/Message type for outbound and inbound

Hello All
Can anyone tell me the idoc/message type for movement type 313 outbound and 315 inbound to SAP. This is for MB1B Enter Transfer Positing.
Thanks
Ricky

Its WMMBXY

In PI 7.1, condition editor does not show the outbound interface structure

Hello,
I am using PI 7.1, I need to use condition whild determing receivers. So I opened the condition editor, then open the expression editor, select XPath instead of Context object. I would expect that the outbound interface structure appears in the box underneath the XPath, so that I can navigate the structure to choose the field I want to use. However nothing appears here. Do you knwo why is that? Or do I need to do anything to bring up the outbound interface structure in the expression editor?
Thanks
Jayson

Hi Jayson,
I had the same problem
the use of context objects and the value help for xpath is available for XI3.0 interfaces in PI 7.10 only. The functionality for "new" interfaces has been implemented in 7.11 only.
you have to use xpath w/o value help.
I have created a context object in one of our 7.10 test systems, and indeed I was unable to use it in a receiver determination unless the service interface pattern is "Stateles (XI 3.0 compatible)". If you were to change the service interface to that pattern, you have to change the operation name unless it is already identical to the interface name. So that may not be an option for you.
It was possible to use the context object in a receiver rule but then I could not activate the receiver determination because the software component version was supposedly unknown. I will check with my PI contacts - please let me know if the change to "XI 3.0" interface would be a possible workaround for you.
Try the steps which I am giving below, although it's a workaround and don't know the exact reason why it is failing.
1. Open your Outbound Message Interface (which you are using in your Receiver Determination) in IR, edit it and change the Interface pattern (which is there just below the category "Outbound") to "Stateless (XI30 - Compatible)" , save it activate it.
2. Follow the same step for your Inbound Message Interface. Change the Interface Pattern from "Sateless" to "Stateless (XI30 - Compatible)" .
3. Go to ID. Remove your Outbound and Inbound Message Interface from their respective Business Service/Comp and add it again.
4. Create your your receiver determination again using the Outbound and Inbound MI you have changed.
5. Open condition editor of your receiver determination.You should be able to see your Message Interface and can choose the XPath.
Thanks,
Raj
Edited by: raj reddy on Jan 21, 2009 5:41 PM

How to make the outbound call in the CCA

HI everyone,
i have opened the CCA URL and they are agents and supervisor.now i want to make the outbound cal to the mobile no inside india.
when i make call i am getting this error "currently unable to reach the phone try again later"
and my port for TCPI bus "8888" is blocked for this reason i am getting this error
can any have the documents how the outbound and inbound cal are configured in the CCA
Please do the needful help
Regards
Laksh

That error means that the call center server thinks that it cant ring the agents phone.
The call center log file should show the cause.

Queue with error in Inbound Queue SMQ2 can not de deleted

Hello,
We did the replication of Materials and Services correctly.
However, in the SMQ2 trx. (inbound Queue in SRM 5), we keep seeing the following queues:
R3AD_ATTRIBUTE
R3AD_CONDITIONS
R3AD_LEDELIVERY
R3AD_OBJCL
These queue have status "SYSFAIL". We want to get rid of these queues but upon deleting them, they keep appearing again the folowing day!
How do we have to proceed?
Thanks for any reply.
Aart

Thanks Dean but it did not work.
The queue´s keep coming back.
The message of the SYSFAIL is now:
SR053 - No mapping function module entered in SMOFSUBTAB
Any clues?
Thanks,
Aart

Inbound queue in APO side

hi,
All R/3 changes are not transfered to APO. It got stuck in SMQ2 in APO side. every time i am manually activating those queues in ready status.
1) Is there any simple way to activate all the queues having status "ready" in single execution.
2) what will be the reason for inbound queue and how to avoid? i able to see only "ready" and "waiting" status queues there is no error

Hi,
Please check the status of the QIN and QOUT scheduler in transaction SMQR/SMQS and see if the destination is registered or not. I am pasting the content of the SAP Help for you quick reference.
Set Up QOUT Scheduler
Use
Queued Remote Function Calls (qRFCs) are used to transfer data between SAP APO and SAP R/3. The QOUT scheduler processes outbound qRFCs (outbound queue).
You complete the following steps in the relevant client in the production system.
You call the QOUT scheduler using transaction SMQS. The destinations to which the outbound qRFCs are to be sent are registered in the QOUT scheduler. As of version 6.20.45 this is done automatically.
The following options exist for a registered destination:
Type
R: The destination is registered, that is, it is started using the QOUT scheduler.
U: The destination is not registered, that is, it is not processed.
N: The destination is not processed using the QOUT scheduler, but is sent at the time of the COMMIT WORK.
Max. Connections: Number of connections that are used to send the qRFCs. The default value is 10 for R/3 connections and 1 for TCP/IP connections.
Max. Runtime: Time that a destination is processed by the QOUT scheduler. The default value is 60 seconds.
The destination NONE means that the qRFCs are processed in the local system and should not be registered up to version 6.20.45, supplement 8 inclusive. As of supplement 9, NONE can be registered and the without tRFC option set.
Requirements
The qRFC configuration must be configured. For more information, see
Set Up QOUT Scheduler
Use
Queued Remote Function Calls (qRFCs) are used to transfer data between SAP APO and SAP R/3. The QOUT scheduler processes outbound qRFCs (outbound queue).
You complete the following steps in the relevant client in the production system.
You call the QOUT scheduler using transaction SMQS. The destinations to which the outbound qRFCs are to be sent are registered in the QOUT scheduler. As of version 6.20.45 this is done automatically.
The following options exist for a registered destination:
Type
R: The destination is registered, that is, it is started using the QOUT scheduler.
U: The destination is not registered, that is, it is not processed.
N: The destination is not processed using the QOUT scheduler, but is sent at the time of the COMMIT WORK.
Max. Connections: Number of connections that are used to send the qRFCs. The default value is 10 for R/3 connections and 1 for TCP/IP connections.
Max. Runtime: Time that a destination is processed by the QOUT scheduler. The default value is 60 seconds.
The destination NONE means that the qRFCs are processed in the local system and should not be registered up to version 6.20.45, supplement 8 inclusive. As of supplement 9, NONE can be registered and the without tRFC option set.
Requirements
The qRFC configuration must be configured. For more information, see
Regards,
Senthilrajan
Edited by: Senthil_APO on Oct 12, 2009 10:54 AM
Edited by: Senthil_APO on Oct 12, 2009 10:55 AM

Creation of Inbound Idoc for the Outbound Idoc in same client

Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
Amar

Example of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear:   g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'.   "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'.              "Direction
* Receiver
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
    g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'.             "Partner type
g_idoc_control_record-rcvpfc = ''.               "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
case sy-sysid.
when 'DE2'.
    g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'.             "Partner type
g_idoc_control_record-sndpfc = ''.               "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam               = 'E1BPACHE09'.
g_edidd-segnum               = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
    exporting
      pi_idoc_control_rec_40              = g_idoc_control_record
*     PI_DO_COMMIT                        = 'X'
*   IMPORTING
*     PE_IDOC_NUMBER                      =
*     PE_ERROR_PRIOR_TO_APPLICATION       =
    tables
      pt_idoc_data_records_40             = g_edidd
    exceptions
      idoc_not_saved                      = 1
      others                              = 2.
if sy-subrc <> 0.
    message id sy-msgid type sy-msgty number sy-msgno
            with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
    in background task as separate unit
    tables
      idoc_control_rec_40 = g_idoc_control_record
      idoc_data_rec_40    = g_edidd.
commit work.
endif.
write: / 'Well done!'.

Messages still stuck in the Inbound queue SMQ2

Hello XI Gurus,
All my messages with "READY" status are still stuck in the inbound queue (smq2) for the last 2 hours...there was no SYSFAIL error messages or scheduled background running. I have to manually go in and executed each of those messages, instead of automatically process it. Could someone please tell me how to troubleshoot this?
Thanks so much in advanced,
Dng

Implement SAP note 758677 for this. This exactly deals with your issue.
This Basically speaks about scheduling 'RSQIWKEX' for inbound and 'RSQOWKEX' for outbound queues.
Also, you need to set the parameter 'QRFC_Restart_ALLOWED' to '1' in the transaction 'SXMB_ADM' -> Integration engine. Its in the runtime dropdown menu.
Note : without this parameter being set this will not work.
Thanks,
Karthik
Edited by: Karthik Rangaraju on Oct 1, 2008 2:13 PM

How write the Outbound file name in the Inbound file

Friends,
I have a scenario like this.
Outbout filename - sample.txt
In sample.txt, i have having data like 20
Inbound filename - vivek.txt
i need data the like sample, 20
(NOTE: sample is the outbound file)
How to get this scenario.
Thanks in advance.
regards,
Vivek.

Hi Vivek,
If your PI is of SP14 and more you have an option called Adapter Specific Message Attributes.(ASMA) in communicatoin channel configurtaion, Which will help you in capturing the Sender file name during runtime.
So you will have to enable that option (ASMA) in Commchannel and capture file name in UDF using Java Code with the help of sap related API and map it to the target field which u would like to get populated.
follow the thread it has the discussion about acessing the Source file name.
Re: Getting file directory using dynamic configuration:Code needed
Thanks,
Ram.

Read Inbound payload at mapping execution of the outbound interface

Hi,
The sap system is sending us a field, that is not avaible on the web service we are consuming.
The problem is that the sap system requires this field at the responce.
How can I read the inbound payload, when I'm mapping the outbound responce?
Thanks in advance,
A

Hi!
Thanks for your responce.
Well, I will ignore solutions 1 and 3. The project has an a "must" not tu use BPM and is not possible to modify the web service due it's a closed system (legal issues).
And regarding the second point, are you proposing to create an RFC on the sap system?, The problem is that is not possible to reconstruct the relationship between the responce and the sended message. That is why I need to read the outbound payload.
Is there any walkaround to "export" this field at the outbound mapping (Context objects?) and then import it at the inbound mapping? Where are the messages stored?... I was thinking that maybe i'll be able to read the sended message using ABAP mapping, using the msgid to read an ABAP table (dont know which one). Can this be done?
Thanks again,
A

BPM - Message has error on the outbound side

I get this error 'Message has error on the outbound side" . I am using IDOC - BPM - JDBC. I checked SXI_CACHE and I see ret code 99 for this Integration Process. I tried to activate it. I see an error saying that ZCUST_NUMBER is not a component object of PAYLOAD. I have this context object defined on the Abstract Message Interface built to store the IDOC.
Any ideas are helpful

Michael,
<i>The program outputs a returncode = 99 during the cache refresh of an integration process (ccBPM), with an error message that says that 'xxxx' is not a component of the 'PAYLOAD' data object.</i>
If you are getting the above error, check OSS NOte 890760

[svn] 1751: Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.

Revision: 1751
Author: [email protected]
Date: 2008-05-15 14:21:43 -0700 (Thu, 15 May 2008)
Log Message:
Bug: BLZ-174 - MessageClient.testMessage() is incorrectly doing a string compare for the subtopic header of an inbound message against the subtopic value (which may contain wildcards) that the Consumer is using.
QA: No - customer verified the fix.
Doc: No
Ticket Links:
http://bugs.adobe.com/jira/browse/BLZ-174
Modified Paths:
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/MessageClient.java
blazeds/branches/3.0.x/modules/core/src/java/flex/messaging/services/MessageService.java

If you create a metadatatype with a single metdata block, and you reference that in your vm/cm cell attribute using a *one* based index, Excel seems to see the link and it honors it when saving the spreadsheet.
So, I ended up with something like:
<c ... cm="1"/> (I'm dealing with cell metadata, but the concept is equivalente to value metadata)
<metadataTypes count="1">
  <metadataType name="MyMetaType" .../>
</metadataTypes>
<futureMetadata count="1" name="MyMetaType">
  <bk>
    <extLst><ext
uri="http://example" xmlns:x="http://example"><x:val>87</x:val></ext></extLst>
  </bk>
</futureMetadata>
<cellMetadata count="1">
  <bk><rc
t="1" v="0"/></bk> 
</cellMetadata>
Hope this helps.

BPM : Message scheduled on the outbound side

Hi
I have messages in SXMB_MONI that have been received into my BPE. They have a status flag ok (chequered flag ) but the Outbound Status is green (message scheduled on outbound side).
The BPE would have finished by now ...been in Message Scheduled on Outbound side for the entire day now.
What has happened ? I have no error - nothing !
(there are no entries in SMQ2, nothing in SXMB_MONI_BPE in error etc etc or Short Dumps)
Please help.

I posted an OSS note on this - so answer from SAP.
Solution is to delete the old entries via RSWWWIDE report (which could also delete work items that do not have a final status.) I ran this for everything not COMPLETED.
When I send another message in - it worked fine. So the fact I had a stalled WF a week ago was affecting any new one coming in.
Drilling down into the message in SXMB_MONI from the PE I could see an Exception Handling in the MergeandSendBlock - no error given - but it did have a time of a week earlier.. anyway then in the ST22 Dump I could see wf-batch with runtime error MESSAGE_TYPE_X_TEXT.
I feel this is very poor design on the BPM processing ! oh well.
See also
#Note 836092 - Archiving/deleting work items in the XI
PS Thanks to Sudhir earlier on... You nailed it - but at that stage I did not know what you mean so did not consider this - as I had no idea what affect running that transaction would do.

Prevent the Output Message when creating PO from inbound IDOC

Hi SAP Gurus,
In my project, I have to create PO from inbound IDOC (PORDCR) with a specific Document Type ('099').
Requirement: These PO should not generate the output message while the others (Doc Type # '099') do.
I have the Z fuction module which call BAPI_PO_CREATE for posting IDOC and it works fine.
In the existing system, there are some set up that trigger the output message type for PO (output NEU) when using ME21 or ME22, as a result my PO created with output message.
Can you please advise if there are some way (User Exit?) that prevent the output message in this scenario (specific PO Type) without touching the current Condition setup?
I'm new in MM and really need help!
Thanks,
Elaine.

Hi Vinod,
I really appreciate your anwer. I'm going to explore this with my functional consultant.
Just like to have more questions:
1. Is it easier if we change the existing condition table instead of creating a new routine?
2. There are two forms for routine 101 (FORM KOBEV_101 and FORM KOBED_101). Can you explain to me why we need 2 here for what purpose of each form.
3. In the debug mode by using WE19 to post inbound IDOC, I change the SY-SUBRC = 4 and PO created without output message. Is it the right direction? Anything else I need to pay attention to?
Thanks again.
Regards,
Elaine.

Queing of messages in the outbound or inbound queues

Similar Messages

Maybe you are looking for