topic Re: Adding segment in Custom IDOC in Application Development and Automation Discussions

Adding segment in Custom IDOC

Former Member — Wed, 28 Dec 2011 10:11:40 GMT

Hi Experts,

I have created an outbound program to populate the outbound IDOC . . Now I need to add one segment to IDOC basic type .

Initially when the idoc type was released ,release was 700 . Now the release is upgraded to 701 . Hence I am not able to insert the segment in the same IDOC type .

So I have created the sucessor for this IDOC type and added this new segment in this sucessor IDOC . Now when this outbound program is executed IDOC goes in error with status record 26 as shown below :

EDI: Syntax error in IDoc (segment cannot be identified)

Message no. E0078

Diagnosis

The segment Z1ZAUDHDR does not occur at the current level of the basic type ZFI_CUST_AGEING (extension ).

Also , I tried updating the release to 701 in table EDBAS and EDISDEF . And then I was able to insert new segment in the original IDOC type .

Can you please let me know what should be the ideal way to do this and why is this error 26 ??

Also should I pass the new sucessor IDOC type in the control record in outbound program.

Please suggest.

Regards,

Kaustubh.

Re: Adding segment in Custom IDOC

Former Member — Wed, 28 Dec 2011 10:22:07 GMT

Hi,

One way i know that Delete the existing IDOC Extension and Recreate it again with your addition, it won't give you error.

Make sure you keep name of IDOC extension same as previous.

Re: Adding segment in Custom IDOC

Former Member — Wed, 28 Dec 2011 10:24:32 GMT

Hi Prarthans,

Thanks a lot for your prompt reply .

According to you , I should create an extension or a sucessor ??

Regards,

Kaustubh.

Re: Adding segment in Custom IDOC

Former Member — Wed, 28 Dec 2011 10:51:28 GMT

Hi Kaustubh,

Is the new idoc extension created released, i.e. maintain suppose release 702.

or check if the data populated in the Idoc is in proper sequence in which ur segments are present.

We got similar kind of issue and we got to know that data was not in proper sequence.

Regards,

Ganesh.

Edited by: Ganesh Lathi on Dec 28, 2011 11:51 AM