The SAP R-3 guide to EDI and interfaces: cut your implementation cost with Idocs, ALE and SapScript
Gespeichert in:
| Hauptverfasser: | , , |
|---|---|
| Format: | Buch |
| Sprache: | English |
| Veröffentlicht: |
Braunschweig ; Wiesbaden
Vieweg [u.a.]
2000
|
| Schriftenreihe: | Business computing
|
| Schlagworte: | |
| Online-Zugang: | Inhaltsverzeichnis |
| Beschreibung: | Auf der Titelseite Name des 1. Verfassers irrtümlich Axeö statt Axel |
| Beschreibung: | XXI, 157 S. Ill., graph. Darst. |
| ISBN: | 3528057297 |
Internformat
MARC
| LEADER | 00000nam a22000008c 4500 | ||
|---|---|---|---|
| 001 | BV013061442 | ||
| 003 | DE-604 | ||
| 005 | 20040225 | ||
| 007 | t | ||
| 008 | 000229s2000 gw ad|| |||| 00||| eng d | ||
| 016 | 7 | |a 958466718 |2 DE-101 | |
| 020 | |a 3528057297 |c Gb. : DM 98.00 |9 3-528-05729-7 | ||
| 035 | |a (OCoLC)44884374 | ||
| 035 | |a (DE-599)BVBBV013061442 | ||
| 040 | |a DE-604 |b ger |e rakddb | ||
| 041 | 0 | |a eng | |
| 044 | |a gw |c DE | ||
| 049 | |a DE-473 |a DE-523 | ||
| 050 | 0 | |a HF5548.4.R2 | |
| 084 | |a ST 510 |0 (DE-625)143676: |2 rvk | ||
| 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 SapScript |c Axeö Angeli ; Ulrich Streit ; Robi Gonfalonieri |
| 264 | 1 | |a Braunschweig ; Wiesbaden |b Vieweg [u.a.] |c 2000 | |
| 300 | |a XXI, 157 S. |b Ill., graph. Darst. | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 490 | 0 | |a Business computing | |
| 500 | |a Auf der Titelseite Name des 1. Verfassers irrtümlich Axeö statt Axel | ||
| 630 | 0 | 4 | |a SAP R/3 |
| 650 | 4 | |a Wirtschaft | |
| 650 | 4 | |a Business |x Computer programs | |
| 650 | 4 | |a Electronic data interchange | |
| 650 | 0 | 7 | |a Schnittstelle |0 (DE-588)4053059-0 |2 gnd |9 rswk-swf |
| 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 SAP R/3 |0 (DE-588)4343439-3 |D s |
| 689 | 0 | 1 | |a Elektronischer Datenaustausch |0 (DE-588)4227290-7 |D s |
| 689 | 0 | 2 | |a Schnittstelle |0 (DE-588)4053059-0 |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 DNB Datenaustausch |q application/pdf |u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=008900165&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |3 Inhaltsverzeichnis |
| 943 | 1 | |a oai:aleph.bib-bvb.de:BVB01-008900165 | |
Datensatz im Suchindex
| _version_ | 1807683370148167680 |
|---|---|
| adam_text |
TABLE
OF
CONTENTS
WHERE
HAS
THE
MONEY
GONE?
1
1.1
COMMUNICATION
.
2
MORE
THAN
80%
OF
THE
TIME
OF
AN
ED!
PROJECT
IS
LOST
IN
WAITING
FOR
ANSWERS,
TRYING
TO
UNDERSTAND
PROPOSALS
AND
RETRIEVING
DATA
NOBODY
ACTUALLY
NEEDS.
2
1.2
PSYCHOLOGY
OF
COMMUNICATION
.
3
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.
3
1.3
PHANTOM
SAP
STANDARDS
AND
A
CALCULATION
.
4
IT
IS
REPORTED
THAT
SAP
R/3
DELIVERS
STANDARD
EDI
PROGRAMS
AND
THAT
THEY
SHOULD
NOT
BE
MANIPULATED
UNDER
NO
CIRCUMSTANCES.
BECAUSE
THIS
IS
NOT
TRUE,
MUCH
PROJECT
IS
LOST
IN
CHASING
THE
PHANTOM.
4
1.4
STRATEGY
.
5
DO
NOT
LOOSE
YOUR
TIME
IN
PLANS.
HAVE
PROTOTYPES
DEVELOPED
AND
TAKE
THEM
AS
A
BASIS.
5
1.5
WHO
IS
ON
DUTY?
.
5
WRITING
INTERFACE
PROGRAMS
IS
MUCH
LIKE
TRANSLATING
LANGUAGES.
THE
SAME
RULE
APPLY.
5
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'TYOU
ASK
THE
QUESTIONS
IN
THE
BEGINNING?
ASK
THE
RIGHT
QUESTION,
THEN
YOU
WILL
KNOW.
6
WHAT
ARE
SAP
R/3
IDOCS
?
7
2.1
WHAT
ARE
IDOCS?
.
8
IDOCS
ARE
STRUCTURED
ASCH
FILES
(OR
A
VIRTUAL
EQUIVALENT).
THEY
ARE
THE
FILE
FORMAT
USED
BY
SAP
R/3
TO
EXCHANGE
DATA
WITH
FOREIGN
SYSTEMS.
8
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.
9
GET
A
FEELING
FOR
/DOES
11
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
TOOK
LIKE,
WHEN
YOU
RECEIVE
IT
AS
A
PLAIN
TEXT
FILE.
12
3.2
THE
IDOC
CONTROL
RECORD
.
14
STRUCTURE
OF
THIS
CONTROL
RECORD
IS
THE
DDIC
STRUCTURE
\EDID()
AND
DESCRIBES
THE
CONTENTS
OF
THE
DATA
CONTAINED
IN
THE
PACKAGE.
14
3.3
THE
IDOC
DATA
.
15
AH
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.
15
XII
CONTENTS
3.4
INTERPRETING
AN
IDOC
SEGMENT
INFO
.
16
AH
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.
16
3.5
IDOC
BASE
-
DATABASE
TABLES
USED
TO
STORE
IDOCS
.
17
WHEN
R/3
PROCESSES
AN
IDOC
VIA
THE
STANDARD
INBOUND
OR
OUTBOUND
MECHA
NISM,
THE
IDOC
IS
STORED
IN
T
HE
TABLE
S.
THE
CONTROL
RECORD
GOES
TO
TABLE
\ED!D(\
AND
THE
DATA
GOES
TO
TABLE
\EDID4,
17
EXERCISE:
SETTING
UP
IDOCS
18
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.
19
4.2
EXAMPLE:
THE
IDOC
TYPE
|MATMASOL|
.
20
TO
SH
ARPEN
YOU
R
UNDERSTANDING,
WE
WILL
SHOW
YOU
AN
EXAMPLE
OF
AN
IDOC
OF
TYPE
\MATMAS0L,
WHICH
CONTAINS
MATERIAL
MASTER
DATA.
20
4.3
EXAMPLE:
THE
IDOC
TYPE
|0RDERS0I|
.
YY
.
21
TO
ALLOW
AN
INTERFERENCE,
HERE
IS
A
SAMPLE
OF
IDOC
TYPE
\0RDERS0L\
WHICH
IS
USED
FOR
PURCHASE
ORDERS
AND
SALES
ORDERS.
21
MONITORING
IDOCS
23
SAMPLE
PROCESSING
ROUTINES
25
6.1
SAMPLE
PROCESSING
ROUTINES
.
26
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
R/3
SAPSCRIPT
STANDARD
TEXT
ELEMENTS
INTO
/DOES
AND
STORES
THEM
BACK.
26
6.2
SAMPLE
OUTBOUND
ROUTINES
.
27
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.
27
6.3
SAMPLE
INBOUND
ROUTINES
.
29
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.
29
IDOCS
TERMINOLOGY
31
7.1
BASIC
TERMS
.
32
THERE
ARE
A
COUPLE
OF
EXPRESSIONS
AND
METHODS
THAT
YOU
NEED
TO
KNOW,
WHEN
DEALING
WITH
IDOC.
32
7.2
TERMINOLOGY
.
33
7.2.1
MESSAGE
TYPE
-
HOW
TO
KNOW
WHAT
THE
DATA
MEANS
33
DATA
EXCHANGED
BY
AN
IDOC
VIA
EDI
IS
KNOWN
AS
MESSAGE.
MESSAGES
OF
THE
SAME
KIND
BELONG
TO
THE
SAME
MESSAGE
TYPE.
33
7.2.2
PARTNER
PROFILES
-
HOW
TO
KNOW
THE
FORMAT
OF
THE
PARTNER
33
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.
33
7.2.3
IDOC
TYPE
-
THE
STRUCTURE
OF
THE
IDOC
FILE
34
XIII
THE
IDOC
TYPE
IS
THE
NAME
OF
THE
DATA
STRUCTURE
USED
TO
DESCRIBE
THE
FILE
FORMAT
OF
A
SPECIFIC
IDOC.
34
7.2.4
PROCESSING
CODES
34
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.
34
/DOCS
CUSTOMIZING
37
8.1
BASIC
CUSTOMIZING
SETTINGS
.
38
SEGMENTS
DEFINE
THE
STRUCTURE
OF
THE
RECORDS
IN
AN
IDOC.
THEY
ARE
DEFINED
WITH
TRANSACTION
WE31.
38
8.2
CREATING
AN
IDOC
SEGMENT
|WE31|
.
40
DEFINED
WITH
TRANSACTION
|VI/E3
7|
.
WE
WILL
DEFINE
A
STRUCTURE
TO
SEND
A
TEXT
FROM
THE
TEXT
DATABASE.
40
8.3
DEFINING
THE
MESSAGE
TYPE
(|EDMSG|)
.
43
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.
43
8.4
DEFINE
VALID
COMBINATION
OF
MESSAGE
AND
IDOC
TYPES
.
44
THE
VALID
COMBINATIONS
OF
MESSAGE
TYPE
AND
IDOC
TYPE
ARE
STORED
IN
TABLE
EDIMSG.
44
8.5
ASSIGNING
A
PROCESSING
FUNCTION
(TABLE
|EDIFC~H
)
.
45
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.
45
8.6
PROCESSING
CODES
.
46
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.
46
8.7
INBOUND
PROCESSING
CODE
.
48
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.
48
IDOC
OUTBOUND
TRIGGERS
51
9.1
INDIVIDUAL
ABAP
.
52
THE
SIMPLEST
WAY
TO
CREATE
IDOCS,
IS
TO
WRITE
AN
ABAP
WHICH
SIMPLY
DOES
IT.
52
9.2
NAST
MESSAGES
BASED
OUTBOUND
IDOCS
.
54
YOU
CAN
USE
THE
R/3
MESSAGE
CONCEPT
TO
TRIGGER
IDOCS
THE
SAME
WAY
AS
YOU
TRIGGER
SAPSCRIPT
PRINTING.
54
9.3
THE
RSNASTOO
ABAP
.
56
THE
ABAP
RSNASTOO
IS
THE
STANDARD
ABAP,
WHICH
IS
USED
TO
COLLECT
UNPROCESSED
NAST
MESSAGE
AND
TO
EXECUTE
THE
ASSIGNED
ACTION.
56
9.4
SENDING
IDOCS
VIA
RSNASTED
.
57
STANDARD
R/3
PROVIDES
YOU
WITH
POWERFUL
ROUTINES,
TO
TRIGGER,
PREPARE
AND
SEND
OUT
/DOES
IN
A
CONTROLLED
WAY.
THERE
ARE
ONLY
A
FEW
RARE
CASES,
WHERE
YOU
DO
NOT
WANT
TO
SEND
IDOCS
THE
STANDARD
WAY.
57
9.5
SENDING
IDOCS
VIA
RSNASTOO
.
58
HERE
IS
THE
PRINCIPLE
FLOW
HOW
RSNASTOO
PROCESSES
MESSAGES
FOR
IDOCS.
58
XIV
CONTENTS
9.6
WORKFLOW
BASED
OUTBOUND
IDOCS
.
59
UNFORTUNATELY,
THERE
ARE
APPLICATION
THAT
DO
NOT
CREATE
MESSAGES.
THIS
IS
ESPECIALLY
TRUE
FORMASTER
DATA
APPLICATIONS.
HOWEVER,
MOST
APPLICATIONS
FIRE
A
WORKFLOW
EVENT
DURING
UPDATE,
WHICH
CAN
EASILY
BE
USED
TO
TRIGGER
THE
IDOC
DISTRIBUTION.
59
9.7
WORKFLOW
EVENT
FROM
CHANGE
DOCUMENT
.
60
INSTEAD
OF
WAITING
FOR
A
POLLINGJOB
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.
60
9.8
ALE
CHANGE
POINTERS
.
61
APPLICATIONS
WHICH
WRITE
CHANGE
DOCUMENTS
WILL
ALSO
TRY
TO
WRITE
CHANGE
POINTERS
FOR
ALE
OPERATIONS.
THESE
ARE
LOG
ENTRIES
TO
REMEMBER
ALL
MODIFIED
DATA
RECORDS
RELEVANT
FOR
ALE.
61
9.9
ACTIVATION
OF
CHANGE
POINTER
UPDATE
.
62
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.
62
9.10
DISPATCHING
ALE
IDOCS
FOR
CHANGE
POINTERS
.
63
CHANGE
POINTERS
MUST
BE
PROCESSED
BY
AN
ABAP,
E.G.
RBDMIDOC.
63
IDOC
RECIPES
65
10.1
HOW
THE
IDOC
ENGINE
WORKS
.
66
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.
66
10.2
HOW
SAP
STANDARD
PROCESSES
INBOUND
IDOCS
.
67
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
RECEIVEDINFORMATION.
67
10.3
HOW
TO
CREATE
THE
IDOC
DATA
.
68
R/3
PROVIDES
A
SOPHISTICATED
IDOC
PROCESSING
FRAMEWORK.
THIS
FRAMEWORK
DETERMINES
A
FUNCTION
MODULE,
WHICH
IS
RESPONSIBLE
FOR
CREATING
OR
PROCESSING
THE
IDOC.
68
10.4
INTERFACE
STRUCTURE
OF
IDOC
PROCESSING
FUNCTIONS
.
70
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.
70
10.5
RECIPE
TO
DEVELOP
AN
OUTBOUND
IDOC
FUNCTION
.
71
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
71
10.6
CONVERTING
DATA
INTO
IDOC
SEGMENT
FORMAT
.
72
THE
PHYSICAL
FORMAT
OF
THE
IDOCS
RECORDS
IS
ALWAYS
THE
SAME.
THEREFORE
THE
APPLICATION
DATA
MUST
BE
CONVERTED
INTO
A
1000
CHARACTER
STRING.
72
PARTNER
PROFILES
AND
PORTS
73
11.1
IDOC
TYPE
AND
MESSAGE
TYPE
.
74
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.
74
XV
11.2
PARTNER
PROFILES
.
75
PARTNER
PROFILES
PLAY
AN
IMPORTANT
ROTE
IN
EDI
COMMUNICATIONS.
THEY
ARE
PARAMETER
FILES
WHICH
STORE
THE
EDI
PARTNER
DEPENDENT
INFORMATION.
75
11.3
DEFINING
THE
PARTNER
PROFILE
(
|WE20|
)
.
76
THE
TRANSACTION
WE20
IS
USED
TO
SET
UP
THE
PARTNER
PROFILE.
76
11.4
DATA
PORTS
(
|WE21|
)
.
77
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.
77
RFC
REMOTE
FUNCTION
CALL
79
12.1
WHAT
IS
REMOTE
FUNCTION
CALL
RFC?
.
80
A
REMOTE
FUNCTION
CALL
ENABLES
A
COMPUTER
TO
EXECUTE
A
PROGRAM
AN
ANOTHER
COMPUTER.
THE
CALLED
PROGRAM
IS
EXECUTED
LOCALLY
ON
THE
REMOTE
COMPUTER
USING
THE
REMOTE
COMPUTER'S
ENVIRONMENT,
CPU
AND
DATA
STORAGE.
80
12.2
RFC
IN
R/3
.
81
RFC
PROVIDES
INTERFACE
SHIMS
FOR
DIFFERENT
OPERATING
SYSTEMS
AND
PLATFORMS,
WHICH
PROVIDE
THE
COMMUNICATION
APIS
FOR
DOING
RFC
FROM
AND
TO
R/3.
81
12.3
TELEPORT
TEXT
DOCUMENTS
WITH
RFC.
82
THIS
EXAMPLE
DEMONSTRATES
THE
USE
OF
RFC
FUNCTIONS
TO
SEND
DATA
FROM
ONE
SAP
SYSTEM
TO
A
REMOTE
DESTINATION.
THE
EXAMPLE
IS
A
SIMPLE
DEMONSTRATION,
HOW
TO
EFFICIENTLY
AND
QUICKLY
USE
RFC
IN
YOUR
INSTALLATION.
82
12.4
CALLING
A
COMMAND
LINE
VIA
RFC
?
.
84
R/3
RFC
IS
NOT
LIMITED
TO
COMMUNICATION
BETWEEN
R/3
SYSTEMS.
EVERY
COMPUTER
PROVIDING
SUPPORTING
THE
RFC
PROTOCOL
CAN
BE
CALLED
FROM
R/3
VIA
RFC.
SAP
PROVIDES
NECESSARY
API
LIBRARIES
FOR
ALL
OPERATING
SYSTEMS
WHICH
SUPPORT
R/3
AND
MANY
MAJOR
PROGRAMMING
LANGUAGES
E:G.
C++,
VISUAL
BASIC
OR
DELPHI.
84
CALLING
R/3
VIA
OLE/JAVASCRIPT
87
13.1
R/3
RFC
FROM
MS
OFFICE
VIA
VISUAL
BASIC
.
88
THE
MICROSOFT
OFFICE
SUITE
INCORPORATES
WITH
VISUAL
BASIC
FOR
APPLICATIONS
(VBA)
A
FULLY
OBJECT
ORIENTED
LANGUAGE.
JAVASCRIPT
AND
JA
VA
ARE
NATURALLY
OBJECT
ORIENTED.
THEREFORE
YOU
CAN
EASILY
CONNECT
FROM
JA
VA
SCRIPT,
J
A
144,
WORD,
EXCEL
AND
ALL
THE
OTHER
VBA
COMPLIANT
SOFTWARE
TO
R/3
VIA
THE
CORBA
COMPATIBLE
OBJECT
LIBRARY
(IN
WINDOWS
KNOWN
ALSO
DLLS
OR
ACTIVE-X
(=OLE/2)
COMPONENTS).
88
13.2
CALL
TRANSACTION
FROM
VISUAL
BASIC
FOR
WORD
97
.
89
THIS
IS
A
LITTLE
WORD
97
MACRO,
THAT
DEMONSTRATES
HOW
R/3
CAN
BE
CALLED
WITH
A
MOUSE
CLICK
DIRECTLY
FROM
WITHIN
WORD
97.
89
13.3
R/3
RFC
FROM
JAVASCRIPT
.
91
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
OR
ACTIVE-X
(=OLE/2)
COMPONENTS).
91
13.4
R/3
RFC/OLE
TROUBLESHOOTING
.
93
PROBLEMS
CONNECTING
VIA
RFC
CAN
USUALLY
BE
SOLVED
BY
REINSTALLING
THE
FULL
SAPGU!
AND/OR
CHECKING
YOUR
NETWORK
CONNECTION
WITH
R/3.
93
XVI
CONTENTS
ALE
-
APPLICATION
LINK
ENABLING
95
14.1
A
DISTRIBUTION
SCENARIO
BASED
ON
IDOCS
.
96
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.
96
14.2
EXAMPLE
ALE
DISTRIBUTION
SCENARIO
.
97
TO
BETTER
UNDERSTAND
LET
US
MODEL
A
SMALL
EXAMPLE
ALE
SCENARIO
FOR
DISTRIBUTION
OF
MASTER
DATA
BETWEEN
SEVERAL
OFFICES.
97
14.3
ALE
DISTRIBUTION
SCENARIO
.
98
ALE
IS
A
SIMPLE
ADD-ON
APPLICATION
PROPPED
UPON
THE
IDOC
CONCEPT
OF
SAP
R/3.
IT
CONSISTS
ON
A
COUPLE
OF
PREDEFINED
ABAPS
WHICH
RELY
ON
THE
CUSTOMISABLE
DISTRIBUTION
SCENARIO.
THESE
SCENARIOS
SIMPLE
DEFINE
THE
IDOC
TYPES
AND
THE
PAIRS
OF
PARTNERS
WHICH
EXCHANGE
DATA.
98
14.4
USEFUL
ALE
TRANSACTION
CODES
.
99
ALE
IS
CUSTOMIZED
VIA
THREE
MAIN
TRANSACTION.
THESE
ARE
|SALE[
|WEDI|
AND
|BALE|
.
99
14.5
ALE
CUSTOMIZING
|SALE|
.
101
ALE
CUSTOMIZING
IS
RELATIVELY
STARIGHT
FORWARD.
THE
ONLY
MANDATORY
TASK
IS
THE
DEFINITION
OF
THE
ALE
DISTRIBUTION
SCENARIO.
THE
OTHER
ELEMENTS
DID
NOT
PROVE
AS
BEING
VERY
HELPFUL
IN
PRACTICAL
APPLICATIONS.
101
14.6
BASIC
SETTINGS
|SALE|
.
102
BASIC
SETTINGS
HAVE
DO
BE
ADJUSTED
BEFORE
YOU
CAN
START
WORKING
WITH
ALE.
102
14.7
DEFINE
THE
DISTRIBUTION
MODEL
(THE
"SCENARIO")
|BD64|
.
103
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.
103
14.8
GENERATING
PARTNER
PROFILES
|WE20|
.
105
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.
105
14.9
CREATING
IDOCS
AND
ALE
INTERFACE
FROM
BAPI
|SDBG|
.
109
THERE
IS
A
VERY
POWERFUL
UTILITY
WHICH
ALLOWS
TO
GENERATE
MOST
IDOC
AND
ALE
INTERFACE
OBJECTS
DIRECTLY
FROM
A
BAPT'S
METHOD
INTERFACE.
109
14.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.
113
WORKFLOW
TECHNOLOGY
115
15.1
WORKFLOW
IN
R/3
AND
ITS
USE
FOR
DEVELOPMENT
.
116
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.
116
XVII
15.2
EVENT
COUPLING
(EVENT
LINKAGE)
.
117
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.
117
15.3
WORKFLOW
FROM
CHANGE
DOCUMENTS
.
118
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.
118
15.4
TRIGGER
A
WORKFLOW
FROM
MESSAGING
.
119
THE
THIRD
COMMON
WAY
TO
TRIGGER
A
WORKFLOW
IS
DOING
IT
FROM
MESSAGING.
119
15.5
EXAMPLE,
HOW
TO
CREATE
A
SAMPLE
WORKFLOW
HANDLER
.
120
LET
US
SHOW
YOU
A
FUNCTION
MODULE
WHICH
IS
SUITABLE
TO
SERVE
AS
A
FUNCTION
MODULE
AND
DEFINE
THE
LINKAGE.
120
BATCH
INPUT
RECORDING
_
125
16.1
RECORDING
A
TRANSACTION
WITH
|SHDB[
.
126
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.
126
16.2
HOW
TO
USE
THE
RECORDER
EFFICIENTLY
.
129
THIS
ROUTINE
REPLACES
BDCRECXX
TO
ALLOW
EXECUTING
THE
PROGRAM
GENERATED
BY
SHDB
VIA
A
CALL
TRANSACTION
INSTEAD
OF
GENERATING
A
BTCI
RILE.
129
16.3
INCLUDE
ZZBDCRECXX
TO
REPLACE
BDCRECXX
.
130
THI
S
ROUTINE
REPLACES
BDCRECXX
TO
ALLOW
EXECUTING
THE
PROGRAM
GENERATED
BY
\SHDE^
VIA
A
CALL
TRANSACTION
INSTEAD
OF
GENERATING
A
BTCI
FILE.
130
16.4
ZZBRCRECXX_FB_GEN:
GENERATE
A
FUNCTION
FROM
RECORDING
.
132
THE
SHOWN
ROUTINE
ZZBDCRECXX_FB_GEN
REPLACES
BDCRECXXIN
A
RECORDED
ABAP.
UPON
EXECUTING,
IT
WILL
GENERATE
A
FUNCTION
MODULE
FROM
THE
RECORDING
WITH
ALL
VARIABLES
AS
PARAMETERS.
132
ED!
AND
INTERNATIONAL
STANDARDS
137
17.1
EDI
AND
INTERNATIONAL
STANDARDS
.
138
ELECTRONIC
DATA
INTERCHANGE
(EDI)
AS
A
TOOL
FOR
PAPERLESS
INTER-COMPANY
COMMUNICATION
AND
BASIC
INSTRUMENT
FOR
E-COMMERCE
IS
HEAVILY
REGULATED
BY
SE
VERA!
INTERNATIONAL
STANDARDS.
138
17.2
CHARACTERISTICS
OF
THE
STANDARDS
.
139
THE
WELL-KNOWN
STANDARDS
EDIFACT,
X.
12
AND
XML
HAVE
SIMILAR
CHARACTERISTICS
AND
ARE
DESIGNED
TIKE
A
DOCUMENT
DESCRIPTION
LANGUAGE.
OTHER
STANDARDS
AND
R/3
IDOCS
ARE
BASED
ON
SEGMENTED
FILES.
139
17.3
XML
.
140
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.
140
17.4
ANSIX.12
.
142
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.
142
XVIII
CONTENTS
ED!
CONVERTER
143
18.1
CONVERTER
.
144
SAP
R/3
HAS
FOREGONE
TO
IMPLEMENT
ROUTINES
TO
CONVERT
IDOCS
INTO
INTERNATIONAL
ED!
STANDARD
FORMATS
AND
FORWARDS
THOSE
REQUESTS
TO
THE
NUMEROUS
THIRD
PARTY
COMPANIES
WHO
SPECIALIZE
IN
COMMERCIAL
EDI
AND
E
COMMERCE
SOLUTIONS.
144
18.2
A
CONVERTER
FROM
GERMANY
.
145
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.
145
APPENDIX
147
19.1
OVERVIEW
OF
RELEVANT
TRANSACTIONS
.
147
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.
147
19.2
USEFUL
ROUTINES
FOR
IDOC
HANDLING
.
148
THESE
ARE
SOME
VERY
USEFUL
ROUTINES,
THAT
CAN
BE
USED
IN
IDOC
PROCESSING.
148
19.3
ALE
MASTER
DATA
DISTRIBUTION
.
149
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.
149
19.4
WWW
LINKS
.
150
THESE
IS
A
RANDOM
LISTING
OF
INTERESTING
WEB
SITES
DEALING
WITH
THE
EDI
TOPIC.
THEY
ARE
ACCURATE
AS
OF
NOVEMBER
1999.
150
19.5
QUESTIONNAIRE
FOR
STARTING
AN
IDOC
PROJECT
.
151
THIS
IS
A
SAMPLE
QUESTIONNAIRE
WITH
IMPORTANT
QUESTIONS
THAT
NEED
TO
BE
CLEARED
BEFORE
ANY
DEVELOPMENT
CAN
BE
STARTED.
151
INDEX
153 |
| 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 | BV013061442 |
| callnumber-first | H - Social Science |
| callnumber-label | HF5548 |
| callnumber-raw | HF5548.4.R2 |
| callnumber-search | HF5548.4.R2 |
| callnumber-sort | HF 45548.4 R2 |
| callnumber-subject | HF - Commerce |
| classification_rvk | ST 510 |
| ctrlnum | (OCoLC)44884374 (DE-599)BVBBV013061442 |
| discipline | Informatik |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>00000nam a22000008c 4500</leader><controlfield tag="001">BV013061442</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20040225</controlfield><controlfield tag="007">t</controlfield><controlfield tag="008">000229s2000 gw ad|| |||| 00||| eng d</controlfield><datafield tag="016" ind1="7" ind2=" "><subfield code="a">958466718</subfield><subfield code="2">DE-101</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">3528057297</subfield><subfield code="c">Gb. : DM 98.00</subfield><subfield code="9">3-528-05729-7</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)44884374</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV013061442</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-473</subfield><subfield code="a">DE-523</subfield></datafield><datafield tag="050" ind1=" " ind2="0"><subfield code="a">HF5548.4.R2</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="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 SapScript</subfield><subfield code="c">Axeö Angeli ; Ulrich Streit ; Robi Gonfalonieri</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Braunschweig ; Wiesbaden</subfield><subfield code="b">Vieweg [u.a.]</subfield><subfield code="c">2000</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XXI, 157 S.</subfield><subfield code="b">Ill., graph. Darst.</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">Business computing</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Auf der Titelseite Name des 1. Verfassers irrtümlich Axeö statt Axel</subfield></datafield><datafield tag="630" ind1="0" ind2="4"><subfield code="a">SAP R/3</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Wirtschaft</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Business</subfield><subfield code="x">Computer programs</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Electronic data interchange</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Schnittstelle</subfield><subfield code="0">(DE-588)4053059-0</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</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">SAP R/3</subfield><subfield code="0">(DE-588)4343439-3</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><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="2"><subfield code="a">Schnittstelle</subfield><subfield code="0">(DE-588)4053059-0</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">DNB 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=008900165&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-008900165</subfield></datafield></record></collection> |
| id | DE-604.BV013061442 |
| illustrated | Illustrated |
| indexdate | 2024-08-18T00:33:20Z |
| institution | BVB |
| isbn | 3528057297 |
| language | English |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-008900165 |
| oclc_num | 44884374 |
| open_access_boolean | |
| owner | DE-473 DE-BY-UBG DE-523 |
| owner_facet | DE-473 DE-BY-UBG DE-523 |
| physical | XXI, 157 S. Ill., graph. Darst. |
| publishDate | 2000 |
| publishDateSearch | 2000 |
| publishDateSort | 2000 |
| publisher | Vieweg [u.a.] |
| record_format | marc |
| series2 | Business computing |
| spelling | Angeli, Axel 1961- Verfasser (DE-588)122589270 aut The SAP R-3 guide to EDI and interfaces cut your implementation cost with Idocs, ALE and SapScript Axeö Angeli ; Ulrich Streit ; Robi Gonfalonieri Braunschweig ; Wiesbaden Vieweg [u.a.] 2000 XXI, 157 S. Ill., graph. Darst. txt rdacontent n rdamedia nc rdacarrier Business computing Auf der Titelseite Name des 1. Verfassers irrtümlich Axeö statt Axel SAP R/3 Wirtschaft Business Computer programs Electronic data interchange Schnittstelle (DE-588)4053059-0 gnd rswk-swf SAP R/3 (DE-588)4343439-3 gnd rswk-swf Elektronischer Datenaustausch (DE-588)4227290-7 gnd rswk-swf SAP R/3 (DE-588)4343439-3 s Elektronischer Datenaustausch (DE-588)4227290-7 s Schnittstelle (DE-588)4053059-0 s DE-604 Streit, Ulrich Verfasser aut Gonfalonieri, Robi 1964- Verfasser (DE-588)122589289 aut DNB Datenaustausch application/pdf http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=008900165&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA Inhaltsverzeichnis |
| 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 SapScript SAP R/3 Wirtschaft Business Computer programs Electronic data interchange Schnittstelle (DE-588)4053059-0 gnd SAP R/3 (DE-588)4343439-3 gnd Elektronischer Datenaustausch (DE-588)4227290-7 gnd |
| subject_GND | (DE-588)4053059-0 (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 SapScript |
| title_auth | The SAP R-3 guide to EDI and interfaces cut your implementation cost with Idocs, ALE and SapScript |
| title_exact_search | The SAP R-3 guide to EDI and interfaces cut your implementation cost with Idocs, ALE and SapScript |
| title_full | The SAP R-3 guide to EDI and interfaces cut your implementation cost with Idocs, ALE and SapScript Axeö Angeli ; Ulrich Streit ; Robi Gonfalonieri |
| title_fullStr | The SAP R-3 guide to EDI and interfaces cut your implementation cost with Idocs, ALE and SapScript Axeö 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 SapScript Axeö 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 sapscript |
| title_sub | cut your implementation cost with Idocs, ALE and SapScript |
| topic | SAP R/3 Wirtschaft Business Computer programs Electronic data interchange Schnittstelle (DE-588)4053059-0 gnd SAP R/3 (DE-588)4343439-3 gnd Elektronischer Datenaustausch (DE-588)4227290-7 gnd |
| topic_facet | SAP R/3 Wirtschaft Business Computer programs Electronic data interchange Schnittstelle Elektronischer Datenaustausch |
| url | http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=008900165&sequence=000001&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
| work_keys_str_mv | AT angeliaxel thesapr3guidetoediandinterfacescutyourimplementationcostwithidocsaleandsapscript AT streitulrich thesapr3guidetoediandinterfacescutyourimplementationcostwithidocsaleandsapscript AT gonfalonierirobi thesapr3guidetoediandinterfacescutyourimplementationcostwithidocsaleandsapscript |