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
Showing results for 
Search instead for 
Did you mean: 
Read only

Inbound IDOC - Trigger Immediately not working.

Former Member
0 Likes
5,213

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?

13 REPLIES 13
Read only

Former Member
0 Likes
2,877

In which transaction did you set this flag?

Read only

Former Member
0 Likes
2,877

shoule be in we20 ->save it ->log off the system -> login - it should work now.

Read only

0 Likes
2,877

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

Read only

former_member194669
Active Contributor
0 Likes
2,877

Whether "Test" flag is ticked?

aRs

Read only

0 Likes
2,877

Test flag: No

Read only

0 Likes
2,877

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

Read only

0 Likes
2,877

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.

Read only

0 Likes
2,877

Standard inbound is background mode.

What kind of message is this and this idoc has too many segments ?

Thanks,

Narayan

Read only

0 Likes
2,877

IDOC Basic type is PORDCH01, Message Type PORDCH.

Two segments, segment 1: E1PORDCH, segment 2: E1BPMEPOTEXTHEADER

Read only

Former Member
0 Likes
2,877

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

Read only

0 Likes
2,877

Aneta, I have not resolved this problem yet. I am now going to open up a message with SAP Support to advise me.

-Mike

Read only

0 Likes
2,877

Hi Mike,

Have you found the solution for this. Can you please share what was the reply from SAP.

Read only

2,877

Was Event Linkage activated ? (transaction OYEB) ?