第 60 页 / 共 65 页
$SSHQGL[
*ORVVDU\
Access An access identifies the document fields used by the system when searching for a
condition record.
Access sequence Sequence used by Message Control to access condition records when searching for
messages.
Basic type IDoc type supplied by SAP. Basic types can be modified by customers to create a
new, upward-compatible IDoc type.
Condition element Part of hierarchy which is examined when searching for a message. An example is
the output type which is at the top of this hierarchy: When a (new) purchase order is
posted, only the messages under the node for the message type NEW are searched.
Condition record Data record in which the key fields represent the condition under which the message
is "found". The remaining fields describe the message itself. Therefore, if one of the
data records transferred from the application matches these key fields, the message
is found and can then be processed (for example exported as a print form or as an
electronic message).
Control record The part of an IDoc which contains the data for identifying the sender and recipient,
as well as the structure of the IDoc itself. Each IDoc always has one control record.
Data record The part of an IDoc which contains the application data. An IDoc usually contains
more than one data record.
EDI = Electronic Data Interchange. EDI (for example of business documents) between
business partners, sometimes in separate countries, who may use different hardware,
software and communication services. The data is formatted according to specific
standards.
EDI message Standard format for a business process (for example, a purchase order) to
be handled by EDI. Various EDI standards (EDIFACT or ANSI X12) can
define different EDI messages for the same business process.
EDI standard General format for data to be transferred electronically. An EDI standard generally
comprises:
o EDI syntax
o Data element service
o Message type service
The SAP standard ’IDoc’ is not yet an EDI standard, but can be compared to other
EDI standards.
EDI subsystem System which converts the SAP standard IDoc into an EDI standard (for example
EDIFACT, ANSI X12) and vice versa. In addition to this task (which is carried out
by the EDI subsystem convertor), there are also administration activities, for
example, archiving the transferred messages, and technical tasks, for example,
technical connection to the subsequent system and syntax checks for formats, to be
considered.
Field catalog Contains all fields which can be selected as key fields for condition tables in
Message Control.
File interface = port type “file”
Hierarchy level Determines the position of a segment in a tree segment. A segment carries business
data in an IDoc. Dependencies in the application data can be represented in this tree
structure, that is, the various hierarchy levels.
(C) SAP AG BC621 5-1
第 61 页 / 共 65 页
IDoc interface Definition of formats (IDoc types, previously: intermediate structures) and methods
(port definitions) for electronic data exchange between SAP Systems and partner
systems.
IDoc type SAP format in which data for a business process is to be transferred. An IDoc is a
real business process formatted according to a certain IDoc type.
Inbound processing Conversion and processing of data for a business process from the time the data is
received in IDoc format to the posting of the corresponding document(s) in the SAP
application.
Mandatory segment The part of an IDoc type which contains important application data and must
therefore exist in an IDoc for an actual business process.
Mapping Rules for assigning the data elements of an EDI message type to the fields of an
IDoc type.
Message Business process (for example, a purchase order), which is transferred in IDoc
format between an SAP System and an external system.
Message Control Module designed to offer interfaces for further processing for applications. This
includes descriptions of the various data configurations and the required actions. An
example of an action is printing a document at a certain time in German. The action
is triggered when the application transfers data which matches your configuration.
Message determination A check to determine whether the application data matches the condition records
(specified in Customizing). If this is the case, one or more messages are "found" and
can then be processed (for example, sent electronically). In message determination, a
search is made for the condition records using a predefined hierarchy.
Message status record = MC record. Log record for the MC table which describes the send status of a
message in Message Control.
Notification If an error occurs (for example, an IDoc with incorrect syntax), a notification is sent
to one or more users. The users responsible are defined in the IDoc Interface or
indirectly via the organization model. Notifications are sent to the integrated inbox.
Optional segment Part of an IDoc type which can include additional, optional data about the business
process. The segment does not therefore have to appear in an IDoc for a specific
business process.
Outbound file Contains specific IDocs to be sent for port type “file”.
Outbound processing Conversion and processing of SAP document data from posting a document to
sending the data in IDoc format.
Partner Communication partner for the IDoc Interface. Definition from Sales and
Distribution: "An individual within or outside of your own organization who is of
commercial interest and who can be contacted in the course of a business
transaction".
Partner profile Definition of the general conditions for electronic data interchange with a business
partner via the IDoc Interface: which message is sent in which direction using which
method?
If a partner profile does not exist, communication with a partner via the IDoc
Interface is not possible.
Port Description of the channel used by the SAP system for communicating with the
external system during external data interchange. There are various technical
methods for implementing this type of communication (port types). The selection of
the port type depends on the technical configuration of the external system.
Example: Most EDI subsystems read IDocs in the form of sequential files, that is,
the port type ’file’ is used.
Procedure A group of messages. A procedure is searched for messages which are to be
processed for the specified data configuration (for example, sent electronically or
printed).
(C) SAP AG BC621 5-2
第 62 页 / 共 65 页
Process code Another name for a defined processing type, for example a function module or an
SAP Business Workflow task. In contrast, a defined IDoc type (standard format for
data communication) is usually assigned to a certain process code. If the process
type for this IDoc type is to be changed, you should assign the corresponding
process code to the new processing type. Without this process code, this IDoc type
must be assigned to the new processing code directly.
Record type An IDoc type consists of the following three record types:
• Control record
• Data record
• Status record
Segment Structure which includes the application data for an IDoc from the data records. As
a result, the data can be assigned to the correct application fields.
Status Processing status of an IDoc, either "generated" or "ready for sending".
An IDoc usually has several statuses which are stored in the status records and
reveal information about the IDoc history. The current (processing) status is also
stored in the control record for the IDoc.
Status confirmation Report from an external system about the processing status of business data received
from the R/3 System in the form of status records. The status confirmation is added
to the IDoc in the R/3 System in the form of status records.
Status file File which contains the status records sent to the IDoc Interface by the EDI
subsystem for outbound messages.
Status group The status group contains several statuses ("milestones" in the process chain), so that
the monitoring programs only have to consider these groups and not each individual
status. Examples:
Group 3 = outbound: IDoc in the external system
Group B = inbound: IDoc sent to the application
Status record One of three record types in an IDoc (SAP standard format for electronic exchange
of application data).
Each status record contains a status which corresponds to one step in IDoc
processing. This means that the number of status records increases as the processing
continues.
Translator Converts internal data formats (IDocs) into EDI messages and vice versa. The
translator is a component of the EDI Subsystem.
Transmission file A data packet which contains the messages to be exchanged electronically. The
messages are EDI messages, that is, they are formatted according to an EDI standard
(for example EDIFACT).
The conversion of the SAP standard IDoc into the EDI standard is carried out by an
external system (EDI subsystem).
(C) SAP AG BC621 5-3
第 63 页 / 共 65 页
,PSRUWDQW(cid:3)0HQX(cid:3)3DWKV
$/((cid:3)5HJLVWUDWLRQ
IDoc initial node: ’HYHORSPHQWfi0HVVDJH(cid:18)$SSOLFDWLRQ(cid:3)REMHFW
$UFKLYLQJ
7RROVfi$GPLQLVWUDWLRQ(cid:15)(cid:3)$GPLQLVWUDWLRQfi’DWD(cid:3)DUFKLYLQJ
0DLQWDLQLQJ(cid:3)$UFKLYLQJ(cid:3)6WDWXV
IDoc initial node: &RQWUROfi0DLQWDLQ(cid:3)VWDWXV(cid:3)YDOXHV
,’RF(cid:3)$GPLQLVWUDWLRQ
IDoc initial node: &RQWUROfi,’RF(cid:3)$GPLQLVWUDWLRQ
’LVSOD\(cid:3),’RF
IDoc initial node: ,’RFfi’LVSOD\(cid:3),’RF
,’RF(cid:3),QLWLDO(cid:3)1RGH
7RROVfi%XVLQHVV(cid:3)&RPPXQLFDWLRQ(cid:15)(cid:3),’RFfi,’RF(cid:3)%DVLV
,’RF(cid:3)6WDWLVWLFV
IDoc initial node: ,’RFfi,’RF(cid:3)6WDWLVWLFV
,’RF(cid:3)7\SH(cid:3)(GLWRU
IDoc initial node: ’HYHORSPHQWfi,’RF(cid:3)W\SHV
3DUWQHU(cid:3)3URILOH
IDoc initial node: ,’RFfi3DUWQHU(cid:3)SURILOH
3RUW(cid:3)’HILQLWLRQ
IDoc initial node:(cid:3),’RFfi3RUW(cid:3)’HILQLWLRQfi0DLQWDLQ(cid:3)5)&(cid:3)GHVWLQDWLRQ
IDoc initial node: ,’RFfi,’RF(cid:3)GHVWLQDWLRQ
6HJPHQW(cid:3)(GLWRU
IDoc initial node: ’HYHORSPHQWfi,’RF(cid:3)VHJPHQWV
3URFHVVLQJ(cid:3)7HVWV
IDoc initial node: 7HVWfi(cid:31)PHQX(cid:3)RSWLRQ(cid:3)DFFRUGLQJ(cid:3)WR(cid:3)WKH(cid:3)UHTXLUHG(cid:3)IXQFWLRQ!
0HVVDJH(cid:3)$OORFDWLRQ(cid:3)–(cid:3),’RF(cid:3)7\SH
IDoc initial node: ’HYHORSPHQWfi,’RF(cid:3)W\SH(cid:18)PHVVDJH
(C) SAP AG BC621 5-4
第 64 页 / 共 65 页
([DPSOHV(cid:3)IRU(cid:3)8QLW(cid:3)(cid:23)
([DPSOHV(cid:3)(cid:5)6WHSV(cid:3)IRU(cid:3)GHYHORSPHQW(cid:3)RI(cid:3)RXWERXQG(cid:3)SURFHVVLQJ(cid:3)XVLQJ
0&(cid:5)(cid:29)
3XUFKDVH(cid:3)RUGHU(cid:15)(cid:3)00
IDoc type ORDERS01
Logical message ORDERS
Function module IDOC_OUTPUT_ORDERS
Outbound process code: ME10
2UGHU(cid:3)FRQILUPDWLRQ(cid:15)(cid:3)6’
IDoc type ORDERS01
Logical message ORDRSP
Function module IDOC_OUTPUT_ORDRSP
Outbound process code: SD10
,QERXQG(cid:3)SURFHVV(cid:3)FRGH(cid:29) 7;7(cid:20)
([DPSOH(cid:3)(cid:5)’HYHORSPHQW(cid:3)VWHSV(cid:3)RI(cid:3)LQERXQG(cid:3)SURFHVVLQJ(cid:3)E\(cid:3)%XVLQHVV
:RUNIORZ(cid:5)(cid:29)(cid:3)7H[W(cid:3)PHVVDJH(cid:15)(cid:3)LQERXQG
IDoc type: TXTRAW01
Logical message: TXTRAW
Object with method: IDOCTXTRAW.MAILCREATE
One-step task: TS30000008
Inbound process code: TXT1
(C) SAP AG BC621 5-5
第 65 页 / 共 65 页
([DPSOHV(cid:3)(cid:5)’HYHORSPHQW(cid:3)VWHSV(cid:3)IRU(cid:3)LQERXQG(cid:3)SURFHVVLQJ(cid:3)XVLQJ(cid:3)$/(
,QWHUIDFH(cid:5)
&XVWRPHU(cid:3)RUGHU(cid:15)(cid:3)6’
Transaction VA01
IDoc type ORDERS01
Logical message ORDERS
Function module IDOC_INPUT_ORDERS
Inbound process code ORDE
Object with method IDOCORDERS.INPUTFOREGROUND
One-step task TS00008046
This function module starts the command CALL TRANSACTION and thus an implicit COMMIT WORK (case 1
in the slide). This is the ALE layer (transaction BD51). VA01 calls IDOC_INPUT_OPEN and
IDOC_INPUT_CLOSE in order to write the IDoc status in the same LUW (it is "ALE-compatible“). If errors
occur, foreground processing is possible.
2UGHU(cid:3)DFNQRZOHGJPHQW(cid:15)(cid:3)00
IDoc type ORDERS01
Logical message ORDRSP
Function module IDOC_INPUT_ORDRSP
Inbound process code ORDR
Object with method IDOCORDRSP.INPUTFOREGROUND
One-step task TS00008075
This function module uses APIs (not a transaction) and does not start a COMMIT WORK (case 2 on the
slide). If errors occur, foreground processing is not possible.