ARIBA-SAP Integration

Ariba Buyer
SAP Integration Guide

Version 8.2
May 2004
Copyright © 1996-2004 Ariba, Inc.
Ariba and the Ariba logo are registered trademarks of Ariba, Inc. Ariba Spend Management, Ariba Analysis, Ariba Buyer, Ariba Category
Management, Ariba Contracts, Ariba Travel & Expense, Ariba Workforce, Ariba Invoice, Ariba eForms, Ariba Enterprise Sourcing, Ariba
Category Procurement, Ariba Contract Workbench, Ariba Settlement, Ariba Supplier Network, BPM Services, Power Sourcing, Total Spend
Capture and PO-Flip are trademarks or service marks of Ariba, Inc. All other trademarks are property of their respective owners.
CONTAINS IBM Runtime Environment for AIX (R), Java (TM) 2 Technology Edition Runtime Modules
(c) Copyright IBM Corporation 1999, 2000
All Rights Reserved
Some versions of this product include software licensed from International Business Machines Corp. Such software is protected by copyright as
provided in the proprietary notices included with the software.
Some versions of this product include software licensed from BEA Systems, Inc. Such software is protected by copyright as provided in the
proprietary notices included with the software.
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.
THIRD PARTY SOFTWARE

See this URL for a complete list of third-party software copyright information: http://www.ariba.com/copyrights.cfm
Table of Contents
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Audience and Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Which Chapters to Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Typographic Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Ariba Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Chapter 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Supported SAP Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Pulling Master and Transaction Data . . . . . . . . . . . . . . . . . . . . . . . . . 17
About Integration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Scheduled Pulls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Pulling Payment Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Pulling Remittance Advice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Pushing and Pulling Purchase Orders . . . . . . . . . . . . . . . . . . . . . . . . . 21
Adjusting Net Price . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Pushing Purchase Orders Using BAPI . . . . . . . . . . . . . . . . . . . . . . . . 23
Understanding BAPI Push Limitations . . . . . . . . . . . . . . . . . . . . 23
Pushing Changed and Canceled Purchase Orders . . . . . . . . . . . . . . . 24
Pulling Header Status of Purchase Orders. . . . . . . . . . . . . . . . . . 25
Pushing Receipts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 2
Ariba Buyer Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Installing and Configuring Ariba Buyer . . . . . . . . . . . . . . . . . . . . . . . 27
Verifying Connection Information. . . . . . . . . . . . . . . . . . . . . . . . 27
Specifying the Locale for the TIB/Adapter for R3 . . . . . . . . . . . 29
Initializing the Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Ariba Buyer SAP Integration Guide iii

Table of Contents
Setting Up the TIB/Adapter Using TIB/Designer . . . . . . . . . . . . . . . 31

Verifying Client Connection Information . . . . . . . . . . . . . . . . . . 32
Verifying Client Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Verifying Parameters for Connection Retries . . . . . . . . . . . . . . . 33
Verifying Server Connection Information . . . . . . . . . . . . . . . . . . 34
Exporting SAP Configuration Changes to Synchronize Data . . . 34
Starting the TIB/Adapter for Each Partition . . . . . . . . . . . . . . . . . . . . 35
Chapter 3
SAP Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Setting Up Ariba Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Creating a CPIC User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Understanding Dialog Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Installing Ariba Buyer SAP Transports . . . . . . . . . . . . . . . . . . . . . . . 40
Delivered Transport Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Location of Transport Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Transport Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . 41
Transport Description Reference . . . . . . . . . . . . . . . . . . . . . . . . . 42
Working With the Time-out Interval. . . . . . . . . . . . . . . . . . . . . . . . . . 44
Checking Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Bank Selling Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Blank Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Vendor Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Vendor ERS Tax Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Validation on Catalog Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
About Real-Time Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Receiving Tolerances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Receiving System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
ERP Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Testing Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Chapter 4
Configuring Pulls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Pulling Additional Fields Into Ariba Buyer . . . . . . . . . . . . . . . . . . . . 52
About Extension Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Adding Fields to Extension Structures . . . . . . . . . . . . . . . . . . . . 54
Extension Structure Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
iv Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Table of Contents
Pulling New Tables Into Ariba Buyer. . . . . . . . . . . . . . . . . . . . . . . . . 55

Declaring Local Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Defining Adapter Services for New Custom RFCs . . . . . . . . . . . 57
Adding Real-Time Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Changing SAP Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Pulling Remittance Advice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Enabling Remittance Pull . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Configuring Remittance Pull . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Filtering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
About Static Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
About ABAP Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Understanding Post-Hook Filtering. . . . . . . . . . . . . . . . . . . . . . . 72
Example RFC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Chapter 5
Configuring Pushes . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Push Extension Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Understanding Screen Field Mappings. . . . . . . . . . . . . . . . . . . . . . . . 78
What Field Mappings Do . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
About Data Push Mapping Tables . . . . . . . . . . . . . . . . . . . . . . . . 79
Sources of Data for Push Mapping Tables . . . . . . . . . . . . . . . . . 80
Mapping Fields for Orders or Receipts. . . . . . . . . . . . . . . . . . . . . . . . 80
Finding the Screen Field to Map . . . . . . . . . . . . . . . . . . . . . . . . . 81
Finding the Source Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Editing the Extension Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Changing and Removing Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Filtering and Customer Exit Functions. . . . . . . . . . . . . . . . . . . . . . . . 84
Modifying Customer Development Classes . . . . . . . . . . . . . . . . . . . . 85
Formatting Dates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Unsupported Push Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
BAPIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Additional Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Additional Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Chapter 6
Parameter Configuration . . . . . . . . . . . . . . . . . . . . . . . 87
About ZARIBTVARV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Default Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Ariba Buyer SAP Integration Guide v

Table of Contents
Parameter Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Days Past Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Minority Vendor Head Offices . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Currency Conversion Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Monetary Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Debugging Pushes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Internal Order Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Purchase Order Document Types . . . . . . . . . . . . . . . . . . . . . . . . 93
Vendor Pull Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Using General Ledger Balance Sheet Accounts . . . . . . . . . . . . . 94
Real-Time ALE/IDOC Partition Loading . . . . . . . . . . . . . . . . . . 95
Duplicate PO Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Duplicate GR Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Change PO Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Language for Texts Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Chapter 7
Account Assignment Categories . . . . . . . . . . . . . . . . . 97
About Account Assignment Categories . . . . . . . . . . . . . . . . . . . . . . . 97
Ariba Buyer Account Assignment Category Pulls . . . . . . . . . . . 98
Displaying Fields and Requiring User Input . . . . . . . . . . . . . . . . . . . 99
Configuring SAP Accounting Fields . . . . . . . . . . . . . . . . . . . . . . 99
Ariba Buyer Accounting Types . . . . . . . . . . . . . . . . . . . . . . . . . 100
Field Status Group Strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Pulling New Accounting Objects From SAP . . . . . . . . . . . . . . 104
Chapter 8
Release Authorizations Pulls . . . . . . . . . . . . . . . . . . . 107
Release Authorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Conditions, Strategies, Indicators, and Codes . . . . . . . . . . . . . . 108
Profiles and Authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
ZAF7 Ariba Buyer Release Assumptions. . . . . . . . . . . . . . . . . . . . . 109
Release Authorization in Ariba Buyer . . . . . . . . . . . . . . . . . . . . . . . 110
Approval Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Approval Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Release Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Release RFCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
vi Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Table of Contents
Chapter 9
Real-Time Integrations . . . . . . . . . . . . . . . . . . . . . . . . 115
Ariba Buyer ALE/IDOC Configuration . . . . . . . . . . . . . . . . . . . . . . 116
Configuring a Base Logical System . . . . . . . . . . . . . . . . . . . . . 116
Defining Logical Systems for Partitions . . . . . . . . . . . . . . . . . . 117
Defining a Distribution Model. . . . . . . . . . . . . . . . . . . . . . . . . . 118
Defining a Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Creating an RFC Destination for ALE/IDOC . . . . . . . . . . . . . . 121
Defining a Partner Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Setting Up Global Company Codes. . . . . . . . . . . . . . . . . . . . . . 123
Installing ALE/IDOC Transports. . . . . . . . . . . . . . . . . . . . . . . . 125
Repository and Worksheet Configuration. . . . . . . . . . . . . . . . . . . . . 125
Configuring Partition Names in Worksheets . . . . . . . . . . . . . . . 125
Opening Worksheets and Executing ALE/IDOCs. . . . . . . . . . . 126
Ariba Buyer Parameter Real-Time Configuration . . . . . . . . . . . . . . 127
ABAP/4 Development Classes . . . . . . . . . . . . . . . . . . . . . . . . . 128
Handling Deletion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Chapter 10
Error Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Failures Pushing to SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Application-Level Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
System-Level Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Failures Pulling from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Enabling Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Debugging Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Appendix A
Ariba SAP Objects. . . . . . . . . . . . . . . . . . . . . . . . 137
Naming Conventions for Ariba SAP Objects . . . . . . . . . . . . . . . . . . 137
Summary of Ariba SAP Development Classes. . . . . . . . . . . . . . . . . 138
ZAR6 Development Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
ZAR6 Function Groups and Modules . . . . . . . . . . . . . . . . . . . . 139
ZAR6 Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
ZAR6 Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
ZAR6 Data Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
ZAR6 Message Class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Ariba Buyer SAP Integration Guide vii

Table of Contents
ZARC Development Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

ZARC Function Groups and Modules. . . . . . . . . . . . . . . . . . . . 147
ZARC Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
ZATI Development Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
ZATI Function Groups and Modules. . . . . . . . . . . . . . . . . . . . . 151
ZATI Includes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
ZATI Message Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
ZATC Development Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
ZATC Function Group and Modules . . . . . . . . . . . . . . . . . . . . . 153
ZAR7 Function Group and Modules . . . . . . . . . . . . . . . . . . . . . 154
ZAR7 Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
ZAR8 Function Group and Module. . . . . . . . . . . . . . . . . . . . . . 155
ZARIBA_CHANGEORDER Development Class . . . . . . . . . . . . . . 155
ZARIBA_CHANGEORDER Function Group and Modules . . 155
ZARIBA_CHANGEORDER Structures . . . . . . . . . . . . . . . . . . 156
ZARIBA_CUSTCHANGEORDER . . . . . . . . . . . . . . . . . . . . . . . . . 157
ZARIBA_CUSTCHANGEORDER Function Group and Module 157
ZARIBA_CUSTCHANGEORDER Structures. . . . . . . . . . . . . 157
ZARIBTVARV RFC Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
ZARIBA_REMITTANCE Development Class . . . . . . . . . . . . . . . . 160
ZARIBA_REMITTANCE Dictionary Structures . . . . . . . . . . . 160
ZARIBA_REMITTANCE Data Element . . . . . . . . . . . . . . . . . 160
ZARIBA_REMITTANCE Function Group. . . . . . . . . . . . . . . . 160
Z_ARIBA_REMITTANCE_PULL Function Module . . . . . . . 161
ZARIBA_CUST_REMITTANCE Development Class . . . . . . . . . . 161
ZARIBA_CUST_REMITTANCE Dictionary Structures . . . . . 161
ZARIBA_CUST_REMITTANCE Function Group . . . . . . . . . 161
ZARIBA_REMITTANCE_PULL_EXT Function Module. . . . 162
Appendix B
About SAP Transports . . . . . . . . . . . . . . . . . . . . 163
Overview of SAP Transports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Delivered Transport Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Location of Transport Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Transport Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Import Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Configuring Your SAP System for Real-Time Integration . . . . 165
viii Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Table of Contents
Transport Description Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Base Functionality Transport. . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Real-Time Integration Transport . . . . . . . . . . . . . . . . . . . . . . . . 167
SAP R/3 Version-Specific Transports . . . . . . . . . . . . . . . . . . . . 167
Appendix C
Integration Events Reference . . . . . . . . . . . . . . . 169
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Ariba Buyer SAP Integration Guide ix

Table of Contents
x Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Preface
This document describes how to integrate Ariba Buyer with SAP.
Audience and Prerequisites

The audience for this document is:
• Ariba Buyer implementation personnel
• SAP administrators, purchasing agents, and developers
This document does not describe all aspects of working with Ariba Buyer. For a
complete list of Ariba Buyer documentation available in this release, see the Ariba
Buyer Documentation Roadmap (doc_roadmap.htm). You can find the roadmap on
Connect (http://connect.ariba.com) along with the other documentation for each
release.
W To locate the Ariba Buyer Documentation Roadmap:

1 Log in to Connect.
2 On the left-hand panel, navigate to the Documentation page for the current release
(where N.n is the current release) by clicking the following links:
Product Info > Ariba Procurement Solution > Buyer N.n > Documentation
3 Under Product Documentation, click the link for the view-only documentation set.
4 Click the link for the language you want, such as Ariba Buyer Documentation: English.
5 In the section About the Release, click Ariba Buyer Documentation Roadmap.
On the same page, the Multi-Document Search link describes how to use Adobe's
Multi-Document search feature to search all the Ariba Buyer guides simultaneously
for specific words or phrases.
Ariba Buyer SAP Integration Guide xi

Preface Which Chapters to Read
Which Chapters to Read

This document includes the following chapters:
• Chapter 1, “Introduction,” explains the features that make integration between
Ariba Buyer and SAP possible, including an overview of integration events,
building block data, BAPI (Business Application Programming Interfaces)
integrations, Remote Function Call (RFC) integrations, customer development
classes, and initialization steps.
• Chapter 2, “Ariba Buyer Setup,” describes the tasks and items you complete within
Ariba Buyer before and after TIBCO database initialization.
• Chapter 3, “SAP Setup,” describes the tasks you complete on SAP to integrate with
Ariba Buyer.
• Chapter 4, “Configuring Pulls,” describes the SAP system components that allow
you to pull new fields and tables, filter data, and create your own Ariba Buyer
RFCs.
• 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
configurations.
• Chapter 9, “Real-Time Integrations,” describes how to configure SAP to share
vendor, general ledger, and cost center data with Ariba Buyer through real-time,
single-object loading through ALE/IDOC configuration.
• Chapter 8, “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.
• Appendix A, “Ariba SAP Objects,” lists the Ariba SAP development objects and
describes the naming conventions for those objects.
• Appendix B, “About SAP Transports,” provides background information about the
Ariba-delivered SAP transports and detailed instructions for installing them.
• Appendix C, “Integration Events Reference,” lists the integration events that work
with SAP.
xii Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Typographic Conventions Preface
Typographic Conventions
The following table describes the typographic conventions used in this document:
Typeface or Meaning Example

Symbol
AaBbCc123 Text you need to change is http://server:port/app/inspector
italicized.
AaBbCc123 The names of user Choose Edit from the File menu.
interface controls, menus,
and menu items.
AaBbCc123 Files and directory names, There is one line in ReportMeta.csv for
parameters, fields in CSV each report in the system.
files, command lines, and
code examples.
AaBbCc123 The names of books. For more information, see the Ariba
Buyer SAP Integration Guide.
Ariba Technical Support

For assistance with Ariba products, Ariba Technical Support is available by phone,
email, or over the Web. For information on how to contact Ariba Technical Support,
refer to the following page on the Ariba Technical Support website:
http://connect.ariba.com/TechSupport_Contacting.htm
Ariba Buyer SAP Integration Guide xiii

Preface Ariba Technical Support
xiv Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Chapter 1
Introduction
This chapter provides an introduction to the way Ariba Buyer integrates with SAP
systems through an integration channel. Although many integration channels might
be implemented with Ariba Buyer, the majority of the examples in this book relate
specifically to the TIBCO integration channel. Therefore, before using this document,
become familiar with the information presented in the Ariba Buyer TIBCO
Configuration Guide.
This chapter contains the following sections:

• “Overview” on page 13
• “Supported SAP Versions” on page 17
• “Pulling Master and Transaction Data” on page 17
• “Pulling Payment Terms” on page 19
• “Pulling Remittance Advice” on page 19
• “Pushing and Pulling Purchase Orders” on page 21
• “Pushing Purchase Orders Using BAPI” on page 23
• “Pushing Changed and Canceled Purchase Orders” on page 24
• “Pushing Receipts” on page 26
Overview
Ariba Buyer interacts with SAP in three distinct ways:
• Pulling master and transaction data from SAP systems. Master data includes
SAP information from accounts, currency conversion rates, suppliers and payment
terms. Transaction data includes remittance advice. To pull data, Ariba Buyer runs
an integration event, which uses the integration channel’s instructions to pull the
data. For example, if TIBCO is your integration channel, the integration event uses
the instructions in its associated TIB/MessageBroker worksheet to perform the data
pull.
Ariba Buyer SAP Integration Guide 13

Chapter 1 Introduction Overview
• Synchronizing the flow of transaction data. This process includes pushing Ariba
Buyer purchase orders and receipts to SAP and pulling purchase order numbers
back into Ariba Buyer from SAP as part of the ERP CC (carbon copy) purchase
order process. Pushing data to SAP works similarly to pulling data. Notable
exceptions include the use of distinct RFCs (remote function calls), and the ability
to use BAPIs to push purchase orders.
• Integrating master data in real time through IDOCs (Intermediate
Documents). For RFC data pulls from SAP to Ariba Buyer, TIB/MessageBroker
sends the instructions outlined in the MessageBroker worksheets to the
TIB/Adapter for R/3. The TIB/Adapter communicates with SAP through particular
RFCs to pull data into Ariba Buyer. Each type of data pull requires a different
RFC. For real-time integrations using IDOCs, SAP sends the data to the
TIB/Adapter whenever the data changes in SAP for cost center, general ledger
(GL) account, and vendor data. The MessageBroker worksheets pick up the data
from the TIB/Adapter and then publish the data to Ariba Buyer.
Note: With Version 8.2, global instance support is available for Ariba Buyer
integrations with SAP. All new Ariba Buyer instances support Simplified Chinese,
Japanese, and European users. If your existing Ariba Buyer instances use
non-Unicode databases, you must convert the databases to Unicode to a support
global instance. Ariba Buyer provides tools to help you convert your Latin-1 database
to Unicode. See the Ariba Buyer Data Load Guide for more information on global
support and details on specifying the correct character encodings for your database.
For comprehensive instructions on converting your Latin-1 database to Unicode, see
the information on Unicode conversion on Connect (http://connect.ariba.com).
14 Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Overview Chapter 1 Introduction
The following diagram illustrates the data flow of integration between Ariba Buyer
and SAP using a typical TIBCO integration channel. Note that if you use a different
channel, such as IBM WebSphere Business Integration Adapter, the information in
this diagram differs slightly.
.
Ariba Ariba Buyer system
Buyer including
Domain integration events
MessageBroker
worksheet TIB/MessageBroker TIBCO
Domain
TIB/Adapter for R/3
SAP system ,
including
SAP
task-specific RFCs,
Domain
BAPIs, or IDOCs, and the
ZARIBTVARV table
The Ariba Buyer, TIBCO, and SAP domains contain the following elements:
• Ariba Buyer System, including integration events—Integration events describe a
data exchange. They are defined by partition in message configuration files and by
variant in message definition files. Integration events tell 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 run pushes or pulls for a
partition manually through Ariba Buyer Administrator, automatically as a
scheduled task, or as a part of the initialization process when you first create the
Ariba Buyer database.

Chapter 1 Introduction Overview
For general information on integration events, see the Ariba Buyer Data Load
Guide. For a description of all integration events, see the Ariba Buyer
Configuration Reference Guide. For information on the integration events that
work with SAP configurations, see Appendix C, “Integration Events Reference.”
• MessageBroker—Ariba Buyer uses TIB/MessageBroker to route and manipulate
data between Ariba Buyer and external data contained in the SAP ERP system. For
integration to SAP or other data sources, the most prominent part of
MessageBroker is the worksheet.
• MessageBroker worksheets—The worksheets (also called transforms) define the
mappings and data transformations between Ariba Buyer and SAP.
MessageBroker uses worksheets to organize the work it does with messages and
their data. Each worksheet is a set of transformation instructions bundled with
publish and subscribe subjects. Worksheets are stored in the TIB/Repository and
are executed when TIB/MessageBroker receives a subject to which the worksheet
subscribes.
• TIB/Adapter for R/3—Your default Ariba Buyer configuration for SAP uses the
TIB/Adapter for R/3 to share data between TIBCO applications and your SAP
system. The TIB/Adapter for R/3 communicates directly with Ariba Buyer RFCs
and the RPC clients in worksheets. If you have enabled real-time integration of cost
center, GL account, and vendor information from SAP, the TIB/Adapter maps the
IDOC to Ariba Buyer objects. For more information about the TIB/Adapter for
R/3, see the documentation on the TIBCO product CD.
• ZARIBTVARV— ZARIBTVARV is a custom table used to configure parameters by Ariba
Buyer RFCs. For more information on this table, see Chapter 6, “Parameter
Configuration.”
• Ariba Buyer RFCs—You load Ariba Buyer RFCs by installing Ariba Buyer into
your SAP system. Ariba Buyer custom RFCs pull data and post transaction data
into SAP.
In addition to pulling data from SAP, an Ariba Buyer SAP partition typically pulls
Ariba-specific data from CSV files, such as adjustment types and commodity code
mapping information.

Supported SAP Versions Chapter 1 Introduction
Supported SAP Versions

Ariba Buyer integrates with the following SAP versions:
• 4.6C
• 4.7
If you use versions 4.6C or 4.7, be aware of the following issues:

• The BAPI for purchase orders does not support service-line items.
• Versions 4.6C and 4.7 share the same worksheet, PurchaseOrderEventBAPI.
• If you are using SAP 4.7, the RFCs expect that you are also using SAP Web
Application Server 6.2. If you are using SAP Web Application Server 6.1, search
the RFCs in the ZAR6 development class and replace all occurrences of:
sy-saprl eq ‘620’
with:
sy-saprl eq ‘610’
Pulling Master and Transaction Data

Master data consists of general information stored in SAP that is used in Ariba Buyer
to construct requisitions. Transaction data includes information like remittance advice
in purchase orders and receipts. You pull data using scheduled integration events or
run integrations events manually from Ariba Buyer Administrator.
About Integration Data

Ariba Buyer pulls only the data it needs to create properly formed purchase orders
and receipt information for SAP.
Ariba Buyer pulls the following data from SAP:

• Account assignment categories
• Accounting field display status
• Language-specific names for data pulls
• Asset accounts
• Cost centers
• Company Codes and Global Company Codes

Chapter 1 Introduction Pulling Master and Transaction Data
• General ledger accounts

• Internal orders
• WBS (Work Breakdown Structure) elements
• Currency conversion rates
• Material groups
• Plants
• Purchasing organizations
• Purchasing groups
• Remittance advice
• Status of purchase orders
• Purchase order numbers
• Goods receipts numbers
• Vendors
• Tax codes
Optionally, you can pull the following data from SAP with some configuration on
your part:
• Users
• Release authorizations
• User release authority
Note: Vendor master payment terms pull is available in Ariba Buyer 8.2.
The Ariba Buyer Data Load Guide discusses how to configure this optional data. For
more information about pulls and integration events related to SAP, see the Ariba
Buyer Configuration Reference Guide.
Scheduled Pulls
Each data pull integration event runs on a separate schedule, so you set up different
schedules for pulling different sorts of information. For example, you might want to
pull vendors more frequently than currency conversions if you know the vendor
information changes more often in SAP.

Pulling Remittance Advice Chapter 1 Introduction
The following events occur when Ariba Buyer pulls data from SAP:
1 Each time an integration event runs, it communicates with the TIB/MessageBroker.
2 The TIB/MessageBroker executes the pertinent MessageBroker worksheet

according to which worksheet subscribes to the specific subject being pulled.
3 The TIB/MessageBroker sends instructions to the TIB/Adapter for R/3.
4 The TIB/Adapter communicates with an appropriate Ariba Buyer RFC on your

SAP system to gather the requested information.
5 The RFC reads the ZARIBTVARV table.
6 The RFCs query and process the information from the SAP database.
7 The RFC returns the mapped information to the Ariba Buyer database for use in
valid Ariba Buyer objects.
Pulling Payment Terms

Payment terms pull for single installments is available through the Ariba File
Channel. Payment terms indicates the negotiated discount between a buying
organization and supplier for a specified number of days before payment is due. For
information on ERP considerations for pulling payment terms and adding payment
terms using a CSV file, see the Ariba Settlement Guide.
Pulling Remittance Advice

Remittance advice is an electronic or paper document that identifies and provides
details about which open invoices are in the process of being paid. Remittance details
include the payment methods, bank information, and a list of paid invoices with
discount and paid amounts.
For SAP 4.6C only, remittance pull is available through the Ariba Settlement module.
You can pull remittance advice for payments created for the following within a
specified time period:
• Invoices
• Credit and debit memos

Chapter 1 Introduction Pulling Remittance Advice
Remittance pull is also available for:

• Future-dated payments
• Voided payments, including void checks and reverse payments
Limitations
SAP does not support remittance pull in the following scenarios:
• The payment document contains withholding tax.
• Partial or residual payments are involved.
• The payment document has been reset.
• The payment document is an intercompany payment.
• The payment document is a down payment.
Process Flow
1 Schedule the RemittancePull integration event, or run the RemittancePull
integration event.
2 The RemittancePull integration event calls the RemittancePullEventSAP
MessageBroker sheet.
3 The MessageBroker sheet reads the date TimeStamp file from the Ariba Buyer
installation directory.
4 If the time stamp is found, it passes the date timestamp as an input parameter to the
RFC, that is, Z_ARIBA_REMITTANCE_PULL is called in the MessageBroker sheet.
5 Each payment document in SAP is mapped to create a payment transaction in
Ariba Buyer, or, in the case of a void document, is mapped to update a payment
transaction in Ariba Buyer.
Note: If you want to pull remittance advice only from a specified date for the initial
run, create a date time stamp field.
When you are entering Ariba invoices in SAP, provide the SupplierInvoice number
in the Reference Number field. If you are using the Reference Number field to enter
the Ariba IR number, change the mapping in the MessageBroker sheet as follows:
map the SAP reference number (RemItems-RefDoc) to PayableReferenceNumber
(LineItems-PayableReferenceNumber) instead of SupplierPayableReferenceNumber in
Mapper3.

Pushing and Pulling Purchase Orders Chapter 1 Introduction
In SAP, it is possible to cancel a payment document for a specified payment, or to

re-issue a check for a payment document without cancelling the payment document.
• If a payment document is cancelled in SAP, the corresponding payment transaction
pulled to Ariba Buyer is voided.
• If a check is re-issued in SAP without cancelling the payment document, the entire
payment transaction in Ariba Buyer is voided, and a new payment transaction with
a new check number is created.
Additional Considerations
The following are considerations pertaining to remittance advice pull:
• When the Check Payment method is used, remittance advice is pulled only after
the checks have been printed.
• If a payment is made to a special GL account, such as a Bill of Exchange,
remittance advice is not pulled to Ariba Buyer.
• For manual payments, associated payment methods are not set in the payment
documents. Consequently, an empty payment is pulled regardless of the payment
method set in the invoice document. In the default configuration, the empty
payment method is mapped to the Ariba Buyer payment method “Other.”
• For manual payments, if the check is printed out after the remittance advice is
pulled, the check number is pulled to Ariba Buyer during the next remittance
advice run and updates the “Payment Number” in the Payment Transaction object.
However, it is not pushed to the AN supplier.
• Down payments are pulled as credit-line items after payments are made on the
down payments and their associated invoices, not at the time they are created.
For additional information on ERP considerations when pulling remittance advice,

see the Ariba Settlement Guide.
Pushing and Pulling Purchase Orders

An Ariba Buyer purchase order is pushed to SAP as soon as it is fully approved in
Ariba Buyer.

Chapter 1 Introduction Pushing and Pulling Purchase Orders
The following steps explain how a purchase order push integration event works:
1 If the order is destined for SAP, Ariba Buyer sends the order to
TIB/MessageBroker.
2 TIB/MessageBroker executes the purchase order push worksheet to obtain the
correct worksheets.
3 TIB/MessageBroker transforms the data into the format required by the
Z_ARIBA_PO_PUSH RFC and then sends the data to Ariba Buyer push RFCs through
the TIB/Adapter for R/3.
4 The Z_ARIBA_PO_PUSH RFC creates purchase orders through purchase order creation
transactions within SAP.
5 The Z_ARIBA_PO_PUSH RFC returns purchase order details, including the purchase
order number, and any errors that occur.
The following features are not provided in the push purchase order integration with
Ariba Buyer:
• Pushing the title of purchase orders to SAP.
• Support for the “deliver to” or “ship to” address in an Ariba Buyer purchase order.
In many circumstances, the plant field provides the information for SAP to deliver
to the address field in purchase orders.
Adjusting Net Price

When pushing amounts, the Ariba Buyer RFC adjusts the net price to the number of
decimals specified for that currency in the SAP TCURX table.
• If the currency is listed and specifies a number greater than zero in the Decimals
column, the RFC adjusts the net price to the number of decimals and price unit
accordingly.
• If the currency is not listed in the table, the RFC adjusts the net price to two
decimal places, which is the default specified in Z_ARIBA_PO_PUSH.
• If the currency is listed in the table but specifies zero in the Decimals column, the
lengths of the net price and price unit are adjusted accordingly.
• Price units are adjusted to a maximum of 10,000 units, at which point an error
message is sent.

Pushing Purchase Orders Using BAPI Chapter 1 Introduction
For example, if the number of decimals allowed in SAP is two for USD and if Ariba
Buyer sends a net price (that is, unit price) of 100.023, the wrapper RFC adjusts the
net price to 1000.23 and the unit price to 10. If the price unit exceeds 10000, an error
message is sent to Ariba Buyer if PO Push using RFC is in use.
Pushing Purchase Orders Using BAPI

The default configuration of Ariba Buyer uses RFCs to push data into SAP. SAP
provides a BAPI interface to push purchase order data. Rather than integrating
through procedural RFC code, the BAPI integration uses an API. The default
configuration of Ariba Buyer uses RFCs for purchase order pushes.
If you are using BAPI to push purchase orders, you use the PurchaseOrderPushBAPI
integration event instead of PurchaseOrderPush. To make sure the correct event is
used, do the following:
• Set the Disable parameter to false for PurchaseOrderPushBAPI.
• Add Disable = true to PurchaseOrderPush in the MessageConfiguration.table file
in each partition where you are using BAPI to push purchase orders.
Understanding BAPI Push Limitations

The BAPI integration with Ariba Buyer does not provide support for the following
features:
• Pushing tax code information
• Split accounting for service-line items
• Ariba Buyer push field mapping mechanism. If you need to add Ariba Buyer
extrinsic fields to BAPI objects, you add these fields to the BAPI structures and
update the SAP schema for the TIB/MessageBroker worksheets.
BAPI truncates the price if it has more than two decimal places, regardless of the
number of decimal places allowed for that currency.
BAPI truncates the net price if it has more decimal places than those defined in the net
price currency.

Chapter 1 Introduction Pushing Changed and Canceled Purchase Orders
If a purchase order or a change purchase order is pushed using a BAPI, the carriage
returns in the line item text are pushed and displayed as the hash character '#' in the
line item text in the SAP purchase order.
Pushing Changed and Canceled Purchase Orders

If you are using SAP 4.6c or 4.7, Ariba Buyer can push changed and canceled
purchase orders (CPO) to SAP. For information on this feature and how to enable it,
see the chapter on changing existing orders in the Ariba Buyer Procurement Guide.
When Ariba Buyer pushes a changed or canceled purchase order, it uses the RFC
Z_ARIBA_BAPI_PO_CHANGE or Z_ARIBA_BAPI_PO_CANCEL to fill the BAPI tables, and, in
turn, calls BAPI_PO_CHANGE to push the purchase order to SAP.
The following are important notes about pushing changed and canceled purchase
orders to SAP:
• If you enable the change/cancel purchase order feature, users must always change
and cancel orders through Ariba Buyer and not change or cancel them through
SAP. Therefore, apply the appropriate authorization concept in SAP to prevent
users from changing purchase orders directly in SAP.
• To enable the change/cancel purchase order feature, you install the change/cancel
order transport. The transport number is listed in the transport readme.txt file. See
Appendix B, “About SAP Transports,” for more information.
• The change/cancel purchase order feature has been tested with specific SAP
support packages. If you installed different support packages, the BAPI interface
might be different. In this case, either install the tested support packages or modify
Z_ARIBA_BAPI_PO_CHANGE and/or Z_ARIBA_BAPI_PO_CANCEL. For a complete list of the
tested support packages, see the Ariba Buyer Release Guide.
• A limitation in the standard SAP BAPI creates the following situation: If the
Account Assignment category is modified in Ariba Buyer, the Account
Assignment category is changed in SAP. Furthermore, the GLAccount is changed
to a default GLAccount after it has been pushed to SAP. To resolve this issue,
modify the GLAccount in SAP using the Account Assignment tab in the Item Detail
section.
• Support packages SAPKH46C30 and SAPKH46C42 are required for text updates.
• On SAP service orders, you cannot change the line items, but you can delete them
or cancel the entire order.

Pushing Changed and Canceled Purchase Orders Chapter 1 Introduction
• To debug the change/cancel purchase order feature, set the parameter

Z_ARIBA_DEBUG_CPO to X and set Z_ARIBA_CPO_FNAME to the name of a log file where
the change/cancel order information is logged. You set both of these parameters in
the ZARIBTVARV table.
• Plant data is not editable if the Purchase Order Line Item is partially or fully
received or partially or fully invoiced in Ariba Buyer or SAP.
Pulling Header Status of Purchase Orders

When changed orders are in a Received, Receiving, or Invoiced, or Invoicing state,
Ariba Buyer cannot cancel them. Similarly, when purchase orders have been received
or invoiced in SAP, the cancel push to SAP fails.
If an order reaches SAP successfully, its status can still change in SAP. For example,
if you receive against an order in SAP, a subsequent cancel order from Ariba Buyer is
certain to be rejected. To reduce the occurrence of such situations, Ariba Buyer
provides a scheduled task, ProcessERPHeaderStatusPull, which pulls header status
information from SAP. This task sets a field in Ariba Buyer, ERPAllowCancel, which
specifies whether the order can be canceled.
Note: Use ProcessERPHeaderStatusPull only if you have enabled change and cancel
order push to SAP and you are doing a lot of receiving in SAP.
The scheduled task ProcessERPHeaderStatusPull does not eliminate all the cancel
push failure errors. SAP uses many factors to determine if it is possible to cancel an
order. However, the status pull is based on invoicing and receiving status.
ProcessERPHeaderStatusPull pulls the status for all orders in the Ordered state for the
time period (days before the current date) you specify in the QueryPeriod parameter.
You can also specify the schedule for the ProcessERPHeaderStatusPull task in
ScheduledTask.table.
The RFC Z_ARIBA_PO_HEADER_STATUS is used to pull the status information from SAP.

Chapter 1 Introduction Pushing Receipts
Pushing Receipts
You schedule receipt push integration events or run them manually from Ariba Buyer
Administrator.
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 approved.
Note: Receipts are not pushed to SAP if the total accepted quantity is zero. This
situation occurs when a user rejects the items and does not accept any items.
2 When the scheduled receipt push scheduled task runs, or is run manually, Ariba
Buyer sends the receipt object to the TIB/MessageBroker receipt push worksheet.
Note: The scheduled task ProcessReceipts posts receipts from Ariba Buyer to SAP.
However, you cannot post a receipt successfully in SAP if the period has been
closed in SAP.
The following are ways to address this problem:

• Set the ProcessReceipts scheduled task and its delay period so the receipt is
approved in Ariba Buyer and, in turn, is posted in SAP on the same day.
• Postpone the closing period in SAP for one or two days so that when you post
the receipt in SAP, the period is still open.
For more information on scheduled tasks, see the Ariba Buyer Configuration
Guide.
3 The worksheet defines the transformation of the data into the format required by
the RFC. Then TIB/MessageBroker sends the data to Ariba Buyer receipt push
RFCs through the TIB/Adapter for R/3.
4 Ariba Buyer Z_ARIBA_GR_PUSH RFC processes the data and inserts it in receipt
creation screens in SAP.
5 The RFC returns a receipt line number and any error information to Ariba Buyer.

Chapter 2
Ariba Buyer Setup
This chapter presents the tasks you complete to configure Ariba Buyer mechanisms
for integration with SAP. It includes the following sections:
• “Installing and Configuring Ariba Buyer” on page 27
• “Initializing the Channel” on page 30
• “Setting Up the TIB/Adapter Using TIB/Designer” on page 31
• “Starting the TIB/Adapter for Each Partition” on page 35
Installing and Configuring Ariba Buyer

When you run the configure command during installation and implementation,
consider the following:
• Use the Demo Version option.
This option creates all the CSV source files you need for an SAP partition.
If you choose the Basic Version option, you don’t have any CSV files for your
implementation.
• Verify configuration file information.
Running the configure command creates entries in the SAPConnectionInfo.table
file, which is described in the next section. Make sure you to review the entries in
this file for accuracy.
Verifying Connection Information

The SAPConnectionInfo.table file contains many settings for you to verify, but the
settings most relevant to SAP integrations describe connection information to your
SAP system.The SAPConnections parameters provide the information Ariba Buyer
needs to communicate with your SAP systems.

Chapter 2 Ariba Buyer Setup Installing and Configuring Ariba Buyer
You create a set of SAPConnections parameters for each SAP instance with which
Ariba Buyer communicates. This document refers to the unique instance name of
your destination SAP system as SAPInstanceName. If you have multiple SAP systems,
each instance name must be unique. For additional information on these parameters,
see the Ariba Buyer Installation Guide for your operating system.
SAP Connection Parameters and Descriptions
Parameter Description
System.SAPConnections.SAPInstanceName. Defines the client identification
ClientID number for the SAP instance.
System.SAPConnections.SAPInstanceName. Defines the destination SAP
Destination instance name.
System.SAPConnections.SAPInstanceName. Represents the gateway for the
SAPGateway instance.
System.SAPConnections.SAPInstanceName. Represents the gateway service for
SAPGatewayService the instance.
System.SAPConnections.SAPInstanceName. Represents your SAP host name
SAPHost for the instance.
System.SAPConnections.SAPInstanceName. Sets the default language for the
SAPLanguage instance according to SAP’s
abbreviations.
System.SAPConnections.SAPInstanceName. Sets the password for connecting
SAPPassword to the instance.
System.SAPConnections.SAPInstanceName. Represents the system number of
SAPSystemNumber the SAP system for the instance.
System.SAPConnections.SAPInstanceName. Defines the user that Ariba Buyer
SAPUser uses to connect to the instance.
System.SAPConnections.SAPInstanceName. Determines whether the
SetTrace connection uses tracing. Set the
parameter to 0 to turn it off, and to
1 to turn it on. The default is 0.

Installing and Configuring Ariba Buyer Chapter 2 Ariba Buyer Setup
Configuring for Multiple Partitions

If you are using multiple SAP partitions for the same SAP variant, make sure you
uniquely identify each SAP Connection for every partition in the SAPConnections
parameter in SAPConnectionInfo.table. 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;
}
Specifying the Locale for the TIB/Adapter for R3

To configure the TIB/Adapter for R/3 by specifying the character encoding to use for
exchanging data with SAP, you use the parameter
Application.Messaging.Channels.Tibco.GlobalProcesses.SAPAdapterLocale in your
named partition. This parameter is used only in SAP configurations that do not use
US English as the default language. The value specifies the character encoding in
which data is transferred.
Using a command-line argument, Ariba Buyer passes the value you specify to the
TIB/Adapter for R/3 as the setlocale parameter. The SAPAdapterLocale parameter
determines the logon locale you use to run the TIB/Adapter for R/3. The logon locale,
in turn, determines the character encoding used to transfer the data. The value
determines the character encoding in which data is transferred.

Chapter 2 Ariba Buyer Setup Initializing the Channel
To set up this parameter, add an entry for each operating system where you run the
TIB/Adapter. For each operating system, list the value in the format locale/encoding,
where the locale and encoding are valid on the operating system you specify. Valid
operating system codes are HPUX, Solaris, AIX, and NT.
For example:
Application = {
Messaging = {
Channels = {
Tibco = {
GlobalProcesses = {
SAPAdapterLocale = {
AIX = ibm-943;
HPUX = ibm-943;
NT = ibm-943;
Solaris = ibm-943;
;
};
};
};
};
};
In the previous example, the configuration runs one adapter on AIX, one adapter on
HP-UX, one adapter on NT, and one adapter on Solaris. For each of those adapters,
the locale/encoding is appropriate for a Japanese language configuration.
For more information on the available options to setlocale, see the documentation for
R/3 on the TIBCO product CD.
For additional details on the parameter

Application.Messaging.Channels.Tibco.GlobalProcesses.SAPAdapterLocale, see the
Ariba Buyer Configuration Reference Guide.
Initializing the Channel

After installing and configuring Ariba Buyer, you initialize the channel and repository
database fully. If you are using TIBCO as your integration channel, you initialize the
channel and TIB/Repository using the following command:
initdb -initchannel

Setting Up the TIB/Adapter Using TIB/Designer Chapter 2 Ariba Buyer Setup
This command creates all the necessary channel-related items to prepare for loading
data into Ariba Buyer. For instructions on running the initdb command, see the Ariba
Buyer Installation Guide.
After initializing the channel repository database, you set up the TIB/Adapter.
This rest of this section describes these steps for TIBCO. If you are using another
integration channel, such as IBM WebSphere BI Adapter, see the documentation from
the channel’s vendor.
Setting Up the TIB/Adapter Using TIB/Designer

TIB/Designer enables you to configure connection information for your TIB/Adapter
for R/3.
Note: TIB/Designer is supported only on Windows configurations. For details on

using the TIB/Designer in other environments, see the Ariba Buyer TIBCO
Configuration Guide.
W To set up the TIB/Adapter using TIB/Designer:

1 If you are in the design process, start the SAP Design-Time Adapter by running:
runtibco -startsapdta variant
2 After you start the SAP Design-Time Adapter, run TIB/Designer by typing:
runtibco -startdesigner
3 In TIB/Designer, choose an existing project.

The Open Project dialog box appears.
4 On the Server Project tab, click the Show Advanced checkbox, and verify the contents
of the Daemon, Network, and Service fields.
5 Click Discover Domains, select the domain you want, and click OK.
6 Click Load Project List.
7 From the Project List, select the SAP project you want, and click OK.
The project you selected opens.

Chapter 2 Ariba Buyer Setup Setting Up the TIB/Adapter Using TIB/Designer
You use TIB/Designer for configuration tasks described in the following sections:
• “Verifying Client Connection Information” on page 32
• “Verifying Client Information” on page 32
• “Verifying Parameters for Connection Retries” on page 33
• “Verifying Server Connection Information” on page 34
• “Exporting SAP Configuration Changes to Synchronize Data” on page 34
Verifying Client Connection Information

You use TIB/Designer to verify and edit the following client connection information
for TIB/Adapter for R/3:
• System number
• Application server
W To verify client connection information for TIB/Adapter:

1 In the folder window of the TIB/Designer, select the TIB/Adapter for the R/3
instance you want, for example:
vsap/R3Connections/ClientConnections/SAInboundRFC.psap/RFCClientConnectionP
ool
2 In the Configuration panel, click the Inbound Connection tab, and verify the contents
of the Application Number and System Number fields.
3 Make any necessary changes.
4 Click Test Connections.
Verifying Client Information

You use TIB/Designer to verify or edit the following client information for the
TIB/Adapter for R/3:
• Client Number
• User Name—the Ariba Buyer CPIC (Common Programming Interface for
Communications, which is a standard call interface for applications that perform
direct program-to-program communication) user name for integrations.
• Password—the Ariba Buyer CPIC user password for integrations.
You encrypt the password using aribaencode. For more information, see Ariba
Buyer Configuration Guide.

Setting Up the TIB/Adapter Using TIB/Designer Chapter 2 Ariba Buyer Setup
• R/3 Logon Language—the default SAP language code for the Ariba Buyer CPIC
user.
W To verify client information for the TIB/Adapter:

1 In the folder window of TIB/Designer, select the TIB/Adapter instance you want,
for example:
vsap/R3Connections/Clients/SAInboundRFC.psap-CLNTOOL
2 In the Configuration panel, click the Configuration tab, and verify the contents of the
Client Number, User Name, Password, and R/3 Logon Language fields.
3 Make changes, if necessary.
4 If you have made changes, click Apply. To change the contents of the fields back to
their initial settings, click Reset.
Verifying Parameters for Connection Retries

You use TIB/Designer to verify and edit three parameters that enable connection
retries if an adapter disconnects from the TIB/Adapter for R/3.
• Retry Attempts—Specifies the TIB/Adapter’s maximum number of SAP
reconnection attempts
• Time Between Retries—Specifies the delay, in milliseconds, between each
reconnection attempt
• Retry Increment—Specifies, incrementally, the retry interval
• Maximum Connections—Specifies the maximum number of inbound RFC
connections allowed
W To verify retry parameters for connection retries for the TIB/Adapter:

1 In the folder window of the TIB/Designer, select the TIB/Adapter instance you
want, for example:
vsap/R3Connections/ClientConnections/SAInboundRFC.psap-RFCClientConnection
Pool
2 In the Configuration panel, click the Advanced tab, and verify the contents of the
Retry Attempts, Time Between Retries, Retry Increment, and Max Connections
fields.

Chapter 2 Ariba Buyer Setup Setting Up the TIB/Adapter Using TIB/Designer
4 If you have made changes, click Apply. If you want to change the contents of the
fields back to their initial settings, click Reset.
Verifying Server Connection Information

You use TIB/Designer to verify and edit the following server connection information
for the TIB/Adapter:
• Program ID
• Gateway Service—Make sure your SAP number creates the last two characters.
For example, if your SAP system number is 08, the entry must read sapgw08.
• Gateway Host—Make sure the SAP host name is set to where you install and
configure ALE/IDOC mechanisms.
W To verify server connection information:

1 In the folder window of TIB/Designer, select the TIB/Adapter instance you want,
for example:
vsap/R3Connections/ServerConnections/SAInboundRFC.psap-RFCServerConnection
Pool
2 In the Configuration panel, click the Configuration tab, and verify the contents of the
Program ID, Gateway Service, and Gateway Host fields.
4 If you have made changes, click Apply. If you want to change the contents of the
fields back to their initial settings, click Reset.
Exporting SAP Configuration Changes to Synchronize Data

Templates to represent the configuration and schema information for the TIB/Adapter
for R/3 are located in the following locations:
• config/variants/variantName/partitions/partitionName/tibco/sapconfig.xml
• config/variants/variantName/partitions/partitionName/tibco/saprealtimeconfig
.xml

Starting the TIB/Adapter for Each Partition Chapter 2 Ariba Buyer Setup
When you run the runtibco -loadsap command, configuration data is:
• Read from Parameters.table and SAPConnectionInfo.table.
• Written into these template files.
• Imported into the TIBCO Repository database.
The runtibco -loadSAP command replaces the existing SAP schema and
configuration data in the TIBCO Repository with the configuration present on the
disk. This command usually runs during the initdb -initchannel command sequence
when the SAP Repository instance is created for the first time.
Ariba recommends that you use runtibco -loadSAP only to update and load into the
TIBCO Repository any connection information defined in SAPConnectionInfo.table.
Make all schema-related changes directly in the TIBCO Repository through the SAP
Design-Time Adapter, as described in “Setting Up the TIB/Adapter Using
TIB/Designer” on page 31.
After you make changes to the SAP schema or configuration using the SAP
Design-Time Adapter, use the runtibco -exportSAPConfig command to export the
changes to the following files:
• config/variants/variantName/tibco/sapconfig.xml
• config/variants/variantName/tibco/saprealtimeconfig.xml
Exporting the changes to these files ensures that the information on the disk is current
and avoids inadvertently replacing the information in the TIBCO Repository with
what is on the disk.
Starting the TIB/Adapter for Each Partition

To start the TIB/Adapter for R/3 for each SAP partition, enter the following
command:
runtibco -startsapadapter variant partition
This command starts a single TIB/Adapter program file, adr3, for integration with an
SAP system for a single partition.
You install and configure one TIB/Adapter for each SAP partition in Ariba Buyer.

Chapter 2 Ariba Buyer Setup Starting the TIB/Adapter for Each Partition

Chapter 3
SAP Setup
Before using Ariba Buyer with SAP, you configure your SAP system and install the
Ariba development classes. This chapter provides the information you need to
configure and install Ariba Buyer items for your SAP system. Ariba recommends that
you have an SAP BASIS administrator assist you.
Note: Before you complete the tasks in this chapter, you must perform the tasks in
Chapter 2, “Ariba Buyer Setup.”
This chapter includes the following sections:

• “Setting Up Ariba Users” on page 37
• “Installing Ariba Buyer SAP Transports” on page 40
• “Working With the Time-out Interval” on page 44
• “Checking Data” on page 46
• “About Real-Time Loading” on page 48
• “Receiving Tolerances” on page 48
• “Testing Connections” on page 49
Setting Up Ariba Users

To work with your SAP instance, you create user accounts for Ariba Buyer and Ariba
Buyer implementation personnel. Create the following users:
• One CPIC user for both Ariba Buyer and the TIB/Adapter for R/3 to use
• One or more dialog users for Ariba Buyer implementation personnel to use and to
assist with debugging

Chapter 3 SAP Setup Setting Up Ariba Users
Creating a CPIC User

In a complete Ariba Buyer implementation, a CPIC user affords Ariba Buyer and the
TIB/Adapter for R/3 access to Ariba Buyer RFCs. Make sure to grant the CPIC user
unrestricted access to your SAP instance with SAP_ALL and SAP_NEW privileges 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.
When connecting to SAP, you choose an account for Ariba Buyer to use. Ariba
recommends you create a new account, but use an existing account if you prefer.
The default user name for this account is ariba. Whichever user you choose, check
the user defaults and make sure they are set as follows:
• For date format: MM/DD/YYYY
• For decimal notation: . (period)
W To create a CPIC user:

1 Access the Maintain Users: Initial Screen using SU01.
2 Enter the user ID you have chosen for Ariba Buyer integration, and click the Create
icon.
3 Click the Logon data tab.
4 Enter the password for the Ariba user in the Initial password field, and click the
CPIC radio button for User Type.
5 In the Profiles tab, enter a profile for SAP_NEW and SAP_ALL.
The other fields in the screen are optional. Fill them in as you want. Choose the
Enter check when you finish.
6 In the Defaults tab, 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 want, and
choose the enter check. In the Parameters tab in the next screen, complete the fields,
or leave them blank, as you want.

Setting Up Ariba Users Chapter 3 SAP Setup
Understanding Dialog Users

You create dialog users for Ariba Buyer implementation to:
• Provide SAP administrators and Ariba Buyer implementation personnel necessary
access to Ariba Buyer RFCs and your SAP instance.
• Allow Ariba Buyer visual dialog access for testing integrations.
About Implementation Dialog Users

You might 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. This practice is necessary
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.
• Customize or extend Ariba Buyer RFCs and RFC structures.
• Configure Application Link Enabling (ALE) for real-time configuration.
About Ariba Buyer Testing Dialog User

As you implement your Ariba Buyer integration, you might find it necessary to step
through the processes of Ariba Buyer RFCs to understand better how they work. In
particular, you might want to see how Ariba Buyer inserts purchase order and goods
receipt fields into SAP screens.
To view Ariba Buyer integrations within the SAP user interface, you allow Ariba
Buyer and the TIB/Adapter for R/3 to access SAP through a dialog user ID. For
convenience, you might use the default user name ariba for this account. As with the
CPIC ID, check the user defaults and make sure they are set as follows:
• For date format: MM/DD/YYYY
• For decimal notation: . (period)

Chapter 3 SAP Setup Installing Ariba Buyer SAP Transports
Installing Ariba Buyer SAP Transports

You import Ariba Buyer transports to integrate Ariba Buyer with SAP. For a list of
the transports, see the readme.txt file at the following location:
BuyerServerRoot/configureOptions/sap/ariba/variant/trans
If you are integrating with SAP, it is required that you install SAP transports as part of
your Ariba Buyer installation. This section provides background information about
the Ariba-delivered SAP transports and detailed instructions for installing them.
Note: Ariba recommends that you ask your SAP BASIS personnel to install the
Ariba-delivered transports.
Delivered Transport Types

Ariba delivers three types of SAP transports to enable integration with Ariba Buyer.
These types include the following:
• Base functionality transport, containing Ariba SAP objects common to all SAP R/3
releases. This transport contains both workbench objects and
client-dependent and independent configurations.
• Real-time integration transport, required if you are exchanging cost center, general
ledger, and vendor data in an incremental, real-time fashion.
• SAP R/3 version-specific transport, required for particular SAP R/3 releases.
Location of Transport Files

The Ariba-delivered SAP transports are installed in the following directory under
your Ariba Buyer Server installation directory:
BuyerServerRoot/configureOptions/sap/ariba/variant/trans
Within this directory are subdirectories containing data files and cofiles for the
Ariba-delivered transports. Each transport has one data file and one cofile. The data
file names begin with the letter R, and cofile names begin with the letter K. For
example, a transport named ABCK900123 might have the following data file and cofile:
trans/data/R900123.ABC
trans/cofiles/K900123.ABC

Installing Ariba Buyer SAP Transports Chapter 3 SAP Setup
Copy the Ariba transports from the location on your Ariba Buyer system to the
relevant subdirectories on your SAP system.
Transport Installation Instructions

The process for installing transports is the same for both first-time installations and
upgrades. Ariba delivers a set of transports for each SAP version for both installation
and upgrade. For complete information on installing transports, see the
BuyerServerRoot/configureOptions/sap/ariba/variant/trans/readme.txt file. You
navigate to this directory under mainerp on the Ariba Buyer CD or under the Ariba
Buyer installation root.
Warning: The transports contain both client-dependent and independent

configurations. Therefore, specify a target client when adding these transports to your
import queue. If you are using TMS (Transport Management System), enable the
target client to be specified in the queue by using extended transport control.
Import Considerations
In general, you do not use any umodes when installing these transports. Use umodes
in the following circumstances:
• You have a previous version of the Ariba objects in your SAP system, and some
core objects have been modified. In this situation, override the repair flag on import
by using a umode. Reinstate any overwritten modifications to Ariba core objects
using the appropriate SAP tools.
• You need to reimport one of the delivered transports. In this situation, make sure
the transport is fully reimported by using umode 1.
If you do not require real-time integration, you do not have to import the real-time
integration transport. However, if you do install this transport, configure your SAP
system to use real-time integration with Ariba Buyer after the import is complete. See
“Real-Time Integration Transport” on page 43.

Chapter 3 SAP Setup Installing Ariba Buyer SAP Transports
Transport Description Reference

This section describes the contents of the transports provided with this release of
Ariba Buyer.
Base Functionality Transport

The following table describes the content of the base functionality transport for this
release.
Content Description Client Dependent?

Data dictionary objects for Ariba core and customer layers No
Structures and function modules added between 6.x and 7.0 No
ZAR6 and ZARC development classes No
Document type “AR” for Ariba Buyer orders (View V_T161) Yes
Table maintenance editor for ZARIBTVARV No
Transport and Table maintenance editor for ZARGRFMAP and No
ZARGRFMAPX. Tracks the fields in which Ariba Buyer pushes
goods receipts.
Default goods receipt field mappings for the ZARGRFMAP table No

Installing Ariba Buyer SAP Transports Chapter 3 SAP Setup
Real-Time Integration Transport

The following table describes the content of the real-time integration transport for this
release.

Customer extension layer for IDOC code. Main development No
class is ZATC.
ZATI development class: IDOC code No
Client-dependent ALE/IDOC items for incremental loading: Yes
• Ariba Buyer message types: ZATCOS, ZATCRE, and ZATGLM
• Additional data for message type BD60
Assign message types to IDOC types (WE82, BD69) Yes
Activate ALE and change pointers for message types ZATCOS, Yes
ZATCRE, and ZATGLM (BD50). Also activate change pointers for
each document item (BD52).
SAP R/3 Version-Specific Transports

This section describes the content of the SAP R/3 version-specific transports for this
release.

Chapter 3 SAP Setup Working With the Time-out Interval
Transports for SAP 4.6C

The following table describes the SAP 4.6C version-specific transports for this
release.

Purchase order push using BAPI wrapper, which includes No
development classes ZAR7 and ZAR8
Change order integration using BAPI wrapper, which No
includes development classes ZARIBA_CHANGEORDER and
ZARIBA_CUSTCHANGEORDER
Remittance pull using BAPI wrapper, which includes No

development classes ZARIBA_REMITTANCE and
ZARIBA_CUST_REMITTANCE
Transports for SAP 4.7

The following table describes the SAP 4.7 version-specific transports for this release.

Purchase order push using BAPI wrapper, which includes No
development classes ZAR7 and ZAR8
Change order integration using BAPI wrapper, which No
includes development classes ZARIBA_CHANGEORDER and
Working With the Time-out Interval

The SAP system has a time-out limit on RFC transactions. The limit makes sure no
resources stay locked in the SAP system inadvertently. 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 might encounter this time-out limit. In this
case, the SAP system could cancel the job. To avoid this problem, you change your

Working With the Time-out Interval Chapter 3 SAP Setup
SAP configuration to lengthen the time-out interval. Change the interval on your
central instance as well as any application servers that communicate with Ariba. For
the change to take effect, restart each SAP server.
Note: Make sure to enlist the help of your BASIS administrator to make these
changes.
W To set the time-out interval:

1 Log in as the SAP Administrator.
2 Run transaction RZ10.
3 Enter the Instance Profile.
4 Enter the most current version (you create a new version based on the most current
one).
5 In the Edit profile panel, click the Extended maintenance radio button.
6 Click Change.
7 Scroll down to Parameter name rdisp/max_wprun_time.
If the value does not appear in your profile, create it by choosing Create from the
Parameter menu.
8 Create or change the value of rdisp/max_wprun_time to something longer, for

example, 3000 (for 3000 seconds).
9 From the Parameter menu, choose Change.
10 Click Copy.
This step makes a copy of the new profile. The status line displays the message
“Changes were made.”
11 Navigate back to the initial Edit Profiles screen, and save the changes.
12 From the Profile menu, choose Activate.
13 Restart your SAP server for the profile changes to take effect.
14 Repeat the steps in this procedure for each application server that exchanges data
with Ariba Buyer.

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

Ariba Buyer pulls currency conversion information from the SAP system to make
sure all purchase orders from Ariba use currencies valid in SAP. In the default
configuration, the bank selling rate is B. The currency conversion pull pulls all
currency conversions associated with the bank setting rate B. The pull fails if the rate
is not configured in the system. If you want to specify a different bank selling rate,
add an entry in the ARIBATVARV table for the BANK_SELLING_RATE_SYMBOL parameter.
W To find the bank selling rate symbol:

1 Run transaction spro.
2 Choose General Settings > Currencies > Check Exchange rate types. 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, the pull ignores that item, and it does not appear in the Ariba Buyer system.
Check your SAP system to make sure all material groups and purchasing groups have
valid—that is, 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 has partner functions specifying
multiple ordering addresses. The SAP integration pulls one ordering address only, so
users cannot choose from among multiple ordering addresses.

Checking Data Chapter 3 SAP Setup
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.
Vendor ERS Tax Status

Ariba Buyer supports vendors from SAP that offer evaluated receipt settlement (ERS)
agreements. These agreements have different tax rates depending on many factors,
such as the tax laws in the location of the supplier and requestor.
Purchase orders from Ariba Buyer for SAP contain a field to determine whether 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 you to 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.
• To correct this problem, configure SAP to set a default tax code.
• If you cannot configure a default tax code, change the message type from error to
information or warning in SAP.
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. 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 has been corrected.

Chapter 3 SAP Setup About Real-Time Loading
About Real-Time Loading

Real-time loading allows Ariba Buyer to obtain updates from SAP for new, changed,
or deleted data. Real-time loading can significantly decrease the amount of time it
takes for Ariba Buyer to load information from SAP.
To use the real-time loading features with your Ariba development classes, you
perform further configuration. For instructions, see “Real-Time Integrations” on
page 115.
Receiving Tolerances
Ariba Buyer allows users to enter receiving information about the items they order. To
support this feature, 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 have
ordered.
Receiving System Parameters

Ariba Buyer allows you to configure receiving tolerances through the following
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.UnderReceivingPercentage
To learn how to set these values, see the Ariba Buyer Procurement Guide.
Make sure you know the following facts about Ariba Buyer receiving integration:
• Ariba Buyer does not push receipt tolerances when pushing a purchase order.
• Ariba Buyer does not pull tolerances from SAP, but instead uses only those
tolerances in the system parameters table.

Testing Connections Chapter 3 SAP Setup
• For receiving integration to work, make sure the receiving tolerances in Ariba
Buyer match the receiving tolerances in SAP.
ERP Orders
ERP orders are purchase orders that Ariba Buyer pushes to an ERP (such as SAP)
instead of sending them to the vendor. Ariba Buyer expects SAP to handle the ERP
orders and transmit them to vendors.
Be careful about receiving integration with ERP orders because SAP users and
processes can change an ERP order after the ERP order is in SAP. Such changes can
cause errors, especially if 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 have been fulfilled.
See your Ariba Solutions Delivery representative to obtain more information and to
decide if ERP orders are appropriate for your implementation.
Testing Connections
Three ways are available for you to test your connection to SAP from Ariba Buyer
after you have completed the tasks in this chapter, performed TIBCO-related initdb
commands, and completed the tasks in Chapter 2, “Ariba Buyer Setup.” You can use
the following:
• runtibco command (-startsapadapter option)
• SAP user interface
• TIB/Designer
W To test your SAP connection using the runtibco command:

1 Start the Repository server:
runtibco -start
2 Run the TIB/Adapter for R/3:

3 Examine the TIB/Adapter for R/3 log file.

The TIB/Adapter creates a log file in ~\logs\tibco\sapadapter

Chapter 3 SAP Setup Testing Connections
4 Open the file in a text editor. If you see entries such as the following, you have
connected successfully to SAP:
SAPAdapter 2000 Aug 02 10:44:35:745 R3-CORE-LIB-6006 info Adding RFC
function "Z_ARIBA_ACC_FIELD_STATUS"
function "Z_ARIBA_ACCOUNT_CAT_NAMES"
function "Z_ARIBA_ACCOUNT_CATEGORY"
5 If you find RFC-related error messages in the file, verify the SAP configuration
using TIB/Designer, as described in “Setting Up the TIB/Adapter Using
TIB/Designer” on page 31.
W To test your SAP connection using the SAP user interface:

1 Log in to SAP through the SAP user interface.
2 View the Gateway monitor.
3 Find an entry for the Ariba Buyer host if you started the TIB/Adapter for R/3.
4 Connect from the Ariba Buyer system through the SAP user interface to make sure
no other factors not related to Ariba Buyer or TIBCO products are affecting your
connection.
W To test your SAP connection using TIB/Designer:

1 Start the SAP Design-Time Adapter:
runtibco -startsapdta variant
2 Open TIB/Designer.
3 Select the adapter instance, for example, select SAPInboundRFC.partition from

repoInstance\Legacy Adapters\SAPAdapter 4.0\SAInboundRFC.partition.
4 Click the Configuration tab in either the Inbound Connection or Design-Time Connection
tab, as appropriate.
5 Specify the proper connection information for the SAP system you want to connect
to.
6 Click Test Connection.
The Connection Success message box appears if your information has been
correct.

Chapter 4
Configuring Pulls
Ariba Buyer provides the worksheets and integration events for standard Ariba Buyer
data pulls from SAP. Because your SAP implementation might contain additional
data to be included with Ariba Buyer purchase orders or receipts, you modify these
data pulls to include such data.

• “Pulling Additional Fields Into Ariba Buyer” on page 52
• “Pulling New Tables Into Ariba Buyer” on page 55
• “Pulling Remittance Advice” on page 60
• “Filtering” on page 63
• “Example RFC” on page 73
The information presented in this chapter is intended for SAP administrators and
developers. Performing the tasks detailed in this chapter requires familiarity with the
ABAP/4 (Advanced Business Application Programming) language and proficiency in
basic SQL tasks.
This chapter describes how to create and edit objects in your SAP instance. When you
make changes to Ariba Buyer objects in SAP, you might encounter the following
warning: “Only urgent repairs in the consolidation system.” This warning appears
when you change objects on both consolidation and development systems and
indicates that you’re making changes to objects that originated in another system. In
this particular case, the objects originated from Ariba. The SAP client expects you to
develop your own objects on a development system rather than to change objects from
third-party vendors. Therefore, in the context of this chapter, it is safe to disregard this
warning message.

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

This section describes how to configure Ariba Buyer custom RFCs to pull additional
fields into Ariba Buyer for existing pull integration events. It includes the following
sections:
• “About Extension Structures” on page 52
• “Adding Fields to Extension Structures” on page 54
• “Extension Structure Example” on page 55
To customize Ariba Buyer RFCs, you identify the data to be pulled, the RFCs to be
used, and the structures where this data appears.
About 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 pull extrinsics into Ariba
Buyer from CSV (comma separated value) files, databases, or ERP systems.
Customer development classes like ZARC provide special structures, called extension
structures. You use extension structures 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. See “Summary of Ariba SAP
Development Classes” on page 138 for a comprehensive list of customer development
classes.

Pulling Additional Fields Into Ariba Buyer Chapter 4 Configuring Pulls
Ariba Buyer RFCs use these extension structures to determine which fields to create
in the tables they export to Ariba Buyer. Essentially, extension structures function as a
template to define the structure of the Ariba Buyer RFC tables. A diagram of this
concept follows:
Ariba Buyer TIB/MessageBroker worksheets retrieve the tables through RPC clients.
The integration channel incorporates the table data into Ariba Buyer objects
according to the field and object descriptions in SAP schema.
Extension structures have all the fields in the core Ariba development structures such
as ZAF6 in addition to any fields you add. The contents of an extension structure are
shown in the following diagram:
For example, the ZXTASSET extension structure for asset pulls contains a substructure
called ZARASSET. The ZARASSET substructure holds all the base fields that Ariba Buyer
RFCs need to run. To add new asset fields to Ariba Buyer RFC data pulls, you add
them to the ZXTASSET structure.

Chapter 4 Configuring Pulls Pulling Additional Fields Into Ariba Buyer
Note: If you change the original structures of Ariba-supplied RFCs, your SAP
integration might not function properly. Similarly, you include the original structures
as well as the .include statements within the extensions.
This chapter explains only how to define extrinsic data within an extension structure.
If you make changes to extension structures, you modify your channel’s data mapping
(TIB/MessageBroker worksheets, for example) to map and transform these fields
appropriately. You also modify the Ariba Buyer metadata XML to include your
changes. For information on these tasks, see the following guides:
• Ariba Buyer TIBCO Configuration Guide
• Ariba Buyer Customization Guide
Note: Use TIB/Designer to add or change SAP schema from RFCs in the
TIB/Repository. For more information, see “Changing SAP Schema” on page 59.
About 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, internal orders have the root ORD. The extension structure has the name
ZXTORD, andthe Ariba Buyer structure is named ZARORD.
Adding Fields to Extension Structures

In most circumstances, each structure and extension structure selects data from one
table only. Consequently, you return additional fields from one table only.
W To add fields to extension structures:

1 Determine the table in SAP that contains the column of data you want to pull.
2 Determine which Ariba Buyer RFC selects data from that particular table.
3 Add the field to the RFC extension structure for the table.
4 Click Activate to activate your changes.

Pulling New Tables Into Ariba Buyer Chapter 4 Configuring Pulls
Extension Structure Example

Assume you want Ariba Buyer to identify the country where an asset originates. The
asset master record, ANLA, contains a column called LAND1, which indicates the country
origin of an asset. In this case, the Ariba Buyer RFC that handles asset pulls from ANLA
is Z_ARIBA_ASSET. For a detailed list of Ariba Buyer SAP objects, see Appendix
A, “Ariba SAP Objects.”
Z_ARIBA_ASSET exports an extension structure called ZXTASSET, which includes the

Ariba Buyer structure ZARASSET. The ZARASSET structure does not contain the LAND1
field by default, so you add it 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. Subsequently, your SAP
system includes a new extrinsic, LAND1, in ZXTASSET, which it pulls from ANLA.
You use the exact field name and data element descriptions for the column from
which you pull data. When the Ariba Buyer RFC runs, it uses the information you
provided to find the column in the table.
Note: Whenever you make changes to a structure, make sure to click Activate.
Pulling New Tables Into Ariba Buyer

In some cases, 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 write your own RFCs and create new schemas for the data you are
pulling. You can also write new RFCs for data that comes from a different schema but
still shares a key with one of the Ariba Buyer RFCs.
To pull data into worksheets, you need to specify the corresponding schema as an
export parameter for your RFC. You might also need to configure your worksheets to
send appropriate variant and partition information as import parameters to the custom
RFC. For more information on this process, see “Defining Adapter Services for New
Custom RFCs” on page 57.
To pull data into Ariba Buyer, you customize your channel’s data mapping, such as
customizing a TIB/MessageBroker worksheet. Often, you import your SAP variant
and partition and define the structure your schema uses.

Chapter 4 Configuring Pulls Pulling New Tables Into Ariba Buyer
W To pull tables not originally defined in Ariba Buyer:

1 Define the SAP schema for the Ariba Buyer custom object in the extension files.
2 Write your custom RFC, importing and exporting any necessary structures.
3 Create the worksheets for the channel you use to change the data into Ariba Buyer
objects.
4 Write your custom Java code, as required.
The rest of this section contains material about filtering and example RFC code useful
for the first step of writing your RFC and importing appropriate structures.
For more information on writing custom RFCs and creating worksheets, see the
following documents:
• 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 channel adapter uses metadata in the XML classes files, called SAP schema, that
describes these parameters. The structure of these XML files resembles the local
interfaces of RFCs. The SAP schema files reside in:
config/variants/variant/partitions/partition/tibco/adapter/sap/classes/sap
Your interfaces should be similar to the interfaces 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

Defining Adapter Services for New Custom RFCs

After you have created the custom RFC in the SAP system, you use TIB/Designer to
create the Adapter Service in the TIB/Repository.
W To view the TIB/Repository using TIB/Designer:

2 Open an existing project.
3 Click the Server-based Project tab.
4 Click the Show Advanced checkbox.
5 Confirm that the Daemon, Network, and Service fields display the correct entries.
If they do not, enter the appropriate corrections.
6 Click the Load Project List button.
7 Select the SAP variant project.
8 Click OK.
9 Ignore any warning messages.
W To create Adapter Services:

2 View the TIB/Repository using the steps outlined in the previous section.
3 Select the following folder:

variant/Legacy Adapters/ SAP Adapter40/SAInboundRFC.partitionName/Adapter
Services
4 Start the SAP Design-Time Adapter using the following command:

runtibco -startsapdpta variant
5 In TIB/Designer, select the following folder:

variant/Legacy Adapters/ SAP Adapter40/SAInboundRFC.partitionName
6 Click the Design-Time Connection tab.
7 Enter the SAP connection values, as appropriate.
9 Confirm that the connection is OK.
10 Click Adapter Services.

Chapter 4 Configuring Pulls Pulling New Tables Into Ariba Buyer
11 Click the Configuration tab, and specify the correct IDoc filter or RFC filter.
12 Specify the custom folder name as SAP.
13 Click Fetch IDocs or Fetch RFC/BAPIs, respectively.
Note: You can also add a resource through using TIB/Designer menus. From the
Resource menu, for example, choose Add Resource > R3 Adapter > Request-Response
Service.
14 Select the RFC/BAPI panel, and make sure the desired RFC is included.
15 From the R3 Adapter palette, select the appropriate service, for example, the
Request-Response Service.
16 Drag the selected service to the Adapter Services folder.
17 In the Request-Response Service panel, click Select RFC/BAPI.

A list of RFC names should appear. If the list does not appear, make sure you
followed steps 11 and 14 correctly. Also, make sure that you specified the correct
parameters in the Request-Response Service panel. The Message Subject field
should not contain any items surrounded by double percentages. For example,
%%Domain%% should not appear in this field.
18 Select the desired RFC, for example, Z_ARIBA_WBSERVER, and click OK.
19 Click the Advanced tab.
20 Change the Message Subject Name to the following format:

SAP.RFCName.SAInboundRFC.partitionName.RFCNameServer
21 Click Apply.
22 Save your changes.
Adding Real-Time Clients

You need to add real-time clients to perform real-time checks like password check
and budget check.
W To create a real-time client:

1 Open TIB/Designer, and navigate to the following:
variant/Legacy Adapters/ SAP Adapter 4.0
2 Use the SAInboundRFC-Realtime.partition folder.

3 Add new real-time clients.
Changing SAP Schema

Using the TIB/Designer to view the TIB/Repository, you can add new fields to the
RFC structures that are provided as part of the default configuration by following
these steps.
W To change SAP schema:

1 Make the structure change in the SAP system as described in “Adding Fields to
Extension Structures” on page 54, and make note of the name of the structure.
2 Start TIB/Designer, and view the TIB/Repository, following the steps described on
page 57.
3 Navigate to the following directory:
Schemas/Classes/ae/TIBCO/SAP/basic/structures
4 Select the structure name you noted in step 1.

The list of fields appears in the upper-right panel.
5 Add the same scalar fields you added in the SAP system, specifying their type.
6 Drag and drop an appropriate generic scalar type from the palette window into the
upper-right panel that displays the list of fields.
Note: You can also change SAP schema using a TIB/Designer menu. From the
Resources menu, choose Add Resource > Adapter Schemas, and select the type you
want.
7 Change the type of the field to Custom Type.
8 Click Apply.
9 The Browse Resources icon appears.
10 Choose the corresponding scalar type from the following folder:

vsap/Schemas/Scalars/ae
For example, if you added a field of type char.4, choose char.4 from the list of
scalar fields.
11 Click Apply.

Chapter 4 Configuring Pulls Pulling Remittance Advice
12 Save your work.

A message appears asking if you want to back up.
13 Click No.
Pulling Remittance Advice

To pull remittance advice from SAP and use the Ariba Supplier Network (Ariba SN)
to transmit the remittance advice directly to the payee, or through a financial
institution, or through a third-party agent, you take the following steps:
1 Enable remittance pull.
2 Configure remittance pull.
These steps are covered in detail in the rest of this section.
Enabling Remittance Pull

To enable remittance pull in SAP 4.6C, you take the following steps:
1 Enable Ariba Settlement from the Ariba Buyer installation program.
2 To import all MessageBroker worksheets to the TIB/Repository, run:

initdb -initchannel
3 Install the SAP transports documented in ReadMe.txt.
Note: If you enabled the Settlement module after the initchannel process, you can
import a specified MessageBroker sheet to the TIB/Repository by running:
runtibco -importsheets variantName -sheets sheetName
For more information on installing the Ariba Settlement module, see the Ariba
Settlement Guide.

Pulling Remittance Advice Chapter 4 Configuring Pulls
Configuring Remittance Pull

To configure SAP 4.6C for remittance pull, you take the following steps:
• Create and update the date timestamp file.
• Map the SAP payment methods to the Ariba Buyer payment methods.
• Increase performance.
• Set up the SAP custom filters.
These steps are described in detail in the sections that follow.
Creating and Updating the Date Timestamp File

Remittance information is pulled incrementally for all Ariba Buyer vendors within a
given time period from the date of the last time the RemittancePull scheduled task ran
to the current date.
Before the initial run of the RemittancePull scheduled task, you create the date
timestamp file in the installation directory with the starting date and time of the
payments that need to be pulled from SAP.
The RemittancePull scheduled task assigns a filename derived from the eventsource
parameter, which is defined in the MessageConfiguration.table.
The eventsource parameter has the following format:
partitionRemittancePullEvent_SAP
The date and timestamp filename is a concatenation of the three parameters in the
eventsource. For example, if your partition name is SAP46c, the name of the file that
exists in your installation area would be:
SAP46cRemittanceSAP
You format the contents of the file as follows:

yyyymmddhhmmss
If the date timestamp file is not found, RemittancePull pulls payments created on the
current date. Subsequently, RemittancePull updates the date timestamp with the
current date after every run.

Chapter 4 Configuring Pulls Pulling Remittance Advice
Mapping Payment Methods

In addition to the payment methods provided in the Ariba Settlement module (check,
wire, ACH, and so forth), you can specify codes to represent the other payment
methods in SAP. To do this, you provide an SAP-Ariba Buyer payment method
mapping in your MessageBroker sheet to determine the corresponding Ariba Buyer
payment method for the payments pulled from SAP.
The following SAP to Ariba Buyer payment method mapping information is available
in the default configuration in the MessageBroker sheet:
SAP Ariba Buyer

C check
D _ACH
T other
If you have a payment method that is not mapped in the default configuration, you
must change the mapping in the MessageBroker sheet.
Increasing Performance
Remittance pull works best for SAP with fewer than 500 payments or fewer than 3000
invoice line items per run. To tune the performance of this feature:
• Increase the Java memory size of the MessageBroker engine from 128 MB to 1024
MB.
• Increase the Java memory heap size of the MessageBroker to avoid out-of-memory
errors.
Setting Up SAP Custom Filters

For additional filters, for example, pull payments, custom filter parameter
ZARIBA_REMITTANCE_BKPF is available for the SAP BKPF payment header table. For
additional information about how to use this parameter, see “About Static Filtering”
on page 63.

Filtering Chapter 4 Configuring Pulls
Filtering
Your SAP development classes for Ariba Buyer offer three ways to filter, or restrict
the data included in a data pull. These filtering methods are described in the following
sections:
• “About Static Filtering” on page 63
• “About ABAP Filtering” on page 70
• “Understanding Post-Hook Filtering” on page 72
About Static Filtering

Static filtering allows you to construct conditional searches of your SAP tables
according to the values of specified fields. The table ZARIBTVARV allows you to
construct queries to limit the data you pull from SAP into Ariba Buyer. Defining
queries within ZARIBTVARV is referred to as static filtering because the data exists in a
structured form within ZARIBTVARV, and data isn’t selected 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 search for any entries that
match their names. If they find a match, they restrict the query according to the
instructions in the ZARIBTVARV entry. The RFCs used to pull master data from SAP into
Ariba Buyer can use the table ZARIBTVARV to filter the data before it is pulled into
Ariba Buyer. Each RFC has a specific table whose fields can be used in ZARIBTVARV.
For more information, see “ZARIBTVARV RFC Reference” on page 158.
Static filtering is quick and simple, but it does not handle inner join queries against
more than one table. If you need to restrict data pulls that pull from more than one
table, use the filtering techniques explained in “About ABAP Filtering” on page 70.
Editing ZARIBTVARV
To restrict statically the data that an Ariba Buyer RFC pulls, make a corresponding
entry in ZARIBTVARV. Enter a new row in the ZARIBTVARV table with the RFC name, the
field you want to use, and information about what you’re trying to find.
Note: Ariba suggests you run transaction SM30 to examine ZARIBTVARV. Your SAP user
ID must have authorization S_TABU_DIS to run transaction SM30. ZARIBTVARV resides as
a table within the dictionary objects for the ZAR6 class.

Chapter 4 Configuring Pulls Filtering
You also use the ZARIBTVARV table to configure variable settings in certain RFCs. In
particular, you 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. To learn more about parameter use, see Chapter
6, “Parameter Configuration.” For instructions on editing the ZARIBTVARV parameters,
see “About ZARIBTVARV” on page 87.
ZARIBTVARV Field Reference

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

Ariba Variant Identifies the unique name for the shape of data Necessary for both filtering
in your SAP system as it appears within Ariba and parameter use
Buyer. An Ariba Buyer variant is different from a (selection types S and P).
variant in SAP.
Ariba Partition Describes the unique instance name of a Necessary for both filtering
specified variant shape as you represent it to and parameter use
Ariba Buyer. (selection types S and P).
Variable Name Provides an index to the table. Ariba Buyer uses Necessary for both filtering
the Name field either to pass the name of the and parameter use
calling function or to pass the name of the (selection types S and P).
parameter it seeks. See Chapter 6, “Parameter
Configuration,” to find out more about
ZARIBTVARV and parameters.
Field Name Refers to the column name you use to filter data. Necessary for filtering only
Leave this field blank to use ZARIBTVARV for (selection type S).
parameters and selection type P.
Selection Determines whether to use ZARIBTVARV to filter Necessary for both filtering
Category data or to configure a parameter for an RFC. and parameter use
Enter a value of S to perform filtering and P to (selection types S and P).
configure parameters.
See Chapter 6, “Parameter Configuration,” to

find out more about ZARIBTVARV and parameters.

ZARIBTVARV Field Reference (Continued)

Number Determines the sequential order of selection Optional and used for
statements. The order determines how to filtering (selection type S).
construct the entire selection.
See “Selection Condition Options” on page 66.

Incl/Excl Determines whether to include or exclude the Required for filtering use
selection condition. Set this value to I for (selection type S).
inclusion if the condition is positive or to E for
exclusion if the condition is negative.
See “Selection Condition Options” on page 66.

Option Allows you to create conditions based on Required for filtering use
equality, value ranges, and patterns. Set it to the (selection type S).
following conditions:
BT — The “BeTween” option specifies a selection

within the range of values in the LOW and HIGH
fields. For example, names between “Reid” and
“Sligh”.
CP — The “Contains Pattern” option allows you

to return data with a given pattern, for instance,
names that begin with “Dan”.
EQ — The “EQual” option determines

equivalency, such as names = “Angus”.
GE — The “Greater than or Equal to” option

determines if the FIELDNAME is greater than or
equal to a value, such as names >= “Bruce”.

ZARIBTVARV Field Reference (Continued)

Selection Value Sets the low value for filtering and settings for Optional for parameter
(LOW) parameters. To enter particularly long values— configuration and required
like strings—overlap values to the HIGH field. for most filtering
statements.
Selection Value Sets the high value and works with LOW values Optional for most
(HIGH) and BT option fields. parameter configuration
and filtering, except BT
option fields.
Selection Condition Options

The selection options in the ZARIBTVARV table reflect the internal structure of select
options in SAP report tables. The ZARIBTVARV structure itself resembles the SAP TVARV
structure, and the fields function similarly.
The ZARIBTVARV 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 specified 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 in specific countries.

W To create the filter:

1 See Z_ARIBA_COMPANY to determine where this information originates.
In this example, the information originates from table T001. Table T001 contains an
entry called LAND1, which designates countries. In this example, the only countries
you want to pull company information from are Australia and Japan, which LAND1
designates with the strings AU and JP.
You 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
2 Build your select statement.
The statement depends on the data set you want to capture. In this example, 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 might look similar to the entries in the following table (the VARIANT and
PARTITION fields are not included):
VARIABLE FIELD SELECTION NUMBER INCL/EXCL OPTION SELECTION SELECTION

NAME NAME CATEGORY VALUE VALUE (HIGH)
(LOW)
Z_ARIBA LAND1 S 0000 I EQ AU
_COMPANY
Z_ARIBA LAND1 S 0001 I EQ JP
_COMPANY
The fields in the VARIABLE NAME column indicate this filter is for the data pulled by the
RFC Z_ARIBA_COMPANY.
The fields in the FIELD NAME column indicate you’re pulling data from the LAND1
column.
The fields in the SELECTION CATEGORY column specify to the calling function that the
row is for filtering, or selecting, data. In this case, the S specifies filtering.

The fields in the NUMBER column include more than one row of the same filtering table
in the condition. It starts at zero, or 0000. The order is not significant.
The fields in the INCL/EXCL column indicate 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. For an example of exclusion, see “Ranges and Exclusion” on
page 68.
The fields in the OPTION column determine that you’re selecting for a condition of
equality (EQ). It is also possible to 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
“Thompson.”
• 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 69.
• 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 could resemble the rows in the following table.

NAME NAME TYPE VALUE VALUE
(LOW) (HIGH)
Z_ARIBA_ LAND1 S 0000 I BT AU GB
COMPANY
Z_ARIBA_ LAND1 S 0001 E EQ CA
COMPANY

The selection first includes the range between AU and GB and then excludes CA.
Patterns and Comparisons

You also select data according to its pattern and by comparing values.
Suppose you want to pull only vendors that certain users have 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 LAFI. LAFI
contains the column ERNAM for the user name. The logic of the selection could
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. Using AND ERNAM < “ND” is more concise.
The values in ZARIBTVARV might resemble the following:

NAME NAME TYPE VALUE VALUE
(LOW) (HIGH)
Z_ARIBA_ ERNAM S 0000 I CP M
VENDOR_
ONLY
Z_ARIBA_ ERNAM S 0001 I CP N
VENDOR_
ONLY
Z_ARIBA_ ERNAM S 0002 E GE ND
VENDOR_
ONLY

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”).
About ABAP Filtering

ABAP filtering is a method 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 Ariba Customer Development classes such as ZARC where you make the
modifications.
Each RFC passes its name to Z_ARIBA_PREFILTER_EXT. You use conditional tests to
determine how and if Z_ARIBA_PREFILTER_EXT restricts the data set of the table based
on the calling RFC name. This process is called ABAP filtering because you write
ABAP/4 code to get the results you want.
This section explains how ABAP filtering:

• Performs inner joins
• Provides an RFC interface
• Works in a sample configuration
Joins and ABAP Filters

You use ABAP filters 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

It is possible for you to create dynamic WHERE statements for selections in the WHERE
structure. The example code in Z_ARIBA_PREFILTER_EXT demonstrates the use of
dynamic WHERE statements. The WHERE statements in the code can come from another
table.
Following 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.

Understanding Post-Hook Filtering

Both static filters and ABAP filters cut down on data before an Ariba Buyer RFC
begins to process anything. You filter data after the Ariba Buyer RFCs finish through
post-hook filtering. SAP commonly provides this feature through “user exits” or
“customer exits.”
This section introduces:

• Exit RFCs
• Post-hook filtering suggestions
Exit RFCs
Only SAP can use the SAP infrastructure of user exits, 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 compose most of the customer
development classes such as ZARC that allow you to make modifications.
An 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 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 restrict it further. ABAP and static filters don’t work because they only
provide you access to the first table, not the second. You need to restrict the data after
the Ariba Buyer RFCs have finished with it. Post-hook filters let you restrict the data.
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, examine the way a typical RFC functions,
as shown in the following diagram:
The content of the company code pull RFC, Z_ARIBA_COMPANY, provides an example of
the mechanisms and techniques this chapter presents:

Chapter 4 Configuring Pulls Example RFC
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
OTHERS = 1.
ENDFUNCTION.

Example RFC Chapter 4 Configuring Pulls
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
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, for you to make changes to the data:
CALL FUNCTION 'Z_ARIBA_COMPANY_EXT'

EXPORTING
VARIANT = VARIANT
TABLES
COMPANY_INFO = COMPANY_INFO
EXCEPTIONS
OTHERS = 1.

Chapter 4 Configuring Pulls Example RFC

Chapter 5
Configuring Pushes
This chapter explains how SAP administrators and developers and Ariba Buyer
implementation personnel configure Ariba Buyer development classes to change the
data Ariba Buyer pushes in purchase orders and good receipts. It includes the
following sections:
• “Push Extension Structures” on page 77
• “Understanding Screen Field Mappings” on page 78
• “Mapping Fields for Orders or Receipts” on page 80
• “Changing and Removing Fields” on page 84
• “Filtering and Customer Exit Functions” on page 84
• “Modifying Customer Development Classes” on page 85
• “Formatting Dates” on page 85
• “Unsupported Push Features” on page 86
The terms and explanations in this chapter assume a working knowledge of the
material in Chapter 4, “Configuring Pulls.”
Push Extension Structures

Ariba Buyer push RFCs provide extension structures that work the same as the
extension structures for pulls. The extension structures allow you to add fields or
columns to the data Ariba Buyer sends to SAP.
For example, the purchase order push RFC, Z_ARIBA_PO_PUSH, provides 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)

Chapter 5 Configuring Pushes Understanding Screen Field Mappings
For example, goods receipt push RFC, Z_ARIBA_GR_PUSH, provides 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)
Make sure 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, see “Pulling Additional Fields Into Ariba Buyer” on page 52.
Understanding Screen Field Mappings

This section discusses screen field mappings that are applicable for pushes using the
CALL transaction method. If you add new fields to push extension structures, you also
define and map these fields in the 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.
This section describes:

• What field mappings do
• Data push mapping tables
• Sources of data for push mapping tables
What Field Mappings Do

The Ariba Buyer development classes allow you to modify the following kinds of
SAP screen field information. You change the way to set or remove values for fields
as screens by telling theAriba Buyer RFCs:
• In which fields in a screen to insert or set values.
• In which fields in a screen not to insert or set values. It is possible to 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.

Understanding Screen Field Mappings Chapter 5 Configuring Pushes
• 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.
About Data Push Mapping Tables

Ariba Buyer provides custom tables that offer specific mappings from the data that
Ariba Buyer includes in purchase orders and good receipts to individual fields in SAP
entry screens. The following two kinds of tables from the ZAR6 and ZARC development
classes are provided:
• ZAR6 tables—part of the Ariba Buyer RFCs you never modify
• ZARC extension table—available for you to edit and change
One of each kind of table is provided for purchase orders and goods receipts:
• ZARPOFMAP—Ariba Buyer RFC Purchase Order Mapping
ZARPOFMAP describes the SAP purchase order fields that Ariba Buyer RFCs have set
as part of a default configuration, including a mapping between the Ariba Buyer
RFC structures and the purchase order destination fields. Do not modify this
table.
• ZARPOFMAPX—Purchase Order Mapping Extension
ZARPOFMAPX is the extension table you use to instruct Ariba Buyer RFCs to add,
remove, or modify the purchase order fields that the Ariba Buyer RFCs have set.
The table maps from Ariba Buyer RFC purchase order extension tables to SAP
purchase order screen fields.
• ZARGRFMAP—Ariba Buyer RFC Goods Receipt Mapping
ZARGRFMAP describes the SAP goods receipts fields that Ariba Buyer RFCs have set
as part of a default configuration, including a mapping between the Ariba Buyer
RFC structures and the goods receipt destination fields. Do not modify this table.
• ZARGRFMAPX—Goods Receipt Mapping Extension
ZARGRFMAPX is the extension table you use to instruct Ariba Buyer RFCs to add,
remove, or modify the goods receipt fields Ariba Buyer RFCs have set. The table
maps from Ariba Buyer goods receipt extension tables to SAP goods receipt screen
fields.

Chapter 5 Configuring Pushes Mapping Fields for Orders or Receipts
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 understand
how to use the extension table for good receipts. The text in this chapter combines the
explanation of these tables.
Note: You customize only the extension tables ZARPOFMAPX 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 Mapping Tables

You acquire the value you set or change for an extension table from the following
locations:
• The Ariba Buyer object model or TIB/MessageBroker worksheet
• An external data source read into an Ariba Buyer PO or goods receipt
TIB/MessageBroker worksheet
• Other tables within your SAP system
Mapping Fields for Orders or Receipts

This section explains how to map fields to the PO Creation and GR Creation
transaction screens 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 the fields
to screens.
The following documents explain how to push new fields to your Ariba Buyer RFCs:
The process of mapping fields for purchase order or goods receipt pushes consists of
three steps:
1 Find the screen field to map (also called the destination field).
2 Find the source field.
3 Edit the corresponding extension table.

Mapping Fields for Orders or Receipts Chapter 5 Configuring Pushes
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 user interface session, and to
keep all three SAP user interface sessions open, for cross reference, until you have
finished 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
want to map in either the purchase order or goods receipt screens. Use the following
steps to locate the table information you need.
W To locate the table destinations:

1 View a purchase order or goods receipt.
2 To find the field you need, either display an existing document or create a new one.
To do so, use one of the following transaction codes:
• ME21—createsnew purchase orders
• ME23—displays existing purchase orders
• MB01—allows you to create new goods receipts
• MB03—displays existing goods receipts
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.
3 Find the field.
4 If you chose to create a new purchase order or goods receipt, navigate through the
SAP screens until you find the field you want to map, entering information, as
necessary.
5 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 screens until
you find the field you want to map.
6 Find the field information.

Chapter 5 Configuring Pushes Mapping Fields for Orders or Receipts
7 Select the field you want to map, and press the F1 key. In the help screen, click
Technical Info.
The screen that appears provides most of the information you need to enter in the
extension table about the destination field, including:
• Program name
• Screen number
• Table name
• Field name
8 Write down this information, or keep your SAP user interface open and use another
session 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
Mapping from Ariba Buyer RFC Import Tables

You might 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. The source field can be the
import or extension table field from either of these 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.

Mapping Fields for Orders or Receipts Chapter 5 Configuring Pushes
W To edit extension tables:

1 Run transaction SE11.
2 Access the initial screen of the ABAP Dictionary, and enter one of the following
data push extension tables within the Database table field:
• ZARPOFMAPX—to map fields for Ariba Buyer purchase orders
• ZARGRFMAPX—to map fields for Ariba Buyer goods receipts
3 Click Display.
4 In the Display Table window, choose Utilities > Table Contents > Create Entries.
5 Press F5, or click New Entries.
6 Enter the following information in the New Entries window:

• Ariba Variant—the name of the Ariba Buyer SAP variant where the purchase
order or goods receipt originates.
• Ariba Partition—the name of the Ariba Buyer SAP partition where the purchase
order or goods receipt originates.
• Program name—the program name of the destination screen field.
• 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.
• Short Description—a short description of the mapping for documentation
purposes.
• Indicator: delete entry—the field for removing field mappings from your default
Ariba Buyer RFC configuration. Leave this field blank if you are creating a new
field mapping.
7 Choose Table View > Change > Display, and then choose Table > Activate to activate
your changes.

Chapter 5 Configuring Pushes Changing and Removing Fields
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.
To remove a mapping of a field that Ariba Buyer RFCs already maps, enter a mapping
for the field you want 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 use these exit functions to manipulate data
at different stages:
• From when the RFCs first import the data to the final batch data control (BDC)
posting for PO push and GR push, or
• To the completion of the RFC
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.
For example, the purchase order push and goods receipt push RFCs offer several
customer exit functions, which execute in the following order:
• Exits before any data processing begins:
Z_ARIBA_PO_PUSH_EXT
Z_ARIBA_GR_PUSH_EXT
• Exits before the batch data control 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

Modifying Customer Development Classes Chapter 5 Configuring Pushes
Use these exit functions to manipulate purchase order and goods receipt pushes in
ways that field mappings do not offer.
Modifying Customer Development Classes

Ariba Buyer provides customer development classes, such as ZARC and ZATC, to extend
or customize the features of the Ariba development classes ZAR6 and ZATI.
Before making any modifications to these Ariba-delivered development classes, make

sure they are transportable. To be transportable, the development classes must be
associated with an appropriate transport layer. This association should be performed
by your SAP BASIS personnel.
Formatting Dates
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 Ariba Buyer pushes to your ERP system or
other data destination are also accurate.
Ariba Buyer imports, or pulls, all dates from external ERP systems and data sources
as strings. Ariba Buyer depends upon the java.text.DateFormat class within the Sun
JDK (Java Development Kit) 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.
The custom TIBCO function stringtodate is used in the worksheets to convert dates
from string format to Java date format.

Chapter 5 Configuring Pushes Unsupported Push Features
Unsupported Push Features

The field mappings for Ariba Buyer push RFCs do not offer the following features:
• BAPIs
• Additional tables
• Additional screens
The following sections explain these limitations and offer 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, do so within the appropriate
TIB/MessageBroker worksheets, not within the mapping tables.
Additional Tables
You 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, 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 an IDES (International Demo Education System) SAP instance. If you
changed the order or content of the purchase order or goods receipts screens on your
SAP system, you might be able to 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 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 change the way Ariba Buyer RFCs function by modifying parameters in the
RFCs. This chapter explains how to change Ariba Buyer RFC parameters and
describes the available parameters. The material in this chapter is appropriate for SAP
developers or administrators.

• “About ZARIBTVARV” on page 87
• “Default Parameters” on page 88
• “Parameter Descriptions” on page 90
About ZARIBTVARV
You configure all Ariba Buyer RFC parameters through the ZARIBTVARV table. By
editing the parameter configurations in ZARIBTVARV, you:
• 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, see the section on ZARIBTVARV in

Chapter 4, “Configuring Pulls.”
This chapter explains how to use ZARIBTVARV to configure Ariba Buyer RFCs. For a
list of the RFCs affected by parameters in ZARIBTVARV, see “ZARIBTVARV RFC
Reference” on page 158.
ZARIBTVARV contains a special field, called TYPE, which determines whether an entry is
for static filtering or parameter configuration. To change parameters, you enter a “P”
in the TYPE field. (If you set the field to S, you use ZARIBTVARV for static filtering; see
“About Static Filtering” on page 63.)

Chapter 6 Parameter Configuration Default Parameters
In your default configuration, ZARIBTVARV does not contain any parameters. Ariba
Buyer RFCs that call ZARIBTVARV already contain certain default values that they use.
Enter a value in ZARIBTVARV only if you want to change the default values.
W To edit ZARIBTVARV parameters:

1 Run transaction SM30.
2 Open the Maintain Table Views initial screen, enter ZARIBTVARV in the Table/View
field, and click Maintain.
3 Choose Edit > New Entries, or click the New Entries button.
4 Enter appropriate information in the screen that appears. For details, see the table
“ZARIBTVARV Parameters” on page 88.
5 To save your changes, choose Table View > Save or (press F11).
6 If a transport window appears prompting you to enter the change request, click
Create Request to create a new request, or choose an existing request number in the
Request field, and then click the check mark to create the transport request.
Default Parameters
The following table lists possible ZARIBTVARV parameters, default values, and the
RFCs that reference them. The remaining sections in this chapter explain what these
parameters do and provide other possible values.
ZARIBTVARV Parameters
Parameter Name Default Calling Function

BALANCE_SHEET_ACCOUNTS disallow Z_ARIBA_GENERAL_LEDGER
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 from Z_ARIBA_LAST_CHANGE_DATE

change document header
table
GENERAL_LEDGER_DAYS_PAST 7 Z_ARIBA_GENERAL_LEDGER
GENERAL_LEDGER_MESSAGE_TYPE ZATGLM Z_ARIBA_GENERAL_LEDGER

Default Parameters Chapter 6 Parameter Configuration
ZARIBTVARV Parameters (Continued)
Parameter Name Default Calling Function

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_BAPI_PO_CRT_ALLOW_DUPS blank Z_ARIBA_BAPI_PUSH
Z_ARIBA_CPO_FNAME null Z_ARIBA_BAPI_PO_CHANGE

Z_ARIBA_BAPI_PO_CANCEL
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_DEBUG_CPO null Z_ARIBA_BAPI_PO_CHANGE

Z_ARIBA_BAPI_PO_CANCEL
Z_ARIBA_GR_PUSH_ALLOW_DUPS blank Z_ARIBA_GR_PUSH
Z_ARIBA_GR_PUSH_DISPLAY_MODE N Z_ARIBA_GR_PUSH
Z_ARIBA_INTERNAL_ORDER_AUART blank Z_ARIBA_INTERNAL_ORDER
Z_ARIBA_ LANGUAGE E Z_ARIBA_ACCOUNT_CATEGORY

Z_ARIBA_MATERIAL_GROUP
Z_ARIBA_PO_DETAILS
Z_ARIBA_COST_CENTER
Z_ARIBA_GENERAL_LEDGER
Z_ARIBA_MINORITY_VENDOR
Z_ARIBA_CURRENCY
Z_ARIBA_TAX_CODE
Z_ARIBA_UOM
Z_ARIBA_PO_PUSH_DISPLAY_MODE N Z_ARIBA_PO_PUSH
Z_ARIBA_RELEASE_AUTHORITY_CNAM FRG_GNETW Z_ARIBA_RELEASE_AUTHORITY
Z_ARIBA_REMITTANCE_BKPF ‘ ‘ Z_ARIBA_REMITTANCEPULL
Z_ARIBA_VENDOR_ONLY_COUNTPORGS 1 Z_ARIBA_VENDOR_ONLY
Z_ARIBA_PO_PUSH_ALLOW_DUPS Checks for duplicate POs Z_ARIBA_PO_PUSH

Chapter 6 Parameter Configuration Parameter Descriptions
Parameter Descriptions
This section groups the following categories of parameters together and explains how
to use them:
• Days past
• Minority indicators
• 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
• Language for texts
Days Past Parameter

The DAYS_PAST parameter allows you to configure how far back, in days, the Ariba
Buyer RFCs look for General Ledger and Cost Center data created or modified in the
specified time period.
Parameter Description Default Value

Z_ARIBA_CURR_CONV_DAYS_PAST Keeps track of currency 60
conversion rates
Make sure that the days past parameters for Ariba Buyer RFCs are values less than or
equal to the scheduled events in the SAP integration table.

Parameter Descriptions Chapter 6 Parameter Configuration
Minority Vendor Head Offices

The Z_ARIBA_MINORITY_VENDOR RFC allows you to 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 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, see the steps on page 113.
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 use these parameters to watch what happens 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
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 = A
Z_ARIBA_GR_PUSH_DISPLAY_MODE = A
You can also configure the TIB/Adapter for R/3 to call the RFC within the SAP user
interface from TIB/Message Broker worksheets that use RPC client plugins.
W To perform ABAP debugging using the SAP user interface:

1 Launch the SAP user interface.
2 Set the ABAP_DEBUG parameter value to 1.
W To perform ABAP debugging using TIB/Designer:

1 Stop the TIB/Adapter for R/3.
1 Launch the TIB/Designer.
2 Choose R3Connections > Clients.
3 Select the client node for which you want to enable ABAP debugging.
4 In the right hand panel, select the Advanced tab.
5 Set the parameter ABAP_DEBUG value to 1.
6 Save your work.
7 Restart the TIB/Adapter.
8 Make sure to use the dialog user login for the adapter so you can launch the SAP
user interface in dialog mode.
Internal Order Types

Internal orders contain a field called AUART, which designates their order type. The
value of AUART determines whether SAP can use the internal order to create a purchase
order. The Ariba Buyer RFCs do not create purchase orders using 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 RFCs can create purchase
orders from any internal order in which the AUART field of the order master data (AUFK):
• 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 carbon copies, also called complimentary copies, of
orders to SAP. SAP uses these copies for accounting purposes. However, Ariba Buyer
can also push orders to SAP so SAP can send them to the vendors. Ariba Buyer RFCs
use order document types to keep track of which orders are for SAP to send and
which are carbon 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 might want to configure a different
document type for Ariba Buyer orders or use a different type for SAP orders. To do
so, set 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 Ariba

Supplier 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.
If you are using BAPI to push purchase orders, you set the parameter
BAPI_PO_CREATE_DOC_TYPE instead of PO_PUSH_ERPCC_DOC_TYPE or
PO_PUSH_DIRECTCC_DOC_TYPE, and you set BAPI_PO_CREATE_ERP_DOC_TYPE instead of
PO_PUSH_ERP_DOC_TYPE.
To learn more about order types, see the Ariba Buyer Procurement Guide.

Vendor Pull Filtering

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

vendor pulls. Valid settings are 1 or 0. The default setting is 1.
• If the parameter is set to 1, the RFC selects only vendors assigned to at least one
purchasing organization.
• If the parameter is set to 0, the RFC pulls all vendors without regard to any
assigned purchasing organizations.
The default setting of 1 pulls a smaller set of data by executing two select statements
within the RFC code. The 0 setting pulls more data, which the RFC refines further
through a single selection query.
To perform an incremental pull of vendor information, you use an ALE/IDOC pull.

The ALE/IDOC pulls only new and changed vendors. For more information on using
ALE/IDOC, see “Defining Logical Systems for Partitions” on page 117.
Using General Ledger Balance Sheet Accounts

You use general ledger balance sheet accounts 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 not to allow this pull, and returns a hard
error message when a user attempts to do so.
To enable Z_ARIBA_GENERAL_LEDGER to pull and use balance sheet accounts, you enter
the value allow in the BALANCE_SHEET_ACCOUNTS parameter. To instruct the RFC not to
use balance sheet accounts, even if balance sheet accounts are permitted on your
system, you enter the value disallow instead.
To perform an incremental pull of general ledger accounts, you use an ALE/IDOC

pull. The ALE/IDOC pulls only new and changed general ledger accounts. For more
information on using ALE/IDOC, see “Defining Logical Systems for Partitions” on
page 117.

Real-Time ALE/IDOC Partition Loading

To configure the optional real-time loading feature, you enter certain parameters in
ZARIBTVARV. For information on using these parameters, see “Ariba Buyer Parameter
Real-Time Configuration” on page 127.
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 if it has already created a PO for the given requisition and the line
number. If so, Ariba Buyer does not create a new PO number but returns the existing
PO number.
If the Z_ARIBA_PO_PUSH_ALLOW_DUPS parameter is set, the RFC does not check for
duplicates. If the Z_ARIBA_BAPI_PO_CRT_ALLOW_DUPS parameter is set for BAPI PO push,
the BAPI code does not check for duplicates.
Note: Do not change this parameter setting unless you are testing with different Ariba
Buyer instances on the same SAP computer.
Duplicate GR Handling
By default, Ariba Buyer does not create duplicate goods receipts (GRs). In the RFC,
Ariba Buyer keeps track of the Ariba Buyer receipt IDs. When a GR is pushed, Ariba
Buyer checks to see whether it has already created a GR for the given receipt. If so,
Ariba Buyer does not create a new GR but returns the existing GR number.
If the Z_ARIBA_GR_PUSH_ALLOW_DUPS parameter is set, the RFC does not check for
duplicates.
Change PO Parameter
You debug the change/cancel purchase order feature by setting the parameter
Z_ARIBA_DEBUG_CPO to X and setting Z_ARIBA_CPO_FNAME to the name of a log file where
the change/cancel order information is logged.

Language for Texts Parameter

Ariba Buyer uses E (English) as the default language. To get language-dependent
descriptions in other languages (if you are running other language instances), you can
set the Z_ARIBA_ LANGUAGE parameter. Subsequently, the descriptions are displayed in
the language set in the parameter. If English language descriptions are not maintained
in SAP, set the value to the language in which descriptions need to be shown in Ariba.

Chapter 7
Account Assignment Categories
This chapter explains how Ariba Buyer uses SAP account assignment categories. It
includes the following sections:
• “About Account Assignment Categories” on page 97
• “Displaying Fields and Requiring User Input” on page 99
The material in this chapter is appropriate for SAP administrators and developers and
Ariba Buyer implementation personnel.
About Account Assignment Categories

SAP uses account assignment categories to specify how to assign a line-item
expenditure to an account. Examples of account assignment categories are 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 were to purchase an elevator for your company’s building through
Ariba Buyer, you could apply the cost of the elevator through an asset account
category. You might do so because buildings are usually considered assets. Quite
often, special tax and accounting considerations exist for expenses related to the
improvement or maintenance of assets.
Such considerations might 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
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.

Chapter 7 Account Assignment Categories About Account Assignment Categories
For example, if a user chooses an asset account assignment category, SAP doesn’t
require the entry of any information related to cost centers. When possible, SAP
includes default values for required information based upon current data.
It is possible to 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 create your own categories.
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.
• Whether to require the user to choose or provide certain types of account
information in the user interface.
The default Ariba Buyer SAP configuration pulls the categories listed in the following
table.
Symbol Assignment Category Required Entries

A Asset Asset Number
F Order Internal Order, GL Account
K Cost Center Cost Center, GL Account
P Project WBS Element, GL Account
The table also identifies the required entries for each assignment category. For more
information about required entries, see “Configuring SAP Accounting Fields” on
page 99.
Note: In the default configuration, the CostCenter field is not displayed on the line-item
details screen when the user chooses account assignment category “F” (Order).

Displaying Fields and Requiring User Input Chapter 7 Account Assignment Categories
Displaying Fields and Requiring User Input

Ariba Buyer pulls account category information and uses it in similar ways to those
used by 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.
Configuring SAP Accounting Fields

SAP has a set of information fields it can display or require for any account
assignment category. You control the way in which the SAP user interface displays a
field and how a user can modify it.
W To configure the SAP accounting fields:

1 To control how SAP displays fields and how users modify them, choose one of the
following four options:
• Required Entry—SAP displays the accounting field and requires user input.
• Optional Entry—SAP displays the accounting field, and a user can change it, but
SAP does not require the user to make any changes.
• Display—SAP displays the accounting field, but the user cannot change it.
• Hidden—SAP does not display the accounting field.
2 To maintain these properties for each account assignment category, choose Go to >
Details in transaction OME9 in the SAP user interface.
For example, the default asset account assignment category settings within an
International Demonstration and Education System (IDES) 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
• Goods recipient/Ship-to party
• Unloading point

Chapter 7 Account Assignment Categories Displaying Fields and Requiring User Input
• Special region
• Display the following for informational purposes, but do not allow the user to
change:
• General ledger account
• Project
• CO/PP order
• Do not display the remaining fields.
Ariba Buyer Accounting Types

Ariba Buyer defines a generic accounting entity, which is a piece of accounting
information. Examples of accounting entities include Project, Cost Center, Account,
and SubAccount.
In a typical configuration, each partition defines its own set of accounting entities.
The accounting fields are not extrinsic—they are just specific instances of the generic
accounting entity.
The default Ariba Buyer configuration for SAP defines the following accounting
entities:
• asset—Asset
• cost center—Cost Center
• general ledger—G/L Account
• internal order—RK/PPC order
• WBS element—Project
Ariba Buyer pulls appropriate data from your SAP system and uses that data to
populate the choosers and accounting information in Ariba Buyer. Ariba Buyer pulls
and uses SAP account assignment category information to determine what users need
to enter for a line item.
When setting up your Ariba Buyer configuration, you define the accounting entities
you plan to use. You also set up your configuration to default accounting information
for catalog items from commodity codes. For information on how to configure
accounting information in Ariba Buyer, see the Ariba Buyer Data Load Guide.

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 these strings to store the
settings previously discussed in the Change View “Account Assignment Categories”:
Details screen, in transaction OME9.
One field status group string exists 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 some settings differently from
SAP within the user interface.
Character SAP User Interface Ariba Buyer

‘+’ (plus sign) Required entry Displays the field and requires user
input.
‘.’ (period) Optional entry Displays the field, and the user can
decide to whether to change it.
‘*’ (asterisk) Display Does not display this field because it
does not require user input.
‘-’ (minus sign) Suppressed 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 pulls all the characters in the
string, but the default configuration uses only those that apply to the five account
types. The character positions relevant to a default configuration for an SAP partition
are as follows:
Account Type Position

Cost Center 10
Internal Order 11
WBS Element 12
Asset 24
General Ledger 51
For example, the positions for an asset category from an IDES system resemble those
in the following diagram:
Ariba Buyer interprets this field status group string in the following way:
• The Cost Center character is a minus sign, 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 does not display them because it does not require the user to
enter a value.
• The Asset character is a plus sign. 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 want 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 in the status string, position 41.
Your SAP partitions create objects with unique names. The file
ariba/variants/variant/partitions/partition/data/FieldStatusToAccountingField
NameMap.csv contains mappings of field positions to the account type. Make sure to
check this file for the new account type you added.
If you implement your own SAP accounting objects to pull other accounting
categories, 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.
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

It is possible to view the field status group strings that the Ariba Buyer RFC pulls for
account assignment categories on your SAP instance.
W To view Ariba Buyer field status group strings:

1 Run transaction SE37 to access the Function Builder Library: Initial Screen.
2 Type “Z_ARIBA_ACCOUNT_CATEGORY” in the Function module field, and click Sngl.test

or choose Function mode > Test > Single test.
The Test Function Module Initial Screen appears.
3 In the Value column, enter your Ariba Buyer variant name and partition, and then
click the green check mark button to execute.
For example, enter “vsap” and “sappart1”.

Pulling New Accounting Objects From SAP

You might want to configure account assignment pulls to provide display information
for a new accounting object you have created in Ariba Buyer.
W To pull a new assignment category:

1 Within SAP, set up a parameter to an entry in ZARIBTVARV for the account
assignment category RFC, Z_ARIBA_ACCOUNT_CATEGORY.
In the default configuration, Ariba Buyer uses the showField method to validate
custom account categories with their field status strings.
2 The default behavior of displaying these fields is based on the visibility conditions
in the code that follows this task. If you want other behavior, you could add a
cluster root object in the metadata XML visibility condition calls.
3 For ideas about how to validate custom account assignment categories with their
field status strings, examine the code that follows this task. For example, you could
use the showField, within a metadata XML user interface description.
The comments provide a 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
Group. We pull this field status group back from SAP when we
pull AACs (Account Assignment Categories. The field status group
is a string of dots,
slashes, plusses, and stars. Each of these means a different thing.
'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 Unique_Name = (String)aac.getFieldValue("UniqueName");
String fstag = (String)aac.getFieldValue("FieldSelectionString1");
char code = fstag.charAt(positionForField(fieldName));
/**For an optional field, if the following combinations of Account

Category (InternalOrder) and Accounting Field (CostCenter) are
encountered, then we will suppress the display of the CostCenter field.*/
if ('.' == code) {
if (Unique_Name.equals("F") ) {
if ( fieldName.equals("CostCenter") ) {
return false;
}
}
// 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;
}
}


Chapter 8
Release Authorizations Pulls
Ariba Buyer provides limited support for certain types of SAP release authorizations
for documents. The RFCs in the ZAF7 development class provide 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, including the
following:
• 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 supports only 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 with a given range of monetary values per release code,
and 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 109.

• “Release Authorities” on page 108
• “ZAF7 Ariba Buyer Release Assumptions” on page 109
• “Release Authorization in Ariba Buyer” on page 110
• “Release Classification” on page 111
• “Release RFCs” on page 112

Chapter 8 Release Authorizations Pulls Release Authorities
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 might 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 the
expenditure is over $2,000, your boss needs the approval of his or her supervisor, and
so forth.
Release authorities might closely resemble the approval flow rules in your version of
Ariba Buyer. The ZAF7 RFCs use your existing SAP release authorization setup to
approve requisitions in Ariba Buyer. For information on how Ariba Buyer handles
approval rules, see the Ariba Buyer Approval Rules Guide.
Release authorities consist of the following:

• “Conditions, Strategies, Indicators, and Codes” on page 108
• “Profiles and Authorizations” on page 109
Conditions, Strategies, Indicators, and Codes

Become familiar with the 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—the requirements that determine which release strategy applies
to a given purchase requisition.
• Release indicator—whatever indicates whether the requisition becomes an order
after it has been released.
• Release code—whatever identifies the point in the release strategy when someone
can release a document.

ZAF7 Ariba Buyer Release Assumptions Chapter 8 Release Authorizations Pulls
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 permissions to approve a given item.
ZAF7 Ariba Buyer Release Assumptions

Ariba Buyer makes further assumptions about the way you 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 release strategies such as those
presented in the following table:
Release Strategies
Release Strategy Release Condition Release Codes

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

Chapter 8 Release Authorizations Pulls Release Authorization in Ariba Buyer
Release Strategies (Continued)
Release Strategy Release Condition Release Codes

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
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 it does have 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 and 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 an approval request. Approval requests correspond to users
or permissions and are represented as points in the chain of approval.

Release Classification Chapter 8 Release Authorizations Pulls
Approval Rules
Ariba Buyer defines the organization of approval requests by applying approval rules.
The default types of approval rules are as follows:
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 Rules Constraint rules organize approval requests in sequence.
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 without classification
• Those with classification
Classification refers to the entire collection of criteria upon which you might 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.

Chapter 8 Release Authorizations Pulls Release RFCs
Users can define release procedures only 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 ZAF7 group RFCs.
You 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.
For step-based instructions on how to display and set monetary amount characteristic
values, see the procedure on page 113.
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 RFC code from Ariba using the Function Builder in the Developer
Workbench.

Release RFCs Chapter 8 Release Authorizations Pulls
W To display and set your monetary amount characteristic value:

1 Run transaction spro, or choose Tools > Customizing > IMG > Edit Project.
2 Click SAP Reference IMG.
3 Choose Select Materials Management > Purchasing > Purchase Order > Release
Procedure for Purchase Order > Define Release Procedure for Purchase Orders.
4 Click Release Strategy.
The Release Strategies overview screen appears.

5 Create a new release strategy, or select (double-click) an existing one.
6 In the Release Strategies Details screen, click Classification.

The Release Strategies for Classification screen appears.
7 In the Values for Class panel, remember the class object, for example, FRG_EKKO.
8 Run transaction CL03.
9 Access the Display Class: Initial Screen, and paste or enter the class object name
you remembered in step 7. Alternatively, if you have forgotten the class object
name, follow these steps:
a Click the drill-down arrow for the class.
b The Restrict value range screen appears.
c Click the drill-down arrow for class type.
d In the Class type screen, select Release strategy.
e Click the green check mark.

All the classes for the release strategy appear.
f Select the class you want, for instance, FRG_EKKO.
10 Enter value 032 for class type.
11 Click the Char. tab.
12 Choose the monetary value that defines the currency.

This value has a Data Type entry of CURR.
13 Remember the value for the associated Characteristic.
15 Enter ZARIBTVARV, and then click Maintain.

Chapter 8 Release Authorizations Pulls Release RFCs
16 If you do not have an entry for Z_ARIBA_RELEASE_AUTHORITY_CNAM, create one with

the following information. For information on how to add parameters to
ZARIBTVARV, see Chapter 6, “Parameter Configuration.”
Field Name What to Enter

(Ariba Buyer) Variant Your variant for your SAP data
(Ariba Buyer) Partition Your partition for your SAP data
Variable Name Z_ARIBA_RELEASE_AUTHORITY_CNAM
Field name Leave blank

Selection cat. “P”
Number “0”
INCL/EXCL Leave blank
Option Leave blank
Selection value The name from the Characteristics field
Selection value Leave blank
17 Save your work.

Chapter 9
Real-Time Integrations
Ariba Buyer supports the use of IDOCs for pulling cost center, GL account, and
vendor information from SAP into Ariba Buyer in real time. This chapter explains
how to configure real-time integration using ALE/IDOC technology.
• ALE stands for Application Link Enabling, an SAP feature that defines a way of
communicating data between an SAP system and another process.
• IDOC stands for Intermediate Document, an SAP format that defines a way of
describing data.
In other words, ALE is a way of transferring data and an IDOC is a way of

representing that data.
This chapter assumes you have already installed Ariba Buyer.
Note: If you use the ZATCOS IDOC to pull cost center data into Ariba Buyer, the
deleted cost centers from SAP are not pulled back due to a limitation in the SAP
Standard Cost Center IDOC (COSMAS).
This chapter contains the following sections:

• “Ariba Buyer ALE/IDOC Configuration” on page 116
• “Repository and Worksheet Configuration” on page 125
• “Ariba Buyer Parameter Real-Time Configuration” on page 127
• “Handling Deletion” on page 129

Chapter 9 Real-Time Integrations Ariba Buyer ALE/IDOC Configuration
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 section includes the following sections:

• “Configuring a Base Logical System” on page 116
• “Defining Logical Systems for Partitions” on page 117
• “Defining a Distribution Model” on page 118
• “Defining a Port” on page 120
• “Creating an RFC Destination for ALE/IDOC” on page 121
• “Defining a Partner Profile” on page 122
• “Setting Up Global Company Codes” on page 123
• “Installing ALE/IDOC Transports” on page 125
If you already performed these tasks, move on to “Repository and Worksheet

Configuration” on page 125.
Configuring a Base Logical System

A logical system represents the source or destination of data exchanged with an SAP
instance. ALE treats all sources and destinations as logical systems.
Every client that uses ALE must have a unique base logical system that represents the
client in data communications. If you have not already configured a base logical
system for the client with which Ariba Buyer integrates, you are required to do so.
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
W To define a base logical system:

1 Run transaction Sale.
2 Define a logical system by choosing Sending and Receiving Systems > Logical
Systems > Define Logical System.
3 Click the green check for any information about client independence.
4 In the Logical Systems Overview screen, click New Entries.

Ariba Buyer ALE/IDOC Configuration Chapter 9 Real-Time Integrations
5 In the Log.System field of the New Entries: Overview of Added Entries screen,
enter a name for the logical system.
For the base logical system, you might want to adopt a naming standard, such as
fooCLNTbar, where foo is the instance name and bar the client.
6 In the Name field, enter a descriptive name for the base logical system.
7 Click Save.
W 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 Click Details, or press F2.

The Client Details view appears.
4 In the Logical System field, choose the base logical system you created in the
previous steps, and then click Save.
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 are required to create outbound logical
systems for every partition in your SAP variants.
W To define outbound logical systems for partitions:

1 Run transaction sale.
2 Choose Sending and Receiving Systems > Logical Systems > Define Logical System.
3 Click the green check button for any information about client independence.
4 Repeat the following steps until you define logical systems for every Ariba Buyer
partition in every SAP variant on all clients.
5 Click New Entries.
6 In the Log.System field, enter the exact Ariba Buyer partition name for the logical
system.
7 In the Name field, enter a descriptive name for the outbound logical system.
8 Click 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 guide 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 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 the message types
within SAP for pulling cost center, general ledger, and vendor information.
Note: To pull the correct General Ledger descriptions for the new General Ledger
Accounts created in SAP 4.6C (Support Pack Number SAPKH46C09), you must
implement OSS note 398301. If you do not perform the code correction described in
the OSS note, the General Ledger descriptions for the new GLAccounts pulled from
SAP using IDOCs will be incorrect. This limitation is not required for RFC pulls.
IDOCs use 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, activates their corresponding
change pointers, and links them to the appropriate IDOCs.
In order to exchange data between Ariba Buyer and SAP, you create and use a
distribution model named Ariba. The Ariba distribution model defines the message
types that a base logical system uses to communicate with each Ariba Buyer partition
logical system through ALE/IDOC.
If you have other SAP systems from which you want to send data to Ariba Buyer (and
they use the same distribution model), it is possible to distribute the model to the other
systems.
When you create a distribution, you can generate a partner profile automatically.

W To create an Ariba distribution model:

1 Run transaction Sale.
2 Choose ALE > Modelling and Implementing Business Practices > Maintain Distribution
Model and Distribute Views > Create Model View.
3 Click Create Model View.
4 Create a distribution customer model with the name Ariba.
5 Click Add Message Type to add the following message types:

• ZATCOS
• ZATGLM
• ZATCRE
For each message type, specify the following parameters:
• Model view: ARIBA
• Sender: SAP logical system
• Receiver: 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. You choose the SAP logical system from the
Logical System list.
Ariba Buyer partition name is the name of the Ariba Buyer partition.
Ariba Buyer message type is either ZATCOS, ZATCRE, or ZATGLM. You choose these
message types from the SAP-supplied list.
6 Click Save.
W To distribute the Ariba customer model to other SAP systems:

1 Highlight the Ariba distribution model.
2 From the Edit menu, choose Model view > Distribute.
3 Highlight the logical systems to which you want to distribute.
W To generate a partner profile for your distribution model:

1 From the Environment menu, choose Generate Partner Profiles.
The Generating Partner Profiles screen appears.
2 In the Model View field, enter ARIBA.

3 In Outbound Parameters panel, make sure the following default parameters are set:
Version: 3
Pack.size: 50 (You can adjust this setting later.)
4 In Output Mode panel, make sure that Transfer IDoc immed. is selected.
5 Click Execute.
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
real-time, single-object load information to the TIB/Adapter for R/3 through a tRFC
port from an RFC. You define this port.
W To define a tRFC port:

1 Run transaction WE21.
2 Choose Transactional RFC.
3 Press Enter if an information message about client independence is displayed.
4 To create your own port, choose Port > Create.

The Create tRFC Port window appears.
5 Choose Generate port name and click the green check mark.
6 Click Create, and then enter the following values:

• Description: a description of the port
• Version: SAP Release 4.x
• RFC Destination: YCIDOCPROC

Note: Remember the unique port number that SAP generates, for example,
A000000011. You need it for the tasks on page 122.
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/Adapter for R/3 that can handle the ALE/IDOC
real-time data. Ariba Buyer provides this RFC destination through a TCP/IP
connection.
RFC destinations for RFCs can use a program ID to identify uniquely a process or
daemon shared between an SAP system and the output of an RFC.
RFC destinations contain port descriptions for logical systems. You configure an RFC
destination called YCIDOCPROC for Ariba Buyer integrations to work.
W To create the TIB/Adapter for the R/3 RFC destination (for SAP 4.7):
2 Highlight TCP/IP connections, and click Create.
The RFC Destination window appears.

3 Enter the following information, and press Enter:
• RFC destination: YCIDOCPROC
• Connection type: T
4 Enter a description, such as Ariba Buyer IDOC.
5 Click the Technical Settings tab.
6 In the Activation Type panel, select Registered Server Program.
7 In the Program ID field, enter the program ID you have specified in the
configuration file for the specific partition.

Testing the Connection

After you create the TIB/Adapter for the R/3 RFC destination, test the connection.
Make sure Ariba Buyer and the TIB/Adapter are running.
W To test the connection for the R/3 RFC destination:

1 Start the TIB/Adapter for R/3 manually with the following command:
3 Scroll down, and open YCIDOCPROC.
Defining a Partner Profile

At a high level, a partner profile defines the way that a logical system sends messages
to other logical systems. All the ALE/IDOC components that 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 data. Partner profiles work at a very high level of
organization within SAP, and, in many ways, are the central component you configure
to allow real-time integration with Ariba Buyer.
SAP offers four types of partner profiles, most of which are involved in EDI
(Electronic Data Interchange) configuration. Real-time integration with Ariba Buyer
requires that you create partner profiles of type LS, for communication related to
logical systems.
W To configure partner profiles for 4.6C or 4.7:

1 Perform the steps in this task for every partition in every SAP variant.
2 Run transaction WE20.
3 In the navigation area, click Partner Profiles.
4 Click Create.

5 Click the Classification tab, and enter the following information:

• Partner no: the Ariba Buyer partition name
• Partner type: LS
• Partner class: ALE
• Partner status: A
7 Use the green arrow to navigate back.
8 In the Outbound parameters table, enter or select the message type and
corresponding basic type for each of these pairs:
• ZATCOS and COSMAS01
• ZATCRE andCREMAS01
• ZATGLM and GLMAST01
9 In the Partner Profiles Outbound Parameter window, enter or select 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
the procedure on page 120.
• Pack.size: 50 (You can adjust this later.)
• Transfer IDoc immed.
• Do not start subsystem
• Basic type: Enter the basic type that corresponds to the message type (COSMAS01,
CREMAS01, GLMAST01).

Ignore warnings that there are no entries for message control. Outbound only
partner profiles do not use message control.
Setting Up Global Company Codes

For an Ariba Buyer integration to work in real time, you set up global company codes:
• When you complete the optional real-time loading configuration, as described in
“Real-Time Integrations” on page 115.
• At any time, as described in “Setting Up Global Company Codes” on page 123.

Note: If you do not use IDOCs, global company codes are unnecessary for non-ALE
SAP integrations.
This section explains how to configure global company codes for real-time
integration. 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 perform this task by using the SAP IMG
(Implementation Guide).
W To set up global company codes:

1 Run transaction SALE.
2 Set up global company codes. For versions 4.6C or 4.7: choose Application Link
Enabling (ALE) > Modelling and Implementing Business Processes > Cross-Application
Settings > Global Organizational Units > Cross-System Company Codes.
3 In the Choose Activity dialog box, choose Cross-System Company Codes.
4 Click New entries to create the cross-system list of global company codes you use.
You might want 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.
6 Use the green arrow to navigate back, and choose Assign Cross-System Company Code to
Chart of Accounts.
7 Enter chart of accounts entries for each global company code, and save.
8 Use the green arrow to navigate back, and choose Assign Company Code to
Cross-System Company Code.
9 Enter Global Company Codes to represent any corresponding local company

codes. For versions 4.6C or 4.7: in the Global CoCde column, select or enter global
company codes to represent any corresponding local company codes.

Repository and Worksheet Configuration Chapter 9 Real-Time Integrations
Installing ALE/IDOC Transports

Your Ariba Buyer distribution media contains SAP transport files that enable
integration with Ariba Buyer. To use ALE/IDOC integration, make sure you have
installed the correct transports.
The ALE/IDOC related transports install the following items:

• The IDOC development classes ZATI and ZATC
• 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
For a list of the transports, see the Readme.txt file.
Repository and Worksheet Configuration

This section describes changes required in TIB/ActiveEnterprise applications and
Ariba Buyer. It includes the following sections:
• “Configuring Partition Names in Worksheets” on page 125
• “Opening Worksheets and Executing ALE/IDOCs” on page 126
Note: If you are using IDOC pull for the creation of general ledgers through the
ZATGLM WorkSheet, you cannot exclude General Ledgers with associated cost
elements. For this behavior, use the corresponding RFC Pull.
Configuring Partition Names in Worksheets

You are required to configure real-time single-object loading worksheets if your SAP
partition names are:
• Uppercase or contain both uppercase and lowercase letters.
• More than 60 characters in length for SAP 4.6C and 4.7.

Chapter 9 Real-Time Integrations Repository and Worksheet Configuration
W To handle partitions with upper or mixed case:

1 From the Ariba Buyer installation directory, enter the following shell command:
runtibco -startmb
2 Enter your user name, choose your SAP variant repository instance name, and then
click Connect.
3 Repeat the following steps for each of these worksheets:
• ZATCOS300
• ZATCRE300
• ZATGLM300
a Open the worksheet.
b Choose the following functions and view their Details panel:

• For ZATCRE300, Function67
• For ZATCOS300, Function8
• For ZATGLM300, Function89
c If your Ariba Buyer partition name is all uppercase, change the Edit Formula
from:
lower(partition.EDI_DC.RCVPRN)
to:
partition.EDI_DC.RCVPRN
If your partition name is in mixed case or too long for your version of SAP,
create a user-defined function that converts the SAP logical system name to the
properly formatted Ariba Buyer partition name. See your ASD representative
for assistance.
d Save the worksheet.
Opening Worksheets and Executing ALE/IDOCs

To execute ALE/IDOC integration events, the associated worksheets must be open in
the TIB/MessageBroker. The worksheets are:
• ZATCOS300
• ZATCRE300
• ZATGLM300

Ariba Buyer Parameter Real-Time Configuration Chapter 9 Real-Time Integrations
W To execute ALE/IDOCs:
1 To open each of the ZATCOS300, ZATCRE300, and ZATGLM300 worksheets, use the
TIB/MessageBroker interface or the following command:
runtibco -startmb
2 Put the worksheets in debugging mode.
3 In SAP, run Transaction BD21 to send the IDOCs not previously sent in SAP, or
schedule the transaction to be run in SAP.
The data flow indicator should change from red to green.
Ariba Buyer Parameter Real-Time Configuration

Ariba Buyer RFCs use the ZARIBTVARV structure to filter real-time ALE/IDOC changes
to appropriate destinations. You enter selection values within ZARIBTVARV for the
ALE/IDOC mechanisms to work. These selection values define the following:
• Variant destination
• Partition destination
• The Ariba Buyer RFC that processes the message types
To review how ZARIBTVARV provides filtering and parameter storage, see the following
sections:
• “About ZARIBTVARV” on page 87
• “Filtering” on page 63
W To define partition selection values:

1 Perform the steps in this task for every partition in every SAP variant.
2 Run transaction SM30, enter ZARIBTVARV, and click Maintain.
3 Continue past any warnings about repairs.

Chapter 9 Real-Time Integrations Ariba Buyer Parameter Real-Time Configuration
4 Repeat the following task for each Ariba Buyer message type:
• ZATCOS
• ZATCRE
• ZATGLM
a Click 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 Development Classes

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

Handling Deletion Chapter 9 Real-Time Integrations
Handling Deletion
Due to a limitation in the IDOC design, you occasionally schedule Ariba Buyer
integration events that pull data for cost centers, general ledger accounts, and
suppliers (which are IDOC-related) through batch methods. SAP can’t inform Ariba
Buyer that a record is inactive through IDOCs without some configuration. As a
result, you might find inactive data in Ariba Buyer that needs deletion.
To remedy this problem, occasionally schedule the non-IDOC integration events and
RFCs to pull IDOC-related data. Such pulls remove any data that requires deletion.
The following pulls resolve this deletion problem:.
Event Associated TIBCO Worksheet

CostCenterPull CostCenterEventSAP
GeneralLedgerPull GeneralLedgerEventSAP
PurchaseOrgSupplierComboPull PurchaseOrgSupplierComboSAP
SupplierPull VendorEventSAP

Chapter 9 Real-Time Integrations Handling Deletion

Chapter 10
Error Recovery
The SAP integration provides 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, the integration event can do two things:

• Recover automatically
• Report the error and wait for an administrator to take action
SAP integration is designed 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 appropriate administrator.
In general, the integration event can recover automatically from any error that occurs
before the data has been committed to SAP. After 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” on page 131
• “Failures Pulling from SAP” on page 134
• “Troubleshooting” on page 134
Failures Pushing to SAP

This section describes two types of errors:
• Application-level errors
• System errors

Chapter 10 Error Recovery Failures Pushing to SAP
Application-Level Errors
This section describes the following:
• Failures occurring during purchase order push
• Failures occurring during receipt push
Note: Because 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 push
successfully 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 pushed
successfully. If any line items for a particular SAP purchase order are rejected, the
push for that entire purchase order fails.
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 Professional
Buyer permission.
Errors During Purchase Order Push

Ariba Buyer always initiates a purchase order push, with an integration event that
pushes the order out to the TIBCO integration channel.
If an error occurs while the integration event for the real-time purchase order push
using TIBCO is initiated, Ariba Buyer logs an error, and the purchase requisition
associated with that order returns to the “Composing” state.
When a requisition is stuck in the “Composing” state, your Ariba Buyer administrator
should perform the following tasks:
1 Check the error in the requisition that has gone to the “Composing” state
2 Diagnose the problem
3 Correct the error
4 Submit/approve the requisition
The second stage of a push occurs when the integration event routes data through
TIB/MessageBroker and the TIB/Adapter for R/3 into SAP.

Failures Pushing to SAP Chapter 10 Error Recovery
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 situation can
happen if the master data objects are out of synch in Ariba Buyer and SAP. For
example, if a supplier is invalidated in the SAP system after the order has been created
in the Ariba Buyer system, the incoming order is rejected because it has a supplier
that is now invalid. You can avoid this problem by using real-time single-object
loading. For details, see Chapter 9, “Real-Time Integrations.”
For purchase orders, the push worksheets return error messages and details about
pushes immediately. When SAP rejects an order, it sends that order back, with an
error message saying why the order has been rejected. The worksheet returns this
error message to Ariba Buyer to indicate that there has been an error.
Errors During Receipt Push

If an application-level error occurs during receipt push (that is, the posting period is
not open in SAP), SAP rejects the receipt. The processing state of the receipt object in
Ariba Buyer goes from “Processing” to “Awaiting Processing.” Receipts are pushed
again when the ProcessReceipts scheduled task is run again.
System-Level Errors
If the TIB/Adapter for R/3 is down due to network problems, SAP never receives a
purchase order from Ariba Buyer. Such a situation could result in system-level errors
where purchase orders or requisitions are stuck in the “Ordering” state.
Once a system-level error has been found, you don’t need to do anything special to
restart the push. The Ariba Buyer scheduled task FailedOrders checks for unfinished
orders and re-executes the order transmission. Either wait until the next scheduled run
of this task, or execute it manually from Ariba Buyer Administrator.
The ProcessStuckERPOrders scheduled task, typically not run on a regular schedule, is

run manually by an administrator correcting an error. This task changes the state of
purchase orders, change orders, and cancel orders destined for SAP to
Ordering/Failed so that the FailedOrders scheduled task can attempt to process them
again. For example, an order might get stuck in Ordering if a network problem or
channel adapter error prevented SAP from receiving the order or prevented Ariba
Buyer from receiving the status. For additional information, see the Ariba Buyer
Procurement Guide. For more information on scheduled tasks, see the Ariba Buyer
Configuration Reference Guide.

Chapter 10 Error Recovery Failures Pulling from SAP
Failures Pulling from SAP

Errors occur in two situations when data is pulled from SAP:
• Standard data pulls
• Network failure during remittance pull
When failures occur during standard data pulls from SAP:

1 Correct the error.
2 Rerun the pull.
In the case of a network failure during remittance pull:

1 Correct the network problem.
2 Run the remittance pull again.
3 Correct the date timestamp.
4 Change the date timestamp in the file accordingly to pull only the payments not
pulled in the first run.
The fields are all updated if the status of the payment transaction has not been
changed from paid to canceled. Otherwise, an error occurs.
Troubleshooting
This section provides tips for solving problems associated with integrating Ariba
Buyer with SAP.
Note: The TIB/Adapter for R/3 sends “Internal Error” stack traces that you can safely
ignore. These stack traces do not cause error conditions. Furthermore, your SAP
events run successfully while or after these traces appear.
Enabling Debugging
When you call an RFC, you can turn on a debugging switch. This action enables you
to access the SAP user interface, where you can set breakpoints.

Troubleshooting Chapter 10 Error Recovery
W To debug through the SAP user interface:

1 Keep an SAP user interface session open.
2 From the Ariba Buyer working directory, turn on SAP’s debugging mode by typing
this command at the command line:
set RFC_DEBUG=1
You can also set this as an environment variable.

3 Restart the Ariba Buyer server.
4 Trigger the event by submitting a requisition or a receipt, or by running a pull

through the Ariba Buyer Administrator.
5 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.
As you call an RFC, the breakpoint you set causes the debugging tool to stop at the
first line of the RFC code.
6 When you finish debugging, turn debugging mode back off again by typing this
command at the command line of the Ariba Buyer working directory:
set RFC_DEBUG=0
You can debug TIB/MessageBroker worksheets at the same time.
W To debug through TIB/MessageBroker:

1 Change the integration event initialization parameter in the Message
Configuration table from its current setting, for example, Automatic Stayup, to
manual.
2 Start TIB/MessageBroker, and open the worksheet.
3 Put the worksheet in Run mode.

All the flow lines turn red.
4 Execute the event from Ariba Buyer.
The lines turn green indicating the flow of data in the worksheet.
5 Choose Watch from the Debug menu to check the data.

Chapter 10 Error Recovery Troubleshooting
Debugging Parameters
Ariba Buyer RFCs offer two parameters:
• Z_ARIBA_PO_PUSH_DISPLAY_MODE
• Z_ARIBA_GR_PUSH_DISPLAY_MODE
To watch push operations, change these parameters from ‘N’ to ‘E’ or ‘A’. Changing
these parameters also enables you to view purchase order or goods receipt screens in
debug mode.
For more information on using these parameters, see “Debugging Pushes” on

page 91.

Appendix A
Ariba SAP Objects
This appendix lists the Ariba SAP development objects and describes the naming
conventions for those objects. The audience for this appendix includes:
• BASIS administrators who import Ariba’s SAP transports and need to see the list
of objects they’re importing
• ABAP developers who are responsible for customizing the Ariba SAP objects
This appendix includes the following sections:

• “Naming Conventions for Ariba SAP Objects” on page 137
• “Summary of Ariba SAP Development Classes” on page 138
• “ZAR6 Development Class” on page 139
• “ZARC Development Class” on page 146
• “ZATI Development Class” on page 151
• “ZATC Development Class” on page 153
• “ZARIBA_CHANGEORDER Development Class” on page 155
• “ZARIBA_CUSTCHANGEORDER” on page 157
• “ZARIBTVARV RFC Reference” on page 158
• “ZARIBA_REMITTANCE Development Class” on page 160
• “ZARIBA_CUST_REMITTANCE Development Class” on page 161
Naming Conventions for Ariba SAP Objects

The general naming conventions for Ariba SAP objects are as follows:
• Development class names begin with the prefix ZA.
• Function group names begin with one of the following prefixes: ZAF, ZAG, ZAT, or
ZTF.

Appendix A Ariba SAP Objects Summary of Ariba SAP Development Classes
• Function module names begin with the prefix Z_ARIBA. Some of the modules end
with the suffix _EXT—for example—Z_ARIBA_GR_PUSH_EXT. These modules are
customizable. The Z_ARIBA modules without the _EXT suffix are core Ariba function
modules that you shouldn’t modify.
• Table names begin with the prefix ZAR. Some of the tables end with an X—for
example, ZARGRFMAPX. These tables are for custom entries. The ZAR tables that don’t
end with an X are core Ariba tables that you shouldn’t modify.
• Structure names begin with the prefix ZAR or ZXT. The ZAR structures are core Ariba
structures that you shouldn’t modify, whereas the ZXT structures are extension
structures that are customizable.
• Data element names begin with the prefix ZAR. The one exception is the data
element ZFIELDNAME in the ZAR6 development class.
• Message class: Ariba’s message classes are named ZA and ZT.
Summary of Ariba SAP Development Classes

This section lists the development classes and the Ariba SAP objects in those classes.
The following table describes the development classes:
Development Class Contents Description

ZAR6 Ariba development objects page 139
ZARC Custom exit functions, append structures, page 146
and so on
ZATI Ariba-TIBCO integration development page 151
objects
ZATC Ariba-TIBCO integration user exits page 153
ZAR7 Ariba-SAP 4.6C development objects page 154
ZAR8 Ariba-SAP 4.6C development objects page 155
ZARIBA_CHANGEORDER Ariba-SAP 4.6C change order integration page 155
development objects
ZARIBA_CUSTCHANGEORDER Custom Ariba-4.6C change order page 157
integration development objects

ZAR6 Development Class Appendix A Ariba SAP Objects
The descriptions of each development class describe the objects in each class,
including any of the following:
• Function groups and function modules
• Tables
• Structures
• Data elements
• Includes
• Message classes
ZAR6 Development Class

The ZAR6 development class contains Ariba development objects.
ZAR6 Function Groups and Modules

The following are the function groups in the ZAR6 development class:
ZAR6 Function Groups
Function Group Description

ZAF1 Ariba Materials Management RFCs
ZAF2 Ariba FICO RFCs
ZAF3 Ariba Core RFCs
ZAF4 Ariba IMG RFCs
ZAF5 Ariba Example RFCs
ZAF7 Ariba Example Release Authority RFCs
ZAF8 ZARIBTVARV maintenance dialog-generated
ZAF9 Maintenance dialog-generated
ZAG1 Maintenance dialog-generated
ZAT2 Maintenance dialog-generated

Appendix A Ariba SAP Objects ZAR6 Development Class
ZAR6 Function Groups (Continued)

In the ZAR6 development class, the function groups ZAF8, ZAF9, ZAG1, ZAT2, ZAT3, ZAT4,
and ZAT5 contain only function modules automatically generated by the SAP
maintenance dialog. The function modules in these function groups are not
customizable and are not described in this document. The function modules for the
rest of the function groups are described in the following tables.
ZAF1 Function Modules
Function Module Description

Z_ARIBA_ACCOUNT_CATEGORY Pulls Account Assignment Categories and their
properties
Z_ARIBA_ACCOUNT_CAT_NAMES Pulls Account Assignment Category
Multi-Lingual Names
Z_ARIBA_ACC_FIELD_STATUS Pull for AccountCategory/Field Status combo
Z_ARIBA_COMPANY Details of Company
Z_ARIBA_GR_PUSH Creates a goods receipt document in SAP
Z_ARIBA_MATERIAL_GROUP Ariba Adapter Material Group Function Module
Z_ARIBA_MATERIAL_GROUP_NAMES Pulls Material Group Multi-Lingual Names
Z_ARIBA_PLANT Ariba Adapter Plant (Ship-To) Pull Function
Module
Z_ARIBA_PLANT_PORG Ariba Adapter Plant/Purchase Org
Combinations Function Module
Z_ARIBA_PO_DETAILS Pull PO details
Z_ARIBA_PO_PUSH Creates a purchase order in SAP
Z_ARIBA_PURCHASE_GROUP Ariba Adapter Purchase Group Function
Module

ZAF1 Function Modules (Continued)

Z_ARIBA_PURCHASE_ORG Ariba Adapter Purchase Organization Pull
Function Module
Z_ARIBA_STRINGSPLIT_AT_POSITON Splits the String at a particular position
Z_ARIBA_VENDOR Pulls vendor and vendor/porg information
Z_ARIBA_VENDOR_ONLY Ariba Adapter Vendor Information Pull
Function Module
Z_ARIBA_VENDOR_PORG Ariba Adapter Vendor/Purchase Organization
Pull Function Module

Z_ARIBA_ASSET Pulls list of assets
Z_ARIBA_COST_CENTER Ariba Adapter Cost Center Pull Function
Module
Z_ARIBA_COST_CENTER_NAMES Pulls Cost Center Multi-Lingual Names
Z_ARIBA_GENERAL_LEDGER Ariba Adapter General Ledger Pull Function
Module
Z_ARIBA_GENERAL_LEDGER_NAMES Pull General Ledgers Multi-Lingual Names
Z_ARIBA_INTERNAL_ORDER Pulls internal orders
Z_ARIBA_MINORITY_INDICATOR Deprecated function module
Z_ARIBA_MINORITY_VENDOR Gets Vendor/Minority Indicator combo
Z_ARIBA_WBS Holds WBS element information for Ariba


Z_ARIBA_LAST_CHANGE_DATE Gets last change date for an object given its
object class
Z_ARIBA_PARAMETER Gets the value of a parameter
Z_ARIBA_PREFILTER Retrieves prefiltering restrictions
Z_ARIBA_SELECT_LIST Returns fields of structure

Z_ARIBA_CURRENCY Pull currencies
Z_ARIBA_CURRENCY_CONVERSION Ariba Adapter Currency Conversion Pull
Function Module
Z_ARIBA_TAX_CODE Tax Code Pull for Use in Ariba
Z_ARIBA_TAX_CODE_NAMES Pulls Tax Code Multi-Lingual Names
Z_ARIBA_UOM Pulls Units of Measure

Z_ARIBA_BUDGET_CHECK Mocked-up budget validation
Z_ARIBA_PASS_CHECK Example password checking RFC
Z_ARIBA_USER_BY_PART_EXAMPLE Example RFC—Pulls mock User information
based on partition parameter

Z_ARIBA_RELEASE_AUTHORITY Example of how release codes can be mapped to
release authority
Z_ARIBA_USER_RELEASE_CODE Example of how users can be mapped to release
codes

ZAR6 Tables
The following are the tables for the ZAR6 development class:
ZAR6 Tables
Table Description
ZARGRFMAP Maps interface tables to screen fields (do not change)
ZARGRFMAPX Maps interface tables to screen fields (customer maintains)
ZARIBAGRS GRs pushed to SAP from Ariba Buyer
ZARIBAPOS SAP POs that have been pushed to SAP by Ariba
ZARIBTVARV TVARV generalized for fields
ZARPOERRRQ Error Requisition Structure for Z_ARIBA_PO_PUSH
ZARPOFMAP Maps interface tables to screen fields (do not change)
ZARPOFMAPX Maps interface tables to screen fields (customer maintains)
ZAR6 Structures
The following are the structures for the ZAR6 development class:
ZAR6 Structures
Structure Description
ZARACCNAME Names for account categories
ZARACCST Account Category/Field Status Group combo
ZARASSET Structure to store MainAsset information for Ariba
ZARCOMPANY Company Code, Name, and other details
ZARCOSTC Structure for Output of All Cost Structure Info for Ariba
ZARCOSTNAM Cost Center Names
ZARCURCO Structure for Currency Conversion Type Info for Ariba
ZARCURR Structure for Currencies
ZARCURTY Structure for Output of All Unit of Measure Info for Ariba

ZAR6 Structures (Continued)
ZARERRCORE Error Message Structure for Z_ARIBA_PO_PUSH
ZARGENLE General ledger info
ZARGLCC Structure for Output G/L / Cost Center Info for Ariba
ZARGLLANG Names of General Ledgers
ZARGRERR Error Message Structure for Z_ARIBA_GR_PUSH
ZARGRHEADR Material Document header info for Ariba GR Push (do not
modify)
ZARGRITEMS Material Document item info for Ariba GRs (do not
modify)
ZARIACCASS Account Assignment Category and its properties
ZARIBAWTAB Table Structure for “WHERE (itab)” Statement
ZARIFSTAG Field status group definitions
ZARMGRP Structure for Output of all Material Group Info for Ariba
ZARMGRPNAM Material Group Names
ZARMGRPT Structure for Output of all Material Group Info for Ariba
ZARMINORIT Ariba structure for Minority Indicators
ZARMINVEND Ariba vendor/minority indicator combination
ZARORD Structure to hold order numbers for Ariba
ZARPGRP Structure for Output of all Purchasing Groups for Ariba
ZARPLANT Structure for Output of all Plant Info for Ariba
ZARPLCC Plant Cost Center Structure used in Z_ARIBA_PLANT_CC_PULL
ZARPLGL Structure for Plant/ G/L Output for Ariba
ZARPLPO Structure for Plant/Purchase Orgs Combinations for Ariba
ZARPLPOT Structure for Plant/Purchase Orgs Combinations for Ariba
ZARPOACCNT Purchase order accounting info for Ariba POs (do not
modify)

ZARPODELIV Ariba Purchase Order delivery date
ZARPODET Structure for pulling PO details
ZARPOERR Error Message Structure for Z_ARIBA_PO_PUSH
ZARPOGL Structure for Output of Purchase Org/GL Info for Ariba
ZARPOH Object created to delete for transport of migration
ZARPOHEADR Purchase order header info for Ariba POs (do not modify)
ZARPOI Table created for deletion
ZARPOITEMS Purchase order item info for Ariba POs (do not modify)
ZARPOORG Structure for Output of Purchase Organizations for Ariba
ZARPORQDET Structure for pulling PO details
ZARPOUTLNE Structure for Outline data for PO Push for Ariba
ZARRELAUTH Example mapping release codes to monetary authorization
levels
ZARSTRING Structure for text data for PO Push for Ariba
ZARTAXCODE Tax Code Information for use in Ariba
ZARTAXNAME Tax Code Names for use in Ariba
ZARTEST Structure for test case of calling an RFC with static
parameters
ZARUOM Structure for Output of All Unit of Measure Info for Ariba
ZARUSERREL Maps Users to Release Codes of Maximum Release
Authority
ZARVEN1 Structure for Output of Vendor Name and ID Info for Ariba
ZARVEND Structure for Output Vendor Information for Ariba
ZARVENDMIN Ariba vendor/minority indicator combination
ZARVENPO Structure for Output of Vendor/Purchase Org Information
for Ariba

Appendix A Ariba SAP Objects ZARC Development Class
ZARWBS Structure to hold WBS element information
ZEXUSER Sample to return user information for example user pull
ZAR6 Data Elements

The following are the data elements for the ZAR6 development class:
Data Element Description

ZARIBAEILE Line number
ZARIBAEKKN Serial number of account assignment
ZARPARTIT Ariba data partition
ZARVARIANT Ariba Buyer Variant Name (do not confuse with an
SAP Variant)
ZARWERKS Plant
ZFIELDNAME Target field name (including parens for fields in step
loop)
ZAR6 Message Class

The following is the message class for the ZAR6 development class:
Message Class Description

ZA Error messages for Ariba SAP ABAP code
ZARC Development Class

The ZARC development class contains customer exit functions, append structures, and
so on.

ZARC Development Class Appendix A Ariba SAP Objects
ZARC Function Groups and Modules

The following are the function groups in the ZARC development class:

ZAFC Customer exits (from 6.1PX)
ZAFD Customer exits (from 7.0)
The following tables describe the function modules for these function groups:
ZAFC Function Modules

Z_ARIBA_ACCOUNT_CATEGORY_EXT Pulls Account Assignment Categories and their
properties
Z_ARIBA_ACC_FIELD_STATUS_EXT Pulls for AccountCategory/Field Status combo
Z_ARIBA_ASSET_EXT Pulls list of assets
Z_ARIBA_COMPANY_EXT Details of Company
Z_ARIBA_COST_CENTER_EXT Ariba Adapter Cost Center Pull Function
Module
Z_ARIBA_CURRENCY_CONV_EXT Ariba Adapter Currency Conversion Pull
Function Module
Z_ARIBA_CURRENCY_EXT Pulls currencies
Z_ARIBA_GENERAL_LEDGER_EXT Ariba Adapter General Ledger Pull Function
Module
Z_ARIBA_INTERNAL_ORDER_EXT Pulls internal orders
Z_ARIBA_MATERIAL_GROUP_EXT Ariba Adapter Material Group Function Module
Z_ARIBA_MINORITY_INDICATOR_EXT Gets Minority Indicators
Z_ARIBA_MINORITY_VENDOR_EXT Gets Vendor/Minority Indicator combo
Z_ARIBA_PLANT_EXT Ariba Adapter Plant (Ship-To) Pull Function
Module

ZAFC Function Modules (Continued)

Z_ARIBA_PLANT_PORG_EXT Ariba Adapter Plant/Purchase Org
Combinations Function Module
Z_ARIBA_PO_DETAILS_EXT Pulls PO details
Z_ARIBA_PO_PUSH_EXT Creates a purchase order in SAP
Z_ARIBA_PREFILTER_EXT Retrieves prefiltering restrictions
Z_ARIBA_PURCHASE_GROUP_EXT Ariba Adapter Purchase Group Function
Module
Z_ARIBA_PURCHASE_ORG_EXT Ariba Adapter Purchase Organization Pull
Function Module
Z_ARIBA_RELEASE_AUTHORITY_EXT Example of how release codes can be mapped to
release authority amount
Z_ARIBA_TAX_CODE_EXT Ariba Adapter Currency Pull Function Module
Z_ARIBA_UOM_EXT Pulls Units of Measure
Z_ARIBA_USER_RELEASE_CODE_EXT Example of how users can be mapped to release
codes
Z_ARIBA_VENDOR_EXT Pulls vendor and vendor/porg information
Z_ARIBA_VENDOR_ONLY_EXT Ariba Adapter Vendor Information Pull
Function Module
Z_ARIBA_VENDOR_PORG_EXT Ariba Adapter Vendor/Purchase Organization
Pull Function Module
Z_ARIBA_WBS_EXT Structure defined to hold WBS element
information for Ariba
ZAFD Function Modules

Z_ARIBA_ACCOUNT_CAT_NAMES_EXT Pulls Account Assignment Categories and their
properties
Z_ARIBA_COST_CENTER_NAMES_EXT Ariba Adapter Cost Center Pull Function
Module

ZARC Development Class Appendix A Ariba SAP Objects
ZAFD Function Modules (Continued)

Z_ARIBA_GL_NAMES_EXT Extension function module for pulls of names
of General Ledgers
Z_ARIBA_GR_PUSH_BDCDATA_EXT Ariba Customer Extention to Z_ARIBA_GR_PUSH
Z_ARIBA_GR_PUSH_ERRORS_EXT Customer exit for changing error messages
from GR push
Z_ARIBA_GR_PUSH_EXT Ariba Customer Extention to Z_ARIBA_GR_PUSH
Z_ARIBA_MATERIAL_GRP_NAMES_EXT Ariba Adapter Material Group Function
Module
Z_ARIBA_PO_PUSH_BDCDATA_EXT Customer exit for changing data on the bdcdata
before doing call trans
Z_ARIBA_PO_PUSH_ERRORS_EXT Customer exit for changing error messages
from PO push
Z_ARIBA_PO_PUSH_PRE_EXT Creates a purchase order in SAP
Z_ARIBA_TAX_CODE_NAMES_EXT Tax Code Pull for Use in Ariba
ZARC Structures
The following are the structures in the ZARC development class:
ZARC Structures
ZXTACCNAME Extension structure for ZARACCNAME
ZXTACCST Ariba Extension for ZARACCST
ZXTASSET Ariba Extension for Assets
ZXTCOMPANY Ariba Extension for Company Codes
ZXTCOSTC Ariba Extension for Cost Centers
ZXTCOSTNAM Extension structure for ZARCOSTNAM
ZXTCURCO Ariba Extension for Currency Conversions

ZARC Structures (Continued)
ZXTCURR Extension structure for ZARCURR
ZXTGENLE Ariba Extension for General Ledgers
ZXTGLLANG Extension structure for ZARGLLANG
ZXTGRERR Extension structure for ZARGRERR
ZXTGRHEADR Ariba Extension for material document header
ZXTGRITEMS Ariba Extension for material document items
ZXTIACCASS Ariba Extension for Account Assignment Categories
ZXTMGRP Ariba Extension for Material Groups
ZXTMGRPNAM Extension structure for ZARMGRPNAM
ZXTMINORIT Ariba Extension for Minority Indicators
ZXTORD Ariba Extension for Internal Orders
ZXTPGRP Ariba Extensions for Purchasing Groups
ZXTPLANT Ariba Extension for Plants
ZXTPLPO Ariba Extension for Plant/Purchase Org Combos
ZXTPOACCNT Ariba Extension for purchase order accounting info
ZXTPODELIV Ariba Extension for ZARPODELIV
ZXTPODET Ariba Extension for PO Details
ZXTPOERR Extension structure for ZARPOERR
ZXTPOHEADR Ariba Extension for purchase order header
ZXTPOITEMS Ariba Extension for purchase order items
ZXTPOORG Ariba Extension for Purchase Organizations
ZXTPORQDET Ariba Extension for PO Details
ZXTRELAUTH Ariba Extension for Release Authorities
ZXTTAXCODE Ariba Extension for ZARTAXCODE

ZATI Development Class Appendix A Ariba SAP Objects
ZARC Structures (Continued)
ZXTTAXNAME Extension structure for ZARTAXNAME
ZXTUOM Extension structure for ZARUOM
ZXTUSERREL Ariba Extension for ZARUSERREL
ZXTVEND Ariba Extension for Vendors
ZXTVENDMIN Ariba Extension for vendor/minority indicator combo
ZXTVENPO Ariba Extension for Vendor Purchase Org combos
ZXTWBS Ariba Extension for WBS Elements
ZATI Development Class

The ZATI development class contains development objects for Ariba-TIBCO
integration.
ZATI Function Groups and Modules

The following are the function groups in the ZATI development class.

ZTF1 TIBCO MM IDOCs
ZTF2 TIBCO FICO IDOCs
ZTF3 TIBCO Core Functions
The following are the function modules for each of these function groups:
ZTF1 Function Module

Z_MASTERIDOC_CREATE_AT_ZATCRE Generates Master IDOC ZATCRE from Change
Pointers

Appendix A Ariba SAP Objects ZATI Development Class
ZTF2 Function Modules

Z_AT_GL_FILTER Selection/Filtering of Valid G/L Accounts
Z_MASTERIDOC_CREATE_AT_ZATCOS Generates Master IDOC ZATCOS from Change
Pointers
Z_MASTERIDOC_CREATE_AT_ZATGLM Generates Master IDOC ZATGLM from
Change Pointers
ZTF3 Function Modules

Z_AT_IDOC_DESTINATION_GET Get all valid partitions for the given data type
Z_AT_ZARIBTVARV_INTEREST_CHECK Check the interest on the objects for a given
partition
ZATI Includes
The following is the include for the ZATI development class:
Include Description
ZTIBCONT Constants
ZATI Message Class

Following is the message class for the ZATI development class:
Message Class Description

ZT Message class

ZATC Development Class Appendix A Ariba SAP Objects
ZATC Development Class

The ZATC development class contains user exits for Ariba-TIBCO integration.
ZATC Function Group and Modules

The following is the function group in the ZATC development class:
ZATC Function Group

ZATC Ariba-TIBCO Integration User Exits Function
The following are the function modules for the ZATC function group:
ZATC Function Modules

Z_AT_ZATCOS_EXT Generates Master IDOC ZATCOS from Change
Pointers
Z_AT_ZATCRE_EXT Generates Master IDOC ZATCRE from Change
Pointers
Z_AT_ZATGLM_EXT Generates Master IDOC ZATGLM from Change
Pointers


The ZAR7 development class contains Ariba development objects for SAP 4.6C.
ZAR7 Function Group and Modules

The following is the function group in the ZAR7 development class:

ZAFA BAPI Wrapper
The following are the function modules for the ZAFA function group:
ZAFA Function Modules

Z_ARIBA_BAPI_PO_CREATE_POST Creates purchase order
Z_ARIBA_BAPI_PO_CREATE_PRE Creates purchase order
ZAR7 Structures
The following are the structures in the ZAR7 development class:
ZAR7 Structures
ZARBAPIEKKOC Ariba structure for BAPI_PO_CREATE Header info
ZARIBABAPIEKKN Ariba structure for BAPIEKKN
ZARIBABAPIEKPOC Transfer Structure: Create PO Item
ZARIBABAPIESKLC Adds the Quantity Field


The ZAR8 development class contains Ariba development objects for SAP 4.6C.
ZAR8 Function Group and Module

The following is the function group in the ZAR8 development class:

ZAFB BAPI Wrapper for 4.6C
The following is the function module for the ZAFB function group:
ZAFB Function Modules

Z_ARIBA_BAPI_PO_CREATE Creates purchase order
ZARIBA_CHANGEORDER Development Class

The ZARIBA_CHANGEORDER development class contains Ariba development objects for
change order integration with SAP 4.6C.
ZARIBA_CHANGEORDER Function Group and Modules

The following is the function group in the ZARIBA_CHANGEORDER development class:
ZARIBA_CHANGEORDER Function Group

ZARIBA_CHANGEORDER Function group for change order integration

Appendix A Ariba SAP Objects ZARIBA_CHANGEORDER Development Class
The following is the function module for the ZARIBA_CHANGEORDER function group:
ZARIBA_CHANGEORDER Function Modules

Z_ARIBA_BAPI_PO_CHANGE Changes the purchase order
Z_ARIBA_BAPI_PO_CANCEL Cancels the purchase order
Z_ARIBA_PO_HEADER_STATUS Pulls SAP cancel status
ZARIBA_CHANGEORDER Structures
The following are the structures in the ZARIBA_CHANGEORDER development class:
ZARIBA_CHANGEORDER Structures
ZARCPOACCNT Accounting information for change orders
ZARCPODELACCNT Deleted accounts for change orders
ZARCPODELITEMS Deleted items for change orders
ZARCPOHEADR Header information for change orders
ZARCPOITEMS Items for change orders

ZARIBA_CUSTCHANGEORDER Appendix A Ariba SAP Objects
The ZARIBA_CUSTCHANGEORDER development class contains custom development objects
for change order integration with SAP 4.6C.
ZARIBA_CUSTCHANGEORDER Function Group and Module

The following is the function group in the ZARIBA_CUSTCHANGEORDER development
class:
ZARIBA_CUSTCHANGEORDER Function Group

Z_ARIBA_CUST_CHANGEORDER Custom function group for change order
integration
ZARIBA_CUST_CHANGEORDER1 Custom function group for change orders and
associated function module
The following is the function module for the ZARIBA_CHANGEORDER function group:
ZARIBA_CUSTCHANGEORDER Function Module

Z_ARIBA_BAPI_PO_CHANGEPRE_EXT Changes the purchase order
Z_ARIBA_PO_HEADER_STATUS_EXT Extension function module for header status pull
ZARIBA_CUSTCHANGEORDER Structures
The following are the structures in the ZARIBA_CUSTCHANGEORDER development class:
ZARIBA_CUSTCHANGEORDER Structures
ZXTCPOACCNT Ariba extension for accounts
ZXTCPODELACCNT Ariba extension for deleted accounts
ZXTCPODELITEMS Ariba extension for deleted items

Appendix A Ariba SAP Objects ZARIBTVARV RFC Reference
ZARIBA_CUSTCHANGEORDER Structures (Continued)
ZXTCPOHEADR Ariba extension for change order header
ZXTCPOITEMS Ariba extension for change order items
ZARIBTVARV RFC Reference

The ZARIBTVARV table contains parameters used by master data pull RFCs. The
following table lists each of these RFCs and its associated table used to filter data. For
a list of the parameters in ZARIBTVARV, see Chapter 6, “Parameter Configuration.”
ZARIBTVARV RFCs
RFC Description Table

Z_ARIBA_ACCOUNT_CATEGORY Pulls Account Assignment Categories and their T162k
properties
Z_ARIBA_ACCOUNT_CAT_NAMES Pulls Account Assignment Category Multi-Lingual T163I
Names
Z_ARIBA_ACC_FIELD_STATUS Pull for AccountCategory/Field Status combination T162K
Z_ARIBA_COMPANY Details of Company T001
Z_ARIBA_MATERIAL_GROUP Ariba Adapter Material Group Function Module T023
Z_ARIBA_MATERIAL_GROUP_NAMES Pulls Material Group Multi-Lingual Names T023T
Z_ARIBA_PLANT Ariba Adapter Plant (Ship-To) Pull Function T001W
Module
Z_ARIBA_PLANT_PORG Ariba Adapter Plant/Purchase Org Combinations T024W
Function Module
Z_ARIBA_PURCHASE_GROUP Ariba Adapter Purchase Group Function Module T024
Z_ARIBA_PURCHASE_ORG Ariba Adapter Purchase Organization Pull T024E
Function Module
Z_ARIBA_VENDOR Pulls vendor and vendor/porg information LFM1
Z_ARIBA_VENDOR_ONLY Ariba Adapter Vendor Information Pull Function LFA1
Module

ZARIBTVARV RFC Reference Appendix A Ariba SAP Objects
ZARIBTVARV RFCs (Continued)
RFC Description Table

Z_ARIBA_VENDOR_PORG Ariba Adapter Vendor/Purchase Organization Pull LFM1
Function Module
Z_ARIBA_ASSET Pulls list of assets ANLA
Z_ARIBA_COST_CENTER Ariba Adapter Cost Center Pull Function Module CSKS
Z_ARIBA_COST_CENTER_NAMES Pulls Cost Center Multi-Lingual Names CSKT
Z_ARIBA_GENERAL_LEDGER Ariba Adapter General Ledger Pull Function SKB1
Module
Z_ARIBA_GENERAL_LEDGER_NAMES Pulls General Ledgers Multi-Lingual Names SKAT
Z_ARIBA_INTERNAL_ORDER Function to pull internal orders AUFK
Z_ARIBA_MINORITY_VENDOR Gets Vendor/Minority Indicator combo LFB1
Z_ARIBA_WBS Structure defined to hold WBS element PRPS
information for Ariba
Ariba IMG RFCs Pulls currencies TCURT
Z_ARIBA_CURRENCY_CONVERSION Ariba Adapter Currency Conversion Pull Function TCURR
Module
Z_ARIBA_TAX_CODE Tax Code Pull for Use in Ariba T007A
Z_ARIBA_TAX_CODE_NAMES Pulls Tax Code Multi-Lingual Names T007S
Z_ARIBA_UOM Pulls Units of Measure T006A
Z_ARIBA_BAPI_PO_CANCEL Integrates Ariba cancel orders with SAP none
Z_ARIBA_BAPI_PO_CHANGE Integrates Ariba change orders with SAP none

Appendix A Ariba SAP Objects ZARIBA_REMITTANCE Development Class
ZARIBA_REMITTANCE Development Class

The ZARIBA_REMITTANCE development class pulls remittance advice from SAP 4.6C.
ZARIBA_REMITTANCE Dictionary Structures

The following are the structures in the ZARIBA_REMITTANCE development class:
ZARIBA_REMITTANCE Dictionary Structures
ZARREMBSAK Ariba Structure for BSAK for Remittance Pull
ZARREMDETAIL Ariba Remittance Pull Detail
ZARREMHEADER Ariba Remittance Pull Header
ZARIBA_REMITTANCE Data Element

The following is the data element for the ZARIBA_REMITTANCE development class:
Data Element Description

ZARIBADATETIME Representation of date timestamp
ZARIBA_REMITTANCE Function Group

The following is the function group for the ZARIBA_REMITTANCE development class:

ZARIBA_REMITTANCE Function group for Remittance Pull

ZARIBA_CUST_REMITTANCE Development Class Appendix A Ariba SAP Objects
Z_ARIBA_REMITTANCE_PULL Function Module

The following is the function module for the ZARIBA_REMITTANCE development class:

Z_ARIBA_REMITTANCE_PULL Pulls remittance advice to Ariba Buyer
ZARIBA_CUST_REMITTANCE Development Class

The ZARIBA_CUST_REMITTANCE development class contains custom development objects
for remittance pull integration with SAP 4.6c.
ZARIBA_CUST_REMITTANCE Dictionary Structures

The following are the structures in the ZARIBA_CUST_REMITTANCE development class:
ZARIBA_CUST_REMITTANCE Dictionary Structures
ZXTREMBSAK Customer extension structure for BSAK table for
Remittance Pull
ZXTREMDETAIL Customer extension structure for Remittance Detail
ZXTREMHEADER Customer extension structure for Remittance Header
ZARIBA_CUST_REMITTANCE Function Group

The following is the function group for the ZARIBA_CUST_REMITTANCE development
class:
ZARIBA_CUST_REMITTANCE Function Group
ZARIBA_CUST_REMITTANCE Customer function group for remittance pull

Appendix A Ariba SAP Objects ZARIBA_CUST_REMITTANCE Development Class
ZARIBA_REMITTANCE_PULL_EXT Function Module

The following is the function module for the ZARIBA_REMITTANCE development class.

Z_ARIBA_REMITTANCE_PULL_EXT Customer Extension function module for remittance
pull

Appendix B
About SAP Transports
If you are integrating with SAP, it is required that you install SAP transports as part of
your Ariba Buyer installation. This appendix provides background information about
the Ariba-delivered SAP transports and detailed instructions for installing them.
Note: Ariba recommends that you ask your SAP BASIS personnel to install the
Ariba-delivered transports.
The appendix includes the following sections:

• “Overview of SAP Transports” on page 163
• “Transport Installation Instructions” on page 164
• “Transport Description Reference” on page 166
Overview of SAP Transports

This section presents an overview of the Ariba-delivered SAP transports. Read this
section before beginning the SAP transport installation process.
Delivered Transport Types

Ariba delivers three types of SAP transports to enable integration with Ariba Buyer.
These types include the following:
• Base functionality transport, containing Ariba SAP objects common to all SAP R/3
releases. This transport contains both workbench objects and
client-dependent and independent configuration.
• Real-time integration transport, required if you are exchanging cost center, general
ledger, and vendor data in an incremental, real-time fashion.
• SAP R/3 version-specific transport, required for particular SAP R/3 releases.

Appendix B About SAP Transports Transport Installation Instructions
Location of Transport Files

The Ariba-delivered SAP transports are installed in the following directory under
your Ariba Buyer Server installation directory:
BuyerServerRoot/configureOptions/sap/ariba/variant/trans/
Within this directory are subdirectories containing data files and cofiles for the
Ariba-delivered transports. Each transport has one data file and one cofile. The data
file names begin with the letter R, and cofile names begin with the letter K. For
example, a transport named ABCK900123 might have the following data file and cofile:
trans/data/R900123.ABC
trans/cofiles/K900123.ABC
Copy the Ariba transports from the location on your Ariba Buyer system to the
relevant subdirectories on your SAP system.
Transport Installation Instructions

The process for installing transports is the same for both first-time installations and
upgrades. Ariba delivers a set of transports for each SAP version for both installation
and upgrade. For complete information on installing transports, see the
configureOptions/sap/ariba/variant/trans/readme.txt file. You navigate to this
directory under mainerp on the Ariba Buyer CD or under the Ariba Buyer installation
root.
Warning: The transports contain both client-dependent and independent configuration.

Therefore, specify a target client when adding these transports to your import queue.
If you are using TMS, enable the target client to be specified in the queue by using
extended transport control.
Import Considerations
In general, you do not use any umodes when installing these transports. Use umodes
in the following circumstances:
• You have a previous version of the Ariba objects in your SAP system, and some
core objects have been modified. In this situation, override the repair flag on import
by using a umode. Reinstate any overwritten modifications to Ariba core objects
using the appropriate SAP tools.

Transport Installation Instructions Appendix B About SAP Transports
• You need to re-import one of the delivered transports. In this situation, make sure
the transport is fully re-imported by using umode 1.
If you do not require real-time integration, you do not have to import the real-time
integration transport. However, if you do install this transport, configure your SAP
system to use real-time integration with Ariba Buyer after the import is complete, as
described in the next section.
Configuring Your SAP System for Real-Time Integration

After you install the transport for real-time incremental loading, you perform several
additional configuration tasks to set up your SAP system. These tasks include the
following:
• Creating RFC destination YCIDOCPROC.
• Configuring a base logical system (LS) for each Ariba Buyer partition.
• Associating a base LS with your SAP client.
• Defining a transactional RFC (tRFC) port for RFC destination YCIDOCPROC.
• Defining a distribution model for the message types from base LS to each partition
LS.
• Defining a partner profile to tie the port definition to each message type.
• Defining partition selection values for each partition.
For detailed information on performing these tasks, see Chapter 9, “Real-Time

Integrations.”

Appendix B About SAP Transports Transport Description Reference
Transport Description Reference

This section describes the contents of the transports provided with this release of
Ariba Buyer.
Base Functionality Transport

The following table describes the content of the base functionality transport for this
release:

Data dictionary objects for Ariba core and customer layers No
Structures and function modules added between 6.x and 7.0 No
ZAR6 and ZARC development classes No
Document type “AR” for Ariba Buyer orders (View V_T161) Yes
Table maintenance editor for ZARIBTVARV No
Transport and Table maintenance editor for ZARGRFMAP and No
ZARGRFMAPX. Tracks the fields in which Ariba Buyer pushes
goods receipts.
Default goods receipt field mappings for the ZARGRFMAP table No

Transport Description Reference Appendix B About SAP Transports
Real-Time Integration Transport

The following table describes the content of the real-time integration transport for this
release:

Customer extension layer for IDOC code. Main development No
class is ZATC.
ZATI development class: IDOC code No
Client-dependent ALE/IDOC items for incremental loading: Yes
• Ariba Buyer message types: ZATCOS, ZATCRE, and ZATGLM
• Additional data for message type BD60
Assign message types to IDOC types (WE82, BD69) Yes
Activate ALE and change pointers for message types ZATCOS, Yes
ZATCRE, and ZATGLM (BD50). Also activate change pointers for
each document item (BD52).
SAP R/3 Version-Specific Transports

This section describes the content of the SAP R/3 version-specific transports for this
release.
Transports for SAP 4.6C

The following table describes the SAP 4.6C version-specific transports for this
release:

PO BAPI wrapper for development classes ZAR7 and ZAR8 No
(SAP 4.6C only) PO BAPI wrapper for change order No
integration for development classes ZARIBA_CHANGEORDER
and ZARIBA_CUSTCHANGEORDER

Appendix B About SAP Transports Transport Description Reference

Appendix C
Integration Events Reference
This appendix lists the integration events provided with Ariba Buyer that work with
SAP configurations. For complete information on these integration events, see the
Ariba Buyer Configuration Reference Guide.
SAP Integration Events
Event Name Description

AccCategoryFieldStatusComboPull Pulls combinations of Account Category and
Field Status codes, used in Ariba Buyer to
simulate accounting combinations used in SAP.
AccountCategoryLanguagePull Defines translations for the names of Account
Categories.
AccountCategoryPull Defines the accounting entity AccCategory,
used in the default configurations.
AccountTypeLanguagePull Defines translations for the names of Account
Types.
AssetPull Defines the accounting entity Asset, used in the
default configurations.
BuyerPaymentBankLocationPull Reads payment bank information for the buying
company from a CSV file. For more
information, see the Ariba Settlement Guide.
CommodityExportMapPull Defines a mapping from commodity codes to
SAP-specific ones.
CompanyCodeIOComboPull Defines combinations of company codes and
internal orders, used in default configurations.
CompanyCodePull Defines the SAP accounting entity
CompanyCode.
CompanyCodeWBSComboPull Defines combinations of company codes and
WBS elements, used in default configurations.

Appendix C Integration Events Reference
SAP Integration Events (Continued)

CostCenterLanguagePull Defines translations for the names of Cost
Centers.
CostCenterPull Defines the accounting entity CostCenter.
CurrencyConversionRatePull Loads the currency conversion rates.
ExampleUserPull Illustrates how to pull user data from CSV in an
SAP configuration. Not used in the default
configuration, but available as an example of
how to create such an event.
FieldStatusToAccountingFieldNameMapPull Maps SAP field status strings to accounting
field names.
GeneralLedgerLanguagePull Defines translations for General Ledger Pulls.
GeneralLedgerPull Defines the SAP accounting entity GL (General
Ledger).
GlobalCompanyCodeMapPull Uses a mapped type to map between local and
global company code data within the partition.
InternalOrderPull Defines the SAP accounting entity IO
(InternalOrder).
ItemCategoryPull Defines the kinds of orders that Ariba Buyer
can generate and push into your SAP system.
MinorityVendorPull Pulls information from SAP to indicate which
vendors are defined with “minority-owned”
status.
PartitionedCommodityCodePull Loads commodity codes from SAP.
PartitionedCommodityCodeLanguagePull Defines translations for commodity code
names.
PaymentTermsPull Defines payment terms.
PlantPull Defines a set of “plants,” which is a concept
similar to addresses.
PlantPurchaseOrgComboPull Pulls combinations of plants and purchasing
organizations, used in Ariba Buyer to simulate
SAP accounting combinations.


PurchaseGroupPull Defines a set of PurchaseGroups, by reading
from SAP.
PurchaseOrderCancelPush Pushes canceled purchase orders to SAP.
PurchaseOrderChangePush Pushes changed purchase orders to SAP.
PurchaseOrderERPHeaderStatusPull Pulls the SAP header status for a set of Ariba
Buyer purchase orders that are in an Ordered
state and that are created during a specified time
period.
PurchaseOrderPush Pushes purchase orders to SAP.
PurchaseOrderPushBAPI Pushes purchase orders to SAP through the
BAPI interface. Not used in the default
configuration.
PurchaseOrgPull Defines a set of purchasing organizations, by
reading from SAP.
PurchaseOrgSupplierComboPull Pulls combinations of purchasing organizations
and supplier, which are used in Ariba Buyer to
simulate the accounting combinations used in
SAP.
ReceiptPush Pushes receipts to SAP.
ReleaseAuthorityPull Pulls release authorization information from
SAP.
RemittancePull Pulls remittance data from SAP to Ariba Buyer.
SupplierLocationRemittanceInformationPull Reads remittance information associated with a
supplier location. For more information, see the
Ariba Settlement Guide.
SupplierPaymentBankLocationPull Reads payment bank information from a CSV
file. For more information, see the Ariba
Settlement Guide.
SupplierPull Defines the set of suppliers that is valid.


RemittanceLocationPull Pulls a list of valid remittance send addresses
from CSV files. This event is used for fraud
protection, to ensure that remittance addresses
defined in a supplier’s profile on Ariba SN are
valid. For more information, see the Ariba
Settlement Guide.
TaxCodeLanguagePull Defines translations for the names of tax codes.
TaxCodePull Defines tax codes required in SAP partitions
and used only in SAP partitions.
UserPull Defines a list of Ariba Buyer users and profile
information, reading from CSV. Also loads
PCardMap.
UserReleaseAuthorityPull Pulls release authorization information from
SAP.
WBSElementPull Defines the SAP accounting entity
WBSElement.

Index
A Advanced Business Application

ABAP debugging 92 Programming language.
ABAP filtering See ABAP/4 configuration classes,
about 70 ABAP/4 development classes,
sample 71 ABAP/4 language, ABAP filtering,
ABAP/4 configuration classes ABAP debugging
configuration 51 ALE/IDOC
real-time integration 128 configuring Ariba Buyer 116
ABAP/4 development classes 128 executing 126
ABAP/4 language 51 installing transports for 125
AccCategoryFieldStatusComboPull partition loading 95
integration event 169 pull 94
account assignment categories technology 115
about 97 amounts, truncating 22
configuring 99 Application Link Enabling. See ALE/IDOC,
displaying fields 98 IDOCs
pulling 98 application-level errors 132
account category RFC 104 approval requests 110
AccountCategoryLanguagePull integration approval rules 111
event 169 Ariba Buyer
AccountCategoryPull integration event 169 release authorization in 110
accounting entities 100 RFCs 16
accounting fields 99 setup 27
accounting information extension 77 Ariba Buyer Administrator 15
accounting objects 103 Ariba customer models. See customer models
accounting types 100 Ariba development classes 37
AccountTypeLanguagePull integration event Ariba distribution model 118
169 Ariba File Channel 19
action tag, reference 137 Ariba IR (invoice reconciliation) number 20
Adapter Services 57 Ariba SAP development objects 137
adr3 program file 35 Ariba Technical Support xiii
Ariba users. See CPIC users
aribaencode command 32
AssetPull integration event 169
assignment categories 104
audience xi

Index
authorizations Change PO parameter 95

CPO 24 change pointers, defined 118
profiles 109 changed purchase orders
release 107 enabling push 24
pulling header status of 25
push limitations 24
B pushing 24
BALANCE_SHEET_ACCOUNTS channels
parameter 88 Ariba File 19
bank selling rate 46 IBM WebSphere Business Integration
BAPI integrations Adapter 15
about 14 initializing 30
limitations 24, 86 repository database 31
pushing POs with 23 TIBCO 15
support 86 characteristics, defined 112
BAPI purchase order RFCs Check Payment method, remittance pull and
about 24 21
account assignment categories and 103 classification, release 111
BAPI_PO_CREATE_DOC_TYPE client connection information, verifying 32
parameter 93 client information, verifying 32
BAPI_PO_CREATE_ERP_DOC_TYPE ClientID parameter 28
parameter 93 ClusterRoot objects 103
base functionality transports 42, 163 commands
base logical systems aribaencode 32
associating with a client 117 configure 27
configuring 116 initdb 30, 49
base rules 111 runtibco 49, 122
basic version configuration option 27 comma-separated values. See CSV source
batch data control (BDC) extension 84 files
batch data control push exit functions 84 CommodityCodeLanguagePull integration
batch scheduling 129 event 170
Bills of Exchange, remittance advice and 21 CommodityExportMapPull integration event
blank descriptions 46 169
blocked vendors 47 Common Programming Interface for
Business Application Programming Communications. See CPIC users,
Interfaces. See BAPI integrations CPIC user name
BuyerPaymentBankLocationPull integration CompanyCodeIOComboPull integration
event 169 event 169
CompanyCodePull integration event 169
CompanyCodeWBSComboPull integration
C event 169
canceled purchase orders 24 comparison filter conditions 69
carbon copies 93 complimentary copies 93
catalog items 47 configure command 27
chain rules 111 connection information, verifying 27

Index
connection retries, verifying 33 customer models 119

connections
R/3 RFC destination 122
testing SAP 49 D
constraint rules 111 data pulls, scheduling 18
cost center data, pulling 14 data push mapping tables
cost center RFCs about 79
account assignment categories 103 sources of 80
parameter configuration 88 date formats
COST_CENTER_DAYS_PAST parameter creating CPIC users 38
88 push configuration 85
COST_CENTER_MSG_TYPE parameter 88 testing dialog users 39
CostCenterLanguagePull integration event date time stamp file
170 creating and updating 61
CostCenterPull integration event process flow and 20
about 170 DAYS_PAST parameters 90
real-time integration 129 debug CPO parameter 25
CPIC user name, verifying 32 debugging
CPIC users about 134
creating 38 CPO 25
setting up 37 enabling 134
CPO file name parameter 95 MessageBroker and 135
CPO filename parameter parameters 136
CPO. See changed purchase orders, canceled pushes 91
purchase orders RFCs 134
CSV source files 27 SAP interface and 134
currency conversion parameters TIB/Adapter for R/3 92
about 91 user accounts and 37
bank rate 89 worksheets 135
days past 90 decimal separators 38
Euro rate 89 Deletion Flag field 84
currency conversion pull 46 deletion, handling 129
currency conversion rates 91 delivered transport types, SAP 40
currency conversion RFCs 89 demo version configuration option 27
currency, decimal places for 22 Destination parameter 28
CurrencyConversionRatePull integration development classes
event 170 ABAP/4 128
custom filters, setting up for SAP 62 for IDOC 128
customer development classes, modifying 85 push configuration 85
customer distribution models. setup 37
See distribution models summary of 138
customer exit functions dialog users 39
about 72 Disable parameter 23
changing ALE/IDOC RFCs 128 display mode parameter 91
filtering 84

Index
distribution models exit RFCs

about 118 about 70
creating Ariba 119 configuring for pulls 72
generating partner profile for 119 exporting configuration data 34
distribution reference models, defined 118 extension mapping tables
DO_GET_LAST_CHANGE_DATE goods receipts 84
parameter 88 purchase orders 84
document types 93 extension structures
documentation typographic conventions xiii about 52
down payments, remittance pull and 21 adding fields to 54
duplicate goods receipts 95 example 55
duplicate purchase orders 95 names 54
push configuration and 77
extension tables
E data sources for 80
editing editing 82
extension tables 83 extrinsics 52
parameters 88
encodings, specifying 29
encrypting passwords 32 F
equality filter conditions 66 FailedOrders scheduled task 133
ERP orders 49 failures, pulling from SAP 134
ERPAllowCancel field 25 field mappings
error message information extension changing 84
purchase orders 77 push 23
receipts 78 SAP purchase order screens 78
error testing exit functions 84 field status group strings
errors about 101
purchase order push 132 viewing 103
receipt push 133 fields
recovery 131 adding to extension structures 54
system-level 133 pulling 52
ERS agreements 47 removing 84
Euro rate parameter 89 FieldStatusToAccountingFieldNameMap.csv
evaluated receipt settlements. See ERS file 103
agreements FieldStatusToAccountingFieldNameMapPull
ExampleUserPull integration event 170 integration event 170
exclusion filter conditions 68 filtering
executing ALE/IDOCs 127 ABAP 70
exit functions about 63
about 72 exit functions 84
customer 84 post-hook 72
filtering 84 post-hook suggestions 72
static 63
filtering exit function 84

Index
filters goods receipts

creating static 67 about 77
custom SAP 62 BAPI mechanism for 86
IDOC 58 changing fields 78
RFC 58 creating new 81
formatting dates 85 displaying existing 81
duplicate handling 95
extension mapping tables 84
G extensions 79
Gateway Host requirements 34 mapping 79
general ledger accounts 14 mapping fields for Ariba Buyer 83
general ledger balance sheet accounts 94 purchase orders and 80
general ledger RFCs 88 pushing 78
GENERAL_LEDGER_DAYS_PAST
parameter 88
GENERAL_LEDGER_MESSAGE_TYPE H
parameter 88 header information extension 77
GeneralLedgerLanguagePull integration header status pull 25
event 170
GeneralLedgerPull integration event 129,
170 I
GL accounts. See general ledger accounts, IBM WebSphere Business Integration
general ledger balance sheet Adapter 15
accounts IDES (International Demo Education
global company codes, setting up 123 System) 86
global instance support 14 IDOCs (Intermediate DOCuments)
global organizational units, defined 124 about 14
GlobalCompanyCodeMapPull integration development classes 128
event 170 real-time integration 115
goods receipt push functions 84 IMG (SAP Implementation Guide) 124
goods receipt push parameters 91 implementation dialog users 39
goods receipt push RFCs inclusion filter conditions 66
account assignment categories 103 initdb command 30, 49
allow duplicates parameter and 95 initialization parameter 135
configuration 82 initializing
mapping from Ariba Buyer import tables channel 30
82 repository database 30
TIB/Repository 30
inner join statements 70
integration channels
data flow 15
initializing 30
integration events and 13
RFC tables and 53
TIBCO 132

Index
integration data 17 master data

integration events defined 13
about 15 filtering 63
for Oracle 169 integrating in real time 14
scheduling 18 pulling 13, 17
Intermediate DOCument. See IDOCs RFCs 158
internal order parameter 89 materials management classification 107
internal order RFCs 89 message configuration files 15
internal orders 92 message definition files 15
InternalOrderPull integration event 170 message types, defined 118
invoice reconciliation number, Ariba 20 MessageConfiguration.table file 23
ItemCategoryPull integration event 170 messages, defined 118
metadata XML
modifying 54
J visibility condition calls and 104
java.text.DateFormat class 85 minority vendor RFCs 91
JDK (Java Development Kit) 85 MINORITY_VENDOR_USE_HEADOFFICE
joins 70 parameter 89, 91
MinorityVendorPull integration event 170
monetary characteristics
L about 91
language for texts parameter 96 parameters 91
last change date RFCs 88 setting values 113
LFA1 table 47 multilingual configurations. See global
line item information extension 77 instance
line item receiving information extension 78 multiple partitions, configuring for 29
local interfaces
about 71
declaring 56 N
local organizational units, defined 124 naming conventions, Ariba SAP objects 137
locales, specifying 29
Location 164
log files 49 O
logical systems ordering addresses, multiple 46
configuring 116 outbound logical systems, defining 117
defined 116 over receiving parameters 48
for partitions 117
outbound 117
partner profiles and 122 P
parameter use, defined 64
parameters. See individual parameter names
M Parameters.table file 35
manual payments, remittance advice and 21 partition names 125
mapping Ariba Buyer to RFC import tables partition selection values 127
82 PartitionedCommodityCodeLanguagePull

Index
integration event 170 profiles

PartitionedCommodityCodePull integration about 109
event 170 authorizations and 109
partitions configuring 122
configuring for multiple 29 CPIC user 38
starting TIB/Adapter for 35 defining 122
upper or mixed case 126 information list 172
partner functions 46 partner 122
partner profiles profile 118
configuring and defining 122 program IDs for RFC destinations, defined
generating for distribution models 119 121
passwords pulling
CPIC user 32, 38 accounting objects from SAP 104
encrypting 32 additional fields 52
example checking RFCs 142 assets 53
setting SAP 28 assignment categories 104
pattern filter conditions 69 failures from SAP 134
payment documents 21 header status of purchase orders 25
payment methods, mapping 62 integration data 17
payment terms information, pulling 19 master data 13, 17
PaymentTermsPull integration event 170 monetary characteristics 91
performance, increasing 62 ordering addresses 46
plant information 22 payment terms 19
PlantPull integration event 170 plants 56
PlantPurchaseOrgComboPull integration PO data 21
event 170 PO numbers 14
PO_PUSH_PCARDCC_DOCTYPE remittance advice 19, 60
parameter 89 schedules and 18
ports 120 selected data 70
post-hook filtering 72 tables 55
pre-filter interfaces 71 tables not defined in Ariba Buyer 56
pre-filter RFCs 75 transaction data 13, 17
privileges 38 purchase order mapping 79
process flow, remittance pull 20 purchase order push errors 132
ProcessERPHeaderStatusPull scheduled task purchase order push functions 84
25 purchase order push integration events
ProcessReceipts scheduled task 26, 133 PurchaseOrderPush 23, 171
ProcessStuckERPOrders scheduled task 133 PurchaseOrderPushBAPI 23, 171
Professional Buyer permission 132 purchase order push parameters 91, 95
PO_PUSH_DIRECTCC_DOC_TYPE 89, 93
PO_PUSH_ERP_DOC_TYPE 89, 93
PO_PUSH_ERPCC_DOC_TYPE 89, 93
purchase order push RFCs 77, 82, 89

Index
purchase order pushes R

about 21 R/3 RFC destinations
BAPI and 23 creating TIB/Adapter for 121
configuring 77 testing connection for 122
debugging 91 range filter conditions 68
duplicate POs 95 rdisp/max_wprun_time parameter 44
field mapping 23 real-time ALE/IDOC partition loading 95
titles 22 real-time clients 58
truncating amounts 22 real-time configuration, Ariba Buyer
unsupported features 86 parameters 127
purchase orders real-time integration
document types for 93 configuring 115
extension mapping tables and 84 configuring SAP for 165
handling of duplicates 95 transports 40, 43, 163
PurchaseGroupPull integration event 171 real-time loading 48
PurchaseOrderAdapterBAPI worksheet 17 real-time pulls 14
PurchaseOrderCancelPush integration event real-time single-object loading worksheets
171 125
PurchaseOrderChangePush integration event receipt pushes
171 about 26
PurchaseOrderERPHeaderStatusPull configuring 77
integration event 171 debugging 91
purchasing organization integration events duplicate receipts 95
PurchaseOrgPull 171 errors during 133
PurchaseOrgSupplierComboPull 129, 171 unsupported features 86
purchasing organizations 47 ReceiptPush integration event 171
push display mode parameter 91 receiving tolerances 48
push extension structures 77 release assumptions 109
pushing release authorities 108
amounts 22 release authority parameters 112
CPO 24 release authority RFCs 112
ERP orders 49 release authorization
goods receipts 42 about 107
large purchase orders 44 Ariba Buyer and 110
purchase order data 21 release characteristics 112
purchase orders 14 release classifications 111
purchase orders using BAPI 23 release codes
receipt tolerances 48 Ariba Buyer roles and 110
receipts 14, 26 defined 108
unsupported features 86 monetary values and 107
strategies 109
release conditions
Q
defined 108
QueryPeriod parameter 25 strategies nd 109
release groups 107

Index
release indicators, defined 108 RFCs

release procedures about 14
classifications and 111 account category 104
defined 108 ALE/IDOC destinations 121
release RFCs 112 Ariba Buyer 16
release strategies configuring 127
assumptions 107 cost center 88
defined 108 currency conversion 89
requisitions and 109 custom 57
release, defined 108 example 73
ReleaseAuthorityPull integration event 171 general ledger 88
remittance advice goods receipts push 82
defined 19 import tables 82
pulling 60 internal tables 82
remittance parameter 89 parameters 56
remittance pull pre-filter 75
about 19 release authority 112
Check Payment method and 21 remittance pull 20
configuring 61 testing connections 122
down payments and 21 user release code 112
enabling 60 vendor only 89
function module 161 roles 110
function module extension 162 runtibco command 49, 126
limitations 20 RZ10 transaction 45
process flow 20
remittance pull RFCs 20
RemittanceLocationPull integration event S
172 S_TABU_DIS authorization 63
RemittancePull integration event 20, 171 SALE transaction 117
remote function calls. See RFCs SAP R/3 version-specific transports
repository configuration 125 content of 43
retry attempts, verifying 33 delivered transport types 163
RFC destinations 121 installing 40
SAP reference number 20
SAP schema, changing 59
SAP Standard Cost Center IDOC
(COSMAS), limitation 115
SAP transport file location 40
SAP transports
about 40, 163
delivered types 40
import considerations 41
installing 40
reference 42
SAP user IDs 107

Index
SAP versions 17 static filtering

SAP, errors pushing to 132 about 63
SAP_ALL privilege 38 ZARIBATVARV table and 87
SAP_NEW privilege 38 SupplierInvoice number 20
SAPAdapterLocale parameter 29 SupplierLocationRemittanceInformationPull
SAPConnectionInfo.table file integration event 171
configure command and 29 SupplierPaymentBankLocationPull
synchronizing data 35 integration event 171
SAPConnections parameters SupplierPull integration event 129, 171
about 27 support packages 24
multiple partition configuration 29 synchronizing data 34
SAPGateway parameter 28 system parameters, receiving 48
SAPGatewayService parameter 28 system-level errors 133
SAPHost parameter 28
SAPKH46C30 support package 24
SAPKH46C42 support package 24 T
SAPLanguage parameter 28 T162K table 101
SAPPassword parameter 28 tables
SAPSystemNumber parameter 28 data sources for 80
SAPUser parameter 28 exported from SAP 53
SCC4 transaction 117 pulling 55
scheduled pulls 18 tax information 23, 47
ScheduledTask.table file 25 TaxCodeLanguagePull integration event 172
schema 59 TaxCodePull integration event 172
screen field information, modifying 78 TCURX table 22
screen field mappings 78 technical support (Ariba) xiii
screen fields 81 testing
SE11 transaction 83 dialog users 39
selection options 66 SAP connections 49
selection values 127 testing connections
server connection information, verifying 34 R/3 RFC destination 122
service line items 17, 24 runtibco command and 49
setlocale parameter 29 SAP 49
SetTrace parameter 28 SAP GUI and 50
showField method 104 TIB/Designer and 50
single-object loading worksheets 125
SM30 transaction 63, 127
SM59 transaction 121, 122
source fields, finding 82
SPERQ field 47
SPERRFKT field 47
split accounting 23
spro transaction 46

Index
TIB/Adapter for R/3 U

about 16 umodes 41, 164
client connection information for 32 under receiving parameters 48
configuration information for 34 user accounts 37
connection information for 31 user authorization profiles 109
creating RFC destination 121 user exits 72
log file 49 user release code RFC 112
running 49 UserPull integration event 172
schema information for 34 UserReleaseAuthorityPull integration event
setting up 31 172
starting 35
TIB/Designer 31
TIB/MessageBroker 14, 16 V
TIB/Repository
validation on catalog items 47
initializing 30, 31
vendor ERS tax status 47
starting 49
vendor master payment terms pull 18
TIBCO integration channel 13
vendor pull filtering 94
time-out intervals 44
vendor-only parameter 89
tolerances, receiving 48
vendor-only RFC 89
TQ04A table 47
vendors
transaction data
data 14
defined 13
restrictions on 46
pulling 13, 17
tuning performance of pulls 94
synchronizing flow 14
versions, supported 17
transactional remote function calls. See tRFC
ports
transforms 16 W
transports
about 40 WBSElementPull integration event 172
base functionality 166 WE20 transaction 122
for change/cancel orders 24 WE21 transaction 120
import considerations 164 worksheet configuration 125
installing 41, 164 worksheets
installing ALE/IDOC 125 opening 126
real-time integration 167 real-time single-object loading 125
reference 166 TIB/MessageBroker 16
SAP R/3 version-specific 167
types delivered 163
Y
version 4.6C 44, 167
version 4.7 44 YCIDOCPROC RFC destination 121
tRFC ports 120
troubleshooting 134
TVARV structure, SAP 66 Z
TYPE field 87 Z_ARIBA functions. See individual function
typographic conventions xiii names

Index
Z_ARIBA parameters. See individual Z_ARIBA_PO_PUSH RFC 89

parameter names calling function 89
Z_ARIBA RFCs. See individual RFC names mapping from RFC import tables 82
Z_ARIBA_ LANGUAGE parameter 89, 96 push extension structures and 77
Z_ARIBA_ACCOUNT_CATEGORY RFC TIB/MessageBroker and 22
89, 104 Z_ARIBA_PO_PUSH_ALLOW_DUPS
Z_ARIBA_BAPI_PO_CANCEL RFC 24 parameter 95
Z_ARIBA_BAPI_PO_CHANGE RFC 24 Z_ARIBA_PO_PUSH_BDCDATA_EXT
Z_ARIBA_BAPI_PO_CRT_ALLOW_DUP function 84
S parameter 95 Z_ARIBA_PO_PUSH_DISPLAY_MODE
Z_ARIBA_COST_CENTER RFC 88, 89 parameter
Z_ARIBA_CPO_FNAME parameter 25, 95 debugging parameters and 136
Z_ARIBA_CURR_CONV_BANK_RATE debugging pushes and 91
parameter 89, 91 ZARIBTVARV and 89
Z_ARIBA_CURR_CONV_DAYS_PAST Z_ARIBA_PO_PUSH_ERRORS_EXT
parameter 90 function 84
Z_ARIBA_CURR_CONV_EURO_RATE Z_ARIBA_PO_PUSH_EXT function 84
parameter 89 Z_ARIBA_PREFILTER RFC 75
Z_ARIBA_CURRENCY RFC 89 Z_ARIBA_PREFILTER_EXT RFC 70
Z_ARIBA_DEBUG_CPO parameter 25 Z_ARIBA_RELEASE_AUTHORITY RFC
Z_ARIBA_GENERAL_LEDGER RFC 88, 89, 112
89 Z_ARIBA_RELEASE_AUTHORITY_CNA
Z_ARIBA_GR_PUSH RFC 26, 82, 89, 92 M parameter
Z_ARIBA_GR_PUSH_ALLOW_DUPS debugging pushes 91
parameter 95 ZARIBTVARV parameters 89
Z_ARIBA_GR_PUSH_BDCDATA_EXT Z_ARIBA_REMITTANCE_BKPF
function 84 parameter 89
Z_ARIBA_GR_PUSH_DISPLAY_MODE Z_ARIBA_REMITTANCE_PULL RFC 20
parameter Z_ARIBA_TAX_CODE RFC 89
configuration 89 Z_ARIBA_UOM RFC 89
debugging pushes 91 Z_ARIBA_USER_RELEASE_CODE RFC
error handling 136 112
Z_ARIBA_GR_PUSH_ERRORS_EXT Z_ARIBA_VENDOR_ONLY RFC 89
function 84 Z_ARIBA_VENDOR_ONLY_COUNTPOR
Z_ARIBA_GR_PUSH_EXT function 84 GS parameter 89, 94
Z_ARIBA_INTERNAL _ORDER RFC 89 ZAF7 release assumptions 109
Z_ARIBA_INTERNAL_ORDER_AUART ZAF7 RFC 108
parameter 89 ZAR prefix 54
Z_ARIBA_LAST_CHANGE_DATE RFC ZAR6 data elements 146
88 ZAR6 development class
Z_ARIBA_MATERIAL_GROUP RFC 89 overview 17
Z_ARIBA_MINORITY_VENDOR RFC 89 pulls and 54
Z_ARIBA_PARAMETER RFC 64 pushes and 85
Z_ARIBA_PO_DETAILS RFC 89 SAP objects and 139
Z_ARIBA_PO_HEADER_STATUS RFC 25 ZAR6 function groups and modules 139

Index
ZAR6 message class 146 ZARIBTVARV structure

ZAR6 structures 143 parameters and 87
ZAR6 tables real-time integration and 127
pushes and 79 release authorizations and 112
SAP objects and 143 ZARIBTVARV table
ZAR7 development class 138, 154 about 16, 87
ZAR7 function group and modules 154 configuring RFC settings 64
ZAR7 structures 154 debugging CPO 25
ZAR8 development class 138 editing 63
ZAR8 function group and module 155 editing parameters 88
ZARASSET extension structure 53 field reference 64
ZARC development class pulls and 63
pulls and 70 RFC reference 158
pushes and 85 selection condition options 66
SAP objects and 146 ZARPOFMAP table 79
ZARC extension table 79 ZATC development class
ZARC function groups and modules 147 pushes and 85
ZARC structures 149 real-time integration 125
ZARGRFMAP table 79 SAP objects and 153
ZARGRFMAPX table 79 ZATC function group and modules 153
ZARIBA_CHANGEORDER development ZATCOS message type
class 155 Ariba distribution model and 119
ZARIBA_CHANGEORDER function group defining 128
and modules 155 installing ALE/IDOC transports and 125
ZARIBA_CHANGEORDER structures 156 Outbound parameters table and 123
ZARIBA_CUST_REMITTANCE ZATCRE message type
development class 161 Ariba distribution model and 119
ZARIBA_CUST_REMITTANCE dictionary installing ALE/IDOC transports and 125
structures 161 Outbound parameters table and 123
ZARIBA_CUST_REMITTANCE function partition selection values and 128
group 161 ZATGLM message type
ZARIBA_CUSTCHANGEORDER Ariba distribution model and 119
development class 157 installing ALE/IDOC transports 125
ZARIBA_CUSTCHANGEORDER function Outbound parameters table and 123
group and module 157 partition selection values and 128
ZARIBA_CUSTCHANGEORDER ZATI development class
structures 157 about 151
ZARIBA_REMITTANCE data element 160 installing ALE/IDOC transports 125
ZARIBA_REMITTANCE dictionary pushes and 85
structures 160 real-time integration 128
ZARIBA_REMITTANCE function group SAP objects and 138
160 ZATI function groups and modules 151
ZARIBTVARV default parameters 88 ZATI includes 152
ZARIBTVARV parameter descriptions 90 ZATI message class 152
ZXT extension prefix 54

Index
ZXTASSET extension structure 53

ZXTGRERR structure 78
ZXTGRITEMS structure 78
ZXTPOACCNT structure 77
ZXTPOERR structure 77
ZXTPOHEADR structure 77
ZXTPOITEMS structure 77

ARIBA, INC.
807 11th Avenue
Sunnyvale, CA 94089 USA
Telephone: 650.390.1000
Fax: 650.390.1100
www.ariba.com

ARIBA-SAP Integration

Uploaded by

Copyright:

Available Formats

ARIBA-SAP Integration

Uploaded by

Document Information

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-SAP Integration

Uploaded by

Copyright:

Available Formats

What is the purpose of this document?

What is the purpose of this document?

What SAP versions are supported for integration?

What SAP versions are supported for integration?

Ariba Buyer

SAP Integration Guide

THIRD PARTY SOFTWARE

Ariba Buyer SAP Integration Guide iii

Setting Up the TIB/Adapter Using TIB/Designer . . . . . . . . . . . . . . . 31

iv Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Pulling New Tables Into Ariba Buyer. . . . . . . . . . . . . . . . . . . . . . . . . 55

Ariba Buyer SAP Integration Guide v

vi Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Ariba Buyer SAP Integration Guide vii

ZARC Development Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

viii Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Transport Description Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Ariba Buyer SAP Integration Guide ix

x Ariba Buyer SAP Integration Guide 82en_us2004.5.12

This document describes how to integrate Ariba Buyer with SAP.

Audience and Prerequisites

W To locate the Ariba Buyer Documentation Roadmap:

Ariba Buyer SAP Integration Guide xi

Which Chapters to Read

xii Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Typeface or Meaning Example

Ariba Technical Support

Ariba Buyer SAP Integration Guide xiii

xiv Ariba Buyer SAP Integration Guide 82en_us2004.5.12

This chapter contains the following sections:

Ariba Buyer SAP Integration Guide 13

14 Ariba Buyer SAP Integration Guide 82en_us2004.5.12

TIB/Adapter for R/3

Ariba Buyer SAP Integration Guide 15

16 Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Supported SAP Versions

If you use versions 4.6C or 4.7, be aware of the following issues:

Pulling Master and Transaction Data

About Integration Data

Ariba Buyer pulls the following data from SAP:

Ariba Buyer SAP Integration Guide 17

• General ledger accounts

18 Ariba Buyer SAP Integration Guide 82en_us2004.5.12

2 The TIB/MessageBroker executes the pertinent MessageBroker worksheet

4 The TIB/Adapter communicates with an appropriate Ariba Buyer RFC on your

Pulling Payment Terms

Pulling Remittance Advice

Ariba Buyer SAP Integration Guide 19

Remittance pull is also available for:

20 Ariba Buyer SAP Integration Guide 82en_us2004.5.12

In SAP, it is possible to cancel a payment document for a specified payment, or to

For additional information on ERP considerations when pulling remittance advice,

Pushing and Pulling Purchase Orders

Ariba Buyer SAP Integration Guide 21

Adjusting Net Price

22 Ariba Buyer SAP Integration Guide 82en_us2004.5.12

Pushing Purchase Orders Using BAPI

Understanding BAPI Push Limitations

Ariba Buyer SAP Integration Guide 23

Pushing Changed and Canceled Purchase Orders