IDOC-Adapter (HCM to PI) Sending Problem

[Former Member]

Hi PI-gurus!

We're trying to implement our first IDOC scenario on PI which for testing should look like this:

HR Backend --> IDOC (Messagetype HRMD_ABA) --> PI --> SFTP/FILE

On PI we tried to use the normal IDOC-adapter and the IDOC_AAE adapter.

Both have the same result:

The IDOC are not sent, but create an error in SM58 / tRFC-queue of the backend.

We got two types of errors:

Mostly, it's this one: Use IDOC Adapter for FM IDOC_INBOUND_ASYNCHRONOUS. --> What does this mean?

Sometimes we get this: Authentication failed.

We are using a SAP ECC 6.0 backend and SAP PI 7.3 with dual stack.

I guess, some configuration is wrong. Does anyone have an idea?

I also wonder about the following questions:

1. Can we use the IDOC_AAE adapter, when having a dual stack system?
2. What are the RFC-Parameters in the IDOC-Sender for? Is this a back connection to the backend or a connection to the ABAP stack of PI?
3. Do we need to configure anything in NWA if we choose "Manual" option?
4. Are there any good tutorials?

[Former Member · Accepted solution]

Hi

Please refer the below blog

http://scn.sap.com/docs/DOC-31398

Hope it helps you

[Former Member]

Okay, thanks guys. But we finally found the solution for the "Authentication failed." problem on our own:

It was the logon option "SAP assertion ticket" which was used in the config of the RFC-connection in the R3 (Sender) system.

I figured out that there is a more explaining error message in the NWA.

Obviously, if you check "SAP assertion ticket", the PI checks if the sender is a "trusted system" (maintained in transaction SMT1). So another solution would be to add the system there.

[former_member184681]

Hi,

Answering your questions:

@1: yes, as far as I know.

@2-4: check Michal's blog here:

Regards,

Grzegorz

[Former Member]

Thanks Grzegorz, but I of course, I already read this blog.

Anyway, in the meantime we found the reason for the error message "Use IDOC Adapter for FM IDOC_INBOUND_ASYNCHRONOUS.".

There was a different RFC-Sender-Adapter, which was listening for data on the same program-id. So this one received the data and of course ran to an error.

But now, we get the second error all the time: Authentication failed.

Sure, this is an authority problem. But, I have no idea, where this comes from.

--> Any ideas where or by what this error could be caused?

--> I guess, the problem appears when using the backwards connection to R3 to read meta data?!

[former_member184681]

Dear Heiko,

Where do you see this error "Authentication failed"? Is it on the ECC side (sm58) or in PI monitoring?

Regards,

Greg

[Former Member]

The error appears in Sender ECC system - not on PI.

[former_member184681]

Then apparently your RFC destination on ECC side is incorrect or incomplete. Make sure of the following:

- Program ID, Gateway host and Gateway service are provided on "Technical settings" tab page

- Client, user name, password and language are provided on "Logon/Security" tab page

- Technical user is authorized to establish RFC connections, send IDocs and so on.

Regards,

Greg