The SAP R/3 guide to EDI and interfaces: cut your implementation cost with IDocs, ALE and RFC
Gespeichert in:
| Beteiligte Personen: | , , |
|---|---|
| Format: | Buch |
| Sprache: | Englisch |
| Veröffentlicht: |
Braunschweig ; Wiesbaden
Vieweg
2001
|
| Ausgabe: | 2., rev. ed. |
| Schriftenreihe: | Vieweg Business Computing
|
| Schlagwörter: | |
| Links: | http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=009250618&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
| Beschreibung: | Online-Service zum Buch unter der Adresse http://idocs.de und http://logosworld.com verfügbar |
| Umfang: | XIX, 148 S. Ill. : 24 cm |
| ISBN: | 3528157291 |
Internformat
MARC
| LEADER | 00000nam a2200000 c 4500 | ||
|---|---|---|---|
| 001 | BV013546880 | ||
| 003 | DE-604 | ||
| 005 | 20070615 | ||
| 007 | t| | ||
| 008 | 010116s2001 gw a||| |||| 00||| eng d | ||
| 016 | 7 | |a 960456112 |2 DE-101 | |
| 020 | |a 3528157291 |9 3-528-15729-1 | ||
| 035 | |a (OCoLC)248435647 | ||
| 035 | |a (DE-599)BVBBV013546880 | ||
| 040 | |a DE-604 |b ger |e rakddb | ||
| 041 | 0 | |a eng | |
| 044 | |a gw |c DE | ||
| 049 | |a DE-91G | ||
| 084 | |a ST 510 |0 (DE-625)143676: |2 rvk | ||
| 084 | |a DAT 307f |2 stub | ||
| 100 | 1 | |a Angeli, Axel |d 1961- |e Verfasser |0 (DE-588)122589270 |4 aut | |
| 245 | 1 | 0 | |a The SAP R/3 guide to EDI and interfaces |b cut your implementation cost with IDocs, ALE and RFC |c Axel Angeli ; Ulrich Streit ; Robi Gonfalonieri |
| 250 | |a 2., rev. ed. | ||
| 264 | 1 | |a Braunschweig ; Wiesbaden |b Vieweg |c 2001 | |
| 300 | |a XIX, 148 S. |b Ill. : 24 cm | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 490 | 0 | |a Vieweg Business Computing | |
| 500 | |a Online-Service zum Buch unter der Adresse http://idocs.de und http://logosworld.com verfügbar | ||
| 650 | 4 | |a Elektronischer Datenaustausch - SAP R/3 | |
| 650 | 0 | 7 | |a SAP R/3 |0 (DE-588)4343439-3 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Elektronischer Datenaustausch |0 (DE-588)4227290-7 |2 gnd |9 rswk-swf |
| 689 | 0 | 0 | |a Elektronischer Datenaustausch |0 (DE-588)4227290-7 |D s |
| 689 | 0 | 1 | |a SAP R/3 |0 (DE-588)4343439-3 |D s |
| 689 | 0 | |5 DE-604 | |
| 700 | 1 | |a Streit, Ulrich |e Verfasser |4 aut | |
| 700 | 1 | |a Gonfalonieri, Robi |d 1964- |e Verfasser |0 (DE-588)122589289 |4 aut | |
| 856 | 4 | 2 | |m HBZ Datenaustausch |q application/pdf |u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=009250618&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |3 Inhaltsverzeichnis |
| 943 | 1 | |a oai:aleph.bib-bvb.de:BVB01-009250618 | |
Datensatz im Suchindex
| DE-BY-TUM_call_number | 0102 DAT 307f 2001 A 5577 |
|---|---|
| DE-BY-TUM_katkey | 1200544 |
| DE-BY-TUM_location | 01 |
| DE-BY-TUM_media_number | 040020261732 |
| _version_ | 1821931682516697088 |
| adam_text | Titel: The SAP R/3 guide to EDI and interfaces
Autor: Angeli, Axel
Jahr: 2001
Table of Contents
Where
1.1
1.2
1.3
1.4
1.5
1.6
What Are SAP RI3 IDocs?
2.1 What Are IDocs?........................................................
2.2 Exploring a Typical Scenario...................................
Get a Feeling for IDocs
3.1 Get A Feeling For IDocs............................................
3.2 The IDoc Control Record..........................................
3.3 The IDoc Data.............................................................
3.4 Interpreting An IDoc Segment Info..........................
3.5 IDoc Base - Database Tables Used to Store IDocs
Exercise: Setting Up IDocs
4.1 Quickly Setting up an Example....................................................................................19
4.2 Example: The IDoc Type matmasoi.............................................................................20
4.3 Example: The IDoc Type ordersoi.............................................................................21
Samp/e Process/ng Routines
5.1 Sample Processing Routines.......................................................................................23
5.2 Sample Outbound Routines........................................................................................24
5.3 Sample Inbound Routines............................................................................................26
/Docs Terminology And Basic Tools
6.1 Basic Terms...................................................................................................................29
6.2 Terminology...................................................................................................................30
IDocs Customizing
7.1 Basic Customizing Settings.........................................................................................34
7.2 Creating An IDoc Segment WE31.................................................................................36
7.3 Defining The Message Type (edmsg)...........................................................................39
7.4 Define Valid Combination Of Message and IDoc Types............................................40
7.5 Assigning a processing function (Table edxfct)....................................................41
7.6 Processing Codes.........................................................................................................42
7.7 Inbound Processing Code............................................................................................44
IDoc Outbound Triggers
8.1 Individual ABAP.............................................................................................................48
8.2 NAST Messages Based Outbound IDocs.......................................................................49
8.3 The RSNAST00 ABAP...................................................................................................50
8.4 Sending IDocs Via RSNASTED....................................................................................51
8.5 Sending IDocs Via RSNAST00.....................................................................................52
8.6 Workflow Based Outbound IDocs...............................................................................53
8.7 Workflow Event From Change Document................................................................. .54
8.8 ALE Change Pointers....................................................................................................55
8.9 Activation of change pointer update...........................................................................56
8.10 Dispatching ALE IDocs for Change Pointers.............................................................57
IDoc Recipes
9.1 How the IDoc Engine Works.....................................
9.2 How SAP Standard Processes Inbound IDocs.......
9.3 How To Create the IDoc Data...................................
9.4 Interface Structure of IDoc Processing Functions
http://idocs.de http://logosworld.com
Has the Money Gone?
Communication..............................................
Psychology of Communication.....................
Phantom SAP Standards and a Calculation
Strategy...........................................................
Who Is On Duty?.............................................
Marcus T. Cicero.............................................
9.5 Recipe To Develop An Outbound IDoc Function.......................................................65
9.6 Converting Data Into IDoc Segment Format...............................................................66
Partner Profiles and Ports
10.1 IDoc Type and Message Type......................................................................................68
10.2 Partner Profiles..............................................................................................................69
10.3 Defining the partner profile ( WE20)............................................................................70
10.4 Data Ports ( WE21)........................................................................................................71
Workflow Technology
11.1 Workflow in R/3 and Its Use For Development...........................................................73
11.2 Event Coupling (Event Linkage)..................................................................................74
11.3 Workflow from Change Documents............................................................................75
11.4 Trigger a Workflow from Messaging...........................................................................76
11.5 Example, How To Create A Sample Workflow Handler.............................................77
11.6 Troubleshooting Workflow Events..............................................................................78
11.7 Send A SAP Mail From A Workflow Event..................................................................79
Calling R/3 Via OLE/JavaScript
12.1 R/3 RFC from MS Office Via Visual Basic...................................................................82
12.2 Call Transaction From Visual Basic for WORD 97.....................................................83
12.3 R/3 RFC from JavaScript..............................................................................................85
12.4 R/3 RFC from Visual Basic Script................................................................................88
12.5 R/3 RFC/OLE Troubleshooting.....................................................................................91
ALE • Application Link Enabling
13.1 A Distribution Scenario Based On IDocs....................................................................93
13.2 Example ALE Distribution Scenario............................................................................93
13.3 How ALE Works.............................................................................................................95
13.4 Useful ALE Transaction Codes....................................................................................97
13.5 ALE Customizing sale.................................................................................................98
13.6 Basic Settings sale......................................................................................................99
13.7 Define The Distribution Model (The Scenario ) BD64...........................................101
13.8 Generating Partner Profiles WE20.............................................................................103
13.9 Creating IDocs and ALE Interface From BAPI SDBG................................................108
13.10 Defining Filter Rules...................................................................................................113
Batch Input Recording
14.1 Recording a Transaction With shdb..........................................................................117
14.2 How to Use the Recorder Efficiently.........................................................................120
14.3 Include 2ZBDCRECXX to Replace BDCRECXX........................................................121
14.4 Generate a Function from Recording........................................................................123
EDI and International Standards
15.1 EDI and International Standards................................................................................129
15.2 Characteristics of the Standards...............................................................................130
15.3 XML...............................................................................................................................131
15.4 ANSI X.12......................................................................................................................133
EDI Converter
16.1 Converter......................................................................................................................135
16.2 A Converter from Germany........................................................................................136
Appendix
17.1 Overview of Relevant Transactions..........................................................................138
17.2 Useful Routines for IDoc Handling............................................................................139
17.3 ALE Master Data Distribution.....................................................................................140
17.4 Monitoring IDocs.........................................................................................................141
17.5 WWW Links..................................................................................................................142
17.6 Questionnaire for Starting an IDoc Project..............................................................143
Index
xi
http://idocs.de http://logosworld.com
Summary
Where Has the Money Gone?
1.1 Communication..................................................................................................
More than 80% of the time of an EDI project is lost in waiting for answers, trying to
understand proposals and retrieving data nobody actually needs.
1.2 Psychology of Communication.........................................................................
Bringing developers together accelerates every project. Especially when both
parties are so much dependent on each other as in an EDI project, the partners
need to communicate without pause.
1.3 Phantom SAP Standards and a Calculation....................................................
SAP RI3 delivers a serious of predefined EDI programs. Many project
administrators see them as standards which should not be manipulated or modified.
The truth is, that these IDoc processing functions are recommendations and
example routines, which can be replaced be own routines in customizing.
1.4 Strategy............................................................................................................................5
Do not loose your time in p/ans. Have prototypes developed and take them as a
basis.
1.5 Who Is On Duty?..............................................................................................................5
Writing interface programs is much like translating languages. The same rule apply.
1.6 Marcus T. Cicero..............................................................................................................6
Some may have learned it in school: the basic rules of rhetoric according to Cicero.
You will know the answers, when your program is at its end. Why don t you ask the
questions in the beginning? Ask the right question, then you will know.
What Are SAP RI3 IDocs?
2.1 What Are IDocs?..............................................................................................................8
IDocs are structured ASCII files (or a virtual equivalent). They are the file format
used by SAP R/3 to exchange data with foreign systems.
2.2 Exploring a Typical Scenario.........................................................................................9
The IDoc process is a straight forward communication scenario. A communication is
requested, then data is retrieved, wrapped and sent to the destination in a
predefined format and envelope.
Get a Feeling for IDocs
3.1 Get A Feeling For IDocs................................................................................................12
For the beginning we want to give you a feeling of what IDocs are and how they
may look like, when you receive it as a plain text file.
3.2 The IDoc Control Record................................................................................................ 4
The very first record of an IDoc package is always a control record. The structure of
this control record is the DDic structure BDIDC and describes the contents of the
data contained in the package.
3.3 The IDoc Data.....................................................................................................
All records in the IDoc, which come after the control record are the IDoc data. They
are all structured alike, with a segment information part and a data part which is
1000 characters in length, filling the rest of the line.
3.4 Interpreting An IDoc Segment Info...................................................................
All IDoc data records are exchanged in a fixed format, regardless of the segment
type. The segment s true structure is stored in R/3 s repository as a DDic structure
of the same name.
http://idocs.de http://logosworld.com
3.5 IDoc Base - Database Tables Used to Store IDocs....................................................17
When RI3 processes an IDoc via the standard inbound or outbound mechanism, the
IDoc is stored in the tables. The control record goes to table edidc and the data
goes to table edid4.
Exercise: Setting Up IDocs
4.1 Quickly Setting up an Example....................................................................................19
If you have a naked system, you cannot send IDocs immediately. This chapter will
guide you through the minimum steps to see how the IDoc engine works.
4.2 Example: The IDoc Type matmasoi............................................................................20
To sharpen your understanding, we will show you an example of an IDoc of type
MATMAS01, which contains material master data.
4.3 Example: The IDoc Type ordersoI............................................................................21
To allow an interference, here is a sample of IDoc type ORDERSOI which is used for
purchase ordersand sales orders.
Sample Processing Routines
5.1 Sample Processing Routines.......................................................................................23
Creating and processing IDocs are a widely mechanical task, as it is true for all
interface programming. We will show a short example that packs SAP RI3
SAPscript standard text elements into IDocs and stores them back.
5.2 Sample Outbound Routines........................................................................................24
The most difficult work when creating outbound IDocs is the retrieval of the
application data which needs sending. Once the data is well retrieved, the data
needs to be converted to IDoc format, only.
5.3 Sample Inbound Routines............................................................................................26
Inbound processing is widely the reverse process of an outbound.. The received
IDoc has to be unpacked, interpreted and transferred to an application for further
processing.
IDocs Terminology And Basic Tools
6.1 Basic Terms...................................................................................................................29
There are a couple of expressions and methods that you need to know, when
dealing with IDoc.
6.2 Terminology...................................................................................................................30
6.2.1 Message Type - How to Know What the Data Means
Data exchanged by an IDoc via EDI is known as message. Messages of the same
kind belong to the same message type.
6.2.2 Partner Profiles - How to Know the Format of the Partner
Different partners may speak different languages. While the information remains the
same, different receivers may require completely different file formats and
communication protocols. This information is stored in a partner profile.
6.2.3 IDoc Type - The Structure of The IDoc File
The IDoc type is the name of the data structure used to describe the file format of a
specific IDoc.
6.2.4 Processing Codes
The processing code is a pointer to an algorithm to process an IDoc. It is used to
allow more flexibility in assigning the processing function to an IDoc message.
IDocs Customizing
7.1 Basic Customizing Settings.........................................................................................34
Segments define the structure of the records in an IDoc. They are defined with
transaction WE31.
xiii
http://idocs.de http://logosvvorld.com
7.2 Creating An IDoc Segment .........................................................................
The segment defines the structure of the records in an IDoc. They are defined with
transaction WE31. We will define a structure to send a text from the text database.
7.3 Defining The Message Type (edmsg)................................................................
The message type defines the context under which an IDoc is transferred to its
destination. It allows to use the same IDoc file format to use for several different
applications.
7.4 Define Valid Combination Of Message and IDoc Types.................................
The valid combinations of message type and IDoc type are stored in table EDIMSG.
7.5 Assigning a processing function (Table edifct).........................................
The combination of message type and IDoc type determine the processing
algorithm. This is usually a function module with a well defined interface or a SAP
business object and is set up in table EDIFCT.
7.6 Processing Codes..............................................................................................
R/3 uses the method of logical process codes to detach the IDoc processing and
the processing function module. They assign a logical name to function instead of
specifying the physical function name.
7.7 Inbound Processing Code.................................................................................
The inbound processing code is assigned analogously. The processing code is a
pointer to a function module which can handle the inbound request for the specified
IDoc and message type.
IDoc Outbound Triggers
8.1 Individual ABAP..................................................................................................
The simplest way to create IDocs, is to write an ABAP. The individual ABAP can
either be a triggering ABAP which runs at certain events, e.g. every night, or it can
be an ABAP which does the complete IDoc creation from scratch.
8.2 NAST Messages Based Outbound IDocs.........................................................
You can use the R/3 message concept to trigger IDocs the same way as you trigger
SAPscript printing.
8.3 The RSNASTOO ABAP.........................................................................................
The ABAP RSNASTOO is the standard ABAP, which is used to collect unprocessed
NAST message and to execute the assigned action.
8.4 Sending IDocs Via RSNASTED.........................................................................
Standard R/3 provides you with powerful rout/nes, to trigger, prepare and send out
IDocs in a controlled way. There are only a few rare cases, where you do not want
to send IDocs the standard way.
8.5 Sending IDocs Via RSNASTOO..........................................................................
Here is the principle flow how RSNASTOO processes messages for IDocs.
8.6 Workflow Based Outbound IDocs.....................................................................
Unfortunately, there are application that do not create messages. This is especially
true for master data applications. However, most applications fire a workflow event
during update, which can easily be used to trigger the IDoc distribution.
8.7 Workflow Event From Change Document........................................................
Instead of waiting for a polling job to create IDocs, they can also be created...............
immediately after a transaction finishes. This can be done by assigning an action to
an workflow event.
8.8 ALE Change Pointers...............................................................
Applications which write change documents will also try towrite cha^
ALE operations. These are log entries to remember all modified data records
relevant for ALE.
.36
.39
.40
.41
.42
.44
.48
.49
.50
.51
.52
,53
.54
55
http://idocs.de http://logosworld.com
xiv
8.9 Activation of change pointer update...........................................................................56
Change pointers are log entries to table BDCP which are written every time a
transaction modifies certain fields. The change pointers are designed for ALE
distribution and written by the function CHANGE_DOCUMENT_CLOSE.
8.10 Dispatching ALE IDocs for Change Pointers.............................................................57
Change pointers must be processed by an ABAP, e.g. RBDMIDOC.
IDoc Recipes
9.1 How the IDoc Engine Works.........................................................................................60
IDocs are usually created in a four step process. These steps are: retrieving the
data, converting them to IDoc format, add a control record and delivering the IDoc to
a port.
9.2 How SAP Standard Processes Inbound IDocs...........................................................61
When you receive an IDoc the standard way, the data is stored in the IDoc base
and a function module is called, which decides how to process the received
information.
9.3 How To Create the IDoc Data.......................................................................................62
R/3 provides a sophisticated IDoc processing framework. This framework
determines a function module, which is responsible for creating or processing the
IDoc.
9.4 Interface Structure of IDoc Processing Functions....................................................64
To use the standard IDoc processing mechanism the processing function module
must have certain interface parameters, because the function is called dynamically
from a standard routine.
9.5 Recipe To Develop An Outbound IDoc Function.......................................................65
This is an individual coding part where you need to retrieve the information from the
database and prepare it in the form the recipient of the IDoc will expect the data
9.6 Converting Data Into IDoc Segment Format...............................................................66
The physical format of the IDocs records is always the same. Therefore the
application data must be converted into a 1000 character string.
Partner Profiles and Ports
10.1 IDoc Type and Message Type......................................................................................68
An IDoc file requires a minimum of accompanying information to give sense to it.
These are the message type and the IDoc type. While the IDoc type tells you about
the fields and segments of the IDoc file, the message type flags the context under
which the IDoc was sent.
10.2 Partner Profiles..............................................................................................................69
Partner profiles play an important role in EDI communications. They are parameter
files which store the EDI partner dependent information.
10.3 Defining the partner profile ( WE20)............................................................................70
The transaction WE20 is used to set up the partner profile.
10.4 Data Ports ( WE2X )........................................................................................................71
IDoc data can be sent and received through a multitude of different media. In order
to decouple the definition of the media characteristics from the application using it,
the media is accessed via ports.
Workflow Technology
11.1 Workflow in R/3 and Its Use For Development...........................................................73
SAP R/3 provides a mechanism, called Workflow, that allows conditional and
unconditional triggering of subsequent transactions from another transaction. This
allows to build up automatic processing sequences without having the need to
modify the SAP standard transactions.
http://idocs.de http://logosworld.com
11.2 Event Coupling (Event Linkage).......................................................................
Contrary to what you mostly hear about R/3 workflow, it is relatively easy and
mechanical to define a function module as a consecutive action after another
routine raised a workflow event. This can e.g. be used to call the execution of a
transaction after another one has finished.
11.3 Workflow from Change Documents..................................................................
Every time a change document is written a workflow event for the change document
object is triggered. This can be used to chain unconditionally an action from a
transaction.
11.4 Trigger a Workflow from Messaging...............................................................
The third common way to trigger a workflow is doing it from messaging.
11.5 Example, How To Create A Sample Workflow Handler...................................
Let us show you a function module which is suitable to serve as a function module
and define the linkage.
11.6 Troubleshooting Workflow Events....................................................................
11.7 Send A SAP Mail From A Workflow Event.......................................................
This is an example coding to demonstrate how you can send a SAP mail triggered
by a workflow event.
Calling R13 Via OLEIJavaScript
12.1 R/3 RFC from MS Office Via Visual Basic.........................................................
The Microsoft Office suite incorporates with Visual Basic for Applications (VBA) a
fully object oriented language. JavaScript and JAVA are naturally object oriented.
Therefore you can easily connect from JavaScript, JA VA, WORD, EXCEL and all
the other VBA compliant software to R/3 via the CORBA compatible object library
(in WINDOWS known also DLLs or ACTIVEX (=OLE/2) components).
12.2 Call Transaction From Visual Basic for WORD 97...........................................
This is a little WORD 97 macro, that demonstrates how R/3 can be called with a
mouse click directly from within WORD 97.
12.3 R/3 RFC from JavaScript....................................................................................
JavaScript is a fully object oriented language. Therefore you can easily connect
from JavaScript to R/3 via the CORBA compatible object library (in WINDOWS
known also DLLs orACTIVE-X (-OLEI2) components).
12.4 R/3 RFC from Visual Basic Script......................................................................
Visual Basic Script also known as Windows Scripting Host is the scripting tool which
is delivered with any Windows installation. See here an extensive example to read
any table from R/3.
12.5 R/3 RFC/OLE Troubleshooting...........................................................................
Problems connecting via RFC can usually be solved by reinstalling the full SAPGUl
andlor checking your network connection with R/3.
ALE - Application Link Enabling
13.1 A Distribution Scenario Based On IDocs..........................................................
ALE has become very famous in business circles. While it sounds mysterious and
like a genial solution, it is simply a mean to automate data exchange between SAP
systems. It is mainly meant to distribute data from one SAP system to the next. ALE
is a mere enhancement of SAP-EDI and SAP-RFC technology.
13.2 Example ALE Distribution Scenario..................................................................
To better understand let us model a small example ALE scenario for distribution of
master data between several offices.
13.3 How ALE Works.................................................................................................
ALE is a simple add-on application propped upon the IDoc concept of SAP R/3. It
consists of a couple of predefined ABAPs which rely on a customised distribution
scenario. These scenarios simply define the IDoc types and the relationship and
technical details of the partners which exchange data.
http://idocs.de http://logosworld.com
.74
.75
.76
.77
.78
.79
.82
.83
.85
.88
.91
.93
93
95
13.4 Useful ALE Transaction Codes....................................................................................97
ALE is customized via three main transaction. These are SALE, wedi and bale.
13.5 ALE Customizing sals.................................................................................................98
ALE customizing is relatively straight forward. The only mandatory task is the
definition of the ALE distribution scenario.
13.6 Basic Settings sale......................................................................................................99
Basic settings have do be adjusted before you can start working with ALE.
13.7 Define The Distribution Model (The Scenario ) BD64...........................................101
The distribution model (also referred to as ALE-Scenario) is a more or less graphical
approach to define the relationship between the participating senders and receivers.
13.8 Generating Partner Profiles WE20.............................................................................103
A very useful utility is the automatic generation of partner profiles out of the ALE
scenario. Even if you do not use ALE in your installation, it could be only helpful to
define the EDI partners as ALE scenario partners and generate the partner profiles.
13.9 Creating IDocs and ALE Interface From BAPI sdbo................................................108
There is a very powerful utility which allows to generate most IDoc and ALE
interface objects directly from a BAPI s method interface.
13.10 Defining Filter Rules...................................................................................................113
ALE allows to define simple filter and transformation rules. These are table entries,
which are processed every time the IDoc is handed over to the port. Depending on
the assigned path this happens either on inbound or outbound.
Batch Input Recording
14.1 Recording a Transaction With shdb..........................................................................117
The BTCI recorder lets you record the screen sequences and values entered during
a transaction. It is one of the most precious tools in R/3 since release 3.1. It allows a
fruitful cooperation between programmer and application consultant.
14.2 How to Use the Recorder Efficiently.........................................................................120
This routine replaces BDCRECXX to allow executing the program generated by
SHDB via a call transaction instead of generating a BTCI file.
14.3 Include ZZBDCRECXX to Replace BDCRECXX........................................................121
This routine replaces BDCRECXX to allow executing the program generated by
shdb via a call transaction instead of generating a BTCI file.
14.4 Generate a Function from Recording........................................................................123
The section shows the coding of routine ZZBDCRECXX_FB_GEN. This goodie can
replaces BDCRECXX in a recorded ABAP. Upon executing, it will generate a
function module from the recording with all variables as parameters.
EDI and International Standards
15.1 EDI and International Standards................................................................................129
Electronic Data Interchange (EDI) as a tool for paperless inter-company
communication and basic instrument for e-commerce is heavily regulated by several
international standards.
15.2 Characteristics of the Standards...............................................................................130
The well-known standards EDIFACT, X. 12 and XML have similar characteristics
and are designed like a document description language. Other standards and R/3
IDocs are based on segmented files.
15.3 XML...............................................................................................................................131
This is an excerpt of an XML EDI message. The difference to all other EDI
standards is, that the message information is tagged in a way, that it can be
displayed in human readable form by a browser.
xvii
http://idocs.de http://logosworld.com
.135
133
15.4 ANSI X.12...........................................................................;........T T Tri...............
This is an example of how an ANSI X. 12 EDI message for a sales order looks like.
The examples do not show the control record (the envelope ). EDIFACT looks very
much the same.
EDI Converter
16.1 Converter...................................................................................................
SAP RI3 has foregone to implement routines to convert IDocs into international tul
standard formats and forwards those requests to the numerous third party
companies who specialize in commercial EDI and e-commerce solutions..
16.2 A Converter from Germany........................................................................................136
In the forest of EDI converters there is only a very limited number of companies who
have actual experience with R/3. We have chosen one very popular product for
demonstration here.
Appendix
17.1 Overview of Relevant Transactions...........................................................................138
There is a couple of transactions which you should know when working with IDocs
in any form. I suggest to call each transaction at least once to see, what is really
behind.
17.2 Useful Routines for IDoc Handling............................................................................139
These are some very useful routines, that can be used in IDoc processing.
17.3 ALE Master Data Distribution.....................................................................................140
The ALE functionality comes with a set of transaction which allow the distribution of
important master data between systems. The busiest argument for installing ALE
might be the distribution of the classification from development to production and
back.
17.4 Monitoring IDocs.........................................................................................................141
There are some utilities in R/3 that help monitoring all the IDocs in the system. They
allow viewing them, analysing eventual cause of error and retrying IDoc processing
in case of failure.
17.5 WWW Links..................................................................................................................142
These is a random listing of interesting web sites dealing with the EDI topic. They
are accurate as of November 1999.
17.6 Questionnaire for Starting an IDoc Project...............................................................143
This is a sample questionnaire with important questions that need to be cleared
before any development can be started.
Index
http://idocs.de http://logosworld.com
xviii
|
| any_adam_object | 1 |
| author | Angeli, Axel 1961- Streit, Ulrich Gonfalonieri, Robi 1964- |
| author_GND | (DE-588)122589270 (DE-588)122589289 |
| author_facet | Angeli, Axel 1961- Streit, Ulrich Gonfalonieri, Robi 1964- |
| author_role | aut aut aut |
| author_sort | Angeli, Axel 1961- |
| author_variant | a a aa u s us r g rg |
| building | Verbundindex |
| bvnumber | BV013546880 |
| classification_rvk | ST 510 |
| classification_tum | DAT 307f |
| ctrlnum | (OCoLC)248435647 (DE-599)BVBBV013546880 |
| discipline | Informatik |
| edition | 2., rev. ed. |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01849nam a2200445 c 4500</leader><controlfield tag="001">BV013546880</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20070615 </controlfield><controlfield tag="007">t|</controlfield><controlfield tag="008">010116s2001 gw a||| |||| 00||| eng d</controlfield><datafield tag="016" ind1="7" ind2=" "><subfield code="a">960456112</subfield><subfield code="2">DE-101</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">3528157291</subfield><subfield code="9">3-528-15729-1</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)248435647</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV013546880</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield><subfield code="e">rakddb</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="044" ind1=" " ind2=" "><subfield code="a">gw</subfield><subfield code="c">DE</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-91G</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 510</subfield><subfield code="0">(DE-625)143676:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">DAT 307f</subfield><subfield code="2">stub</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Angeli, Axel</subfield><subfield code="d">1961-</subfield><subfield code="e">Verfasser</subfield><subfield code="0">(DE-588)122589270</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">The SAP R/3 guide to EDI and interfaces</subfield><subfield code="b">cut your implementation cost with IDocs, ALE and RFC</subfield><subfield code="c">Axel Angeli ; Ulrich Streit ; Robi Gonfalonieri</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">2., rev. ed.</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Braunschweig ; Wiesbaden</subfield><subfield code="b">Vieweg</subfield><subfield code="c">2001</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XIX, 148 S.</subfield><subfield code="b">Ill. : 24 cm</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="490" ind1="0" ind2=" "><subfield code="a">Vieweg Business Computing</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Online-Service zum Buch unter der Adresse http://idocs.de und http://logosworld.com verfügbar</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Elektronischer Datenaustausch - SAP R/3</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">SAP R/3</subfield><subfield code="0">(DE-588)4343439-3</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Elektronischer Datenaustausch</subfield><subfield code="0">(DE-588)4227290-7</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Elektronischer Datenaustausch</subfield><subfield code="0">(DE-588)4227290-7</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">SAP R/3</subfield><subfield code="0">(DE-588)4343439-3</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Streit, Ulrich</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Gonfalonieri, Robi</subfield><subfield code="d">1964-</subfield><subfield code="e">Verfasser</subfield><subfield code="0">(DE-588)122589289</subfield><subfield code="4">aut</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="m">HBZ Datenaustausch</subfield><subfield code="q">application/pdf</subfield><subfield code="u">http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=009250618&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA</subfield><subfield code="3">Inhaltsverzeichnis</subfield></datafield><datafield tag="943" ind1="1" ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-009250618</subfield></datafield></record></collection> |
| id | DE-604.BV013546880 |
| illustrated | Illustrated |
| indexdate | 2024-12-20T10:49:13Z |
| institution | BVB |
| isbn | 3528157291 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-009250618 |
| oclc_num | 248435647 |
| open_access_boolean | |
| owner | DE-91G DE-BY-TUM |
| owner_facet | DE-91G DE-BY-TUM |
| physical | XIX, 148 S. Ill. : 24 cm |
| publishDate | 2001 |
| publishDateSearch | 2001 |
| publishDateSort | 2001 |
| publisher | Vieweg |
| record_format | marc |
| series2 | Vieweg Business Computing |
| spellingShingle | Angeli, Axel 1961- Streit, Ulrich Gonfalonieri, Robi 1964- The SAP R/3 guide to EDI and interfaces cut your implementation cost with IDocs, ALE and RFC Elektronischer Datenaustausch - SAP R/3 SAP R/3 (DE-588)4343439-3 gnd Elektronischer Datenaustausch (DE-588)4227290-7 gnd |
| subject_GND | (DE-588)4343439-3 (DE-588)4227290-7 |
| title | The SAP R/3 guide to EDI and interfaces cut your implementation cost with IDocs, ALE and RFC |
| title_auth | The SAP R/3 guide to EDI and interfaces cut your implementation cost with IDocs, ALE and RFC |
| title_exact_search | The SAP R/3 guide to EDI and interfaces cut your implementation cost with IDocs, ALE and RFC |
| title_full | The SAP R/3 guide to EDI and interfaces cut your implementation cost with IDocs, ALE and RFC Axel Angeli ; Ulrich Streit ; Robi Gonfalonieri |
| title_fullStr | The SAP R/3 guide to EDI and interfaces cut your implementation cost with IDocs, ALE and RFC Axel Angeli ; Ulrich Streit ; Robi Gonfalonieri |
| title_full_unstemmed | The SAP R/3 guide to EDI and interfaces cut your implementation cost with IDocs, ALE and RFC Axel Angeli ; Ulrich Streit ; Robi Gonfalonieri |
| title_short | The SAP R/3 guide to EDI and interfaces |
| title_sort | the sap r 3 guide to edi and interfaces cut your implementation cost with idocs ale and rfc |
| title_sub | cut your implementation cost with IDocs, ALE and RFC |
| topic | Elektronischer Datenaustausch - SAP R/3 SAP R/3 (DE-588)4343439-3 gnd Elektronischer Datenaustausch (DE-588)4227290-7 gnd |
| topic_facet | Elektronischer Datenaustausch - SAP R/3 SAP R/3 Elektronischer Datenaustausch |
| url | http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=009250618&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
| work_keys_str_mv | AT angeliaxel thesapr3guidetoediandinterfacescutyourimplementationcostwithidocsaleandrfc AT streitulrich thesapr3guidetoediandinterfacescutyourimplementationcostwithidocsaleandrfc AT gonfalonierirobi thesapr3guidetoediandinterfacescutyourimplementationcostwithidocsaleandrfc |
Inhaltsverzeichnis
Paper/Kapitel scannen lassen
Paper/Kapitel scannen lassen
Teilbibliothek Mathematik & Informatik
| Signatur: |
0102 DAT 307f 2001 A 5577 Lageplan |
|---|---|
| Exemplar 1 | Ausleihbar Am Standort |