IDoc Adapter 151 - Transaction aborted

[Former Member]

Hi fellows,

after patching our XI-System to SP19 we try to do a new IDoc2File Szenario. We have one from the old XI-Level which runs really good. It's going from external R/3 to our XI server into the file system.

the new scenario has some selfmade IDoc and i already checked EVERYTHING (we20, we21, sm58, sm59, idx1, idx2, idx5, sm21) Following i give some hints what kind of problems i see. perhaps u can help me?!

in the sender-system:

sm58: IDOC_INBOUND_ASYNCHRONOUS, some mistake in IDX1 saying RFC-Destination is corrupt. But i can successfully use the remote login and the connection test.

in the receiver system:

idx5: nothing displayed concerning the new szenario

<b>sm21:Transaction aborted IDOC_ADAPTER 151</b>

I have no clue what it can be, has someone had same experiences?!

thx best regards, Jens

[Former Member]

Hi,

Are you using the same business system in both these scenarios?

In IDirectory, double click on your business system. In the service menu, go to adapter specific identifiers and check if the system details displayed is correct.

Else, change the parameters in the sld and refresh the data in the adapter specific identifiers page.

Regards,

Smitha.

[Former Member]

Thx for your input. I already checked the business system and it is all fine.

But because the scenario contains to write a file into a filesystem, i have also a business service which has the file communication channel.

In this, the service menu is empty. Do i have to have some data here concerning the sender business system?

I think i don't need some because the other scenario use nearly the same Service and runs fine.

any ideas left?

[Former Member]

Hi,

Can you make sure that the idoc(and all the idoc segments)is released?

Go to we31of the R/3 system and check this.

Regards,

Smitha.

[Former Member]

Hi, i finally made it!

It's because of idx2 where i load the metadata for the wrong port. Now i took the right one and everything works fine.

Sorry, my fault!!

thx2everybody

[stefan_grube]

From SE91 the error message IDOC_ADAPTER 151 means:

<b>Short Text</b>

Transaction IDX1: Port &1, client &2, RFC destination &3 contain error

<b>Diagnosis</b>

Transaction IDX1: Port &1, client &2, RFC destination &3 contain errors

<b>System response</b>

You tried to fetch the metadata for the current IDoc from the reference system, using RFC.

In doing so, an error occurred that was caused by one of the following:

1. You have not yet assigned a port/client to the RFC destination.

2. You have not yet created the RFC destination or it contains errors.

3. The target system is unable to receive.

<b>Procedure</b>

1. Check your RFC destination in transaction SM58.

2. Check your assignment of port and client to the RFC destination in transaction IDX1.

<b>Procedure for System Administration</b>

Contact your system administrator.

Is there anything useful inside?

Regards

Stefan

[Former Member]

Thx!

> From SE91 the error message IDOC_ADAPTER 151 means:

>

> <b>Short Text</b>

> Transaction IDX1: Port &1, client &2, RFC destination

> &3 contain error

>

> <b>Diagnosis</b>

> Transaction IDX1: Port &1, client &2, RFC destination

> &3 contain errors

>

> <b>System response</b>

> You tried to fetch the metadata for the current IDoc

> from the reference system, using RFC.

>

> In doing so, an error occurred that was caused by one

> of the following:

>

> 1. You have not yet assigned a port/client to the RFC

> destination.

>

> 2. You have not yet created the RFC destination or it

> contains errors.

>

> 3. The target system is unable to receive.

>

> <b>Procedure</b>

> 1. Check your RFC destination in transaction SM58.

>

Yes, SM58 in the sender system says an error concerning IDX1. RFC destination is wrong - BUT it's all working fine. in case of reading the metadata i also configured IDX2 in XI System to get the metadata in advance. RFC remote login and Connection test runs fine!!

I have no clue again because when i use WE19 with the old IDoc-Scenario and the SAME parameters of sending the IDoc it's working, with the new one it doesn't.

some ideas

null

[stefan_grube]

Does the user who is applied to the RFC connection have sufficient authority rights?

Unfortunately I do not find the list of the roles which are needed.

Stefan

[Former Member]

I don't know the rights either but with this user i already have a running scenario on the system. so it has to be the right one......

[Former Member]

Hi,

Are you using the same RFC destination in the other interface that are working. If no then can you check on the authorization .

Regards

Vijaya

[Former Member]

yes i do use the same rfc destination - that's the point! There is sth strange going on.

[stefan_grube]

Check note 940313. Maybe there is a useful hint inside.

Regards

Stefan

[Former Member]

Hi, i just checked the RWB for monitoring some adapters and in the BPE i find an hint that i have to configure the Workflow Runtime.

can u tell me if it's something concerning my issue?!

@Stefan: thx but i already checked this note

[Former Member]

Hi,

what is the SP Level of ABAP Stack. (System -> status -> find the SAP-BASIS component what level this also sould be SP 19).

Here my question is both ABAP Stack & Java Stack SP is same.

Regards,

Venu.

[Former Member]

Hi it's SAPKB64019, so SP19!

But again, the nearly the same scenario is already or still running! Just the IDoc is no Basistype.

thx in advance

[Former Member]

Hi,

Now you are not able to test New Scenario.

What is the problem you are faceing while testing and the backend configuration which you created first time..that was there.

Can you post your problem more clearly.

Regards,

Venu.

[Former Member]

The problem seems to be that i successfully send the IDoc from the sendersystem (we02 says status 3).

So for me it seems to be a problem on the XI side. there i found the Syslog like given above in SM21. so i have no clue what to do. actually everything is like it was with the old scenario.

In the ID and IR it's also nearly the same....i am desperate

i can't point it out more clearly....