idoc segment fields

Former Member — Fri, 31 Jul 2009 19:03:41 GMT

experts

which tcode is used to see the idoc segement fields basically i want to see the orders01 idoc segment fields,

I checked we60 ,we30 etc but not much use. I want to see the descripton of the fields as well. I mean i want to know which field for sales org , which field for po in sales order etc

Re: idoc segment fields

Former Member — Fri, 31 Jul 2009 19:07:26 GMT

Hi ,

Check tcode-WE61.

Regards,

Himanshu V

Re: idoc segment fields

Former Member — Sat, 01 Aug 2009 04:11:59 GMT

thanks verma.

is there any other tcode which gives the discription of the fields of the segments etc

Re: idoc segment fields

alex_m — Sat, 01 Aug 2009 06:39:45 GMT

WE61 itself you can find the description of the fields & segments...

Re: idoc segment fields

Former Member — Sat, 01 Aug 2009 11:01:37 GMT

Hello,

Try transaction code WE31.

Thanks,

Augustin.

Re: idoc segment fields

Former Member — Sat, 01 Aug 2009 11:20:53 GMT

Hi,

Here is a brief info to find field segments of an idoc.

Interpreting an IDoc Segment Info

All IDoc data records are exchanged in a fixed format, regardless of the segment type. The segmentu2019s true structure is stored in R/3u2019s repository as a DDic structure of the same name.

R/3 is only interested in the segment name

The segment info tells the IDoc processor how the current segment data is structured and should be interpreted. The information, which is usually the only interest, is the name of the segment EDID4-SEGNAM.

Segment name tells the data structure

The segment name corresponds to a data dictionary structure with the same name, which has been created automatically when defining the IDoc segment definition with transaction WE31 .

Remaining information is only for foreign systems

For most applications, the remaining information in the segment info can be ignored as being redundant. Some older, non-SAP-compliant partners may require it. E.g. the IDoc segment info will also store the unique segment number for systems, which require numeric segment identification.

To have the segment made up for processing in an ABAP, it is usually wise to move the segment data into a structure, which matches the segment definition.

For a segment of type e1maram the following coding is commonly used:

Data in EDID4-SDATA 
TABLES: e1maram.
   . . . 
MOVE edidd-sdata TO e1maram.

Then you can access the fields of the IDoc segment EDIDD-SDATA as fields of the structure e1maram .

Data in EDID4-SDATA 
WRITE: e1maram-matnr.

Sample coding

The following coding sample, shows how you may read a MATMAS IDoc and extract the data for the MARA and MARC segments to some internal variables and tables.

DATA: tmarc AS STANDARD TABLE OF e1marcm 

            WITH HEADER LINE.

LOOP AT edidd.

   CASE edidd-segnam.

         WHEN 'E1MARAM'.

          MOVE edidd-sdata TO xmara.

         WHEN 'E1MARCM'.

           MOVE edidd-sdata TO tmarc.

          APPEND tmarc.

   ENDCASE.

ENDLOOP.

Hope this solves your problem.

Thank you,

Pavan.

topic Re: idoc segment fields in Application Development and Automation Discussions

idoc segment fields

Re: idoc segment fields

Re: idoc segment fields

Re: idoc segment fields

Re: idoc segment fields

Re: idoc segment fields