5 Replies Latest reply: Jun 17, 2010 10:20 PM by Sandeep Bhavsar RSS

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

Sandeep Bhavsar
Currently Being Moderated

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.

  • Re: EDISDEF: Port XXX segment defn E2EDK35 in IDoc type ORDERS05 CIM type
    Stefan Grube
    Currently Being Moderated

    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.

    • Re: EDISDEF: Port XXX segment defn E2EDK35 in IDoc type ORDERS05 CIM type
      Sandeep Bhavsar
      Currently Being Moderated

      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

  • Re: EDISDEF: Port XXX segment defn E2EDK35 in IDoc type ORDERS05 CIM type
    Heiko Hertrich
    Currently Being Moderated

    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

Actions