Segments of an idoc type

Hi,
i need to know the table which can be used to identify all the segments an idoc types..
Rgds,
Harikrishna Indugu.

Hi,
Use transaction WE30 to see what are the segments involved in basic types and use WE60 to see what are the segments and fields are involved in particular basic type. You can use the transaction SE11 to see what are the fields are involved in the particular Segment.
Thanks,
Asit Purbey.

Similar Messages

Custom segments to basic IDOC type without extension

Hi,
Is it possible that an IDOC has custom segments which are getting populated and the basic type does not have any custom segments.
How should we find from where the custom segments are getting populated and displayed?
Regards,
Subhashini

Hello,
Lets say in DELVRY05 Idoc Type, we have a Segment Called E1EDL20 and since this is a Standard SAP Provided Basic Type, it will not have any Custom Segments ( Z-Segments). Now, If I want some additional Information to be populated as part of a Custom Segment, what I would do is to Create an IDoc Extension ZDELVRY05 with reference to the Basic Type DELVRY05 and Create a Custom Segment Z1EDL20 (Per Say) in which I'll populate the Custom Data Fields using an Exit. So, unless we create an IDoc Extension for a Basic Type, the Standard SAP Basic Type will not have any Custom Segments-Fields (Z-Segments).
Thanks,
Venkata Phani Prasad K

Idoc segment version in idoc type

hi,
we have just upgraded our R/3 system from 4.6c to SAP ECC 6.0. We then tried to send idocs to SAP XI 3.0 SP 20. However the idocs failed due to wrong segment version of idoc. It did not match the loaded metadata in XI. I know that in WE20 you can control the segment version used to send to XI. In the communication channel in XI you can also set the segment version.
So my question is: Is the correct way to handle sytems requiring diffenrent verions to import the newest metadat in idx2 and then control the versions asper the above paragraph?
Any comments are apreciated.
kr Rasmus

Hi,
for sending IDocs to XI no adapter is necessary. It should be enough to reload the metadata in idx2:
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
Regards
Patrick

Missing E1KNVLM segment in DEBMDM IDOC TYPE

Dear Experts,
When we run mdmc transaction to create idocs for customer master data,
The debmdm idocs is geeting created with out E1KNVLM segment.
We need to retrive LICNR from the E1KNVLM, we are on ECC5.0,
Appreciate your valuable help.
Thanks and Regards.
Sravya.

Hi,
Check BD79( Creation of Rule) , is there any rule cretaed for this particulat segment .
At the same time check BD56 for any segments fileterd.
Revrt back if any issues,
regards,
Naveen

Segment Display in IDOC Type MBGMCR02

Hi,
I am creating a goods movement and an IDOC gets created. But when I see the IDOC with WE02 not all segments are displayed. What should be done to see a field ITEM_TEXT in the segment?
Thanks & Regards,
YJR.
Message was edited by: YJR

Hi,
Yeah that is fine but now the problem is I have created a conversion Rule where I use the BATCH as the imput and I would retrieve the SIZE and this value is supposed to be populated in ITEM_TEXT and this creation of conversion Rule is done and it works. But when I try to see it in WE02 the field ITEM_TEXT itself is not visible.
How should this be handled to see the field ITEM_TEXT in the first place itself.
Thanks & Regards,
YJR.

Idoc segment for shpmnt notification for idoc type shpmnt02

Hi gurus,
I have to find the idoc segment for shipment notification,idoc type which we are going to use is shpmnt02 or shpmnt01,Can any one of you please tell me the idoc segments for this idoc type with fields and table name?.Thanks in advance.

Hi Nagarathinam
You can use transaction WE60 for documentation on IDOCs
Best regards,
Chris

Adding new segment to IDoc type DELVRY03

Hello everybody!
I just got a request to add two new segments to an Idoc (type DELVRY03) under the segment E1EDL24. (E1EDL43 and E1EDL41).
They told me to use the userexit EXIT_SAPLV55K_004 to add the new segments using the table IDOC_CONTROL since it is standard. But the problem is that the changes are not been saved.
I realised that by the time that this exit is called the standard already stored the information on EDID4.
I appreciate any help!
Thanks in advance!

Hi Kumar,
If we change EDBAS table data and modify my idoc type by adding segment.
after completing process have to move my object to production.
Hope it ll through an error... because it will check with table data also for validation.
could you please justify your answer kumar?
Thanks for your helpful information.
Regards,
BALAJI.

How to add a custom segment in standard IDoc?

Hi,
I want to add a custom segment in stanard IDoc type (eg. MATMAS). I don't want to go for extended idoc (copying stanard idoc into zidoc and adding custom segment).
Please tell me.

Hello
Transaction BD10 uses fm MASTERIDOC_CREATE_REQ_MATMAS which in turn uses MASTERIDOC_CREATE_MATMAS to create and distribute material master IDocs.
Fm MASTERIDOC_CREATE_MATMAS belongs to function group MV01 in package MGV. Here you will find the user-exit function group XMGV.
Perhaps EXIT_SAPLMV01_002 might be useful for you.
Regards
Uwe

Why message type if idoc type or idoc is already there.

Experts.
this has been posted several times and i gone through so many threads but stil some confusion . So anyone can tell in simple terms what is the difference and why sap has given this two instead of one.
Diff. with IDOC type
An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data
*****from the above statements , by seeing the name of the idoc type ex matmas01 also we ca n say that it is used for material data, then why message type matmas needed?

Hi,
Idoc type means combination of segements
Message type means Combination of idoc type
or
Message type mean combination of Idoc type + Extension idoc type( Custom segments added to idoc type)..
Example:-
If you want to fill the data to custom segment which is available at exension idoc ...
then first check the message type then check basic idoc type then check it contains exetension idoc type ..then fill the segment
Generally the communication occurs between system through message type...
Prabhudas

Adding fields to custom idoc type

Hi,
i have a query regarding adding fields to custom idoc type.
To add fields to custom idoc type we are trying to cancel the release from we30, but we are facing error that 'The release of basis type cannot be reset'
When we are trying to cancel release from we31we are facing error 'Error while ressting release of segment z type'.
Kindly suggest the solution to add fields in basic idoc type.
Thanks & regards,
Farheen.

Reason that you are getting these errors is that you cannot cancel
the release of an extension made in previous version . Instead you have to create a new extension.
1.It is not possible to change a segment definition which is released in a
lower release.
2.You must create a new segment definition for the new release e.g. 620 with a new segment
field with the appropriate length.
In transaction WE20, outbound parameters, you can specify
the "segment release in IDoc type" for the communication.
Please read the F1 help of this field for further information.
3.For your own segments you can define a new version of the segment
tcode WE31 -> Add Version
Thanks!

Nhi guru's cross apps what is basic type,idoc type , message type

nhi guru's cross apps what is basic type,idoc type , message type plz help me i am larning how to work on idocs using ale explain me like realtime environment

Hi,
Hi,
i got this data from sdn .plz go thru might be helpful
IDOC is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
how to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
For creating a IDOC u need to Create a segment type in WE31.The internal table in which we store the data to be passed to the IDOc thos fielda are defined in fieldname and data element.Save and release the segment.
Create IDOC type in WE30. Give min and max types. Mark it as mandatory.
Create Message type in WE81.Assign it to a change request and save it.
Link this message type with IDOC type in WE82.
Then start your coding and pass the details of Data and control records.
Just have a look at these links:
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
Creation of IDOC:
idoc creation
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=creation%20of%20idoc&cat=sdn_all&start=11
ALE/ IDOChttp://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
i think this will helps u
<b>reward is usefull</b>

New Header Segment in Extension IDoc

Hi,
I want to create a new header segment in Extension IDoc.
I am not able to create. I want to extend the Basic IDoc DESADV01 by adding a new header segment (Batch numbers, ID's and with time stamp).
The remaining segments should be under this segment only.
Is it possible that or shall I create Custom IDoc?
Thanks in advance.

Hi,
You can not create new header segment when extending IDoc type DESADV01.
System only allows you to insert as child segment instead.
If you still want to create new header segment, then you need to create a custom IDoc.
Regards,
Ferry Lianto

Segment Hierarchy - DEBMAS IDOC Creation

Hi All,
I am able to create a DEBMAS Idoc successfully but the segment hierarchy does not seem to be right.
Can somebody tell me what fields are to be filled to create the correct segment hierarchy or point me to a standard program where DEBMAS idoc segments are filled?
Thanks,
Meghna

Hi,
there is no distribution of customer hierarchy.
Therefore you will not find a proper segment in DEBMAS* idocs types
You may look at [note 548716|https://service.sap.com/sap/support/notes/548716].
BR
Alain

Populating the custom segments for the Basic type attached to HRMD_A (IDOC)

Hi,
I've enhanced a few infotypes and want the new fields to be available in an IDOC created through the program RHALEINI.
Here are the steps I followed.
Step 1 :(we31)
We created new segment Z1IT023 , containing all the fields from infotype 0023 along with the custom fields added.
Step 2 :(we30)
We created an extension of IDOC type HRMD_A07 by name HRMD_EX to include this segement.
Step 3 :
We added an entry in table EDIMSG against message type HRMD_A , with base type : HRMD_A07 , extension : HRMD_EX , version : 700
Step4 :(we20)
Now , we made changes to partner profile by adding entry for message type HRMD_A with base IDOC type as HRMD_A07 and extension as HRMD_EX
Step5:
We changed the entry in table T777D and specified the IDOC segment as Z1IT023.
Step6.
We then tried to execute the report RHALEINI to generate the IDOC. The IDOC got created, but it didn't have the data for the segment Z1IT023.
In fact, there is a different solution to this... by adding the custom segment(containing nly the new infotype fields) as a child of the original segment E1P0023 and then writting code in the user-exit to populate the segment, but our intension is to have a single segment with all the infotype 0023 data. Besides, I believe in HR, making an entry in T777D should free us from writing any code for populating the IDOC segments.
Can anybody please suggest me, where am I going wrong. How can the new segments be populated automatically.
Thanks in advance.
Sujit.
Responses will be suitably rewarded.

Hi,
Did u get any exit to populate the custom segment?
Thanks,
San

Flat File IDOC - ECC, segment defn x in IDoc type y CIM type do not exist

Hi,
I'm working on idoc flat file > sap scenario. Everything seems to be working up until the point where I get an error message:
EDISDEF: Port EDIPORT segment defn E2FINBU000 in IDoc type FIDCCP01 CIM type do not exist
I've loaded the meta data, and the file structure is fine. I believe the issue is related to PI not having the idoc I'm interested in listed in WE30. How do I reference the standard IDOC type FIDCCP01? Ideas I've had are around SWCV or transport from another system, the first I'm not sure which SWCV, the later seems a bit of a bodge and I dont like the idea.
Thanks
James.

Hmm.. some light for the situation. Seems that the segments imported are:
E1FINBU     E2FINBU     31I
E1FINBU     E2FINBU001     40A
E1FINBU     E2FINBU002     40B
E1FINBU     E2FINBU003     45A
E1FINBU     E2FINBU004     45B
E1FINBU     E2FINBU005     46A
E1FINBU     E2FINBU006     46C
Which indeed does not have E2FINBU000, which the IDOC is most definitely trying to pass. I can only guess that the middleware producting this IDOC is flawed, and that standard SAP ALE will accept this as E2FINBU (It works into another SAP system without XI).
Guess I've answered my own question, but feel free to offer light for points
Thanks,
James.

Segments of an idoc type

Similar Messages

Maybe you are looking for