^]b\z `}~ Zl~F{Fl~`}~\ \ n~}mzz|^ ~||
by user
Comments
Transcript
^]b\z `}~ Zl~F{Fl~`}~\ \
n~}mzz|^
~||
^]b\z
`}~
Z
Zl~F{Fl~`}~\
\
n~}mzz|^
~||
]zzb~|z~
lZiez{Eb|G
3DOR$OWR&DOLIRUQLD
\
© 1999 by SAP AG. All rights reserved.
Neither this documentation nor any part of it may be copied or reproduced in
any form or by any means or translated into another language, without the
prior consent of SAP AG.
]|
z~
SAP AG makes no warranties or representations with respect to the content
hereof and specifically disclaims any implied warranties of merchantability or
fitness for any particular purpose. SAP AG assumes no responsibility for any
errors that may appear in this document. The information contained in this
document is subject to change without notice. SAP AG reserves the right to
make any such changes without obligation to notify any person of such
revision or changes. SAP AG makes no commitment to keep the information
contained herein up to date.
mz}~z
SAP, the SAP logo, R/2, R/3, SAPscript, ABAP, and other SAP related
products mentioned herein are registered or unregistered trademarks of SAP
AG. All other products mentioned in this document are registered or
unregistered trademarks of their respective companies.
Simplification Group
SAP Labs, Inc.
3475 Deer Creek Road
Palo Alto, CA 94304
ZZZVDSODEVFRPVLPSOH
VLPSOLI\U#VDSFRP
Printed in the United States of America.
&217(176
\z~JS`~lz~}^
~||]zzb~|z~
P
pzb^
~||]zzb~|z~X GGGGGGGGGGGGGGGGGGGGGGGGQ
a]~^]ba~
[~~XGGGGGGGGGGGGGGGGGGGGGGGGGGG JI
b
~~^]bSm\}~GGGGGGGGGGGGGGGGGGGGGG JI
.H\(',,PSOHPHQWDWLRQ,VVXHV +RZ'RHVWKLV*XLGH+HOS" +RZWR8VHWKLV*XLGH" \z~KS\kHLl~^]b
JL
h~~ GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG JM
\~zz}Zze|z
l~z\
~ GGGGGGGGGG JM
Z|zlZip
GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG JP
Z|z^~Fk~|~~ez~ GGGGGGGGGGGGGGGGGGGGGGGGG KJ
l~nzb]|Z}zGGGGGGGGGGGGGGGGGGGGGGGGGG KK
]~z_
~i GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG KL
]~n~Fl~||izz~~ GGGGGGGGGGGGGGGGGGGGGGGGG KP
M
EDI Configuration Guide | Release 4.x
\z~LS\l~||mzz|
KR
\b{}lz
~h}~AQNIBGGGGGGGGGGGGGGGGGGGG LI
6HWWLQJXSDQ,QERXQG3DUWQHU3URILOH &RQYHUWLQJ([WHUQDO3DUWQHUVWR,QWHUQDO3DUWQHUV 6HWWLQJ8S6DOHV2UJDQL]DWLRQ'DWD 6HWWLQJ8SWKH&XVWRPHU0DWHULDO,QIR5HFRUG 7LSVDQG7ULFNV,QERXQG6DOHV2UGHUV 3ULFLQJ 8VLQJ'RFXPHQW7H[WDVD3LSHOLQH 8QLYHUVDO3URGXFW&RGH83& 8QLWRI0HDVXUH&RQYHUVLRQ \h{}Z}z|~lg|~AQNOBGGGGGGGGGGG MI
$GYDQFH6KLS1RWLFHIRU6WDQGDUG$61 $GYDQFH6KLS1RWLFHIRU*URXSHG$61 6'6SHFLILF&RQILJXUDWLRQ6WDQGDUG$61 6'6SHFLILF&RQILJXUDWLRQ*URXSHG$61 (',6SHFLILF&RQILJXUDWLRQ6WDQGDUG$61 &RQGLWLRQ5HFRUG2XWSXW'HWHUPLQDWLRQ 2XWERXQG3DUWQHU3URILOH 2XWERXQG3DUWQHU3URILOH (',6SHFLILF&RQILJXUDWLRQ*URXSHG$61 &RQGLWLRQ5HFRUG2XWSXW'HWHUPLQDWLRQ 2XWERXQG3DUWQHU3URILOH 7LSVDQG7ULFNV2XWERXQG$GYDQFH6KLS1RWLFHV 8QLYHUVDO&DUWRQ&RGHV8&& 7KH3DFNLQJ5HODWLRQVKLSZLWKLQWKH6KLSPHQW,'RF \h{}b|~AQJIBGGGGGGGGGGGGGGGGGGGGGG OK
6'6SHFLILF&RQILJXUDWLRQ 2XWSXW'HWHUPLQDWLRQIRU%LOOLQJ'RFXPHQWV (',6SHFLILF&RQILJXUDWLRQ &RQGLWLRQ5HFRUG2XWSXW'HWHUPLQDWLRQ 2XWERXQG3DUWQHU3URILOH 7LSVDQG7ULFNV2XWERXQG,QYRLFHV 0DSSLQJWRWKH6$&$OORZDQFHVDQG&KDUJHV 3DFNLQJ,QIRUPDWLRQRQWKH,QYRLFH Contents
\z~MSm~^]b]|~
N
PN
m~b{}]|~GGGGGGGGGGGGGGGGGGGGGGGGGGGGGG PO
m~h{}]|~GGGGGGGGGGGGGGGGGGGGGGGGGGGGG PQ
9LHZLQJDQ,'RF o~]|~GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG QJ
O
EDI Configuration Guide | Release 4.x
& + $ 3 7 ( 5
`~lz~}^
~||
]zzb~|z~
J
Q
EDI Configuration Guide | Release 4.x
pzb^
~||]zzb~|z~X
Electronic Data Interchange (EDI) is about doing business and
carrying out transactions with your trading partners electronically.
EDI covers most things that are traditionally done using paper-based
communication, for example placing orders with suppliers and
carrying out financial transactions.
EDI is a technique used to communicate
business and information transactions
between computer systems of different
companies and organizations.
EDI is described as the interchange of structured data according to
agreed message standards between computer systems, by electronic
means. Structured data equates to a simple and direct method of
presenting the data content of a document, be it an invoice, a sales
order, or any other document type. The method of ensuring the
correct interpretation of the information by the computer system is
defined by the EDI standard.
Recognizing the value of EDI as a key business enabler early on, SAP
has provided support for EDI since R/3 Release 2.2x and continues to
enhance its solution.
History of EDI
Notes
EDI technologies have evolved as a natural data carrier replacing the paper
document. It is not a new concept or a new practice. EDI has existed for over
two decades in Europe and North America.
Early electronic interchanges used proprietary formats agreed upon between
two trading partners. This required a new program each time a new partner was
added to the existing system. In the 1960’s, some industry groups began a
cooperative effort to develop industry EDI standards for purchasing,
transportation, and financial applications. Many of these standards supported
only intra-industry trading, which led to a large number of EDI formats.
In 1979, the Accredited Standards Committee (ASC) X12 was formed to
develop a generic EDI standard. In 1993, Version 3, Release 4 contained 192
standards. There are over 100 additional standards in development. In the U.S.,
the most commonly used standard is ANSI X12, coordinated by the American
National Standards Institute (ANSI). While in Europe, it is the Electronic Data
Interchange for Administration, Commerce, and Transportation (EDIFACT)
standard.
R
Getting Started with Electronic Data Interchange
As shown in Figure 1–1, Company A and Company B want to
exchange business documents electronically. To achieve electronic
data interchange, the business applications (for example, R/3 System)
used in these companies would need to generate EDI transactions or
messages.
To enable data interchange, the business applications used by
Company A and B face the following obstacles:
n
Volume of the EDI transactions or messages is high
n
Different EDI formats exist for different industries
n
EDI standards are constantly upgraded
To overcome these obstacles, most business applications (including
R/3 System) make use of an EDI subsystem to convert application
data to the EDI standards. Figure 1–1 shows the flow of data between
Company A and B with R/3 System and EDI subsystems. Since the
EDI subsystem handles conversion and data transmission across the
WAN, the business applications do not have to contend with EDIrelated issues.
Figure 1–1 Interchange of business
documents between two companies using
R/3 System
Company A
Company B
Document
R/3 System
R/3 System
IDoc
IDoc
EDI
Subsystem
Transaction (X12) or
Message (EDIFACT)
Wide Area Network (WAN)
EDI
Subsystem
JI
EDI Configuration Guide | Release 4.x
a]~^]ba~
[~~X
n
Improves data accuracy: With EDI businesses can eliminate the
need to re-enter data from paper documents and thus prevent
potential data entry errors. Additionally, the cost of processing an
electronic requisition is estimated to be one-tenth the cost of
handling its paper equivalent.
n
Lowers personnel costs: EDI can help companies reduce the need
for personnel involved in orders and accounts processing.
n
Speeds up information exchange: EDI systems can shorten the
lead time between receipt and fulfilment of orders. When
scheduling information is transmitted with ordering data,
companies can plan production more accurately and thus reduce
stock inventories.
n
Reduces technical complexity related to data interchange: With
EDI companies use standardized data formats to exchange
documents. EDI allows companies using different business
applications and systems to achieve computer-to-computer
electronic exchange of business documents.
b
~~^]bSm\}~
EDI is implemented in much the same way as any other major
business strategy—in a piecemeal fashion, proving and evaluating
each stage before moving to the next. To avoid disruption of key
processes, it is advised not to attempt to switch to a full EDI operation
overnight. It takes time for people, systems, and processes to adapt to
any new methodology.
d~^]bb
~~zb~
Implementing EDI in an R/3 environment is often perceived to be a
daunting task.
Listed below are some of the key “areas of pain” in EDI
implementations:
n
Configuring at the application-level
n
Completing the technical set up
n
Testing the EDI setup
n
Mapping SAP IDoc to the EDI transaction or message type
Getting Started with Electronic Data Interchange
JJ
a]~`}~a~
X
This guide is intended to jump-start your EDI implementation. Using
step-by-step instructions, you will learn how to speed up the EDI
implementation.
The material covered in this guide is organized as follows:
n
Chapter 1: Getting Started with Electronic Data Interchange This
chapter presents an overview of EDI, its history, and how EDI
helps businesses.
n
Chapter 2: Configuring R/3 System for EDI: This chapter
describes application and technical configuration steps for EDI.
n
Chapter 3: Configuring Specific Transactions: This chapter
explains how to configure specific transactions in R/3.
n
Chapter 4: Testing EDI Documents: This chapter covers the tasks
related to testing your EDI documents. It includes various
transaction codes available in R/3.
n
Ready-to-use mapping documents: Generic mapping documents
(in Microsoft Excel format) are available for download at
KWWSZZZVDSODEVFRPHGL
an~`}~X
Throughout this guide, you will find the symbols shown below. These
mark special information that supplements the main discussion or
theme.
m~|mz
: This symbol flags information that is highly technical. It is
included for those who want to dig deeper into particular concepts or
explore background theory.
TechTalk
m?m|SThis symbol flags suggestions, hints, and practical
techniques to help you become more efficient in the way you use the
R/3 System.
Tips & Tricks
\zSThis symbol flags information that can help you steer clear
of common pitfalls. It demands careful reading.
Caution
JK
EDI Configuration Guide | Release 4.x
In the table below, you will find some of the text conventions used
throughout this guide.
Text convention
What it means
VDQVVHULI
Command syntax.
sans-serif italic
Screen names or on-screen objects (buttons, fields, etc.).
monospace
User input (text the user types verbatim).
name1 → name2
Menu selection. name1 is the menu name, and name2 is
the item on the menu.
g~
For illustration purposes, the step-by-step examples in this guide refer to certain system
names and values. Some or all of the values and system names shown in the examples
may not be applicable to your environment. Check with your system administrator for more
information on the systems you can use.
& + $ 3 7 ( 5
\kHLl~^]b
K
JM
EDI Configuration Guide | Release 4.x
h~~
Before you can enable your R/3 System for EDI, certain configuration
steps must be completed. In this chapter you will learn the following
first-time configuration steps:
1. Create and assign a logical system to a client
2. Activate the SAP Workflow
3. Activate event-receiver linkage
4. Set up an IDoc administrator
5. Define a port
6. Define user-specific parameters
\~zz}Zze|z
l~z\
~
Since all EDI transaction in R/3 Release 4.5B are ALE-enabled, a
logical system must be defined for each client. In this section we
explain how to create and assign a logical system to a client.
Caution
Each client in your system landscape that needs a logical system must have a
different logical system name. No two clients can have the same logical system
name. This restriction also applies to clients in different instances (for example,
development, test, or production systems).
mz
&UHDWHDORJLFDOV\VWHP
JG From the SAP main menu choose Tools → Business Engineer →
Customizing. Then, choose Implementation project → SAP Reference
IMG.
Configuring R/3 System for EDI
JN
KG On the Display structure: SAP reference IMG screen:
zG Expand the folder hierarchy as shown: Cross-Application
Components → Distribution (ALE) → Basic Settings → Logical
Systems
{G Double-click Define Logical System to execute it.
LG On the Change View “Logical system”: Overview screen, choose New
entries.
JO
EDI Configuration Guide | Release 4.x
MG On the New Entries: Overview of Created Entries screen:
zG Enter a logical system name (for example, YPCC) in the Log system
column.
{G Enter a description (for example, PCC logical system) in the
Description column.
|G Choose Save.
}G Choose Back.
mz
$VVLJQDORJLFDOV\VWHPWRDFOLHQW
JG On the Display structure: SAP Reference IMG screen, choose CrossApplication Components → Distribution (ALE) → Basic Settings →
Logical Systems → Assign Logical System to Client and choose
Execute.
KG An informational message (“The table is client-dependent “) appears.
Choose Continue.
Configuring R/3 System for EDI
JP
LG On the Change View “Clients”: Details screen:
zG Position the cursor in the Logical system field and choose F4 or
Possible entries.
{G Select the appropriate logical system (for example, YPCC) and
choose Enter.
|G Choose Save.
MG Choose Back to return to the SAP main screen.
Z|zlZip
SAP Workflow plays a critical role in EDI monitoring and notification.
Before you can start using SAP Workflow, you must perform the steps
shown below:
JG On the SAP main screen, enter transaction SWU3 in the Command field
and choose Enter (or in the IMG, choose Basis Components → Business
Management → SAP Business Workflow → Maintain Standard Settings for
SAP Business Workflow, and choose Execute).
KG On the Verify workflow Customizing screen, choose Automatic
Customizing.
JQ
EDI Configuration Guide | Release 4.x
LG If your Correction and Transport System (CTS) is on, you will need
to input a change request.
MG Once processing is complete, the Auto-customizing log appears in the
Verify workflow Customizing screen, providing the status of the listed
items.
NG Choose Back to return to the previous screen.
OG Under Workflow development environment, choose Execute next to No
prefix numbers for standard object types exist.
Execute
Configuring R/3 System for EDI
JR
PG On the Prefix Numbers for Workflow and Organizational Management:
Display screen:
zG Choose Change/Display.
{G Choose New Entries (Create in Release 4.0B).
Change/Display
New Entries
QG On the Detail View of Prefix Number: Create screen:
zG Enter a prefix number for your system client in the Prefix number
field (7 in Release 4.5B; 9 in Release 4.0B).
{G Choose Save.
Accept the default values for SAP
system and Client.
RG If your CTS system is on, you will need to input a change request.
KI
EDI Configuration Guide | Release 4.x
JIG On the Create Request screen:
zG Enter a short description (for example, prefix numbers) in the
Short description field.
{G Choose Save.
JJG On the Enter Change Request screen, choose Enter. The change request
data is now saved.
JKG Choose Back (or Cancel in Release 4.0B).
JLG On the Prefix Numbers for Workflow and Organizational Management:
Maintain screen:
zG Note that your entry is now in the table.
{G Choose Back to return to the workflow customizing screen.
Configuring R/3 System for EDI
KJ
JMG On the Verify workflow Customizing screen, choose Test RFC destination.
If the RFC destination is set up
correctly, you should receive the
message: ‘Ping’ performed
successfully. The RFC destination for
SAP Business Workflow is fully
configured.
JNG The Workflow runtime system shows that customizing is complete for
SAP workflow scenarios.
JOG If you are creating your own tasks, maintain an explicit number-range
for customer tasks.
JPG Choose Back to return to the IMG.
We need to activate the workflow because the EDI error handling and
notification procedure makes extensive use of workflow.
TechTalk
It is a good strategy to make use of workflow for error handling and notification
handling.
Z|z^~Fk~|~~ez~
JG In the Command field, enter transaction OYEB and choose Enter (or in
the IMG, choose Cross-Application Components → IDoc Interface /
Electronic Data Interchange → IDoc interface – Basis → Activate event
receiver linkage for IDoc inbound and choose Execute).
KG On the Activate event linkage popup, choose Yes. You will now get the
following system message: “IDoc: Event-event receiver coupling
activated successfully.”
KK
EDI Configuration Guide | Release 4.x
The inbound processing of IDoc uses the workflow functionality to pass the EDI
data to the appropriate application. Activating the event linkage creates the link
needed for the inbound EDI process to inform workflow to take the EDI data and
process it in the application.
TechTalk
l~nzb]|Z}z
Setting up an IDoc Administrator is required so that the system
knows whom to notify when an EDI error occurs.
The IDoc administrator could be specified for:
n
Each partner profile and message combination
n
Each partner
n
All partners and messages
The IDoc administrator could be any of the PD Organization
elements. Ideally, it is better to specify a position as an administrator.
Additionally, make sure that there is at least one administrator
defined. Otherwise, the notification will go to the inbox of all SAP
users since the work-item is considered as a general task.
JG In the Command field, enter transaction OYEA and choose Enter (or in
the IMG, choose Cross-Application Components → IDoc Interface /
Electronic Data Interchange → IDoc interface – Basis → Set up IDoc
administration and choose Execute).
KG On the Global parameter for IDoc interface screen:
zG Enter US in the Recipient type field.
{G Enter the user ID in the Identification field.
|G Choose Save.
Configuring R/3 System for EDI
Tips & Tricks
KL
For illustration purposes, the IDoc administrator has been directly assigned to a
specific user in this guide. We recommend that the IDoc Administrator be
assigned to a position in an existing organizational structure. Such an
assignment allows for greater flexibility within the system to handle personnel
changes.
]~z_
~i
Defining a port helps define the directories and filenames the
system uses to generate to and/or retrieve from the EDI IDoc file.
JG In the IMG, choose Cross-Application Components → IDoc
Interface/Electronic Data Interchange → IDoc interface – Basis → Set
proposal values for partner profiles and choose Execute (or transaction
code WE21).
KG On the Choose Activity screen:
zG Select the Define port: Port type “File” line.
{G Choose Choose.
KM
EDI Configuration Guide | Release 4.x
LG On the Change view “Definition of file ports”: Overview screen, choose
New entries.
MG On the New Entries: Details of Added Entries screen:
zG Enter a name (for example, SAPEDI) in the Port field.
{G Enter a description (for example, EDI port) in the Description
field.
|G Choose Command file.
Configuring R/3 System for EDI
TechTalk
KN
The version of an IDoc type or segment is developed in a correction level. The
latest version remains the current version in all subsequent correction levels.
When a new version is developed, it then becomes the current version. All
versions are retained in the system, hence reductions from current versions to
former versions are possible at any time. This allows the IDoc interface to serve
the interface with any subsystem in a compatible mode even after upgrades.
Remote Function Call (RFC) is the R/3 functionality that allows the translator to
communicate with the R/3 System and vice versa. The SERVER_EXEC is a
preconfigured destination provided by SAP for the customer.
The directory and shell script defined in the command file parameter is
necessary for outbound EDI if the R/3 System is to start—or trigger—the
external system (translator) using RFC. Consult your translator documentation
for more information on how to trigger the translator from SAP.
NG On the Parameters for Command File screen:
zG Enter SERVER_EXEC in RFC destination.
{G Enter the shell script directory in the Directory field.
Note that the shell script is provided by the translator company
and the directory is the location where the script is loaded by the
translator company.
|G Enter the shell script name (for example, out.script) in Shell
script.
}G Choose Copy.
OG From the Details screen, choose Outbound file.
KO
EDI Configuration Guide | Release 4.x
PG On the Parameters for Outbound File screen:
zG Enter /usr/sap/trans/data/ in Directory or the directory
structure assigned by Basis team.
{G Enter outbound in Outbound file.
|G Choose Copy.
Tips & Tricks
For illustration purposes, this guide assigns the outbound parameters to the
static filename “outbound.” For a standard installation, the use of a function
module to generate a dynamic name is usually preferred. On the Parameters for
Outbound File screen, you can view the function modules available by selecting
possible entries for Function module.
QG From the Details screen, choose Inbound file.
RG On the Parameters for inbound file screen:
zG Enter /usr/sap/trans/data/ in Directory.
{G Enter inbound in Inbound file.
|G Choose Copy.
TechTalk
For illustration purposes, the screenshot shows the inbound IDoc directory as
set to the standard SAP data directory. For a standard installation, the directory
and filename should be set to the appropriate values where the inbound IDoc
will reside.
Configuring R/3 System for EDI
KP
g~
For both inbound and status files, if the translator sends the directory and filename in the
script, then these values would be as documentation. If the translator is not making use of
pre-defined filenames, then these values become relevant and need to be integrated with
the translator script.
Defining parameters for the status file is necessary only if you want the
translator to send back the status of the IDocs and have it updated in R/3.
TechTalk
JIG From the Details screen, choose Status file.
JJG On the Parameters for Status File screen:
zG Enter /usr/sap/trans/data/ in Directory.
{G Enter status in Status file.
|G Choose Copy.
JKG On the Change View “Definition of file ports:” Details screen, choose
Save.
]~n~Fl~||izz~~
It is a good idea to set up user-specific parameters as they provide the
default values. Some examples of user parameters are as follows:
n
Test port for the file interface. For example, the paths for Test
inbound modified outbound file are derived from this description
n
Output format for the IDoc documentation, as well as directory and
name for the files outputted (for the HTML/XML/C-header)
n
HTML output of the IDoc Documentation (whether or not you want
to automatically start a browser)
n
Display zero values in the IDoc lists. For example, if every time step
in the case of IDoc inbound processing is to be displayed, even if
no IDocs have been received
KQ
EDI Configuration Guide | Release 4.x
& + $ 3 7 ( 5
\l~||mzz|
L
LI
EDI Configuration Guide | Release 4.x
Depending on the type of EDI transactions you want to set up with
your trading partner, you must first configure the specific transactions
you plan to use.
In this chapter you will learn how to configure the following
transactions for EDI processing:
n
Inbound sales order
n
Outbound advance ship notice
n
Outbound invoice
\b{}lz
~h}~AQNIB
Before you can start accepting EDI-enabled inbound sales orders from
a customer, the following configuration steps must be performed:
n
Set up a profile for each inbound partner
n
Convert the external partner number to an internal partner
number
n
Set up sales organization data
n
Set up the customer-material info record
Make sure that SAP workflow is activated. Inbound EDI processing will not
function properly unless the workflow event-receiver linkage is active.
Caution
l~zb{}iz~i
~
The process of setting up partner profile for each EDI customer allows
you to define the EDI-specific information the system would need to
process inbound IDocs.
JG To access the partner profiles screen, in the Command field, enter
transaction WE20 and choose Enter (or choose Tools → Business
Framework → ALE → Development → IDoc → IDoc Basis → IDoc →
Partner profile).
Configuring Specific Transactions
LJ
KG On the Change View “Partner profiles: header entries”: Overview screen,
choose New entries.
LG On the New Entries: Details of Created Entries screen:
zG Enter the customer number in Partn.number. This SAP Customer
number.
{G Enter KU in Partn.type.
|G Enter A in Partn.status.
}G Enter US in Typ.
~G Enter EN in Lang.
G Enter the user ID in User.
To allow greater flexibility
in error handling, the user
indicated in step 3f is
notified of an error only if no one is
specified at the transaction level.
LK
EDI Configuration Guide | Release 4.x
G Choose Save.
G Choose Back.
Tips & Tricks
In this guide, agents are assigned directly to a specific user in the partner profile
for testing. We recommend that you set up an organizational structure; agents
should be assigned to positions in the organizational structure. Such assignment
allows for greater flexibility within the system to handle personnel changes.
MG On the Change View “Partner profiles: Header entries”: Overview screen:
zG Select the partner from the list.
{G Choose Inbound parameters.
NG On the Change View “Partner profiles: Inbound parameters”: Overview
screen, choose New entries.
Configuring Specific Transactions
LL
OG On the New Entries: Details of Created Entries screen:
g~
Use German codes for partner
functions.
zG Enter AG in Partn.funct.
{G Enter ORDERS in Message type.
|G Enter ORDE in Process code.
}G Under Processing by function module, select Trigger immediately. If
you are using ABAP as your port type on Release 4.5, you could
choose Trigger by background program.
~G Enter US in Typ.
G Enter EN in Lang.
G Enter the user ID (for example, YPCC) in ID. Note that this is just
an example. Ideally, we recommend that you use an organization
structure (such as position).
G Choose Save.
LM
EDI Configuration Guide | Release 4.x
\~^~z
iz~b~z
iz~
The data defined in this transaction is used by inbound EDI
processing to convert the customer’s partner number to an R/3
partner number. In the example below, the ship-to number, passed on
with the IDoc, is referenced to the R/3 ship-to number. This can also
be used for outbound transactions (for example, 856 and 810) if the
customer wants the original identifiers to be referenced.
JG In the Command field, enter transaction VOE4 and choose Enter (or in
the IMG, choose Sales and Distribution → Electronic Data Interchange →
EDI messages → Configure EDI partners → Convert external to internal
partner numbers).
KG On the Change View “View for table EDPAR”: Overview screen, choose
New entries.
Configuring Specific Transactions
LN
LG On the New Entries: Overview of Created Entries screen:
zG Enter the customer number (for example, 1000025) in Customer.
{G Enter WE in Ext.function.
|G Enter 0010 in External partner.
}G Enter ship-to partner number (for example, 1000025) in Int.no.,
SAP Ship-to party.
~G Choose Save.
You must enter WE (the German code
for ship-to) in Ext. Function column.
However, the screen will display SH (the
English code for ship-to).
This value is checked against segment
E1EDKA1 field LIFNR where field
PARVW = “WE” (ship-to) on the IDoc.
Caution
The External partner field in this transaction is a character field. When entering
the external partner number, make sure the value is entered exactly how it
appears on the IDoc. Otherwise, the system will not be able to find the entry.
l~nlz
~hzz]zz
When creating a sales order, the system needs to know the sales
organization, distribution channel, and division for the order. By
setting up a sales organization record, you define the organizational
structure in which an inbound EDI order (for a specific customer)
should be created.
JG In the Command field, enter transaction VOE2 and choose Enter (or in
the IMG, choose Sales and Distribution → Electronic Data Interchange →
EDI messages → Configure EDI partners → Assign customer/vendor to
sales organization data).
LO
EDI Configuration Guide | Release 4.x
KG Choose New entries.
LG On the New Entries: Overview of Created Entries screen:
zG Enter the customer number in Customer, SAP Sold-to party.
{G Enter vendor number in Vendor number.
|G Enter 0010 in SOrg.
}G Enter 10 in DChl.
~G Enter 10 in Dv.
G Choose Save.
This value is checked against segment
E1EDKA1 field LIFNR where field
PARVW = “AG” (vendor) on the IDoc.
Note that the vendor # represents you
as the vendor to your customer.
Moreover, if the customer can buy from
more than one sales organization, then
the Vendor number field is the
differentiator.
if you have only one sales
organization, then it could be
hard-coded in the IDoc itself to
avoid this table.
Configuring Specific Transactions
TechTalk
LP
The Vendor number field is a character field in this transaction. When entering
the vendor number, make sure the value entered is exactly how it looks on the
IDoc. Otherwise, the system will not find the entry.
When the SaTy field is left empty, the system defaults to the standard order type
OR when processing the inbound IDoc. You can specify a different sales order
type in this field.
l~n~\~Ffz~z
bk~|}
R/3 uses the customer-material info record to determine what R/3
material number should be used in the sales order document.
JG To access the customer-material info record screen, in the Command
field, enter transaction VD51 and choose Enter (or choose Logistics →
Sales and distribution → Master data → Agreements → Customer-Material
Information → Create).
If the inbound IDoc contains the vendor material number (the R/3 material
number), then a customer-material info record does not have to be created.
Tips & Tricks
KG On the Create Customer-Material Info Record screen:
zG Enter the customer number in Customer.
{G Enter 0010 in Sales organization.
|G Enter 10 in Distribution channel.
}G Choose Enter.
LQ
EDI Configuration Guide | Release 4.x
LG On the Create Customer-Material Info Record: Overview Screen:
zG Enter the material number in Material, SAP Material # .
{G Enter the customer material number in Customer material. This
value is checked against segment E1EDP19 field IDTNR where
field QUALF = “001” on the IDoc.
|G Choose Save.
TechTalk
The customer material field is a character field in this transaction. When entering
the customer material number, make sure the value entered is exactly how it
appears on the IDoc. Otherwise, the system will not find the entry.
mz}m|Sb{}lz
~h}~
i|
On the inbound sales order (850) IDoc the customer-expected price
(E1EDP01-VPREI field) is an available field for the customer to
transmit. Of course, the customer generally does not tell the vendor
how much a product should cost. However, to use the pricing features
provided in R/3, the price may be transmitted by the customer and
imported into the sales order as a statistical pricing value only. When
a value exists in the customer-expected price (E1EDP01-VPREI) field,
it gets entered into the sales order as pricing condition “EDI1Customer expected Price.”
Depending on your company’s business practice the pricing
procedure used by the sales order can be configured to keep the
customer-expected price as a statistical reference or block the order if
Configuring Specific Transactions
LR
the difference in the customer and vendor’s price is too great.
Additionally, EDI1 and EDI2 must be included in every pricing
procedure that could be used by inbound order processing.
n]|~m~zzi~
~
Customers often provide vendors with information on the inbound
sales order IDoc that is not required by the vendor’s R/3 System. At
times, the customer requires this information on subsequent
outbound EDI transmissions that are sent to them. For example,
many customers include their internal department number on the
purchase order and require it back on the invoice sent to them.
This common scenario can be dealt with by bringing in the desired
information as document header text (E1EDKT1 & E1EDKT2
segments) and/or document item text (E1EDPT1 & E1EDPT2
segments). By configuring the text determination in the SD module,
texts can be passed from the sales order to the delivery and then to the
invoice document. The desired information will appear on the
outbound document and can be mapped to the appropriate field on
the outbound EDI transmissions.
n~z
i}|\}~Ani\B
Currently, when only the EAN/UPC code (E1EDP19-IDTNR when
E1EDP19-QUALF = 003) is transmitted on the inbound sales order
IDoc, the R/3 System interprets the UPC code as the material number.
Using the UPC code as the material number can be a problem if your
material master is not set up by UPC code.
The inbound EDI sales order process will show errors because the
system will be unable to recognize the material number. The current
inbound EDI orders process does not lookup material numbers based
on UPC code even though the information is maintained on the
material master. Usually, a user-exit is developed for the ORDERS
IDoc to search for the appropriate material number when provided
with the EAN/UPC number.
nFFf~z~\~
For inbound transactions (for example, sales orders), different
customers often transmit different unit-of-measure codes to define a
specific unit of measure for a vendor. Not all trading partners use ISO
unit-of-measure codes when sending an inbound order. In this
scenario, it is common that the translator converts the incoming unit
of measure into a valid unit of measure that R/3 recognizes.
MI
EDI Configuration Guide | Release 4.x
Be aware that the quantities should also be converted when the unit of
measure is converted (if necessary). See Figure 3–1 for an example of
unit-of-measure conversion.
Figure 3–1 Converting unit of measure:
An example
Order From Customer "A"
Quantity
UNIT OF MEASURE
50
PC
Order From Customer "B"
Quantity
UNIT OF MEASURE
1000
DA
Order From Customer "C"
Quantity
UNIT OF MEASURE
100
CB
E
D
I
S
U
B
S
Y
S
T
E
M
Order From Customer "A"
Quantity
UNIT OF MEASURE
50
EA
Order From Customer "B"
Quantity
UNIT OF MEASURE
2000
EA
Order From Customer "C"
Quantity
UNIT OF MEASURE
100
EA
^z
~
Customers A and C both order units of measure that are equivalent to the SAP configured
unit of measure. Therefore, the only requirement is to change the unit of measure field from
their value to the SAP EA value. Customer B’s orders relate to two of the internal SAP
configured units of measure. Therefore the unit of measure value as well as the actual order
quantities must be recalculated through the EDI subsystem to account for this.
\h{}Z}z|~lg|~AQNOB
The Advance Ship Notice (ASN) is one of the more difficult
transactions to map. Mapping difficulty occurs because there are
many levels and possible relationships that must be displayed
within the outbound EDI document. There are two scenarios in
which EDI customers receive ASNs; some customers require
grouped ASNs while others require standard ASNs. Both of these
scenarios are handled similarly within SAP. Just a few additions
must be made to supply customers with a grouped ASN.
MJ
Configuring Specific Transactions
Z}z|~lg|~lz}z}Zlg
The standard ASN sends one transaction to the partner pertaining to
one of their orders. Within this transaction there are two possible
scenarios:
n
Pick pack
n
Carton pack
In both cases the intermediate document for a standard ASN is the
output from the Shipping module of SAP R/3 (Logistics → Sales and
distribution → Shipping). Figure 3–2 shows the two types of standard
ASN transaction documents.
Figure 3–2 Standard ASN—Pick pack
and Carton Pack
Standard ASN: Pick Pack
Standard ASN: Carton Pack
Delivery
Pack
Delivery
Pack
Item
Item
Item
Item
Item
Pack
Pack
Pack
Standard ASNs are sent using R/3’s shipping functionality. The
output of the intermediate document is based on the creation and
goods-issue posting of a delivery in R/3. For guidance on mapping
EDI customers, refer to the mapping documents on the Internet at
KWWSZZZVDSODEVFRPHGL.
Z}z|~lg|~`~}Zlg
A grouped ASN sends information pertaining to multiple customer
orders in a single transactional document. This grouped ASN is
achieved by producing output from R/3’s Transportation module
(Logistics → Sales and distribution → Transportation).
MK
EDI Configuration Guide | Release 4.x
The Transportation module allows deliveries to be grouped together
into one shipment. Just like the standard ASN, the grouped ASN too
has two types of structures in which data can be presented: Pick pack
and the carton pack scenarios. Figure 3–3 shows the structure of a
grouped ASN.
Figure 3–3 Structure of a grouped ASN
Grouped Advanced Ship Notice
Shipment
In a grouped ASN everything
below the delivery level is
maintained the same as a
standard ASN. The only
difference between a grouped
ASN and a standard ASN is the
grouped ASN is able to display
multiple deliveries on one
transactional document.
Delivery A
Delivery B
l]l~||\zSlz}z}Zlg
Output type LAVA is the default output type configured for EDI to
generate an ASN from the Shipping application. To have output
determination such that when a delivery document is created a
corresponding ASN IDoc is generated, the output type LAVA needs to
be included in the output determination procedure for deliveries.
Configuring Specific Transactions
ML
Using the PCC you can verify the setup by performing the following
steps.
JG In the Command field, enter transaction V/36 and choose Enter (or in
the IMG, choose Sales and Distribution → Basic Functions → Output
Control → Output Determination → Output Determination Using the
Condition Technique → Maintain Output Determination for Deliveries →
Maintain output determination procedures).
MM
EDI Configuration Guide | Release 4.x
KG On the Change View “Procedures (Output Shipping)”: Overview screen:
zG Choose the appropriate procedure from the list.
{G Choose Control.
LG Make sure that condition type LAVA exists. If not, add it to your
procedure and save.
Add condition-type LAVA, if not present.
Configuring Specific Transactions
MN
At most companies, it is a common practice to create the ASN document after
the following two steps have been completed:
Tips & Tricks
n
Delivery note
n
Goods-issue
Output determination can be configured to do this by setting a requirement in the
output procedure. You can use “1”, the SAP- delivered requirement that can be
used to check if the delivery document has been goods-issued.
l]Fl~||\zS`~}Zlg
Output type SHAD (in Release 4.5B ) or LAT1 (in Release 4.0B) is the
default output type configured for EDI to generate ASN from the
Transportation module. To set up output determination such that
when a shipping document is created a corresponding ASN IDoc is
generated, the output type LAT1 needs to be included in the output
determination procedure for shipping. Using the PCC you can verify
the set up by performing the following steps.
JG In the Command field, enter transaction V/84 and choose Enter (or in
the IMG, choose Sales and Distribution → Basic Functions → Output
Control → Output Determination → Output Determination Using the
Condition Technique → Maintain Output Determination for Shipments →
Maintain output determination procedures).
MO
EDI Configuration Guide | Release 4.x
KG On the Change View “Procedures (Output Transport)”: Overview screen:
zG Choose the appropriate procedure (for example, V7ALLE) from
the list.
{G Choose Control.
LG Make sure that condition type SHAD exists. If not, add it to your
procedure and save.
Configuring Specific Transactions
MP
^]bFl~||\zSlz}z}Zlg
The configuration required for each customer you wish to send a
standard advance ship notice to via EDI is outlined below (Logistics →
Sales and distribution → Shipping).
\}k~|}Ah]~~zB
Creating a condition record for a specific customer sets up output
determination to generate an EDI message whenever a delivery note
is created for that customer.
JG To access the Create Output – Condition Records: Shipping screen, in the
Command field, enter transaction VV21 and choose Enter (or choose
Logistics → Sales and distribution → Master data → Output → Shipping
→ Create).
KG On the Create Output – Condition Records: Shipping screen:
zG Enter LAVA in Output type.
{G Choose Key combination.
LG On the Key Combination popup window:
zG Select Sales Organization/Customer Number.
{G Choose Enter.
MQ
EDI Configuration Guide | Release 4.x
MG
JG On the Create Condition Records (Outg. ship notifica.): Fast Entry screen:
zG Enter customer number in Customer, SAP Ship-to # .
{G Enter WE in PartF.
|G Enter 6 in Medium.
}G Enter 4 in Time.
~G Enter EN in Language.
G Choose Save.
Note that you could enter a value
between 1 and 4 in this field. It
controls the time at which the
output is actually generated and
dispatched. It is important that you study
the different possibilities and make an
appropriate decision. Moreover, in the
document, it can default in from the
condition type configuration.
h{}iz~i
~
The setup of a partner profile for each specific EDI customer allows
you to define the EDI-specific information the system needs when
generating the outbound IDocs.
JG To access the partner profiles screen, in the Command field, enter
transaction WE20 and choose Enter (or choose Tools → Business
Framework → ALE → Development → IDoc → IDoc Basis → IDoc →
Partner profile).
Configuring Specific Transactions
MR
KG On the Change View “Partner profile: Header entries”: Overview screen:
zG In change mode, select the customer (partner) from the list.
Note: This step assumes that the partner was already set up for
inbound sales order processing. Therefore, a header record
already exists. If the partner has not already been set up, “Setting
up an Inbound Partner Profile” on page 30 for more information
on how to create a header record.
{G Choose Outbound parameters.
NI
EDI Configuration Guide | Release 4.x
LG On the Change View “Partner profiles: Outbound parameters”:
Overview screen, choose New entries.
Configuring Specific Transactions
NJ
MG On the New Entries: Details of Added Entries screen:
zG Enter WE in Partn.funct.
{G Enter DESADV in Message type.
|G Enter the port name in Receiver port.
}G Under Output mode, select Transfer IDoc immed. Depending on the
business requirements or the translator capabilities, you could
make a different choice in the Output mode section.
~G Enter DELVRY01 in Basic type.
G Enter US in Typ.
G Enter EN in Lang.
G Enter the user ID in ID.
G
Choose the EDI standard tab.
EDI standard tab
Tips & Tricks
In this guide, agents are assigned directly to a specific user in the partner profile
for testing. We recommend that you set up an organizational structure; agents
should be assigned to positions in this structure. Such assignment allows for
greater flexibility within the system to handle personnel changes.
NK
EDI Configuration Guide | Release 4.x
NG On the New Entries: Details of Added Entries screen:
Steps 5a through 5c are not
mandatory and are mostly used for
documentation purposes. However,
some EDI subsystems read this
information to determine what map to
call.
zG Enter X in EDI standard.
{G Enter 856 in Message type.
|G Enter the version number of the X12 standard in Version.
}G Choose Save.
~G Choose Back.
Configuring Specific Transactions
NL
OG On the Change View “Partner profiles: Outbound parameters”:
Overview screen, choose Message Control.
Creating a message
control record links the
output determination to the
partner profile and defines the
function module and record structure
the system will use to create the
outbound IDoc.
PG On the Change View “Partner profiles: Message Control”: Overview
screen, choose New entries.
NM
EDI Configuration Guide | Release 4.x
QG On the New Entries: Details of Added Entries screen:
zG Enter V2 in Application.
{G Enter LAVA in Message type.
|G Enter DELV in Process code.
}G Choose Save.
^]bFl~||\zS`~}Zlg
This section outlines the required configuration for each customer you
wish to send a grouped ASN to via EDI (Logistics → Sales and
distribution → Transportation).
\}k~|}Ah]~~zB
Creating a condition record for the specific customer causes output
determination to generate an EDI message whenever a shipment
document is created for that customer.
JG To access the Create Output – Condition Records screen, in the Command
field, enter transaction VV71 and choose Enter (or choose Logistics →
Sales and distribution → Master data → Output → Shipment → Create)
Configuring Specific Transactions
NN
KG On the Create Output-Condition Records: Transport screen:
zG Enter SHAD (LAT1 in Release 4.0B) in Output type.
{G Choose Key Combination.
LG On the Key Combination popup window:
zG Select TrspPlPoint and Shipment Type.
{G Choose Enter.
MG On the Create Condition Records (Ship. notification): Fast Entry screen:
zG Enter the transportation planning point in TransportPlanningPt.
{G Enter the shipment type in ShipmntTyp.
|G Enter WE in PartF.
}G Enter 6 in Medium.
~G Enter 4 in Time.
G Enter EN in Language.
G Choose Save.
NO
EDI Configuration Guide | Release 4.x
h{}iz~i
~
The setup of a partner profile for each specific EDI customer allows
you to define the EDI-specific information the system needs when
generating the outbound IDocs.
JG To access the partner profiles screen, in the Command field, enter
transaction WE20 and choose Enter (or choose Tools → Business
Framework → ALE → Development → IDoc → IDoc Basis → IDoc →
Partner profile).
KG On the Change View “Partner profiles: Header entries”: Overview screen:
zG Select the customer (partner) from the list (for example, partner
number 1001580).
7. Note: This step assumes the partner is already set up for inbound
sales order processing. Therefore, a header record already exists.
If the partner has not already been set up, see “Setting up an
Inbound Partner Profile” on page 30.
{G Choose Outbound parameters.
Configuring Specific Transactions
NP
LG On the Change View “Partner profiles: Outbound parameters”:
Overview screen, choose New entries.
NQ
EDI Configuration Guide | Release 4.x
MG On the New Entries: Details of Added Entries screen:
zG Enter WE in Partn.funct.
{G Enter SHPMNT in Message type.
|G Enter the port name in Receiver port.
}G Under Output mode, select Transfer IDoc immed.
~G Enter SHPMNT02 in Basic type.
G Enter US in Typ.
G Enter EN in Lang.
G Enter the user ID in ID.
G
Tips & Tricks
Choose the EDI standard tab.
In this guide, agents are assigned directly to a specific user in the partner profile
for testing. We recommend that you set up an organizational structure; agents
should be assigned to positions in this structure. Such assignment allows for
greater flexibility within the system to handle personnel changes.
Configuring Specific Transactions
NR
NG On the New Entries: Details of Added Entries screen:
zG Enter X in EDI standard.
{G Enter 856 in Message type.
|G Enter the version of the X12 standard in Version.
}G Choose Save.
~G Choose Back.
OI
EDI Configuration Guide | Release 4.x
OG On the Change View “Partner profiles: Outbound parameters”:
Overview screen, choose Message Control.
TechTalk
Creating a message control record links the output determination to the partner
profile and defines the function module and record structure the system will use
to create the outbound IDoc.
PG On the Change View “Partner profiles: Message Control”: Overview
screen, choose New entries.
Configuring Specific Transactions
OJ
QG On the New Entries: Details of Added Entries screen:
zG Enter V7 in Application.
{G Enter SHAD or LAT1 in Message type.
|G Enter SD11 in Process code.
}G Choose Save.
~G Choose Back twice.
mz}m|Sh{}Z}z|~lg|~
n~z
\z\}~An\\B
The universal carton code (UCC-128) assignment is not a standard
delivered calculation. Once an item has been packed in its appropriate
shipping material, the shipping material is given a shipping unit ID.
This shipping unit ID will appear in the E1EDL37-EXIDV field on the
SHPMNT02 IDoc. The universal carton code can be provided on the
SHPMNT02 IDoc by creating a user-exit that takes the E1EDL37EXIDV value, adds the vendor-specific information to it, and creates
the check digit.
OK
EDI Configuration Guide | Release 4.x
m~iz|k~
z~l~b]|
Defining the packing relationship for pick pack ASNs requires the
translator to do some referencing. The EDI document often requires
that the materials be presented by shipping unit ID, followed by the
material number. However, the SAP IDoc does not directly present the
information in this order. The diagram below illustrates the packing
relationship presented by the IDoc.
The IDoc displays the information
pertaining to the packing material
(E1EDL37). This segment however
does not contain the information on the
material numbers in the shipping unit.
The information provided on the
material only displays the line number of
the delivery that the material originates
from (E1EDL44-POSNR).
Delivery
Packing material ID -- EXIDV
Packing Material
(E1EDL37)
To find the actual material number, the
E1EDL24 segment must be referenced
using the line number (POSNR) from
the E1EDL44 segment.
Line items of the delivery that
are packed within it
Contents Information
(E1EDL44)
This reference may take some creative
programming within the EDI subsystem
translator. Often the values within the
E1EDL37 segment are augmented to
display all the required information
instead of developing this complex
reference within the subsystem.
Delivery line item
Material in the delivery line item
Delivery Line
Information
(E1EDL24)
\h{}b|~AQJIB
l]Fl~||\z
h]~~z[
]|~
At most EDI installations where a single output type is used for
multiple outputs (for example, printers and EDI), the output
determination for a specific document is usually set up in a tiered
order. This setup is used to distinguish the output on a customer-by-
Configuring Specific Transactions
OL
customer basis. However, you do not have to set up a specific output
condition for each customer. The two-tier approach allows the system
to first check if a condition exists to generate the output (for example,
EDI) for a specific customer. If not, then a more general condition (for
example, based on sales organization) would exist to direct the system
to generate a paper document for the current customer.
In the example shown below, you will see how output determination
can be configured using the PCC as a basis.
g~
This example refers to installations that use the condition technique for output
determination and only one output type “RD00”.
JG In the Command field, enter transaction V/54 and choose Enter (or in
the IMG, choose Sales and Distribution → Basic Functions → Output
Control → Output Determination → Output Determination Using the
Condition Technique → Maintain Output Determination for Billing
Documents → Maintain access sequences).
OM
EDI Configuration Guide | Release 4.x
KG On the Change View “Access Sequence (Output Billing)”: Overview
screen:
zG Choose the desired access sequence (for example, YPCC, Sales
organization).
LG Choose Accesses.
Configuring Specific Transactions
ON
MG On the Change View “Accesses (Output Billing)”: Overview screen:
zG Add the Sales Organization/Customer Number access above the
existing Sales Org. access.
{G In the Requirement column, enter a requirement (for example, 62)
if desired.
|G Select the Exclusive checkbox for the first access.
}G Choose Save.
Checking the Exclusive box directs the
system to stop searching for another
condition after the first one is found. Leave
this box unchecked if you want the system
to continue searching for additional
conditions. Be aware that non-selection
means that you will most likely generate
multiple outputs for your invoice
document. Most customers are adding
billing type to the access sequence
because they want certain invoice
document types to go out via EDI but not
others.
An entry in the Requirements
column directs the system to send
the output only if it fulfills the
requirement.
^]bFl~||\z
Configuring for EDI involves the following two steps:
n
Condition record (output determination)
n
Outbound partner profile
\}k~|}Ah]~~zB
This section outlines the configuration steps required for each
customer you wish to send an invoice via EDI.
Creating a condition record for the specific customer sets up output
determination to generate an EDI message whenever an invoice is
created for that customer.
OO
EDI Configuration Guide | Release 4.x
JG To access the Create Output – Condition Records screen, in the Command
field, enter transaction VV31 and choose Enter (or choose Logistics →
Sales and distribution → Master data → Output → Billing document →
Create).
KG On the Create Output – Condition Records: Billing screen:
zG Enter RD00 in Output type.
{G Choose Key combination.
LG On the Key Combination popup window:
zG Select Sales Organization/Customer Number.
{G Choose Enter.
Configuring Specific Transactions
OP
MG On the Create Condition Records (Invoice): Fast Entry screen:
zG Enter the customer number in Customer.
{G Enter RE in PartF.
|G Enter 6 in Medium.
}G Enter 4 in Time.
~G Enter EN in Language.
G Choose Save.
h{}iz~i
~
The setup of a partner profile for each specific EDI customer allows
you to define the EDI-specific information the system needs when
generating the outbound IDocs.
JG To access the Partner profiles screen, in the Command field, enter
transaction WE20 and choose Enter (or choose Tools → Business
Framework → ALE → Development → IDoc → IDoc Basis → IDoc →
Partner profile).
OQ
EDI Configuration Guide | Release 4.x
KG On the Change View “Partner profiles: Header entries”: Overview screen:
zG Select the customer (partner) from the list.
Note: This step assumes that the partner was already set up for
inbound sales order processing. If the partner has not already
been set up, see “Setting up an Inbound Partner Profile” on
page 30 for details on how to create a header record.
{G Choose Outbound parameters.
LG On the Change View “Partner profiles: Outbound parameters”:
Overview screen, choose New entries.
Configuring Specific Transactions
OR
MG On the New Entries: Details of Added Entries screen:
zG Enter RE in Partn.funct.
{G Enter INVOIC in Message type.
|G Enter the port name in Receiver port.
}G Under Output mode, select Transfer IDoc immed.
~G Enter INVOIC02 in Basic type.
G Enter US in Typ.
G Enter EN in Lang.
G Enter the user ID in ID.
G
Choose the EDI standard tab.
In this guide, agents are assigned directly to a specific user in the partner profile
for testing. We recommend that you set up an organizational structure; agents
should be assigned to positions in this structure. Such assignment allows for
greater flexibility within the system to handle personnel changes.
PI
EDI Configuration Guide | Release 4.x
JG On the New Entries: Details of Added Entries screen:
zG Enter X in EDI standard.
{G Enter 810 in Message type.
|G Enter the version of the X12 standard in Version.
}G Choose Save.
~G Choose Back.
Configuring Specific Transactions
PJ
KG On the Change View “partner profiles: Outbound parameters”: Overview
screen, choose Message Control.
TechTalk
Creating a message control record links the output determination to the partner
profile and defines the function module and record structure the system will use
to create the outbound IDoc.
LG On the Change View “Partner profiles: message Control”: Overview
screen, choose New entries.
PK
EDI Configuration Guide | Release 4.x
MG On the New Entries: Details of Added Entries screen:
zG Enter V3 in Application.
{G Enter RD00 in Message type.
|G Enter SD09 in Process code.
}G Choose Save.
mz}m|Sh{}b|~AQJIB
fz~lZ\SZ
z|~z}\z~
The allowances and charges within the EDI document are usually
predefined by the trading partner. These allowance and charge codes
must relate to a corresponding pricing condition within the sales
document pricing procedure. Since pricing procedures are unique to
each implementation, be sure that all the allowance and charge codes
required by the customer are contained within the billing document
pricing procedure.
Configuring Specific Transactions
PL
iz|bz~b|~
Currently the SAP INVOIC02 IDoc information pertaining to the way
an item is packed is not available. This information is available on the
advance ship notice IDoc. To have this information present on the
INVOIC02 IDoc, a user-exit must be activated to extract the
information from the delivery document and provide it on the
outgoing IDoc. EDI header information such as the total number of
units shipped is also not available on the standard delivered
INVOIC02 IDoc. A user-exit is often used to pass this information
with the E1EDS01 segment.
PM
EDI Configuration Guide | Release 4.x
& + $ 3 7 ( 5
m~^]b]|~
M
PO
EDI Configuration Guide | Release 4.x
m~b{}]|~
When an implementation project starts, the setup and mapping of
data the translator needs to trigger the inbound process may not be
ready. However, this should not keep you from testing the inbound
process within R/3. As part of the EDI subsystem, testing tools are
provided to simulate the triggering of the inbound processing just like
the translator. Often, it is convenient to simultaneously test both
outbound and inbound processes in R/3 by generating an outbound
IDoc and then passing it back as an inbound IDoc. In the PCC, this
scenario is preconfigured and the Modification of Outbound File
Triggering Inbound Process is the transaction used to achieve this task.
To use this transaction, in the Command field, enter transaction WE12
and choose Enter (or choose Tools → Business Framework → ALE →
Development → IDoc → IDoc Basis → Test → Inbound proc of modified
outbound file).
Testing EDI Documents
PP
NG On the Modification of Outbound File screen:
zG Under Source, enter c:\sappcadam\outbound in
Directory+file.
{G Under Target, enter c:\sappcadam\inbound in Directory+file.
|G Enter customer number in Partner number.
}G Enter KU in Partner type.
~G Enter AG in Partn.function
G Enter ORDERS in Message type.
G Enter SAPEDI in Port.
G Choose Execute.
PQ
EDI Configuration Guide | Release 4.x
m~h{}]|~
o~zb]|
During testing it may be useful to view the information created in the
IDoc.
JG To access the IDoc lists screen, in the Command field, enter transaction
WE05 and choose Enter (or choose Tools → Business Framework → ALE
→ Development → IDoc → IDoc Basis → IDoc → IDoc lists).
KG On the IDoc Lists screen:
zG Enter the desired date range in Date created.
{G Choose Execute.
Tips & Tricks
You can narrow the number of IDocs returned by entering ORDERS (for sales
orders), DESADV (for advance ship notices) or INVOIC (for invoice) in the
logical Message type field.
Testing EDI Documents
PR
LG Perform one of the following two actions:
zG Double-click on ORDERS to view the list of outbound orders,
DESADV to view the list of outbound advance ship notices or
INVOIC to view the list of outbound invoices.
{G Double-click on ORDERS to view the list of inbound orders or
DESADV to view the list of inbound advance ship notices, ORDRSP
to view list of inbound confirmations or INVOIC to view the list of
inbound invoices.
Option 1
Option 2
MG On the IDoc List screen, double-click on the desired IDoc from the
list.
QI
EDI Configuration Guide | Release 4.x
NG On the IDoc display screen, click the plus (+) node to expand the list.
You can view the data in the IDoc by
double-clicking on any of the segments.
Testing EDI Documents
QJ
o~]|~
To view or verify the documents created via EDI, you can execute the
transaction or menu paths in the following table for the desired
document.
Table 4–1 Verifying EDI documents
EDI Message
Transaction
Menu Path
Outbound Purchase
Order
ME23
Logistics → Materials Management 1.
→ Purchasing → Purchase order
→ Display
2.
Inbound Sales Order
VA03
Outbound Order
Confirmation
VA03
Inbound Order
Confirmation
ME23
Outbound Delivery
(ASN)
VL03
Inbound Delivery
(ASN)
VL33
Logistics → Sales and distribution
→ Sales → Order → Display
Logistics → Sales and distribution
→ Sales → Order → Display
Steps
Choose Enter.
1.
Enter Sales Order number in Order field.
2.
Choose Enter.
1.
Enter Sales Order number in Order field.
2.
Choose Enter.
Logistics → Materials Management 1.
→ Purchasing → Purchase order
→ Display
2.
Logistics → Sales and distribution
→ Shipping → Outbound delivery
→ Display
Enter Purchase Order number in Purchase
order field.
Enter Purchase Order number in Purchase
order field.
Choose Enter.
3.
Select an Item.
4.
Choose Item → Details.
5.
Verify Sales order number in the Acknowl.no
field.
1.
Enter Delivery number in Delivery field.
2.
Choose Enter.
Logistics → Logistics execution → 1.
Inbound Delivery → Inbound
2.
delivery → Display
Enter Delivery number in Delivery field.
Choose Enter.