Re: Inbound idoc remain in status 64

[ Follow Ups ] [ Post Followup ] [ Message Board ]

Posted by [IP Address: 192.6.111.74] 'hacquard' on September 17, 2001 at 04:38:46 EST:

In Reply to: Re: Inbound idoc remain in status 64 posted by [IP Address: 192.6.111.74] 'Lax' on September 16, 2001 at 03:47:51 EST:

Hello Lax,

where can I define this 'commit work' ?

I use function startrfc....

: Once IDOC is written to the database, tRFC is called to pass
: the idoc data, then if you don't use 'commit work', idocs will
: remains in status 64 even though you set up partner profile
: for immediate transfer.

: Lax

: : Hello,

: : I have done the set up of inbound idocs with 'trigger immediately' but all inbound idocs remains in status 64.
: : Then, I have activated inbound event link with OYEB (note 168276) but nothing changes !
: : Has anybody an idea of the reason of that issue and how to solve it ??
: : Regards,

: : Alain

Follow Ups:

Post a Followup

Name:
E-Mail:
Subject:
Message: : Hello Lax, : where can I define this 'commit work' ? : I use function startrfc.... : : Once IDOC is written to the database, tRFC is called to pass : : the idoc data, then if you don't use 'commit work', idocs will : : remains in status 64 even though you set up partner profile : : for immediate transfer. : : Lax : : : Hello, : : : I have done the set up of inbound idocs with 'trigger immediately' but all inbound idocs remains in status 64. : : : Then, I have activated inbound event link with OYEB (note 168276) but nothing changes ! : : : Has anybody an idea of the reason of that issue and how to solve it ?? : : : Regards, : : : Alain