Inbound Message - Scheduling

HI All,
I am working on F2F Scenario with FCC, my data is getting processed successfully by sender and receiver CC, and also i could see the chequred flag in SXMB_MONI, but when i see the pipeline it is showing as"Scheduled" in the Inbound message.
What could be the problem eventhough I have received the output file successfully,
Regards,
Nithiyanandam

Hi Suraj,
No error shown in Receiver CC. it shows
10/8/09 11:34:29 AM 27498307-86a8-4d16-353a-946fa68178f2 Message processing completed successfully
10/8/09 11:34:29 AM 27498307-86a8-4d16-353a-946fa68178f2 Message with ID 27498307-86a8-4d16-353a-946fa68178f2 processed
10/8/09 11:34:29 AM 27498307-86a8-4d16-353a-946fa68178f2 Message processing started
Also when I looked into the message data tab in receiver channel it shows
End Point http://XXXX:XXXX/MessagingSystem/receive/AFW/XI
Authorization PasswordCredential(PIISUSER):password=********
Is this correct or it should be using PIAPPLUSER. If so where should this be changed
Regards,
Nithiyanandam
Edited by: Nithiyanandam A.U. on Oct 8, 2009 8:11 AM

Similar Messages

BPM Mapping scheduled status in SXI_MONITOR Message scheduled on outbound

Hi All,
Please help me how can i solve following issue.
My Scenario WebService - PI - Proxy.
One of the message gets an error in the moni. where I get an green flag 'Message Scheduled on the outbound side".
The design was working fine earlier. It is giving problem now.
I tried following options:
1) I tested the mapping - it is working fine.
2) I checked Cache - the status is fine.
3) I checked Inbound queue(SMQ2) there are no messages stucked in the queues or saved in (smq3). Here i am using EOIO.
4) I checked SWWL - there are message with COMPLETED and STARTED but there are not ERROR messages.
Could any one please tell me - Can i DELETE - COMPLETED messages from SWWL? If i delete what is going to happen.
Please advice
Thanks
VR

Hi,
In SXMB_MONI click on "PE" and open the Graphic Flow to see where actually your BPM has failed
Also suggesting to check both the Queues....SMQ1 and SMQ2.....
delete an instance from SWWL only if it is in error state.....
regards,
Abhishek.

In SXMB_MONI with(Green Flag) "Message Scheduled Outbound Side" (using BPM)

Hi All,
I had a Scenario where I am using BPM (to collect the Idocs received from Sender SAP R/3 system) and create a File as target structure. But one of the entry i found as (Green Flag) with status "Message Schedule Outbound Side". But the remaining messages are processed successfuly through the same BPM.
I even found that the when i double click on the PE of the "Green flag entry". its leading to "qRFC Monitor(Inbound Queue) with empty entries" instead it should lead me to the workflows Log screen. Since other successfully messages are leading to workflow log when i double click on the PE.
Please let me know your comments on this.
Thanks,
Shailaja

Hi Gouri,
I am getting gray flag in the column (Status - XML Message Status) and green flag in Colum (C- Outbound Status). So this Greem flag itself is creating the problem, because of this itself my messages is not getting processed and not delivered to target system.
I have even checked SXI_CACHE, when i click on the Integration Process-- Right click on my BPM and select the "Activation Log" .. here a message which i had
I Language not set. Using system default E
The container element MULTI_INVOIC02 is written, but not read or exported
The container element MULTI_INVOIC02 is written, but not read or exported
So the "MULTI_INVOIC02 " is used in the Container Operation & Multimapping of my BPM. I suspect that error as taken place in doing Corelation. Do you have any comments on this. If i get any error in Corelation .. how can i debug my BPM.
Thanks,
Shailaja

Message scheduled on outbound side for proxy to proxy scenario

Hi All,
I am working on Proxy-to-Proxy Scenario.
When i checked my messages in SXMB_MONI, after PE tab it was showing green flag with message as
Message Scheduled on Outbound side.
Please provide the solution what i have to do.
Points will be given
Thanks
Ram

Hi Swarup,
When i clicked on PE, its leading to qRFC Monitor (Inbound Queue).
Here error was showing as Permanent Error in BPE Inbound Processing.
Could u please guide me how to procedd.
Thanks
Ram

Emulation inbound message problem

Hello.
I try to emulate call operation in my BPEL process. Operation is defined as synchronous two-way operation in WSDL. But when I create test with emulation inbound message I see in log this:
<2008-02-19 10:16:54,136> <ERROR> <default.collaxa.cube.bpeltest> <com.collaxa.cube.engine.test.PartnerEmulation$ScheduledPost::execute> scheduled post failed
com.oracle.bpel.client.ServerException: IDeliveryService.post() invoked for twp-way operation 'orderAccept'. This method can only be used to invoke one-way operations which don't return any messages. Please check the WSDL which defines this operation and use the method IDeliveryService.request() to invoke a two-way operation
 at com.collaxa.cube.engine.delivery.DeliveryHandler.post(DeliveryHandler.java:98)
 at com.collaxa.cube.ejb.impl.DeliveryBean.post(DeliveryBean.java:201)
 at com.collaxa.cube.ejb.impl.DeliveryBean.post(DeliveryBean.java:156)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
 at com.evermind.server.ThreadState.runAs(ThreadState.java:646)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
 at DeliveryBean_RemoteProxy_4bin6i8.post(Unknown Source)
 at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.java:195)
 at com.collaxa.cube.engine.test.PartnerEmulation$ScheduledPost.execute(PartnerEmulation.java:531)
 at com.collaxa.cube.engine.test.PartnerEmulation.emulatePost(PartnerEmulation.java:339)
 at com.collaxa.cube.engine.test.PartnerEmulation.emulate(PartnerEmulation.java:396)
 at com.collaxa.cube.engine.ext.wmp.BPELReceiveWMP.perform(BPELReceiveWMP.java:181)
 at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3672)
 at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1650)
 at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:184)
 at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:276)
 at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5658)
 at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1726)
 at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.handleWorkItem(CubeEngineBean.java:306)
 at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAs(Subject.java:396)
 at com.evermind.server.ThreadState.runAs(ThreadState.java:648)
 at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
 at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
 at CubeEngineBean_LocalProxy_4bin6i8.handleWorkItem(Unknown Source)
 at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handle(PerformMessageHandler.java:45)
 at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:138)
 at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
 at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
 at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.interceptor.system.SetContextActionInterceptor.invoke(SetContextActionInterceptor.java:44)
 at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
 at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
 at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.OC4J_invokeMethod(MessageEndpointImpl.java:297)
 at WorkerBean_EndPointProxy_4bin6i8.onMessage(Unknown Source)
 at oracle.j2ee.ra.jms.generic.WorkConsumer.run(WorkConsumer.java:266)
 at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
 at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
 at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
 at java.lang.Thread.run(Thread.java:595)
What can I do?

I found this problem similar to
BPEL Testcase with pick-activity
How to emulate invoke in BPEL process test
Problem is how to change mind of BPEL testsuite to use IDeliveryService.request() instead of IDeliveryService.post().
I found on metalink that is a real bug. But there is a workaround with external call.

SXMB_MONI only getting the Inbound Message ( CENTRAL ) not other steps

Hi All,
I am doing a File to proxy scenerios. I am posting the file using file content cnversion. When ever i am checking the scenerios throught tool-->Test
Its working perfectly fine.
But when i am sending the file and checking the SXMB_MONI.
Its only showing the Inbound Message ( CENTRAL ) step. After that its not showing any receiver messages steps. What is the problem? Is there any services not activated? Can you help me on this?
Thanks
Manas

HI Ravi,
i have check the trace lavel this is 1. I have given the trace lavel below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = PID</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2008-07-08T11:24:07Z PST</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 04B466276FDB48713ABDB7E5A31732C5</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0006</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0006</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MIOA_MT_GLEmpExp*</Trace>
<Trace level="1" type="T">select interface namespace http://omnicell.com/FIN</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
</SAP:Trace>

[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 Mapping error in SXI_MONITOR Message scheduled on outbound side.

When I try to process this message i get an error.
Message scheduled on outbound side.
I am using a BPM.
MI_Source -> MI_Receive_BPM -> MI_TRANS1_BPM -> MI_TRANS2_BPM -> MI_TARGET
Using EOIO in the send step Queue Name: cases
If I remove MI_TRANS2_BPM the message reaches the bpm, but with both transformation in the BPM the message gets an error in the queue where I get a green flag 'Message Scheduled on the outbound side"
This BPM was working on Friday but hasn't worked since. There have been no changes to the my development XI environment.
Some things that i have tried: Clearing the Queues (smq2), Redoing the entire scenario, clearing cpa cache.
Please help.
Thanks
Chirag

Hi,
MI_Source -> MI_Receive_BPM -> MI_TRANS1_BPM -> MI_TRANS2_BPM -> MI_TARGET
Any specific need to have the above design pattern....you can also try:
MI_Receive_BPM -> MI_TRANS_BPM -> MI_TARGET
You can use the message that you initially receive and apply all the necessary transformation on it and the map it to the target structure....
As you mentioned that if you remove MI_TRANS2_BPM your message is executed successfully...it means that the BPM transformation 2 is waiting for some event / Message....
If you need to go by the same design then you can follow the below steps to resolve the problem:
1) Check the return code of BPM in SXI_CACHE...it should be 0
2) Check for any errored instance of your BPM in SWWL (as mentioned in above posts)
3) Open the corresponding Queue and see for the messages stuck in the Queue....your Queue may be blocked....your BPM will be using a particular Queue and if any message is stuck in the Queue then all the messages that follow will get stuck in the Queue....
Now if it is only your BPM that is using this particular Queue then Delete the Queue (applicable to development environment....do not try in QA or Production environment)
4) In SXMB_MONI click on "PE" and open the Graphic Flow to see where actually your BPM has failed (possible only if the message has entered the BPM.
Regards,
Abhishek.

Error receiving AS2 message from partner: B2B-50037: B2B inbound message processing error

B2B/SOA 11.1.1.6.0
We are setting a new trading partner and when we started document transmissions we are getting errors on the inbound messages: B2B-50037: B2B inbound message processing error.
The attachment shows the relevant lines from the soa log and diagnostic log files. Here is the error detail that shows:
[URI: /b2b/httpreceiver] Error -: B2B-50037: B2B inbound message processing error[[
Error -: B2B-50037: B2B inbound message processing error
 at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:3143)
 at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1650)
 at oracle.tip.b2b.transport.InterfaceListener.onMessageLocal(InterfaceListener.java:403)
 at oracle.tip.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:214)
 at oracle.tip.b2b.transport.basic.TransportServlet.doPost(TransportServlet.java:754)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
 at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
 at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
 at java.security.AccessController.doPrivileged(Native Method)
 at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
 at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
 at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
 at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
 at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
 at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
From the b2b_wire_message we get these Protocol_Transport_BINDINGS:
ChannelName=TransportServlet
Reverse-Via=LIN-ISA1
AS2-To=accobra.....
Date=Fri, 26 Sep 2014 05:46:17 +0000
AS2-Version=1.2
AS2-From=K.......
Disposition-Notification-Options=signed-receipt-protocol=optional, pkcs7-signature; signed-receipt-micalg=optional, sha1
Disposition-Notification-To=http://<ip&port>/as2in
Message-ID=<[email protected]>
MSG_RECEIVED_TIME=Fri Sep 26 00:46:17 CDT 2014
ECID-Context=1.0050z5j^buc6yGn6wnZf6G0002f60007bt;kXjE1ZDLIPGIj2QCYV8QoKSSmLRO_PQT_IS
Content-Type=application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m
Proxy-Client-IP=172.17.25.101
MIME-Version=1.0
User-Agent=e-integration AS2 Server V 6.1.8
X-Forwarded-For=172.17.25.101
Content-Length=3602
Host=nalinsoa05.abd.ad.acco.com
x-weblogic-cluster-hash=QoZzGUzdcjBD5fGIE8Uos5abiHI
EDIINT-Features=multiple-attachments, CEM
Connection=Keep-Alive
X-WebLogic-KeepAliveSecs=30
X-WebLogic-Request-ClusterInfo=true
The message creates a wire message, business message, and an application message.
What doesn't happen is no MDN gets sent back to the partner. It should be a synchronous MDN.
We have double checked the certificates on both ends and they are OK.
The document and Agreement get recognized OK:
Refer To Message
Refer To Message
Sender Type
AS2 Identifier
Sender Value
K. . .
Receiver Type
AS2 Identifier
Receiver Value
accobr. . .
Sender
K. . . l
Receiver
ACCO . . .
Agreement Id
K. . .l_EDI_X12_4010_856_856Def_Inbound
Agreement
K. . .l_EDI_X12_4010_856_856Def_Inbound
Document Type
856
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
INBOUND
State
MSG_ERROR
Acknowledgement Mode
SYNC
Response Mode
ASYNC
Send Time Stamp
09/26/2014 12:46:17 AM
Receive Time Stamp
09/26/2014 12:46:17 AM
The error is vague enough to provide little or no help in locating the root cause of the issue.
Any assistance in providing information on how to get this working would be greatly appreciated.
We do have dozens of other AS2 partners working in this instance just foe reference. We are just having issues with this new partner setup.
Thank you.
Regards,
Ken

Ken,
I am observing the Ack Mode is set as "SYNC" . This is selected by default. This option is available in the channel configuration section
If the usecase is not SYNC, please change as ASYNC and test. It should work.

EDI Message Type for Credit Memo inbound message

Hi Experts ,
We have ECC6.04.
We configured Incoming vendor invoice idoc ( Message Type - INVOIC, Basic type - INVOIC02) which is working fine. We also have Credir Memo incoming message ( Message Type - GSVERF , Basic type - GSVERF03 , Processing code- GSVE , FM-IDOC_INPUT_GSVERF_START and assigned this FM to Object Type- BUS2094)
I am using same IdoC in WE19 that of Invoice, which successfully posted and editing the BSART as CRME and entering the Messgae type GSVERF , but when I am posting it system is giving error
No record exists in T661W for vendor 2000001 , plant , unloading pointMessage no. V4032
Diagnosis
The system could not determine a sold-to party as no record has been specified in Table T661W for the displayed supplier, plant, and unloading point values.
System Response
IDOCS processing is terminated.
Procedure
Please create a record in Table T661W for the above values and restart the IDOCS planning from electronic mail.
and
EDI: Syntax error in IDoc (segment cannot be identified)Message no. E0078
Diagnosis
The segment E1EDK04 does not occur at the current level of the basic type GSVERF03 (extension ).
This error can have several reasons:
The segment E1EDK04 is assigned to a group whose header segment does not occur.
The segment E1EDK04 does not exist in the syntax description of the basic type GSVERF03 (extension ).
The sequence of segments in the group in which the segment appears is incorrect.
Previous errors ('mandatory' segment or group missing) may be due to this error.
Procedure
Please check the IDoc or the syntax description of the basic type GSVERF03 (extension ).
Th table T661W is for Vendor, partner decribtion, Sold to party, Unlaoding Point. So I am not getting whsy sold to part relevant table ssytem is asking to make entry ?
Can anyone please suggest/help me what is the problem and solution on this ?
Thanks
NAP

Hi ,
Currently we are using Message Type - GSVERF , Basic type - GSVERF03 , Processing code- GSVE , FM-IDOC_INPUT_GSVERF_START and assigned this FM to Object Type- BUS2094)..which is giving above error. I just found that process code GSVE is for Outbound message
Can any one suggest / confirm what should be exact Message Type , Basis Type, Process code and Funct. Module requiered for processing EDI inbound message in MM - Logistics Inv Varification ?
Thanks
NAP

Send Commit to message stuck in "Message Scheduled" status

Hello,
I generated some messages using ABAP Proxy. However, the commit work never happened in the program that created the message. Now these messages are stuck in "Message Scheduled" status. How can I push the message forward. Can I trigger a commit? If so, how?
Regards
Cerish

Hi Cerish,
Are you getting this status in the XI ? If so, go to Queue Monitor and try to activate the same.
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Also check the SXMB_MONI of Application System(R/3) if you have a access about is proxy message is executed or not .
If the status is restart not possible, then you need to reprocess that.
Hope this helps,
regards,
moorthy

Handling inbound messages in B2B

Dear All
I have problem configurating B2B to receive any inbound message from the IP_IN_QUEUE, local directory or ftp. Basically, the remote partner transport just doesn't go and pick up the incoming messages. All outbound messages work fine. I am using the HL7 protocol.
I have tried to set oracle.tip.adapter.b2b.DocumentRouting=true as recommended in the manual but it doesn't help.
Just wondering any other setting I need to change before the engine is able to pick up inbound messages.
Thanks in advance,
Alan

Dear all,
I can finally recieve an inbound HL7 with MLLP. One strange thing I find is that the Win32 version does not have the option for entering the "MLLP ID". However, I Still do not have much luck with inbound file.
I now have other questions. We want to setup a B2B server to receive all HL7 messages. As the B2B server would process all incoming messages and put it in the IP_IN_QUEUE, how would the BPEL processes know which message they should pickup from the queue? I read something about the document routing ID but it seems that HL7 doesn't have this feature.
Another question, is it possible to adjust the frequency of the B2B server to poll the outbound queue for jobs? We have applications that require very fast response and the current setting just do not serve our needs.
Finally, is it that if we want an inbound queue services in B2B, how long does it take for the feature to be included in the service?
Thank you very much for you help,
Alan

MDM adapter Non-XML Inbound Messaging

Hi all,
I have a scenario where I transport a csv file via PI (NW711_05_REL) to MDM using the File adapter (sender) and MDM adapter 7.1 7.1 (receiver).
The message is sent through to the MDM port fine, and it seems to choose xml as default file type and PI MSG ID as file name.
This results in an xml file with csv content.
As I want to put the file on the port with its original file type (csv) and name, I need to tweak the MDM adapter a bit. For this I have tried to find MDM specific modules, but have been unable to do so.
I have found a u201Cwork aroundu201D by using u201CSet Adapter Specific Message Attributeu201D on the sender file adapter u2013 described on help.sap.com
Configuring the sender file adapter as described in http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854884d3217cee10000000a421937/content.htm i am able to set the "FileName" attribute in dynamic configuration.
This enables me to get some of the desired effect, as the file on the MDM port is now a csv file u2013 half way there!! However the file name remains PI MSG ID...
Am I missing something here or is the adapter not working as intended? I donu2019t understand why it should only use the file type when the entire filename and type is there. I would assume that the entire filename and extension would be used in the MDM port.
I have tried achieving the desired result by using the "AF_Modules/DynamicConfigurationBean" on a JMS adapter, but the result is the same.
I would like to avoid developing my own custom module to handle this, as it seems like it should be possible to handle in a more standard way.
I hope someone out there can help me out, and hope to see a lot of good replies.
Best Regards,
Jesper

have you gone thur these settings?
Non-XML Inbound Messaging
When the backend system uses the PI File Adapter sender as the communication channel to deliver messages to the PI server, and the receiving MDM channel corresponds to an inbound MDM port of type other than XML (for example, Flat text file), then you must enable the File Adapter Specific Message Attribute named File Name as follows:
       1.      Edit the corresponding File Adapter sender communication channel.
       2.      In the Advanced tab, choose Set Adapter Specific Message Attribute.
       3.      Choose the File Name.
       4.      Save and activate the changes.
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854884d3217cee10000000a421937/frameset.htm

[URGENT] Get Inbound Message in EBS Using XML Gateway + SOAP

Hi experts,
I want to ask you about how to process the inbound message using XML Gateway and SOAP protocol.
I have 2 EBS instances, let's called it A (source) and B (destination).
FYI, I'm following this ebook: "Oracle E-Business Suite Development and Extensibility Handbook" in chapter 12 regarding Oracle XML Gateway.
So I don't use BPEL PM to do this.
I'm just using EBS with XML Gateway and Integrated SOA Gateway responsibilities.
When I tried to send the XML from A to B using OXTA, it's success, the data can be processed in B and could store in the database.
But when I tried to use SOAP, the XML message that has been sent from A is success, and when I check it on B (Integrated SOA Gateway -> SOA Monitor), the message is in there and I can see the SOAP request and response as well.
SOAP request:
<?xml version="1.0" encoding="UTF-8" ?>
- <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://xmlns.oracle.com/apps/fnd/XMLGateway" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
- <env:Header>
- <ns0:XMLGateway_Header>
<ns0:MESSAGE_TYPE>XML</ns0:MESSAGE_TYPE>
<ns0:MESSAGE_STANDARD>OAG</ns0:MESSAGE_STANDARD>
<ns0:TRANSACTION_TYPE>XKLB</ns0:TRANSACTION_TYPE>
<ns0:TRANSACTION_SUBTYPE>ORDER_DETAILS_XO</ns0:TRANSACTION_SUBTYPE>
<ns0:DOCUMENT_NUMBER>9282</ns0:DOCUMENT_NUMBER>
<ns0:PARTY_SITE_ID>142</ns0:PARTY_SITE_ID>
<ns0:USERNAME>cons.ade</ns0:USERNAME>
<ns0:PASSWORD>cons.ade</ns0:PASSWORD>
</ns0:XMLGateway_Header>
</env:Header>
- <env:Body>
<ns0:ReceiveDocument xsi:type="xsd:string"><ORDER_DETAILS_XO xmlns=""> <ORDER> <ORDNO>100002</ORDNO> <ORDWT>100002</ORDWT> <RDATE/> <CITY>JAKARTA</CITY> <ZIP>17121</ZIP> </ORDER> </ORDER_DETAILS_XO></ns0:ReceiveDocument>
</env:Body>
</env:Envelope>
SOAP response:
- <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header />
- <env:Body>
- <ReceiveDocument_Response xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">
<ResponseCode xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">200</ResponseCode>
<ResponseMsgId xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">BD4EAD91E76051D5E0440021287448DA</ResponseMsgId>
<ResponseInfo xmlns="http://xmlns.oracle.com/apps/fnd/XMLGateway">Document received and pushed into queue for asynchronous processing. Enqueued message id is 'BD4EAD91E76051D5E0440021287448DA'.</ResponseInfo>
</ReceiveDocument_Response>
</env:Body>
</env:Envelope>
But the problem is the message that has been got in B can't store into the database yet.
I had already changed the Queue in the XML Gateway -> Define Transaction, from APPLSYS.ECX_IN_OAG_Q (this is for OXTA) to APPLSYS.WF_WS_JMS_IN.
After I invoke the webservice and the SOAP message has been got in B, I checked APPLSYS.WF_WS_JMS_IN in database and there is 1 record, the value of USER_DATA column is:
((, , , , , , ((BES_EVENT_NAME, 100, oracle.apps.fnd.wf.ws.inbound.xmltx.receive, , 27), (BES_EVENT_KEY, 100, 796550960, , 27), (BES_PRIORITY, 200, , 1, 23), (BES_FROM_AGENT, 100, [email protected], , 27), (BES_TO_AGENT, 100, [email protected], , 27), (MSG_ID, 100, 1334117503435, , 27), (ECX_MESSAGE_TYPE, 100, XML, , 27), (ECX_MESSAGE_STANDARD, 100, OAG, , 27), (ECX_PARTY_SITE_ID, 100, 142, , 27), (WS_PORT_OPERATION, 100, ReceiveDocument, , 27), (ECX_TRIGGER_ID, 100, 7101, , 27), (UserId, 100, 3020, , 27), (ECX_USERNAME, 100, CONS.ADE, , 27), (ECX_TRANSACTION_SUBTYPE, 100, ORDER_DETAILS_XO, , 27), (ECX_PASSWORD, 100, CONS.ADE, , 27), (ECX_DOCUMENT_NUMBER, 100, 9285, , 27), (BES_PAYLOAD_OBJECT, 100, false, , 27), (ECX_ATTACHMENTS, 100, , , 27), (ECX_TRANSACTION_TYPE, 100, XKLB, , 27), , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , )), 0, , )
When I tried to select APPLSYS.WF_WS_JMS_IN for the 2nd time, there is no result, which means the business event has been triggered, right?
So in this point I still don't have any idea why the process is (likely) ended after enter the Queue and the message can't store into B's database yet.
Do I miss any setup when changing from OXTA into SOAP protocol to send XML message?
Any urgent help most appreciated.
Best Regards,
Rheza

Hi,
Did you ever get any answers to this? We are thinking about the same thing.
Thanks
Darma
[email protected]

Message Scheduled But is not delivered

HI
I have one large message which is broken in to smaller packets and in r3 and sent to the XI system via abap proxy . My scanario uses a BPM where i have a loop which has a correlation . I collect one message send it and then again the loop collects and sends the next message.
My problem is in SXMB_MONI out of the eight small messages one message shows a green flag (Message scheduled on the outbound side ) . It is not scheduled but not delivered from the IEngine to The PE. Rest all the message are delivered properly.
How can debug such a scenario.
regards
Nilesh Taunk

Hi,
 In SXMB_MONI, did you get a message like this as seen below:-
"Message <MessageID> parked at the process <ProcessID> but not yet processed"
 Solution:
 Check your correlation defined. Use local correlation instaed of global correlation, i.e use the correlation in your block step. This should solve the problem.
Also see the SAP Notes below:
898131 : BPE-RUN: Messages lost when processes are incorrect.
894906 : BPE-RUN: Finding unprocessed messages.
Hope this resolves the issue.
Regards,
Dhana

Inbound Message - Scheduling

Similar Messages

Maybe you are looking for