sas supplier relationship management adapter for...

SAS®

Supplier RelationshipManagement Adapter for SAP R/3: Implementation Guide

The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2004. SAS® Supplier Relationship Management Adapter for SAP R/3: Implementation Guide. Cary, NC: SAS Institute Inc.

SAS® Supplier Relationship Management Adapter for SAP R/3: Implementation Guide

Copyright © 2004, SAS Institute Inc., Cary, NC, USA

All rights reserved. Produced in the United States of America. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc.

U.S. Government Restricted Rights Notice: Use, duplication, or disclosure of this software and related documentation by the U.S. government is subject to the Agreement with SAS Institute and the restrictions set forth in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513. 1st printing, April 2004 SAS Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential. For more information about our e-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing Web site at support.sas.com/pubs or call 1-800-727-3228. SAS® and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration. Other brand and product names are trademarks of their respective companies.

ContentsPREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v

CHAPTER 1: SETTING UP THE BATCH RFC SERVER REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1The Batch RFC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Creating an RFC Destination Group and RFC Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Create an RFC Destination Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Create RFC Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Creating a Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

CHAPTER 2: INSTALLING THE SAS SUPPLIER RELATIONSHIP MANAGEMENT ADAPTER FOR SAP R/3 . . . . . .11Extracting the Solution Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Editing the autoexec.sas File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Updating the Adapter Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Adding the Data Warehouse Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Setting Up SAP Logon Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Create a New Logon Profile in SAS/ACCESS Interface to R/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Update the autoexec.sas File for Automatic Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Extracting SAP R/3 Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Update the Metadata Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Create R/3 Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

CHAPTER 3: SETTING UP THE RFC LISTENER REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27The RFC Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Creating an RFC Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Updating the CMD or Shell Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Update sas_rfcexec.cmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Update kill_listener.cmd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Editing the autoexec.sas File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

CHAPTER 4: INTEGRATING WITH SAS SUPPLIER RELATIONSHIP MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . .33Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Update SAS Supplier Relationship Management Properties for Language Formats . . . . . . . . . . . . . . . . . . . .33

APPENDIX A: UPDATING THE autoexec.sas FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35The autoexec.sas File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Changing the User Default Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Change Data Capture of Accounting Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Starting the Batch RFC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Updates for Automatic Logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Updates for Server-Side Join Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Language and Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

APPENDIX B: Recommended Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Preface

Purpose

This document covers the location and extraction of SAP R/3 system data for integration with the SAS Supplier Relationship Management Adapter for SAP R/3.

Prerequisites

To take full advantage of the SAS Supplier Relationship Management Adapter for SAP R/3, the following software components must be installed.

Data warehouse components:

• SAS System software, Version 8.2 or later version • Recommended: SAS/AF software • Recommended: SAS/CONNECT software (depends on configuration) • SAS/FSP software • SAS/Warehouse Administrator software • SAS/ACCESS Interface to R/3 software

Data warehouse exploitation:

• SAS/EIS software • SAS/GRAPH software • SAS Supplier Relationship Management

Setting Up the Batch RFC Server Requirements

The Batch RFC Server The Batch RFC Server enables SAP R/3 table extraction to execute as a batch job, running as a background process. The main benefits of running on the Batch RFC Server are as follows:

• There is no interference with the foreground sessions (Dialogue Processes) that are running interactively.

• Any time-out restrictions that have been placed on the standard RFC server will not affect Batch RFC Server processes.

Hence much longer and more resource consuming extractions can be executed without fear of timing out or preventing users from using their interactive sessions.

Creating an RFC Destination Group and RFC Destinations An RFC destination defines for SAP R/3 exactly where to send the information that it has extracted. RFC destinations can be set up in an RFC destination group.

Create an RFC Destination Group To create an RFC destination group:

1. Log in to the SAP R/3 GUI. 2. On the command line, type SM59. The Display and Maintain RFC Destinations window opens

(Display 1.1).

C H A P T E R

1

2 SAS Supplier Relationship Management Adapter for SAP R/3: Implementation Guide

Display 1.1 Display and Maintain RFC Destinations Window

3. Click Create. The RFC Destination window opens (Display 1.2).

Chapter 1: Setting Up the Batch RFC Server Requirements 3

Display 1.2 RFC Destination Window

4. In the RFC Destination window, fill in the fields as follows: • RFC destination: SRMADAPTER • Connection type: T • Description: SRM Adapter Destination Group

5. Press ENTER. The RFC Destination SRMADAPTER window opens (Display 1.3).


Display 1.3 RFC Destination SRMADAPTER Window

6. In the RFC Destination SRMADAPTER window, click Registration. Type SRMADAPTER in the

Program ID field.

7. To save the changes, click the diskette icon ( ). The status bar indicates that the destination was saved.

8. Click the Back button ( ) to exit.

Create RFC Destinations The same process that is used to create the destination group is also used to create the destinations. The process that is described below must be repeated for each required destination. For each additional destination, the suffix number in the destination name and in the program ID must be incremented by 1 (for example, SRMADAPTER1 changes to SRMADAPTER2, and so on). To create an RFC destination:

1. On the SAP R/3 GUI command line, type SM59. The Display and Maintain RFC Destinations window opens (Display 1.4).



3. In the RFC Destination window, fill in the fields as follows: • RFC destination: SRMADAPTER1 • Connection type: T • Description: SRM Adapter Data Destination

4. Press ENTER. The RFC Destination SRMADAPTER1 window opens (Display 1.6).


Display 1.6 RFC Destination SRMADAPTER1 Window

5. In the RFC Destination SRMADAPTER1 window, click Registration. Type SRMADAPTER1 in the Program ID field.


7. Click the Back button ( ) to exit. 8. If applicable, repeat this process for the next destination, incrementing the number at the end of the

RFC Destination name and the Program ID.

Creating a Variant To create a variant:

1. On the SAP R/3 GUI command line, type SE38. The ABAP Editor: Initial Screen window opens (Display 1.7).


Display 1.7 ABAP Editor: Initial Screen Window

2. In the ABAP Editor: Initial Screen window, type ZSASRDBT in the Program field, select Variants, and click Display. The ABAP: Variants – Initial Screen window opens (Display 1.8).


Display 1.8 ABAP: Variants - Initial Screen Window

3. In the Variant field, type SRMADAPTER. Click Create. The Maintain Variant: Report ZSASRDBT, Variant SRMADAPTER window opens (Display 1.9).

Display 1.9 Maintain Variant: Report ZSASRDBT, Variant SRMADAPTER Window


4. In the G_DEST field, type the name of the destination group that you created earlier. Click the Attributes button.

5. Type a description in the Description field.

6. To save the changes, click the diskette icon ( ). The status bar indicates that the variant was saved. If desired, you can now log out of the SAP R/3 GUI.

Installing the SAS Supplier Relationship Management Adapter for SAP R/3

Extracting the Solution Adapter The adapter is provided in the form of a self-extracting WinZip file, named SRMAdapter_v24.exe. Double-click this file to launch the InstallShield Wizard, which will guide you through the installation process (Display 2.1).

Display 2.1 InstallShield Wizard

C H A P T E R

2


By default, the adapter files are installed in the C:\SRM_sa_2.4 folder. To accept this default, ensure that the Save files in folder field contains the text C:\ and click Next. To install the adapter in a directory other than the default, edit the text in the Save files in folder field and click Next (Display 2.2).

Display 2.2 Custom Installation Folder

All the adapter folders and files are extracted to the specified directory.

Editing the autoexec.sas File If the adapter is installed in a directory other than the default, then the autoexec.sas file must be updated to reflect the new location, see “Changing the Default User Path” in Appendix A.

Updating the Adapter Shortcut If the adapter is installed in a directory other than the default, then the shortcut to the adapter must be updated to point to the new location. The shortcut SAS® SRM Adapter for SAP R3 2.4 is located in the same directory as the autoexec.sas file. To update the shortcut, right-click the file and select Properties. The Properties dialog box for the shortcut opens (Display 2.3). Update the Start in field to reflect the required directory path.

Chapter 2: Installing the SAS Supplier Relationship Management Adapter for SAP R/3 13

Display 2.3 Changes to Solution Adapter Shortcut

Click OK to save the changes.

Adding the Data Warehouse Icon If desired, copy the shortcut SAS® SRM Adapter for SAP R3 2.4 from the installation directory to the Windows desktop. Double-click the shortcut to launch a new SAS session and start SAS/Warehouse Administrator. Initially presented is an empty desktop folder, named SAS® SRM Adapter for SAP R/3 2.4. A desktop icon must be added to allow access to the Data Warehouse. To add the desktop icon:

1. Right-click in the blank desktop area, then select Add Item → Data Warehouse Environment. The Data Warehouse Environment Properties dialog box opens (Display 2.4).


Display 2.4 Data Warehouse Environment Properties Dialog Box

2. In the Path field, type !root\SRM\SRMDW\DW_Env. 3. Click OK. The desktop now contains an icon for the adapter (Display 2.5).

Display 2.5 Resulting Warehouse Administrator Desktop Folder


Setting Up SAP Logon Details To be able to access a SAP system, a valid logon must be set up and used to sign in. You can set up an automatic logon to the SAP system that executes when you start up the adapter by specifying the logon details in the autoexec.sas file.

Create a New Logon Profile in SAS/ACCESS Interface to R/3 1. To set up the logon details in the adapter, select the SAS/ACCESS to R/3 button at the bottom of the

SAS window (Display 2.6). Double-click the Logon icon.

Display 2.6 Selecting the Logon Process

2. In the Logon to R/3 window (Display 2.7), update the fields by entering values that are relevant to the

SAP system to be accessed.


Display 2.7 Logon to R/3 Window

Profile: User-defined name to identify logon details Client: R/3 client identification number. The client ID must be three numeric

characters with leading zeros. For example, “10” will fail but “010” will work.

User ID: SAP user ID Password: Password that is associated with the SAP user ID Language: Human language in which to display data for R/3 (E=English, D=German,

and so on). The text descriptions and help screens will be presented in the chosen language as long as the language support is installed.

3. Select Advanced. The Advanced Parameters window opens (Display 2.8).


Display 2.8 Advanced Parameters Window

4. Complete the details that are relevant to the SAP system to be accessed by using each of the available tabs.

Tab: General Connection ID: User-defined name of connection Remote: To read R/3 tables into SAS DATA sets in a remote SAS session, the

connection to R/3 has to be established in the remote SAS session. Tab: TCP/IP Host: Specifies the network location of the batch RFC server. The default is

localhost. Port: The TCP/IP port to use for communicating with the batch RFC

server. The default port number is 6993.


Tab: RFC Host: Defines the R/3 server for the batch RFC server to connect to. Destination: A logical name that is used by the sideinfo file. If a destination is set

here, the other fields on the RFC tab will be ignored because the sideinfo file will override them.

Gateway host: The gateway host that is used by the batch RFC server to communicate with the R/3 system. The default value for this field is Host.

Gateway service: The communication gateway service that is used by R/3. System number: The system number that identifies which R/3 system to access if there

is more than one R/3 system that resides on the same host. The default value for this field is 0.

Function: A SAS function to call as part of the R/3 logon process. You can specify the R/3 function module that is used for RFC. The default function is Z_SAS_READ_TABLE_CPIC.

Tab: CPI-C Client: The three-digit R/3 client identification number. Enter a CPI-C client

ID if it is different from the RFC client. User: The R/3 user ID. Enter a CPI-C user ID if it is different from the RFC

user. Password: The R/3 password. Enter your CPI-C password if it is different from

the RFC password. Language: The language for use by the CPI-C logon. The default language is

installation dependent. Destination: The CPI-C destination. The default value is SELF, and must be

defined in the XCOM or TXCOM table of the R/3 system.

5. Click OK to save the changes. 6. Click Save to save the newly created logon profile to the SAS data set SASUSER.R3CONN. All

logon profiles that are set up in this manner are stored in SASUSER.R3CONN. These profiles are then made available from the drop-down list in the Logon to R/3 window.

7. Click OK to log on to the SAP system. The message in Display 2.9 should be displayed if the login was successful.

Display 2.9 Successful Connection Message


Update the autoexec.sas File for Automatic Logon To enable an automatic logon by using the login profile that you created above, you must edit the autoexec.sas file that is located in the installation directory. See “Updates for Automatic Logon” in Appendix A.

Extracting SAP R/3 Metadata The procedure for setting up the R/3 metadata depends on the existing setup:

• If the R/3 metadata already exists (for instance, if it has already been extracted for SAS/ACCESS to R/3 or perhaps if another adapter has already been installed), then the autoexec.sas file should be changed to point to the directory where the metadata has been stored. See instructions under “Updating the Metadata Directory” below.

• If the metadata does not yet exist, then the Wizard to Load Metadata must be run to extract the information. See “Creating R/3 Metadata” below.

Update the Metadata Directory If the R/3 metadata has already been extracted, then to save time and space and also to keep the metadata centralized, simply update the autoexec.sas file to assign the libref R3LIB to the correct directory path. Use Display 2.10 as a guide.

Display 2.10 Updating the autoexec.sas File Metadata Library Assignment

Create R/3 Metadata If the R/3 metadata has not yet been extracted, then it must be created so that the SAS/Warehouse Administrator processes run correctly.


To create the R/3 metadata: 1. Start up the adapter’s SAS/Warehouse Administrator environment and select the SAS/ACCESS to

R/3 button at the bottom of the window. Then double-click the Wizard to Load Metadata icon (Display 2.11).

Display 2.11 Wizard to Load Metadata Icon

2. Select Data Dictionary, and click Next (Display 2.12).


Display 2.12 Select Import Type Window

3. Select the correct connection ID (the default value should be correct), and click Next (Display 2.13).

Display 2.13 Selecting a Connection


4. Leaving the default in the Select the Libref field will create the metadata in the R3LIB directory that

was assigned in the autoexec.sas file. If you need to change this libref, then click the Define button to assign a new libref. (Remember to update the autoexec.sas file to assign the chosen directory.) Otherwise, click Next (Display 2.14).

Display 2.14 Selecting a Metadata Destination

5. To receive the full metadata content, accept the defaults and click Options (Display 2.15).


Display 2.15 Selecting the Metadata

6. Clear the Exclude structures, maint. and help views and Read fields metadata only for extracted table metadata options (Display 2.16).

Display 2.16 Clearing Options

7. Click OK to close the Options dialog box, then click Next. 8. If desired, specify the name of a file in which to save a copy of the SAS code to run the metadata

extraction (Display 2.17). Click Next.


Display 2.17 Selecting SAS Program File

9. Click Finish to start the metadata extraction (Display 2.18). Note that the metadata extraction can take several hours to complete.


Display 2.18 Starting the Metadata Extraction

Setting Up the RFC Listener Requirements

The RFC Listener The RFC Listener is used during the execution of the BKPF/BSEG Accounting Document job. In the absence of an SAP server-side join within Version 8 of SAS, this process imitates a server-side join of the tables BKPF and BSEG. The listener process involves invoking program SASRFCEX on the machine that is requesting the data from SAP. The SASRFCEX program then waits for calls to the ABAP program (via the ABAP function Z_SAS_READ_TABLE_JOIN) to retrieve data and write it to an external file. The listener is automatically started and stopped by the SAS/Warehouse Administrator job that executes the macros %START_LISTENER and %KILL_LISTENER, respectively. There are several components that are needed for this process to function correctly:

• An SAP destination, of type “registration,” must be defined. This destination specifies the communication with the program SASRFCEX.

• A CMD or shell script must be created to invoke the listener program. • An output file for the returned data must be specified.

Creating an RFC Destination To create an RFC destination group:

1. If you have not already done so, log on to the SAP R/3 GUI. 2. On the command line, type SM59. The Display and Maintain RFC Destinations window opens

(Display 3.1).

C H A P T E R

3

Chapter 3: Setting Up the RFC Listener Requirements 29


4. In the RFC Destination window, fill in the fields as follows:

• RFC destination: SRMADLSNR • Connection type: T • Description: SRM Adapter listener program

5. Press ENTER. The RFC Destination SRMADLSNR window opens (Display 3.3).


Display 3.3 RFC Destination SRMADLSNR Window

6. In the RFC Destination SRMADLSNR window, click Registration. Type sasrfcex.srmadlsnr in the

Program ID field.


8. Click the Back button ( ) to exit. If desired, you can now log off from the SAP R/3 GUI.

Updating the CMD or Shell Scripts The SRM_sa_2.4 folder contains two .cmd files. The sas_rfcexec.cmd file invokes the listener; the kill_listener.cmd file stops the listener on process completion. Both of these files must be updated to reflect the settings at your site.

Chapter 3: Setting Up the RFC Listener Requirements 31

Update sas_rfcexec.cmd

Display 3.4 sas_rfcexec.cmd File

The sas_rfcexec.cmd file must be updated as follows: PATH_TO_SAS_RFCEXEC “<installpath>\SRM_sa_2.4\v8\r3addins\win\”

(if installation is not on Windows, change the last folder name to reflect the correct operating environment).

PROG_ID Must be set to the same name that was chosen for Program ID in the previous section.

GWHOST The full gateway host ID that is used by the batch RFC server to communicate with the R/3 system.

GWSERV The communication gateway service that is used by R/3.

Update kill_listener.cmd

Display 3.5 kill_listener.cmd File


The kill_listener.cmd file must be updated as follows: PATH_TO_SAS_RFCEXEC “<installpath>\SRM_sa_2.4\v8\r3addins\win\”

(if installation is not on Windows, change the last folder name to reflect the correct operating environment).

Editing the autoexec.sas File The autoexec.sas file defines several macro variables that are related to this server-side join process. See “Updates for Server-Side Join Processing” in Appendix A for details.

Integrating with SAS Supplier Relationship Management

Formats The adapter, by default, creates two format catalogs. The first is for language-dependent texts (material descriptions, months, days, and so on). The second is for language-independent formats. The language-dependent catalog is named FMT, suffixed with the relevant SAP language code. For example, the English language formats are created in the catalog FMTE, the German language formats in FMTD, the French language formats in FMTF, and so on.

Update SAS Supplier Relationship Management Properties for Language Formats From the SAS Supplier Relationship Management root directory, locate the pv.properties file in the SpendAnalysis/WEB-INF directory. Open this file in a text editor. Locate the line that contains SAS.Command= and update with a format search specification, as in Display 4.1. The format catalog that is listed first should be changed to reflect the desired language format catalog.

Display 4.1 Updating the Format Search Chain

Save and close the pv.properties file.

C H A P T E R

4

Recommended Reading

Recommended Reading Here is the recommended reading list for this title:

• SAS/ACCESS Interface to R/3: User’s Guide • SAS Supplier Relationship Management Adapter for SAP R/3: Implementation Guide • SAS/Warehouse Administrator User's Guide

For a complete list of SAS publications, see the current SAS Publishing Catalog. To order the most current publications or to receive a free copy of the catalog, contact a SAS representative at SAS Publishing Sales SAS Campus Drive Cary, NC 27513 Telephone: (800) 727-3228 Fax: (919) 677-8166 E-mail: [email protected] Web address: support.sas.com/publishing * For other SAS Institute business, call (919) 677-8000. Customers outside the United States should contact their local SAS office.

A P P E N D I X

B

Your Turn

If you have comments or suggestions about SAS Supplier Relationship Management Adapter for SAP R/3: Implementation Guide, please send them to us on a photocopy of this page or send us electronic mail.

For comments about this book, please return the photocopy to

SAS Publishing SAS Campus Drive Cary, NC 27513 E-mail: [email protected]

For suggestions about the software, please return the photocopy to

SAS Institute Inc. Technical Support Division SAS Campus Drive Cary, NC 27513 E-mail: [email protected]