Inbound IDOC not Triggering Immediately

[Former Member]

I am processing an inbound idoc using startrfc, EDI_DATA_INCOMING. It posts the idoc, but stuck with status 64. Partner profile set to Trigger immediately. Why will it not process immediately? I can execute the RBDAPP01 to handle, but prefer immediately. Is there something on the EDI_DC that needs to be set?

[Former Member]

I am processing an inbound idoc using startrfc, EDI_DATA_INCOMING. It posts the idoc, but stuck with status 64. Partner profile set to Trigger immediately. Why will it not process immediately? I can execute the RBDAPP01 to handle, but prefer immediately. Is there something on the EDI_DC that needs to be set?

[Former Member]

Hi,

Try to give a commit work after this function is called.

regards,

Advait

[Former Member]

How would you do that? I call the startrfc process. Is there a parameter included in this to do what you indicate?

[Former Member]

Oh, unfortunately not with startrfc. I overlooked the startrfc word in your post.

You can check this SAP note 168276. It talks about The event receiver linkage not activated in Customizing. (t-code OYEB)

regards,

Advait

[ThomasZloch]

Check in transaction SWETYPV whether type linkage for object type IDOC, event PROCESSSTATEREACHED and receiver type TS30200090 is activated (called "activate event receiver linkage for IDoc inbound" in SPRO)

Thomas

[Former Member]

The Type Linkage is not checked / activated.

[ThomasZloch]

well, activate it and that might do it already (transaction OYEB as mentioned).

Thomas

[Former Member]

Doing the OYEB, activating Linkage seems to allow the inbound idocs to "Trigger Immediately".

Thanks all.

[Former Member]

Thanks for the fix. Can you give more info as to what does the SWE2 / OYEB do regarding allowing the startrfc process to post immediately?