cancel
Showing results for 
Search instead for 
Did you mean: 

idocs

Former Member
0 Kudos

Hello SAP gurus

Could please let me know all the transactions related to IDOCS.

Thanks for your help

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Transaction Related to IDOCS are as follows:

1. T-Code - WE02 (Idoc List)

By selection criteria we can find out the required Idoc.

2. T-code - WE30 for getting information about segments

3. T-code VOE2

4. T-code -VOE4 ,the table for this screen is EDPAR for making customer EDI

5. T-code WE20: Partner Profiles

6. T-code WE21- PORT DETAILS

Reward if it is helpful

nisha_sharma1
Active Contributor
0 Kudos

Hello,

All the transactions related to Idocs can be seen in WEDI -area menu.

in Transaction SALE you can create logical systems. Chk this one too.

and go to transaction SE16 and eneter the table name TSTC

in search crieteria enter BD* for transactions.

you will get all the transactions for IDOC scenario set up. reagrding message type , Function Module assignment to process code . which are inturn associated to message type like (DELINS, Desadv messsage types)

same procedure you can repeat with WE*

this will help you.

Regards,

Nisha

@ award pts , if useful.

Former Member
0 Kudos

Go to WEDI which is area menu.

take /nwedi in your command field it will take you to that menu.

here you can find all the transactions releted to idocs.

In this WE02, WE05, WE09, WE19&20 are imp onces

Former Member
0 Kudos

Hi,

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.

A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.

IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.

An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.

There are basically two types of IDOCs.

Basic IDOCs

Extended IDOCs

Idoc Components

Basic Idoc

Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.

Extension Idoc

Extending the functionality by adding more segments to existing Basic IDOCs.

Creation of IDoc

To Create Idoc we need to follow these steps:

Create Segment ( WE31)

Create Idoc Type ( WE30)

Create Message Type ( WE81)

Assign Idoc Type to Message Type ( WE82)

Creating a Segment

Go to transaction code WE31

Enter the name for your segment type and click on the Create icon

Type the short text

Enter the variable names and data elements

Save it and go back

Go to Edit -> Set Release

Follow steps to create more number of segments

Create IDOC Type

Go to transaction code WE30

Enter the Object Name, select Basic type and click Create icon

Select the create new option and enter a description for your basic IDOC type and press enter

Select the IDOC Name and click Create icon

The system prompts us to enter a segment type and its attributes

Choose the appropriate values and press Enter

The system transfers the name of the segment type to the IDOC editor.

Create IDOC Type

Follow these steps to add more number of segments to Parent or as Parent-child relation

Save it and go back

Go to Edit -> Set release

Create Message Type

Go to transaction code WE81

Change the details from Display mode to Change mode

After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter

Click New Entries to create new Message Type

Fill details

Save it and go back

Assign Message Type to IDoc Type

Go to transaction code WE82

Change the details from Display mode to Change mode

After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.

Click New Entries to create new Message Type.

Fill details

Save it and go back

Reward points pls.

Regards,

Govind.

Former Member
0 Kudos

Thalapalli,

Please Find below the Important T.Codes Realted to IDocs:

WE02 - Idoc list

WE05

WE09 -- Idoc testing tool

WE19

WE20

WE21

WE30 -- develop Idoc types

BD87

BD12- customer

BD14- Vendor

Please Reward If Really Helpful,

Thanks adn Regards,

Sateesh.Kandula

Former Member
0 Kudos

Hi,

IDOC:-

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.

Award points if it helps.

Thanks

Mohan