Ariba Buyer SAP Integration Guide

Ariba Buyer SAP
Integration Guide
VERSION 7.0.5
MAY 2001
Copyright © 1996-2001 Ariba, Inc.
Ariba and the Ariba logo are registered trademarks of Ariba, Inc. Ariba B2B Commerce Platform,
Ariba Buyer, Ariba Live, Ariba Marketplace, Ariba Network, Ariba Network Connect Program ,
MarketMaker.Ariba, Ariba Network Connectors , Ariba Reach , Ariba Dynamic Trade, Ariba
Commerce Services Network, buyer.ariba, RFQBuilder, Ariba Sourcing, SmartMatch,
supplier.ariba, Ariba SupplierLive, ECTranslator, ECTransport, Walkup UI, Supplier Advisor and
Making the Net Work for B2B are trademarks or servicemarks of Ariba, Inc. Ariba Proprietary and
Confidential. All rights reserved. Patents pending.
All other brand or product names may be trademarks or registered trademarks of their respective
companies or organizations.
ALL LICENSES OF ARIBA SOFTWARE PROGRAMS AND RELATED DOCUMENTATION

("PROGRAMS") ARE SUBJECT TO ANY EXPORT LAWS, REGULATIONS ORDERS OR
OTHER RESTRICTIONS IMPOSED BY THE UNITED STATES OF AMERICA OR BY ANY
OTHER GOVERNMENT ENTITY ON THE PROGRAMS OR INFORMATION RELATING
THERETO. A LICENSEE OF ANY PROGRAM WILL NOT IMPORT, EXPORT, OR ALLOW
THE EXPORT OR REEXPORT, DIRECTLY OR INDIRECTLY, OF THE PROGRAM (OR
TECHNICAL DATA OR OTHER INFORMATION RELATED THERETO) OR ANY DIRECT
PRODUCT THEREOF, TO ANY COUNTRY TO WHICH SUCH IMPORT, EXPORT, OR
REEXPORT IS RESTRICTED OR PROHIBITED, OR AS TO WHICH SUCH GOVERNMENT
OR ANY AGENCY THEREOF REQUIRES ANY EXPORT LICENSE OR OTHER
GOVERNMENTAL APPROVAL AT THE TIME OF IMPORT, EXPORT OR REEXPORT,
WITHOUT FIRST OBTAINING SUCH APPROVAL.
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Document Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Shared Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Ariba Buyer Documentation Set . . . . . . . . . . . . . . . . . . . . . . . . . 10
Typographic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Ariba Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 1
SAP Integration Architecture . . . . . . . . . . . . . . . . . . . . . . 15
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Integration Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Data Pulls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Scheduled Pulls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Purchase Order Pushes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Receipt Pushes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Integration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Pushing BAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
BAPI Push Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Supported SAP Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Customer Development Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Date Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Chapter 2
Ariba Buyer Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Before Running TIBCO initdb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Install and Configure Ariba Buyer . . . . . . . . . . . . . . . . . . . . . . . 24
Edit SAPAdapter_AllRFCs_RFCInboundConfig.xml . . . . . . . . 27
Edit SAPAdapteridocIdocPublisherConfig.xml . . . . . . . . . . . . . 29
Ariba Buyer SAP Integration Guide iii

Table of Contents
After Running TIBCO initdb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Loading SAP Version Specific Data into the Repository . . . . . . 31
Regenerating Worksheet Mappers . . . . . . . . . . . . . . . . . . . . . . . . 32
Starting the TIB/R3 Adapter for Each Partition . . . . . . . . . . . . . 32
Starting the TIB/R3 Adapter for IDOC Integration. . . . . . . . . . . 33
SAP Password Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 3
SAP Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Setting Up Ariba Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
CPIC User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Dialog Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Transport Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Time-out Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Checking Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Bank Selling Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Blank Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Vendor Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Vendor ERS Tax Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Validation on Catalog Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Incremental Real Time Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Global Company Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Receiving Tolerances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Receiving System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
ERP Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Testing Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Chapter 4
Configuring Pulls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Pulling Additional Fields Into Ariba Buyer . . . . . . . . . . . . . . . . . . . . 46
Extension Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Adding Fields to Extension Structures . . . . . . . . . . . . . . . . . . . . 49
Extension Structure Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Pulling New Tables Into Ariba . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Declaring Local Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Adding Custom RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Static Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
ABAP Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Post Hook Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
iv Ariba Buyer SAP Integration Guide 705en_us2001.5.12

Table of Contents
Example RFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Chapter 5
Configuring Pushes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Push Extension Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Screen Field Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
What Field Mappings Do . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Data Push Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Sources of Data for Push Tables . . . . . . . . . . . . . . . . . . . . . . . . . 70
Mapping Fields for Orders or Receipts. . . . . . . . . . . . . . . . . . . . . . . . 71
Finding the Screen Field to Map . . . . . . . . . . . . . . . . . . . . . . . . . 71
Finding the Source Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Editing the Extension Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Changing and Removing Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Filtering and Customer Exit Functions . . . . . . . . . . . . . . . . . . . . . . . . 74
Unsupported Push Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
BAPIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Additional Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Additional Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Chapter 6
Parameter Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 77
ZARIBTVARV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Default Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Incremental Loading Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 81
Minority Vendor Head Offices . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Currency Conversion Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Monetary Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Debugging Pushes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Internal Order Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Purchase Order Document Types . . . . . . . . . . . . . . . . . . . . . . . . 84
Vendor Pull Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . 85
Using General Ledger Balance Sheet Accounts . . . . . . . . . . . . . 85
Real Time ALE/IDOC Partition Loading . . . . . . . . . . . . . . . . . . 86
Duplicate PO Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Ariba Buyer SAP Integration Guide v

Table of Contents
Chapter 7
Account Assignment Categories . . . . . . . . . . . . . . . . . . . 87
What Are Account Assignment Categories? . . . . . . . . . . . . . . . . . . . 87
Ariba Buyer Account Assignment Category Pulls . . . . . . . . . . . 88
Displaying Fields and Requiring User Input . . . . . . . . . . . . . . . . . . . 88
SAP Accounting Field Configuration . . . . . . . . . . . . . . . . . . . . . 89
Ariba Buyer Accounting Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Field Status Group Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Viewing Field Status Group Strings . . . . . . . . . . . . . . . . . . . . . . 94
Using Account Assignment Category Pulls . . . . . . . . . . . . . . . . . . . . 94
Chapter 8
Real Time Integrations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Configuring ALE/IDOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Installing ALE/IDOC Transports. . . . . . . . . . . . . . . . . . . . . . . . 102
Installing Ariba Buyer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Ariba Buyer Repository and Worksheet Configuration . . . . . . . . . . 103
Configuring Partition Names in Worksheets . . . . . . . . . . . . . . . 104
Worksheets and Executing ALE/IDOCs . . . . . . . . . . . . . . . . . . 105
Ariba Buyer ALE/IDOC Configuration . . . . . . . . . . . . . . . . . . . . . . 105
Defining Logical Systems for Partitions . . . . . . . . . . . . . . . . . . 106
Defining a Distribution Model . . . . . . . . . . . . . . . . . . . . . . . . . 106
Defining a Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Creating an RFC Destination for ALE/IDOC . . . . . . . . . . . . . . 109
Defining a Partner Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Ariba Buyer Object Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 113
ABAP/4 Configuration Classes . . . . . . . . . . . . . . . . . . . . . . . . . 114
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Chapter 9
Release Authorizations Pulls . . . . . . . . . . . . . . . . . . . . . 117
Release Authorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Conditions, Strategies, Indicators, and Codes . . . . . . . . . . . . . . 118
Profiles and Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
ZAF7 Ariba Buyer Release Assumptions. . . . . . . . . . . . . . . . . . . . . 119
Release Authorization in Ariba Buyer . . . . . . . . . . . . . . . . . . . . . . . 120
Approval Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Approval Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
vi Ariba Buyer SAP Integration Guide 705en_us2001.5.12

Table of Contents
Release Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Release RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Chapter 10
Error Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Failures Pushing to SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Failures pushing Purchase Orders to TIB/MessageBroker . . . . 125
Failures Pushing Purchase Orders or Receipts to SAP . . . . . . . 126
Pulling Failures from CSV files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Failure Pulling Multiple Entries From CommodityExportMap.CSV
127
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Debugging Pushes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Ariba Buyer SAP Integration Guide vii

Table of Contents
viii Ariba Buyer SAP Integration Guide 705en_us2001.5.12

Preface
Preface
Preface
The Ariba Buyer SAP Integration Guide provides the information for configuring
SAP and Ariba Buyer server to exchange information.
This document is for system administrators and personnel who install Ariba Buyer,
TIB/MessageBroker, and set up the integration with SAP. The information assumes
the presence of an experienced SAP BASIS (database administrator.)
Preface
Document Structure
This document includes the following chapters:
• Chapter 1, “SAP Integration Architecture” explains the items that make integration
between Ariba Buyer and SAP possible, including an overview of integration
events, building block data, BAPI and RFC integrations, customer development
classes, and initialization steps.
Preface
• Chapter 2, “Ariba Buyer Setup” describes the tasks and items you must complete
within Ariba Buyer before and after TIBCO database initialization.
• Chapter 3, “SAP Setup” describes the tasks you must complete on SAP to integrate
with Ariba Buyer.
• Chapter 4, “Configuring Pulls” describes the SAP system components that allow
you to pull new fields, pull new tables, filter data, and create your own Ariba Buyer
RFCs.
Preface
• Chapter 5, “Configuring Pushes” describes how to push extra fields to SAP through
extension structures, screen field mappings, filtering, and parameters.
• Chapter 6, “Parameter Configuration” describes the ZARIBTVARV parameter table

and the settings it provides to configure Ariba Buyer RFCs.
• Chapter 7, “Account Assignment Categories” describes how Ariba Buyer pulls

account assignment categories and field status strings so you can perform your own
Preface
configurations.
Ariba Buyer SAP Integration Guide 9

Related Documentation Preface
• Chapter 8, “Real Time Integrations” describes how to configure SAP to share

vendor, general ledger, and cost center data with Ariba Buyer in a real time,
incremental fashion through ALE/IDOC configuration.
• Chapter 9, “Release Authorizations Pulls” describes a scenario in which you can

pull release authorizations into Ariba Buyer to use in the approval flow.
• Chapter 10, “Error Recovery” describes how to deal with integration error
conditions and troubleshooting.
Related Documentation
The Ariba Buyer documentation set includes a set of reference documentation (shared
with other Ariba products), and a set of documentation specific to Ariba Buyer. This
section describes the documents that are appropriate for customers of Ariba Buyer.
Shared Documentation Set

The following documents include reference information that is shared between Ariba
Buyer and other Ariba products:
Ariba Catalog Format Reference

Provides information on cXML and CIF, which are the two catalog
formats used in the Ariba product suite. This document is valuable
both for suppliers who create catalogs and buyers who access those
catalogs.
Ariba Buyer Documentation Set

The Ariba Buyer documentation set includes the following documents:
Ariba Buyer Release Guide

Describes new features and known limitations of an Ariba Buyer
release.
Ariba Buyer Installation Guide

Describes how to install Ariba Buyer. Ariba provides versions of
the installation guide for each supported OS platform: AIX, HP-
UX, Solaris, and Windows NT.
10 Ariba Buyer SAP Integration Guide 705en_us2001.5.12

Preface Related Documentation
Preface
Ariba Buyer Database Configuration Guide
Describes how to configure a Microsoft SQL Server, Oracle, or
IBM DB2 UDB database installation for use with Ariba Buyer.
Ariba Buyer Web Server Configuration Guide

Describes how to configure your Web server for use with Ariba
Buyer: how to set up CGI script access, directory aliases,
permissions, and other required configuration.
Preface
Introduction to Ariba Buyer
Provides a high-level overview of Ariba Buyer, including its major
components, architecture, and enterprise integration framework.
Ariba Buyer Configuration Overview

Provides an overview of the configuration and customization
process. It describes the kinds of changes you can make during the
configuration process and introduces the data files that define a
configuration.
Preface
Ariba Buyer Configuration Guide
Describes how to load basic data such as users, passwords,
currencies, and countries, into Ariba Buyer. The data described in
this document is data used both by the Procurement module and the
Travel and Expenses module.
Customizing Ariba Buyer

Describes how to customize and extend the Ariba Buyer user
Preface
interface.
Ariba Buyer eForms Tutorial

Describes how to create your own custom forms in Ariba Buyer.
Ariba Buyer Procurement Guide

Describes how to set up and configure Ariba Buyer’s Procurement
features, such as ordering, receiving, and purchasing cards.
Preface
Ariba Buyer Catalog Management Guide
Describes how to set up your Ariba Buyer product catalog with
catalog items from suppliers.
Ariba Buyer TIBCO Configuration Guide

Describes how to install, configure, and use Tibco to exchange data
with Ariba Buyer.
Preface

Related Documentation Preface
Ariba Buyer PeopleSoft Integration Guide, Ariba Buyer SAP Integration Guide,
and Ariba Buyer Oracle Financials Integration Guide
Describe implementation details specific to particular underlying
ERP systems.
Ariba Buyer Administration Guide

Describes how to do ongoing system administration for Ariba
Buyer.
Ariba Buyer API Guide

Describes how to extend Ariba Buyer with custom Java classes.
Ariba Buyer Approval Rules Guide

Describes the role rules play in the approval process, the different
approvable document types, and how to write your own approval
rules.
Ariba Query API Guide

Describes how to use the Ariba Query API to access objects in the
Ariba database.
Ariba Buyer Travel and Expenses Guide

Describes how to use the Ariba Buyer Travel and Expenses module
to manage expense reports, travel profiles, and travel
authorizations.
Ariba Buyer Configuration Reference Guide

Provides reference information on all scheduled tasks, integration
events, and parameters used in Ariba Buyer. This book describes
settings used during the configuration phase.
Ariba Buyer Customization Reference Guide

Provides reference information on the file formats, XML
configuration DTDs, and library components that are used in Ariba
Buyer. This book describes options available during the
customization phase.
Ariba Buyer Master Glossary

Provides definitions for Ariba Buyer terminology.
Ariba Buyer ASP Edition Implementation Guide

Describes how to implement Ariba Buyer Application Service
Provider (ASP) Edition. Ariba Buyer ASP Edition allows Ariba
Partners to offer a hosted version of Ariba Buyer.

Preface Typographic Conventions
Preface
Ariba Buyer Troubleshooting Guide
Describes common problems and their solutions, the
troubleshooting process, and other information that is helpful in
solving problems with Ariba Buyer.
Typographic Conventions
Preface
The following table describes the typographic conventions used in this document:
Typeface or
Meaning Example
Symbol
<AaBbCc123> Text you need to change is http://<yourServer>:<HTTPServerPort>/inspector
italicized, and appears between
angle brackets.
AaBbCc123 The names of user interface Choose Edit from the File menu.
Preface
controls, menus, and menu
items.
AaBbCc123 Files and directory names, There is one line in ReportMeta.csv for each report
parameters, fields in CSV files, in the system.
command lines, and code
examples.
AaBbCc123 The names of books. For more information, see Ariba Buyer
Configuration Overview.
Preface
Ariba Technical Support
For assistance with Ariba Buyer, Ariba Technical Support is available by phone, e-
mail, or over the Web. For information on how to contact Ariba Buyer Technical
Support, see the Ariba Technical Support Website or send e-mail to
[email protected].
Preface
The Ariba Technical Support Website is:
http://connect.ariba.com
Preface

Ariba Technical Support Preface

Chapter 1
SAP Integration Architecture
This chapter provides an introduction to the way Ariba Buyer integrates with SAP
systems through a TIBCO integration channel. Before you use this document, you
should be familiar with the TIBCO integration channel information contained in the
Ariba Buyer TIBCO Configuration Guide.
Overview
Ariba Buyer performs three integration tasks with SAP:
• Pulling data from SAP systems. Ariba Buyer pulls in basic SAP data, like accounts
and suppliers, and uses that data to populate the choosers in Ariba Buyer.
• Pushing Ariba Buyer purchase orders to SAP.
• Pushing Ariba Buyer receipts to SAP.
To pull data, Ariba Buyer runs an integration event. The integration event uses the
instructions in its associated TIB/MessageBroker worksheet to perform the data pull.
For most data pulls, TIB/MessageBroker sends the worksheet instructions to the
TIB/TIB/R3 Adapter for SAP. The adapter communicates with SAP through RFCs
and BAPIs to load the data into SAP. To pull incremental cost center, GL account, and
vendor information, the TIB/Message Broker uses the SAP/IDOC adapter to pull the
data.
To push purchase orders or receipts to SAP, Ariba Buyer runs an integration event.
The integration event uses instructions in its associated TIB/MessageBroker work-
sheet to send the purchase order or receipt information to the TIB/TIB/R3 Adapter for
SAP. The adapter communicates with SAP through RFCs and BAPIs to load the data
into SAP.

Overview Chapter 1 SAP Integration Architecture
The following diagram illustrates the data flow in an Ariba Buyer/SAP integration
across the TIBCO integration channel.
• TIB/MessageBroker—Your Ariba Buyer default configuration provides worksheets

that define mappings and data transformations between Ariba Buyer objects and
SAP data. These worksheets communicate with SAP Adapter through RPC Clients.
• TIB/MessageBroker Worksheets—The worksheets define the mappings and data

transformations between Ariba Buyer and SAP. The worksheets are stored in the
TIB/Repository.
• TIB/R3 Adapter—Your default configuration for SAP uses the TIB/R3 Adapter to
share data between TIBCO applications and your SAP system. The TIB/R3
Adapter communicates directly with Ariba Buyer RFCs and the RPC clients in
worksheets.
• Ariba Buyer RFCs—You must install and configure RFCs from Ariba development
classes on your SAP system. These RFCs query and refine the data Ariba Buyer
pulls and insert the data Ariba Buyer pushes.

Chapter 1 SAP Integration Architecture Integration Events
• SAP IDoc Adapter—The SAP IDoc adapter is an optional component used for
pulling incremental cost center, GL account, and vendor information from SAP.
SAP R/3 creates an IDoc and passes it to the SAP IDoc Adapter. Using
TIB/MessageBroker worksheets, the SAP IDoc adapter maps the IDoc to Ariba
Buyer objects.
In addition to pulling data from SAP, an Ariba Buyer SAP partition also pulls data
from CSV files for information related to Ariba Buyer such as adjustment types and
commodity code mapping information. This information, together with the
information pulled from SAP is used to create SAP-valid purchase orders.
Integration Events
An integration table, integrationEvent.table, describes all the data exchanges for partition.
Each entry in the table, an integration event, tells Ariba Buyer how to push or pull a
unit of common information, such as how to pull addresses or vendors or how to push
purchase orders or goods receipts. You can run pushes or pulls for a partition
manually through the Enterprise Manager, automatically as a scheduled task, or as a
part of initialization process when you first create the Ariba Buyer database.
For more information on integration events, refer to the Ariba Buyer TIBCO
Configuration Guide. For a description of each SAP-related integration event, refer to
the Ariba Buyer Configuration Reference Guide.
Data Pulls
Data pull integration events can run on a schedule as set in the integration event table
entry, or can be run manually from the Enterprise Manager.
Scheduled Pulls
Each data pull integration event runs on a separate schedule, so you can set up
different schedules for pulling different sorts of information. For example, you might
want to pull suppliers more frequently than currency conversions, if you know the
supplier information changes more often on the SAP side. The following events occur
when Ariba Buyer pulls data from SAP:

Purchase Order Pushes Chapter 1 SAP Integration Architecture
1. Each of the SAP data pulls run on a regular schedule, according to the way
you define integration table entries. Each time a pull integration table entry
runs, it communicates with a TIB/MessageBroker worksheet.
2. The TIB/MessageBroker worksheet sends its instructions to the TIB/R3

Adapter.
3. The TIB/R3 Adapter communicates with the Ariba Buyer RFCs on your
SAP system to gather the requested information.
4. The RFCs query and process the information and send it through the TIB/R3
Adapter to the worksheet.
5. The worksheet transforms and maps the data into the Ariba Buyer object
model.
6. Ariba Buyer uses metadata XML mappings to process the data from the
worksheet and incorporate it into valid Ariba Buyer objects.
Purchase Order Pushes

A purchase order is pushed to SAP as soon as it is created in Ariba Buyer (that is,
when the requisition is fully approved).
The following steps explain how a purchase order push integration event works:
1. When a requisition becomes fully approved in Ariba Buyer, the Ariba order
processor converts the requisition into one or more orders and then checks to
see if any or all of those orders are destined for the SAP system.
2. If the order is destined for SAP, Ariba Buyer sends the order to TIB/Message
Broker purchase order push worksheet.
3. The purchase order push worksheet transforms the data into the format
required by the RFC and then sends the data to Ariba Buyer push RFCs
through the TIB/R3 Adapter.
4. Ariba Buyer RFCs process the data and insert it in purchase order creation
screens in SAP.
5. The RFC returns purchase order details, including the purchase order
number. If an error occurs, the error information is returned.

Chapter 1 SAP Integration Architecture Receipt Pushes
Receipt Pushes
Receipt push integration events can run on a schedule as set in the integration event
table entry, or can be run manually from the Enterprise Manager.
The following steps explain how a receipt push integration event works:
1. When an item is received in Ariba Buyer, a receipt object instance is created.
2. When the scheduled receipt push integration event runs, Ariba Buyer sends
the receipt object to the TIB/Message Broker receipt push worksheet.
3. The worksheet transforms the data into the format required by the RFC and
then sends the data to Ariba Buyer receipt push RFCs through the TIB/R3
Adapter.
4. Ariba Buyer RFCs process the data and insert it in receipt creation screens in
SAP.
5. The RFC returns a receipt line number. If an error occurs, it returns the error
information.
Integration Data
Ariba Buyer pulls only the data it needs to create properly formed purchase orders,
and receiving information for SAP.
Ariba Buyer pulls the following data from SAP:

• Account categories
• Accounting field display status
• Language specific names for data pulls
• Assets
• Cost centers
• Local and global company codes
• General ledgers
• Internal orders
• WBS elements

Pushing BAPI Chapter 1 SAP Integration Architecture
• Currency conversion rates

• Material groups
• Minority vendors
• Plants
• Purchasing organizations
• Purchasing groups
• Status of pushed purchase orders and receipts
• Vendors
• Tax codes
Optionally, you can also pull the following data from SAP with some configuration
on your part:
• Users
• Release authorizations
• User release authority
The Ariba Buyer Configuration Guide discusses how to configure this other data. For
more information about all pulls and integration events related to SAP, refer to the
Ariba Buyer Configuration Reference Guide.
Pushing BAPI
Your default configuration of Ariba Buyer uses RFCs to push data into SAP.
However, SAP does support another kind of interface called BAPI (Business
Application Programming Interface).
SAP offers a BAPI interface to push purchase order data, but not for receipts. Rather
than integrating through procedural RFC code, the BAPI integration uses an API and
an underlying mechanism which vaguely resembles the encapsulation of object
oriented languages.
Ariba Buyer supports BAPI data pushes for purchase orders only for customers using
the 4.0B version or higher of SAP. You default configuration uses RFC for data
pushes, because this method works with more versions of SAP.

Chapter 1 SAP Integration Architecture Supported SAP Versions
BAPI Push Limitations

The BAPI integration with Ariba Buyer does not provide the following functionality.
• Pushing ERS tax code information.
• Pushing service line items for version 4.0B.
• Split accounting for service lineitems.
• Pushing the title of purchase orders to SAP.
• Support for the “deliver to” address in an Ariba Buyer purchase order. In many
circumstances, the plant information provides this information.
• Support for the Ariba Buyer push field mapping mechanism. If you need to add
Ariba Buyer extrinsic fields to BAPI objects, you must do so within the appropriate
TIB/MessageBroker worksheets instead of within the mapping structures.
In addition, the BAPI method requires that you create purchase orders from within
Ariba Buyer in the same language your vendors use. If you do not use Ariba Buyer to
create a purchase order in the same language as a vendor, the vendor cannot read it.
Supported SAP Versions

Ariba Buyer integrates with the following SAP versions:
• 3.1I
• 4.0B
• 4.5B
• 4.6B
If you use versions 4.0B, 4.5B, or 4.6B with Ariba Buyer, you should be aware of the
following:
• The BAPI for purchase orders does not support service line items.
• 4.0B, 4.5B, and 4.6B share the same worksheet, PurchaseOrderAdapterBAPI.

Customer Development Classes Chapter 1 SAP Integration Architecture
Customer Development Classes

Your Ariba Buyer transports offer the following development classes that you can use
to safely configure and modify your integration on SAP:
• ZARC—Ariba Buyer customer development class
• ZATC—Ariba Buyer TIBCO incremental loading customer development class
Date Formatting
Ariba Buyer formats dates to have four digit years. Ariba Buyer cannot know that the
dates you provide from an ERP system, flat file, database, or other external source are
accurate and properly formatted. If you provide accurate and properly formatted dates
to Ariba Buyer, the corresponding dates which Ariba Buyer pushes, or exports, into
your ERP system or other data destination will also be accurate.
Ariba Buyer imports, or pulls, all dates from external ERP systems and data sources
as strings, and depends upon the java.text.DateFormat class within the Sun JDK to
format these strings into Java date objects. See Sun’s API Java documentation and the
Sun Java source code for more information about how to format ERP and external
data source dates as strings for the java.text.DateFormat class.

Chapter 2
Ariba Buyer Setup
This chapter presents the tasks you must complete to configure Ariba Buyer
mechanisms for integration with SAP.
The basic process for configuring Ariba Buyer for an SAP integration is:
1. Perform the tasks described in, “Before Running TIBCO initdb” on page 24.
2. Run initdb -inittibco.

This command creates all the TIBCO related items you need to prepare for
loading data into Ariba Buyer.
For instructions on running this command, refer to:
• Ariba Buyer TIBCO Configuration Guide
3. Perform the tasks described in, “After Running TIBCO initdb” on page 30.
4. Run initdb -initdb.

This option pulls data into Ariba Buyer from SAP and CSV files.
For instructions on running this command, refer to:
• Ariba Buyer Installation Guide for your system

Before Running TIBCO initdb Chapter 2 Ariba Buyer Setup
Before Running TIBCO initdb

Before you initialize the TIBCO database, perform the following:
• Install and configure Ariba Buyer.
• Edit SAPAdapter_AllRFCs_RFCInboundConfig.xml.
• Edit SAPAdapteridocIdocPublisherConfig.xml.
If you have already run TIBCO initdb options, you can perform the tasks in this
section, and then run them again.
Install and Configure Ariba Buyer

When you run the configure script during installation and implementation, consider
the following:
• Use the Demo Version

Use the “Demo Version” when running the configure option. This option creates all
of the CSV source files you need for an SAP partition.
If you choose the “Basic Version,” you won’t have any CSV files for your
implementation.
• Verify configuration file information

Running the configure script creates entries in the following files that you should
review for accuracy:
• Parameters.table
• ConnectionInfo.table
Note: If you make changes to these files, you should run the following
command for Ariba Buyer to implement your changes throughout your
configuration:
runtibco -updateconfigfiles

Chapter 2 Ariba Buyer Setup Before Running TIBCO initdb
Parameters.table and System.SAPConnections
There are many settings in the parameters.table file that you should verify, but those
most relevant to SAP integrations describe connection information to your SAP
system. The SAPConnections parameters provide the information Ariba Buyer needs to
communicate through TIB/ActiveEnterprise products with your SAP systems.
You must create a set of SAPConnections parameters for each SAP instance with which
Ariba Buyer communicates. This document represents the unique instance name of
your destination SAP system as <SAPInstanceName>. For additional information on
these parameters, refer to the Ariba Buyer Installation Guide for your OS system.
Table 1. SAPConnections Parameters
Parameter Description
System.SAPConnections.<SAPInstanceName>.ClientID This parameter defines the client
identification number for the SAP
instance.
System.SAPConnections.<SAPInstanceName>.Destination This parameter defines the destination
SAP instance name.
System.SAPConnections.<SAPInstanceName>.SAPGateway This parameter represents the gateway
for the instance.
System.SAPConnections.<SAPInstanceName>.SAPGatewayService This parameter represents the gateway
service for the instance.
System.SAPConnections.<SAPInstanceName>.SAPHost This parameter represents your SAP
host name for the instance.
System.SAPConnections.<SAPInstanceName>.SAPLanguage This parameter sets the default
language for the instance according to
SAP’s abbreviations.
System.SAPConnections.<SAPInstanceName>.SAPPassword This parameter sets the password for
connecting to the instance.
System.SAPConnections.<SAPInstanceName>.SAPSystemNumber This parameter represents the system
number of the SAP system for the
instance.
System.SAPConnections.<SAPInstanceName>.SAPUser This parameter defines the user that
Ariba Buyer uses to connect to the
instance.
System.SAPConnections.<SAPInstanceName>.SetTrace This parameter determines whether or
not the connection uses tracing. Set the
parameter to 0 to turn it off, to 1 to turn it
on. The default is 0.

Configuring for Multiple Partitions
If you are using multiple SAP partions for the same SAP variant, you must uniquely
identify each partion in the SAPConnections parameter in the parameters.table file. For
example:
SAPConnections = {
ASH = {
ClientID = 800;
Destination = ASH;
SAPGateway = sapoak;
SAPGatewayService = sapgw01;
SAPHost = sapoak;
SAPLanguage = E;
SAPPassword = mssql;
SAPSystemNumber = 01;
SAPUser = ariba;
SetTrace = 0;
};
ELM = {
ClientID = 800;
Destination = ELM;
SAPGateway = sapelm;
SAPGatewayService = sapgw00;
SAPHost = sapelm;
SAPLanguage = E;
SAPPassword = mssql;
SAPSystemNumber = 00;
SAPUser = ariba;
SetTrace = 0;
ConnectionInfo.table
The connectionInfo.table file defines external connections to databases for integration

events. After running the configure script, verify that any SAP-related information is
correct.
For additional information on the connectionInfo.table file, refer to the Ariba Buyer
TIBCO Configuration Guide.
Specifying the Locale
If your SAP configuration uses a default language other than US English, you use
System.Integration.Channels.Tibco.SAPAdapterLocale to specify this language. Ariba Buyer
passes the value you specify for SAPAdapterLocale to the R/3 adapter, as the setlocale
parameter.

For example:
Application = {
Integration = {
Channels = {
Tibco = {
SAPAdapterLocale = {
NT=Japanese_Japan.932;
HPUX=ja_JP.SJIS;
};
};
};
};
};
For more information on the setlocale options, see SAP’s R/3 documentation.
Edit SAPAdapter_AllRFCs_RFCInboundConfig.xml
SAPAdapter_AllRFCs_RFCInboundConfig.xml is a file that defines connection information
for your TIB/R3 Adapter.
Ariba Buyer stores a default configuration of inbound RFC information in the

following partition specific locations within your Ariba Buyer installation directory:
~/config/variants/<variant>/partitions/<partition>/tibco/adapter/sap/config/SAPAdapter_AllRFCs_RFCInboundConfig.xml
This section presents:
• Client connection pool tags
• Client tags
• Sample client connection pools
• Configuration for connection retries
• Configurations for multiple partitions
Client Connection Pools
There are a group of settings within a <clientConnectionPool> tag that you must verify
and edit. Each <clientConnectionPool> describes an SAP gateway and application server.

You must provide or verify the following <clientConnectionPool> attributes:
• systemNumber—the system number
• appServer—the application server
• gatewayHost—the gateway host
• gatewayService—the gateway service
Clients
Each <clientConnectionPool> contains one or more <client> tags that define other
connection information.
You must provide or verify the following <client> tag attributes:
• number—the client number
• userName—the Ariba Buyer CPIC user name for integrations
• password—the Ariba Buyer CPIC user password for integrations
• language—the default SAP language code for the Ariba Buyer CPIC user
You should verify or provide the following information in this file.
Sample <clientConnectionPool> Entry
The following text presents a sample <clientConnectionPool> entry for connecting to one
SAP machine. The attributes that you must create, edit, or verify appear in bold:
<SAPAdapter instanceId="SAInboundRFC.psap">
<deployment name="SAPAdapterDeployment">
<connectionManager name="RFCConnectionManager">
<clientConnectionPool
name="RFCClientConnectionPool"
destination="TIB"
maxConnections="1"
systemNumber="00"
appServer="sap"
gatewayHost="sap"
gatewayService="sapgw00"
defaultClient="CLNT001"
>
<client
name="CLNT001"

number="800"
userName="ariba"
password="ariba">
language="EN"
</client>
</clientConnectionPool>
</connectionManager>
Using the <clientConnectionPool> Entry for Connection Retries
Should a SAP adapter disconnect from SAP R/3, specify three parameters in the
<clientConnectionPool> entry to enable connection retries.
• maxAttempts—Specifies the SAP adapter’s maximum number of SAP reconnection

attempts. The default is 3.
• retryInterval—Specifies the delay, in milliseconds, between each reconnection

attempt.
• retryIncrement—Specifies, incrementally, the retry interval. The default is 0.
Note: Before you restart the SAP R/3 adapter, reload and update the
connection parameters in the repository:
runtibco -loadSAP <variant> <partition> io <sap-release>
Edit SAPAdapteridocIdocPublisherConfig.xml
In order for your IDOC integration with Ariba Buyer to work, you must edit and
confirm some settings within a file called SAPAdapteridocIdocPublisherConfig.xml.
A different copy of this file exists for every SAP partition, and you must edit and
confirm settings for each copy. You can find the file in the following partition specific
locations within your Ariba Buyer installation directory:
./config/variants/<variant>/partitions/<partition>/tibco/adapter/sap/config/SAPAdapteridocIdocPublisherConfig.xml
You must also edit the server connection pools.

After Running TIBCO initdb Chapter 2 Ariba Buyer Setup
Server Connection Pools
You must verify attributes of the <serverConnectionPool> tag within the file:
• For gatewayService, ensure that you SAP system number creates the last two
characters. For example, if you SAP system number is 08, then the entry must read
sapgw08.
• Ensure that the gatewayHost is set to the SAP host name where you install and
configure ALE/IDOC mechanisms.
• Ensure that the destination is set to your SAP SID.
The following text presents a sample <serverConnectionPool> tag. The attributes that
you must create, edit, or verify appear in bold:
<serverConnectionPool
name="SAOutboundIdoc-idoc-RFCServerConnectionPool"
timerRef="RfcPollingTimer"
maxConnections="1"
programID="bangoYC"
gatewayService="sapgw00"
gatewayHost="sap"
destination="SAPSYS"
useSAPRFCIni="0"
maxAttempts="1"
retryInterval="10000"
retryIncrement="0" rfcTrace="0">
};
After Running TIBCO initdb

This section presents tasks you must complete after you fully initialize the TIBCO
database and its contents through initdb -inittibco command. For information about
TIBCO-related database initialization, refer to the Ariba Buyer TIBCO Configuration
Guide.
After initializing the TIBCO database, you should:
• Load SAP version specific data into the Repository.
• Regenerate worksheet mappers.
• Start the TIB/R3 Adapter for batch integration.

Chapter 2 Ariba Buyer Setup After Running TIBCO initdb
• Start the TIB/R3 Adapter for IDOC integration.
• Tweak your integration through the Meta Adapter and Adapter Configurator.
Loading SAP Version Specific Data into the Repository

You must load some SAP version specific items into the Repository through the
following command:
runtibco [-instance <instance>] -loadSAP <variant> <partition> <mode> <SAPversion>
This option loads in partition specific inbound RFC parameters and schema for an
SAP system into an SAP variant Repository instance through the TIBCO program
file, r3MigrationTool.
The command takes the following arguments:
• <mode> can be “i” to insert data for the TIB/R3 Adapter, or “io” to both insert and
overwrite data.
• <SAPversion> can be 3.1I, 4.0B, 4.5B, or 4.6B
Note: If you use SAP version 4.0B, you must load the SAP 4.0B schema
with the following command:
runtibco [-instance <instance>] -loadSAP <variant> <partition> io 40B
Note: If you use SAP version 4.6B, you must load the SAP 4.6B schema
with the following command:
runtibco [-instance <instance>] -loadSAP <variant> <partition> io 46B
Each SAP partition runs on a separate TIB/R3 Adapter, and each SAP variant uses a
single Repository instance for all partitions. This means that a single variant must
maintain configuration information for each partition specific TIB/R3 Adapter. This
information consists of configuration settings for “inbound” RFC information from
TIB/MessageBroker.
Ariba Buyer stores a default configuration of inbound RFC information in the

following partition specific locations within your Ariba Buyer installation directory:
config/variants/<variant>/partitions/<partition>/tibco/adapter/sap/config/SAPAdapter_AllRFCs_RFCInboundConfig.xml

After Running TIBCO initdb Chapter 2 Ariba Buyer Setup
This option records its progress in a log file, located in the following location:
~/logs/tibco/adapter/sap/log
Regenerating Worksheet Mappers

Mappers often do not work in TIB/MessageBroker worksheets that you import into
the Repository. Use the following command to make them work:
runtibco [-instance <instance>] -regenMappers [-variant <variant> [-sheets <sheet1>
<sheet2>]]
This option automatically updates, or regenerates, worksheet mappers.
If you run the option without arguments, it generates mappers for all worksheets in all
Repository instances. This works well for large migration tasks.
The option takes the following optional arguments:

• -variant <variant>
• -sheets <worksheet1> <worksheet2>
The -variant <variant> arguments, by themselves, update all mappers in all worksheets
within a variant Repository instance.
The -sheets arguments work with the -variant argument to update one or two worksheets
within a variant, by name.
Starting the TIB/R3 Adapter for Each Partition

You need to start the TIB/R3 Adapter for each SAP partition by entering the
following command:
runtibco [-instance <instance>] -startsapadapter <variant> <partition>
This option starts a single TIB/R3 Adapter program file, r3Adapter, for integration with
an SAP system for a single partition.
You must install and configure one TIB/R3 Adapter for each SAP partition in Ariba
Buyer.

Chapter 2 Ariba Buyer Setup SAP Password Changes
Starting the TIB/R3 Adapter for IDOC Integration

You need to start the TIB/R3 Adapter for IDOC integration for each SAP variant
through the following command:
runtibco [-instance <instance>] -startsapidocadapter <variant>
This option starts the TIB/R3 Adapter program file, r3Adapter, for IDOC real time
integration with SAP systems through generic listeners.
This option runs a special TIB/R3 Adapter only for real time incremental loading of
data from SAP systems. It finds the configuration data it needs within the following
Repository location:
~/tibco/private/adapter/SAPAdapter30/SAOutboundIdoc-idoc
SAP Password Changes

If your SAP password changes, you must update the TIB/Repository. There are two
ways you can do this:
• Method one:
1. Manually change the System.SAPConnections value in the parameters.table file.
2. Shutdown the Ariba Buyer server.
3. Run the following command:

runtibco {-instance <instance>] -updateSAPConnection
<variant><partition><sapconnection> [<saprelease>]
• Method two:
1. Export the TIB/Repository.
2. Manually edit the export file.
3. Import the export file to the TIB/Repository.

SAP Password Changes Chapter 2 Ariba Buyer Setup

Chapter 3
SAP Setup
Before using Ariba Buyer with SAP, you must configure your SAP system and install
the Ariba development classes. This section contains the information you need to
configure and install Ariba Buyer items for your SAP system. Ariba recommends that
you have an SAP Basis administrator help you.
The basic tasks required for setting up your SAP system to integrate with Ariba Buyer
are:
• Set up a user account on the SAP system for Ariba Buyer transactions only.
• Install the Ariba transports.
• Ensure the RFC transactions from Ariba Buyer do not time out on SAP.
• Verify that fields are set properly on your SAP system.
• Configure incremental loading if you wish to use this feature.
• Set up global company codes.
• Configure receiving tolerances.
• Test your connection
The rest of this chapter explains these tasks in detail.
Before you complete the tasks in this chapter, you must perform the tasks in Chapter
2, “Ariba Buyer Setup.”

Setting Up Ariba Users Chapter 3 SAP Setup
Setting Up Ariba Users

You must create user accounts for Ariba Buyer and Ariba Buyer implementation
personnel to work with your SAP instance:
• One CPIC user for Ariba Buyer and the TIB/R3 Adapter to use
• One or more dialog users for Ariba Buyer implementation personnel and debugging
CPIC User
In a complete Ariba Buyer implementation, a CPIC user affords Ariba Buyer and the
TIB/R3 Adapter access to Ariba Buyer RFCs. You should grant the CPIC user
unrestricted access to your SAP instance with SAP_ALL and SAP_NEW in the profile.
These privileges are necessary for Ariba Buyer and the Ariba Buyer RFCs to
communicate properly.
Note: It is safe to grant the Ariba Buyer CPIC user full privileges because
CPIC users have no dialog access to your SAP instance.
You must choose an account for Ariba Buyer to use when connecting to SAP. Ariba
recommends you create a new account, but you can use an existing account if you
prefer.
The default username for this account is ariba. Whichever user you choose, you
should check the user defaults and make sure they are set as follows:
• For date format:MM/DD/YYYY
• For currency separator:. (period)
▼ To create a CPIC user:
1. Access the Maintain Users: Initial Screen, SU01.
2. Enter the user ID you chose for Ariba Buyer integration and click the create
icon.
3. Select the Logon Data tab.
4. Enter the password for the Ariba user and choose the CPIC radio button for
User Type.

Chapter 3 SAP Setup Setting Up Ariba Users
5. In the Profiles tab, enter a profile for SAP_NEW and SAP_ALL.
The other fields in the screen are optional and you may fill them in as you
like. Choose the enter check when you finish. The Maintain Fixed Values
screen appears.
6. Enter the following values for the following fields:
• Date format—MM/DD/YYYY
• Decimal point format —Period
7. Complete the other fields of this screen or leave them blank as you like and
choose the enter check. Do the same for the user parameters in the following
screen.
Dialog Users
You should create dialog users for Ariba Buyer implementation for two purposes:
• To provide SAP administrators and Ariba Buyer implementation personnel

necessary access to Ariba RFCs and your SAP instance
• To allow Ariba Buyer visual dialog access for testing integrations
Implementation Dialog Users
You may not need to create new dialog users if you already have user IDs available
for the people who implement and configure Ariba Buyer RFCs. Your SAP system
administrator can create any necessary user IDs based upon approved requests for
access.
Ariba recommends you have or create one dialog user ID for each developer or
administrator working on your Ariba Buyer integration because these people must
perform the following tasks on your SAP instance:
• Install the Ariba Buyer RFC transports
• Configure the order determination for purchase orders from Ariba Buyer
• Administer ALE/IDOC mechanisms for the optional incremental loading features
• Make any changes to the way Ariba Buyer RFC integrations function

Transport Installation Chapter 3 SAP Setup
Ariba Buyer Testing Dialog User
As you implement your Ariba Buyer integration, you may find it necessary to step
through the processes of Ariba Buyer RFCs to better understand how they work. In
particular, you may wish to see how Ariba Buyer inserts purchase order and goods
receipt fields into SAP screens.
To view Ariba Buyer integrations within the SAP GUI, you must allow Ariba Buyer
and the TIB/R3 Adapter to access SAP through a dialog user ID. This ID is similar to
the CPIC ID that you use for your actual implementation. Like the CPIC ID, it
requires full privileges, SAP_ALL and SAP_NEW, to work properly. For convenience,
you may wish to use the default username ariba for this account. As with the CPIC ID,
you should check the user defaults and make sure they are set as follows:
• For date format:MM/DD/YYYY
• For currency separator:. (period)
Transport Installation
You must install Ariba Buyer objects on your SAP system by using transports. The
most recent version of the Ariba Buyer Release Guide provides the information you
need to install the transports.
Time-out Interval
The SAP system has a time-out limit on RFC transactions which is designed to ensure
that no resources inadvertently stay locked on the SAP side. The SAP time-out
interval is defined by the profile parameter rdisp/max_wprun_time. The default value is
300 seconds.
If you have a large purchase order to push (with a large number of line items) or a
large amount of data to pull back, you may encounter this time-out limit and the SAP
system will cancel the job. To avoid this problem you must change your SAP
configuration to lengthen the time-out interval. You must change the interval on your
central instance as well as any application servers that communicate with Ariba. You
must restart each SAP server for the change to take effect.

Chapter 3 SAP Setup Time-out Interval
▼ To set the Time-out Interval:
1. Log in as a CPIC user (see “CPIC User” on page 36).
2. Transaction RZ10.
3. Enter the Instance Profile.
4. Enter the most current version (you will create a new version based on the
most current one).
5. Select Extended maintenance.
6. Click Change.
7. Scroll down to Parameter name rdisp/max_wprun_time.

If the value does not appear in your profile, you must create it by opening the
Parameter menu and selecting Create.
8. Create or change the value of rdisp/max_wprun_time to something longer, for

example, 3000 (for 3000 seconds).
9. Open the Parameter menu and choose Change.
10. Click on the Copy button.

This makes a copy of the new profile. The status line will display “The
changed profile was transferred”.
11. Move back to the initial Edit Profiles screen, RZ10, and save the profile.
In the dialog that appears, activate the profile.
12. Restart your SAP server for the profile changes to take effect.
Repeat these steps for each application server that exchanges data with
Ariba.

Checking Data Chapter 3 SAP Setup
Checking Data
In some cases, Ariba Buyer does not pull data from the SAP system unless that data is
set up in a particular manner on the SAP side. This section describes a few places
where you should check the data on your SAP system, to make sure that it is set up to
match the expectations of Ariba Buyer.
If an integration entry fails you can check this section again to look for problems.
Bank Selling Rate

Ariba Buyer pulls currency conversion information from the SAP system to ensure
that all purchase orders from Ariba use currencies valid in SAP. The currency
conversion pull expects to find a BANK_SELLING_RATE_SYMBOL in the SAP system. If
this symbol is not set, the currency pull fails.
To check whether this symbol is set, use transaction spro and go to Global Setting>
Currencies>Check Exchange rate type. Set the symbol if necessary.
Blank Descriptions
For most data in the SAP system, such as Purchasing Groups, the SAP integration
pulls (and uses) both ID and description fields from the SAP system. If either value is
blank, then the pull ignores that item and it doesn’t appear in the Ariba system.
Check your SAP system to ensure that all material groups and purchasing groups
have valid (non-blank) ID and description fields.
Vendor Restrictions
The Ariba Buyer/SAP integration has some restrictions on vendors. To pull all
available vendors, make sure none of the vendors have partner functions specifying
multiple ordering addresses. The SAP integration pulls in only one ordering address;
if there are multiple ordering addresses on the SAP side then there is no way for the
Ariba end user to choose among them.
Ariba Buyer does not pull vendors that are blocked. SAP uses special codes to
designate blocked vendors. The field SPERQ in table LFA1 specifies the code that SAP
uses for blocked vendors. The value you need to check for the SPERQ field is in table
TQ04A in field SPERRFKT. You can perform the following steps to find out the code for
blocked vendors.

Chapter 3 SAP Setup Checking Data
▼ To find blocked vendor codes:
1. Use transaction /nse11.
2. Enter table name LFA1, click on Tables and then Display.
3. Click on check table TQ04A corresponding to field SPERQ.
4. On the top menu choose Utilities->Table Contents.
5. Choose Execute.
6. You will see the block function values. Check the codes for purchase orders.
Vendor ERS Tax Status

Ariba Buyer supports vendors from SAP that offer evaluated receipt settlement (ERS)
agreements. These agreements can have different tax rates depending on a variety of
factors, such as the tax laws in location of the supplier and the tax laws in the location
of the requestor.
Purchase orders from Ariba Buyer for SAP contain a field to determine whether or
not a vendor has ERS tax information. Ariba Buyer always sets a value for the ERS
tax field. If Ariba Buyer has no tax ERS information about a vendor, it sets this field
to a blank, empty, or null value.
Some SAP systems require that you set a default value for empty tax code values.
Such systems return an error message during purchase order pushes if you have not
configured them to handle empty values. You can correct this problem by doing one
of the following:
• Configure SAP to set a default tax code.
• If you cannot configure a default tax code, change any error flags.
Validation on Catalog Items

Catalog items are validated against the Purchasing Organization. The vendor for each
catalog item must be defined in the purchasing organization.
If a user picks a catalog item that originated in the SAP system, Ariba Buyer validates
the vendor of that item against the user’s purchasing organization.

Incremental Real Time Loading Chapter 3 SAP Setup
If the vendor is not defined in the purchasing organization, Ariba Buyer flags the field
as invalid and does not allow the user to submit the purchase requisition until the field
is corrected.
Incremental Real Time Loading

Incremental real time loading allows Ariba Buyer to only pull data which has
changed, is new, or requires removal as the data changes. Incremental loading can
significantly decrease the amount of time it takes for Ariba Buyer to load information
from SAP.
To use the incremental loading features with your Ariba development classes, you
must perform further configuration. For instructions, refer to “Real Time
Integrations” on page 97.
Global Company Codes

You must set up global company codes for your Ariba Buyer integration to work. You
can set up global company codes:
• When you complete the optional real time incremental loading configuration as
described in “Real Time Integrations” on page 97.
• At any time, as described in “To set up global company codes:” on page 101.
Receiving Tolerances
Ariba Buyer allows end users to enter receiving information about the items they
order. To do this, Ariba Buyer and SAP both need to receive items in the same way.
For example, both must have similar receiving tolerances, or similar ways of allowing
users to account for times when they receive fewer or more items than they ordered.
This section presents the following information about receiving tolerances:
• Receiving system parameters
• ERP orders

Chapter 3 SAP Setup Receiving Tolerances
Receiving System Parameters

Ariba Buyer allows you to configure receiving tolerances through settings in the
system parameters table:
• Application.Procure.OverReceivingOperator
• Application.Procure.OverReceivingPercentage
• Application.Procure.OverReceivingQuantity
• Application.Procure.OverReceivingValue
• Application.Procure.UnderReceivingOperator
• Application.Procure.UnderReceivingQuantity
• Application.Procure.UnderReceivingValue
• Application.Procure.UnderReceiving
You can learn how to set these values in the Ariba Buyer Procurement Guide.
As an SAP administrator, you should know the following about Ariba Buyer
receiving integration:
• Ariba Buyer does not push receipt tolerances at the document level.
• Ariba Buyer does not pull tolerances from SAP, but instead uses only those in the
system parameter table.
• As an SAP administrator, it is your responsibility to ensure that the receiving

tolerances in Ariba Buyer match those of SAP.
ERP Orders
ERP orders are purchase orders that Ariba Buyer pushes to SAP. Ariba Buyer expects
SAP to handle ERP orders and transmit them to vendors. ERP orders don’t take
advantage of dynamic trade or the Ariba Commerce Services Network.
You should be careful about receiving integration with ERP orders because SAP users
and processes can change an ERP order once it is in SAP.
Such changes can cause errors, especially in the event that SAP applies release
strategies to purchase orders from Ariba Buyer. SAP does not allow you to receive
against a purchase order until all the release strategies are fulfilled.
See your Ariba Professional Services representative for more information and to
decide if ERP orders are right for your implementation.

Testing Connections Chapter 3 SAP Setup
Testing Connections
You can test your connection to SAP from Ariba Buyer after you complete the tasks
in this chapter, perform TIBCO-related initdb commands, and complete the tasks in
Chapter 2, “Ariba Buyer Setup.”
▼ To test your SAP connection
1. Start the Repository server:

runtibco -startreposerver
2. Run the TIB/R3 Adapter.

runtibco -startsapadapter <variant> <partition>
3. Examine the TIB/R3 Adapter log file.

The TIB/R3 Adapter creates a log file in:
~\logs\tibco\adapter\sap\log\SAPAdapter_<instance>_RFCInboundConfig.log
Open the file in a text editor. If you see entries such as the following, you
successfully connected to SAP:
SAPAdapter 2000 Aug 02 10:44:35:745 R3-CORE-LIB-6006 info Adding RFC function
"Z_ARIBA_ACC_FIELD_STATUS"
"Z_ARIBA_ACCOUNT_CAT_NAMES"
"Z_ARIBA_ACCOUNT_CATEGORY"
If you find RFC-related error messages in the file, you should verify that you
have correct connection information in the XML files, as described in
Chapter 2, “Ariba Buyer Setup.”
4. You can also check whether you connected correctly to SAP by logging into
SAP through the SAPGUI and viewing the Gateway monitor.
You should find an entry for the Ariba Buyer host if you have started the
TIB/R3 Adapter.
You probably want to connect from the Ariba Buyer machine through the SAPGUI
just to make sure there aren’t other factors not related to Ariba Buyer or TIBCO
products that are affecting your connection.

Chapter 4
Configuring Pulls
Ariba Buyer provides the worksheets and integration event table entries for standard
Ariba Buyer data pulls from SAP. Because your SAP implementation may contain
additional data that would need to include with the Ariba Buyer purchase orders or
receipts, you can modify these data pulls to include additional data.
This chapter explains how to:
• Pull new fields
• Pull new tables
• Filter data
• Understand Ariba RFCs
The intended audience for this information is SAP administrators. Performing these
tasks requires familiarity with the ABAP/4 language and basic SQL tasks. To perform
similar tasks for data pushes, see Chapter 5, “Configuring Pushes.”
Note: The material in this chapter instructs you to edit and create objects on
your SAP instance. When you make changes to Ariba Buyer objects on SAP,
you may encounter the warning “Only urgent repairs in the consolidation
system”. This warning appears whether you’re changing objects on your
consolidation system or your development system.
This warning indicates that you’re making changes to objects that originated
from another system. In this case, the objects originated from Ariba Inc. The
SAP client doesn’t expect you to change objects from third party vendors
such as Ariba Inc. Rather, it expects you to develop your own objects on a
development system. You can disregard this message.

Pulling Additional Fields Into Ariba Buyer Chapter 4 Configuring Pulls
Pulling Additional Fields Into Ariba Buyer

This section describes how to configure your SAP system to pull additional fields into
Ariba Buyer for existing pull integration events. This section presents:
• Extension structures
• Edits to extension structures
• Example extension structures
As an SAP administrator, you must coordinate your efforts with any personnel who
are configuring Ariba Buyer. You both want to identify the data you’re pulling as well
as the RFC and structures in which this data will appear.
Extension Structures
The term extrinsic refers to any data field you pull into an Ariba Buyer object that is
not part of the object as supplied with Ariba Buyer. You can pull extrinsics into Ariba
Buyer from CSV files, databases, or ERP systems.
The ZARC development class provides special structures, called extension structures,
that you can use to define extrinsic data in the Ariba Buyer RFCs on your SAP
instance. Most Ariba Buyer RFCs offer one or more extension structures for you to
configure extrinsic pulls.
Ariba Buyer RFCs use the extension structures to determine what fields to create in
each of the tables they export to Ariba Buyer. Extension structures work as a template
to define the structure of the Ariba RFC tables.

Chapter 4 Configuring Pulls Pulling Additional Fields Into Ariba Buyer
Ariba Buyer TIB/MessageBroker worksheets retrieve the tables through RPC clients.
The Ariba Buyer TIBCO integration channel incorporates the table data into Ariba
Buyer objects according to the field and object descriptions in metadata XML.
Extension structures have all the fields in the ZAF6 development structures as well as
any fields you add to them:

For example, the ZXTASSET extension structure for asset pulls contains a substructure
called ZARASSET. ZARASSET holds all the base fields that Ariba Buyer RFCs need to
run:
If you want to add new asset fields to Ariba Buyer RFC data pulls, you add them to
the ZXTASSET structure:
Note: Never make changes to the original structures for Ariba RFCs. Your
SAP integration may not function properly if you do so. Likewise, you must
always include the original structures within the extensions. Never remove
the “.include” statements.
This chapter only explains how to define extrinsic data within an extension structure.
If you make changes to extension structures, you must modify your
TIB/MessageBroker worksheets to map and transform these fields appropriately and
you must also modify the Ariba Buyer metadata XML to include your changes. For
information on these tasks, refer to:
• Customizing Ariba Buyer

Chapter 4 Configuring Pulls Pulling Additional Fields Into Ariba Buyer
Note: Ariba Buyer does not support metadata created with the TIBCO SAP
metadata editing tool. You must modify Ariba Buyer metadata directly, by
editing the metadata XML files.
Extension Structure Names
By convention, extension structure names begin with the letters ZXT and belong to the
Ariba Buyer configuration development class, ZARC. The corresponding Ariba Buyer
structure names begin with ZAR and belong to the ZAR6 development class, which you
should not alter. Both names share the same root.
For example, for internal orders there is a root of ORD. The extension structure has the
name ZXTORD and the Ariba Buyer structure is ZARORD.
Adding Fields to Extension Structures

In most circumstances, each structure and extension structure select data from one
and only one table. Consequently, you should return additional fields from only one
table.
▼ To add fields to extension structures:
1. Determine the table that contains the column you need to pull.
2. Find the Ariba RFC that selects data from that table.
3. Add the field to the RFC extension structure for the table.
4. Activate your changes.

Extension Structure Example

For this example, you need Ariba Buyer to identify the country in which an asset
originates. The asset master record, ANLA, contains a column called LAND1 that
indicates the country origin of an asset.
You can search through the Ariba Buyer development classes to determine which
Ariba Buyer RFC pulls data from the SAP table ANLA. In this case, the Ariba Buyer
RFC that handles asset pulls from ANLA is Z_ARIBA_ASSET.
Z_ARIBA_ASSET exports an extension structure called ZXTASSET that includes the

Ariba Buyer structure ZARASSET. ZARASSET does not contain the LAND1 field.
You need to add LAND1 to the Ariba Buyer extrinsic asset pull structure, ZXTASSET,
and then activate your changes. Make sure to enter AM_LAND1 for the data element
description, exactly as it appears in the ANLA table. When you finish, your SAP system
will include a new extrinsic, LAND1, in ZXTASSET, which it pulls from ANLA.

Chapter 4 Configuring Pulls Pulling New Tables Into Ariba
You must use the exact same field name and data element description as the column
you pull. When the Ariba Buyer RFC runs, it uses the information you provide to find
the column in the table.
Note: Whenever you make changes to a structure, you must

make sure to run the “activate” button, or you risk losing your
changes.
Pulling New Tables Into Ariba

You might find extrinsics don’t provide the ability to pull the data you need. For
example, you might decide you need to pull users from SAP. To implement such
configurations, you can write your own RFCs and create new tables for the data you
pull.
You can also write new RFCs for data that comes from a different table, but that
shares a key with one of the Ariba Buyer RFCs.
In order to pull data into worksheets, you must export tables from your RFCs. You
may also need to configure your worksheets to send appropriate variant and partition
information.
To pull data into Ariba Buyer, you need to interact with a TIB/MessageBroker
worksheet. Quite often, you need to import your SAP variant and partition from the
worksheet and to define the structure your table or tables use.
▼ To pull new tables:
1. Write your RFC, importing any necessary structures.
2. Create any new TIB/MessageBroker worksheets to transform the data into

Ariba Buyer objects.
3. Write your custom Java code and incorporate the new data in metadata
XML.

Pulling New Tables Into Ariba Chapter 4 Configuring Pulls
The following material about filtering and example RFC code contains useful
information for the first step of writing your RFC and importing structures. For
information on steps two and three, refer to the following guides:
• Customizing Ariba Buyer
• Ariba Buyer API Guide
Declaring Local Interfaces

Local interfaces define the input and output parameters of an RFC. In SAP the "in"
parameters are called "import" parameters, the "out" parameters are "export"
parameters and "in-out" parameters are "table" parameters.
The TIB/Adapter for R/3 uses metadata in the XML classes files that describes these
parameters. The structure of these XML files resembles the local interfaces of RFCs.
The XML classes files are found in:
config/variants/<variant>/partitions/<partition>/tibco/adapter/sap/classes/sap/
Your interfaces should be similar to those of Ariba Buyer RFCs. The following local
interface appears in the ABAP code for a plant pull:
3 *”*”Local interface:
4 *” IMPORTING
5 *” VALUE(VARIANT) LIKE ZARIBTVARV-VARIANT
6 *” VALUE(PARTITION) LIKE ZARIBTVARV-PARTIT
7 *” TABLES
8 *” SHIP_TO_INFO STRUCTURE ZXTPLANT
Adding Custom RFCs

Once you have created the custom RFC, you must add the RFC to Ariba Buyer and
create the corresponding metadata XML. The XML metadata files are in the
following directory:
~\config\variants\<variant>\partitions\<partition>\tibco\adapter\sap\config

Chapter 4 Configuring Pulls Pulling New Tables Into Ariba
Define the RFC in Ariba Buyer
To define RFCs you must edit the SAPAdapter_AllRFCs_RFCInboundConfig.default.xml file.
Add two entries for the new RFC to the file: one to define <server> and the other to
specify <invoke function = "add">. For example:
-<SAPAdapter InstanceID>
-<deployment name>
-<servers>
<rvCmRpcServer name="Z_ARIBA_PURCHASE_GROUP-RPCServer"
session="RFCClientCMSession-SAInboundRFC.parsap"
subject="SAP.Z_ARIBA_PURCHASE_GROUP.SAInboundRFC.
parsap.Z_ARIBA_PURCHASE_GROUP"
classRef="Z_ARIBA_PURCHASE_GROUP"/>
-<component>
-<interface>
-<init>
<invoke function="add">
<values name="Z_ARIBA_PURCHASE_GROUP"
rpcRef="Z_ARIBA_PURCHASE_GROUP-RPCServer"
classRef="Z_ARIBA_PURCHASE_GROUP"
deploymentRef="default" />
</invoke>
You can use these examples as a template for your own entries.
Note: Be very careful when you make these entries, if there is an error,
finding the error can be difficult.
Define the Metadata XML
After you have made these entries, you must define XML metadata for the classes
(RFC input/output/table parameters). The XML metadata files are in the following
directory:
~\variants\<variant>\partitions\<partition>\tibco\adapter\sap\classes\SAP
You must create a <rfc_name>.xml file and and a <rfc_name>_<param_name>.xml file for
each structure/table input/output/table parameter.
Note: Parameters must have char.X values or fixe.X.Y data types.

Filtering Chapter 4 Configuring Pulls
Below is a sample RFC metadata XML definition. You can use this as a guideline to
create your RFC metadata XML definition.
-<schema>
-<class name="Z_ARIBA_PURCHASE_GROUP">
-<operation name="Z_ARIBA_PURCHASE_GROUP" returns="string">
<parameter name="PARTITION" classRef="char.20" direction="in" />
<parameter name="PGROUP_INFO"
classRef="sequence[Z_ARIBA_PURCHASE_GROUP
_PGROUP_INFO]" direction="inout" />
<parameter name="VARIANT" classRef="char.20" direction="in" />
</operation>
</class>
</schema>
Load the RFC in the TIB/Repository
Once the RFC has been created and defined in Ariba Buyer, you must load the custom
files in the TIBCO repository using the following command:
runtibco -loadSAP XXX_SAP XXX_Part1 io 45B
Note: If you use i, the command only inserts new schemas but doesn’t
modify existing configurations. You must use io (insert and overwrite).
You might want to check the output of the above command. If it's using the correct
configuration file, it should print something similar to:
Inserting schema Z_BAPI_ACC_INVOICE_RECEIPT_PST_VALUEFIELD
Filtering
Your SAP development classes for Ariba Buyer offer you three ways to restrict the
data they offer. Restricting the data included in a data pull is called filtering. Ariba
Buyer RFCs offer three types of filtering:
• Static filtering
• ABAP filtering
• Post hook filtering

Chapter 4 Configuring Pulls Filtering
Static Filtering
Static filtering allows you to construct conditional searches of your SAP tables
according to the values of given fields. The table ZARIBTVARV allows you to construct
queries to limit the data you pull from SAP into Ariba Buyer. Defining queries within
this table is referred to as static filtering. This type of filtering is static because it
exists in a structured form within ZARIBTVARV and does not select data based on
dynamically formed queries.
Every Ariba Buyer RFC that pulls data from your SAP system first makes a call to
ZARIBTVARV to see if it needs to restrict its search. The RFCs look to find any entries
that match their names. If they find a match, they restrict the query according to the
instructions in the ZARIBTVARV entry.
Static filtering is rather quick and easy to use, however, it does not handle inner join
queries against more than one table. If you need to restrict data pulls the pull from
more than one table, you must use the filtering techniques explained in “ABAP
Filtering” on page 61.
Editing ZARIBTVARV
To restrict the data that an Ariba Buyer RFC pulls, you just need to make a
corresponding entry in ZARIBTVARV. Enter a new row in ZARIBTVARV with the RFC
name, the field you want to use, and some information about what you’re trying to
find.
Note: Ariba suggests you use transaction SM30 to examine ZARIBTVARV.

Your SAP user ID must have authorization S_TABU_DIS in order to use
SM30.ZARIBTVARV resides as a table within the dictionary objects for the
ZAR6 class. You can learn more about the ZAR6 development class through
the SAP Developer Workbench.
You can use the ZARIBTVARV table to configure variable settings in certain RFCs. In
particular, you can use it to store and retrieve parameters through calls to the
Z_ARIBA_PARAMETER RFC. This text refers to ZARIBTVARV’s configuration and
parameter capabilities as parameter use. You can learn about parameter use in
Chapter 6, “Parameter Configuration.” For instructions on editing the ZARIBTVARV
parameters, refer to “ZARIBTVARV” on page 77.

ZARIBTVARV Field Reference
The following table presents the fields you can set in ZARIBTVARV.
Table 2. ZARIBTVARV Fields
Field Name Description Use and Necessity

VARIANT The Ariba Buyer variant field The VARIANT field is
identifies the unique name for the necessary for both filtering
shape of data in your SAP system and parameter use
as it appears within Ariba Buyer. An (selection types S and P).
Ariba Buyer variant is different from
a variant in SAP.
PARTITION The PARTITION field describes the The PARTITION field is
unique instance name of a given necessary for both filtering
variant shape as you represent it to and parameter use
Ariba Buyer. (selection types S and P).
NAME The NAME field provides an index The NAME field is necessary
to the table. Ariba Buyer uses it for both filtering and
either to pass the name of the parameter use (selection
calling function or to pass the name types S and P).
of the parameter it seeks. See
“Parameter Configuration” on
page 77 to find out more about
ZARIBTVARV and parameters.
FIELDNAME FIELDNAME refers to the column The FIELDNAME column is
name you use to filter data. (You necessary for filtering only
must leave this blank to use (selection type S).
ZARIBTVARV for parameters,
selection type P.)
TYPE The TYPE field determines whether The TYPE field is necessary
to us ZARIBTVARV to filter data or to and determines both filtering
configure a parameter for an RFC. and parameter use.
Enter a value of S to perform
filtering and P to configure
parameters.
See “Parameter Configuration” on
page 77 to find out more about
ZARIBTVARV and parameters.
NUMB The NUMBER field determines the The NUMBER field is
sequential order of selection optional and is used for
statements. The order determines filtering (selection type S).
how to construct the entire
selection.
See “Selection Condition Options”
on page 57.

Table 2. ZARIBTVARV Fields (Continued)
Field Name Description Use and Necessity

SIGN The SIGN field determines whether The SIGN field is required for
to include or exclude the selection filtering use (selection type
condition. Set this value to “I” for S).
inclusion if the condition is positive
or to “E” for exclusion if the
condition if negative.
See “Selection Condition Options”
on page 57.
OPTI The OPTION field allows you to The OPTION field is required
create conditions based on equality, for filtering use (selection
value ranges, and patterns. You type S).
may set it to the following
conditions:
BT — The “BeTween” option
specifies a selection within the
range of values in the LOW and
HIGH fields, e.g. names between
“Daly” and “McDonald”.
CP — The “Contains Pattern” option
allows you to return data with a
given pattern, e.g. names that
begin with “Lu”.
EQ — The “EQual” option
determines equivalency, e.g.
names = “Doug”.
GE — The “Greater than or Equal
to” option determines if the
FIELDNAME is greater than or
equal to a value, e.g. names >=
“Bruce”.
LOW The LOW is the default setting for The LOW field is optional for
value conditions for filtering and parameter configurational
settings for parameters. If you need and required for most
to enter particularly long values - filtering statements.
like strings - you can overlap values
to the HIGH field.
HIGH The HIGH field works with LOW The HIGH field is optional for
values and BT option fields. most parameter
configuration and filtering,
except BT option fields.
Selection Condition Options
The selection options in ZARIBTVARV reflect the internal table structure of select
options in SAP reports. The ZARIBTVARV structure itself resembles the SAP TVARV
structure, and the fields work in much the same way.

The structure allows you to create the following conditions:
• Equality and inclusion
• Ranges and exclusion
• Patterns and comparisons
Equality and Inclusion
Equality and inclusion conditions allow you to set a selection criteria that equals or
includes a given value.
The following example takes you through the steps of creating an equality and
inclusion filter condition:
Scenario: You need to create a static filter that pulls only company information for
companies within a given country.
▼ To create the filter:
1. Refer to Z_ARIBA_COMPANY to find out where this information originates.

The information originates from table T001.
2. Open T001. It contains an entry called LAND1, which designates countries.

The only countries you want to pull from are Australia and Japan, which
LAND1 designates with the strings AU and JP.
You now have the information you need to build your static filter:
• The Ariba Buyer RFC that pulls the data
• The column that contains the data (and the table)
• The data set you want to return
3. Build your select statement. The statement depends on the data set you want
to capture. In this case you want to pull rows where LAND1 is equal to AU or
rows in which LAND1 is equal to JP. Another way of saying this might be:
(LAND1 = “AU”) OR (LAND1 = “JP”)

In this example, you want to define a logical “OR” based on two conditions
of equality. Each condition in a selection requires its own row in
ZARIBTVARV. The two rows would look similar to the entries in Table 3.
Example OR Entry (the VARIANT and PARTITION fields are not included in the
example):
Table 3. Example OR Entry
NAME FIELDNAME TYPE NUMBER SIGN OPTION LOW HIGH

Z_ARIBA_COMPANY LAND1 S 0000 I BT A G
Z_ARIBA_COMPANY LAND1 S 0001 E EQ CA
The NAME column indicates this filter is for the data that Z_ARIBA_COMPANY
pulls.
The FIELDNAME tells you that you’re pulling data from the LAND1 column.
You can infer the table from the column, T001.
The TYPE fields of S tells the calling function that the row is for filtering, or
selecting, data.
The NUMBER field includes more than one row of the table in the condition.
It starts at zero, or 0000. The order is not significant.
The SIGN field determines whether to exclude the condition from the
statement or include it, signified by I or E. An included condition is generally
specified with an OR statement. To specify an excluded condition, you
generally use an AND NOT statement. (See below for an example of
exclusion).
The OPTION column determines that you’re selecting for a condition of

equality (EQ). You can also specify:
• Ranges of values (BT) The “BeTween” option specifies a selection within

the range of values in the LOW and HIGH fields, such as the names between
“Daly” and “McDonald.” For more information, see “Ranges and
Exclusion” below.
• Pattern matches (CP) The “Contains Pattern” option allows you to return
data with a given pattern, for example, names that begin with “Lu.” For
more information, see “Patterns and Comparisons” on page 60.
• Greater than or equal to conditions (GE) The “Greater than or Equal to”
option determines if the FIELDNAME is greater than or equal to a value, for
example names >= “Bruce.”

Ranges and Exclusion
You can also create other kinds of selection options. Suppose you want to pull only
countries whose SAP codes alphabetically range between, and include, AU and GB
(for Australia and Great Britain). However, you need to exclude Canada (CA) from
this pull. Here’s a rough statement of the logic:
(“AU” >= LAND1 >= “GB”) AND NOT (LAND1 = “CA”)
The ZARIBTVARV entries would resemble the following.
Table 4. Example Range and Exclusion Entry

Z_ARIBA_COMPANY LAND1 S 0000 I BT AU GB
Z_ARIBA_COMPANY LAND1 S 0001 E EQ CA (empty)
The selection first includes the range between AU and GB and then excludes CA.
Patterns and Comparisons
You can also select data according to its pattern and by comparing values.
Suppose you want to pull only vendors that certain users created, according to the
user’s name. You want to pull only users who have names that begin with the letter
“M” or “N”. For some reason, however, you want only some of the “N” users,
specifically, only those in the alphabetic range “N” through “NE”.
The Ariba Buyer RFC, Z_ARIBA_VENDOR_ONLY, pulls vendors from the table LAF1.
LAF1 contains the column ERNAM for the user name. The logic of the selection would
resemble the following statement:
(ERNAM LIKE “M*”) OR (ERNAM LIKE “N*”) AND NOT (ERNAM >= “ND”)
Note: You do not have to use AND NOT ERNAM >= “ND”, but this
example does so for illustrative purposes. AND ERNAM < “ND” is more
concise.

The values in ZARIBTVARV would resemble the following:
Table 5. Example Pattern and Comparison Entry

Z_ARIBA_VENDOR_ONLY ERNAM S 0000 I CP M (empty)
Z_ARIBA_VENDOR_ONLY ERNAM S 0001 I CP N (empty)
Z_ARIBA_VENDOR_ONLY ERNAM S 0002 E GE ND (empty)
This filter selects three conditions:
• Names that begin with “M”
• Names that begin with “N”
• After the first two conditions, the filter refines the set to only those names that are
equal to or less than “NE” (or not greater than or equal to “ND”).
ABAP Filtering
The term ABAP filtering refers to a way of selecting data by editing a special exit
RFC called Z_ARIBA_PREFILTER_EXT. Every Ariba Buyer RFC that pulls data first
makes a call to Z_ARIBA_PREFILTER_EXT to refine the table data set.
Z_ARIBA_PREFILTER_EXT is part of the ZARC Ariba Customer Development class
where you can make modifications.
Each RFC passes its name to Z_ARIBA_PREFILTER_EXT. You can use conditional tests
to determine how and if Z_ARIBA_PREFILTER_EXT should restrict the data set of the
table based on the calling RFC name. This type of filtering is called “ABAP filtering”
because you need to write ABAP/4 code to get the results you want.
This section explains how ABAP filtering:
• Performs inner joins
• Offers an RFC interface
• Can work in a sample configuration
Joins and ABAP Filters
The main reason you might use ABAP filters is to reduce your data set through
references to more than one table. Because you’re writing the code yourself, you can
implement inner join statements.

Prefilter Interface
The local interface for Z_ARIBA_PREFITLER_EXT is as follows:

*”*”Local interface:
*” IMPORTING
*” VALUE(VARIANT) LIKE ZARIBTVARV-VARIANT
*” VALUE(PARTITION) LIKE ZARIBTVARV-PARTIT
*” VALUE(NAME) LIKE ZARIBTVARV-NAME
*” TABLES
*” WHERE STRUCTURE WHERETAB
*” EXCEPTIONS
*” INVALID_SELECTION_SIGN
*” INVALID_SELECTION_OPTION
The RFCs pass your unique Ariba Buyer variant, partition, and RFC name.
Sample ABAP Filter
You can create dynamic WHERE statements for selections in the WHERE structure. The
example code in Z_ARIBA_PREFILTER_EXT demonstrates the use of a dynamic WHERE
statements. The WHERE statements in the code can come from another table.
Below is an example of an inner join ABAP filter. This example joins a purchase
organization table to a company code table to retrieve all purchase organizations for
company codes tied to the US:
TABLES: T001.
DATA: US_BUKRS LIKE T001-BUKRS.
IF 'Z_ARIBA_PURCHASE_ORG' = NAME.
SELECT DISTINCT BUKRS INTO US_BUKRS
FROM T001
WHERE LAND1 = 'US'.
DESCRIBE TABLE WHERE LINES COUNT.
IF COUNT > 0.
WHERE = 'or'. APPEND WHERE.
ENDIF.
CONCATENATE 'bukrs = ''' US_BUKRS '''' INTO WHERE.
APPEND WHERE.
ENDSELECT.
ENDIF.

Post Hook Filtering

Both static filters and ABAP filters cut down on data before an Ariba Buyer RFC
begins to process anything. You can filter data after the Ariba Buyer RFCs finish
through post hook filtering. SAP commonly provides such functionality through “user
exits” or “customer exits”.
• Exit RFCs
• Post hook filtering suggestions
Exit RFCs
Only SAP can use the SAP infrastructure of user exists, so Ariba Buyer provides post
hook filtering through exit RFCs instead. Ariba Buyer RFCs call exit RFCs just
before they exit.
Each Ariba Buyer RFC has its own exit RFC. Exit RFCs derive their names from the
Ariba Buyer module that calls them, with the suffix _EXT. For example,
Z_ARIBA_ASSET calls the exit RFC, Z_ARIBA_ASSET_EXT. Exit RFCs comprise most of
the ZARC class that allows you to make modifications.
Exit RFC usually imports only the Ariba Buyer variant, partition, and the extension
structure for a given internal table. The interface for Z_ARIBA_ASSET appears as
follows:
*” IMPORTING
*” VALUE(VARIANT) LIKE ZARIBTVARV-VARIANT
*” VALUE(PARTITION) LIKE ZARIBTVARV-PARTIT
*” TABLES
*” ASSET_INFO STRUCTURE ZXTASSET
Post Hook Filtering Suggestions
Ariba Buyer RFCs expose filtering for only some of the tables from which they take
data in SAP. Ariba Buyer RFCs sometimes depend on filtering for one table to restrict
the data pulled from a second table. For example, you might filter one table for a data
type in the first table, and then use that filtered result to pull data from a second table.

Example RFC Chapter 4 Configuring Pulls
In most circumstances this sort of arrangement works just fine. However, if the Ariba
Buyer RFCs retrieve data from the second table that you don’t want, you need some
mechanism to further restrict it. ABAP and static filters won’t work because they only
provide you access to the first table, not the second. You need to be able to restrict the
data after the Ariba Buyer RFCs finish with it. Post hook filters let you do this.
You need to write ABAP code to manipulate the data within the given internal table
for an Ariba Buyer RFC.
Example RFC
To understand how to configure data pulls you can examine the way a typical RFC
functions:

Chapter 4 Configuring Pulls Example RFC
The content of the company code pull RFC, Z_ARIBA_COMPANY, provides an example
of the mechanisms and techniques this chapter presents:
FUNCTION Z_ARIBA_COMPANY.
*"----------------------------------------------------------------------
*"*"Local interface:
*" IMPORTING
*" VALUE(VARIANT) LIKE ZARIBTVARV-VARIANT
*" VALUE(PARTITION) LIKE ZARIBTVARV-PARTIT
*" TABLES
*" COMPANY_INFO STRUCTURE ZXTCOMPANY
*"----------------------------------------------------------------------
DATA: WA LIKE T001.
DATA: WTAB LIKE WHERETAB OCCURS 1 WITH HEADER LINE.
CALL FUNCTION ’Z_ARIBA_PREFILTER’

EXPORTING
VARIANT = VARIANT
PARTITION = PARTITION
NAME = ’Z_ARIBA_COMPANY’
TABLES
WHERE = WTAB
EXCEPTIONS
INVALID_SELECTION_SIGN = 1
INVALID_SELECTION_OPTION = 2
OTHERS = 3.
DATA: SELECT_LIST LIKE SDIT_QRY OCCURS 5.
CALL FUNCTION ’Z_ARIBA_SELECT_LIST’

EXPORTING
STRUCTURE_NAME = ’ZXTCOMPANY’
INTERSECTION_STRUCT = ’T001’
TABLES
SELECT_FIELDS = SELECT_LIST
EXCEPTIONS
OTHERS = 1.
SELECT (SELECT_LIST) FROM T001

INTO CORRESPONDING FIELDS OF TABLE COMPANY_INFO
WHERE (WTAB).
CALL FUNCTION ’Z_ARIBA_COMPANY_EXT’

EXPORTING
VARIANT = VARIANT
TABLES
COMPANY_INFO = COMPANY_INFO
EXCEPTIONS

Example RFC Chapter 4 Configuring Pulls
OTHERS = 1.
ENDFUNCTION.
Within the declaration of Ariba Buyer pull RFCs, you find the extension structures or
structures that define the fields returned:
*" TABLES
*" COMPANY_INFO STRUCTURE ZXTCOMPANY
The call to Z_ARIBA_SELECT_LIST uses the structure to select the fields in the structure
into the table that is returned.
Before the RFC begins processing, it makes a call to Z_ARIBA_PREFILTER. It passes the
variant, partition, and name of the calling RFC, together with a working table. You
can use this information to edit Z_ARIBA_PREFILTER to change data or perform other
processes before the RFC runs:
CALL FUNCTION ’Z_ARIBA_PREFILTER’
EXPORTING
VARIANT = VARIANT
NAME = ’Z_ARIBA_COMPANY’
TABLES
WHERE = WTAB
EXCEPTIONS
INVALID_SELECTION_SIGN = 1
INVALID_SELECTION_OPTION = 2
OTHERS = 3.
The RFC selects company code fields from T001. When it finishes, the RFC executes
the customer exit function, Z_ARIBA_COMPANY_EXT. It passes the variant, partition,
and the table it exports, COMPANY_INFO, so you can make changes to the data:
CALL FUNCTION ’Z_ARIBA_COMPANY_EXT’
EXPORTING
VARIANT = VARIANT
TABLES
COMPANY_INFO = COMPANY_INFO
EXCEPTIONS
OTHERS = 1.

Chapter 5
Configuring Pushes
This chapter explains how SAP administrators and Ariba Buyer personnel can
configure Ariba Buyer development classes to change the data Ariba Buyer pushes in
purchase orders and good receipts.
Ariba Buyer RFCs offers the following means of configuring pushes on your SAP
system:
• Push extension structures
• Screen field mappings
• Purchase order and goods receipt filtering
• ZARIBTVARV parameters
This chapter explains the first two means of configuring pushes. You can learn about
how to configure Ariba Buyer RFC parameters in Chapter 6, “Parameter
Configuration.” This chapter also explains how to configure your TIB/R3 Adapter
and Ariba Buyer RFCs so you can watch and test data pushes from
TIB/MessageBroker worksheets.
The terms and explanations in this chapter assume a working knowledge of the
material in Chapter 4, “Configuring Pulls.”

Push Extension Structures Chapter 5 Configuring Pushes
Push Extension Structures

Ariba Buyer push RFCs offer extension structures that work like those for pulls. The
extension structures allow you to add fields or columns to the data Ariba Buyer sends
to SAP.
The purchase order push RFC, Z_ARIBA_PO_PUSH, offers the following extension
structures:
• ZXTPOHEADR—for header information
• ZXTPOITEMS—for line item information
• ZXTPOACCNT—for accounting information
• ZXTPOERR—for error messages the RFC sends to Ariba Buyer (not part of the push)
The goods receipt push RFC, Z_ARIBA_GR_PUSH, offers the following extension
structures:
• ZXTGRITEMS—for line item receiving information
• ZXTGRERR—for error messages the RFC sends to Ariba Buyer (not part of the
push)
You must ensure that the corresponding worksheets set values for any fields you add
to the extension structures. The error message structures, ZXTPOERR and ZXTGRERR,
are for pulling error data into Ariba Buyer. For general information on extension
structures and how they work, refer to “Pulling Additional Fields Into Ariba Buyer”
on page 46.
If you add new fields to push extension structures, you also need to define and map
these fields in the screen field mappings, as explained below.
Screen Field Mappings

Ariba Buyer pushes orders into SAP by populating fields within the SAP purchase
order entry screens, and Ariba Buyer pushes goods receipts to SAP by populating the
fields within SAP goods receipts entry screens. The Ariba Buyer RFC determines
which fields to push and what information the fields contain through special tables for
field mappings.

Chapter 5 Configuring Pushes Screen Field Mappings
• What field mappings do
• Data push mapping tables
• Sources of data for push tables
What Field Mappings Do

The Ariba Buyer development classes allow you to modify the following kinds of
SAP screen field information:
• You can tell Ariba Buyer RFCs in which fields in a screen to insert or set values.
• You can tell Ariba Buyer RFCs in which fields in a screen not to insert or set
values. You can change or remove the fields that Ariba Buyer RFCs set for
purchase orders or goods receipts as part of your default Ariba Buyer RFC
configuration.
• You can tell Ariba Buyer RFCs where to find the information to place within a
given field, for example, from a purchase order or goods receipt internal table or
elsewhere in your SAP system.
Data Push Mapping Tables

Ariba Buyer provides tables that offer specific mappings from the data Ariba Buyer
includes in purchase orders and good receipts to individual fields in SAP entry
screens. There are two kind of tables:
• ZAR6 tables—tables that comprise part of the Ariba Buyer RFCs that you must
never modify
• ZARC extension table—tables that are available for you to edit and change
There is one of each kind of table for purchase orders and goods receipts:
• ZARPOFMAP—Ariba Buyer RFC Purchase Order Mapping

ZARPOFMAP is the table that describes the SAP purchase order fields that Ariba
Buyer RFCs set as part of a default configuration, including a mapping between the
Ariba Buyer RFC internal sources and the purchase order desintation fields. Do not
modify this table.
• ZARPOFMAPX—Purchase Order Mapping Extension

Screen Field Mappings Chapter 5 Configuring Pushes
ZARPOFMAPX is the extension table that you use to instruct Ariba Buyer RFCs to
add, remove, or modify the purchase order fields that Ariba Buyer RFC set. The
table maps from Ariba Buyer purchase order extension tables to SAP purchase
order screen fields.
• ZARGRFMAP—Ariba Buyer RFC Goods Receipt Mapping

ZARGRFMAP is the table that describes the SAP goods receipts fields that Ariba
Buyer RFCs set as part of a default configuration, including a mapping between the
Ariba Buyer RFC internal sources and the goods receipt destination fields. Do not
modify this table.
• ZARGRFMAPX—Goods Receipt Mapping Extension

ZARGRFMAPX is the extension table that you use to instruct Ariba Buyer RFCs to
add, remove, or modify the goods receipt fields that Ariba Buyer RFCs set. The
table maps from Ariba Buyer goods receipt extension tables to SAP goods receipt
screen fields.
The tables for purchase orders and goods receipts work in exactly the same way. If
you understand how to use the extension tables for purchase orders, you should in
turn also understand how to use the extension table for good receipts. The text in this
chapter combines the explanation of these tables.
Note: You may customize only the extension tables, ZARPOMAPX and
ZARGRFMAPX. Do not modify ZARPOFMAP or ZARGRFMAP. The
extension tables provide all the utilities you might need to modify or remove
fields in your default Ariba Buyer RFC configuration.
Sources of Data for Push Tables

You can acquire the value you set or change for an extension table from the following
locations. The value must reside somewhere within a table on your SAP instance:
• From an SAP partition extrinsic or intrinsic field from the Ariba Buyer object
model or TIB/MessageBroker worksheet
• From an external data source you read into an Ariba Buyer purchase order or goods
receipt TIB/MessageBroker worksheet
• From other tables within your SAP system
This section explains how to use fields available within your SAP system. This
section does not explain how to send new fields to Ariba Buyer RFCs; it describes
only how to map them to screens.

Chapter 5 Configuring Pushes Mapping Fields for Orders or Receipts
The following documents explain how to push new fields to your Ariba Buyer RFCs:
• Ariba Buyer Customization Reference Guide
Mapping Fields for Orders or Receipts

The process of mapping fields for purchase order or goods receipt pushes consists of
three steps:
1. Find the screen field to map.
2. Find the source field.
3. Edit the corresponding extension table.
These steps are related to each other and can become complex. You might find it
easier to complete each of these steps in a separate SAP GUI client, and to keep all
three SAP GUI clients open, for cross reference, until you finish your field mappings.
Finding the Screen Field to Map

The first step in mapping new fields is to determine the destination of the field you
wish to map in either the purchase order or goods receipt screens. Use the following
steps to locate the table information you need.
▼ To locate the table destinations:
1. View a purchase order or goods receipt.

In order to find the field you need, you must either display an existing
document or create a new one. To do so, use one of the following transaction
codes:
• ME23—displays existing purchase orders
• ME21—creates new purchase orders
• MB03—displays existing goods receipts
• MB01—allows you to create new goods receipts

Mapping Fields for Orders or Receipts Chapter 5 Configuring Pushes
If you choose to create a new document, be prepared to enter any necessary

information, and remember not to submit the document when you finish.
2. Find the field.

If you chose to create a new purchase order or goods receipt, navigate
through the SAP GUI until you find the field you wish to map, entering
information as necessary.
If you chose to display an existing purchase order or goods receipt, enter the
purchase order or material document number or use the selection box to
locate a document on your system to display. Then, navigate through the
SAP GUI until you find the field you wish to map.
3. Find the field information.

Select the field you wish to map and press the F1 key. In the help screen
which appears, choose the Technical info button. The screen that appears
provides most of the information you need to enter in the extension table
about the destination field:
• Program name
• Screen number
• Table name
• Field name
Write down this information, or keep your SAP GUI open and use another
SAP GUI client to find the source field and edit the extension table.
Finding the Source Field

You need to know two things about the source of a field mapping:
• The table from which the data comes
• The field name

Chapter 5 Configuring Pushes Mapping Fields for Orders or Receipts
Mapping from Ariba Buyer RFC Import Tables
You may decide to map from the tables that Ariba Buyer purchase order and good
receipt RFCs use on your SAP system. The Ariba Buyer RFC tables function as
import parameters from TIB/MessageBroker worksheets. To map from them, you can
pull from any of the import tables or extension table fields for the following RFCs:
• Z_ARIBA_PO_PUSH
• Z_ARIBA_GR_PUSH
Editing the Extension Table

Perform the following steps to map fields that exist within your SAP system,
including those within Ariba Buyer RFC internal tables:
Note: You make changes to the extension table by adding new rows, not by
adding new columns.
▼ To edit extension tables:
1. Use transaction SE11.

Access the initial screen of the Data Dictionary and enter one of the
following data push extension tables within the Object name field:
• ZARPOFMAPX—to map fields for Ariba Buyer purchase orders
• ZARGRFMAPX—to map fields for Ariba Buyer goods receipts

Click Display.
2. In the Display Fields window, open Utilities>Create contents.
3. Click the F5 key or the New Entries button.
4. Enter the following information:
• Short text—a short description of the mapping for documentation purposes
• Ariba Variant—the name of the Ariba Buyer SAP variant from which the
purchase order or goods receipt originates
• Ariba Partition—the name of the Ariba Buyer SAP partition from which
the purchase order or goods receipt originates
• Program name—the program name of the destination screen field

Changing and Removing Fields Chapter 5 Configuring Pushes
• Screen number—the number of the destination screen
• Table name—the destination table of the screen field
• Field name—the destination field
• Import parameter—the source import parameter or other table
• Field name—the source field from the import parameter or other table
• Deletion Flag—this field is for removing field mappings from your default
Ariba Buyer RFC configuration. Leave it blank if you are creating a new
field mapping
5. Choose the Display>Change button and activate your changes.
Changing and Removing Fields

The purchase order and goods receipt extension mapping tables allow you to change
or delete the default field mappings that Ariba Buyer RFCs use.
To change a mapping of a field that Ariba Buyer RFCs map, enter a mapping for the
field you need to change within the extension table, together with the relevant source
information.
If you need to remove a mapping of a field that Ariba Buyer RFCs already maps,
enter a mapping for the field you need to change within the extension table, but place
an “X” in the Deletion Flag field.
Filtering and Customer Exit Functions

The purchase order and goods receipt RFCs offer several customer exit functions that
allow you to filter the data they push. You may use these exit functions to manipulate
data at several different stages, from when the RFCs first import it to the final batch
data control (BDC) posting. The customer exit functions work the same for pushes as
they do for pulls, the only difference is the direction in which the data is moving.

Chapter 5 Configuring Pushes Unsupported Push Features
The purchase order push and goods receipt push RFCs offer the following customer
exit functions, that execute in the following order:
• Exits before any processing begins:

Z_ARIBA_PO_PUSH_EXT
Z_ARIBA_GR_PUSH_EXT
• Exits before the batch data control (BDC) push:

Z_ARIBA_PO_PUSH_BDCDATA_EXT
Z_ARIBA_GR_PUSH_BDCDATA_EXT
• Exits at the end for testing error conditions:

Z_ARIBA_PO_PUSH_ERRORS_EXT
Z_ARIBA_GR_PUSH_ERRORS_EXT
You can use these exit functions to manipulate purchase order and goods receipt
pushes in ways that field mappings do not offer.
Unsupported Push Features

The field mappings for Ariba Buyer push RFCs do not offer the following features:
• BAPIs
• Additional tables
• Additional screens
The following text explains these limitations and offers suggestions about how to
work around them.
BAPIs
SAP’s BAPI mechanism for purchase orders and goods receipts does not support
configuration of screen fields through Ariba Buyer RFCs. If you need to add Ariba
Buyer extrinsic fields to BAPI objects, you must do so within the appropriate
TIB/MessageBroker worksheets, not within the mapping tables.

Unsupported Push Features Chapter 5 Configuring Pushes
Additional Tables
You may only add extrinsic fields to the header and line item tables for purchase
orders or goods receipts. The extension table mechanism does not allow you to create
new tables and add fields to them. If you need the Ariba Buyer push RFCs to use
additional tables, you can write the code to do so within the customer exit functions.
Additional Screens
The Ariba Buyer push RFCs and mapping files navigate through SAP purchase order
screens and goods receipt screens in a predefined order, based on the configuration of
SAP screens in a basic SAP instance. If you have changed the order or content of the
purchase order or goods receipts screens on your SAP system, you may be able use
the customer exit functions to implement the changes you need to Ariba Buyer RFCs.
You cannot use the mapping mechanism to map to fields in screens that are not
included in the RFCs navigation sequence.
For example, you could use the customer exits that execute before the BDC push to
insert rows as appropriate within the BDC table. See the Ariba Buyer push RFC
ABAP code for more information.

Chapter 6
Parameter Configuration
You can change the way Ariba Buyer RFCs function by changing parameters in the
RFCs. This chapter explains how to change Ariba Buyer RFC parameters and
describes the parameters available. The material in this chapter is appropriate for SAP
administrators.
This chapter presents:

• ZARIBTVARV
• Editing ZARIBTVARV parameters
• Default parameters
• Parameter descriptions
ZARIBTVARV
You can configure all Ariba Buyer RFC parameters in one location, through the
ZARIBTVARV structure. By editing the parameter configurations in ZARIBTVARV, you
can:
• Perform static filtering on data pulls through TVARV-like selection options
• Configure parameters that affect how Ariba Buyer RFCs function
For information on performing static filtering, refer to ZARIBTVARV in Chapter 4,

“Configuring Pulls.”
This chapter explains how to use ZARIBTARV to configure Ariba Buyer RFCs.

ZARIBTVARV Chapter 6 Parameter Configuration
ZARIBTVARV contains a special field, called TYPE, that determines whether an entry is
for static filtering or parameter configuration. For changing parameters, you must
enter a P in the TYPE field.
(If you set the field to S, you can use ZARIBTVARV for static filtering, see “Static
Filtering” on page 55.)
In your default configuration, ZARIBTVARV does not contain any parameters. The
Ariba Buyer RFCs that call ZARIBTVARV already contain certain default values that
they use. Enter a value in ZARIBTVARV if you want to change the default values.
▼ To edit ZARIBTVARV parameters:
1. Run transaction /nSM30.

Access the Maintain Table View screen, enter ZARIBTVARV in the Table/view
field, and click Maintain.
2. Choose Edit>New Entries or click New entries button.

Chapter 6 Parameter Configuration ZARIBTVARV
3. Enter the information for your parameter in the screen that appears.
4. Save your changes (F11).
5. You might see a transport POP-UP window asking to enter change request.
If you do, click Create Request button to create a new request or enter a
request number already exists in the Request field.
6. Click Check box (Continue button) to create a transport request.

Default Parameters Chapter 6 Parameter Configuration
Default Parameters
The following table lists each possible ZARIBTVARV parameter, its default value, and
the RFC that references it. The following sections in this chapter explain what these
parameters do and offer other possible values.
Table 6. Default ZARIBTVARV Values
Parameter Name Default Calling Function

BALANCE_SHEET_ACCOUNTS determine_from_ Z_ARIBA_GENERAL_LEDGER
ki281
COST_CENTER_DAYS_PAST 7 Z_ARIBA_COST_CENTER
COST_CENTER_MSG_TYPE ZATCOS Z_ARIBA_COST_CENTER
DO_GET_LAST_CHANGE_DATE Last change date Z_ARIBA_LAST_CHANGE_DATE
from change
document header
table
GENERAL_LEDGER_DAYS_PAST 7 Z_ARIBA_GENERAL_LEDGER
GENERAL_LEDGER_MESSAGE_TYPE ZATGLM Z_ARIBA_GENERAL_LEDGER
MINORITY_VENDOR_USE_HEADOFFICE T Z_ARIBA_MINORITY_VENDOR
PO_PUSH_DIRECTCC_DOC_TYPE AR Z_ARIBA_PO_PUSH
PO_PUSH_ERP_DOC_TYPE NB Z_ARIBA_PO_PUSH
PO_PUSH_ERPCC_DOC_TYPE AR Z_ARIBA_PO_PUSH
PO_PUSH_PCARDCC_DOCTYPE AR Z_ARIBA_PO_PUSH
Z_ARIBA_CURR_CONV_BANK_RATE B Z_ARIBA_CURRENCY_CONVERSION
Z_ARIBA_CURR_CONV_DAYS_PAST 60 Z_ARIBA_CURRENCY_CONVERSION
Z_ARIBA_CURR_CONV_EURO_RATE EURO Z_ARIBA_CURRENCY_CONVERSION
Z_ARIBA_GR_PUSH_DISPLAY_MODE N Z_ARIBA_GR_PUSH
Z_ARIBA_INTERNAL_ORDER_AUART ‘‘ Z_ARIBA_INTERNAL_ORDER
Z_ARIBA_PO_DETAILS_DAYS_PAST 21 Z_ARIBA_PO_DETAILS
Z_ARIBA_PO_PUSH_DISPLAY_MODE N Z_ARIBA_PO_PUSH
Z_ARIBA_RELEASE_AUTHORITY_CNAM FRG_GNETW Z_ARIBA_RELEASE_AUTHORITY
Z_ARIBA_VENDOR_ONLY_COUNTPORGS 1 Z_ARIBA_VENDOR_ONLY
Z_ARIBA_PO_PUSH_ALLOW_DUPS Checks for Z_ARIBA_PO_PUSH
duplicate POs

Chapter 6 Parameter Configuration Parameter Descriptions
Parameter Descriptions
This section groups parameters together and explains how to use them:
• Incremental loading parameters
• Minority vendor head offices
• Currency conversion rates
• Monetary characteristics
• Debugging pushes
• Internal order types
• Purchase order document types
• Vendor pull performance tuning
• General ledger balance sheet accounts
• Real time ALE/IDOC partition loading
• Duplicate PO handling
Incremental Loading Parameters

You can configure the Ariba Buyer RFCs to incrementally load data. Incremental
loads only pull data that has changed since the previous pull.
Incremental loading parameters consist of those which:
• Enable or disable incremental loading
• Define days past parameters
Turn Incremental Loading Off
Incremental loading is set by default. You must explicitly turn incremental loading
off. To turn off incremental loading set the following:
DO_GET_LAST_CHANGE_DATE = F
A value of F causes Ariba Buyer to load all data for every pull it makes.

Parameter Descriptions Chapter 6 Parameter Configuration
Days Past Parameters
The DAYS_PAST parameters allow you to configure how far back in days, the Ariba
Buyer RFCs look for certain data.
Table 7. Days Past Default Values
Parameter Description Default Value

Z_ARIBA_CURR_CONV_DAYS_PAST Keeps track of currency 60
conversion rates
Z_ARIBA_PO_DETAILS_DAYS_PAST Optional purchase order 21
details pull
You must ensure that the days past parameters for Ariba Buyer RFCs are values less
than or equal to the scheduled events in the SAP integration table.
Minority Vendor Head Offices

The Z_ARIBA_MINORITY_VENDOR RFC allows you change the way you pull minority
indicators so they come only from the individual entries in the central vendor master
record. The default is to use the minority status of the head office account through the
MINORITY_VENDOR_USE_HEADOFFICE parameter.
To find the indicator from the vendor itself set the following:
MINORITY_VENDOR_USE_HEADOFFICE = F
Currency Conversion Rates

The Z_ARIBA_CURRENCY_CONVERSION RFC calls ZARIBTVARV to look up
specifications for SAP currency conversion rates for banks or for the Euro:
• Z_ARIBA_CURR_CONV_BANK_RATE
• Z_ARIBA_CURR_CONV_EURO_RATE
The defaults are “B” and “Euro”.
Note: You can determine how far back in the past the RFC looks to pull
historical currency conversion information to deal with expenses from the
past through the following parameter, Z_ARIBA_CURR_CONV_DAYS_PAST.

Monetary Characteristics
The Ariba Buyer RFCs offer a special limited way of pulling monetary characteristics
to use in Ariba Buyer approval flows.
The Z_ARIBA_RELEASE_AUTHORITY_CNAM parameter specifies the monetary

characteristic value you use on your system to classify your release strategy. For
information on finding your monetary amount characteristic value, refer to
“Displaying and Setting Your Monetary Amount Characteristic Value” on page 122.
Debugging Pushes
Ariba Buyer RFCs offer two parameters that allow you to watch push operations fill
purchase order or goods receipt screens:
• Z_ARIBA_PO_PUSH_DISPLAY_MODE
• Z_ARIBA_GR_PUSH_DISPLAY_MODE
You may use these parameters to see what’s going on during a purchase order or
goods receipt push from Ariba Buyer to your SAP system. When you run
Z_ARIBA_PO_PUSH or Z_ARIBA_GR_PUSH, the parameters instruct the RFCs to show
the screens they fill up with data.
To watch the RFCs fill the screens with data through a single test of transaction se37
set the following:
Z_ARIBA_PO_PUSH_DISPLAY_MODE = T
Z_ARIBA_GR_PUSH_DISPLAY_MODE = T
You can also configure the TIB/R3 Adapter to invoke the RFC within the SAP GUI
from TIB/Message Broker worksheets that use RPC client plugins. For more
information, refer to “For example, you could use the customer exits that execute
before the BDC push to insert rows as appropriate within the BDC table. See the
Ariba Buyer push RFC ABAP code for more information.” on page 76.
Internal Order Types

Internal orders contain a field called AUART, which designates their order type. The
value of AUART determines whether or not SAP can use the internal order to create a
purchase order. The Ariba Buyer RFCs do not create purchase orders from internal
orders that have an AUART value specified with Z_ARIBA_INTERNAL_ORDER_AUART.

If you do not specify a value for AUART, your Ariba Buyer development classes
assume that they may create purchase orders from any internal order in which the
AUART field of the order master data (AUFK) has the following properties:
• Is not equal to a space
• Is not marked for deletion (LOEKZ)
• Is not already ordered or released
Purchase Order Document Types

By default, Ariba Buyer pushes complimentary copies, called carbon copies, of orders
Ariba Buyer sends to vendors to SAP. SAP uses these copies for accounting purposes.
However, Ariba Buyer can also push orders to SAP for SAP to send. Ariba Buyer
RFCs use order document types to keep track of which orders are for SAP to send and
which are complimentary copies.
By default, the Ariba Buyer RFCs designate carbon copies of orders with a document
type of AR and orders that SAP must send with a document type of NB. These
document types correspond to the BSART field on the purchase orders Ariba Buyer
pushes to SAP.
You can change the document type of a purchase order as it appears in your SAP
system from Ariba Buyer. For example, you may wish to configure a different
document type for Ariba Buyer orders or use a different type for SAP orders. You can
do so by setting the following ZARIBTVARV parameters:
• PO_PUSH_ERPCC_DOC_TYPE
• PO_PUSH_DIRECTCC_DOC_TYPE
• PO_PUSH_ERP_DOC_TYPE
PO_PUSH_ERPCC_DOC_TYPE is a carbon copy of orders Ariba Buyer sends through

the Ariba Network. PO_PUSH_DIRECTCC_DOC_TYPE is a carbon copy of orders Ariba
Buyer sends directly to vendors through methods such as fax or email.
PO_PUSH_ERP_DOC_TYPE is a document type for orders Ariba Buyer expects SAP to
send to vendors.
You can learn more about order types in the Ariba Buyer Procurement Guide.

Vendor Pull Performance Tuning

By default, Ariba Buyer RFCs pull only those vendors from SAP they find associated
with at least one purchasing organization.
The parameter, Z_ARIBA_VENDOR_ONLY_COUNTPORGS, provides a performance

tuning parameter for vendor pulls. Valid settings are 1 or 0; the default is 1. If 1, then
the RFC only selects vendors assigned to at least one purchasing organization. If 0,
the RFC pulls back all vendors without regard to any assigned purchasing
organizations.
The default setting of 1 pulls back a smaller set of data, but does so by executing two
select statements within the RFC code. The 0 setting pulls back more data that the
RFC refines further, but it does so through a single selection query. If you decide to
tweak the performance of vendor pulls, you must balance the trade off between the
smaller amount of data returned with option 1 and the time it takes to perform another
select statement on your own system. You might find it helpful to examine the actual
RFC code in Z_ARIBA_VENDOR_ONLY.
If you need to perform an incremental pull of vendor information, you can use an
ALE/IDOC pull. The ALE/IDOC only pulls new and changed vendors. For more
information on using ALE/IDOC, refer to “Ariba Buyer ALE/IDOC Configuration”
on page 105.
Using General Ledger Balance Sheet Accounts

You may decide that you would like to use general ledger accounts that are for
balance sheets for your procurement needs in Ariba Buyer. By default,
Z_ARIBA_GENERAL_LEDGER does not pull accounts for balance sheets, particularly if
your SAP system is configured to not allow this and it returns a hard error message
when a user attempts to do so.
You can tell Z_ARIBA_GENERAL_LEDGER to pull and use balance sheet accounts if you
enter a value of allow_balance_sheets for the BALANCE_SHEET_ACCOUNTS parameter.
You can also instruct the RFC to not use balance sheets, even if it is permitted on your
system, if you enter a value of disallow_balance_sheets.
If you need to perform an incremental pull of general ledger balance sheet accounts,
you can use an ALE/IDOC pull. The ALE/IDOC only pulls new and changed general
ledger accounts. For more information on using ALE/IDOC, refer to “Ariba Buyer
ALE/IDOC Configuration” on page 105.

Real Time ALE/IDOC Partition Loading

In order to configure the optional real time incremental loading feature, you must
enter certain parameters within ZARIBTVARV. For information on using these
parameters, refer to “Ariba Buyer Object Configuration” on page 113.
Duplicate PO Handling
By default, Ariba Buyer does not create duplicate purchase orders. In the RFC, Ariba
Buyer keeps track of the Ariba Buyer requisition IDs. When a PO is pushed, Ariba
Buyer checks to see whether it has already created a PO for the given requisition. If
so, it does not create a new PO but returns back the existing PO number.
If the Z_ARIBA_PO_PUSH_DUPS parameter is set, the RFC does not check for
duplicates.
Note: You should not change this parameter setting unless you are testing
with different Ariba Buyer instances on the same SAP machine.

Chapter 7
Account Assignment Categories
This chapter explains how Ariba Buyer uses SAP account assignment categories. It
presents the following information:
• An explanation of account assignment categories in SAP
• An explanation of Ariba Buyer accounting types for SAP partitions
• How Ariba Buyer decides to display or require account assignment categories

within its user interface
• Configuration ideas
The material in this chapter is appropriate for SAP administrators and Ariba Buyer
implementation personnel.
What Are Account Assignment Categories?

SAP uses account assignment categories within purchasing documents to specify
how to assign a line item expenditure to accounts, such as assets, WBS elements, or
cost centers. Account assignment categories determine what information a user must
provide for a line item, such as the account number of an asset.
For example, if you purchase an elevator for your company’s building through Ariba
Buyer, you can apply the cost of the elevator through an asset account category. You
might do so because buildings are usually considered assets. Quite often, there are
special tax and accounting considerations for expenses related to the improvement or
maintenance of assets.
These considerations can make it necessary for your SAP system to handle expenses
for assets in a different manner than expenses for other items such as manufacturing
raw materials or office supplies. These differences affect the kinds of information

Displaying Fields and Requiring User Input Chapter 7 Account Assignment Categories
SAP displays to users who enter asset line items, and what they must do with this
information. Account assignment categories let SAP know how to handle these
differences.
For example, if a user chooses an asset account assignment category, then SAP
doesn’t need the user to enter any information related to cost centers. When possible,
SAP includes default values for required information based upon current data.
You can configure all existing SAP account assignment categories to display and
require the accounting fields you want. If the default account assignment categories
do not suit your needs, you can create your own.
Ariba Buyer Account Assignment Category Pulls

Ariba Buyer pulls account assignment categories from SAP. The pull from SAP
includes information about how the Ariba Buyer user interface must treat account
assignment categories:
• To know what types of accounts to display in the user interface
• To know whether to require the user to choose or provide certain types of account
information in the user interface
Although SAP supports several account assignment categories, your default Ariba
Buyer SAP partition only pulls the following categories:
• K—Cost center
• P—WBS element project
• F—Internal order
• A—Asset
Displaying Fields and Requiring User Input

Ariba Buyer pulls account category information and uses it in ways that are similar to
SAP. This section explains how SAP allows you to configure account assignment
categories, and then explains how Ariba Buyer pulls, displays, and handles account
assignment categories in the user interface.

Chapter 7 Account Assignment Categories Displaying Fields and Requiring User Input
SAP Accounting Field Configuration

SAP has a set of information fields that it can display or require for any account
assignment category. You can switch between various types of display and kinds of
user modification by choosing one of four options:
• Required Entry—the SAP GUI displays the accounting field and requires input from
the user.
• Optional Entry—the SAP GUI shows the accounting field, a user can change it, but
the SAP GUI does not require the user to make any changes.
• Display—the SAP GUI shows accounting field, but the user cannot change it.
• Suppressed—the SAP GUI does not show the accounting field.
You can maintain these properties for each account assignment category through the
the Change View “Account Assignment Categories”: Details screen, through Goto>Details in
transaction OME9.

Ariba Buyer Accounting Types Chapter 7 Account Assignment Categories
For example, the default asset account assignment category settings within an IDES
system are as follows.
• Display and require the user to enter an asset name or ID.
• Display but do not require the user to enter the following:
• Asset sub-number
• Business area
• Deletion indicator
• Details account assignment block
• Quantity/Percent for material account assignment
• Ship-to party
• Unloading point
• Display the following for informational purposes, but do not allow the user to
change:
• General ledger account
• Project
• RK/PPC order
• Do not display remaining fields.
Ariba Buyer Accounting Types

SAP offers more types of accounts than Ariba Buyer. In fact, some of the fields that
you can configure within SAP for account assignment categories refer to types of
accounts: profit centers, cost centers, general ledgers, and so forth.
Ariba Buyer represents SAP accounts as a special object called a ClusterRoot. Your
default configuration for Ariba Buyer for an SAP partition offers only five kinds of
account objects:
• asset—Asset

Chapter 7 Account Assignment Categories Field Status Group Strings
• cost center—Cost center
• general ledger—G/L Account
• internal order—RK/PPC order
• WBS element—Project
Ariba Buyer instantiates these kinds of objects with the data it pulls from your SAP
system. That way, users can choose the correct data they need to make purchase
orders in Ariba Buyer that are valid in SAP.
Ariba Buyer uses SAP account assignment category information to determine what
users need to enter for a line item. Ariba Buyer and SAP use the information in a
similar fashion, to dynamically change the user interface for creating purchase orders.
Ariba Buyer pulls and uses SAP account assignment category information as a basis
for the behavior of the user interface. Depending upon how you configure SAP, Ariba
Buyer users may or may not need to select one of the five account types for a given
line item.
Field Status Group Strings

SAP stores information about when to display or require user input for account
assignment categories in field status group strings. SAP uses theses strings to store
the settings previously discussed in the Change View “Account Assignment Categories”:
Details screen, in transaction OME9.
There is one field status group string for each account assignment category in your
SAP instance.The strings reside in table T162K, within field faus1. Ariba Buyer pulls
the strings and interprets them to handle accounting fields within the user interface.
Each string consists of a series of four characters or spaces. Each of the four
characters corresponds to the four settings SAP allows for accounting fields for a
given account assignment category. Ariba Buyer treats these settings differently than
SAP within the user interface.

Field Status Group Strings Chapter 7 Account Assignment Categories
Table 8. T162K-FAUS1 Accounting Field UI Properties
Character SAP GUI Meaning Ariba Buyer Meaning

‘+’ (plus sign) Required Entry Ariba Buyer displays the field and
requires user input.
‘.’ (period) Optional Entry Ariba Buyer displays the field, and the
user can decide change it or not
‘*’ (asterisk) Display Ariba Buyer does not display this field
because it does not require user input.
‘-’ (minus sign) Suppressed Ariba Buyer does not display this field
because it is not relevant.
The position of each character within the string determines the accounting field to
which it applies. For example, in an IDES system the field status group strings for the
default Ariba Buyer account assignment categories are as follows:
The position of the characters within the string corresponds to the accounting fields
within the OME9 maintenance screen. Ariba Buyer does pull all the characters in the
string, but your default configuration only uses those that apply to the five account
types. The character positions relevant to a default configuration for an SAP partition
are as follows:
• Cost Center — position 10
• Internal Order — position 11
• WBS Element — position 12
• Asset — position 24
• General Ledger— position 51
For example, the positions for an asset category from an IDES system resemble the
following diagram:

Chapter 7 Account Assignment Categories Field Status Group Strings
Ariba Buyer interprets this field status group string in the following way:
• The cost center character has an empty space, which means it is not relevant to
asset line items and does not appear in the Ariba Buyer user interface.
• The internal order, WBS element (project), and general ledger characters are
asterisks, *. Ariba Buyer displays them, but does not require the user to enter a
value.
• The asset character is a plus, +. Ariba Buyer displays the asset field in the user
interface and requires the user to enter a value.
Ariba Buyer pulls the entire field status group, even though the default configuration
examines only five of the character positions. Ariba Buyer does so in case you wish to
customize Ariba Buyer to use and display other accounting type objects.
For example, if you wanted to use profit centers within Ariba Buyer, you could create
profit center objects and write code within Ariba Buyer that examines the character
position for profit centers, position 41.
Your SAP partitions create objects with unique names based upon the position of the
field status characters that you can use to manipulate corresponding accounting
objects, should you decide to implement them. (See
ariba/variants/<variant>/partitions/<partition>/data/FieldStatusToAccountingFieldNameMap.csv.)
If you implement your own SAP accounting objects for Ariba Buyer, the status
strings are available for you to use. You can modify the RFCs that pull account
categories with selection filters in ZARIBTVARV to include categories for custom
accounting objects.

Using Account Assignment Category Pulls Chapter 7 Account Assignment Categories
The implementation of a new accounting object in Ariba Buyer is beyond the scope of
this document, but generally includes creating a new ClusterRoot object that resembles
the existing accounting types. For more information, see the Ariba Buyer API Guide
Viewing Field Status Group Strings

Perform the following steps to view the field status group strings that Ariba Buyer
RFCs use for account assignment categories on your SAP instance.
▼ How to view Ariba Buyer field status group strings:
1. Run transaction SE37 to access the ABAP/4 Function Library: Initial Screen.
2. Type “Z_ARIBA_ACCOUNT_CATEGORY” in the Function module field and choose

the Sngl. test button. The content of the display will change.
3. In the Value column, enter your Ariba Buyer variant name and partition.
For example, enter “vsap” and “sappart1”, and choose the execute green
check button.
4. Highlight the top value for the No. of lines Before Start column and choose the
choose magnifying glass button.
Using Account Assignment Category Pulls

You might want to configure account assignment pulls to provide display information
for a new accounting object you created in Ariba Buyer.
Within SAP, you could pull the field status string by selecting the new account
assignment category through an entry in ZARIBTARV for the account assignment
category RFC, Z_ARIBA_ACCOUNT_CATEGORY.
Ariba Buyer provides a sample class file, ariba.sap.common.AACUtil, that you can
examine to get ideas about how to validate custom account assignment categories
with their field status strings. You could use the following method, showField, within
an AML UI description. The comments provide good summary of this chapter:
/**
Given a field on Accounting for the SAP variant, and a given
account assignment category on that Accounting object,
determine if the accounting field should show up. This is
based on SAP’s account category property called FieldStatus

Chapter 7 Account Assignment Categories Using Account Assignment Category Pulls
Group. We pull this field status group back from SAP when we
pull AACs. The field status group is a string of dots,
slashes, plusses, and stars. Each of these means a different this.
’Optional’ (’.’) means the accounting field should be shown,

but does not require any kind of input.
’Suppressed’ (’-’) means the accounting field should not be

shown at all.
’Required’ (’+’) means the accounting field requires input,

and therefore it should be shown.
’Display’ (’*’) in SAP means visible, but no input possible.

In Ariba that means that the field is simply not visible. SAP
has this option ’display’ for when it defaults values to an
accounting field and wants the field to be visible for
informational purposes only. Since we don’t do any defaulting
like that, it’s not necessary to show such a field.
@aribaapi external
*/
public static boolean showField (String fieldName, ValueSource aac)
{
if (null == aac) {
return false;
}
String fstag = (String)aac.getFieldValue("FieldSelectionString1");
char code = fstag.charAt(positionForField(fieldName));
if (’.’ == code) {
// Optional
return true;
}
else if (’-’ == code) {
// Suppressed
return false;
}
else if (’+’ == code) {
// Required
return true;
}
else if (’*’ == code) {
// Display-only
return false;
}
else {
// error handling
return false;
}
}

Using Account Assignment Category Pulls Chapter 7 Account Assignment Categories

Chapter 8
Real Time Integrations
This chapter explains how to configure your SAP system to load data in an
incremental, real time fashion into Ariba Buyer. It also presents ALE/IDOC
configuration necessary for Ariba Buyer to properly pull company code information.
This chapter is for SAP administrators who configure Ariba Buyer integration. The
material assumes an understanding and expertise regarding SAP IDOC configuration
and administration. This chapter also contains material appropriate for Ariba Buyer
administrators, including those who manage TIB/ActiveEnterprise products from
TIBCO Inc.
The term incremental load refers to the process of pulling new or changed data into
existing objects and tables. In comparison, non-incremental loading, or full loading,
recreates and repopulates all data. Incremental loading provides a more efficient and
manageable way of dealing with huge amounts of data because it does not reload all
data from your SAP system.
SAP integration with Ariba Buyer through TIBCO Inc. products allows you to
perform incremental updates in a real time fashion. A real time update changes the
data within Ariba Buyer as it changes within SAP.
Organization
This chapter presents a lot of tasks for real time integration. Most of these tasks are
related to ALE/IDOC configuration on a SAP system. Some are not. The goal of these
tasks is to create partner profiles for Ariba Buyer partitions.
ALE stands for Application Linking and Embedding, a feature that allows data
communication with between an SAP system and another process or SAP system.
ALE provides for a variety of data communication methods, including synchronous
and asynchronous protocols.
IDOC stands for Intermediate DOCument, a feature that allows SAP to represent data
in coherent, self describing containers. IDOCs represent data and ALE transfers that
data.

Chapter 8 Real Time Integrations
Most of the ALE/IDOC components which you install or configure for real time
integration reside within a partner profile. Partner profiles contain the following
pieces:
• Change pointers
• Message types
• Logical systems
• Distribution models
• Ports
• RFC destinations
• Program IDs
This chapter explains how to configure these pieces to work with Ariba Buyer,
TIB/ActiveEnterprise products, and Ariba Buyer development classes on your SAP
system.
This chapter contains the following sections:
• Getting Started—presents the configuration and tasks you must complete before
moving on to the main tasks of this chapter. You may have already performed the
tasks in this section.
• Ariba Buyer Repository and Worksheet Configuration—presents configuration

tasks for TIB/Repository and TIB/MessageBroker.
• Ariba Buyer ALE/IDOC Configuration—presents the specific ALE/IDOC

components that you must create.
• Ariba Buyer Object Configuration—explains how to configure Ariba Buyer objects

within SAP to take advantage of ALE/IDOC configuration.
• Maintenance—explains how to ensure that your data is kept up-to-date.

Chapter 8 Real Time Integrations Getting Started
Getting Started
In order to perform most of the tasks in this chapter, you must first do the following:
• Configure ALE/IDOC on your SAP system
• Install the Ariba Buyer ALE/IDOC related transports
• Install Ariba Buyer
This section explains how to perform these tasks or refers to you to appropriate
documentation. If you have already performed these tasks, you can move on to the
next section.
Configuring ALE/IDOC
Real time incremental integration with an SAP instance is possible through ALE and
IDOC mechanisms.
There are two steps you must complete to configure ALE/IDOC:
1. Configure a base logical system
2. Set up global company codes
Configuring a Base Logical System
A logical system (LS) represents the source or destination of data exchanged with an
SAP instance. ALE treats all sources and destinations as logical systems, whether
they consist of R/3 systems or not.
Logical systems are client independent. (Clients represent the highest order of data
organization available with an R/3 system.) Every client that uses ALE must have a
unique base logical system that represents the client in data communications. You can
think of a base logical system as being analogous to the unique IP address in TCP/IP.
SAP uses the term inbound to describe data communication that arrive at a base
logical system, and SAP uses the term outbound to describe data communication that
a base logical system sends. For example, an Ariba Buyer push operation could create
an inbound data communication, and a pull operation could create an outbound data
communication.
If you have not already configured a base logical system for the client with which
Ariba Buyer integrates, you must do so.

Getting Started Chapter 8 Real Time Integrations
In general, this configuration consists of the following tasks:
• Defining a base logical system for your SAP instance
• Associating the base logical system with the relevant client
▼ To define a base logical system:
1. Run transaction SALE.
2. For 3.1I: choose Basic configuration>Set up logical system>Maintain logical

system.
For 4.0B: choose Basic Settings>Set up logical system>Maintain logical system.

For 4.5B, 4.6B: choose Basic Settings>Logical Systems>Define Logical System.
3. Choose the green check for any warnings about client independence.
4. Choose the New Entries button.
5. Enter a name for the logical system.

For the base logical system: you may wish to adopt a naming standard, such
as fooCLNTbar, where foo is the instance name and bar the client.
6. Enter a description for the base logical system.
7. Save.
▼ To associate a base logical system with a client:
1. Run transaction SCC4.
2. Select the row that includes an entry for your client.
3. Choose the details push button or F2.
4. For the Logical System field, enter the base logical system you created above.
5. Save.
You can perform other tasks to configure logical systems. This text presents only
those most relevant to Ariba Buyer integration and assumes that you use default
settings.

Chapter 8 Real Time Integrations Getting Started
Setting Up Global Company Codes
This section explains how to configure global company codes for the following Ariba
Buyer features:
• Purchase order and receipt integration that works for all company codes on all your
SAP systems
• Real time incremental loading of system wide data into Ariba Buyer through
ALE/IDOC mechanisms
Global organizational units provide a central naming location for all company codes
and business areas. SAP uses the term local to describe organizational units for a
given SAP system. Each SAP system must assign its local organizational units to
corresponding global units. You can do so through the IMG.
▼ To set up global company codes:
2. For 3.1I choose Distribution (ALE)>Distribution scenarios>Global organizational

units>Set up global company codes.
For 4.0B choose Distribution (ALE)>Application Distribution and

Interfaces>Global Organizational Units>Set up global company codes.
For 4.5B, 4.7B choose Distribution - ALE>Standard ALE Business

Processes>Global Organizational Units>Set Up Cross-System Company Codes.
3. Choose Cross-system company codes.
4. Click New entries to create the cross system list of global company codes you
use.
You may wish to name the global company codes to reflect any
corresponding local company codes. For example, a local company code of
1000 might have a corresponding global company code of GL1000.
5. Save.
6. Green arrow back and choose Assign cross-system co. code -> chrt of accts.
7. Enter chart of accounts entries for each global company code.
8. Save.

Getting Started Chapter 8 Real Time Integrations
9. Green arrow back and choose Assign company code -> Cross-system company
code.
10. For 3.1I and 4.0B: in the X-system CoCde column, select or enter global
company codes to represent any corresponding local company codes.
For 4.5B and 4.6B: in the Global CoCde column, select or enter global
company codes to represent any corresponding local company codes.
11. Save.
Installing ALE/IDOC Transports

Your Ariba Buyer distribution media contains SAP transport files that install a variety
of items on your system to enable integration with Ariba Buyer. You must first fully
install all transports necessary for Ariba Buyer configuration before you complete the
steps in the following sections.
Ariba Buyer transports change a great deal from release to release. You can learn how
to fully install Ariba Buyer transports from the following documents:
• The Ariba Buyer Release Guide for your version of Ariba Buyer
• The README.txt file that resides in the following location where you installed Ariba
Buyer:
~\configureOptions\sap\config\variant\trans\README.txt
The ALE/IDOC related transports install the following items:
• An IDOC development class ZATI
• Ariba Buyer message types:

• ZATCRE
• ZATGLM
• ZATCOS
• Assignment data of message types to IDOCs
• Additional message type data
• ALE activation of change pointers for Ariba Buyer message types
• Activation of change pointers for document items

Chapter 8 Real Time Integrations Ariba Buyer Repository and Worksheet Configuration
Installing Ariba Buyer

Before you can complete all the tasks in this chapter you must first:
• Configure databases for Ariba Buyer and the TIB/Repository as described in the
following documents:
• Ariba Buyer Installation Guide
• TIB/Repository Installation and Administration
• Configure your SAP system as described in “SAP Setup” on page 35.
• Fully install Ariba Buyer, without initializing any databases, as described in the
Ariba Buyer Installation Guide.
Database Initialization Suggestion
If you prefer, you can initialize only those database items necessary to complete the
tasks in this chapter instead of creating your entire Ariba Buyer database and filling it
with SAP data. The following initdb options are all you need complete.
▼ To initialize only for ALE/IDOC:
1. Run initdb -emptytibco to create database tables for the TIB/Repository.
2. Run initdb -loadtibco to enter SAP integration data and worksheets into the
TIB/Repository.
3. Complete the rest of the tasks in this chapter.
4. Later, perform initdb -initdb or some other combination of initialization options

to load data into Ariba Buyer.
Ariba Buyer Repository and Worksheet Configuration

This section presents tasks you must complete within the TIB/ActiveEnterprise
applications that Ariba Buyer provides as part of your default configuration:
• Configure Repository RFC Server Connection Pools
• Configure partition case in worksheets

Ariba Buyer Repository and Worksheet Configuration Chapter 8 Real Time Integrations
Configuring Partition Names in Worksheets

You must configure real time incremental loading worksheets if your SAP partition
names are:
• In upper case or contain both upper and lower case letters
• More than 10 characters in length for SAP 3.x
• More than 60 characters in length SAP 4.x
▼ To handle partitions with upper or mixed case:
1. From the Ariba Buyer installation directory, enter the following shell
command:
runtibco -startrepoadmin
2. Enter your user name, choose your SAP variant Repository instance name,
and choose Connect.
3. Repeat the following steps for each of the following worksheets:

• ZATCOS300
• ZATCRE300
• ZATGLM300
a. Open the worksheet.
b. Choose the following functions and view their Details panel:
• For ZATCRE300, Function67
• For ZATCOS, Function8
• For ZATGLM, Function89
c. If your Ariba Buyer partition name is in all upper case, change the Edit
Formula from:
lower(partition.EDI_DC.RCVPRN)
to
partition.EDI_DC.RCVPRN

Chapter 8 Real Time Integrations Ariba Buyer ALE/IDOC Configuration
d. If your partition name is in mixed case or too long for your version of
SAP, you should create a user defined function that converts the SAP
logical system name to the properly formatted Ariba Buyer partition
name.
See your Ariba Professional Services representative for assistance.
e. Save the worksheet.
Worksheets and Executing ALE/IDOCs

In order for ALE/IDOC integration events to execute, the associated worksheets must
be open in the TIB/MessageBroker. The worksheets are:
• ZATCOS300
• ZATCRE300
• ZATGLM300
You can open the worksheets through the TIB/MessageBroker interface or by using
the command:
runtibco -startengine <variant><worksheet>
Ariba Buyer ALE/IDOC Configuration

This section explains how to configure ALE/IDOC mechanisms on your SAP system
to interact with the items from the Ariba Buyer ALE/IDOC transports. This sections
explains how to:
• Define logical systems for each partition
• Define a distribution model
• Define ports
• Define a partner profile

Ariba Buyer ALE/IDOC Configuration Chapter 8 Real Time Integrations
Defining Logical Systems for Partitions

Ariba Buyer ALE/IDOC configuration sends data to every partition within an SAP
variant as a unique logical system. You must create outbound logical systems for
every partition in your SAP variants.
▼ To define outbound logical systems for partitions
2. For 3.1I: choose Basic configuration>Set up logical system>Maintain logical

system
For 4.0B: choose Basic Settings>Set up logical system>Maintain logical system

For 4.5B: choose Basic Settings>Logical Systems>Define Logical System
For 4.6B: choose Sending and Receiving System>Logical Systems>Define
Logical Systems
3. Choose the green check for any warnings about client independence.
4. Repeat the following steps until you have defined logical systems for every
Ariba Buyer partition in every SAP variant on all clients.
a. Choose the New Entries button.
b. Enter the exact Ariba Buyer partition name for the logical system.
c. Enter a description for the outbound logical system.
d. Save.
Defining a Distribution Model

A distribution model provides a way of configuring the data communications
exchanged between logical systems. Your SAP system includes a sample distribution
model upon which you can base your own configuration called the distribution
reference model. This document refers to the distribution reference model found in an
IDES system. Sometimes SAP refers to distribution models as customer models or
customer distribution models.
Distribution models consist of the following components:
• Logical systems

• Message types
SAP uses the term message to describe data sent between logical systems. You can
send a wide variety of data in messages. SAP uses message types to represent the
kinds of data available to a message. The data a message type represents is often
linked to an IDOC description.
For example, a message type called MATMAS represents an IDOC of Material Master
data. Ariba Buyer creates its own message types that resemble those within SAP for
pulling cost center, general ledger, and vendor information.
IDOCs use a mechanism called change pointers to keep track of data changes at the
field level. Change pointers trigger message types that define data communication
between logical systems. Ariba Buyer transports install message types, activate their
corresponding change pointers, and link them to the appropriate IDOCs for you.
In order to exchange data between Ariba Buyer and SAP, you must create and use a
distribution model named Ariba. The Ariba distribution model defines the message
types a base logical system uses communicates with each Ariba Buyer partition
logical system through ALE/IDOC mechanisms.
▼ To create an Ariba distribution model:
2. Create a distribution customer model with the name Ariba.
3. Add the following message types:

• ZATCOS
• ZATGLM
• ZATVEN
Each message type must specify the following:
Model view: Ariba

Sender/client: <SAP logical system>
Receiver/server: <Ariba Buyer partition name>
Message type: <Ariba Buyer message type>
<SAP logical system> is the SAP logical system that sends ALE/IDOC
information, usually your base logical system.

<Ariba Buyer partition name> is the name of the Ariba Buyer partition.
<Ariba Buyer message type> is either ZATCOS, ZATCRE, or ZATGLM.
4. Save your entries.
▼ To distribute the Ariba customer model
1. Run transaction BD64.
2. Highlight the Ariba model.
3. Select Distribution.
Defining a Port
SAP allows an IDOC to travel to a variety of destinations through a port. SAP
provides four kinds of ports:
• Files
• TCP/IP destinations
• Transactional remote function calls (tRFCs)
• R/2 systems
tRFC ports define an IDOC data communication channel from an RFC.
SAP sends incremental real time load information to the TIB/R3 Adapter through a
tRFC port from an RFC. You need to define this port.
▼ To define a tRFC port
1. Run transaction WE21.
2. Open Transactional RFC.
3. Choose the change icon.
4. Enter for any warning messages about client independence.
5. Choose the New Entries button.

6. For 3.1I: enter a description for the port in the Description column and
YCIDOCPROC in the Logical Destination column.
For 4.0B, 4.5B, 4.6B: enter the following values:

Version: SAP Release 3.0/3.1
RFC Destination: YCIDOCPROC
Port Description: a description of the port
7. Save.
Note: Remember the unique port number that SAP generates, for example,
A000000011. You need it for other tasks in this chapter:
• “To configure partner profiles for 3.1I:” on page 110
• “To configure partner profiles for 4.0B, 4.5B, or 4.6B:” on page 112
Creating an RFC Destination for ALE/IDOC

RFC destinations define external processes to which an SAP system can send
ALE/IDOC information. Your Ariba Buyer integration uses an RFC destination to
connect to a process in the TIB/R3 Adapter that can handle the ALE/IDOC real time
incremental data. It does so through a TCP/IP connection.
RFC destinations for RFCs can use a program ID, to uniquely identify a process or
daemon shared between an SAP system and the output of an RFC.
RFC destinations contain port descriptions for logical systems. You need to configure
an RFC destination called YCIDOCPROC for Ariba Buyer integrations to work.
▼ To create the TIB/R3 Adapter RFC destination:
1. Run transaction SM59.
2. Highlight TCP/IP connections and click Create.

RFC destination: YCIDOCPROC
Connection type: T
4. Enter a description such as Ariba Buyer IDOC.

5. Enter.
6. Choose the Registration button.
7. For Program ID, enter bangoYC.
Testing the Connection
After you create the TIB/R3 Adapter RFC destination, you should test the connection.
Be sure Ariba Buyer and the TIB/Repository are started.
▼ To test the connection:
1. Manually start the IDOC R3/Adapter with the following command:

runtibco -startsapidocadapter <variant> <partition>
3. Scroll down and open YCIDOCPROC.
4. Choose Test Connection.
Defining a Partner Profile

At a high level, a partner profile defines the way a logical system sends messages to
other logical systems. All of the ALE/IDOC components which you install or
configure for real time integration reside within partner profiles.
Partner profiles combine the ALE and IDOC components necessary for Ariba Buyer
and SAP to exchange real time incremental data. Partner profiles work at a very high
level of organization within SAP, and in many ways are the central component you
must configure to allow real time incremental integration with Ariba Buyer.
SAP offers four types of partner profiles, most of which are involved in EDI
configuration. Real time incremental integration with Ariba Buyer requires that you
create partner profiles of type LS, for communication related to logical systems.
▼ To configure partner profiles for 3.1I:
Perform the following tasks for every partition:


Partn. number: <the Ariba Buyer partition name>
Partn. type: LS
3. Choose the create icon.

Partner class: ALE
Partn. status: A
5. Choose Outbound Parameters.
6. Choose New Entries and perform the following tasks for each Ariba Buyer
message type and its corresponding basic type:
• ZATCOS and COSMAS01
• ZATCRE and CREMAS01
• ZATGLM and GLMAST01
a. Enter the following information:
Message type: enter one of the Ariba Buyer message types listed above
Receiver port: enter the port number generated for the tRFC port you
defined in “To define a tRFC port” on page 108
Transfer IDoc immed.
Do not start subsystem
Doc type: enter the basic type that corresponds to the message type
(COSMAS01, CREMAS01, GLMAST01)
b. Enter.
c. For Pack. size: enter a default value of 50
d. Save.
Ignore warnings that there are no entries for message control. Outbound
only partner profiles do not use message control.

▼ To configure partner profiles for 4.0B, 4.5B, or 4.6B:
1. Perform the following tasks for every partition.
2. In the navigation area, choose -->Header entries.
3. Choose the change->display icon, then New Entries.
Partn.number: <the Ariba Buyer partition name>
Partn.type: LS
Partner class: ALE
Partn.status: A
5. Save and green arrow back.
6. With the partition parnter number still selected, in the navigation area,
choose -->Outbound parameters.
7. Choose New Entries and perform the following tasks for each Ariba Buyer
message type and its corresponding basic type:
• ZATCOS and COSMAS01
• ZATCRE andCREMAS01
• ZATGLM and GLMAST01
a. Enter the following information:
Message type: enter one of the Ariba Buyer message types listed above
Receiver port: enter the port number generated for the tRFC port you
defined in “To define a tRFC port” on page 108
Pack.size: 50 (you can adjust this later)

Transfer IDoc immed.
Do not start subsystem

Chapter 8 Real Time Integrations Ariba Buyer Object Configuration
Basic type: enter the basic type that corresponds to the message type
(COSMAS01, CREMAS01, GLMAST01)
b. Save.
Ignore warnings that there are no entries for message control. Outbound
only partner profiles do not use message control.
Ariba Buyer Object Configuration

Ariba Buyer RFCs use the ZARIBTARV structure to filter incremental real time
ALE/IDOC changes to appropriate destinations. You must enter selection values
within ZARIBTVARV for the ALE/IDOC mechanisms to work. These selection values
define:
• The variant destination
• The partition destination
• The Ariba Buyer RFC that processes the message types
You can review how ZARIBTARV provides filtering and parameter storage in:
• “Parameter Configuration” on page 77
• “Filtering” on page 54
▼ To define partition selection values
1. Perform the steps in this task for every partition in every SAP variant.
3. For 3.1I: enter an Object name of ZARIBTVARV and choose Change.

For 4.0B, 4.5B, 4.6B: choose Structures, enter ZARIBTVARV, and choose
Change.
4. Continue past any warnings about repairs.
5. Choose Utilities>Create Entries.
6. For each Ariba Buyer message type:

Ariba Buyer Object Configuration Chapter 8 Real Time Integrations
• ZATCOS
• ZATCRE
• ZATGLM
perform the following tasks:
a. Choose New Entries.
b. Enter the following information:
Ariba Variant: your Ariba Buyer variant name
Ariba Partition: your Ariba Buyer partition name
Variable name: IDOC_DEST_<message_type>
(Where <message_type> is one of the Ariba Buyer message types.)

Selection cat.: P
Number: 0
Selection value (LOW): your Ariba Buyer partition name
c. Save and create any necessary change requests.
ABAP/4 Configuration Classes

TIBCO Inc. and Ariba Buyer provide the following development classes for
processing real time incremental IDOC data:
• ZATI—the objects and RFCs that customers should never change
• ZATC—customer exit functions for safely changing ALE/IDOC RFCs
These classes resemble the ZAR6 and ZARC development classes. You can examine the
contents of ZATI to learn how the RFCs process data, and then you can safely make
changes to those RFCs through the customer exit functions in ZATC. You can review
how this works in “Post Hook Filtering” on page 63.
Neither class offers the ability to define fields through extension structures.

Chapter 8 Real Time Integrations Maintenance
Maintenance
You must occasionally schedule Ariba Buyer integration events that pull IDOC
related data through batch methods due to a limitation in the IDOC design. SAP can’t
inform Ariba Buyer that a record is inactive through IDOCs, at least not without some
configuration. As a result, you may find inactive data in Ariba Buyer that needs
deletion.
To remedy this problem, you should occasionally schedule the non-IDOC integration
events and RFCs to pull IDOC related data. Such pulls clean away any data that
requires deletion.
The following pulls can resolve this deletion problem:

Event: Accounting_CCSAP
Worksheet: CostCenterEventSAP
Event: Accounting_GLSAP
Worksheet: GeneralLedgerEventSAP
Event: PurchaseOrgSupplierCombo_SAP
Worksheet: PurchaseOrgSupplierComboSAP
Event: Supplier_SAP
Worksheet: VendorEventSAP
Event: PurchaseOrgSupplierCombo_SAP
Worksheet: PurchaseOrgSupplierComboSAP

Maintenance Chapter 8 Real Time Integrations

Chapter 9
Release Authorizations Pulls
Ariba Buyer provides limited support for certain types of SAP release authorizations
for documents. The RFCs in the ZAF7 development class are an example of how you
can pull your SAP release procedures into Ariba Buyer and use them to approve
requisitions. Ariba Buyer supports the features of the ZAF7 RFCs and can represent
their data within the Ariba Buyer approval flow.
Ariba Buyer RFCs make assumptions about your SAP configuration. These
assumptions include:
• The SAP user IDs map directly to Ariba Buyer user IDs (without regard to case).
• All your release strategies for requisitions are global to your entire SAP system; for
example, you do not have multiple release groups for each classification type.
• Ariba Buyer only supports release procedures for requisitions that work in
conjunction with the Materials Management classification. Support-related
processes that work without SAP’s classification system are not supported.
• You set up your releases in terms of a given range of monetary values per release
code, and that each code releases a document in sequence of an increasing
allowance for expenditures. For more information about value ranges and
sequence, see “ZAF7 Ariba Buyer Release Assumptions” on page 119.
This chapter presents the following items:
• Release authorities
• Release assumptions in Ariba Buyer
• Release authorization in Ariba Buyer
• Release classification
• Release RFCs

Release Authorities Chapter 9 Release Authorizations Pulls
Release Authorities
In the context of approving an SAP document such as a requisition or a purchase
order, SAP uses the term release to signify the act of approving, clearing, or giving
the “go ahead” to procure materials or services. (Do not confuse this reference with
the more common meaning of release in regard to issuing orders against long term
purchase agreements.)
Release authorities are privileges certain SAP users have to release or approve an
SAP document. For example, you may not have the authority to approve expenditures
at all, while your immediate boss has the authority to approve requisitions within a
certain range of cost, say anything under $2,000. If it is over $2,000, then your boss
needs the approval of his or her supervisor, and so forth.
Release authorities may closely resemble the approval flow rules in your Ariba
Buyer. The purpose of the ZAF7 RFCs is to use your existing SAP release
authorization setup to approve requisitions in Ariba Buyer. For information on how
Ariba Buyer handles approval rules, refer to the Ariba Buyer Configuration Guide.
Release authorities consist of:
• Conditions, Strategies, Indicators, and Codes
• Profiles and Authorizations
Conditions, Strategies, Indicators, and Codes

You should be familiar with following release-related terms in order to apply the
information in this chapter:
• Release procedure—the process of configuring the release of a document.
• Release strategy—the mechanism by which individuals or departments release a

requisition in terms of “who does what” and “in what order”.
• Release conditions—determine which release strategy applies to a given purchase

requisition.
• Release indicator—indicates whether the requisition becomes an order after it is

released.
• Release code—identifies the point in the release strategy when someone can release
a document.

Chapter 9 Release Authorizations Pulls ZAF7 Ariba Buyer Release Assumptions
Profiles and Authorizations

All SAP user authorizations are defined in profiles. A user can have more than one
profile; and thereby, can have more than one set of authorizations.
SAP uses authorizations as permission to approve a given item.
ZAF7 Ariba Buyer Release Assumptions

Ariba Buyer makes further assumptions about the way you have constructed your
release strategies for integration:
• Requisitions fall into a release strategy by release conditions based on monetary

value ranges.
• The value ranges reflect a progressive step-by-step increase of monetary value

ranges that do not overlap.
• A strategy contains the release code of all other strategies that have a lower
monetary value range. (If you have authority to spend $100,000, you also have
authority to spend $5.)
• As the price increases, more and more release codes (individuals or departments)
are in each strategy.
The number of release codes for each release strategy increases as the monetary value
of the strategy increases. For example, you might have eight release strategies like the
following.
Release Release Condition Release Codes
Strategy
RS1 $0 to $5,000 R1
RS2 $5,000 to $10,000 R1, R2
RS3 $10,000 to $25,000 R1, R2, R3
RS4 $25,000 to $30,000 R1, R2, R3, R4
RS5 $30,000 to $50,000 R1, R2, R3, R4, R5
RS6 $50,000 to $100,000 R1, R2, R3, R4, R5, R6
RS7 $100,000 to $500,000 R1, R2, R3, R4, R5, R6, R7
RS8 N > $500,000 R1, R2, R3, R4, R5, R6, R7, R8

Release Authorization in Ariba Buyer Chapter 9 Release Authorizations Pulls
Note: Ariba Buyer does not alter SAP’s workflow as it relates to release
authorities.
Release Authorization in Ariba Buyer

The example RFCs take a special case of release data from SAP into Ariba Buyer.
Ariba Buyer does not have release codes, but there are roles that can approve
requisitions. Ariba Buyer can take the value range for release conditions and map a
role to the upper limit of each range.
This section explains how Ariba Buyer turns release data from SAP into:
• Approval requests
• Approval rules
Approval Requests
In Ariba Buyer, approval rules determine how a requisition works through approval
flows from one person or role to the next. The most important concept in Ariba
Buyer’s approval rules is that of an approval request. Approval requests correspond
to users or permissions and are represented as points in the chain of approval.
Approval Rules
Ariba Buyer defines the organization of approval requests by applying approval
rules. The default type of approval rules are:
Rule Types How to use them
Base Rules Base rules add approval requests if a given condition is
satisfied.
Filter Rules Filters remove approval requests based on conditions. Filters
are not used to translate release authorizations into Ariba
Buyer.
Chain Rules Chain rules add several approval requests at one time, and
often travel up a management chain of command. Chain rules
do not organize approval requests in sequence.
Constraint Constraint rules organize approval requests in sequence. For
Rules example, your boss has to approve something before his or her
boss needs to approve.

Chapter 9 Release Authorizations Pulls Release Classification
Ariba Buyer translates its special case of SAP release authorizations into Ariba Buyer
approval rules. Ariba Buyer creates approval requests for each release code and
organizes them with approval rules. The result for the special case should be a
sequential list of management hierarchies and release codes for an approval request
based on monetary value.
Release Classification
SAP supports two types of release procedures:
• Those with classification
• Those without classification
Classification refers to the entire collection of criteria upon which you may define
release strategies, as well as the conditions themselves.
This section describes how Ariba Buyer and SAP use release classification and
characteristics for release authority integration.
Release procedures that do not offer classification allow you to only work with the
following conditions:
• Monetary value
• Material group
• Account assignment
• Plant
Procedures with classification work with any criterion available to the Materials
Management module. They enable the previous four conditions as well as purchasing
group, purchasing organization, and many others.
Note: ZAF7 RFCs only work with classification.
Characteristics
The individual values from which you create conditions for classification are
characteristics. It is important to know the individual value for your monetary
characteristic to use the ZAF group RFCs.

Release RFCs Chapter 9 Release Authorizations Pulls
You must set a parameter called Z_ARIBA_RELEASE_AUTHORITY_CNAM in the

ZARIBTVARV structure with the monetary characteristic value for your SAP system for
purchase order release authorizations.
Displaying and Setting Your Monetary Amount Characteristic Value
For step-based instructions on how to display and set monetary amount characteristic
values, see “To display and set your monetary amount characteristic value:” on
page 122.
Release RFCs
Ariba Buyer provides two RFCs to pull your release authorizations and release codes:
• Z_ARIBA_RELEASE_AUTHORITY
• Z_ARIBA_USER_RELEASE_CODE
Ariba Buyer also provides customer exit functions for these RFCs.
To learn more about how the Ariba Buyer RFCs pull release authorizations, see the
sample RFCs from Ariba in the Developer Workbench.
▼ To display and set your monetary amount characteristic value:
1. Enter transaction OMGS if you want to deal with purchase orders.

Enter OMGQ if you wish to release purchase requisitions.
2. Click the Release strategy button and double click on the first row in the
Release Strategies overview table.
3. Click the Classification button.

Sometimes you have to open the following buttons and choose Continue, in
sequence, before you can access the Classifications button screen: “Release
prerequisites”, “Release statuses”.
4. Remember (or copy into your buffer) the value for Class.
5. Use transaction /NCL03.

Access the Display Class: Initial Screen and paste or enter the value for Class.

Chapter 9 Release Authorizations Pulls Release RFCs
6. Enter value 032 for class type.

(If this field is empty and you want to select the value from the available
class types, open the Extras menu and choose Change Class Types. Scroll
down to open the Release Strategy node and click on the node you wish to
use. Select the release strategy by double clicking on it.)
7. Click the Characteristics button.
8. Choose the monetary value that defines the currency.

This value will have a DTyp entry of CURR. Copy this value (into the buffer)
or remember the characteristic value for the applicable currency value.
9. Use transaction /NSM30.

Enter ZARIBTVARV then choose Display.
10. Open Utilities>Table Contents>execute.
If you do not have an entry for Z_ARIBA_RELEASE_AUTHORITY_CNAM, you

must to make one with the following information. For information on how to
add parameters to ZARIBTVARV, see in “Parameter Configuration” on
page 77.
Field Name What to enter
(Ariba Buyer) Enter your variant for your SAP data.
Variant
Partition Enter your partition for your SAP data.
Name Enter Z_ARIBA_RELEASE_AUTHORITY_CNAM.
Fieldname Leave blank.
Type Enter “P”.
Number Enter “0”.
Sign Leave blank.
Option Leave blank.
Low Enter the name from the Characteristics field.
High Leave blank.

Release RFCs Chapter 9 Release Authorizations Pulls

Chapter 10
Error Recovery
The job of the SAP integration is to provide reliable data exchange between Ariba
Buyer and SAP. If anything goes wrong during the process, the integration event must
detect the error and take some action.
When an error occurs, there are two things the integration event can do:
• Recover automatically
• Report the error and wait for an administrator to take action
SAP integration is designed to try to recover automatically whenever possible, with

minimal intervention. In some cases however, the integration event cannot recover
automatically and must report the error to the attention of an appropriate
administrator.
In general, the integration event can recover automatically from any error that occurs
before the data is committed to SAP. Once the data has been committed on the SAP
system, the integration event does not try to recover from errors. The integration
event reports the error and waits for an administrator to intervene.
Failures Pushing to SAP

In general there are two parts of the push to consider: from the Ariba Buyer to the
TIB/MessageBroker worksheets, and from the worksheets to the TIB/R3 Adapter into
SAP. This section describes those two stages separately.
Failures pushing Purchase Orders to TIB/MessageBroker

The Ariba Buyer order processor is responsible for the first stage of a purchase order
push: it takes an order on Ariba Buyer and writes it out to the TIBCO integration
channel through an integration event.

Failures Pushing to SAP Chapter 10 Error Recovery
If the order processor encounters an error while writing an order to the interface table,
it logs an error in the Ariba Buyer error log and the purchase requisition associated
with that order remains in the “Ordering” state.
When a requisition is stuck in the “ordering” state, an Ariba administrator must:
1. Check the Ariba Buyer log files, find the error message, and diagnose the
problem.
2. Correct the error.
Once the error has been found and corrected, you don’t have to do anything special to
restart the push. There is an Ariba Buyer scheduled task (FailedOrders) that checks
for unfinished orders and re-executes the order transmission. You can either wait until
the next scheduled run of this task or you can execute it manually from the Ariba
Buyer Enterprise Manager.
For more information on scheduled tasks, see the Ariba Buyer Configuration Guide.
Failures Pushing Purchase Orders or Receipts to SAP

The second stage of a push is when the integration event routes data through
TIB/MessageBroker and the TIB/R3 Adapter into SAP.
The most common error at this stage is when the SAP system rejects the incoming
order because it contains data that is not valid for the SAP system. This can happen if
the adapters are slightly out of synch: for example, if a supplier is invalidated on the
SAP side after the order was cut on the Ariba Buyer, then the incoming order is
rejected because it has a supplier that’s now invalid. (You can avoid this problem by
using real time incremental loading; refer to Chapter 8, “Real Time Integrations.”)
For purchase orders, the push worksheets return error messages and details about
pushes immediately. When SAP rejects a order, it sends that order back, with an error
message saying why the order was rejected. The worksheets returns this error
message to Ariba Buyer to indicate that there was an error.
Note: Since an Ariba Buyer requisition can contain line items that go to
more than one SAP purchase order, it is possible for some line items from a
requisition to successfully push to SAP while other line items do not. All
line items for a particular SAP purchase order must be accepted by SAP for
that purchase order to be successfully pushed. If any line items for a
particular SAP purchase order are rejected, the push for that entire purchase
order fails.

Chapter 10 Error Recovery Pulling Failures from CSV files
The administrator should work with the original requester to fix the problems that
caused the order errors, and then resubmit the requisition.
By default, the notification message is sent to all users who have the Purchasing
Agent permission.
Pulling Failures from CSV files

Ariba Buyer can pull data from CSV files for information related to requisitions,
including company codes. This section describes how such a pull might fail, and how
to troubleshoot the failure.
Failure Pulling Multiple Entries From CommodityExportMap.CSV

The use of default partition commodity codes, assorted company codes, and
accounting data requires multiple entries in CommodityExportMap.CSV. However,
multiple entries may fail to load.
For example, in a requisition, you populate the commodity code or material group
when you select the last company code (from the multiple entries in
CommodityExportMap.CSV). But, to choose a company code, which proceeds the last
entry, produces a null material group or commodity code.
Evidently, a load appears successful when, actually, only the final entry loads.
▼ To successfully load multiple entries:
1. Extend the lookup key in SAPERPVariantExt.aml:

<inClass name="ariba.procure.core.CommodityExportMapEntry">
<inClassVariant name="vsap">
<lookupKey fields="CompanyCode"/>
</inClassVariant>
</inClass>
2. Reload the extension file.
3. Reload CommodityExportMap.CSV.

Troubleshooting Chapter 10 Error Recovery
Troubleshooting
Here are some suggestions you can use when things are not working properly.
When you call an RFC, you can turn on a debugging switch. This allows you the
opportunity to access the SAP user interface, where you can set breakpoints.
▼ To debug through the SAP GUI:
1. From the Ariba Buyer working directory, turn on SAP’s debugging mode by
typing this command at the command line:
set RFC_DEBUG=1
2. Trigger the event by submitting a requisition, receipt, or by running a pull

through the Enterprise Manager.
3. When the SAP user interface opens, open another session, go to transaction
se37, and set a breakpoint on a line of code in the RFC.
4. When you’re finished debugging, you should turn debugging mode back off
again:
set RFC_DEBUG=0
You can also debug TIB/MessageBroker worksheets at the same time.
▼ To debug through TIB/MessageBroker:
1. Set the integration event initialization parameter to manual.
2. Start TIB/MessageBroker and open the worksheet.
3. Perform the steps above.

Chapter 10 Error Recovery Debugging Pushes
Debugging Pushes
Ariba Buyer RFCs offer two parameters that allow you to watch push operations
actually fill purchase order or goods receipt screens:
• Z_ARIBA_PO_PUSH_DISPLAY_MODE
• Z_ARIBA_GR_PUSH_DISPLAY_MODE
To use these parameters, see “Debugging Pushes” on page 83.

Debugging Pushes Chapter 10 Error Recovery

Index
A base logical system

account assignment categories 87 defining 100
displaying fields 88 description 99
accounting field configuration 89 basic version configuration option 24
accounting information extension 68 batch scheduling 115
accounting object 94 blocked vendors 40
Accounting Types 90 breakpoint 128
Accounting_CCSAP 115 Business Application Programming Interface
Accounting_GLSAP 115 See also BAPI
ALE 97, 111
ALE/IDOC
C
configuration 105
executing 105 change pointers 107
partition loading 86 characteristics 121
Application Linking and Embedding 97 classification 121
application server 27 client connection pool 27
approval request 120 client tag 28
approval rules 120 clientConnectionPool
Ariba Buyer RFCs 16 sample 28
Ariba customer model 108 tag 27
Ariba development classes 35 Clients 99
Ariba distribution model 107 ClusterRoot 94
ariba.sap.common.AACUtil 94 company code 97
associate a base logical system 100 connection information table 26
authorizations 119 ConnectionInfo.table 26
COST_CENTER_DAYS_PAST 80
COST_CENTER_MSG_TYPE 80
B CostCenterEventSAP 115
BALANCE_SHEET_ACCOUNTS 80 CPIC user 36
bank selling rate 40 CSV source files 24
BANK_SELLING_RATE_SYMBOL 40 currency conversion rates 82
BAPI currency separator 36
pushing 20 customer distribution models 106
support 75

Index
customer exit functions GENERAL_LEDGER_MESSAGE_TYPE

changing ALE/IDOC RFCs 114 80
filtering 74 GeneralLedgerEventSAP 115
customer models 106 generic listeners 33
global company codes 101
global organizational units 101
D goods receipt mapping extension 70
date format 22
Days Past 82
debugging 128 H
Deletion Flag field 74 header information extension 68
demo version configuration option 24
dialog users 37
distribution model 106 I
distribution reference model 106 IDOC 33, 97
document types 84 IMG 101
Implementation Dialog Users 37
inbound 99
E incremental data loading 81, 97
error message information extension incremental loading worksheets 104
purchase order 68 initdb
receipts 68 after initializing 30
Error Recovery 125 before initializing 24
error recovery 125 -emptytibco 103
ERS tax code 21 -initdb 23, 103
exit function -inittibco 23, 30
customer 74 -loadtibco 103
filtering 74 options 103
initialization 128
integration 15
F integration event 17
FailedOrders 126 Intermediate DOCument
field mapping See also IDOC
push 21 Internal Order Types 83
SAP purchase order screens 68 internal tables 73
SAP screens 69
field status group strings 91
filtering exit function 74 L
language 21, 26
line item information extension 68
G line item receiving information extension 68
gatewayHost 30 loadSAP 31
gatewayService 30 local organizational units 101
general ledger balance sheet accounts 85 locale 26
GENERAL_LEDGER_DAYS_PAST 80 log 32

Index
logical system 99, 110 privileges 36

logical systems for partitions 106 profile
CPIC user 36
user authorization 119
M program ID for RFC 109
maintentance 115 pull
mapping fields 71 outbound data communication 99
materials management classification 117 purchase order mapping 69
message 107 purchase order mapping extension 69
message control warning 113 PurchaseOrderAdapterBAPI 21
message types 107 PurchaseOrgSupplierCombo_SAP 115
Minority Vendor Head Offices 82 PurchaseOrgSupplierComboSAP 115
MINORITY_VENDOR_USE_HEADOFFI Purchasing Agent permission 127
CE 80, 82 push
monetary characteristics 83 debugging 83
multiple partitions 26 inbound data communication 99
O R
OMGQ 122 r3Adapter 32, 33
OMGS 122 rdisp/max_wprun_time 38
order processor real time
convert requisition 18 incremental integration 99
purchase order push 125 incremental loading 97
ordering addresses 40 release
outbound 99 code 117, 118, 120
outbound logical systems 106 conditions 118
groups 117
indicator 118
P procedure 118, 121
parameters 77 strategies 117
Parameters.table 25 strategy 118
partition names 104 release authorities
partition selection values 113 SAP privileges 118
partner functions 40 ZAF7 RFC 118
partner profile RFC destination 109
3.1H 110 RFC Import Tables 73
4.0B and 4.5B 112 RFC, custom
create 97 adding 52
description 110 define metadata xml 53
PO_PUSH_DIRECTCC_DOC_TYPE 80 load in TIB/Repository 54
PO_PUSH_ERP_DOC_TYPE 80 RFC_DEBUG 128
PO_PUSH_ERPCC_DOC_TYPE 80 roles 120
PO_PUSH_PCARDCC_DOCTYPE 80
port 108

Index
runtibco static filtering 77

-regenMappers 32 Structures
-updateconfigfiles 24 SARPOI 68
RZ10 39 ZARPOH 68
Supplier_SAP 115
System.SAPConnections 25
S
SAOutboundIdoc-idoc 33
SAP gateway 27 T
SAP IDOC adapter 17 TCP/IP connections 109
SAP user IDs 117 TIB/MessageBroker 16
SAP_ALL 36 TIB/MessageBroker worksheets 16
SAP_NEW 36 TIB/R3 Adapter 16, 27, 32, 33
SAPAdapter_AllRFCs_RFCInboundConfig. Tibco database 30
xml time-out interval 38
connection information 27 title of purchase orders 21
default configuration 31 Transactional remote function calls 108
SAPAdapteridocIdocPublisherConfig.xml transports 38, 102
29 tRFC 108
SAPAdapterLocale 26 troubleshooting 128
SAPConnections 25 TYPE field 78
SAPConnections parameter
ClientID 25
Destination 25 U
SAPGateway 25 user accounts 36
SAPGatewayService 25 username 36
SAPHost 25
SAPPassword 25
SAPSystemNumber 25 V
SAPUser 25 Value 94
SetTrace 25 Vendor Pull Performance Tuning 85
SAPGUI 128 VendorEventSAP 115
SAPLanguage 25 vendors 40
SCC4 100 version specific data 31
SE11 73
selection values 113
server connection pool 30 W
serverConnectionPool 30 WE21 108
service line item support 21 workflow 120
setlocale parameter 26 worksheets 104
showField 94
Source Field 72
start the TIB/R3 Adapter 32 Y
startsapadapter 32
startsapidocadapter 33 YCIDOCPROC 109

Index
Z ZARIBTVARV 77, 122

Z_ARIBA_ACCOUNT_CATEGORY 94 ZARIBTVARV values 80
Z_ARIBA_COST_CENTER 80 ZARPOFMAP 69
Z_ARIBA_CURR_CONV_BANK_RATE ZARPOFMAPX 69, 73
80, 82 ZATC 114
Z_ARIBA_CURR_CONV_DAYS_PAST ZATCOS 107, 114
80, 82 ZATCOS300 104
Z_ARIBA_CURR_CONV_EURO_RATE ZATCRE 114
80, 82 ZATCRE300 104
Z_ARIBA_CURRENCY_CONVERSION ZATGLM 107, 114
80, 82 ZATGLM300 104
Z_ARIBA_GENERAL_LEDGER 80, 85 ZATI 114
Z_ARIBA_GR_PUSH 68, 73, 80 ZATVEN 107
Z_ARIBA_GR_PUSH_BDCDATA_EXT 75 ZXTGRERR 68
Z_ARIBA_GR_PUSH_DISPLAY_MODE ZXTGRITEMS 68
80, 83 ZXTPOACCNT 68
Z_ARIBA_GR_PUSH_ERRORS_EXT 75 ZXTPOERR 68
Z_ARIBA_GR_PUSH_EXT 75 ZXTPOHEADR 68
Z_ARIBA_INTERNAL_ORDER 80 ZXTPOITEMS 68
Z_ARIBA_INTERNAL_ORDER_AUART
80, 83
Z_ARIBA_LAST_CHANGE_DATE 80
Z_ARIBA_MINORITY_VENDOR 80, 82
Z_ARIBA_PO_DETAILS 80
Z_ARIBA_PO_DETAILS_DAYS_PAST 80,
82
Z_ARIBA_PO_PUSH 73, 80
Z_ARIBA_PO_PUSH_BDCDATA_EXT 75
Z_ARIBA_PO_PUSH_DISPLAY_MODE
80, 83
Z_ARIBA_PO_PUSH_ERRORS_EXT 75
Z_ARIBA_PO_PUSH_EXT 75
Z_ARIBA_RELEASE_AUTHORITY 80,
122
Z_ARIBA_RELEASE_AUTHORITY_CN
AM 80, 83, 122, 123
Z_ARIBA_USER_RELEASE_CODE 122
Z_ARIBA_VENDOR_ONLY 80
Z_ARIBA_VENDOR_ONLY_COUNTPOR
GS 80
ZAR6 tables 69
ZARC extension table 69
ZARGRFMAP 70
ZARGRFMAPX 70, 73
ZARIBTARV 113

ARIBA, INC.
807 11TH AVENUE
SUNNYVALE, CA 94089 USA
TELEPHONE: 650.390.1000
FAX: 650.390.1100
WWW.ARIBA.COM

Ariba Buyer SAP Integration Guide

Uploaded by

Copyright:

Available Formats

Ariba Buyer SAP Integration Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ariba Buyer SAP Integration Guide

Uploaded by

Copyright:

Available Formats

Ariba Buyer SAP

ALL LICENSES OF ARIBA SOFTWARE PROGRAMS AND RELATED DOCUMENTATION

Ariba Buyer SAP Integration Guide iii

After Running TIBCO initdb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

iv Ariba Buyer SAP Integration Guide 705en_us2001.5.12

Ariba Buyer SAP Integration Guide v

vi Ariba Buyer SAP Integration Guide 705en_us2001.5.12

Release Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Ariba Buyer SAP Integration Guide vii

viii Ariba Buyer SAP Integration Guide 705en_us2001.5.12

• Chapter 6, “Parameter Configuration” describes the ZARIBTVARV parameter table

• Chapter 7, “Account Assignment Categories” describes how Ariba Buyer pulls

Ariba Buyer SAP Integration Guide 9

• Chapter 8, “Real Time Integrations” describes how to configure SAP to share

• Chapter 9, “Release Authorizations Pulls” describes a scenario in which you can

Shared Documentation Set

Ariba Catalog Format Reference

Ariba Buyer Documentation Set

Ariba Buyer Release Guide

Ariba Buyer Installation Guide

10 Ariba Buyer SAP Integration Guide 705en_us2001.5.12

Ariba Buyer Web Server Configuration Guide

Ariba Buyer Configuration Overview

Customizing Ariba Buyer

Ariba Buyer eForms Tutorial

Ariba Buyer Procurement Guide

Ariba Buyer TIBCO Configuration Guide

Ariba Buyer SAP Integration Guide 11

Ariba Buyer Administration Guide

Ariba Buyer API Guide

Ariba Buyer Approval Rules Guide

Ariba Query API Guide

Ariba Buyer Travel and Expenses Guide

Ariba Buyer Configuration Reference Guide

Ariba Buyer Customization Reference Guide

Ariba Buyer Master Glossary

Ariba Buyer ASP Edition Implementation Guide

12 Ariba Buyer SAP Integration Guide 705en_us2001.5.12

Ariba Buyer SAP Integration Guide 13

14 Ariba Buyer SAP Integration Guide 705en_us2001.5.12

• Pushing Ariba Buyer purchase orders to SAP.

• Pushing Ariba Buyer receipts to SAP.

Ariba Buyer SAP Integration Guide 15

• TIB/MessageBroker—Your Ariba Buyer default configuration provides worksheets

• TIB/MessageBroker Worksheets—The worksheets define the mappings and data

16 Ariba Buyer SAP Integration Guide 705en_us2001.5.12

Ariba Buyer SAP Integration Guide 17

2. The TIB/MessageBroker worksheet sends its instructions to the TIB/R3

Purchase Order Pushes

18 Ariba Buyer SAP Integration Guide 705en_us2001.5.12

1. When an item is received in Ariba Buyer, a receipt object instance is created.

Ariba Buyer pulls the following data from SAP:

Ariba Buyer SAP Integration Guide 19

• Currency conversion rates

20 Ariba Buyer SAP Integration Guide 705en_us2001.5.12

BAPI Push Limitations

• Pushing ERS tax code information.

• Pushing service line items for version 4.0B.

• Split accounting for service lineitems.