| Home • Tips • Tutorials • Forums • Certification Q's • Interview Q's • Jobs • Testimonials • Contact Us | ||
Document Categories:
What's New?
Contribute?Sample SpecsWhat's Hot? |
Creation of Custom IDOC TypeBy Sarang Kahu 1.Business
Case
SAP R/3 systems send out data through IDoc (Intermediate Document), which in internally has segments and fields containing the data. But sometimes, these fields are not sufficient for a specific end-to-end business scenario as far as data transfer is concerned. So in such scenario, either few fields are to be added or subtracted, or completely new structure- IDoc needs to be created. This are called as Custom – IDOC Types. Following blog gives out step-by-step approach for creation of the same. 2.Development
of IDOC types
2.1 Creation of Segment Types
Run T-code ‘WE31’ to create segment type, which has
fields to contain the data and are added to the segment type in the same
transaction. The data stored contained into the segment mesh is finally stored
in EDISEGMENT table.
Add your custom fields as per business scenario.
To make it available to other transactions, release the
segment created. Go to Edit -> Set Release 2.2
Creation of IDoc type
Run T-code ‘WE30’ to create custom IDoc type. Enter
the name of custom IDoc you want to create and click on red box for creation.
Now, it takes you to following screen. Here you can add
description for your IDoc type. Also you can specify name of existing IDoc for
Copy or Successor mode. Now, you can maintain attributes of the custom IDoc,
which consists of attaching segment type created above to the IDoc type. Also
specifying the details of frequency of these segments getting filled i.e.
Maximum and Minimum number. Fill the necessary details and release this IDoc
type as well. 2.3
Creation of logical message types
Run T-code ‘WE81’ to create the logical message
types. Go to Edit mode and click New Entry to go to following screen.
Save the entered data. 2.4
Linking Message type and IDoc type.
Run T-Code ‘WE82’. Now we have to link these created
IDoc types and Message types. Enter the message type name, Basic IDoc type (ZCUST_IDC)
and release type to be linked. In the data transfer through ALE, these message
types represent the IDOC structure.
Extension field above will be used as per the Extended
IDoc type scenario i.e. in case of addition of few more fields into the existing
IDoc type. Hence, now our Creation of Custom IDoc is ready to use in ALE scenarios.
|
|
|
Please send us your feedback/suggestions at webmaster@SAPTechnical.COM Home • Contribute • About Us • Privacy • Terms Of Use • Disclaimer • Safe • Companies: Advertise on SAPTechnical.COM | Post Job • Contact Us ©2006-2007 SAPTechnical.COM. All rights reserved. All
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG. Graphic Design by Round the Bend Wizards |
||