sitemap
 | |  | |  | |  | |  | |  | |  | |  | |  |
IDOC mean Intermediate document. As the name stands for, idoc is a contained that holds data and used to transfer
information between any two systems.
Any IDOC is a result of an ALE or EDI process.
IDOCS are stored in a database tables and every idoc ahs its unique number assigned to it. The beauty of the idoc is it is
independent of any system , i.e it is not dependent of sending system or receiving system. Only thing is the sending and
receiving systems should understand its language, syntax and semantics of the idoc.
IDOCS can be viewed in a text editor.
IDOC documentation:
Idoc documentation can be seen in the transaction WE60. go to transaction we60 and give some idoc , for example give
orders05 and see for its documentation. The output that displayed will be stored in the form of a web page also.
The displayed report gives the complete documentation related to that idoc like the different segments it contains and the
purpose of the segment. So by seeing the purpose of each segment you can later extend the segment in idoc extensions.
Different function modules are there to see the data from any idoc. You can get use of those function modules to read
any idoc you want.
An idoc has typically consists of 3 records.
1 Control record
2 Data record
3 Status record
BASIC IDOC type is defined as the actual structure an the format of the actual business transaction document that is to
be transferred between two systems. Imagine you are sending a piece of paper through your secretary from your cabin
to one person in production department. Here you can say your secretary is media like ale or edi that takes the
paper(data / business data). Your cabin is the sending system and production dept is the receiving system. As simple as it
is.
Idoc versions are maintained in general with incrementing its last digits. For example..
Orders01, order02, orders03 are three versions orders03 is the latest version that is enhanced version. When a new
version is created the segments that exists in the older version will not be deleted.
Typically, the segments together make an idoc structure.
Hierarchy segments means a sort of parent and child relation between segments. A child segment cannot exist with out a
parent segment.
While we are defining a segment type for an idoc we need to mention whether the segment is mandatory or optional.
information between any two systems.
Any IDOC is a result of an ALE or EDI process.
IDOCS are stored in a database tables and every idoc ahs its unique number assigned to it. The beauty of the idoc is it is
independent of any system , i.e it is not dependent of sending system or receiving system. Only thing is the sending and
receiving systems should understand its language, syntax and semantics of the idoc.
IDOCS can be viewed in a text editor.
IDOC documentation:
Idoc documentation can be seen in the transaction WE60. go to transaction we60 and give some idoc , for example give
orders05 and see for its documentation. The output that displayed will be stored in the form of a web page also.
The displayed report gives the complete documentation related to that idoc like the different segments it contains and the
purpose of the segment. So by seeing the purpose of each segment you can later extend the segment in idoc extensions.
Different function modules are there to see the data from any idoc. You can get use of those function modules to read
any idoc you want.
An idoc has typically consists of 3 records.
1 Control record
2 Data record
3 Status record
BASIC IDOC type is defined as the actual structure an the format of the actual business transaction document that is to
be transferred between two systems. Imagine you are sending a piece of paper through your secretary from your cabin
to one person in production department. Here you can say your secretary is media like ale or edi that takes the
paper(data / business data). Your cabin is the sending system and production dept is the receiving system. As simple as it
is.
Idoc versions are maintained in general with incrementing its last digits. For example..
Orders01, order02, orders03 are three versions orders03 is the latest version that is enhanced version. When a new
version is created the segments that exists in the older version will not be deleted.
Typically, the segments together make an idoc structure.
Hierarchy segments means a sort of parent and child relation between segments. A child segment cannot exist with out a
parent segment.
While we are defining a segment type for an idoc we need to mention whether the segment is mandatory or optional.
All of the product names here are trademarks of their respective companies. The site
www.allsaplinks.com no way affiliated with SAP AG. We have made every effort for the content
integrity. Information used on this site is at your own risk.
www.allsaplinks.com no way affiliated with SAP AG. We have made every effort for the content
integrity. Information used on this site is at your own risk.
| SapMaterial.com |
Segment is dividing into 3 parts.
Segment type,
Segment definition
Segment documentation
Segment type is version independent and starts with E1 or Z1(custom)
Segment definition is version dependent and starts with E2 or Z2.
Segment documentation gives information about fields in segment definition and starts with E3 or Z3.
Idoc is an instance of idoc type. There are basically 3 records in any idoc .
Control record,
Data record,
Status record.
Idoc is viewed at WE02, WE03 transaction.
Control record contains the data about idoc number, sending system info, receiving system info, and message type information.
Important transaction:
Segment creation at transaction We31.
Create IDOC WE30.(basic idoc creation)
Message type creation WE81
Attach message type to idoc WE82.
Create logical systems – SALE.
Assign logical systems to client-sale
Create rfc destination- SM59
Creating port WE21
Maintaining customer distribution model- BD64
Generate partner profile- BD82
Sending material from one client to another (outbound process)-BD10.
Idoc inbound processing- WE19.
IDOC list- WE05.
The complete Documentation of control record is viewed at WE61.
Fields in data record:
Docnum-idoc number
Counter-counter in cluster table
Segnum-segment number
Segnam-segment name
Hleve-heirarchy level
Sdata-application data
Segment type,
Segment definition
Segment documentation
Segment type is version independent and starts with E1 or Z1(custom)
Segment definition is version dependent and starts with E2 or Z2.
Segment documentation gives information about fields in segment definition and starts with E3 or Z3.
Idoc is an instance of idoc type. There are basically 3 records in any idoc .
Control record,
Data record,
Status record.
Idoc is viewed at WE02, WE03 transaction.
Control record contains the data about idoc number, sending system info, receiving system info, and message type information.
Important transaction:
Segment creation at transaction We31.
Create IDOC WE30.(basic idoc creation)
Message type creation WE81
Attach message type to idoc WE82.
Create logical systems – SALE.
Assign logical systems to client-sale
Create rfc destination- SM59
Creating port WE21
Maintaining customer distribution model- BD64
Generate partner profile- BD82
Sending material from one client to another (outbound process)-BD10.
Idoc inbound processing- WE19.
IDOC list- WE05.
The complete Documentation of control record is viewed at WE61.
Fields in data record:
Docnum-idoc number
Counter-counter in cluster table
Segnum-segment number
Segnam-segment name
Hleve-heirarchy level
Sdata-application data
For outbound system, sap passes the data to sub-system and then sub-system generates status records and sends it to sap.
In Inbound system, sap generates status records.
Status codes 0 to 49 are reserved for outbound process and 50 and above are reserved for inbound process.
Status records generated by sap and stored in edids table. The key for this table is idoc number.
The complete documentation of status records can be viewed at we61.
Fields in status records table:
Docnum-idoc number
Logdat-date of status information
Logtim-time of status info
Countr-edi status number
Credit-status record create date
Status-status of idoc
IDOC development is a 3 step process.
Create new idoc or extend an existing idoc.
Write a program for this new idoc or extended idoc.
Then configure ale/edi to recognize this new idoc and its program.
There r 2 types of idocs.
One is basic idoc which is standard idoc by sap.
Other is extended idoc where we create a structure and insert it into existing idoc structure.
In most cases basic idoc will be suitable for your applications and if it is lacking with few set of fields then you can extend the idoc by
inserting with the fields you required. If your requirement is completely new where the basic idoc is not fit for the requirement , you will
have to create a custom idoc from the scratch. But if you extend a basic idoc, it will be supported in upgrade. If you develop a new idoc
from scratch it is not supported in upgrades.
In Inbound system, sap generates status records.
Status codes 0 to 49 are reserved for outbound process and 50 and above are reserved for inbound process.
Status records generated by sap and stored in edids table. The key for this table is idoc number.
The complete documentation of status records can be viewed at we61.
Fields in status records table:
Docnum-idoc number
Logdat-date of status information
Logtim-time of status info
Countr-edi status number
Credit-status record create date
Status-status of idoc
IDOC development is a 3 step process.
Create new idoc or extend an existing idoc.
Write a program for this new idoc or extended idoc.
Then configure ale/edi to recognize this new idoc and its program.
There r 2 types of idocs.
One is basic idoc which is standard idoc by sap.
Other is extended idoc where we create a structure and insert it into existing idoc structure.
In most cases basic idoc will be suitable for your applications and if it is lacking with few set of fields then you can extend the idoc by
inserting with the fields you required. If your requirement is completely new where the basic idoc is not fit for the requirement , you will
have to create a custom idoc from the scratch. But if you extend a basic idoc, it will be supported in upgrade. If you develop a new idoc
from scratch it is not supported in upgrades.
Understand and know
idoc. use of idocs and
why sap idocs have
become important
components in sap while
data distribution of data
between sap to sap and
sap to non sap, for
outbound processes and
inbound process.
idoc. use of idocs and
why sap idocs have
become important
components in sap while
data distribution of data
between sap to sap and
sap to non sap, for
outbound processes and
inbound process.
ABAP TECHNICAL
SAP Introduction
sap abap faq
sap Tables
SAP Transaction codes
Internal tables
data dictionary
performance tuning
transports & Requests
Sap scripts
Smartforms
lsmw
reports
sap Workflow
module pool/ dialog
programming
table control
user exits
sap memory
abap memory
alv reports
ABAP ADVANCED
IDOC
ALE
BAPI
BADI
RFC
FUNCTIONAL SIDE
Materials Management
FICO
Human Resources
BIW / BW / SEM
Free Documentation
Abap Material
Ale Material
BAPI Material
BC Material
IDOC Material
R/3 Database Management
SAP material
RFC
Transport
Sales & Distribution Material
Basic Data and Function
Material
Basis (BC) Material
Billing Material
CA Material
CATT : Computer Aided Test
Tool
Capacity Evaluation and
leveling Material
Capacity Planning Material
Cross Application Material
Countries
Customer Service Material
Enterpise Material
Financial / Controlling (FICO)
Internet Time Sheet
Inspection Material
HR Material
Material Management
Material
Payments Material
Payroll Material
Pension Fund
Production Planning and
Control
Plant Maintenance
Quality Management Material
Real Estate Material
SAP material
Wage Types
SAP Introduction
sap abap faq
sap Tables
SAP Transaction codes
Internal tables
data dictionary
performance tuning
transports & Requests
Sap scripts
Smartforms
lsmw
reports
sap Workflow
module pool/ dialog
programming
table control
user exits
sap memory
abap memory
alv reports
ABAP ADVANCED
IDOC
ALE
BAPI
BADI
RFC
FUNCTIONAL SIDE
Materials Management
FICO
Human Resources
BIW / BW / SEM
Free Documentation
Abap Material
Ale Material
BAPI Material
BC Material
IDOC Material
R/3 Database Management
SAP material
RFC
Transport
Sales & Distribution Material
Basic Data and Function
Material
Basis (BC) Material
Billing Material
CA Material
CATT : Computer Aided Test
Tool
Capacity Evaluation and
leveling Material
Capacity Planning Material
Cross Application Material
Countries
Customer Service Material
Enterpise Material
Financial / Controlling (FICO)
Internet Time Sheet
Inspection Material
HR Material
Material Management
Material
Payments Material
Payroll Material
Pension Fund
Production Planning and
Control
Plant Maintenance
Quality Management Material
Real Estate Material
SAP material
Wage Types