idocs, idoc types, tables

can anybody tell me what type of idoc types are typically used in a regular order to cash cycle in sd .

and are there tables related to it?

what is the tcode to see them

n.bhardwaj

my id is

nehabhardwaj01@gmail.com

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (2)

Dear Neha,

Idoc Types:

ORDERS01 Purchasing/Sales

ORDERS02 Purchasing/Sales

ORDERS03 Purchasing/Sales

ORDERS04 Purchasing/Sales

ORDERS05 Purchasing/Sales

INVCON01 Stock change data for inventory controlling

INVCON02 Stock Change Data for Inventory Controlling

INVOIC01 Invoice/Billing document

INVOIC02 Invoice/Billing document

INV_ID01 Invoice

DELFOR01 Delivery schedule/JIT schedule

DELFOR02 Delivery Schedule/JIT Schedule

DELIVERYPROCESSING_EXECUTE01 Delivery processing

DELVRY01 Delivery interface

DELVRY02 Delivery interface with dangerous goods data

DELVRY03 Delivery interface

DELVRY04 Delivery interface

You can view Idoc types in transaction WE30.

WE02/WE05 for displaying IDOCs.

WE19 for testing IDOCs.

ALE and IDOC:

ALE stands for Application Link Enabling and is used for distribution of data. IDOC is an Intermediate Document. It carries the application data from one server to another server.It uses the RFC(Remote Function call) .

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.

It is the the combination of Segements.

Segment : All the required fields will get assigned in relavant segement.Like that we will have lot of segments.We will assign all the segments to IDOC type.In the required level(Parent & child level .Like tree nodes).

Idocs Type is a Structure by lot of segments.

IDOC is generared at the time of run time .

It will have the data.

There are basically two types of IDOCs.

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

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

http://www.allsaplinks.com/idoc_sample.html

http://www.allsaplinks.com/

http://www.sap-img.com/

http://www.sappoint.com/abap.html

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf