EDISDEF: Port XXX segment defn E2EDK35 in IDoc type ORDERS05 CIM type

[Former Member]

Hello everyone. I have read a lot of threads here and seen a lot of OSS notes but still this one beats me.

I am sending an Idoc from my ECC sandbox to my PI system. I get a status '03' on the idoc but it gets stuck.

In SM58 I see the error :EDISDEF: Port XXX segment defn E2EDK35 in IDoc type ORDERS05 CIM type.

I debugged the whole thing and I see that the RFC is fine and it gets in PI , executes INBOUND_IDOC_PROCESS and

while in IDX_IDOC_TO_XML it calls up PERFORM fill_segtyp_cache_inbound USING l_control l_edidc40.

Over here the internal table and DD40-segnam differ.

I am thinking there has got to be a note there for this but have not found one yet. The SAP basis component on my PI system is

support pack SAPKB71004, should it be higher?

Can someone help me figure this one out.

Regards and TIA.

[stefan_grube · Accepted solution]

check IDX1, is the RFC connection vaild, has the user sufficient rights?

Check SM21 in both systems.

7.1 SP4 is not the latest, but Idoc adapter should work anyway.

[Former Member · Accepted solution]

Thanks Stefan , I did check everything else and it looks fine.

The problem occurs when it does : convert the external segdef to segtyp

The internal table has segment E2EDK35000 and fails against <DD40> -segnam E2EDK35.

I deleted the IDX2 metadata and re-imported it.

Here is the SM21 log in PI,

Documentation for system log message D0 1 :

The transaction has been terminated. This may be caused by a

termination message from the application (MESSAGE Axxx) or by an

error detected by the SAP System due to which it makes no sense to

proceed with the transaction. The actual reason for the termination

is indicated by the T100 message and the parameters.

Additional documentation for message IDOC_ADAPTER 155

EDISDEF: Port &1 segment defn &2 in IDoc type &3 CIM type &4 do not exist

&CAUSE&

EDISDEF: Port & segment definition & in IDoc type & Cim type & does not

exist.

&SYSTEM_RESPONSE&

The external segment definition could not be converted to a segment

type.

This could be due to the following:

1. The meta data in the system is not up-to-date (for example, after a

Support Package).

2. The meta data in the reference system is not complete.

3. The segment types were converted to shortened segment definitions in

the sender system.

&WHAT_TO_DO&

Update the meta data for the IDoc type/Cim type and, if necessary, do

not use any conversions.

&SYS_ADMIN&

Contact your system administrator.

I will show this to basis but any clue/suggestions?

Thanks

Edited by: Sandeep Bhavsar on Jun 16, 2010 10:36 AM

[Former Member]

Hi,

I faced same kind of issue and I deleted the metadata in PI and asked ABAPER to execute the SM58 entries and all were successful.

Ashutosh

[Former Member]

Please try the following:

In your PI system, call transaction IDX2 (Metadata Overview for IDoc Adapter). Select the respective Port and open folder "IDoc Types". Mark the affected IDoc Type and click on the trash icon (delete). The Idoc Metadata is deleted and reloaded afterwards with the new content/structure. Afterwards you can reprocess the Idocs in the Source System/SM58.

Hope this helps.

Kind regards

Heiko

[Former Member]

Heiko, Thanks but I already tried that one, still geting the error.

The issue looks like the seg name is E2EDK35, in the table , IDXEDISDEF, the entry is E2EDK35000 , I do not know why it comes up as E2EDK35 in the convert to XML FM.

Table IDXEDISDEF entry.

PORT SAPEX1

SEGDEF E2EDK35000

SEGTYP E1EDK35

ACTRELEASE X

RELEASED 45A

APPLREL

[Former Member]

OK , this one is resolved, turned out to be a small thing.

A colleague noticed that I had selected Idoc version 3.0 /3.1 in the port creation in we21 ( in the ECC system).

Once it was moved to 4.x it was resolved.

of course I think this is an issue and the older idoc versions should be allowed. The Siebel folks I know use the older version.

That is another issue though.