on 06-09-2008 11:18 PM
Someone knows where to find the description of an IDoc means what an IDoc is suppose to do?
Thanks in advance.
Check we60 on R/3 side
Thanx
Aamir
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI
Idoc is a data container itu2019s not a process, these are stored in database tables and each idoc has a unique number. Idocs are independent of direction of adapt exchange. Idocs are based on EDI Standards and close to EDIFACT. Idocs can be viewed in text editor and do not contain any binary data.
Workflow is used to control and co-ordinate the sequence of steps in a business process
Idocs are of 2 types.
1. Master IDOC.
2. Communication IDOC.
Master Idoc is a temporary idoc and it is not stored in database table.
First of all master idoc is created and if it succeeds in validations, it is converted to communication idoc.
Idoc Structure is of 2 types.
1. Basic
2. Extension
A basic idoc type will have the following characteristics:
Name: Can be up to 30 characters
List of permitted segments
Hierarchy of segments
Mandatory vs. Optional segments
Maximum/Minimum Range for segments.
Information hold by IDOCS is of 3 types. They are:
Control Record: Specifies Sender & receiver information.
Data Record: Contains data to be transferred.
Status Record: Contains status of IDOC.
Format of IDOC in Control Record: EDIDC
Message Type
Idoc Structure
Direction -1 or 2 1 is for outbound & 2 is for Inbound
Port [Receiver]
Partner Number [Logical System Name]
Partner Type
Format of IDOC in Data Record: EDIDD
Segment Name - SDATA (1000)
Format of IDOC in Status Record is EDIDS.
Segments: Segments will define format and structure of data record. Segments are reusable components. Segments contains field that represent data in data record.
Segments can hold only 1000 characters of data, if it exceeds new segment will be created.
The following are segment components:
Segment Type: It is the name of segment. Starts with u2018E1u2019 for sap defined and Starts with u2018Z1u2019 for user defined.
Segment Definition: It canu2019t be >1000 bytes and starts with E2 for sap defined and starts with Z2 for user defined
Segment Documentation: Represents data dictionary documentation for each field. Starts with E3 for sap defines and u2018Z3u2019 for user defined.
Segments get created as structure in dictionary and every segment must be released. Generally Release no for outbound is 620 and 640 for inbound.
Set release means, changes are made permanent. To make any changes to released segment, first cancel the release, then make necessary changes, save then release again.
Transaction Ports: These are used to transfer idoc between r/3 systems.
File ports: These are used to transfer idocs to sub systems in form of files.
Outbound programs referred as u2018IDOC Generatorsu2019
Inbound programs called as u2018POSTING Programsu2019.
Posting programs are implemented as function modules and are generally named as u2018IDOC_INPUT_<MSG TYPE>.
Status of IDOC:
01 - Initial status.
30 - Ready for dispatch
03 - Waiting at port.
12 - Reached Destination.
Modes of Transport: Outbound & Inbound
Outbound and Inbound numbers of idoc will not be same but data is same.
Reduced Message Type: To suppress some segments of standard structure.
Extended Idocs: Adding some new segments to existing idocs.
SOLD-TO-PARTY: Customer who placed order.
SHIP-TO-PARTY: To whom goods are sent
BILL-TO-PARTY: To whom bill is sent.
Transaction codes for IDOCS:
WE32 - Idoc Views
WE60 - Documentation for Idocs
WE61 - Documentation for IDOC record types
WE62 - Documentation for IDOC segment types
VOFM- Requirements & formulas used in message controls
SM51 - List of application servers running
SM59 - To create RFC destination
WE64 - Process code in Inbound & outbound IDOC.
BD59 - To create field level filter
WE02 - Transaction for idoc list display
WE05 - Transaction for idoc list display
cheers
reward points if found useful
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Idoc is an inter medieat document ..using this we can exchange the data between two different SAp systems.
The messages exchanged between systems are of various message types. The message type depends on the data contained and the process involved. It determines the technical structure of the message, the IDoc type. For example, the FIDCMT message type is used for journal messages.
The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.
An IDoc type consists of the following components:
· a control record
This is identical for each IDoc type.
· several data records
One data record consists of a fixed key part and a variable data part. The data part is interpreted using segments, which differ depending on the IDoc type selected.
· several status records
These are identical for each IDoc type and describe the statuses an IDoc has already passed through or the status an IDoc has attained.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
WE60 and the Basic Type will provide you with all the information you require.
Thanks
Saiyog
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
what an IDoc is suppose to do?
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.
Idoc creation
IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
regards
chandrakanth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
try t-code we60, here you can give the IDoc type and it displays the idoc structure in a descriptive html format.
Please reward points if it helps
Thanks
Vikranth
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You can get the all description from below tcodes
WE60-> Documentation for IDoc types
WE09-> Search for IDocs by Content
BD87-> Status Monitor for ALE Messages
WE63 -- information about Standard IDOC in R/3
WE64 - Details about process codes
WE82, WE30, WE31 -- IDOC Types
Thanks
Swarup
Edited by: Swarup Sawant on Jun 10, 2008 5:50 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the WE60 I only can see the structure of the IDoc Am I missing something?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.