IDOC's PDF

IDoc Basics For Functional Consultants | SCN
Page 1 of 39
Welcome, Guest
Login
Register
Products Industries Lines of Business
Services & Support Training & Education University Alliances
About SCN Partnership Events & Webinars
Downloads Developer Center Innovation
IDoc Basics For Functional Consultants

created by Niranjan Nagle on Dec 31, 2012 11:30 AM, last modified by Niranjan Nagle on Sep 6, 2013 7:05 AM
ABSTRACT IDocs are used in most of the SAP applications for transfer of message from SAP to other systems and vice versa. A lot of documentation is available on web for IDocs but most of them are technical in nature. This document is written from perspective of a functional consultant and this will help in dealing with support issues related to IDoc. An effort has been made to capture all the necessary information about IDocs that a functional consultant needs to be aware of. OVERVIEW IDoc is an SAP object that carries data of a business transaction from one system to another in the form of electronic message. IDoc is an acronym for Intermediate Document. The purpose of an IDoc is to transfer data or information from SAP to other systems and vice versa. The transfer from SAP to non-SAP system is done via EDI (Electronic Data Interchange) subsystems whereas for transfer between two SAP systems, ALE is used. IDoc can be triggered in SAP system or in EDI subsystem. This depends on the direction in which IDoc is sent and is called as Inbound IDoc and
http://scn.sap.com/docs/DOC-34785
9/14/2013
Page 2 of 39
Outbound IDoc accordingly. In case of outbound flow, IDoc is triggered in SAP through document message control which is then sent to EDI subsystem. EDI converts the data from IDoc into XML or equivalent format and then sends the data to partner system through Internet. For inbound flow, EDI converts partner data and IDoc is created in SAP. After successful processing of this IDoc, Application Document is posted in SAP.
EDI STANDARDS AND IDOC EDI is electronic exchange of business document between the computer systems of business partners, using a standard format over a communication network. EDI stands for Electronic Data Interchange. For transmission of information electronically, two widely used standards are ANSI ASC X12 and EDIFACT. ANSI ASC X12 is a committee formed by representatives of major organizations, government bodies and EDI software companies which defines standards and guidelines for information interchange over EDI. UN/EDIFACT stands for United Nations EDI for Administration, commerce and Transport and was formed in 1985 using ANSI X12 and UNTDI (United Nations Trade Data interchange) as base standards. ANSI X12 describes business document as transactions and each transaction is represented by three digit number e.g. 850 Purchase Order, 855 - Purchase Order Acknowledgement. EDIFACT describes business document as messages, represented by standard names e.g. ORDERS for purchase order.
9/14/2013
Page 3 of 39
IDOC TERMINOLOGIES IDOC (BASIC) TYPE IDoc Types are based on the EDI standards and mostly on EDIFACT standards. Basic Types (or IDoc Type) defines the structure of an IDoc. Each basic type describes standard IDoc segments, format of data fields and their size. Basic Type also defines number of segments and fields in an IDoc. All the fields that are necessary for transmission of message for a particular business transaction are mapped in different segments. It also defines the structure and relationship of IDoc segments along with mandatory and optional segments.
IDOC EXTENSION
9/14/2013
Page 4 of 39
Basic type contains all the standard fields that are necessary for carrying out a business transaction. However, if any additional values are to be sent to the partner then we can make use of the IDoc Extension feature. IDoc extension is extension of basic type and contains additional custom IDoc segments and fields that are not available in standard basic type. IDOC SEGMENTS IDoc segments contain the actual data that is sent to or received from a partner. These segments contain the actual values that are sent as part of IDoc transmission.
PARENT AND CHILD SEGMENTS IDoc segment is termed as Parent segment if it contains its own segments. The dependent segments are called as child segments.
Version 13
INBOUND/OUTBOUND IDOCS IDocs sent outside the system are termed as Outbound IDocs and the ones that are received into the system, are called as Inbound IDocs.
9/14/2013
Page 5 of 39
IDOC DIRECTION This signifies the direction is which information is sent and is similar to terminology used in mails. If information is sent outside the system then the direction is outbox when it is received into the system then direction is inbox. In SAP Outbox direction is represent by 1 i.e. outbox and Inbox direction is represented by 2.
PARTNER Partner is the Business Partner with which the exchange of information is to take place using IDoc. It can be a vendor or customer or any other system. Depending on the direction of information in which the information is sent it plays a role of either a sending partner or a receiving partner.
PARTNER TYPE Partner type/role is used to identify partners within the sap systems. Partner type is KU for customer, LI for vendor and LS for Logical System.
9/14/2013
Page 6 of 39
MESSAGE TYPE IDoc processing involves transmission or receipt of document in the form of a message, each of which represents a document in SAP. These documents can be Order, Shipment Confirmation, Advance Shipping Notification, Goods Receipt, or Invoice. Message type is associated with Basic IDoc Type (Basic Type) and defines the kind of data or document that is exchanged with the partner. PROCESS CODE The process code contains the details of the Function Module that are used for IDoc processing. Message Type can be linked to the Process code. PORT IDoc Port contains the information about the way data is sent between the source or target system. The type of port defines the information contained within the port. For port type Internet Port will contain IP address of the target system. For port type file, directory or file name information is maintained. tRFC port contains information about the RFC destination of the target system. For IDoc transmission using ALE tRFC ports are used. PARTNER PROFILE MAINTENANCE PARTNER PROFILE (WE20)
9/14/2013
Page 7 of 39
Partner profile must be maintained for all the business partners to whom we want to send or receive the IDocs. The TCODE for maintaining the partner profile is WE19.
Double clicking on the Partner will show the following screen:
9/14/2013
Page 8 of 39
Partner profile contains parameters for Inbound and Outbound processing of IDocs. For each message type we can maintain, inbound/outbound options, message control, post processing options and contact information within Inbound and outbound parameters. OUTBOUND OPTIONS (OUTBOUND PARAMETERS)
9/14/2013
Page 9 of 39
This involves sender/receiver port, Output mode and relation to IDoc type i.e. Basic Type and extension.
MESSAGE CONTROL (OUTBOUND PARAMETERS) This contains application for which IDoc will be created e.g. EF for Purchase order, the message type of the application that will trigger the IDoc and Process Code that will convert SAP document to an IDoc. For example, if PO is to be sent to the Vendor AXXXXZ, then in the outbound option of the partner AXXXXZ we need to maintain the message type ZXX1 and link it to the Process Code ME10. So when message type ZXX1 is triggered in the PO then an IDoc will be created for the partner vendor AXXXXZ.
9/14/2013
Page 10 of 39
Process Code is linked to the Function Module in SAP that converts application data into an IDoc. Standard function modules are provided by SAP for this conversion however these can also be customized as per business needs.
Change Message Indicator indicates whether the IDoc is sent as a notification of change. For example, Purchase Order change messages are sent to vendor using EDI standard message type 860.
Separate message type should be triggered in the purchase order for PO change. Additional line with change message type must be added in the Message control tab with change message indicator on.
9/14/2013
Page 11 of 39
INBOUND OPTIONS (INBOUND PARAMETERS) For inbound options process code is maintained in the Inbound screen only. IDoc processing can be triggered by background program and triggered immediately.
9/14/2013
Page 12 of 39
POST PROCESSING (INBOUND/OUTBOUND PARAMETERS) In the post processing option we can maintain the workflow details of the users or positions to which an error notification will be sent if an IDoc processing fails.
TELEPHONY (INBOUND/OUTBOUND PARAMETERS) We can also maintain the contact details in the telephony option.
EDI STANDARD (OUTBOUND PARAMETERS) EDI standard screen contains the details of the Standard EDI terminology used for the IDoc transmission.
For example, Message Type 850 is an EDI standard for Purchase Order IDoc and is linked to IDoc Message Type Orders.
9/14/2013
Page 13 of 39
IDOC STRUCTURE AND RECORDS STRUCTURE IDoc structure is divided into Control Record, Data Records and Status records.
These records are stored in the transparent tables in SAP. These are EDIDC, EDID4 and EDIDS. CONTROL RECORD (EDIDC) It contains information such as IDoc number, direction, IDoc Status, Basic Type, Message Type, Partner (Sender/Receiver), date and time of creation/update, Interchange File or ISA number,etc.
9/14/2013
Page 14 of 39
9/14/2013
Page 15 of 39
DATA RECORD (EDID4) It contains the details of the IDoc segments.
9/14/2013
Page 16 of 39
IDoc segment has fields that contain the data necessary for posting the documents.
9/14/2013
Page 17 of 39
STATUS RECORDS (EDIDS) IDoc Status defines the processing status of the IDoc. IDoc statuses are used to track the IDoc and its various processing states. Status Numbers represents IDoc status. Current status of the IDoc is present in Control record.
9/14/2013
Page 18 of 39
Initial Status numbers are 64 for inbound and 03 for outbound. Successful status is 53 for inbound and 16 for outbound IDocs. SENDING AND RECEIVING IDOCS TRIGGERING AN OUTBOUND IDOC Outbound IDocs can be triggered from the output message types of Purchase Orders, deliveries, Material Documents, invoices, etc. The following figure shows that once the output ZXX1 of PO XXXXXXX1 is processed an IDoc 000000XXXXXXXXX1 is added/created.
The relationship between the IDoc and the application document can be found in two ways: 1. Relationship tab of IDoc
9/14/2013
Page 19 of 39
2. Relationship tab of Application Document, e.g. PO, SO, Material Document, etc.
The initial status of this IDoc will be 30, which after successful processing will convert into status 16.
9/14/2013
Page 20 of 39
A successful outbound IDoc will pass through all the above statuses in reverse order (01-03-18-06-12-16). Each status represents an IDoc validation step. If an IDoc passes all the validations it would reach status 16. These different validation steps for outbound IDocs are explained below: 01: IDoc generation successful 30: IDoc is ready to be processed by IDoc Processing job 03: IDoc data is passed to the Port 18: IDoc successfully triggered EDI subsystem 06: IDoc data translated to EDI format 12: IDoc is dispatched successfully to the partner 16: Partner has received the IDoc successfully IDoc can possibly fail at any of the above steps during validation. RECEIVING AN INBOUND IDOC The initial status of an inbound IDoc is 64 and successful status is 53. Different validation steps for inbound IDocs are explained below: 50: IDoc received successfully in the system 64: IDoc is ready to be processed by IDoc processing job 53: Application document created and saved successfully. The document number can be found by expanding the status node 53
9/14/2013
Page 21 of 39
An inbound IDoc goes through all the above statuses in reverse order (50-6453). IDOC PROCESSING AUTOMATIC/IMMEDIATE PROCESSING In this case, IDoc are processed immediately as they generated or added in the system. The check Transfer IDoc immediately is selected in Outbound Options and Trigger Immediately is selected in Inbound Option. These checks are generally used when the real time information exchange is necessary between two systems.
9/14/2013
Page 22 of 39
MANUAL PROCESSING IDocs can also be manually processed using the TCODE BD87 in SAP. PROCESSING VIA BACKGROUND JOB IDoc processing by background is the most preferred way of processing the IDocs. Following Programs are used from processing the IDocs using background job: RBDAPP01 - Inbound IDocs RSEOUT00 - Outbound IDocs REPROCESSING IDOCS On the basis of IDoc statuses different programs can be used for reprocessing of failed IDocs. These are given below:
9/14/2013
Page 23 of 39
TESTING AND EDITING IDOCS If an IDoc contains error in the data then such IDocs can be edited using TCode WE02 or WE05. When an IDoc is edited the original IDoc information (backup) is saved in a New IDoc under status 70 (for inbound) / 33 (for outbound). These IDoc stays in the system for reference only and cannot be processed. The status of the edited IDoc becomes 69 (inbound) and 32 (outbound). These IDocs can then be processed using BD87 transaction or batch jobs. Debugging of IDocs can be done using by copying the IDocs using TCode WE19. WE19 is a test tool for Idocs processing. WE19 copies the existing idoc and creates a new IDoc which can then be modified as per testing needs. The newly generated IDoc can also be processed using BD87. CONVERTING IDOC STATUS Report RRC1_IDOC_SET_STATUS can be used to change the status of IDoc. Status changes are generally needed to move an IDoc to status 68 no further processing
SEARCHING IDOCS IN SAP TCODE WE02/WE05: GENERAL SEARCH IDocs can be displayed in system via TCODE WE02 and WE05. If IDoc number is not known then search can be made on the basis of IDoc Date,
9/14/2013
Page 24 of 39
Direction, BASIC TYPE, MESSAGE TYPE, and PARTNER NUMBER. Partner number can be found in the Output Messages of the documents.
IDoc search can also be made on the basis of ISA or Transfer file Reference.
9/14/2013
Page 25 of 39
TCODE WE09: SEARCHING DATA IN IDOC SEGMENTS If we are looking for specific information within the IDocs Segments then this can be found using TCODE WE09. This is useful if you are searching for a particular information in similar kind of IDoc within IDoc segments. For example, if you want to search a particular Purchase Order number e.g. 100000001 in multiple IDocs which lies in Segment E1EDK01 of an IDoc under field BELNR. Then the search can be executed in the following manner.
IDOC VALIDATIONS, COMMON IDOC ERRORS AND SOLUTION
9/14/2013
Page 26 of 39
Though, the IDoc failure may not be related to any of the above mentioned reasons, the best way to find the IDoc error is to compare the existing IDoc with the good example. Good example IDoc can be easily searched with any of the IDoc search methods as described above.
DOCUMENTATION FOR IDOC TYPES IDoc documentation can be found using TCODE WE60 and can be helpful to obtain information of the IDoc Type or its particular segment. It also provides information such as mandatory and optional segments, minimum and maximum number of segments, etc.
9/14/2013
Page 27 of 39
GENERAL INFORMATION TYPES
FOR
COMMON
IDOC
MESSAGE
The following list gives the Basic Type and Message Type combination for common idocs
9/14/2013
Page 28 of 39
ARCHIVING/DELETION OF IDOCS FROM DATABASE As IDocs grow older they are archived and deleted from the database. Archived IDocs can be viewed using TCODE SARI in Achieve Explorer using archiving object as IDoc. Following are the few programs that are used for archiving and deletion of IDocs from database.
9/14/2013
Page 29 of 39
22385 Views
Tags: sap, edi, idoc
Average User Rating (43 ratings)
64 Comments
Manjunath Tony Jan 1, 2013 5:41 PM
Very useful document, keep up the good work. Expecting more documents like this from u..... With regards, Tony.
Like (2)
Raju Prabhune Jan 2, 2013 5:47 AM
Hi Niranjan,
9/14/2013
Page 30 of 39
Wow!!! What an excellent document. Working in SAP for last 3 year, 1st time I've found such a extensive/detailed document on IDoc. Congratulations & Happy new year.
Like (1)
Narendra Konnipati Jan 8, 2013 8:50 AM
Hi Niranjan , Wonderful Document ( Its seems ,dont want EDI Consultant to handle issues of EDI when we have this Doc ). Wish U Happy New Year buddy. Thanks, Naren
Like (1)
Vithal Bhadrachalam Jan 8, 2013 10:57 PM
Hello Niranjan, Very useful document.It will help many consultants to enrich their knowledge in IDOCs. Thank you verymuch, Vithal
Like (1)
Nikhil Karnam Jan 28, 2013 11:29 AM
Hi Niranjan Bhai, IDOC document is very helpful. Thanks, Nikhil

Like (1)
Nayeem .S.N Feb 11, 2013 4:42 PM
Hi Nirajan, Document is really wonderful and it will really helpful for many SAP consultants to gain their knowledge. Keep posting such documents..... Thanks Nayeem.
Like (1)
Adam Krawczyk Feb 14, 2013 2:02 PM
Very comprehensive and detailed blog about IDoc.
9/14/2013
Page 31 of 39
In fact as developer I am just searching for general overview so for me it is still too technical, however I found here some basic concepts here as well.Thank you, great job! Regards, Adam
Like (1)
naveen joseph Apr 4, 2013 12:20 PM
Thanks for the effort

Like (1)
Md Ruhul Amin May 10, 2013 1:35 PM
Its really very helpful document...

Like (1)
Md Ruhul Amin May 11, 2013 11:37 AM
Very good and excellent docs for people who are new in IDOC .It is usefull to make them aware of business process
Like (1)
Kalaiyarasan M May 13, 2013 3:27 PM
Hi, A very good job. This is much informative & helps one to understand the concept in a detailed way. Cheers !!! kalai.
Like (1)
Jason Zhuang May 30, 2013 3:17 PM
Thanks so much. it is really a good sharing.

Like (1)
Poorna yalamanchili Jun 4, 2013 3:55 AM
Thanks for posting this document. very informative and helpful for starters cheers Poorna
Like (1)
Bisweswar Sahu Jun 12, 2013 4:32 AM
Nice Doc. Thanks a lot. Bisweswar
9/14/2013
Page 32 of 39
Like (1)
T W Jun 14, 2013 2:24 PM
Niranjan, Very informative and easy to understand document! Many thanks!

Like (1)
RHEA LYN TAN Jun 18, 2013 11:20 AM
thanks for this. good job!

Like (1)
Srinivas S Jun 20, 2013 1:48 PM
Really wonderful document. Keep on posting this kind of useful document . thank you very much. regards. Srinu.
Like (1)
Itsik Versano Jun 20, 2013 1:51 PM
thanks for this. great work!

Like (1)
Maria Teplyakova Jun 21, 2013 7:59 AM
Hi Niranjan Bhai, I'd like to join in all these good comments and thanks. Plese keep writing such useful articles. Regards, Maria
Like (1)
venkata pochiraju Jun 21, 2013 9:56 PM
Thanks for the hard work. Good information.

Like (1)
Santhosh Venreddy Jun 24, 2013 10:25 AM
Very Useful Article Regards Santhosh

Like (1)
9/14/2013
Page 33 of 39
Jun 24, 2013 12:07 PM
Nice blog! if the SAP screen is color, it will be much more better! Thank you for your nice job!
Like (1)
Manaseegan K Jun 25, 2013 1:18 PM
A detailed work worth going through. Regards, Manas.

Like (1)
Ranjith M Nair Jun 26, 2013 11:01 AM
Very Informative for budding consultants, Thank You Regards, Ranjith

Like (1)
Ravi Gupta Jun 27, 2013 5:42 PM
very informative and detail article on IDoc. Thanks.

Like (1)
ramya lakshmanan Jul 1, 2013 10:08 AM
Very clearly stated document on IDoc. Thanks a lot.

Like (1)
Nikhil Ghadge Jul 1, 2013 1:42 PM
Hey Niranjan, Very informative and easy to understand document! thanks a ton!
Like (1)
Samkit Shah Jul 2, 2013 12:07 AM (in response to Nikhil Ghadge)
Hi Niranjan Its very helpful and informative and good understanding on Idoc
Like (1)
Ankur Jain Jul 2, 2013 10:31 AM
9/14/2013
Page 34 of 39
Hi Niranjan, Thanks for this useful document.

Like (1)
Binu wilson Jul 3, 2013 8:20 AM
Hi Niranjan, Appreciate your hardwork for preparing this document and sharing. Thanks a lot:)
Like (1)
D Sea Jul 3, 2013 6:17 PM
Hi, It is an excellent article. Really brings out the right depth and yet easily understood. Congratulations! One small typo -> EDI is Electronic Data Interchange (EDI). Just my two cents. Keep sharing such useful documents. Have a good one. Thanks.
Like (1)
ravindra devarapalli Jul 5, 2013 8:51 AM
Hi, Thanks ...........I hope it is very helpful to all users. Is it possible to do in IDES server. If it is possible please provide complete details how to do. I am new for this IDOC. Please help i want to learn
Like (1)
T W Jul 5, 2013 9:05 AM (in response to ravindra devarapalli)
ravindra, The content (with the transaction codes) mentioned in the document can be tried out in IDES too. Configuration, checking the already created IDocs, these things are possible in IDES. Sending and receiving IDocs to and from an external application is not possible in IDES. But from learning point of view (theoritical learning) is very much possible with IDES.
Like (1)
ravindra devarapalli Jul 5, 2013 11:30 AM (in response to T W)
HI,
9/14/2013
Page 35 of 39
Thanks a lot. I will try now in IDES.

Like (0)
Niranjan Nagle Jul 5, 2013 9:30 AM (in response to ravindra devarapalli)
T W is right. You may try the TCODEs in IDES from learning perspective. However, actual IDoc flow can only be seen in non IDES systems since EDI/EAI connection with SAP is necessary for IDoc transmission.
Like (0)
Syam Kumar Dodda Jul 5, 2013 9:25 PM
Hi Niranjan, Appreciate your hard work!!! This document is wonderful... Keep Posting like this....
Like (1)
Robert Christenberger Jul 6, 2013 8:24 PM
Hello Niranjan, thank you for this detailed document.

Like (1)
Raja v Jul 11, 2013 9:56 AM
thank u so much...very usefull to me..
Like (1)
A Manish Kumar Jul 26, 2013 6:35 AM
Great effort buddy,,,

Like (1)
sanjeet kumar Jul 26, 2013 10:28 PM
Really very systematic and informative. Thanks a lot for sharing with us. Regards Sanjeet Kumar
Like (1)
k j Jul 30, 2013 7:32 PM
Thanks for sharing such a wonderful informative document
9/14/2013
Page 36 of 39
Like (1)
SURYA S Aug 8, 2013 4:25 PM
Very informative, systematic & easy to understand. Appreciate your effort on this document. Regards, Surya Seemakurty
Like (1)
avinash kowale Aug 12, 2013 11:16 AM
Extremly good document. Regards, Avinash Kowale

Like (1)
Syam Babu Aug 12, 2013 12:43 PM
Excellent
Like (1)
yogesh raina Aug 12, 2013 1:10 PM
Thanks for sharing this document very useful and intresting. Yogesh
Like (1)
Deepa Tate Aug 16, 2013 6:37 AM
Thanks for sharing the document...Very useful for beginners

Like (1)
Naresh Krishnamoorthy Aug 19, 2013 10:48 AM
Very Useful Resource. Many Thanks. Best Regards, Naresh K.

Like (1)
Gurunath Kumar Dadamu Aug 20, 2013 3:04 PM
Good documents. Regards, Gurunath

Like (1)
9/14/2013
Page 37 of 39
Jimmy John Aug 20, 2013 7:28 PM
Excellent blog.
Like (1)
Sattaiah Gundu Aug 21, 2013 8:55 AM
excellent Document.... hats of to you

Like (1)
Jamie Jiang Aug 29, 2013 9:39 AM
Idoc Basics,good job.

Like (1)
Manasa Anantapur Sep 1, 2013 7:41 PM
good info,Thank u '

Like (1)
Amala Srinivasa Rao Sep 2, 2013 6:06 AM
Appreciable effort dear

Like (1)
Ankita Chhabra Sep 2, 2013 9:43 AM
Hello
Niranjan Nagle, Hope to read a few more from your side.
Thank you for sharing such an informative document Regards, Ankita.
Like (1)
ravindra kulkarni Sep 2, 2013 4:51 PM
Thanks for sharing this very useful information document. Regards, Ravindra kulkarni
Like (1)
A D Sep 3, 2013 7:45 AM (in response to ravindra kulkarni)
Dear Thinks a lot, good job Regards
9/14/2013
Page 38 of 39
AD
Like (1)
Anupam Kumar Sep 4, 2013 1:51 PM
Thank you so much for sharing such an informative document. It will really help to have good insight for the functional consultants regarding IDOC functioning
Like (1)
mastan vali Sep 5, 2013 7:12 AM
Hello Niranjan, Good document, appreciate your time and effort. Regards Mastan vali
Like (1)
Kiran Nimmagadda Sep 5, 2013 2:13 PM
Dear Niranjan, It is really informative and also very much useful for IDOC debuggers .. Keep it up... Regards Kiran N
Like (1)
Rajesh Ravuri Sep 6, 2013 10:49 AM
It is really usefull information for new learners. Thanks and grate share
Like (1)
Anupam Kumar Sep 12, 2013 10:48 AM
Dear Niranjan, Thanks for such an informative document, its really useful for the new entrants. Regards Anupam
Like (1)
Ivan Marconato Sep 12, 2013 4:01 PM
Hi, this is a great job on IDOCs ! Thanks Ivan
9/14/2013
Page 39 of 39
Like (1)
pankaj labhasetwar Sep 12, 2013 8:42 PM
Hi Niranjan, Thanks for such great document... Regards, Pankaj

Like (1)
Rajesh Kumar Sep 13, 2013 2:10 PM
Hi Niranjan, It is very helpful document for IDOC Regards, Rajesh

Like (1)
Site Index Privacy
Contact Us Terms of Use
SAP Help Portal Legal Disclosure
Copyright
9/14/2013

IDOC's PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IDOC's PDF

Uploaded by

Copyright:

Available Formats

IDoc Basics For Functional Consultants | SCN

Products Industries Lines of Business

Services & Support Training & Education University Alliances

About SCN Partnership Events & Webinars

Downloads Developer Center Innovation

IDoc Basics For Functional Consultants

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

Double clicking on the Partner will show the following screen:

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

DATA RECORD (EDID4) It contains the details of the IDoc segments.

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

IDOC VALIDATIONS, COMMON IDOC ERRORS AND SOLUTION

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

GENERAL INFORMATION TYPES

IDoc Basics For Functional Consultants | SCN

IDoc Basics For Functional Consultants | SCN

Tags: sap, edi, idoc

Average User Rating (43 ratings)

Raju Prabhune Jan 2, 2013 5:47 AM

IDoc Basics For Functional Consultants | SCN

Narendra Konnipati Jan 8, 2013 8:50 AM

Vithal Bhadrachalam Jan 8, 2013 10:57 PM

Nikhil Karnam Jan 28, 2013 11:29 AM

Hi Niranjan Bhai, IDOC document is very helpful. Thanks, Nikhil

Nayeem .S.N Feb 11, 2013 4:42 PM

Adam Krawczyk Feb 14, 2013 2:02 PM

Very comprehensive and detailed blog about IDoc.

IDoc Basics For Functional Consultants | SCN

naveen joseph Apr 4, 2013 12:20 PM

Thanks for the effort

Md Ruhul Amin May 10, 2013 1:35 PM

Its really very helpful document...

Md Ruhul Amin May 11, 2013 11:37 AM

Kalaiyarasan M May 13, 2013 3:27 PM

Jason Zhuang May 30, 2013 3:17 PM

Thanks so much. it is really a good sharing.

Poorna yalamanchili Jun 4, 2013 3:55 AM

Bisweswar Sahu Jun 12, 2013 4:32 AM

Nice Doc. Thanks a lot. Bisweswar

IDoc Basics For Functional Consultants | SCN

T W Jun 14, 2013 2:24 PM