Message not created in RWB

[Former Member]

HI,

I am doing <b>IDOC->FILE Scenario</b>. I done all those

thing to required do like

In R/3

-

---

LS, Port,PartnerProfile, RFC Destination

in XI

-

---

RFC Destinations , port, Loaded Meta data.

Then Message is not created in RWB. It is showing

File adaptor is working fine. But Idoc adaptor is not

shwoing in the adaptor list. I am working on PI-

netweaver2004s.

But in R/3 idoc status is showing "30 - IDoc ready

for dispatch (ALE service)".

What will be problem?

thx and regards,

ansar.

[Shabarish_Nair · Accepted solution]

for idoc monitoring check idx5 in XI

and in R3 check the log for sm58.

[Former Member · Accepted solution]

Hi,

>> I checked in R/3-We20 it was in "Transfer

Immidiatly"

>> I checked in XI - IDX5 : "No messages found"

>> Excuted Program RBDMIDOC : but "Message type cann't be sent with change pointer"

>> >> <b>In R/3-SM58 : "User PIRWBUSER has no RFC authorization for function group ERPF"</b>

Error came... How to solve it

thx,

Ansar

[Former Member · Accepted solution]

Hi,

Still I am getting this Error:... (Idoc -> File)

In R/3

-

---

We02 - "IDoc: 0000000000199043 Status: Data passed

to port OK"

sm58 - "In R/3-SM58 : "User PIRWBUSER has no RFC

authorization for function group ERPF"

Can anyone give me solution for this.

thx

Ansar.

[Former Member · Accepted solution]

Hello Ansar,

In your RFC destination on the R/3 Side use the user "PIAPPLUSER" instead of "PIRWBUSER" in the "LOGON_SECURITY" tab.

Regards,

Sri.

[Former Member · Accepted solution]

Hi Srihari,

<i> In your RFC destination on the R/3 Side use the

user "PIAPPLUSER" instead of "PIRWBUSER" in

the "LOGON_SECURITY" tab.</i>

By placing "PIAPPLUSER" My problem solved.

thx.

[Former Member]

Hi Ansar,

Please goto transaction SE38 and execute the Program RBDMIDOC.

cheers,

Prashanth

P.S Please mark helpful answers

[MichalKrawczyk]

hi,

why?

doesn't it have to mean that the IDOC was based

on change pointers ?

Regards,

michal

[MichalKrawczyk]

hi,

>>>>But in R/3 idoc status is showing "30 - IDoc ready

for dispatch (ALE service)".

this means you need to send the IDOC from R3

you can do it from BD87

you can change this behaviour in WE20

(change the outobund profile to - process immediately)

Regards,

michal