topic Re: IDOC Segment Data element Problem in Application Development and Automation Discussions

IDOC Segment Data element Problem

itabhishek9 — Wed, 24 Mar 2010 12:19:58 GMT

Hi SDNites,

I have created a custom segment for a custom IDOC and the details of this segment has to be shown in the ALV with field headers having the description corresponding to data element used for IDOC segment fields. But when the segments are created as a structure all the data elements are changed to char automatically so my column header descriptions are coming

Re: IDOC Segment Data element Problem

Former Member — Wed, 24 Mar 2010 16:20:08 GMT

Hi Abhishek Gupta

you question is not clear... Explain in clear way....

Thanks

Ramesh

Re: IDOC Segment Data element Problem

itabhishek9 — Thu, 25 Mar 2010 04:40:17 GMT

Hi,

Reiterating my question,

Whenever we create an IDOC segment using WE31, a structure gets created in SE11. But this structure doe not contains the data element used in We31. Inspite of that fields are associated with Char types.

When these segments are used to display in ALV, the description does not come up as they are associated with char types. I have a lot of segments in my pgm which are displayed in ALV. Is there a simpler way to get the description in ALV.

Regards,

Abhi

Re: IDOC Segment Data element Problem

Former Member — Thu, 25 Mar 2010 07:01:25 GMT

Hi,

Use the FM IDOC_COMPLETE_SEGMENT_READ. You will get desc and feild lenght info.

Then populate field catalogue manually. inorder to show the descriptions.

Regards,

Shanmugavel Chnadrasekaran

Re: IDOC Segment Data element Problem

Former Member — Thu, 25 Mar 2010 07:24:08 GMT

That's where in the good old days SAP used to generate several dictionary structures. The E1 structure was used for filling the actual IDoc, so had to consist only of character-type fields. However, then there were also corresponding E2 (segment definition) and E3* (segment documentation) structures defined, which contained the relevant information. This doesn't happen any longer, but you can see that for example when looking at E1MARAM, E2MARAM does have the information you need.

Anyhow, nowadays those (superfluous) additional dictionary structures are no longer generated and segment information field information is stored in table EDSAPPL. However, in general you're probably better off to utilize a function module (as indicated by previous poster) in case you worry about versioning.

However, instead of using function module IDOC_COMPLETE_SEGMENT_READ, I'd use SEGMENT_READ_COMPLETE, because the latter is released. Should you need complete IDoc information use IDOCTYPE_READ_COMPLETE.

Cheers, harald