SAP idoc 标准教程 BC620 IdocInterfaceTechnologyBC620EN46AVIP

1、 sap ag 1999 bc620 - sap idoc interface (technology) sap ag bc620bc620 sap idoc interface (technology) sap idoc interface (technology) sap ag 1999 copyright 2000 sap ag. all rights reserved. neither this training manual nor any part thereof may be copied or reproduced in any form or by any means, or

2、 translated into another language, without the prior consent of sap ag. the information contained in this document is subject to change and supplement without prior notice. all rights reserved. copyright sap ag 1999 business integration technologies ii business integration technology bc0953 days lev

3、el 2level 3 building enterprise solutions with sap components ca1502 days data transfer bc4205 days programming with bapis in visual basic ca9255 days r/3 interface and bapi programming in c+ ca9275 days application link enabling (ale) technology bc6193 days edi interface ca2104 days interface progr

4、amming data exchange communication interfaces in abap bc4152 days programming with bapis in java ca9265 days sap idoc interface - development bc6211 day sap idoc interface technology bc6202 days sap ag 1999 recommended: basic knowledge of the r/3 system, as gained from courses sap20 and sap50, for e

5、xample course prerequisites sap ag 1999 participants: consultants administrators project team members duration: 2 days target group sap ag 1999 course overview course goals course objective(s) course content course overview diagram main business scenario contents: sap ag 1999 understand the possibil

6、ities offered by the idoc interface for electronic data transfer use the idoc interface course goals this course will enable you to: sap ag 1999 course objective(s) configure the idoc interface trace the processing of idocs in the system select and use the correct idoc types for your business proces

7、ses at the conclusion of this course, you will be able to: sap ag 1999 course content unit 9general settings unit 10further test programs unit 11a process chain unit 12statistics and monitoring unit 13workflows and idocs unit 14using an edi subsystem unit 15archiving unit 1course overview unit 2basi

8、c principles unit 3idocs in business process unit 4documentation tools unit 5port definition unit 6partner profiles unit 7the test tool unit 8mc and idocs preface and introduction exercises solutions appendix sap ag 1999 main business scenario message idocidoc quickdeliver smartmart sap r/3 systemsa

9、p r/3 system edi subsystemedi subsystem edi subsystemedi subsystem sap r/3 systemsap r/3 system sap ag 1999 basic principles idoc concept and fundamental terms data flow and process flows when using the idoc interface contents: sap ag 1999 explain the terms idoc, edi and ale identify the basic steps

10、 in idoc processing topic objectives at the conclusion of this unit, you will be able to: sap ag 1999 idoc concept message-oriented asynchronous system 1 document system 2 idoc document sap ag 1999 idoc applications workflowworkflow businessbusiness connectorconnector electronicelectronic formform a

11、leale ediedi subsystemsubsystem r/3 systemr/3 system r/2 systemr/2 system otherother systems.systems. internetinternet intranetintranet idocidoc sap ag 1999 edi and ale document idoc message idocidoc sap r/3 systemsap r/3 system edi subsystemedi subsystemedi subsystemedi subsystem sap r/3 systemsap

12、r/3 system sap ag 1999 process flow: sending data check partner, find port transfer data, process further post document generate idoc r/3 systemr/3 system external systemexternal system sap ag 1999 idoc settings: sending data post document generate idoc check partner, find port transfer data, proces

13、s further archive idoc ? archive idoc ? edi subsystem ? edi subsystem ? partner profiles partner profiles port definition port definition documentation tools documentation tools r/3 systemr/3 system external systemexternal system sap ag 1999 process flow: receiving data error handling ok? ok? no no

14、check port output type: orders port: subsystem permitted agent: idoc type: orders01 edi agent for partner quickdeliver (qd) (purchase orders) general outbound mc settings partner: qd ; appl: ef; otpttype : newobject type, language,. partner: qd ; appl: ef; otpttype : new mc record sap ag 1999 partne

15、r profiles: inbound processing process code: ordr; permitted agents: edi agent for partner quickdeliver, order acknowledgments idoc control record inb. processing partner: qd; message: ordrsp idoc type: orders01 partner: qd; message: ordrsp sap ag 1999 process codes i partner application mess.type p

16、rocess code example: mc parameters in partner profiles process code function module (writes the application data in an outbound idoc) sap ag 1999 process code process codes ii partner message process code example: inbound function module/workflow (reads data from an inbound idoc and processes data f

17、urther) sap ag 1999 process codes iii documentation via messages process code message n m sap ag 1999 outbound modes: port type file description transfer single idoc + start external system (trigger) transfer single idoc; no trigger transfer multiple idocs + start external system (trigger) transfer

18、multiple idocs; no trigger partner profile sap ag 1999 partner profiles output display sap ag 1999 partner profiles: summary partner profiles specify which messages are sent to which users, using which method and how they are processed. partners must be entered in the partner profile before idocs ca

19、n be sent successfully. the port (the way) is part of the outbound partner profile. technical communication parameters are entered in the port definition. inbound ports do not require such parameters - their technical parameters are defined by the external sending system. process codes are also part

20、 of the partner profiles. they are used for processing data. process codes which are defined outside the partner profile are used in error handling. partner profiles exercise sap ag 1999 the test tool test tool options sap ag 1999 test tool options test tool exercise sap ag 1999 message control and

21、idocs message determination and message processing condition components dispatch times sap ag 1999 message control and idocs: unit objectives at the conclusion of this unit, you will be able to: explain condition components find examples of condition components in mm customizing display and process

22、the proposed message from the mm application transaction sap ag 1999 business scenario as a member of the implementation team for smartmart, you are responsible for configuring the idoc interface. a purchase order from smartmart is firstly created as a message by the message control module, before b

23、eing converted into idoc format. you know that the basic settings for this module exist in the standard sap system, but wish to find out more about other message control functions. sap ag 1999 outbound processing using message control mcmc recordrecord documentdocument sap application mc idoc interf

24、ace/ale services find proposal edit process sap ag 1999 condition elements procedure sap application output type access sequence condition table 1:n m:n n:1 m:n sap ag 1999 message processing: idocs r s n a s t e d check mc record read partner profile call selection module (from application) call al

25、e services transfer according to output mode 1/ 23/ 4 single idoc multiple idocs via rseout00 sap ag 1999 dispatch times in outb. procg using mc applicationmcidoc interfaceexternal system real time fast batch postoutmod = 1 postoutmod = 1 postoutmod = 3 postoutmod = 4 batch batch vsztp = 1 vsztp = 1

26、 vsztp = 1 vsztp = 4 sap ag 1999 summary message control is important in idoc outbound processing. messages defined in customizing are examined in a certain sequence to determine whether or not they apply to the current application data. this sequence is defined by the condition components and their

27、 hierarchy. idoc-specific message processing takes place via program rsnasted. up to three different dispatch times can be defined for outbound processing. message control and idocs exercise message control and idocs: solutionunit: message control and idocs topic: condition elements sap ag 1999 gene

28、ral settings number ranges event-receiver linkage idoc administration fast entry long names - short names sap ag 1999 general settings: unit objectives at the conclusion of this unit, you will be able to: configure the general parameters in the img describe when the idoc administrator is notified sa

29、p ag 1999 customizing using the img r/3 customizing img cross-application components idoc interface img documentation project documentation project management activities sap ag 1999 number ranges idoc interface sap ag 1999 event-receiver linkage idoc interface r/3 application processingprocessing sa

30、p ag 1999 idoc administration: global parameters sap ag party to be notified (idoc administrator) system environment (basis system?) processing details sap ag 1999 sap ag idoc administration: user parameters tests documentation tools development sap ag 1999 fast entry default values sap ag 1999 long

31、 names - short names release 4.0release 3.x type longnamexyz01 type short01 sap ag 1999 general settings: summary general settings are entered via the img. in addition, user-specific parameters can be changed at any time via the control menu. the idoc administrator is part of the global parameters w

32、hich are maintained in idoc administration. when exceptions occur, the administrator is always notified if no partner profile is found. general settings exercise sap ag 1999 additional test programs test layers test programs sap ag 1999 processing tests: unit objectives use special test programs and

33、 determine when to implement them during processing at the conclusion of this unit, you will be able to: sap ag 1999 processing tests: business scenario as a member of the implementation team for your company (smartmart or quickdeliver), you are responsible for configuring the idoc interface. after

34、tests have been completed successfully in your own system and the edi subsystem has been connected, you wish to test data transfer. the idoc interface test programs are to be used for this purpose and this unit contains information about using these tools. sap ag 1999 test layers: overview inbound i

35、doc file application idoc interface workflowmc outbound idoc file status confirm. we12 we16we17 we19 , we18 we15 we14, we19 file system external system we18 sap ag 1999 test layers: outbound processing application mc we15 we14, we19 external system idoc interface mc sap ag 1999 test layers: inbound

36、processing inbound idoc file application idoc interface workflow outbound idoc file we12 we16 we19 file system sap ag 1999 test layers: status confirmation application idoc interface workflow we17 file system outbound file with systat01 we12 we16 we19 , we18 inbound file with systat01 status confirm

37、. we18 sap ag 1999 when to test which function? data exchange with the file system: we14 (outbound), we16 (inbound), we17 (status confirmation, inbound) processing mc record: we15 data transfer from the idoc interface to additional inbound processing: we19 data transfer to any port: we14 sap ag 1999

38、 processing tests: summary special test programs require mc records, files or existing idocs from the database. if necessary, automatic outbound processing must be stopped via the output mode from the partner profile and the dispatch time in the mc condition record. the test tool allows general test

39、s for inbound processing, outbound processing and status confirmation via systat01. sap ag 1999 a process chain send purchase order post standard order sap ag 1999 a process chain: unit objectives at the conclusion of this unit, you will be able to: send a purchase order via idoc receive a standard

40、order via idoc explain which edi-specific master data must be maintained sap ag 1999 a process chain: business scenario as a member of the implementation team for your company (smartmart or quickdeliver), you are responsible for configuring the idoc interface. for test purposes, idocs are to be crea

41、ted by smartmart and sent to quickdeliver. sap ag 1999 edi-relevant master data in purchasing idoc type orders01 e1edka1 (parvw = “ag”): partner information e1edp19 (qualf= “001”): material number data record data record e1edka1 (parvw = lf): partner information data record vendor master record : pa

42、rtner number, type, function vendor master record : vendor account material master record: material name vendor material number: material name for vendor mc condition record with transmiss. medium 6 (edi) e1edp19 (qualf= “002”): material number data record sap ag 1999 standard order for quickdeliver

43、 r/3 systemr/3 system generate work item ok? ok? no no send data to r/3 system determine processing for smartmart data, generate idoc post standard order external system =external system = quickdeliver quickdeliver edi subsystem edi subsystem sap ag 1999 edi-specific master data in sales idoc type o

44、rders01 idoc type orders01 e1edka1 (parvw = lf): partner information e1edp19 (qualf= “002”): material number data record data record customer master record: partner number, type, function sd customizing: assigning customer/ vendor to sales organization material master record: material name e1edka1 (

45、parvw = “ag”): partner information data record sap ag 1999 a process chain: summary special edi parameters must be entered in the application master data. these include partner information and transmission medium 6 in the condition record for outbound processing using message control (mc). outbound

46、processing using message control is always applied for purchase orders from the mm module. process chain exercise sap ag 1999 statistics and monitoring passive and active monitoring work item analysis sap ag 1999 statistics and monitoring: unit objectives at the conclusion of this unit, you will be

47、able to: decide when different tools should be implemented for idoc monitoring use the individual monitoring transactions sap ag 1999 business scenario as a member of the implementation team for your company (smartmart or quickdeliver), you are responsible for configuring the idoc interface. the exc

48、hange of idocs between the two companies is to be monitored. as a result, you must be familiar with the idoc monitoring tools available for the idoc interface. sap ag 1999 monitoring programs: overview active monitoring passive monitoring 4712 4711 4713 4718 display rseidocmstatistics list, idoc sea

49、rch sap ag 1999 selection fields for monitoring control record creation date change date partner, message,. idoc statistics idoc list idoc search idoc display active monitoring edi references sap ag 1999 status group: monitor/statistics 4 = idoc transfer4 = idoc transfer successfulsuccessful 39 = id

50、oc in target system (ale) 12 = send ok 13 = send ok retransmission ok 0 20 40 60 80 100 1. qrtl. 2. qrtl. 3. qrtl. 4. qrtl. sap ag 1999 work item analysis usually refers to exception handling work items which exist in the system are listed application for lost work items, for example (no user select

51、ed) sap ag 1999 the idoc data flow can be monitored via four passive programs and one active program in the idoc interface. active monitoring is a function which can be individually configured for error handling or general exception handling. the level of detail in the passive monitoring programs go

52、es as far as displaying the individual idocs. the least-detailed monitoring tool is the status group display under idoc statistics. statistics and monitoring: summary statistics and monitoring exerciseunit: statistics and monitoring topic: passive monitoring statistics and monitoring: solution unit:

53、 statistics and monitoring sap ag 1999 workflow and idocs inbound processing exception handling notification concept organizational structure sap ag 1999 workflow and idocs: unit objectives at the conclusion of this unit, you will be able to: explain how the agent responsible is informed if an error

54、 occurs during idoc processing maintain the organizational structure sap ag 1999 workflow and idocs: business scenario as a member of the implementation team for quickdeliver, you are responsible for configuring the idoc interface. a purchase order from smartmart is received by quickdeliver as an in

55、bound idoc of type orders01. inbound processing is configured using a process code as direct via a function module, exception handling takes place by means of workflow. you must configure a party to be notified if an error occurs. sap ag 1999 inbound processing with workflow sap application document

56、document idoc +idoc + processprocess workflow idoc interface inbound processing with ale?; permitted agents; and so on. sap ag 1999 more documentation begin end typedef struct z2incodx000 z2incodx000 idoc interface: documentation tools xml sap ag 1999 the edi subsystem is used mainly for converting

57、the idoc format into an edi standard (and vice versa). the edi subsystem is an interface to external systems and has its own responsibilities. format definitions can be defined in the edi subsystem in a form which can be read by other systems. using an edi subsystem: summary using an edi subsystem exercise