EHP3 for SAP ERP
6.0
December 2009
English
750: ECR Compliant
Procurement Processes
Building Block Configuration Guide
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices
750: ECR Compliant Procurement Processes: Configuration Guide
Copyright
© Copyright 2008 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x,
System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS,
POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of
IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks
of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks
or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C ®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and
other SAP products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of SAP AG in Germany and in several other countries all over the world. All other
product and service names mentioned are the trademarks of their respective companies. Data
contained in this document serves informational purposes only. National product specifications may
vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its
affiliated companies ("SAP Group") for informational purposes only, without representation or warranty
of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The
only warranties for SAP Group products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
Key:
<XXX>
© SAP AG
 Variable entries
'XXX'
 Fixed entries
[XXX]
 Pushbutton
Page 2 of 8
SAP Best Practices
750: ECR Compliant Procurement Processes: Configuration Guide
Icons
Icon
Meaning
Caution
Example
Note or Tip
Recommendation
Syntax
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include field
names, screen titles, pushbuttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text
Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT
Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.
Example text
Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text>
Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.
© SAP AG
Page 3 of 8
SAP Best Practices
750: ECR Compliant Procurement Processes: Configuration Guide
Contents
ECR-Compliant Procurement Processes: Configuration Guide ................................................ 5
1
Purpose .............................................................................................................................. 5
2
Preparation ......................................................................................................................... 5
3
Configuration ...................................................................................................................... 5
3.1
Set Up the IDoc Interface ......................................................................................... 5
3.1.1
Create RFC Destination ....................................................................................... 5
3.1.2
Creating Transactional RFC ................................................................................ 6
3.1.3
Creating Fileport .................................................................................................. 7
3.1.4
Test Fileport Access ............................................................................................ 7
© SAP AG
Page 4 of 8
SAP Best Practices
750: ECR Compliant Procurement Processes: Configuration Guide
ECR-Compliant Procurement Processes:
Configuration Guide
1 Purpose
This configuration guide provides the information you need to set up the configuration of this
building block manually.
If you do not want to configure manually and prefer an automated installation process using
BC Sets and other tools, refer to the installation guide of this building block.
2 Preparation
Before you start installing this building block, you must install prerequisite building blocks. For
information on the prerequisite building blocks, see the Quick Guide for installing Retail
(located on the DVD in Retail_FR\Documentation\Retail_Quick_Guide_EN_FR_V1603.doc).
3 Configuration
3.1 Set Up the IDoc Interface
The IDoc interface is used for electronic data communication between different computers
and/or systems. IDocs map a business process (for example, an order). They make it
possible to have a paper-free exchange of business data. They are particularly useful as a
document that is understood by many functions and can be passed on to these functions.
IDocs depend solely on the business transaction – the message.
To be able to send IDocs within our SAP ECC System or between different SAP Systems, we
use a transactional Remote Function Call (RFC). RFCs make it possible to call and execute
predefined function modules on a remote system or within the same system. In this case we
are using function modules to process IDocs. The Remote Function Call is controlled using
the parameters of the RFC destination.
Setting the RFC destination takes place within the component ALE (Application Link
Enabling). ALE provides a basis from which to integrate business processes that can be
carried out across several SAP ECC or non-SAP systems. Data is also exchanged here in
the form of IDocs.
3.1.1
Create RFC Destination
Use
Here you must enter the address of the EDI partner system. As our EDI process takes place
in one system you enter the system address.
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu
© SAP AG
IMG  SAP NetWeaver  Application Server  IDoc
Interface/Application Link Enabling(ALE)  Communication 
Page 5 of 8
SAP Best Practices
750: ECR Compliant Procurement Processes: Configuration Guide
Create RFC Connections  ABAP connections
Transaction Code
SM59
2. On Screen Configuration of RFC Connections ,choose Create.
3. On Screen RFC Destination, make the following entries :
Field name
Description
User action
and values
Note
RFC Destination
Standard
name of an
RFC
destination
RTFCLNT013
log. System of your
client
Connection Type
3
Calculate SP from
planned markup
Target Host
Host name of
your system
Host name of your
system
System Number
System number
of your system
System number of
your system
4. Choose Save.
3.1.2
Creating Transactional RFC
Use
IDocs can be exchanged with ports in different ways using the external system. There are
different technical ways of carrying out port type communication. Setting up ports is a basic
precondition for exchanging data.
Four port categories are available in the standard SAP System, to which you can assign ‘real’
ports:

Transactional RFC (Remote Function Call) for ECC – ECC connections and external
systems

File port

CPI-C for R/2 connections

Internet
In our process we use a port with a transactional RFC. For this you enter the target system
directly as the RFC destination.
The system sends the IDocs using this port. You must enter the port in the outbound
parameters for the partner profiles.!
Procedure
1. Access the activity using one of the following navigation options:
IMG Menu
Tools  ALE  ALE Administration  Runtime Settings 
Port Maintenance
Transaction Code
WE21
© SAP AG
Page 6 of 8
SAP Best Practices
750: ECR Compliant Procurement Processes: Configuration Guide
2. On screen Port in IDoc processing, select Transactional RFC and choose Create.
3. Select own port name and make the following entries :
Field name
Description
User action and values
Name
PCS-RFC
Description
PCS RFC port
RFC destination
RTFCLNT013
Note
as created
in 3.1.1
4. Choose Save.
3.1.3
Creating Fileport
Use
Procedure
1.
Access the activity using one of the following navigation options:
IMG Menu
Tools  ALE  ALE Administration  Runtime Settings 
Port Maintenance
Transaction Code
WE21
2.
On screen Port in IDoc processing, select File and choose Create.
3.
On screen Port in IDoc processing, make the following entries :
Field name
Description
User action and values
Port
PCS-FILE
Description
File Port for PCS
Note
Outbound File
Physical directory
X
Function module
EDI_PATH_CREATE_ME
STYP_DOCNUM
3.1.4
Test Fileport Access
Procedure
1.
Access the activity using one of the following navigation options:
IMG Menu
Tools  ALE  ALE Administration  Runtime Settings 
Port Maintenance
Transaction Code
WE21
2.
On the Port in IDoc processing screen, expand File and select PCS-FILE.
3.
Choose tab page Outbound file,and check the Directory.
Attention: The file paths in field Directory depend on the operating system of your
application server! l(The direction of the slashes in the file paths (‘/’ or ‘\’) is
© SAP AG
Page 7 of 8
SAP Best Practices
750: ECR Compliant Procurement Processes: Configuration Guide
different)
For example: D:\usr\sap\<system>\SYS\global OR
D:/usr/sap/<system>/SYS/global
4.
Guideline: Update and use the path that is correctly defined in transaction AL11.
Choose Access Test.
5.
Choose Enter for confirming the message Access to directory possible from
application server.
6.
Choose Enter to confirm the appeared.
© SAP AG
Page 8 of 8