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

idocs

Former Member
0 Likes
601

hello,

can anybody give me the proper information about the following topics ?

IDOC Tools

Testing Tools for IDOC

Reporting Tools for IDOC

Thank you very much.

Regards,

Vijaya.

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
578

Hi ,

Check below..

IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an

asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.

While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.

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

We can use the IDocs

From SAP to SAP and

SAP to NOn-SAP also.

For example.

SAP TO SAP : By useing ALE we can send the data from SAP to SAP.

SAP to Non-SAP : By using EDI (Here we will use third party tools : Mercator) we can transfer SAP to Non SAP.

In EDI each servers will have one third party tool each.

This information is copied of one of sdn thread.

you can also refer many documents in SDN, it is source of SAP information..!!

hope this will give you some clue.

//Kiran Singh

3 REPLIES 3
Read only

Former Member
0 Likes
579

Hi ,

Check below..

IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an

asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.

While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.

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

We can use the IDocs

From SAP to SAP and

SAP to NOn-SAP also.

For example.

SAP TO SAP : By useing ALE we can send the data from SAP to SAP.

SAP to Non-SAP : By using EDI (Here we will use third party tools : Mercator) we can transfer SAP to Non SAP.

In EDI each servers will have one third party tool each.

This information is copied of one of sdn thread.

you can also refer many documents in SDN, it is source of SAP information..!!

hope this will give you some clue.

//Kiran Singh

Read only

Former Member
0 Likes
578

Hi,

Testing tool :

you can send a test IDoc with transaction WE19.

It's also described here:

[https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1819] [original link is broken] [original link is broken] [original link is broken];

[https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2923] [original link is broken] [original link is broken] [original link is broken];

Pls. reward if useful...

Read only

Former Member