IDOC

[Former Member]

Hi Friends,

What is the use with "IDOC" in sap and how it works?

Pls give me the inputs

Thanks in advance

N.M.B

[bpawanchand]

Hi

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/ale+idocs

Check SDN Forums you ll find lot of stuff.

Regards

Pavan

[Former Member]

IDOCs Detailed Information Configuration

Definition

"EDI is described as the interchange of structured data according to agreed message standards between computer

systems, by electronic means. Structured data equates to a simple and direct method of presenting the data

content of a document. The method of ensuring the correct interpretation of the information by the computer

system is defined by the EDI standard."

EDI is a technique used to communicate business transactions between computer systems of different companies

and organizations. Note that sometimes the EDI mechanism deployed at a company is often used to interface to

other systems within the same organization."

Some thoughts

You should not to attempt to switch to a full SAP EDI implementation overnight. It takes time for people, systems,

and processes to adapt to any new methodology. Implementing SAP EDI is a project in its own right and needs to

be handled phase by phase as in any other information system implementation. We describe some of the issues

and how to implement an SAP EDI solution in the following pages.

What Is IDOC

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.

What are the main advantages of IDOC?

IDoc is the data Format used by the SAP in data transfer using ALE /EDI methods. They provide more data

security. An IDoc is an intermediate document used to send data in two ways, that is internal and the external

point for you.

In BW, IDoc is a transfer mode, when you create a Infosource you can select the transfer mode as PSA or IDOC.

Its the method provided for backward compatibility. In older version the hirerchies where loaded using IDOC

transfer method. Now its possible with PSA but still that method is available to load the hierarchies.

An example in SD:

For creating sales documents (sales order) through IDOCS you will have to use the T code WE19. In that click

basic type and enter order05(IDOC type) and select via message type then enter ORDERS(message type), click

execute.

You will get to see many fields.here you have to enter the datas that you enter in the VA01 screen in order to

create sales order. The datas such as material name, date, qty, P.O no etc. After entering all the datas, you click

standard inbound the IDOC would be created by the system.You can see the created order by going in to VA03

screen.

Next time when you create the IDOC, in same tcode WE19 screen, click existing IDOC and enter the IDOC which

you created in the above step and just change the P.O no.Sytem will create new sales order through new IDOC

Before doing all you need to maintain the partner profile in T code WE20. For this Discuss with EDI consultant.

Difference Between EDI and IDOC

EDI is nothing but Electronic data interchange. SAP will support EDI through Intermediate documents

(IDOCS).

EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between

the computer systems of business partners, using a standard format over a communication network.

EDI is also called paperless exchange.

Advantages:

Reduced Data entry errors

Reduced processing time

Availability of data in electronic form

Reduced paperwork

Reduced Cost

Reduced inventories and better planning

Standard means of communications

Better business process

EDI has two processes

1. Outbound process.

2. Inbound process.

OP:

1.Application document is created.

2.IDOC is generated

3.IDoc is transferred from SAP to Operating system layer

4.Idoc is converted into EDI standards

5.Edi document is transmitted to the business partner

6.The Edi Subsystem report status to SAP

IP:

1.EDI transmission received

2.EDI document is converted into an IDOC

3.IDOC is transferred to the SAP layer

4.The application document is created

5.The application document can be viewed.

IDOC:

IDOC is a container that can be used to exchange data between any two processes.

Each iDoc is assigned a unique number for tracking and future reference.

iDoc Consist of several segments, and segments contain several fields.

iDoc contains the following three type of records...

1.One Control Record.

2.One or many Data Record

3.One or many Status record.

PORT:

Port is used in the outbound process to determine the name of the EDI subsystem program, the directory path

where the idoc file will be created at the operating system level, the idoc file names and the RFC designations.

RFC Destination:

Used to define the characteristics of communication links to a remote system on which a functions needs to be

executed.

Partner Profile:

Partner profile specified the various components used in an outbound process ( Partner number, IDoc type,

message type, Port, Process code),the mode in which it communicates with the subsystem(batch or immediate)

and the person to be notified in case of errors.

Message Control

Used in pricing, account determination, material determination, and output determination. The message control

component enables you to encapsulate business rules without having to write abap programs.

Process:

Setup RFC destinations SM59

Port Destinations WE21

Partner Profile WE20

Message control NACE

Purchase Order ME21

Check IDOCs WE02,WE05

Created change pointers related to message types like MATMAS and LOIBOM by keeping specific conditions

(running a background job). so server created lakhs of Idocs. Due to this sever is running very very slow.

Delete/Remove of IDocs from R3 [Covered from Search]

You may delete it from BD87.

This is also used for processing, but there is an

option to mark it for deletion

In BD87 - uncheck the option that says "Process in Background", and it will

take you into a screen that looks like the workitem for a failed idoc in

your inbox.

Click the "Delete Flag" button, and this will mark the idoc for deletion at

the next archiving run

Use the instructions below. I think the transaction

should be BD73. (Not BD87)

Recently I discovered transaction we11 (report RSETESTD), with this transaction you can delete sap idocs. No, I'm

not talking about deleting as the last step of idoc archiving, I'm talking about simple straight forward deletion of

idocs from the database

First things first, transaction we11 really works, the idocs are successfully deleted from the database.

Second, as opposed to archiving idocs, we11 will delete idocs regardless of their processing status (idoc archiving

using transaction sara, only works for successfully processed idocs). This may be good or bad for you, it largely

depends on your needs.

I also regulary delete IDOC, but I use RSEXARCB in the background job.

Since you mentioned 'delete' I assume that both programs RSEXARCA and RSEXARCB Archive & Delete at the same time.

Please use Object Idoc from SARA. If you use this it will write file using program RSEXARCA and delets using RSEXARCD.

Take a look at running report RBDCPCLR from SE38 in the backgorund. You will probably have to up a varient we

run the report weekely and keep the last 6 weeks of data. You will be removing from table BDCPS take a look and

it will all make sense.

Report RBDCPCLR selection screen is for deleting change pointers. My question is deleting IDocs which are created

by Change Pointers. Please guide me to next step. What should I do......

Aplogises thought that we were talking change pointers ....

"There is no special deletion program for IDocs.

Use the archiving programs. IDoc is a separate archiving class. The following programs are available:

1. Archive RSEXARCA and RSEXARCB (as of Release 3.0C)

2. Delete RSEXARCD

3. Read archive RSEXARCR

4. Restore RSEXARCL

The Idoc archiving is checked against the status. The statuses which can be archived and those that cannot be

archived are stored in the "Status maintenance" table. You can change the standard settings. Menu path:

Area menu "WEDI", control, status maintenance.

The archiving procedure is described in the documentation 'IDoc interface for EDI'."

I tried as like you said, first tried with RSEXARCA (Archived) then deleted from SAP R/3 RSEXARCD(Deleted from

R/3) I tried this for few IDocs and it worked fine.

but after tried for more no of IDocs(20000). then given like 'last create archive file without data objects was

deleted' for report RSEXARCA. and not showed any thing for report RSEXARCD.

I am not that familiar with the transaction but it may be possible to break down the IDOCS in to batches of 5000

and run these in the background ??

Have you checked the customizing for object 'IDOC' - I mean not only in transaction SARA but also the

application-related customizing. There might be a parameter, defining the minimun-duration time of idocs ...

unfortunately I don't remember the transaction ...

[Former Member]

Hello,

U go through saptechnical.com

here u can understand very easily because here step by step process .

Regards:

Prabu

[Former Member]

The IDoc interface function is under Tools ® IDoc Interface/ALE in the SAP menu.

Follow this link

http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b809b43d711d1893e0000e8323c4f/frameset.htm

[Former Member]

Dear friends,

I am a functionl consultant, so i don' want tonnes of data regarding this. friends pls give me brief information.

Thanks

[rainer_hbenthal]

What has this to do with ABAP?

[Former Member]

Hi,

Check the following link:

http://www.sapdb.info/wp-content/uploads/2008/08/idoc-and-ale.pdf

Regards,

Bhaskar