document format. IDocs enable te connection of di!erent a""lication s#stems usin$ a messa$e%based interface. Te use of IDocs as tree main aims& Structured exchange and automatic posting of application documents. Reduction of the varying complex structures of diferent application systems to one simple structure. For example, the structure of an SAP application document and the structure of the corresponding ED message according to the !"#EDFA$% standard. Detailed error handling &efore the data is posted in the application. IDOCS CAN '( R()ARD(D AND D(*IN(D ON T+O ,(-(,S& ON A T(C.NICA, ,(-(, AND ON AN APP,ICATION ,(-(,. T.( T(C.NICA, ,(-(, (NA',(S T.( S/PPORT O* CROSS%APP,ICATION */NCTIONS S/C. AS RO/TIN) AND T(C.NICA, (RROR .AND,IN).
Technical view This view is defined by three different types of structure that are generated by the IDoc interface: CONTRO, R(CORD DATA R(CORD STAT/S R(CORD Application view This view is defined by the segments of an IDoc. Segments are structures that are used for the interpretation of the field SDATA in the data record. An IDoc type is defined by the corresponding: S()0(NTS ATTRI'/T(S O* T.(S( S()0(NTS (*OR (1A0P,(2 0A1I0/0 N/0'(R2 .I(RARC.ICA, S(3/(NC(2 AND S()0(NT STAT/S). 'essage %ype and doc %ype( 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 FIDCT message type is used for !ournal messages. The IDoc type indicates the "A# format that is to be used to interpret the data of a business transaction. Sample D)$***n&ound that is posted successfully. +ets no, go through the entire D)$ components step &y step- Transaction *or Idoc 0essa$e t#"es-----.E/0 This acts as a repository for different message types in SAP. One can go through this Tcode and chec what are all message type e!ists. Transaction to *ind te ,atest -ersion of IDOC t#"e assi$ned to 0essa$e t#"e4.E/1 "o through this Tcode and find the latest version of the IDO# assigned for a particular $essage type and can use that. Transaction to See te IDOC t#"e structure%%%%%% .E23 To Display the basic IDO# type and see the parent and child relationships between different segments% we use this Tcode. This can also be used to create Idoc type e!tensions... Transaction to dis"la# Se$ments in an IDOC& %%%.E20
This Tcode is used to create a new segment or display the e!isting segment. &e can create a new segment and can assign parent and child relationships% 'urther they can be assigned to the IDO# type e!tended. The below screen shot shows the display of a segment. IDOC Documentation %%%%%%.E43 #omplete IDO# documentation which shows the IDO# structure with different relations between segments% lengths and status lie optional or $andatory. The Screen shot below shows them in detail Transaction to See IDOC status4.E56 Idocs in general have different status before they got posted successfully into Database. The below screenshot of the mentioned tcode will show the different status that an IDO# undergoes. Partner Pro5les& .E13 The partner profile contains parameters that define the electronic interchange of data with a partner via that IDoc interface. Idoc Test Tool4..E07 This is termed as IDOC test tool, if you open an existing IDoc in WE19 and process it again you create a ne IDoc. The test tool is a to!step process. In the "rst step, you create an IDoc #y using one of the folloing options $ Copy an existing IDoc. Create an IDoc #ased on an IDoc type. Create an IDoc #ased on a message type. Create an IDoc using a "le as a template. Create an IDoc ith no template. The option you choose depends on your tastes and program re%uirements. The "rst option is most commonly used #ecause it ena#les you to modify an existing IDoc &in#ound or out#ound' to suit your needs. In the second step, the IDoc created is passed to the in#ound process. (ou ha)e se)eral options to select the method of starting the in#ound process$ *tart the in#ound processing )ia the standard path. This method uses all in#ound components. Call the in#ound function module directly. The system #ypasses the chec+s for partner pro"le and hands the IDoc data to your in#ound function module directly. This method is useful for testing an in#ound process ithout ha)ing to maintain any in#ound con"guration. (ou can also start the function module in de#ug mode and select the processing option for your posting module. *a)e the IDoc in a "le, and start the in#ound process. This method is similar to the "rst method except that you also create an IDoc "le at the operating system le)el. This method is used mainly for EDI processes. P,(AS( DO NOT /S( +(67 *OR R(PROC(SSIN). IT IS ON,8 *OR T(STIN) AND D('/))IN) P/RPOS(S. IDOC list%%%%%.E31#38 Idocs of certain type can be filtered by using the Archive $ey..
This tcode displays all the Idocs of a particular message type %Idoc type in a certain period of time IDOC Statistics4...E36 +(9: is used for getting the idoc satistics.The IDocs are sorted for statistical purposes #y processing status. The categories shon #elo are used here. Only those IDocs hose status has change ithin a de"ned period are selected. 6 .(rror if this indicator is set, the IDocs ith an error status and hen this as is gi)en. The status records are also e)aluated. ;. (rror Resol<ed =.*la$ed for deletion Transaction to Post IDOCs& 9D13 &y providing Date and essage type..The IDocs in '( status can be processed%posted into Database. In order to post Idocs faster than the normal rate)we can go or #arallel processing. I,e) Idocs in >6 status can be re"rocessed b# usin$ 9D/6 To select certain ID*Cs we can use the following selection...
Program to change the status of docs...
Status of the D)$ &efore processing... Execute the program...