‎2007 Jun 19 8:09 PM
Incoming IDOC (for example type PORDCH) is set to Trigger Immediately in Partner Profile but upon receipt of the IDOC it remains in status 64, ready to be processed, with no error messages. Only when RBDAPP01 is executed does the IDOC process into the application. What is needed to process into the application immediately without executing or scheduling of RBDAPP01? Shouldn't the Trigger Immediately option cause it to process into the application immediately?
‎2007 Jun 19 8:15 PM
‎2007 Jun 19 8:18 PM
shoule be in we20 ->save it ->log off the system -> login - it should work now.
‎2007 Jun 19 8:34 PM
Yes, the setup was done via WE20.
Partner Type LI
Partner Role VN
Message Type PORDCH
Process Code BAPI
Cancel Processing after Syntax Error: Yes
Processing by Function Module: Trigger Immediatley
‎2007 Jun 19 8:51 PM
‎2007 Jun 19 8:55 PM
‎2007 Jun 20 1:20 AM
This happens in Production or test system.
Reason some time if system is too busy.
We also face this problem, but this happen once or twice a year.
Did you tried to process your idoc in WE19 transaction(Run background).
Thanks,
Narayan
‎2007 Jun 20 4:11 PM
This is happening for all IDOC types in Production system as well as test system.
WE19 works OK. I can start Standard Inbound processing and IDOC gets passed to application as expected. There is no background option for WE19 that I can see.
‎2007 Jun 20 4:37 PM
Standard inbound is background mode.
What kind of message is this and this idoc has too many segments ?
Thanks,
Narayan
‎2007 Jun 20 4:42 PM
IDOC Basic type is PORDCH01, Message Type PORDCH.
Two segments, segment 1: E1PORDCH, segment 2: E1BPMEPOTEXTHEADER
‎2007 Sep 27 8:18 PM
Hi Mike,
Were you able to solve this problem? I have a similar issue, maybe you can advise what can be done to fix it?
Thanks,
AK
‎2007 Oct 24 7:38 PM
Aneta, I have not resolved this problem yet. I am now going to open up a message with SAP Support to advise me.
-Mike
‎2015 Nov 06 10:25 AM
Hi Mike,
Have you found the solution for this. Can you please share what was the reply from SAP.
‎2015 Dec 16 2:37 PM