IDoc Basics For Functional Consultants - SCN

4/29/2016
IDocBasicsForFunctionalConsultants|SCN
GettingStarted Newsletters
Hi,Guest
LogOn
JoinUs
Products
Services&Support
AboutSCN
Downloads
Industries
Training&Education
Partnership
DeveloperCenter
Activity
LinesofBusiness
UniversityAlliances
Events&Webinars
Innovation
Browse
IDocBasicsForFunctionalConsultants
Store
SearchtheCommunity
Communications
Actions
Version17
createdbyNiranjanNagleon31Dec201211:30,lastmodifiedbyNiranjanNagleon09Jul201507:56
Share
94
42
Tweet
Like
116
ABSTRACT
Today IDocs are used in most SAP applications for transfer of
message(information) from SAP system to other systems and vice
versa. Though lot of documentation is available on IDocs it is
difficult for a functional consultant to understand such documents
duetotheirtechnicalnature.Whileafunctionalconsultantisnot
expected to know the IDoc concepts in its entirety, an effort has
beenmadetocapturetheminimumnecessaryinformationthatone
needs to be aware of in order to handle project/support issues on
IDocs.
OVERVIEW
IDoc is an SAP object that carries data of a business transaction from one
systemtoanotherintheformofelectronicmessage.IDocisanacronymfor
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 nonSAP system is done via EDI (Electronic Data Interchange)
subsystemswhereasfortransferbetweentwoSAPsystems,ALEisused.
IDoccanbetriggeredinSAPsystemorinEDIsubsystem.Thisdependson
the direction in which IDoc is sent and is called as Inbound IDoc and
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
andthensendsthedatatopartnersystemthroughInternet.
Forinboundflow,EDIconvertspartnerdataandIDociscreatedinSAP.After
successfulprocessingofthisIDoc,ApplicationDocumentispostedinSAP.
http://scn.sap.com/docs/DOC34785
1/21
4/29/2016
EDISTANDARDSANDIDOC
EDI is electronic exchange of business document between the computer
systemsofbusinesspartners,usingastandardformatoveracommunication
network.EDIstandsforElectronicDataInterchange.
Fortransmissionofinformationelectronically,twowidelyusedstandardsare
ANSI ASC X12 and EDIFACT. ANSI ASC X12 is a committee formed by
representativesofmajororganizations,governmentbodiesandEDIsoftware
companies which defines standards and guidelines for information
interchange over EDI. UN/EDIFACT stands for United Nations EDI for
Administration,commerceandTransportandwasformedin1985usingANSI
X12andUNTDI(UnitedNationsTradeDatainterchange)asbasestandards.
ANSI X12 describes business document as transactions and each
transactionisrepresentedbythreedigitnumbere.g.850PurchaseOrder,
855 Purchase Order Acknowledgement. EDIFACT describes business
document as messages, represented by standard names e.g. ORDERS for
purchaseorder.
IDOCTERMINOLOGIES
IDOC(BASIC)TYPE
IDoc Types are based on the EDI standards and mostly on EDIFACT
standards.
BasicTypes(orIDocType)definesthestructureofanIDoc.Eachbasictype
describesstandardIDocsegments,formatofdatafieldsandtheirsize.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.
IDOCEXTENSION
2/21
4/29/2016
Basictypecontainsallthestandardfieldsthatarenecessaryforcarryingout
abusinesstransaction.However,ifanyadditionalvaluesaretobesenttothe
partnerthenwecanmakeuseoftheIDocExtensionfeature.IDocextension
isextensionofbasictypeandcontainsadditionalcustomIDocsegmentsand
fieldsthatarenotavailableinstandardbasictype.
IDOCSEGMENTS
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
IDoctransmission.
PARENTANDCHILDSEGMENTS
IDocsegmentistermedasParentsegmentifitcontainsitsownsegments.
Thedependentsegmentsarecalledaschildsegments.
INBOUND/OUTBOUNDIDOCS
IDocssentoutsidethesystemaretermedasOutboundIDocsandtheones
thatarereceivedintothesystem,arecalledasInboundIDocs.
IDOCDIRECTION
This signifies the direction is which information is sent and is similar to
terminologyusedinmails.Ifinformationissentoutsidethesystemthenthe
directionisoutboxwhenitisreceivedintothesystemthendirectionisinbox.
InSAPOutboxdirectionisrepresentby1i.e.outboxandInboxdirectionis
representedby2.
PARTNER
3/21
4/29/2016
PartneristheBusinessPartnerwithwhichtheexchangeofinformationisto
takeplaceusingIDoc.Itcanbeavendororcustomeroranyothersystem.
Depending on the direction of information in which the information is sent it
playsaroleofeitherasendingpartnerorareceivingpartner.
PARTNERTYPE
Partnertype/roleisusedtoidentifypartnerswithinthesapsystems.Partner
typeisKUforcustomer,LIforvendorandLSforLogicalSystem.
MESSAGETYPE
IDocprocessinginvolvestransmissionorreceiptofdocumentintheformofa
message, each of which represents a document in SAP. These documents
canbeOrder,ShipmentConfirmation,AdvanceShippingNotification,Goods
Receipt,orInvoice.MessagetypeisassociatedwithBasicIDocType(Basic
Type) and defines the kind of data or document that is exchanged with the
partner.
PROCESSCODE
TheprocesscodecontainsthedetailsoftheFunctionModulethatareused
forIDocprocessing.MessageTypecanbelinkedtotheProcesscode.
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
thetargetsystem.ForIDoctransmissionusingALEtRFCportsareused.
PARTNERPROFILEMAINTENANCE
PARTNERPROFILE(WE20)
4/21
4/29/2016
Partnerprofilemustbemaintainedforallthebusinesspartnerstowhomwe
want to send or receive the IDocs. The TCODE for maintaining the partner
profileisWE20.
DoubleclickingonthePartnerwillshowthefollowingscreen:
PartnerprofilecontainsparametersforInboundandOutboundprocessingof
IDocs.Foreachmessagetypewecanmaintain,inbound/outboundoptions,
message control, post processing options and contact information within
Inboundandoutboundparameters.
OUTBOUNDOPTIONS(OUTBOUNDPARAMETERS)
Thisinvolvessender/receiverport,OutputmodeandrelationtoIDoctypei.e.
BasicTypeandextension.
5/21
4/29/2016
MESSAGECONTROL(OUTBOUNDPARAMETERS)
ThiscontainsapplicationforwhichIDocwillbecreatede.g.EFforPurchase
order, the message type of the application that will trigger the IDoc and
ProcessCodethatwillconvertSAPdocumenttoanIDoc.Forexample,ifPO
is to be sent to the Vendor AXXXXZ, then in the outbound option of the
partnerAXXXXZweneedtomaintainthemessagetypeZXX1andlinkitto
theProcessCodeME10.SowhenmessagetypeZXX1istriggeredinthePO
thenanIDocwillbecreatedforthepartnervendorAXXXXZ.
ProcessCodeislinkedtotheFunctionModuleinSAPthatconverts
applicationdataintoanIDoc.Standardfunctionmodulesareprovidedby
SAPforthisconversionhoweverthesecanalsobecustomizedasper
businessneeds.
Change Message Indicator indicates whether the IDoc is sent as a

notification of change. For example, Purchase Order change messages are
senttovendorusingEDIstandardmessagetype860.
6/21
4/29/2016
Separate message type should be triggered in the purchase order for PO

change. Additional line with change message type must be added in the
Messagecontroltabwithchangemessageindicatoron.
INBOUNDOPTIONS(INBOUNDPARAMETERS)
ForinboundoptionsprocesscodeismaintainedintheInboundscreenonly.
IDoc processing can be triggered by background program and triggered
immediately.
POSTPROCESSING(INBOUND/OUTBOUNDPARAMETERS)
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
processingfails.
7/21
4/29/2016
TELEPHONY(INBOUND/OUTBOUNDPARAMETERS)
Wecanalsomaintainthecontactdetailsinthetelephonyoption.
EDISTANDARD(OUTBOUNDPARAMETERS)
EDI standard screen contains the details of the Standard EDI terminology
usedfortheIDoctransmission.
Forexample,MessageType850isanEDIstandardforPurchaseOrderIDoc
andislinkedtoIDocMessageTypeOrders.
IDOCSTRUCTUREANDRECORDS
STRUCTURE
IDoc structure is divided into Control Record, Data Records and Status
records.
TheserecordsarestoredinthetransparenttablesinSAP.TheseareEDIDC,
EDID4andEDIDS.
CONTROLRECORD(EDIDC)
It contains information such as IDoc number, direction, IDoc Status, Basic
Type, Message Type, Partner (Sender/Receiver), date and time of
creation/update,InterchangeFileorISAnumber,etc.
8/21
4/29/2016
DATARECORD(EDID4)
ItcontainsthedetailsoftheIDocsegments.
9/21
4/29/2016
IDoc segment has fields that contain the data necessary for posting the
documents.
STATUSRECORDS(EDIDS)
IDocStatusdefinestheprocessingstatusoftheIDoc.IDocstatusesareused
to track the IDoc and its various processing states. Status Numbers
represents IDoc status. Current status of the IDoc is present in Control
record.
Initial Status numbers are 64 for inbound and 03 for outbound. Successful
statusis53forinboundand16foroutboundIDocs.
SENDINGANDRECEIVINGIDOCS
TRIGGERINGANOUTBOUNDIDOC
10/21
4/29/2016
Outbound IDocs can be triggered from the output message types of

PurchaseOrders,deliveries,MaterialDocuments,invoices,etc.Thefollowing
figureshowsthatoncetheoutputZXX1ofPOXXXXXXX1isprocessedan
IDoc000000XXXXXXXXX1isadded/created.
The relationship between the IDoc and the application document can be
foundintwoways:
1.RelationshiptabofIDoc
2.RelationshiptabofApplicationDocument,e.g.PO,SO,Material
Document,etc.
TheinitialstatusofthisIDocwillbe30,whichaftersuccessfulprocessingwill
convertintostatus16.
11/21
4/29/2016
A successful outbound IDoc will pass through all the above statuses in
reverseorder(010318061216).EachstatusrepresentsanIDocvalidation
step. If an IDoc passes all the validations it would reach status 16. These
differentvalidationstepsforoutboundIDocsareexplainedbelow:
01:IDocgenerationsuccessful
30:IDocisreadytobeprocessedbyIDocProcessingjob
03:IDocdataispassedtothePort
18:IDocsuccessfullytriggeredEDIsubsystem
06:IDocdatatranslatedtoEDIformat
12:IDocisdispatchedsuccessfullytothepartner
16:PartnerhasreceivedtheIDocsuccessfully
IDoccanpossiblyfailatanyoftheabovestepsduringvalidation.
RECEIVINGANINBOUNDIDOC
TheinitialstatusofaninboundIDocis64andsuccessfulstatusis53.
DifferentvalidationstepsforinboundIDocsareexplainedbelow:
50:IDocreceivedsuccessfullyinthesystem
64:IDocisreadytobeprocessedbyIDocprocessingjob
53: Application document created and saved successfully. The document
numbercanbefoundbyexpandingthestatusnode53
AninboundIDocgoesthroughalltheabovestatusesinreverseorder(5064
53).
IDOCPROCESSING
12/21
4/29/2016
AUTOMATIC/IMMEDIATEPROCESSING
Inthiscase,IDocareprocessedimmediatelyastheygeneratedoraddedin
thesystem.ThecheckTransferIDocimmediatelyisselectedinOutbound
Options and Trigger Immediately is selected in Inbound Option. These
checks are generally used when the real time information exchange is
necessarybetweentwosystems.
MANUALPROCESSING
IDocscanalsobemanuallyprocessedusingtheTCODEBD87inSAP.
PROCESSINGVIABACKGROUNDJOB
IDocprocessingbybackgroundisthemostpreferredwayofprocessingthe
IDocs. Following Programs are used from processing the IDocs using
backgroundjob:
RBDAPP01InboundIDocs
RSEOUT00OutboundIDocs
REPROCESSINGIDOCS
On the basis of IDoc statuses different programs can be used for
reprocessingoffailedIDocs.Thesearegivenbelow:
TESTINGANDEDITINGIDOCS
If an IDoc contains error in the data then such IDocs can be edited using
13/21
4/29/2016
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
transactionorbatchjobs.
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.ThenewlygeneratedIDoccanalsobeprocessedusingBD87.
CONVERTINGIDOCSTATUS
ReportRC1_IDOC_SET_STATUScanbeusedtochangethestatusofIDoc.
StatuschangesaregenerallyneededtomoveanIDoctostatus68no
furtherprocessing
SEARCHINGIDOCSINSAP
TCODEWE02/WE05:GENERALSEARCH
IDocs can be displayed in system via TCODE WE02 and WE05. If IDoc
numberisnotknownthensearchcanbemadeonthebasisofIDocDate,
Direction, BASIC TYPE, MESSAGE TYPE, and PARTNER NUMBER.
PartnernumbercanbefoundintheOutputMessagesofthedocuments.
14/21
4/29/2016
IDocsearchcanalsobemadeonthebasisofISAorTransferfileReference.
TCODEWE09:SEARCHINGDATAINIDOCSEGMENTS
IfwearelookingforspecificinformationwithintheIDocsSegmentsthenthis
canbefoundusingTCODEWE09.Thisisusefulifyouaresearchingfora
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.
15/21
4/29/2016
IDOCVALIDATIONS,COMMONIDOCERRORSAND
SOLUTION
Though,theIDocfailuremaynotberelatedtoanyoftheabovementioned
reasons,thebestwaytofindtheIDocerroristocomparetheexistingIDoc
withthegoodexample.GoodexampleIDoccanbeeasilysearchedwithany
oftheIDocsearchmethodsasdescribedabove.
DOCUMENTATIONFORIDOCTYPES
IDocdocumentationcanbefoundusingTCODEWE60andcanbehelpfulto
obtaininformationoftheIDocTypeoritsparticularsegment.Italsoprovides
information such as mandatory and optional segments, minimum and
maximumnumberofsegments,etc.
16/21
4/29/2016
GENERAL INFORMATION FOR COMMON IDOC MESSAGE

TYPES
The following list gives the Basic Type and Message Type combination for
commonidocs
ARCHIVING/DELETIONOFIDOCSFROMDATABASE
As IDocs grow older they are archived and deleted from the database.
ArchivedIDocscanbeviewedusingTCODESARIinAchieveExplorerusing
archiving object as IDoc. Following are the few programs that are used for
archivinganddeletionofIDocsfromdatabase.
17/21
4/29/2016
255370Views
Products:sap_erp_logistics_materials_managementTopics:enterprise_resource_planningTags:sap,edi,idoc
AverageUserRating
(183ratings)
Share
94
42
Tweet
Like
116
256Comments
1 2 3 11
ManjunathRavi01Jan201317:41
Veryusefuldocument,keepupthegoodwork.
Expectingmoredocumentslikethisfromu.....
Withregards,
Tony.
Like(5)
RajuPrabhune02Jan201305:47
HiNiranjan,
Wow!!!Whatanexcellentdocument.WorkinginSAPforlast3year,1sttimeI'vefoundsucha
extensive/detaileddocumentonIDoc.
Congratulations&Happynewyear.
Like(3)
NarendraKonnipati08Jan201308:50
HiNiranjan,
WonderfulDocument(Itsseems,dontwantEDIConsultanttohandleissuesofEDIwhenwehave
thisDoc).
WishUHappyNewYearbuddy.
Thanks,
Naren
Like(2)
VithalBhadrachalam08Jan201322:57
HelloNiranjan,
Veryusefuldocument.ItwillhelpmanyconsultantstoenrichtheirknowledgeinIDOCs.
18/21
4/29/2016
Thankyouverymuch,
Vithal
Like(2)
NikhilKarnam28Jan201311:29
HiNiranjanBhai,
IDOCdocumentisveryhelpful.
Thanks,
Nikhil
Like(2)
SyedNayeemudenSN11Feb201316:42
HiNirajan,
DocumentisreallywonderfulanditwillreallyhelpfulformanySAPconsultantstogaintheir
knowledge.
Keeppostingsuchdocuments.....
Thanks
Nayeem.
Like(3)
AdamKrawczyk14Feb201314:02
VerycomprehensiveanddetailedblogaboutIDoc.
InfactasdeveloperIamjustsearchingforgeneraloverviewsoformeitisstilltootechnical,however
Ifoundheresomebasicconceptshereaswell.Thankyou,greatjob!
Regards,
Adam
Like(2)
naveenMarijoseph04Apr201312:20
Thanksfortheeffort
Like(1)
MdRuhulAmin10May201313:35
Itsreallyveryhelpfuldocument...
Like(1)
MdRuhulAmin11May201311:37
VerygoodandexcellentdocsforpeoplewhoarenewinIDOC.Itisusefulltomakethemaware
ofbusinessprocess
Like(2)
KalaiyarasanM13May201315:27
Hi,
Averygoodjob.Thisismuchinformative&helpsonetounderstandtheconceptinadetailedway.
Cheers!!!
kalai.
Like(2)
JasonZhuang30May201315:17
Thankssomuch.itisreallyagoodsharing.
Like(2)
Poornayalamanchili04Jun201303:55
Thanksforpostingthisdocument.veryinformativeandhelpfulforstarters
cheers
Poorna
Like(2)
BisweswarSahu12Jun201304:32
19/21
4/29/2016
NiceDoc.Thanksalot.
Bisweswar
Like(1)
TWTypewriter14Jun201314:24
Niranjan,
Veryinformativeandeasytounderstanddocument!
Manythanks!
Like(1)
RHEALYNTAN18Jun201311:20
thanksforthis.goodjob!
Like(1)
SrinuS20Jun201313:48
Reallywonderfuldocument.Keeponpostingthiskindofusefuldocument.
thankyouverymuch.
regards.
Srinu.
Like(2)
ItsikVersano20Jun201313:51
thanksforthis.greatwork!
Like(1)
MariaTeplyakova21Jun201307:59
HiNiranjanBhai,
I'dliketojoininallthesegoodcommentsandthanks.Plesekeepwritingsuchusefularticles.
Regards,Maria
Like(1)
venkatapochiraju21Jun201321:56
Thanksforthehardwork.Goodinformation.
Like(1)
SanthoshVenreddy24Jun201310:25
VeryUsefulArticle
Regards
Santhosh
Like(1)
24Jun201312:07
Niceblog!iftheSAPscreeniscolor,itwillbemuchmorebetter!
Thankyouforyournicejob!
Like(1)
ManaseeganK25Jun201313:18
Adetailedworkworthgoingthrough.
Regards,
Manas.
Like(1)
RanjithMNair26Jun201311:01
VeryInformativeforbuddingconsultants,ThankYou
Regards,
Ranjith
Like(2)
20/21
4/29/2016
RaviGupta27Jun201317:42
veryinformativeanddetailarticleonIDoc.
Thanks.
Like(1)
1 2 3 11
SiteIndex
Privacy
ContactUs
TermsofUse
SAPHelpPortal
LegalDisclosure
Copyright
FollowSCN
21/21

IDoc Basics For Functional Consultants - SCN

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

IDoc Basics For Functional Consultants - SCN

Diunggah oleh

Hak Cipta:

Format Tersedia

4/29/2016

Change Message Indicator indicates whether the IDoc is sent as a

Separate message type should be triggered in the purchase order for PO

Outbound IDocs can be triggered from the output message types of

TCode WE02 or WE05. When an IDoc is edited the original IDoc

GENERAL INFORMATION FOR COMMON IDOC MESSAGE

Anda mungkin juga menyukai