Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

creating an idoc

Former Member
0 Likes
659

Hi All

i have a requirement where i have to design a screen program to provide the user with a input screen. The user will input data on this screen, after the user enters the data and clicks on execute button on the module screen the system must generate a IDOC in the system. This IDOC will be picked up from another program within the same system.reson for this is we dont want ot use we19 and want to test our idoc this way.

Thanks and Regards,

Gunjan

5 REPLIES 5
Read only

Former Member
0 Likes
626

You can Create IDoc in this process :and transfer masterdata from one system to another.

you can transfer Master data in Bulk through SMD(Share masterdata tool) Tool.

The main SMD tools in SAP are BD10 for Material Master

BD12- customer

BD14- Vendor

Suppose u want to transfer material in bulk.

u have configure the systems :

TA:SALE for ale customization -


create logical system here.

Steps:

1) Create port(WE21) and logical system and RFC destination(SM59)

1) Create Distribution Model in BD64.

2) Create Partner Profile (WE20)in both systems and disrtibute the model and in receiver system the model will be created itself after distribution.

3) Go to TA :BD10(SMD for material)

4) message type will be MATMASand specify the logical system and press execute.

it will generate the master IDoc and communication IDoc in sender system

now u can chk the receiver system the Inbound IDOC must be there wth all the materials

TA for IDOC CHK :WE02,WE05.

Go through This link too:PDF Index.IDoc

for any funther clarification get back to me

Regards,

Nisha

<b>@award pts if Helpful.</b>

Regards...

Abhay Singh.

Read only

Former Member
0 Likes
626

An IDoc is made up of the following parts:

Control Record: This section contains control information regarding the Idoc. Its constituents are Sender’s name, Receiver name, Message type and Idoc type (illustrated in figure 3). The format of the control record is similar for all IDoc types.

Data Segment: It consists of a header that contains the identity of the Idoc. Its constituents include, a sequential segment number, a segment type description and field containing the actual data of the segment.

Status records: The status record shows the information regarding the already processed stages and remaining processing stages of the Idoc. It has an identical format for each IDoc type.

T code for Idoc

WE30 -- develope Idoc types

WE02 -- Idoc list

WE09 -- Idoc testing tool

<b>Reward points if u helpful</b>

Read only

Former Member
0 Likes
626

for test purposes you can use the transaction WE19. With the help of this transaction you can create a new IDOC as a copy of an existing IDOC. If necessary, you can edit the newly created IDOC. So, the transaction WE19 creates a new (copied from another) IDOC.

On the SD side in the most cases we work with inbound IDOCs. So, we should not create a new IDOC, but should apply the coming (from MM) IDOC.

Only OrderResponse and Invoice IDOCs are created within the SD module. For creating the OrderResponse IDOC you have to use the same tools as for printing the sales order. Only in Output control you should create an IDOc instead of printed document. For creating the IDOC itself you have to use then the report RSNAST00. The creation takes place in the function module IDOC_OUTPUT_ORDRSP .

<b>I hope, this information helps you a little bit further.</b>

Read only

Former Member
0 Likes
626

hi

just refer to the link below <b>step by step procedure</b>

http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g

regards

ravish

<b>plz dont forget to reward points if helpful</b>