SAP idoc 標(biāo)準(zhǔn)教程 BC620 IdocInterfaceTechnologyBC620EN46A

《SAP idoc 標(biāo)準(zhǔn)教程 BC620 IdocInterfaceTechnologyBC620EN46A》由會(huì)員分享，可在線閱讀，更多相關(guān)《SAP idoc 標(biāo)準(zhǔn)教程 BC620 IdocInterfaceTechnologyBC620EN46A（173頁珍藏版）》請(qǐng)?jiān)谘b配圖網(wǎng)上搜索。

1、 SAP AG 1999BC620 - SAP IDoc Interface (Technology) SAP AGBC620BC620 SAP IDocInterface(Technology) SAP IDocInterface(Technology) SAP AG 1999Copyright 2000 SAP AG. All rights reserved.Neither this training manual nor any part thereof maybe copied or reproduced in any form or by any means,or translate

2、d into another language, without the priorconsent of SAP AG. The information contained in thisdocument is subject to change and supplement without priornotice.All rights reserved.Copyright SAP AG 1999Business Integration Technologies IIBusiness IntegrationTechnologyBC0953 daysLevel 2Level 3Building

3、EnterpriseSolutions with SAPComponentsCA1502 daysData TransferBC4205 daysProgramming withBAPIs in Visual BasicCA9255 daysR/3 Interface and BAPIProgramming in C+CA9275 daysApplication LinkEnabling (ALE)TechnologyBC6193 daysEDI InterfaceCA2104 daysInterface ProgrammingData ExchangeCommunicationInterfa

4、ces in ABAPBC4152 daysProgramming withBAPIs in JAVACA9265 daysSAP IDoc Interface -DevelopmentBC6211 daySAP IDoc InterfaceTechnologyBC6202 days SAP AG 1999Recommended:Basic knowledge of the R/3 System, as gained fromcourses SAP20 and SAP50, for exampleCourse Prerequisites SAP AG 1999Participants:Cons

5、ultantsAdministratorsProject teammembersDuration: 2 daysTarget Group SAP AG 1999Course OverviewCourse GoalsCourse Objective(s)Course ContentCourse Overview DiagramMain Business ScenarioContents: SAP AG 1999 Understand the possibilities offered by theIDoc Interface for electronic data transfer Use th

6、e IDoc InterfaceCourse GoalsThis course will enable you to: SAP AG 1999Course Objective(s) Configure the IDoc Interface Trace the processing of IDocs in thesystem Select and use the correct IDoc types foryour business processesAt the conclusion of this course, you will beable to: SAP AG 1999Course C

7、ontentUnit 9General SettingsUnit 10Further Test ProgramsUnit 11A Process ChainUnit 12Statistics and MonitoringUnit 13Workflows and IDocsUnit 14Using an EDI SubsystemUnit 15ArchivingUnit 1Course OverviewUnit 2Basic PrinciplesUnit 3IDocs in Business ProcessUnit 4Documentation ToolsUnit 5Port Definitio

8、nUnit 6Partner ProfilesUnit 7The Test ToolUnit 8MC and IDocsPreface and IntroductionExercisesSolutionsAppendix SAP AG 1999Main Business ScenarioMessageIDocIDocQuickDeliverSmartMartSAP R/3 SystemSAP R/3 SystemEDI SubsystemEDI SubsystemEDI SubsystemEDI SubsystemSAP R/3 SystemSAP R/3 System SAP AG 1999

9、Basic PrinciplesIDoc concept and fundamental termsData flow and process flows when using the IDoc InterfaceContents: SAP AG 1999Explain the terms IDoc, EDI and ALEIdentify the basic steps in IDoc processingTopic ObjectivesAt the conclusion of this unit, you will be able to: SAP AG 1999IDoc ConceptMe

10、ssage-orientedAsynchronousSystem 1DocumentSystem 2IDocDocument SAP AG 1999IDoc ApplicationsWorkflowWorkflowBusinessBusinessConnectorConnectorElectronicElectronicFormFormALEALEEDIEDISubsystemSubsystemR/3 SystemR/3 SystemR/2 SystemR/2 SystemOtherOtherSystems.Systems.InternetInternetIntranetIntranetIDo

11、cIDoc SAP AG 1999EDI and ALEDocumentIDocMessageIDocIDocSAP R/3 SystemSAP R/3 SystemEDI SubsystemEDI SubsystemEDI SubsystemEDI SubsystemSAP R/3 SystemSAP R/3 System SAP AG 1999Process Flow: Sending DataCheck partner, find portTransfer data,process furtherPost documentGenerate IDocR/3 SystemR/3 System

12、External systemExternal system SAP AG 1999IDoc Settings: Sending DataPost documentGenerate IDocCheck partner, find portTransfer data,process furtherArchive IDoc ?Archive IDoc ?EDI Subsystem ?EDI Subsystem ?Partner ProfilesPartner ProfilesPort DefinitionPort DefinitionDocumentationToolsDocumentationT

13、oolsR/3 SystemR/3 SystemExternal SystemExternal System SAP AG 1999Process Flow: Receiving DataError handlingok?ok?NoNoCheck port & partner,Generate IDocSend data toR/3 SystemtransferPost documentR/3 SystemR/3 SystemExternal SystemExternal System SAP AG 1999IDoc Settings: Receiving DataError handling

14、Send data toR/3 SystemCheck port & partner,generate IDocPost documentPort Definition,Partner ProfilesPort Definition,Partner ProfilesArchive IDoc ?Archive IDoc ?DocumentationToolsDocumentationToolsEDI Subsystem ?EDI Subsystem ?R/3 SystemR/3 SystemExternal SystemExternal System SAP AG 1999IDoc is an

15、SAP standard for data transfer betweensystems.Known implementation areas for IDocs: ALE andEDI scenariosThe IDoc Interface facilitates both IDoc processingand flexible error/exception handlingBasic Principles: Summary SAP AG 1999IDoc Record TypesIDoc and IDoc typeIDoc processing: Inbound and outboun

16、dprocessingIDocs in Business Processes SAP AG 1999At the conclusion of this unit, you will be able to:IDocs in Business Processes: Course Objectives Explain the difference between IDocs andIDoc types Describe the structure of an IDoc Determine where in the business process orthe process chain the ID

17、oc was created SAP AG 1999Business scenarioAs a member of the implementation team foryour company (SmartMart or QuickDeliver), youare responsible for configuring the IDocInterface. You must therefore understand thebasic principles behind the interface: the IDocformat and how to embed the interface i

18、n bothoutbound processing (SmartMart) and inboundprocessing (QuickDeliver). SAP AG 1999IDoc Record TypesStatus recordsData recordsControl record SAP AG 1999Control recordControl recordIDoc IDPartnerIDoc type and logical messageExternal structure SAP AG 1999Data Records and Segment StructuresData rec

19、ordControl part, containssegment namesApplication dataField 2Field 1.Segment SAP AG 1999Status RecordStatus RecordIDoc IDStatus information SAP AG 1999IDoc Record Types: SummaryControl recordData recordsIDoc IDPartnerIDoc type and logical messageExternal structureControl partApplication dataStatus r

20、ecordsIDoc IDStatus information SAP AG 1999IDoc TypesControl RecordStatus RecordsData records, represented as a segment treeE1TLSUME1HDADRE1ITSCHE1HDDOCE1ITDOCElternsegmentKindsegmentE1ITSCHC5E1ITDOCM1C99M1C5C1 SAP AG 1999Outbound and Inbound ProcessingOutbound ProcessingInbound IDoc Interface/ALE S

21、ervicesExternal SystemSAP ApplicationR/3 System SAP AG 1999Outbound Processing using MessageControlIDocIDocMCMCrecordrecordDocumentDocumentSAP ApplicationMessage Control (MC)External SystemIDoc Interface / ALE Services SAP AG 1999Comm. IDocComm. IDocComm. IDocComm. IDocComm. IDocComm. IDocMaster IDo

22、cMaster IDocDirect Outbound Processing using ALESAP ApplicationExternal SystemIDoc Interface / ALE Services SAP AG 1999Inbound Processing using WorkflowDocumentDocumentIDoc +IDoc +processprocessIDocIDocSAP ApplicationSAP Business WorkflowExternal SystemIDoc Interface & ALE Services SAP AG 1999IDocID

23、ocDirect Inbound Processing using ALEIDocIDocSAP ApplicationExternal SystemIDoc Interface & ALE Services SAP AG 1999IDocs in Business Processes: SummaryEach IDoc in the R/3 database consists of one controlrecord and several data and status records. Onlycontrol records and data records are exchanged

24、withexternal systems.There are various IDoc types which are distinguishedby their segments and their order. This information isstored in the control part of the data records.Different processing options are available for IDocs inboth inbound and outbound processing.IDocs in Business Processes Exerci

25、seIDocs in Business Processes Solutions SAP AG 1999Documentation ToolsRecord types, IDoc types, segmentsOutput formats SAP AG 1999Use the documentation toolsDecide in which situations they would be usefulAt the conclusion of this unit, you will be able to:Documentation Tools: Unit Objectives SAP AG

26、1999Overview Diagram (Sending Data)R/3 SystemR/3 SystemPost documentGenerate IDocCheck partner, find portTransfer data,process furtherArchive IDoc ?Archive IDoc ?EDI Subsystem ?EDI Subsystem ?DocumentationToolsDocumentationToolsPartner ProfilesPartner ProfilesPort DefinitionPort DefinitionExternal S

27、ystemExternal System SAP AG 1999Business scenarioAs a member of the implementation team for yourcompany (SmartMart or QuickDeliver), you areresponsible for configuring the IDoc Interface.Your EDI subsystem does not yet know the structureof the IDoc type to be used. The IDoc Interface canexport IDoc

28、type structures in various formats, usingthe documentation tools. You must know about thisfunction, as you can save yourself a lot ofprogramming work in the EDI subsystem. SAP AG 1999Documentation Tools: SummaryThe documentation tools describe both thestructure and the use of different IDocs.The str

29、ucture is in the structure information.External structures are always documented,specifically regarding how they are exchangedwith external systems.The output formats can be read by externalsystems, so that non-R/3 Systems can quicklyrecognize the IDoc structure.Documentation Tools Exercise SAP AG 1

30、999Port DefinitionPort types and when they are usedPort definition parametersCommunication with Older Releases SAP AG 1999Decide which port types should be implementedfor which external systemsEnter a port definition in the R/3 SystemDetermine which additional steps are required forlinking to the re

31、levant external systemEnter special settings which are required forcommunication with older R/3 releases and R/2SystemsAt the conclusion of this unit, you will be able to:Port Definition: Unit Objectives SAP AG 1999Overview Diagram (Sending Data)R/3 SystemR/3 SystemPost documentGenerate IDocCheck pa

32、rtner, find portTransfer data,process furtherArchive IDoc ?Archive IDoc ?EDI Subsystem ?EDI Subsystem ?DocumentationToolsDocumentationToolsPartner ProfilesPartner ProfilesPort DefinitionPort DefinitionExternal SystemExternal System SAP AG 1999Port Definition: Business ScenarioAs a member of the impl

33、ementation team forSmartMart, you are responsible for configuringthe IDoc Interface.You must decide which port type is suitable forthe system of your partner companyQuickDeliver. SAP AG 1999IDoc Interface: Port TypesIDoc InterfaceCPI-CR/2 SystemExternal SystemFileIDoc/IDoc/statusstatusIDoc/IDoc/stat

34、usstatusPIIDocIDoc?XMLIDocIDoctRFCIDocIDocInternetIDocIDoc SAP AG 1999Process Flow: Port Type File (with Triggering)1WriteIDoc file4Read2RFC3Callrfcexecout.script1WriteIDoc fileStatus reportstartrfcin.scriptstatus.script3RFC2Call4ReadIDoc InterfaceExternal System SAP AG 1999Port Type XML: Flat File

35、and XML FileEDI_DC40 004000000000030702346B 3013 ORDERS01.E2EDP01005 00400000000003070230000210000000200E2EDP20 00400000000003070230000220000210323.E2EDPT1001 004000000000030702300002600002103BESTDE2EDPT2001 004000000000030702300002700002604This is SAP AG 1999Port Type XML: Flat File and XML File (2

36、)EDI_DC40E1EDP01E1EDP20E1EDPT1E1EDPT20040000000000307023.00010 001023.000.23.000 19990622.BESTD.This is thepurchase order text. SAP AG 1999Port Definition - Port Type tRFCRFC destination(R/3 connection)Port name (assigned automatically)Application server for receiving system SAP AG 1999Port Definiti

37、on: CPI-C (R/2 System)Host destinationRFC destinationTechnical parametersSend status records?sideinfo-entryHost on R/2TXCOM entry SAP AG 1999Process Flow: Port Type PIIDoc InterfaceOwn function moduleIDocIDoc SAP AG 1999Communication with Older ReleasesField 1Field 2Field 1Field 2Field 22.1/2.23.0/3

38、.14.XNew field 3Field 1Field 3Differences in IDoc record types SAP AG 1999Port Definition: SummaryIDocs or status records are always exchanged with anexternal system via a port.In the port definition for the IDoc Interface, users definethe target system and the technical communicationparameters. In

39、addition, users can specify the releasestatus for the external system via the version entry.Additional technical settings must also be entered (alsooutside R/3), before a port can be used.There are six basic communication techniques for theIDoc Interface, represented by the six different porttypes.P

40、ort Definition Exercise SAP AG 1999Partner ProfilesStandard partner profilesChecking Partner ProfilesFast entry SAP AG 1999Partner Profiles: Unit ObjectivesAt the conclusion of this unit, you will be able to:Explain the purpose of partner profiles andprocess codesMaintain partner profiles SAP AG 199

41、9Overview Diagram (Sending Data)R/3 SystemR/3 SystemPost documentGenerate IDocCheck partner, find portTransfer data,process furtherArchive IDoc ?Archive IDoc ?EDI Subsystem?EDI Subsystem?DocumentationToolsDocumentationToolsPartner ProfilesPartner ProfilesPort DefinitionPort Definition SAP AG 1999Par

42、tner Profiles: Business ScenarioSmartMart must define QuickDeliver as a partner.You have already configured a suitable port in theport definition.In outbound processing, QuickDeliver is the partnerfor the purchase order. In outbound processing, itis the partner for the order acknowledgment. SAP AG 1

43、999Partner Profiles: Outbound Processing IIDocIDocMCMCrecordrecordDocumentDocumentDocumentDocumentSAP ApplicationMCReceiving SystemIDoc Interface / ALE ServicesMC settingsMC settingsGeneral+outboundGeneral+outbound SAP AG 1999Partner Profiles: Outbound Processing IIProcess code: ME10Message: ORDERSP

44、artner: QD; Output type: ORDERSPort: SUBSYSTEM Permitted agent:IDoc type: ORDERS01 EDI agent for partner QuickDeliver (QD) (purchase orders)GeneralOutboundMCsettingsPartner: QD ; Appl: EF; OtptType : NEWObject type,language,.Partner: QD ; Appl: EF; OtptType : NEWMC record SAP AG 1999Partner Profiles

45、: Inbound ProcessingProcess code:ORDR;Permitted agents: EDIagent for partnerQuickDeliver, orderacknowledgmentsIDocControl RecordInb. ProcessingPartner: QD; Message: ORDRSPIDoc type:ORDERS01Partner: QD; Message: ORDRSP SAP AG 1999Process Codes IPartnerApplicationMess.typeProcess codeExample: MC param

46、eters in partner profilesProcess codeFunction module (writes the applicationdata in an outbound IDoc) SAP AG 1999Process codeProcess Codes IIPartnerMessageProcess codeExample: Inbound Function module/workflow (reads data from aninbound IDoc and processes data further) SAP AG 1999Process Codes IIIDoc

47、umentation via messagesProcess codeMessagenm SAP AG 1999Outbound Modes: Port Type FileDescriptionTransfer single IDoc +start external system (trigger)Transfer single IDoc;no triggerTransfer multiple IDocs + startexternal system (trigger)Transfer multiple IDocs;no triggerPartner profile SAP AG 1999Pa

48、rtner Profiles OutputDisplay SAP AG 1999Partner Profiles: SummaryPartner profiles specify which messages are sent to whichusers, using which method and how they are processed.Partners must be entered in the partner profile before IDocs canbe sent successfully.The port (the way) is part of the outbou

49、nd partner profile.Technical communication parameters are entered in the portdefinition. Inbound ports do not require such parameters - theirtechnical parameters are defined by the external sendingsystem.Process codes are also part of the partner profiles.They are used for processing data.Process co

50、des which are defined outside the partner profile areused in error handling.Partner Profiles Exercise SAP AG 1999The Test ToolTest Tool Options SAP AG 1999Test Tool OptionsTest Tool Exercise SAP AG 1999Message Control and IDocsMessage determination and message processingCondition componentsDispatch

51、times SAP AG 1999Message Control and IDocs: Unit ObjectivesAt the conclusion of this unit, you will be able to:Explain condition componentsFind examples of condition components in MMCustomizingDisplay and process the proposed message from theMM application transaction SAP AG 1999Business ScenarioAs

52、a member of the implementation team forSmartMart, you are responsible for configuring theIDoc Interface.A purchase order from SmartMart is firstly created as amessage by the Message Control module, before beingconverted into IDoc format. You know that the basicsettings for this module exist in the s

53、tandard SAPsystem, but wish to find out more about other MessageControl functions. SAP AG 1999Outbound Processing using MessageControlMCMCrecordrecordDocumentDocumentSAP ApplicationMCIDoc Interface/ALE ServicesFind proposalEditProcess SAP AG 1999Condition ElementsProcedureSAP ApplicationOutput TypeA

54、ccess SequenceCondition Table1:nm:nn:1m:n SAP AG 1999Message Processing: IDocsRSNASTEDCheck MC recordRead partner profileCall selection module(from application)Call ALE ServicesTransfer according tooutput mode1/ 23/ 4Single IDocMultiple IDocs via RSEOUT00 SAP AG 1999Dispatch Times in Outb. Procg usi

55、ng MCApplicationMCIDoc InterfaceExternal SystemReal timeFast batchPostOUTMOD = 1PostOUTMOD = 1PostOUTMOD = 3PostOUTMOD = 4BatchBatchVSZTP = 1VSZTP = 1VSZTP = 1VSZTP = 4 SAP AG 1999SummaryMessage Control is important in IDoc outboundprocessing.Messages defined in Customizing are examined in acertain

56、sequence to determine whether or not theyapply to the current application data. This sequence isdefined by the condition components and theirhierarchy.IDoc-specific message processing takes place viaprogram RSNASTED.Up to three different dispatch times can be defined foroutbound processing.Message C

57、ontrol and IDocs ExerciseMessage Control and IDocs: SolutionUnit: Message Control and IDocsTopic: Condition elements SAP AG 1999General SettingsNumber rangesEvent-receiver linkageIDoc administrationFast entryLong names - short names SAP AG 1999General Settings: Unit ObjectivesAt the conclusion of th

58、is unit, you will be able to:Configure the general parameters in the IMGDescribe when the IDoc Administrator is notified SAP AG 1999Customizing using the IMGR/3 Customizing IMGCross-applicationcomponentsIDoc InterfaceIMG documentationProject documentationProject managementActivities SAP AG 1999Numbe

59、r RangesIDoc Interface SAP AG 1999Event-Receiver LinkageIDoc InterfaceR/3 ApplicationProcessingProcessing SAP AG 1999IDoc Administration: Global Parameters SAP AGParty to be notified (IDoc Administrator)System environment (Basis system?)Processing details SAP AG 1999 SAP AGIDoc Administration: User

60、ParametersTestsDocumentation ToolsDevelopment SAP AG 1999Fast entryDefault values SAP AG 1999Long Names - Short NamesRelease 4.0Release 3.XTypeLongNameXYZ01Type Short01 SAP AG 1999General Settings: SummaryGeneral settings are entered via the IMG. Inaddition, user-specific parameters can be changedat

61、 any time via the control menu.The IDoc Administrator is part of the globalparameters which are maintained in IDocAdministration. When exceptions occur, theadministrator is always notified if no partner profileis found.General Settings Exercise SAP AG 1999Additional Test ProgramsTest layersTest prog

62、rams SAP AG 1999Processing Tests: Unit ObjectivesUse special test programs and determine when toimplement them during processingAt the conclusion of this unit, you will be able to: SAP AG 1999Processing Tests: Business ScenarioAs a member of the implementation team for yourcompany (SmartMart or Quic

63、kDeliver), you areresponsible for configuring the IDoc Interface.After tests have been completed successfully inyour own system and the EDI subsystem has beenconnected, you wish to test data transfer.The IDoc Interface test programs are to be used forthis purpose and this unit contains informationab

64、out using these tools. SAP AG 1999Test Layers: OverviewInboundIDoc fileApplicationIDoc InterfaceWorkflowMCOutboundIDoc fileStatusconfirm.WE12WE16WE17WE19 ,WE18WE15WE14, WE19File SystemExternalSystemWE18 SAP AG 1999Test Layers: Outbound ProcessingApplicationMCWE15WE14, WE19ExternalSystemIDoc Interfac

65、e MC SAP AG 1999Test Layers: Inbound ProcessingInboundIDoc fileApplicationIDoc InterfaceWorkflowOutboundIDoc fileWE12WE16WE19File System SAP AG 1999Test Layers: Status ConfirmationApplicationIDoc InterfaceWorkflowWE17File SystemOutboundfile withSYSTAT01WE12WE16WE19 ,WE18Inbound file withSYSTAT01Stat

66、usconfirm.WE18 SAP AG 1999When to Test Which Function?Data exchange with the file system: WE14(outbound), WE16 (inbound), WE17 (statusconfirmation, inbound)Processing MC record: WE15Data transfer from the IDoc Interface to additionalinbound processing: WE19Data transfer to any port: WE14 SAP AG 1999Processing Tests: SummarySpecial test programs require MC records, files orexisting IDocs from the database. If necessary,automatic outbound processing must be stopped viathe output mode from the part