CONFIDENTIAL

2019-05

Administration and data maintenance

fundamentals
SAP Ariba Procurement solutions
© 2019 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

Topics about using the administration area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Administering your SAP Ariba cloud solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Viewing and exporting information from tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Workspaces and tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Adapter source values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Self-service site configuration parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
How to modify configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Handling custom workflows with SAP Ariba e-forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Topics about managing dashboard templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

About dashboard templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
How to view, add, modify, or delete dashboard templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
How to publish dashboard templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
How to add content items to the current dashboard tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
How to change the title and types of approvables on the current dashboard tab. . . . . . . . . . . . . . . . . . . 18
How to add new dashboard tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
How to add or modify dashboard template groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
How to adjust the ranking for applying dashboard templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
How to configure the news content item. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
How to reset a user's dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Enforcing confirmation before deleting approvables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Topics about importing, exporting, and managing data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Preparing to import data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Master data import overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Retrieving master data from your ERP system or database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Importing master data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Using the data dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
How to download the data dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Data dictionary worksheets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
How to run individual data import tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
How to run batch data import tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
How to view supported files for a batch data import task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Data import task status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
How to run data export tasks in SAP Ariba Procurement solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Data encryption in SAP Ariba Procurement solutions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Managing your master data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Administration and data maintenance fundamentals

2 CONFIDENTIAL Content
 How to add, modify, and deactivate a single object or record. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
How to add, update, or remove data with header-detail files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
How to add and modify multiple types of master data records in once batch. . . . . . . . . . . . . . . . . . . 44
How to deactivate multiple types of master data records in one batch. . . . . . . . . . . . . . . . . . . . . . . .45
IDs assigned to manually entered addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Topics about data integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Data integration using Web Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Authentication and security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Web Services workflow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Data integration tasks that support Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
How to view integration tasks that support Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
How to add service line item details to Export Change Purchase Orders. . . . . . . . . . . . . . . . . . . . . 53
How to configure an end point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
How to configure an integration task for Web Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
How to generate a WSDL file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
How to enable or disable configured integration tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
How to include custom header fields in Web Services export tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Topics about managing changes to integration events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Reviewing the data definition of export and import tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
How to manage data definition changes for export and import tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . 60
How to revert changes to the data definition of export and import tasks. . . . . . . . . . . . . . . . . . . . . . . . . 61
Reviewing data definition changes in the data dictionary or WSDL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Topics about tracking browser use in SAP Ariba cloud solutions. . . . . . . . . . . . . . . . . . . . . . . . . . 63

Tracking browser use. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
How to view users' browser information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
How to find users with unsupported browsers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
How to find users of a specific browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
How to export enterprise user browser information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Topics about privacy policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Privacy policy settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Workflow for custom privacy policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
How to configure your SAP Ariba solution to link to a custom privacy policy. . . . . . . . . . . . . . . . . . . . . . 71
Site configuration options for privacy policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Topics about CSV file formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

CSV file structure and data entry guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
CSV syntax conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
CSV character encoding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Fax number formats in CSV files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Administration and data maintenance fundamentals

Content CONFIDENTIAL 3
 Date formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Number formats in CSV files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Boolean values in CSV files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Codes for system data in CSV files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Default batch data import operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Default batch data import operations for PeopleSoft ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Default batch import operations for SAP ERP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Default batch import operations for generic ERPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Revision history. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Administration and data maintenance fundamentals

4 CONFIDENTIAL Content
Topics about using the administration area

In this section:

Administering your SAP Ariba cloud solutions [page 5]

Viewing and exporting information from tables [page 5]

Workspaces and tasks [page 6]

Adapter source values [page 9]

Self-service site configuration parameters [page 10]

Handling custom workflows with SAP Ariba e-forms [page 12]

Administering your SAP Ariba cloud solutions

You can use the administration area to set up and manage your organization's data for your SAP Ariba site.

● To show the Administration dashboard tab, log in to your SAP Ariba site and choose Manage Core
Administration from the Home tab. When SAP Ariba Procurement solutions are integrated with SAP Ariba
Strategic Sourcing solutions or an SAP Ariba reporting site, you can also view a Manage Administration
option.
● When you choose Manage Administration , the Administration dashboard tab for the remote site
appears. The administration tasks you can perform at the remote site depend on the groups you belong to. For
more information, see the SAP Ariba Procurement solutions group descriptions table.
● To return to the administration area for SAP Ariba Procurement solutions, choose Manage Core
Administration .

Viewing and exporting information from tables

When viewing search results, the data is displayed in tables. You can use different tools to change how the data is
displayed, and then export the data into a Microsoft Excel file.

The following table describes the tools for changing how the data is displayed:

Icon / Links Description

Table Options Menu Some tables provide an icon for the Table Options menu. Click the icon to display a menu of options.
icon:

Administration and data maintenance fundamentals

Topics about using the administration area CONFIDENTIAL 5
Icon / Links Description

Scroll bars Some tables provide vertical and horizontal scroll bars, as necessary, to scroll through data without
pagination. When you scroll large amounts of data, a progress bar indicates data is being loaded.

Minimize and maxi­ Some tables provide icons for minimizing or maximizing the table. You find them on the top right cor­
mize icons ner of the title bar.

Pagination controls Some tables provide horizontal arrows and a pull-down menu above the table’s column headers, for
displaying other pages of data. Click an arrow to display the previous or next page or select a page from
the pull-down menu.

Expand and collapse Some rows provide a triangle icon for expanding or collapsing rows of subcategory information.
icons

Hide Detail/Show De­ The Hide Details / Show Details toggle link allows you to display or hide details for some data, such as
tail requisition or invoice line items. You find the link on top right of the table.

Once the data has been configured to your preferences, you then have the option to export rows from the table or
the entire page into an Excel file. The following export commands are available on the Table Options menu,
accessible using the following table options icon ().

● Export All Rows exports all rows of the table, up to a maximum of 2000 rows.
● Export Current Page exports up to 50 rows, which is the maximum number of rows displayed in a page.

 Note

These commands do not export data to a CSV file that can then be used for importing data.

If the table you export includes a custom string field that contains only numerals, the resulting value in the Excel
file will be a number, not a string. Also, numbers longer than 15 digits are truncated in the Excel file.

Workspaces and tasks

Some workspaces are common to all SAP Ariba Procurement solutions, and some workspaces appear only for
specific products.

Group membership enables you to access specific workspaces and tasks. If you are member of the Customer
Administrator group, you can access most of the workspaces and tasks. If you are not a member of the Customer
Administrator group, you can access only a subset of the workspaces and tasks.

For information on the groups that can access specific workspaces and tasks, see the SAP Ariba Procurement
solutions group descriptions table.

Workspace Description Where to find more information

Site Manager Use this workspace to import and export data and Common data import and administration
view user activities. guide for SAP Ariba Procurement solu­
tions

Administration and data maintenance fundamentals

6 CONFIDENTIAL Topics about using the administration area
 Workspace Description Where to find more information

Integration Manager Use this workspace to manage the data import/ This guide (see the related information
export tasks, review and accept changes to the data below).
definition, and configure connection information for
For the cloud integration gateway capa­
connecting to external systems.
bility: SAP Ariba Cloud Integration Gate­
For sites integrated with SAP ERP, use this work­ way installation guide
space to enable the cloud integration gateway capa­
bility, which provides a self-service way to integrate
SAP Ariba solutions with ERP systems.

Customization Manager Use this workspace to: For enumerations and approver lookup
tables:Common data import and admin­
● View, upload, and download enumerations and
istration guide for SAP Ariba Procurement
approver lookup tables
solutions

 Note For site configuration options, click the

Details button on the Parameters page
You must be a member of the
Customization Administrator group to ac­ for the parameter you want to know more
cess these tasks. about.

● View and modify some of the site configuration

options, or parameters, available for your site.
SAP Ariba Procurement solutions include hun­
dreds of parameters that determine how pro­
curement and invoicing processes work. Most
parameters are accessible to SAP Ariba repre­
sentatives only, but you can control a subset of
them. We'll continue to expose more parame­
ters over time.

User Manager Use this workspace to manage users, groups, and Common data import and administration
user delegations. guide for SAP Ariba Procurement solu­
tions

Dashboard Manager Use this workspace to manage dashboard tem­ Common data import and administration
plates. A dashboard template defines the default guide for SAP Ariba Procurement solu­
dashboard tabs, content items, and layout of the tions
dashboard for new users.

Supplier Manager Use this workspace to view, add, delete, and modify Common data import and administration
suppliers. guide for SAP Ariba Procurement solu­
tions

Commodity Code Manager Use this workspace to manage ERP commodity co­ Common data import and administration
des and ERP commodity code maps. guide for SAP Ariba Procurement solu­
tions

Budget Manager Use this workspace to manage budget information. Procurement data import and administra­
tion guide
 Note
This workspace is applicable for budget checks
within SAP Ariba Procurement solutions.

Administration and data maintenance fundamentals

Topics about using the administration area CONFIDENTIAL 7
Workspace Description Where to find more information

PCard Manager Use this workspace to view, add, modify, and delete Procurement data import and administra­
purchasing cards. tion guide

Travel and expense data import adminis­

tration guide

Procure-to-Pay Manager Use this workspace to manage invoice exception Procurement data import and administra­
types, receiving types, payment methods and terms, tion guide
payment bank locations, and supplier payment in­
formation.

Tax Manager Use this workspace to manage tax data. You can use Common data import and administration
this tax data to apply and manage taxes on requisi­ guide for SAP Ariba Procurement solu­
tions, purchase orders, invoices, and invoice reconci­ tions
liation documents.
Invoicing data import and administration
 Note guide

You must be a member of the Tax Manager or

Customer Administrator groups to access this
workspace.

Invoicing Manager (SAP Ariba Invoice Management only) Use this Invoicing data import and administration
workspace to manage invoice exception types. guide

Payment Manager (SAP Ariba Invoice Management only) Use this Invoicing data import and administration
workspace to manage payment methods, payment guide
terms, payment bank locations, and supplier pay­
ment information.

Contracts Manager Use this workspace to view generated subscriptions, Procurement data import and administra­
compare generated subscription versions, and view tion guide
and email generated subscription errors.
Invoicing data import and administration
guide

Catalog Manager Use this workspace to view generated subscriptions, Procurement data import and administra­
compare generated subscription versions, view and tion guide
email generated subscription errors, and manage
Catalog administration guide for buyers
catalog kits, files, hierarchies, and views.

Travel & Expense Manager (Travel and expense only) Use this workspace to Travel and expense data import adminis­
view, modify, add, and delete expense per diem lim­ tration guide
its.

Related Information

Topics about data integration [page 47]

Topics about managing changes to integration events [page 58]

Administration and data maintenance fundamentals

8 CONFIDENTIAL Topics about using the administration area
Adapter source values
When you create, edit, or delete an object in the administration area, your changes are saved to the database.
Depending on the adapter source value for the object, your changes may be overwritten or deleted the next time
you run data import tasks.

Creating objects from adapter source values

When creating an object in the administration area, you need to choose an adapter source value.

The following table describes each of the available adapter source values:

Adapter source Description

External The object and all its data fields are maintained in an external system, such as an ERP system or a
set of CSV files. Objects with this adapter source can be overwritten or deleted when data is im­
ported from the external system.

AribaManaged The object is not maintained in an external system. Objects with this data source are maintained in
the administration area.

ManuallyMaintained The source of the object is an external system, but the object cannot be overwritten or deleted
when data is imported from the external system.

Punchin (SAP Ariba Catalog only) The source of the object is an external system (the
PunchinGroup.csv); data is imported from the CSV file by the Import Punchin Groups
data import task.

Editing objects

You can view, but not modify, the adapter source value when editing an object in the administration areas.

Objects created by SAP Ariba, such as the default user groups, have a special adapter source called SYSTEM. You
can't edit objects that have the SYSTEM adapter source.

If you attempt to edit an object that has the External adapter source, you receive the following warning message:

You have changed one or more field values in an externally managed object. These
changes will be overwritten the next time you import this data from your external
system into SAP Ariba.

If you attempt to edit an object that has the Punchin adapter source, you also receive a warning message.

Exporting objects

When running a data export task in the administration area, you choose an adapter source value or All. If you
choose an adapter source value, it exports only objects with that adapter source. If you choose All, all objects are

Administration and data maintenance fundamentals

Topics about using the administration area CONFIDENTIAL 9
exported, regardless of their adapter source. The adapter source dialog box doesn't appear for data export tasks
that export transactional data.

Self-service site configuration parameters

SAP Ariba solutions use parameters to control many aspects of site configuration.

Parameters control whether entire capabilities such as receiving are turned on and whether certain user actions
such as the ability to dispute an invoice exception is available to users. They also set certain default values such as
escalation periods.

Many site-wide settings such as company holidays or email notification configuration settings are also controlled
by parameters.

Typically, during the site setup and deployment phase,SAP Ariba project managers work with your organization's
implementation team to determine the initial site configuration based on your unique business flows and
requirements, which is then implemented by SAP Ariba Customer Support.

SAP Ariba is gradually exposing certain self-service configuration parameters to members of the Customer
Administrator group to give you more flexibility in testing configuration changes and rolling them out to your
production site.

 Caution

Before you make any changes to your site's configuration, make sure users and functional owners are aware of
any possible impact.

How to modify configuration parameters

Prerequisites

You must be a member of the Customer Administrator group to modify configuration parameters.

Context

Parameter names appear in dot notation as follows:

parameter_type.section.[subsection.]name

where:

● parameter_type indicates the type of parameter. Application parameters operate on customer site data and
are the only type of parameter available to customer self-service.

Administration and data maintenance fundamentals

10 CONFIDENTIAL Topics about using the administration area
 ● section indicates the product or module that the parameter affects. For example, parameters in the Procure
section affect purchasing features and parameters in the Invoicing section affect the invoicing module.
Parameters in the Base section typically affect the entire customer site.
● An optional subsection further defines the product or module affected by the parameter.
● name is the name of the parameter.

Parameter changes typically take effect immediately or the next time a process impacted by the parameter is run.
You cannot schedule a date or time when you want to have the parameter change to be available to users.
Therefore, plan any changes in configuration settings carefully for your production site.

 Tip

If you need more information about how specific parameters work, see the administration and business user
guides for the functional area in the help center. For example, approvable related parameters are described in
the Approval process management guide. Or use the search function in the help center to search for information
by the parameter name.

Procedure

1. Click Manage Core Administration to change parameter settings for SAP Ariba Procurement solutions
or Manage Administration to change parameters impacting SAP Ariba Strategic Sourcing solutions.

2. Click Customization Manager Parameters

3. Click List All to get a listing of all parameters available for self-service or enter any part of the parameter name
to search. For example, enter Base and click Search to see all base parameters or enter any partial text to find
parameters related to specific functionality. For example, split returns all parameter values with the string
split anywhere in the name.
4. Review the parameter settings and modify it as required. Most parameters are boolean values that enable (if
set to Yes) or disable (if set to No) certain functionalities. Other parameters take a single value, which might be
an integer or a text string. Parameters with an Edit button next to the value generally expect a list of values.
5. To enter values for parameters that expect a list of values:
a. Click Details to review the parameter description, which provides information about the expected values.
Most list values are not validated when you enter them, so it's important that you understand how to enter
these values correctly. The description on the Details page includes information where to find the source
values.
b. Enter the value you want to add into the New Entry text box and click Add. The value is added to the list of
current values.
c. For some parameters, the sequence of values in the list might be important because it determines the
sequence of execution steps or the order in which the values are displayed to the user. To reorder the list,
click the entry you want to move and then use the Move Up or Move Down button to move the entry.
d. Click OK.
6. On the Parameters page, click Save.
7. Click OK to confirm your parameter changes.

Administration and data maintenance fundamentals

Topics about using the administration area CONFIDENTIAL 11
Handling custom workflows with SAP Ariba e-forms
Your SAP Ariba solution can include custom approvables designed for your organization's specific business needs.

For example, you might require employees to get approval on a request for authorization before they can create a
purchase requisition. There are two ways to create a new type of approvable for this purpose:

● A member of the Custom Form Designer group can use the forms builder to create a form.
● You can have SAP Ariba create an eForm. SAP Aribaworks with you to create a custom design called “request
for authorization.”

SAP Ariba eForms

Buyers can have SAP Ariba create custom forms, or eForms. After SAP Ariba e-forms are published, members of
the Customer Administrator group can create a custom approval process for them. For more information about
setting up approval processes, see the Approval process management guide. Customer administrators can also
grant users access to SAP Ariba e-forms by assigning users to the specific groups for each one. For more
information on groups, see the SAP Ariba Procurement solutions group descriptions table.

All SAP Ariba e-forms have a corresponding export task, accessible by members of the Customer Administrator
group. SAP Ariba e-forms export tasks have the name Export eForm eFormName.

Custom forms created in the forms builder

The forms builder provides a fast and flexible way to extend procurement processes. Members of the Custom
Forms Designer group can create forms easily without the help of IT teams or SAP Ariba . Start with a blank design,
or choose a template your organization already created and modify it as needed. Create procurement-related
forms such as check requests, educational reimbursement requests, and expense authorizations. Design the form
using a drag-and-drop interface, add an approval flow, and configure conditions for the widgets and approvers, all
without writing any code. For more information, see the guide Buiding forms in the forms builder.

Administration and data maintenance fundamentals

12 CONFIDENTIAL Topics about using the administration area
Topics about managing dashboard templates

In this section:

About dashboard templates [page 13]

How to view, add, modify, or delete dashboard templates [page 15]

How to publish dashboard templates [page 16]

How to add content items to the current dashboard tab [page 17]

How to change the title and types of approvables on the current dashboard tab [page 18]

How to add new dashboard tabs [page 18]

How to add or modify dashboard template groups [page 19]

How to adjust the ranking for applying dashboard templates [page 19]

How to configure the news content item [page 20]

How to reset a user's dashboard [page 21]

About dashboard templates

The dashboard for new users is created from a dashboard template, which determines the dashboard tabs, content
items, and layout of the dashboard.

Following is an example of a typical dashboard:

Administration and data maintenance fundamentals

Topics about managing dashboard templates CONFIDENTIAL 13
1. Create menu
2. Manage menu
3. Recent menu
4. Search bar
5. Preferences and Logout links
6. Search and Print icons, and the Help menu
7. Configure Tabs and Refresh Content icons
8. Action tiles
9. Content items

Your configuration includes a default dashboard template, and all user dashboards are initially based on this
template. Users can customize their own dashboards.

You can use the Dashboard Templates task in the Dashboard Manager workspace to modify the default
dashboard template and create new dashboard templates.

User groups and dashboard templates

You can associate a dashboard template with a user group. When a new user belongs to a group that has an
associated dashboard template, the user’s dashboard is created from that dashboard template. Associating a
dashboard template with a group is optional.

Dashboard template rankings

Each dashboard template has an associated rank. A rank number of 1 is the highest possible rank. New users get
the dashboard template with the highest rank.

Rank determines which dashboard template a new user gets when:

● A template is associated with the user’s group and the user belongs to multiple groups
● More than one dashboard template is associated with the same group

Related Information

How to view, add, modify, or delete dashboard templates [page 15]

How to publish dashboard templates [page 16]
How to add or modify dashboard template groups [page 19]
How to reset a user's dashboard [page 21]

Administration and data maintenance fundamentals

14 CONFIDENTIAL Topics about managing dashboard templates
How to view, add, modify, or delete dashboard
templates
You can view a list of all your current dashboard templates, along with information about them. You can also add,
modify, or delete dashboard templates in the Dashboard Templates page.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Dashboard Manager Dashboard Templates to view the dashboard templates.

The following table describes the columns on the Dashboard Templates page.

Column Description

Rank The dashboard template’s rank, which can determine which dashboard template a new user gets. A rank
number of 1 is the highest possible rank.

Name The name of the dashboard template.

Creator The name of the user who created the dashboard template.

Group The user group associated with the dashboard template or None, which indicates no group association.
When a new user belongs to a group that has an associated dashboard template, the user’s dashboard is
created from that dashboard template.

State The state of the dashboard template. The possible states are:
○ Published: the template is available to users at your site
○ Editing: the template creator is editing the template

Version The version number of the dashboard template. The default version number for a new template is 0.

Actions This column contains the buttons you use to perform actions on dashboard templates:
○ Configure: Lets you add content to and edit properties for the current dashboard tab, add new
dashboard tabs, compare your dashboard template to the default settings, and revert your dash­
board template to the default settings.
○ Delete: Deletes the dashboard template.
○ Publish: Publishes the dashboard template. The Publish button is available only when the dash­
board template is in the Editing state.

The Dashboard Templates page also contains the following options:

○ New Template: Creates a new dashboard template.

○ Update Rank: Updates dashboard template rankings.

3. Click New Template to create a new template, or find the template you want to modify and click Configure for
that template.
4. Click the configuration icon () to:

○ Add content to the current dashboard tab

○ Edit properties for the current dashboard tab

Administration and data maintenance fundamentals

Topics about managing dashboard templates CONFIDENTIAL 15
 ○ Add new dashboard tabs
○ Compare your dashboard template to the default settings
○ Revert your dashboard template to the default settings
5. Click the To Do icon, and choose Required to prevent users from removing a content item.
6. Find the dashboard template you want to delete, and then click Delete.
a. Click Yes to delete the template, or No to return to the previous page without deleting the template.
7. Click Return to Administration page to return to the Dashboard Templates page where you can delete or
publish your template.

Related Information

About dashboard templates [page 13]

Dashboard template rankings [page 14]
How to publish dashboard templates [page 16]
How to add content items to the current dashboard tab [page 17]
How to change the title and types of approvables on the current dashboard tab [page 18]
How to add new dashboard tabs [page 18]
How to add or modify dashboard template groups [page 19]
How to adjust the ranking for applying dashboard templates [page 19]
How to configure the news content item [page 20]

How to publish dashboard templates

Publishing a dashboard template makes them available to users in your site.

Context

If a newly published template replaces the existing default template, new users will get the new template when they
log in. Existing users will not get the new template unless they reset their dashboards to the default settings (click
Configure Tabs, and click Revert Tab Set to Default Settings).

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Dashboard Manager Dashboard Templates .

3. Find the dashboard template you want to publish, and click Publish.

Administration and data maintenance fundamentals

16 CONFIDENTIAL Topics about managing dashboard templates
 4. Enter a message to announce the publication of the template.
5. Click Translations to enter translations in one or more of the languages supported at your site.
6. Click OK to publish the template, or Cancel to return to the previous page without publishing the template.

How to add content items to the current dashboard

tab
You add content items to the current dashboard tab to make them easily accessible.

Procedure

1. Click the configuration icon (), and click Add Content.

2. In the Add Content menu, drag and drop an item to any location on the dashboard tab. Use the blue line that
appears when you start dragging the item to position it before you drop it. You can also click an item to add it to
the right column of your dashboard tab.
3. Click Done when you have finished adding content items.
4. Click the pushpin icon in the title bar of the content item, and click Required. You can prevent users from
removing the content item from their dashboards based on the template.
5. Click Return to Administration page to return to the Dashboard Templates page.

Related Information

How to publish dashboard templates [page 16]

Administration and data maintenance fundamentals

Topics about managing dashboard templates CONFIDENTIAL 17
How to change the title and types of approvables on
the current dashboard tab
Dashboards have properties that include the title that appears on the dashboard tab (for example, “Procurement
Dashboard”), the types of approvable documents that are visible on the dashboard tab, and whether the dashboard
tab is the primary tab for approvable documents of a certain type.

Procedure

1. On the dashboard, click the configuration icon (), and click Edit Properties.
2. To change the title of the dashboard tab, enter a new title in the Title field.
3. Click Display all document types on this tab if you want all approvable document types to be visible on the
dashboard tab, or click Restrict this tab for use with specific document types if you want to choose the
document types to show on the dashboard tab.
4. If you chose Restrict this tab for use with specific document types, specify the approvable document types
you want to show on the dashboard tab:

○ Choose Available to make a document type visible on the dashboard tab.

○ Choose Primary to make this dashboard tab the main tab for documents of a certain type.
5. Click OK to save your changes, or Cancel to return to the previous page without saving your changes.
6. Click Return to Administration page to return to the Dashboard Templates page.

How to add new dashboard tabs

Adding tabs to a dashboard allows you to group related content items on their own tabs.

Procedure

1. On the dashboard, click the configuration icon () and click Add New Tab.
2. Enter a title for the new dashboard tab in the Title field.
3. Click Display all document types on this tab if you want all approvable document types to be visible on the
dashboard tab, or click Restrict this tab for use with specific document types if you want to select the
document types that will be visible on the dashboard tab.
4. If you selected Restrict this tab for use with specific document types, specify the approvable document
types you want to be visible on the dashboard tab:

○ Select Available to make a document type visible on the dashboard tab.

○ Select Primary to make this dashboard tab the main tab for documents of a certain type.

Administration and data maintenance fundamentals

18 CONFIDENTIAL Topics about managing dashboard templates
 5. Click OK to add the dashboard tab.

The new dashboard tab appears on the command bar and the Add Content menu opens.

Related Information

How to add content items to the current dashboard tab [page 17]

How to add or modify dashboard template groups

You can assign a dashboard template to a user group so that when you add new users to the group, the user’s
dashboard is created from the dashboard template you assign to the group. Similarly, you can unassign a
dashboard template from a group.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Dashboard Manager Dashboard Templates .

3. Find the dashboard template, and click Edit in the Group column.

○ To associate the dashboard template with a group, select a group from the group chooser. When a new
user belongs to a group that has an associated dashboard template, the user’s dashboard is created from
that dashboard template.
○ To disassociate the dashboard template from a group, select None from the group chooser.

How to adjust the ranking for applying dashboard

templates
You can change the rank of a dashboard template and then update dashboard template list rankings accordingly.

Context

Dashboard template rank determines which dashboard template a new user gets when a template is associated
with the user’s group, when the user belongs to multiple groups, and when more than one template is associated
with a group. The user gets the template with the highest ranking.

Administration and data maintenance fundamentals

Topics about managing dashboard templates CONFIDENTIAL 19
Your site automatically assigns the lowest rank to a new dashboard template. For example, if the lowest ranked
dashboard template is 12, a new dashboard template receives rank 13. The greater the rank number, the lower the
ranking. A rank number of 1 represents the highest possible ranking.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Dashboard Manager Dashboard Templates .

3. Find the dashboard template and enter the new rank in the Rank column.
4. Click Update Rank.

Results

The dashboard template list is reorganized in ascending order. For example, if you have only two dashboard
templates with ranks 5 and 6, their ranks change to 1 and 2 respectively.

How to configure the news content item

You can use the news content item to publish company news for users.

Prerequisites

Before you can edit the news content item, it must be added to the dashboard template you are working with.

Context

You can update the news with text, or you can configure a Really Simple Syndication (RSS) news feed. RSS is a
format for delivering web content automatically. Many news-related sites and other online publishers syndicate
content as an RSS feed that you can use.

Procedure

1. On the Home dashboard tab, click the menu icon in the News content item, and then click Edit Content.

Administration and data maintenance fundamentals

20 CONFIDENTIAL Topics about managing dashboard templates
 The Edit Company News page appears.
2. Do one of the following:

○ To enter text, choose the Text radio button.

○ To enter a web address, choose the RSS radio button.
3. Choose a language from the Edit for this language dropdown.

 Note

The language you choose must be one that is enabled on the site.

4. Do one of the following:

○ Type the text in the text box, and use the rich-text formatting toolbar to format the text.
○ Enter the URL for the RSS news feed in the text box.
5. Click Done to save your changes.

How to reset a user's dashboard

User administrators can reset a user's dashboard to match the assigned default dashboard template by clicking
the Reset Dashboard option for that user. This is helpful if the user isn't seeing the latest dashboard content.

Procedure

1. Do one of the following:

○ In SAP Ariba Procurement solutions, choose Manage Core Administration .

○ In SAP Ariba Strategic Sourcing solutions, choose Manage Administration .
○ If your site includes both SAP Ariba Procurement solutions and SAP Ariba Strategic Sourcing solutions,
choose Manage Core Administration .
2. Click User Manager, and then click Users.
3. Search for the user whose dashboard you want to reset.
4. Choose Reset Dashboard from the Actions dropdown next to that user.

Results

The next time the user logs in, the user's dashboard shows the latest content.

Administration and data maintenance fundamentals

Topics about managing dashboard templates CONFIDENTIAL 21
Enforcing confirmation before deleting
approvables

Your site can be configured so that users are always prompted for confirmation before deleting an approvable.

By default, when users attempt to delete approvables, a confirmation message is displayed, prompting users to
confirm that they want to delete the approvable. Users can edit their preferences to prevent the message from
being displayed.

If your site is configured to enforce users to confirm before deleting approvables, a confirm deletion message is
displayed to all users.

To enable this feature, please have your Designated Support Contact log a service request. An SAP Ariba Customer
Support representative will follow up to complete the request.

 Note

When this feature is enabled, the Show confirmation page before deleting a request option in the Default
Preferences page is not displayed.

Administration and data maintenance fundamentals

22 CONFIDENTIAL Enforcing confirmation before deleting approvables
Topics about importing, exporting, and
managing data

In this section:

Preparing to import data [page 23]

Master data import overview [page 25]

Retrieving master data from your ERP system or database [page 26]

Importing master data [page 27]

Using the data dictionary [page 29]

How to run individual data import tasks [page 33]

How to run batch data import tasks [page 34]

How to view supported files for a batch data import task [page 37]

Data import task status [page 37]

How to run data export tasks in SAP Ariba Procurement solutions [page 39]

Data encryption in SAP Ariba Procurement solutions [page 41]

Managing your master data [page 41]

IDs assigned to manually entered addresses [page 46]

Preparing to import data

You can import your company-specific data into SAP Ariba cloud solutions to use and manage it. Similarly, you can
also export data from your SAP Ariba site.

Before you begin the data import process, we recommend downloading the SAP Ariba site enablement files from
the help center or from SAP Ariba Connect. The enablement files provide samples and tools to help you import
data and export data.

The following table describes the SAP Ariba site enablement files.

File Description

Reference data workbook An Excel workbook that contains reference information you might need when defining
your data, such as currency codes, country codes, and locale IDs.

Sample CSV files A ZIP file that contains sample comma-separated value (CSV) files for each type of data
required by your SAP Ariba site.

SAP Ariba data transfer tool A command line utility for importing and exporting CSV files in batch mode.

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 23
File Description

Sample SQL queries If you are integrating with a PeopleSoft system, you can use these sample SQL queries to
retrieve master data from your PeopleSoft system. For more information, see Integrating
procurement and invoicing data between SAP Ariba cloud solutions and PeopleSoft ERP.

SAP transport files If you are integrating with an SAP system, you must install these SAP transports. For in­
formation on installing the SAP transports provided by SAP Ariba, see the Integrating pro­
curement and invoicing data between SAP Ariba cloud solutions and SAP ERP.

Common data

SAP Ariba Procurement solutions use master data common to all solutions as well as solution-specific master and
transactional data.

Common data (master data common to all SAP Ariba Procurement solutions)
Common data includes:

● Currency information
● Unit of measure mappings
● Accounting information
● Payment terms
● Bank information
● Purchasing units
● Groups
● User information
● Supplier information
● Commodity codes
● Tax data
● Contracts (bulk import)
● Custom relationships between files (relation entries)

Many of the CSV files for common data contain master data retrieved from your system.

For information on defining and importing common data, see the Common data import and administration guide for
SAP Ariba Procurement solutions.

Solution-specific data
Solution-specific data is data used only in specific SAP Ariba Procurement solutions.

Product-specific data includes:

● Procurement data
● Invoicing and payment data

Defining and importing product-specific data is described in the following documents:

● Procurement data import and administration guide

● Invoicing data import and administration guide
● Travel and expense data import administration guide

Administration and data maintenance fundamentals

24 CONFIDENTIAL Topics about importing, exporting, and managing data
Master data import overview
The data import process consists of three general steps: data entry, master data retrieval, and importing.

More specifically, the steps are:

1. Enter your data in CSV files.

2. Retrieve master data from your ERP system or database.
3. Import data into your SAP Ariba system.

Entering your data in CSV files

You must enter your data in CSV files. You can create CSV files in a text editor or in Excel.

When entering data in CSV files, see:

● The data dictionary for file names, column names, and detailed descriptions of the CSV files used by SAP Ariba
Procurement solutions.
● CSV file formats for file syntax conventions.
● The various import and administration guides for examples and explanations of CSV file contents.

CSV file names

In some cases, the CSV file name listed in the data dictionary differs from the name listed in the user interface and
the documentation.

Keep the following in mind when naming your CSV files:

● When you run a batch data import task using either the administration area or the SAP Ariba integration
toolkit, you must name the CSV files as shown in the data dictionary on the worksheet that defines the batch
data import task. If you use the administration area to run batch data import tasks, you can also use the View
Supported Files button to see the expected file names.
● When you run an individual data import task in the administration area, the name of the CSV file can be
anything. For example, if you are importing addresses, the name of the CSV file can be address.csv,
addresspull.csv, or any other name. The name does not have to reflect what is shown in the user interface
or the data dictionary.

Maximum file size for importing data

The maximum file size for CSV and ZIP files that you import through the administration area is 40 MB. It applies to
all SAP Ariba cloud solutions and is subject to change by SAP Ariba. The limit prevents server problems that can
occur when users upload very large files.

For information about file size limits when using the SAP Ariba integration toolkit, see the SAP Ariba cloud solutions
integration toolkit guide.

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 25
  Note

Approver lookup table CSV files have a different limit. They are limited to 100,000 lines and 10 MB. These limits
apply to all SAP Ariba Procurement solutions. If you need to have this limit increased to 30 MB, have your
Designated Support Contact log a service request. An SAP Ariba Customer Support representative will follow
up to complete the request. SAP Ariba configures the following to enable this feature on your site: PL-10144,
Increase CSV file size limit.

Related Information

Using the data dictionary [page 29]

Topics about CSV file formats [page 75]
Preparing to import data [page 23]
How to run batch data import tasks [page 34]

Retrieving master data from your ERP system or

database
You can retrieve some of the data required by SAP Ariba Procurement solutions from your ERP system or database.
This data is referred to as master data.

How you retrieve master data depends on your ERP system or database.

ERP System or Database How to Retrieve Master Data

PeopleSoft You can use the sample SQL queries provided by SAP Ariba to retrieve data from your Peo­
pleSoft system, or you can write your own queries.

SAP Use the master data pull program (ZARIBA_SSP_MASTER_DATA_PULL) to retrieve mas­
ter data from your SAP system. For more information, see the Integrating procurement and
invoicing data between SAP Ariba cloud solutions and SAP ERP.

Oracle, DB2, SQL Server You can use the DB Connector to extract master data from an ERP system database. For in­
formation on using the DB Connector, see the SAP Ariba cloud solutions integration toolkit
guide.

Country codes in telephone and fax numbers

When you extract telephone and fax numbers from your external ERP system for import into SAP Ariba, don't
include the country codes. SAP Ariba adds the country codes automatically. If you import country codes with the
telephone and fax numbers, the codes will appear twice.

Administration and data maintenance fundamentals

26 CONFIDENTIAL Topics about importing, exporting, and managing data
Country codes in sites integrated with PeopleSoft ERP

PeopleSoft uses 3-digit country codes, whereas SAP Ariba cloud solutions use 2-digit country codes. If you include
3-digit country codes in an import file (for example, TaxCodeLookup.csv), SAP Ariba cloud solutions map the
codes internally to the corresponding 2-digit codes.

SAP Ariba supports the ISO standard 2-digit and 3-digit country codes.

 Note

There are two 3-digit codes supported for Romania: ROU (the current country code) and ROM (the previous
country code).

Importing master data

After you finish entering your data in CSV files, you import it into SAP Ariba solutions by running data import tasks
in the administration area or by using the SAP Ariba data transfer tool.

● If you are importing data for the first time, want to import individual data files, or import data on an intermittent
basis only, we recommend that you run data import tasks in the administration area.
● If you are importing all data on a frequent and regular basis, we recommend that you use the SAP Ariba data
transfer tool.

For SAP and PeopleSoft integrations, you can set up the SAP Ariba data transfer tool on your SAP server to run
when the master data download is complete. The SAP Ariba data transfer tool picks up the master data CSV files
and sends them to SAP Ariba.

Data import order

We recommend that you use the Import Batch Data import task to import your data because it always runs data
import tasks in the proper order.

If you choose to import your data by running individual data import tasks, you must run the tasks in the proper
order. Some data import tasks depend on the data imported by other data import tasks. When running individual
data import tasks, keep the following general rule in mind: any object referenced in the CSV file you are currently
importing must already exist in your SAP Ariba site.

The data import and administration guides for procurement, invoicing and payment, and travel and expense data
show the order in which Import Batch Data runs individual data import tasks. You can use this information as a
guide when running individual data import tasks.

Importing translation data

You can optionally define translations for some types of procurement and invoicing data.

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 27
The following language values are supported:

● English
● French
● Italian
● Spanish
● BrazilianPortuguese
● German
● Dutch
● Danish
● Norwegian
● Swedish
● Finnish
● Bulgarian
● Croatian
● Czech
● Polish
● Hungarian
● Korean
● Russian
● Turkish
● Romanian
● Greek
● SimplifiedChinese
● TraditionalChinese
● Japanese

The languages in which you are importing translations must be enabled on your site. To enable a language, have
your Designated Support Contact log a service request. An SAP Ariba Customer Support representative will follow
up to complete the request.

You import translations after importing the data that you are translating. For example, before you can import
translations for cost center names, you must import cost center data.

To import translation data, you can use either batch or individual data import tasks. If you use batch data import
tasks, you must use the CSV file names that the batch import task expects. For information about the data
referenced by the batch data import tasks, see the data dictionary. The following batch data import tasks are for
importing translation data:

● Import ERP Master Data Translations imports translations for variant-specific master data (that is, data
specific to the SAP, PeopleSoft, or Simple Generic variant).
● Import Master Data Translations imports translations for all master data, including translations for variant-
specific master data.

You can also use individual import tasks such as Import ERP Commodity Code Translations and Import Account
Type Translations. Information about specific translation tasks is covered in the data dictionary and in the
appropriate sections of each import and administration guide. For example, for information about importing ERP
commodity code translations, see the section about importing ERP commodity codes in the Common data import
and administration guide for SAP Ariba cloud solutions.

Administration and data maintenance fundamentals

28 CONFIDENTIAL Topics about importing, exporting, and managing data
You can include multiple languages in a single CSV translation file. For example, a file for importing cost center
translations into a generic variant SAP Ariba Buying and Invoicing site might look like this:

UTF8
UniqueName,Name,Language
1000,Corporate Services,English
1000,Services d’entreprise,French
1000,Servicios corporativos,Spanish

In the preceding example, UniqueName corresponds to the UniqueName field of the cost center data that you
already imported into SAP Ariba.

 Note

Importing translations does not change the Active setting of records in the database. That is, you cannot
activate or deactivate a record by importing translation data for that record. If the CSV translation file contains
an Active column, values in the column are ignored.

The data dictionary includes information about the format of CSV files containing translations.

Additional References

● SAP Ariba cloud solutions integration toolkit guide

● Integrating procurement and invoicing data between SAP Ariba cloud solutions and SAP ERP
● Integrating procurement and invoicing data between SAP Ariba cloud solutions and PeopleSoft ERP

Using the data dictionary

The data dictionary is a Microsoft Excel workbook that contains detailed descriptions of the data import and export
tasks available for your SAP Ariba site, along with information about the structure of the CSV files you can import
and export. Refer to the data dictionary when entering data in CSV files and running data import tasks.

Data dictionary content

When you download the data dictionary, the file is generated based on the variant of your SAP Ariba site, feature
set, and group membership.

More specifically these factors are:

● The variant of your SAP Ariba site: PeopleSoft, SAP, or Generic.

● The features that are enabled on your site.
● Your group membership. That is, the data dictionary that you download includes information about the import
and export tasks that you can access in the user interface. If a particular import or export task is not available
to you in the user interface, the data dictionary that you download will not contain information about that task.

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 29
CSV files created by the SAP master data pull program

The CSV files created by the SAP master data pull program (ZARIBA_SSP_MASTER_DATA_PULL) might contain
columns that are not described in the data dictionary. Columns that are not described contain data that is not used
by SAP Ariba solutions. The data dictionary describes only data used by SAP Ariba solutions.

Related Information

Topics about CSV file formats [page 75]

How to download the data dictionary

You download the data dictionary so you can prepare definitions of your data import tasks for import into SAP
Ariba.

Procedure

1. Log in to your SAP Ariba site.

2. On the dashboard, choose Manage Core Administration .

3. Click Site Manager Data Import/Export .

4. On the Data Import/Export page, click Download Data Dictionary.
5. When the File Download dialog box appears, click Save to save the data dictionary to your local hard drive.

Data dictionary worksheets

Except for the last worksheet, each worksheet in the data dictionary describes a particular data import task.

Data import tasks are grouped together alphabetically, by type, in the following order:

● Batch data import tasks, which import multiple CSV files from a ZIP file by running multiple data import tasks,
appear first. For example, the first worksheet describes Import All Accounting Related Data, which imports all
the accounting-related CSV files.
● Header-detail data import tasks, which import header data from one CSV file and detail data from another CSV
file, appear next. For example, Import Group to Child Group Mapping imports header data (groups) from the
file GroupParentGroup.csv and detail data (group and child group mappings) from the file
GroupChildGroupMap.csv.
● Simple data import tasks, which import data from a single CSV file, appear after header-detail data import
tasks. For example, Import Account Types imports data from the file AccountType.csv.

Administration and data maintenance fundamentals

30 CONFIDENTIAL Topics about importing, exporting, and managing data
Indexes worksheet

The Indexes worksheet is an index of all the data import tasks available for the site. Click the end arrow () on the
toolbar to navigate quickly to the Indexes worksheet.

Data import tasks are listed on the Indexes worksheet in alphabetical order.

Each data import task name on the Indexes worksheet is a link to the worksheet that describes that data import
task.

Worksheets for header-detail and simple data import tasks

The worksheets for header-detail and simple data import tasks describe the columns in the CSV file (or files)
imported by those data import tasks.

The following table describes the columns that appear on worksheets for header-detail and simple data import
tasks.

Column Description

Data Import Task Name The name of the data import task as it appears in the administration area.

Task Description A description of the data import task.

Header File Name For header-detail data import tasks, this is the name of the file that contains the header data. For
simple data import tasks, this is the name of the CSV file it imports.

Detail File Name For header-detail data import tasks, this is the name of the file that contains the detail data. For
simple data import tasks, this column is blank.

File Column Name The name of a column in the CSV file.

The CSV file examples in this document identify column names with bold text. For example:

UTF8

UniqueName,Name,Description,CategoryId

Auto_Commodity_Code,Auto_Commodity_Code,,5

BENEFIT:AUTOLEASE,BENEFIT:AUTOLEASE,,75

Field Name The field in the SAP Ariba object model that corresponds to the value in the CSV file column.

Field Description A description of the value in the CSV file column.

Data Type The data type of the value in the CSV file column, for example, “Boolean.”

String Length The maximum string length, if the data in the CSV file column is a text string.

Restrictions Restrictions on the value in the CSV file column, if any.

Sample Values Examples of values you can enter in the CSV file column.

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 31
Column Description

Required Indicates whether the column is a required column (“true”) or an optional column (“false” or
blank) in the CSV file. The Required setting is not validated during import operations. The Re­
quired settings in the data dictionary are consistent with the required fields in the user interface.

You should always provide values in the following columns:

● UniqueName, which is the unique internal identifier for the object you are creating. If you
retrieved the object from an external system, this value might be the internal identifier used
in that system. It must be unique for the object type.
● Name, which is the object name as it appears on pages in the user interface and in the ad­
ministration area.
● Description, which is the object description that appears on pages in the user interface
and in the administration area.

 Note
See the entry for Allow Null in this table to understand how the Required setting affects
blank Allow Null settings.

Allow Null Indicates whether a null value is allowed in the CSV file column. “Yes” means the column can
contain null values. “No” means that at least a blank string is required (for example, ""). The
Allow Null setting is validated during import operations.

If Allow Null is blank, the value can be null only if the file column is not a required file column.
(See the entry for Required in this table.) If the file column is required, and Allow Null is blank, a
null value is not allowed. At least a blank string is required. It is the same as if Allow Null were set
to No.

Reference to Field If the value in this CSV file column refers to a value in a column in another CSV file, this is the
name of that column.

Reference to File If the value in this CSV file column refers to a value in a column in another CSV file, this is the
name of that CSV file.

Worksheets for batch data import tasks

Batch data import tasks run multiple data import tasks and import multiple CSV files. The worksheets that
describe batch data import tasks list the names of those data import tasks and CSV files. You must use the file
names specified on the batch data import worksheets. Each data import task name is a link to the worksheet that
describes that data import task.

Administration and data maintenance fundamentals

32 CONFIDENTIAL Topics about importing, exporting, and managing data
How to run individual data import tasks
Individual data import tasks import CSV files that contain a specific type of data.

Context

There are two types of individual data import tasks:

● Simple data import tasks, which import a single CSV file.

● Header-detail data import tasks, which import header data from one file and detail data from another file. For
example, Import Group to Child Group Mapping imports header data (groups) from the file
GroupParentGroup.csv and detail data (group and child group mappings) from the file
GroupChildGroupMap.csv.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Site Manager Data Import/Export .

The Data Import/Export page opens.

3. On the Import tab, find the individual data import task you want to run and click Import.

You can search for a data import task by entering its name in the text box provided and clicking Search. Search
looks in the Tasks column for the text you specify, not in the Integration Toolkit Names column.
4. For data import tasks that import data, click the radio button for the data import operation you want to
perform.
The data import operation determines exactly how the data is imported. The following table describes import
operations. If a data import task does not support a particular data import operation, that operation is not
available.

 Note

The maximum number of objects that can be removed from the database at one time is 160,000. This
number is controlled by a system parameter. If this number is exceeded, a warning message is displayed.

Operation Description

Load Creates and modifies objects using the values in the import file. If an object in the import
file doesn't exist in the database, the object is created. If an object in the import file al­
ready exists in database, it is modified using values in the import file.

Create Creates new objects in the database using the values in the import file. If an object in the
import file already exists in the database, it is not modified.

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 33
 Operation Description

Update Only Modifies existing objects using the values in the import files. If an object in the import file
doesn't already exist in the database, the object is not created.

 Note
○ If you don't want to modify an object, don't include it in any data file associated
with this import operation. Doing so can lead to inadvertent data loss, object de­
activation, or object reactivation.
○ When you import user group mappings, Update Only performs a full load for the
groups you include in the header file (UserParentGroup.csv). The map­
pings in the detail file (GroupSharedUserMap.csv) replace existing map­
pings for all the groups in UserParentGroup.csv.

Deactivate Deactivates objects. All the objects listed in the import file are deactivated in the data­
base. If you don't want to deactivate an object, don't include it in the import file.

Update Details For header-detail data import tasks, modifies details of existing objects in the database
using the values in the import files. If an element or mapping in the detail file doesn't al­
ready exist in the referenced object, it is added to the object. If an element or mapping in
the detail file already exists in the object, it is modified. No elements or mappings are re­
moved. If you don't want to modify an object, don't include it in the import files.

Remove Details For header-detail data import tasks, removes details of objects in the database based on
values in the import files. The details will no longer be referenced by the objects. If you
don't want to remove a particular detail from an object, don't include it in the import files.

5. For data import tasks that import translations, choose the language of the translation from the dropdown.
6. Enter the location of the CSV file(s), or click Browse to browse to and select the CSV file(s).

 Note

In some cases, the file name listed in the user interface differs from the name listed in the data dictionary.
When you run an individual data import task, the name of the CSV file doesn't matter; it can be anything
you want.

7. Click Run to import your data, or click Cancel to return to the previous page without importing your data.

How to run batch data import tasks

Batch data import tasks import multiple CSV files at once by running multiple individual data import tasks and
reading CSV files from a ZIP file.

Context

Import Batch Data is a special batch data import task that lets you import most of your CSV files at once, from a
ZIP file. You do not have to include all of your CSV files in the ZIP file. This feature is useful during the initial data

Administration and data maintenance fundamentals

34 CONFIDENTIAL Topics about importing, exporting, and managing data
import process, when you might want to import your CSV files in several small “batches.” To import your CSV files
in batches, group dependent CSV files together in separate ZIP files and then run the Import Batch Data data
import task multiple times.

There are also two batch data import tasks for importing translation data: Import Master Data Translations and
Import ERP Master Data Translations.

Procedure

1. Using a file compression application, such as WinZip, add the CSV files that contain your data to the archive.
The files you include in the archive depend on the batch data import task you plan to run and which files you
want to import.
2. Save the ZIP file to your local file system. If you plan to run the Import CSV Lookup Tables Used By Approval
Rules data import task, you must name your ZIP file RuleCSVHelperFiles.zip. For the other batch data
import tasks, you can name the ZIP file anything you like.
3. Log in to your SAP Ariba site.

4. On the dashboard, choose Manage Core Administration .

5. Click Site Manager Data Import/Export .

The Data Import/Export page appears.
6. On the Import tab, find the batch data import task you want to run and click Import. You can search for a data
import task by entering its name in the text box provided and clicking Search.
7. Click the radio button for the data import operation you want to perform:

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 35
 Operation Description

Full Load Creates, updates, or deactivates objects in the database using values in the import files. If an object in
a data file:
○ doesn't exist in the database, the object is created.
○ already exists in the database, it is modified using values in the import file.
○ exists in the database but does not exist in the data file, the object is deactivated in the database
if the default import operation for that CSV file is Load And Delete.

 Note
Default import operations for batch data files are not reflected in the user interface. See De­
fault batch data import operations [page 81].

○ already exists in the database and the object was previously deactivated, it is reactivated.

Some data files may update objects that were previously created by other files in the ZIP file.

 Note
If the ZIP file includes a CSV file that contains the column headers but no records, Full Load does
not deactivate all the data. For example, if the ZIP file includes a TaxCode.csv file that contains
only the character encoding row (such as “UTF-8”) and the column header row (such as
"SETID_TAX_CD_,TAX_CD,SETID,TAX_CD_DESCR_,DESCR"), Full Load does not de­
activate all tax codes. If the file contains a single tax code record, however, Full Load adds or up­
dates that tax code and deactivates all other tax codes.

Incremental Load Creates or modifies objects in the database using values in the import files. If an object in an import
file:
○ Doesn't exist in the database, the object is created.
○ Exists in the database, it is updated using the value in the import file.
○ Exists in the database and was previously deactivated, the object is reactivated.

Some data files may update objects that were previously created by other data files in the ZIP file.

8. Enter the location of the ZIP file you prepared, or click Browse to browse to and select the ZIP file.
9. Click OK to import your data, or click Cancel to return to the previous page without importing your data.

Related Information

How to view supported files for a batch data import task [page 37]
Default batch data import operations [page 81]

Administration and data maintenance fundamentals

36 CONFIDENTIAL Topics about importing, exporting, and managing data
How to view supported files for a batch data import
task
The CSV files you can include in the archive depend on the batch data import task you plan to run. You can view the
CSV files that can imported by a batch data import task.

Prerequisites

● In full loads, when the default import operation is Load And Delete, the system deactivates objects that exist in
the database but do not exist in the import file.
● Your CSV files must be named as specified on the File Contents page.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Site Manager Data Import/Export .

3. On the Import tab, find the batch data import task and click Import.
4. Click View Supported Files to display the File Contents of Multiple File Upload Task page.

If you do not want to import a particular file in the list, you can omit it from your ZIP file.
5. Click Done to return to the previous page.

Related Information

Default batch data import operations [page 81]

Data import task status

After you run a data import task, data import status information is displayed in the Status column on the Data
Import/Export page in the administration area.

To view the current status of a data import task, click Refresh Status. The following table describes the values that
can appear in the Status column.

Status Description

Completed The data was imported successfully.

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 37
Status Description

Completed (!) A warning or non-fatal error occurred when the data was imported.

Error A fatal error occurred. The data was not imported.

Viewing detailed status information

To view detailed status information, click the link in the Status column. The Details tab shows detailed status
information, including the number of records created, updated, and deleted. The History tab shows information
about past data imports.

Viewing warnings and errors

To view detailed warning or error information, click the Error or Completed (!) link in the Status column and then
click the Error Details tab.

The following table describes the columns that can appear on the Error Details tab.

Column Description

Item ID A unique ID that identifies the message.

Severity The severity of the message.

File Name The name of the CSV file in which the problem occurred.

Line Number The line number in the CSV file where the problem occurred.

Error Message A message that describes the problem.

Other Addresses Additional lines where the problem occurred, if any.

To view additional details about a message, click the Show Details link beside a message on the Error Details tab.

When you click Show Details, you'll see three additional fields of information for each message:

● The Column field identifies the field (or fields) in the CSV file where the problem occurred
● The Data Value field shows the values in those fields.
● The Field Name field is for SAP Ariba internal use.

To hide the additional fields, click Hide Details.

Controlling the appearance of the Error Details tab

You can click the table options icon to control which columns appear and how messages are grouped on the Error
Details tab. For example, to group messages by file name, choose the File Name option.

Administration and data maintenance fundamentals

38 CONFIDENTIAL Topics about importing, exporting, and managing data
Exporting messages to an Excel file

To export messages to an Excel file, click the table options icon and then choose the Export all Rows or Export
Current Page option.

Viewing status for Web Services data integration tasks

To view the status of Web Services data integration tasks, in the administration area, click the Web Service Status
tab on the Data Import/Export page in either the Integration Manager or Site Manager workspace. The tab
shows the status of all the Web Services tasks that have been run.

If no Web Services task has been run you will not find any information on this tab. You can view status information
like the number of records created, updated, or deleted. You can also view the error details (if any), as well as the
history of the Web Services integration tasks that were run.

How to run data export tasks in SAP Ariba

Procurement solutions
Data export tasks allow you to download data from SAP Ariba solutions to local files.

Context

Most data import tasks have corresponding data export tasks in the administration area. This feature enables you
to export, adjust, and re-import most data.

You should be aware of the following considerations when exporting data:

● The data in exported CSV files is always in en_US locale format, regardless of user and site default locale
settings.
● Data export tasks export all CSV file columns, including optional columns that were not included in imported
files.

 Note

File channel data export tasks do not export data in custom vector fields.

● Data export tasks do not export records that reference inactive objects. For example, if you export the
mappings between ERP commodity codes and system commodity codes, and some of the entries refer to
inactive accounts, the exported ERPCommodityCodeMap.csv file does not include records that reference the
inactive accounts. All export tasks work this way. Because you can import records that reference inactive
objects, it is possible to have a situation in which fewer records are exported than were imported.
● If you choose the All or SYSTEM adapter source when running Export Enterprise Users, internal SAP Ariba
users are exported to the CSV file.

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 39
● For security reasons, Export Users and Export Users Direct do not export the UserPCardMap.csv file.
● Numerical values in exported CSV files do not include the comma (“,”) separator.
● SAP Ariba reserves the right to append new columns at the end of the export files, or add additional files that
are created when running any data export task. Ensure that the interface to your external system is robust
enough to handle export file changes delivered in service packs or release updates of your SAP Ariba site.
Whenever SAP Ariba introduces a change to an export event, if you want your export events to incorporate the
changes, you must accept the changes to the data definition.

The following data import tasks (which import multiple CSV files) do not have corresponding data export tasks:

● Import Batch Data

● Import All Accounting Related Data
● Import Commodity Code Related Data
● Import Supplier Related Data

For information on using the SAP Ariba data transfer tool to export data, see the SAP Ariba cloud solutions
integration toolkit guide.

Procedure

1. On the dashboard, click Manage Core Administration .

2. Click Site Manager, and then Data Import/Export.
3. On the Export tab, find the data export task you want to run and click Export. You can search for a data export
task by entering its name in the text box provided and clicking Search. The search looks in the Tasks column
for the text you specify, not in the Integration Toolkit Names column.
4. Choose the adapter source of the data you want to export, or choose All to export all data, regardless of the
adapter source.

 Note

The adapter source dialog box does not appear when you export transactional data.

5. Click OK to export the data, or Cancel to return to the previous page without exporting the data.
6. After the data has finished downloading, click Open to view the contents of the file or click Save to save the file
to your local hard drive.

Related Information

Topics about managing changes to integration events [page 58]

Administration and data maintenance fundamentals

40 CONFIDENTIAL Topics about importing, exporting, and managing data
Data encryption in SAP Ariba Procurement solutions
Data encryption reduces the risk of exposure for your sensitive data that is stored in the database without reducing
application functionality or usability.

In the default configuration, data encryption is disabled. To enable this option, have your Designated Support
Contact (DSC) submit a Service Request (SR). An SAP Ariba Customer Support representative will follow up to
complete the request.

When the encryption is enabled, sensitive fields and attachments are encrypted before they are stored in the
database. There is no impact on the following functionalities:

● Full search and analytics

● PDF generation
● Inter-company collaboration
● SAP Ariba API support

SAP Ariba generates unique keys for each customer site to ensure data isolation. The fields that are encrypted
include all string fields (except primary keys, index fields, or lookup fields), attachments, and blobs. Numerical
fields, such as amounts, are not encrypted to prevent issues with the application functionality.

 Note

After the data is encrypted, it cannot be decrypted. The new data is encrypted immediately after the
encryption is enabled, but the historical data is encrypted three days after the encryption is enabled.

Managing your master data

You can update, delete and add master data by using workspaces and tasks in the administration area and by
modifying comma-separated values (CSV) files and running data import tasks from the administration area or from
the SAP Ariba data transfer tool.

We recommend using a data management system to track all your data changes. Before deleting data, you should
export the data to CSV files by running data export tasks. You can then use these CSV files to reimport your data, if
necessary. Regularly exporting data can also help you keep track of your current configuration.

About managing data using workspaces and tasks in the administration area

The administration area includes workspaces and tasks that let you maintain some of your data. You typically use
these workspaces and tasks when you need to quickly add, modify, or deactivate one or two objects.

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 41
About managing data using data import tasks

You typically run data import tasks to maintain your data when you need to add, modify, or deactivate many objects
at one time. When you run a data import task, the data import operation you choose determines whether data is
added, modified, or deactivated.

You can run individual data import tasks to add, modify and deactivate a single type of master data, such as
addresses. Or you can run batch data import tasks to add, modify, or deactivate multiple types of master data at
once, such as addresses, accounts, and users.

A simple data import task imports data from a single CSV file.

Automating master data maintenance

You can automate master data maintenance. The methods for automating maintenance depend on your
integration with SAP Ariba.

You can automate master data maintenance in the following ways:

● For SAP, you can use the SAP integration programs provided by SAP Ariba to pull master data out of the SAP
database and transfer it to CSV files at regularly scheduled intervals. For information, see the Integrating
procurement and invoicing data between SAP Ariba cloud solutions and SAP ERP.
● For PeopleSoft, you can use the sample SQL queries provided by SAP Ariba to retrieve master data from your
PeopleSoft system, or you can write your own queries. For information, see the Integrating procurement and
invoicing data between SAP Ariba cloud solutions and PeopleSoft ERP.
● You can use the DB Connector to retrieve master data from an Enterprise Resource Planning (ERP) system
database.

You can use the SAP Ariba data transfer tool with a scheduler to import data periodically from CSV files into SAP
Ariba. For information, see the SAP Ariba cloud solutions integration toolkit guide.

How to add, modify, and deactivate a single object or

record

You can use an import task to add, modify, or deactivate a single object.

Procedure

1. Create a CSV file that contains only the object you want to add.

2. On the dashboard, choose Manage Core Administration .

3. Click Site Manager Data Import/Export .

4. On the Import tab, find the individual data import task you want to run and click Import.

Administration and data maintenance fundamentals

42 CONFIDENTIAL Topics about importing, exporting, and managing data
5. To add, modify, and deactivate an object, do one of the following:

○ Click Create to add an object. Enter the location of your CSV file, and then click Run to import your data.

○ Click Update Only to modify an object. Enter the location of your CSV file, and then click Run to import
your data.

○ Click Deactivate to deactivate an object. Enter the location of your CSV file, and then click Run to import
your data.

How to add, update, or remove data with header-detail files

Adding , updating, or removing data from header-details files involves creating CSV files containing the new or
modified data.

Context

A header-detail data import task imports header data from one CSV file and detail data from another CSV file and
creates associations (or “mappings”) between that data.

Some examples of header-detail data import tasks are:

● Import User Group Mappings—updates the Group object. This task imports header data (groups) from the file
UserParentGroup.csv. and detail data (user and group mappings) from GroupSharedUserMap.csv. The
Group object has a vector field called Users, which is a vector of User objects.
● Import Supplier Location Remittance Information—updates the SupplierLocation object. This task imports
header data (supplier locations) from the file SLRemittanceInformation.csv, and detail data (remittance
locations for the supplier locations) from the file SLRemittanceInformationDetails.csv. The
SupplierLocation object has a vector field called RemittanceLocations, which is a vector of RemittanceLocation
objects.

Procedure

1. Create header and detail CSV files that contain only the data you want to add or modify.

2. On the dashboard, click Manage Core Administration .

3. Click Site Manager, and then Data Import/Export.
4. On the Import tab, find the individual data import task you want to run and click Import.
5. To add, modify, and remove details, do one of the following:

○ Click Update Details, enter the location of your CSV files, and then click Run to import your data.
○ Click Remove Details, enter the location of your CSV files, and then click Run to import your data.

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 43
How to add and modify multiple types of master data
records in once batch

To add or modify multiple types of data in a batch, you create and import a zip file that contains the CSV files with
the records you want to add or modify and then run the Import Batch Data task.

Context

Batch import tasks enable you to add, modify, and deactivate multiple records by running the Import Batch Data
task either in the administration area or by using the SAP Ariba data transfer tool.

Procedure

1. Create CSV files that contain only the records you want to add or modify.

 Note

To remove a field value from an object, you must specify a blank string (for example, "").

2. Using a ZIP program, such as WinZip, add the CSV files to the archive.
3. If you are using the administration area:

1. Choose Manage Core Administration .

2. Click Site Manager Data Import/Export .
3. On the Import tab, find Import Batch Data and click Import.
4. Click Incremental Load, enter the location of your ZIP file, and click OK to import your data.
4. If you are using the SAP Ariba data transfer tool, upload the data in incremental-load mode and specify Import
Batch Data in the -event option.

Results

The incremental data import operation creates or updates records in the database using values in the data files. If a
record in a data file:

● Does not already exist in the database, it is created.

● Already exists in the database, it is updated using the value in the import file.
● Already exists in the database and the record was previously deactivated, it is reactivated.

 Note

Some data files might update records that were previously created by other data files in the ZIP file.

Administration and data maintenance fundamentals

44 CONFIDENTIAL Topics about importing, exporting, and managing data
How to deactivate multiple types of master data records in
one batch

To deactivate multiple types of master data records in one batch, you must edit CSV files to remove only the data
you want to delete. All records you want to remain active must remain in the CSV file.

Context

Batch import tasks enable you to add, modify, and deactivate multiple types of data by running the Import Batch
Data task either in the administration area or by using the SAP Ariba data transfer tool.

Procedure

1. Remove the records you want to deactivate from your CSV files.

 Note

Make sure all the records you want to remain active are still included in the CSV files.

2. Using a ZIP program, such as WinZip, add the CSV files to the archive.
3. If you are using the administration area:

1. Choose Manage Core Administration .

2. Click Site Manager Data Import/Export .
3. On the Import tab, find Import Batch Data and click Import.
4. Click Full Load, enter the location of your ZIP file, and then click OK to import your data.
4. If you are using the SAP Ariba data transfer tool, upload the data in full-load mode and specify Import Batch
Data in the -event option.

Results

The full data import operation creates, updates, or deactivates objects in the database using values in the data
files. If a record in a data file:

● Does not already exist in the database, it is created.

● Already exists in the database, it is updated using the value in the import file.
● Already exists in the database and the object was previously deactivated, it is reactivated.
If an object in the database does not exist in a data file, it is deactivated in the database.

 Note

Some data files might update records that were previously created by other data files in the ZIP file.

Administration and data maintenance fundamentals

Topics about importing, exporting, and managing data CONFIDENTIAL 45
IDs assigned to manually entered addresses
Addresses entered in the user interface are assigned automatically generated unique names, or IDs.

When users add an address such as a supplier workspace address, supplier location, or a nonstandard (ad hoc)
address for themselves, the system-generated unique name includes a prefix that ensures uniqueness between
addresses in SAP Ariba Strategic Sourcing and Supplier Management solutions and addresses in SAP Ariba
Procurement solutions.

● Addresses created in SAP Ariba Strategic Sourcing and Supplier Management solutions include ACM in the
prefix, as in ADACM112.
● Addresses created in SAP Ariba Procurement solutions include Buyer in the prefix, as in ADBuyer112.

 Note

Prefixes for addresses entered in the user interface prior to July 2018 are simply AD, for "address."

You can see address unique names in export files that include addresses. They're also visible in the user interface
for supplier locations in SAP Ariba Procurement solutions.

Administration and data maintenance fundamentals

46 CONFIDENTIAL Topics about importing, exporting, and managing data
Topics about data integration

In this section:

Data integration using Web Services [page 47]

Authentication and security [page 50]

Web Services workflow [page 50]

Data integration tasks that support Web Services [page 51]

How to configure an end point [page 53]

How to configure an integration task for Web Services [page 55]

How to generate a WSDL file [page 55]

How to enable or disable configured integration tasks [page 56]

How to include custom header fields in Web Services export tasks [page 56]

Data integration using Web Services

SAP Ariba Web Services enable you to exchange data between SAP Ariba Procurement solutions and other
systems, such as ERP systems, for real-time data integration. Web Services are primarily for exchanging
transactional data, but you can also use Web Services to import some types of master data.

In most cases, SAP Ariba Web Services are used between SAP Ariba cloud solutions and an intermediary
Enterprise Application Integration (EAI) system that handles Web Service communication for an ERP system. For
simplicity, the term EAI system is used in this chapter to refer to either the EAI or the ERP system.

SAP Ariba Web Services use the W3C SOAP messaging framework to exchange messages over HTTP or HTTPS.
We strongly recommend that you use SAP Ariba Web Services over an HTTPS link to the EAI system.

The SAP Ariba Integration Manager generates descriptions of the SAP Ariba Web Services operations in the Web
Services Description Language (WSDL), an XML-based language. Typically, developers on the EAI system use the
WSDL descriptions when creating applications to communicate with SAP Ariba Web Services. There are numerous
software development packages that can read WSDL definitions and to create Web Service clients.

Data integration with SAP ERP systems

SAP Ariba provides end-to-end integration between SAP Ariba Procurement solutions and SAP ERP back end
systems. Integration uses SAP NetWeaver PI to act as an EAI tool to ensure that SOAP messages (Request and
Response) are exchanged between procurement solutions and the SAP back end system.

Administration and data maintenance fundamentals

Topics about data integration CONFIDENTIAL 47
The following diagram illustrates how transactions are exchanged between SAP Ariba Procurement solutions and
SAP ERP back end systems using Web Services:

Figure 1: Data integration with SAP ERP

For more information, see the Integrating procurement and invoicing data between SAP Ariba cloud solutions and
SAP ERP.

Data integration with PeopleSoft and other third-party ERP systems

To integrate SAP Ariba Procurement solutions with a PeopleSoft back end system, SAP Ariba Procurement
solutions publish a SOAP message for the required integration task. Customers need to use an EAI tool or
application that can consume this SOAP message and send an acknowledgment back as an ID or error.

Administration and data maintenance fundamentals

48 CONFIDENTIAL Topics about data integration
The following diagram illustrates how transactions are exchanged between SAP Ariba Procurement solutions and a
PeopleSoft or third-party system using Web Services:

Figure 2: Data integration with PeopleSoft and other third-party ERP systems

For more information about integration with PeopleSoft ERP systems, see Integrating procurement and invoicing
data between SAP Ariba cloud solutions and PeopleSoft ERP.

SAP Ariba Web Services integration tasks and end points

SAP Ariba Web Services provide integration tasks, or integration events, that send and receive SOAP messages. An
integration task requires an end point for the logical communication channel used by the Web Service. An end point
consists of the URL and authentication information that controls access to the end point.

There are two types of end points: inbound and outbound. Inbound end points are used when the task is initiated by
the EAI system. Outbound end points are used when the task is initiated by SAP Ariba.

Related Information

Authentication and security [page 50]

Data integration tasks that support Web Services [page 51]

Administration and data maintenance fundamentals

Topics about data integration CONFIDENTIAL 49
Authentication and security
SOAP messages can be sent using HTTP or HTTPS protocols. HTTPS provides server authentication and an
encrypted communication channel. For inbound end points, SAP Ariba always uses HTTPS. For outbound end
points, the EAI administrator can choose HTTP or HTTPS, but we strongly recommend that you use HTTPS.

In addition, SAP Ariba Web Services support the following mechanisms to provide authentication and security:

● Web Services Security (also referred to as WS-Security or WSS): An industry-defined specification for SOAP
messaging enhancements that use X.509 security certificates and public-key encryption. SAP Ariba Web
Services use WS-Security to provide message integrity and client message authentication.
● HTTP basic authentication: Provides simple authentication using a credential that consists of a user ID and
password. The authentication information is sent in the HTTP header as a basic authorization request header
field. The field has the following format:
Authorization : Basic userID:password
The userID and password are separated by a colon and then Base64 encoded. These fields are encrypted if
HTTPS is used, but are not encrypted if HTTP is used.
The user ID specified for HTTP basic authentication is used exclusively to control access to the end point. It is
unrelated to any user IDs configured for your SAP Ariba cloud solution, and we recommend using a different
user ID and password from an actual user configured for your SAP Ariba site.
Although the HTTP basic authentication mechanism provides only authentication (proof of identity) and by
itself not provide authorization (granting access to resources based on identity), the information is sent in an
HTTP authorization request header field. You could use HTTP basic authentication as part of an authorization
scheme to restrict access to different integration tasks by creating a unique end point for each integration task.
Only users with the authentication credentials for a given end point could use the end point to access the
integration task.

 Note

The WS-Security and HTTP basic authentication options do not provide message confidentiality. If you use
HTTP instead of HTTPS, your data is sent in clear text, even if you use WS-Security and HTTP basic
authentication.

Web Services workflow

The web services workflow involves planning your configuration, understanding EAI systems’ access and security
information, creating endpoints, enabling integration tasks, and generating appropriate WSDL.

1. Plan your configuration by determining:

○ The integration tasks you want to use and the types (inbound or outbound) of end points needed.
○ The type of security mechanisms (WS-Security or HTTP Basic Authentication) for your end points. You
must configure at least one form of security for a given end point. You can also configure both forms of
security for a given end point.
○ How many end points you will configure. You can specify only one end point per integration task, but you
can use an end point for multiple integration tasks.
You can configure only one peer certificate for WS-Security and one set of HTTP authentication credentials
for a given inbound end point. If multiple external systems will connect to an inbound end point, all EAI

Administration and data maintenance fundamentals

50 CONFIDENTIAL Topics about data integration
 systems connecting to the end point must use the same certificate and/or HTTP credentials. (If EAI
systems will use different integration tasks, you can create a different end point for each task.)
2. Collect access and security information from the EAI systems.
3. Create the end points using the Integration Manager End Point Configuration task.
4. Enable the integration tasks and link them to end points using the Integration Manager Integration
Configuration task.

 Note

To administer or configure integration tasks and end points, you must be a member of the Customer
Administrator or Integration Admin group.

5. Generate the WSDL for each integration task, and use the WSDL file on the EAI system to build the appropriate
SOAP requests and process replies.

Data integration tasks that support Web Services

Several integration tasks for import and export support Web Services.

The following integration tasks are supported for transactional data:

● Export Purchase Orders

● Export Change Purchase Orders
● Export Cancel Purchase Order
● Export Advance Payments
● Export Cancel Advance Payments
● Export Expense Reports (SAP and PeopleSoft variants only)
● Export Payment Requests
● Export Receipts
● Import Purchase Order Header Status (SAP and PeopleSoft variants only)
● Import Remittance
● Import Requisitions
● Import Receipts from External Systems

 Note

You need to add the ServiceLineItemDetails [page 53] field to the Export Change Purchase Orders web
service because it isn't included by default.

Master data integration with SAP systems

In SAP variants, you can configure some master data import tasks to use Web Services.

Administration and data maintenance fundamentals

Topics about data integration CONFIDENTIAL 51
Master data Integration task name

Company code Import Company Codes

General ledger Import General Ledgers

Cost center Import Cost Centers

Purchase organization Import Purchase Organizations

Supplier Import Suppliers

Master data integration with PeopleSoft systems

In PeopleSoft variants, you can configure some master data import tasks to use Web Services.

Master data Integration task name

SetID Import SetIDs

Supplier Import Suppliers

Master data integration with other third-party systems

In generic variants, you can configure some master data import tasks to use Web Services.

Master data Integration task name

Procurement unit Import Purchasing Units

Supplier Import Suppliers

How to view integration tasks that support Web Services

To determine which integration tasks support Web Services, you can view a list of enabled and disabled tasks.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Integration Manager Integration Configuration .

3. Choose Web Service from the Format menu, and choose the Enabled and Disabled check boxes.
4. Click Search.

Administration and data maintenance fundamentals

52 CONFIDENTIAL Topics about data integration
How to add service line item details to Export Change
Purchase Orders

You need to add the ServiceLineItemDetails field to the Export Change Purchase Orders web service
because it isn't included by default.

Procedure

1. SAP Ariba Customer Support uploads the following standard customization:

xml: <inClass name="ariba.purchasing.core.POLineItem">

<inFieldname="ServiceLineItemDetails">
<templates> <template name="TransactionExportableField" operator="add"/></
templates>
</inField>
</inClass>

For information about standard customizations, see the Ariba dForm and eForm Design Guide.

2. On the dashboard, choose Manage Core Administration .

3. Click Integration Manager Integration Configuration .

4. Click Actions > Edit for the Export Change Purchase Orders task.
5. Click ViewWSDL beside the Name field.
6. Close the WSDL file, and then click Save on the Edit data import/export page.

7. Choose Manage Core Administration .

8. Click Integration Manager Data Definition .

9. Click Actions > Review for Export Change Purchase Order.
10. Click Accept Changed Fields, and then click Publish all Changes.

How to configure an end point

You need to create one end point for an integration task. An integration task requires an end point for the logical
communication channel used by the Web Service.

Prerequisites

In order to configure end points, you need to gather access and security information about the EAI system you plan
to interact with.

Administration and data maintenance fundamentals

Topics about data integration CONFIDENTIAL 53
Gather the following access and security information about the EAI system:

● If you are configuring an inbound end point with WS-Security, get a copy of the EAI system’s certificate. The
certificate must be a signed X.509 certificate encoded using Privacy Enhanced Mail (PEM) Base64-encoding.
The first line of the certificate must be the following text:
-----BEGIN CERTIFICATE-----
The last line of the certificate must be the following text:
-----END CERTIFICATE-----
● If you are configuring an outbound end point, get the URL for the EAI system.
● If you are configuring an outbound end point with HTTP basic authentication, get the user name and password
required to access the EAI system.

Context

An end point consists of the URL and authentication information that controls access to the end point. Each
integration task may only have a single end point, but multiple integration tasks can use the same end point.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Integration Manager End Point Configuration .

3. Click Create New.
4. In the Name field, enter a name for the end point.
5. Choose the type of end point: Inbound or Outbound.

 Note

Inbound end points are used when the task is initiated by the EAI system. Outbound end points are used
when the task is initiated by SAP Ariba.

6. If this is an inbound end point and you are using WS-Security, paste the contents of the certificate file from the
EAI system in the Certificate File field under Web Services Security.
7. If this is an outbound end point, you'll see a URL field. Enter the URL for the endpoint on the EAI system.
8. If this is an outbound end point, the Web Services Security area displays the contents of the SAP Ariba
certificate. To enable WS-Security, choose Yes in the Sign with Ariba Private Key field.
9. Copy the certificate, beginning with the line -----BEGIN CERTIFICATE----- and ending with the line -----
END CERTIFICATE-----. Provide this certificate to the administrator on the EAI system.
10. To use HTTP Basic Authentication, navigate to the HTTP Authentication area. Enter the user ID in the Login
field and the password in the Password fields. If this is an inbound end point, provide this information to the
administrator on the EAI system. If this is an outbound end point, this information must match the data
configured on the EAI system.
11. Click Save.

Administration and data maintenance fundamentals

54 CONFIDENTIAL Topics about data integration
How to configure an integration task for Web
Services
When you configure an SAP Ariba Web Services integration task, you link the task to an end point.

Prerequisites

If no end points have been defined, you must first create an end point [page 53] before configuring the integration
task.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Integration Manager.
3. Click List All or enter search criteria, and then click Search to find the task you want to configure.
4. Choose Actions > Edit for the task to open the Edit data Import/export task page.
5. Choose Web Service from the Format field dropdown.
6. Choose Enabled in the Status field.
7. Choose an end point from the End point dropdown.
8. Click Save.

How to generate a WSDL file

After you configure an integration task, you need to generate a WSDL file to use with your EAI to build the
appropriate SOAP requests and process replies.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Integration Manager Integration Configuration .

3. Click List All or enter search criteria, and then click Search to find the task.
4. Choose Actions > Edit for the task.
5. Click View WSDL.

Administration and data maintenance fundamentals

Topics about data integration CONFIDENTIAL 55
Results

A new window opens with the WSDL contents. Use your browser to save the contents to a file. The descriptions for
each field in the WSDL are provided in the WSDL itself. The WSDL also includes the URL for the end point.

How to enable or disable configured integration

tasks
When an integration task is configured for Web Services, you need to enable it before you can use it. Similarly, you
can disable an integration task that is currently enabled.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Integration Manager Integration Configuration .

3. Use the search filters to find the task you want to enable or disable.
4. From the Actions menu for the task, choose Enable or Disable.

Related Information

How to configure an integration task for Web Services [page 55]

How to include custom header fields in Web Services

export tasks
You can include custom header fields in all Web Services export tasks or for individual export tasks.

Context

By default, custom header-level fields are not included in Web Services exports, even though they are included in
the CSV file for file channel exports. You can change this behavior for all Web Service export events.

Administration and data maintenance fundamentals

56 CONFIDENTIAL Topics about data integration
SAP Ariba can configure your site to include custom header fields in all Web Services export tasks by setting a
parameter. Have your Designated Support Contact submit a service request to set the
Application.Messaging.EnableComplexNestedCustomField parameter to Yes for your site.

If you need to limit the inclusion of custom header fields to a specific export task, SAP Ariba can set a special
integration event parameter (a message configuration parameter) for the task by applying a data fix to your site.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Integration Manager End Point Configuration , and then configure an end point for outbound
tasks.

3. Click Integration Manager Integration Configuration .

4. Search for the export task in which you want to include custom header level fields, click Actions > Edit.
5. Choose the Enabled radio button if it's not already selected for the Status field.
6. Choose Web Services from the Format pull-down menu.
7. Associate the task with the outbound end point.
8. Click Save.
9. To apply the required data fix to your site, have your Designated Support Contact log a service request to have
an SAP Ariba Customer Support representative follow up to complete the request. The data fix involves turning
on the EnableComplexNestedCustomField message configuration parameter for the export task you
configured.

Administration and data maintenance fundamentals

Topics about data integration CONFIDENTIAL 57
Topics about managing changes to integration
events

When SAP Ariba introduces new fields for integration events that require you to modify your existing events,
members of the Integration Admin and Customer Administrator groups can manage and absorb these changes.

SAP Ariba cloud solutions export transactional data to be used in third-party ERP or legacy systems. Similarly, they
import transactional and master data from ERP or legacy systems. These exports and imports (also called
integration events) are done through the file channel or the Web Services channel.

SAP Ariba may introduce new fields in integration events as a part of a new release, service pack, or hot fix, to
support newer workflows and to send more information to ERP or legacy systems. Any change to the data
definition (for example, a new field introduced in an export task) or to the field order has the potential to break the
integration of these exports to your ERP or legacy systems.

To solve this potential problem, you can review the field changes made to integration events, and if desired, accept
the changes. This ensures that the data definition changes that SAP Ariba makes won't incorporated into your data
imports or exports until you explicitly accept those changes. This process of explicitly accepting changes to
integration events applies to new custom fields as well. That is, the SAP Ariba doesn't include any new custom
fields in an integration event until you explicitly accept the changes to the event.

 Note

If you choose not to accept changes for an integration event, you can't add new custom fields. You either need
to accept all the fields (custom fields and new standard SAP Ariba fields) or accept nothing. You don't have the
option to accept only new custom fields.

After accepting changes to the data definitions, if needed, you can revert to the previously accepted data definition.

For the Web Services channel, you also review changes to imports because all documents must adhere to the
WSDL for the event regardless of whether they are import or export tasks. For the file channel, you don't review
changes to imports because import integrations in SAP Ariba cloud solutions don't rename import fields and are
able to handle extra and incorrect fields.

 Note

You can't review changes for the following Excel exports:

● Sourcing projects
● Supplier profile questionnaires

Backward compatibility

Some file channel data export tasks aren't compliant with the data definition review and have been replaced. If you
are using one of these old tasks, you need to transition to the new versions.

Administration and data maintenance fundamentals

58 CONFIDENTIAL Topics about managing changes to integration events
The following table lists the old tasks and their replacements:

Old Replacement SAP Ariba cloud solu­ Integration chan­

data export task data export task tion nel ERP variant

Export Vendor Master File Export Vendor Master File v2 SAP Ariba Procure­ File channel All ERP var­
ment solutions iants

Export Suppliers Export Suppliers v2 SAP Ariba Procure­ File channel SAP ERP
ment solutions

Export Tax Code Lookups Export Tax Code Lookups v2 SAP Ariba Procure­ File channel SAP ERP
ment solutions

Reviewing the data definition of export and import

tasks
You access the Data Definition area of the Integration Manager workspace to see whether there are changes to
the fields involved in data export or import tasks.

The tasks with changes are listed at the top of the page and show a status of Changed.

1. Data export tasks with changes.

2. Choose the Review command.

Each integration event has an Actions menu. The commands in the menu vary depending on the status of the
event.

The Actions menu includes the following option:

Option Description

View View the data definition for integration events that have no changes (available only for events
that are using the latest data definition).

Review Review the changes and accept them if necessary (available only for tasks that have changes
that you haven't accepted).

Revert Revert the changes you have accepted (available only if a previous version of the data defini-
tion exists). You can only revert to the most recently accepted version.

Administration and data maintenance fundamentals

Topics about managing changes to integration events CONFIDENTIAL 59
Choosing the Review option opens a page that lists the files involved in the integration event (for file channel
events) or the groups involved (if it is a Web Services integration task). If the data definition has changed in any of
the files or groups, the file or group has a status of Needs Review.

You choose a file or group to see its data definition, and you can view any changes by comparing the Current Field
and New Field columns. The New Field column shows all unchanged fields as well as any new fields. Any field that
was removed is shown in the Current Field column and isn't shown in the New Field column.

Clicking the Accept Changed Fields button accepts changes to the set of fields that you are reviewing. After
accepting all data definition changes, clicking the Publish All Changes button incorporates all of the accepted
changes into the data export or import task.

How to manage data definition changes for export

and import tasks
You review and accept the changes to the data definition in order to update the fields that are included in your
integration events.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Integration Manager Data Definition .

3. On the Data Definition page, choose Actions > Review for a data export or import task in Changed status.
4. Choose the CSV file name (if it is a file channel event) or group name (if it is a Web Services integration task) in
Needs Review status.
5. Review the changes.

 Tip

The New Field column shows the new data definition.

6. Do one of the following:

○ To accept the changes, click Accept Changed Fields.

○ To reject the changes, click Exit.
7. Repeat steps 3 through 6 for all files or groups with changes.
8. After accepting all changes in the data export or import task, click Publish All Changes, and then click OK in
the confirmation dialog box to incorporate the changes into the data export or import task.

 Note

You must accept all the changes to the data export or import task in order for any of the changes to take
effect.

Administration and data maintenance fundamentals

60 CONFIDENTIAL Topics about managing changes to integration events
Related Information

How to revert changes to the data definition of export and import tasks [page 61]

How to revert changes to the data definition of

export and import tasks
You can undo accepted changes to the most recent version of a data export or import task for which you previously
accepted changes.

Procedure

1. On the dashboard, choose Manage Core Administration .

2. Click Integration Manager Data Definition .

3. On the Data Definition page, choose Actions > Revert for the data export or import task.
4. Choose the CSV file name (if it is a file channel task) or group name (if it is a Web services integration task) in
Needs Review status.
5. Click Accept Changed Fields to revert changes.
6. Repeat steps 3 through 5 for all files or groups with changes to be reverted.
7. After accepting all the changes to revert, click Publish All Changes, and then click OK in the confirmation
dialog box to restore the data export or import task to its previous state.

 Note

You must revert all changes to the data export or import task for any of the changes to be reverted.

Reviewing data definition changes in the data

dictionary or WSDL
You can review the data definition changes in the data dictionary or WSDL, depending on your configuration.

Data dictionary (file channel only)

The data dictionary reflects the data definition for each file channel integration event. On the Data Definition page
you can see a list of data definition fields indicating if any have changed.

Administration and data maintenance fundamentals

Topics about managing changes to integration events CONFIDENTIAL 61
You can download the data dictionary for an event in Excel format by clicking the Download Data Dictionary link on
the Data Definition page. The Excel file lists task names, task descriptions, data file name, [current] file column
names, new column file names and field names.

The data dictionary uses the following colors to represent different types of fields:

● Deprecated column names and fields are displayed in red.

● Proposed new column names and fields are displayed in green, indicating what the new data definitions would
be if you accept the changes.
● The data definitions for column and field names in black remain unchanged.

WSDL (Web Services only)

You can preview what the contents of the WSDL would be if you accepted the data definition changes. To get the
WSDL with the latest data definition, add the latest=true parameter to the URL used to get the WSDL.

For example:

http://s1-integration.ariba.com/Buyer/soap/realm/event?wsdl&latest=true

Where:

● realm is your site name

● event is the data export or import task name

This generates the WSDL as it would appear if you accepted all of the data definition changes for this event.

Administration and data maintenance fundamentals

62 CONFIDENTIAL Topics about managing changes to integration events
Topics about tracking browser use in SAP Ariba
cloud solutions

Tracking browser use

Buyers using SAP Ariba Procurement solutions and SAP Ariba Strategic Sourcing solutions can track which
browsers their users are using.

 Note

Browser tracking does not apply to Ariba Network.

In SAP Ariba Procurement solutions and SAP Ariba Strategic Sourcing solutions, administrators can quickly find
out which browsers users are using and whether those browsers SAP Ariba supports.

User administrators and SAP Ariba Customer Support often need to know which browsers users are using.
Browser information is helpful for troubleshooting issues. Also, as browser vendors stop supporting previous
versions of their browsers, SAP Ariba in turn considers whether to continue to support those versions. Knowing
which browsers are in use helps SAP Ariba work with customers on browser support issues, enabling
administrators to prepare for changes. Administrators can find out which users are using browsers that SAP Ariba
no longer supports.

SAP Ariba solutions track a user's browser whenever the user logs in. Administrators can view the browser
information on the Users page in the User Manager workspace of the administration area. They can use the
browser information in search criteria and can export users' browser information to an Excel file.

The Users page includes the following optional columns to display and to use as search criteria:

● Last Browser Used: The name and version of the browser with which the user last logged in to the SAP Ariba
solution.
● Browser Is Supported: Indicates whether the last browser used is a browser supported by SAP Ariba. Possible
values are Yes and No.

Related Information

How to view users' browser information [page 64]

How to find users with unsupported browsers [page 65]
How to find users of a specific browser [page 66]
How to export enterprise user browser information [page 67]

Administration and data maintenance fundamentals

Topics about tracking browser use in SAP Ariba cloud solutions CONFIDENTIAL 63
How to view users' browser information
In SAP Ariba Procurement solutions and SAP Ariba Strategic Sourcing solutions, administrators can display users'
browser information in search results on the Users page of the administration area.

Prerequisites

Users who belong to the Customer Administrator or User Administrator group can perform this task.

Context

Browser information includes the name and version of the browser that the user last used to log in to the SAP Ariba
solution and whether that browser SAP Ariba supports.

Procedure

1. Go to the administration area by performing one of the following actions:

○ For SAP Ariba Procurement solutions or on suite-integrated sites, click Manage Core
Administration .
○ For SAP Ariba Strategic Sourcing solutions, select Manage Administration .
2. Click User Manager, and then click Users.
3. Click the Table Options icon , and select Last Browser Used.
4. Click the Table Options icon , and select Browser Is Supported.

Results

The search results table includes columns for the fields you selected. When you search for users, their browser
information is displayed in search results.

Next Steps

After you display users' browser information, you can export the information to an Excel file by clicking the Table
Options icon  and selecting Export to Excel Export all Rows .

Administration and data maintenance fundamentals

64 CONFIDENTIAL Topics about tracking browser use in SAP Ariba cloud solutions
Members of the Customer Administrator group can use the Export Enterprise User Browser Information data
export task to export browser information for all users [page 67] into a CSV file.

Related Information

How to find users with unsupported browsers [page 65]

How to find users of a specific browser [page 66]
How to export enterprise user browser information [page 67]

How to find users with unsupported browsers

In SAP Ariba Procurement solutions and SAP Ariba Strategic Sourcing solutions, administrators can find out which
users are using browsers that SAP Ariba cloud solutions don't support.

Prerequisites

Users who belong to the Customer Administrator or User Administrator group can perform this task.

Context

You can base your search on all unsupported browsers, regardless of the brand, or you can search based on
unsupported versions of a specific brand.

Procedure

1. Go to the administration area by performing one of the following actions:

○ For SAP Ariba Procurement solutions or on suite-integrated sites, click Manage Core
Administration .
○ For SAP Ariba Strategic Sourcing solutions, click Manage Administration .
2. ClickUser Manager, and then click Users.
3. If the Search Filters section does not include browser-related fields, follow these steps to add filters:
a. Click Add/Remove Search Filters.
b. (Optional) To search based on a specific brand of browser, select Last Browser Used.
c. Select Browser Is Supported.

Administration and data maintenance fundamentals

Topics about tracking browser use in SAP Ariba cloud solutions CONFIDENTIAL 65
 d. Click OK.
4. (Optional) In the Last Browser Used field, enter the name of a browser, such as Chrome.
5. In the Browser Is Supported field, select No.

Entering No in this field finds users who used an unsupported browser the last time they logged in to the SAP
Ariba solution.
6. Click Search.

Results

The search results table lists all users who last logged in with a browser version that the SAP Ariba solution doesn't
support.

Related Information

How to find users of a specific browser [page 66]

How to export enterprise user browser information [page 67]

How to find users of a specific browser

In SAP Ariba Procurement solutions and SAP Ariba Strategic Sourcing solutions, administrators can find out which
users are using a given browser and browser version for accessing the solutions.

Prerequisites

Users who belong to the Customer Administrator or User Administrator group can perform this task.

Procedure

1. Go to the administration area by performing one of the following actions:

○ For SAP Ariba Procurement solutions or on suite-integrated sites, click Manage Core
Administration .
○ For SAP Ariba Strategic Sourcing solutions, click Manage Administration .
2. ClickUser Manager, and then click Users.

Administration and data maintenance fundamentals

66 CONFIDENTIAL Topics about tracking browser use in SAP Ariba cloud solutions
 3. If the Search Filters section does not include the Last Browser Used field, follow these steps to add a filter:
a. Click Add/Remove Search Filters.
b. Select Last Browser Used, and click OK.
4. In the Last Browser Used field, enter the name of the browser you want to search for.

You can include a version number, too. For example, you can search for Chrome 47.
5. Click Search.

Results

The search results table lists all users who last logged in with the browser you specified.

Related Information

How to export enterprise user browser information [page 67]

How to export enterprise user browser information

Steps for exporting information about the browsers users are using to access SAP Ariba Procurement solutions
and SAP Ariba Strategic Sourcing solutions.

Prerequisites

Members of the Customer Administrator group can perform this task.

Context

The Export Enterprise User Browser Information data export task exports information about the browsers used
for accessing SAP Ariba cloud solutions. Information includes the last browser (name and version) used by each
user and whether that browser SAP Ariba cloud solutions support it.

Administration and data maintenance fundamentals

Topics about tracking browser use in SAP Ariba cloud solutions CONFIDENTIAL 67
Procedure

1. On the dashboard, click Manage Core Administration .

2. Choose Site Manager Data Import/Export .

3. On the Export tab, find and run the task Export Enterprise User Browser Information.

Results

The task exports browser information to a CSV file called SharedUserBrowserExport.csv.

Administration and data maintenance fundamentals

68 CONFIDENTIAL Topics about tracking browser use in SAP Ariba cloud solutions
Topics about privacy policies

In this section:

Privacy policy settings [page 69]

Workflow for custom privacy policies [page 70]

How to configure your SAP Ariba solution to link to a custom privacy policy [page 71]

Site configuration options for privacy policies [page 73]

Privacy policy settings

You can configure the Privacy Statement popup that appears at first login. The popup can link to the SAP Ariba
Privacy Statement or your organization's custom privacy policy, or you can omit the privacy policy link and consent
prompt altogether.

SAP Ariba provides this feature to offer customer administrators more control over privacy-related messaging
presented to users, because there are varying regional legal approaches to privacy statements and consent
requirements.

There are three options for linking to privacy policies in the Privacy Statement popup users see when they first log
in.

● Keep the default link to the SAP Ariba Privacy Statement, requiring users to consent to the statement.
● Replace the SAP Ariba Privacy Statement link with a a link to your organization's privacy policy, requiring users
to consent to the policy.
● Omit the privacy policy link, and don't require users to accept a privacy statement when they first log in.

Privacy policy options are controlled by site configuration parameters, accessible in Ariba Administrator under
Customization Manager Parameters .

Tracking user consent to privacy policies

The audit log records user consent to privacy policies, including the version number of the policy and whether the
policy was a custom privacy policy or the SAP Ariba Privacy Statement.

When users download information about their user record (under Preferences), the resulting TXT file lists the most
recent privacy policy consent information.

Administration and data maintenance fundamentals

Topics about privacy policies CONFIDENTIAL 69
Related Information

Workflow for custom privacy policies [page 70]

How to configure your SAP Ariba solution to link to a custom privacy policy [page 71]
Site configuration options for privacy policies [page 73]

Workflow for custom privacy policies

The following steps illustrate what happens when your SAP Ariba solution links to a custom privacy policy instead
of the SAP Ariba Privacy Statement.

1. A member of the Customer Administrator group configures the SAP Ariba solution to link to the organization's
privacy policy instead of the SAP Ariba Privacy Statement.
2. A user logs in to the SAP Ariba solution.
3. A privacy notice popup opens. It includes a link to the custom privacy policy and a checkbox prompting the
user to consent to the policy.

Figure 3: Custom privacy notice popup

4. The user clicks the checkbox to consent to the privacy agreement.

5. The audit log records the user's consent to the agreement. The audit log specifies the URL of the agreement
and which version of the agreement the user consented to. (The version is tracked in a parameter set by the
Customer Administrator.)
6. The link to the SAP Ariba Privacy Statement no longer appears at the bottom of every page of the solution.

Administration and data maintenance fundamentals

70 CONFIDENTIAL Topics about privacy policies
 7. When users download their preferences using the Download preferences option, the resulting TXT file lists the
most recent privacy policy consent information.
8. If a customer administrator changes the version of the privacy policy or switches back to the SAP Ariba Privacy
Statement, users are prompted to consent to the latest privacy policy.

 Note

If you link your site to your organization's privacy policy, and your organization changes that policy, make
sure to increment the version specified by the parameter
Application.User.CustomPrivacyAgreement.Version. Changing the version number causes the
privacy notice popup to prompt users to consent to the policy again.

If a customer administator configures the site to omit a privacy policy link, the popup shown at first login
doesn't include a link or a consent checkbox.

Related Information

How to configure your SAP Ariba solution to link to a custom privacy policy [page 71]
Site configuration options for privacy policies [page 73]

How to configure your SAP Ariba solution to link to a

custom privacy policy
Use site configuration parameters to have the Privacy Statement popup display a link to your organization's
custom privacy policy instead of the SAP Ariba Privacy Statement, or eliminate the link entirely.

Prerequisites

You must be a member of the Customer Administrator group to perform this task.

Obtain the URL for your organization's privacy policy.

Context

The Privacy Statement popup appears when users log in for the first time. After that, it appears whenever the
version of the policy is incremented or whenever you switch to a different policy option. The popup prompts users
to agree to the privacy statement unless you choose to omit the privacy policy link entirely.

Administration and data maintenance fundamentals

Topics about privacy policies CONFIDENTIAL 71
Procedure

1. From the dashboard, perform one of the following actions:

○ For SAP Ariba Procurement solutions, or if your site integrates SAP Ariba Procurement solutions with SAP
Ariba Strategic Sourcing and Supplier Management solutions, choose Manage Core
Administration .
○ If your site includes only SAP Ariba Strategic Sourcing and Supplier Management solutions, choose
Manage Administration .

2. Choose Customization Manager Parameters .

3. In the Parameter Name or Value search box, enter Application.User.
4. Set the following parameters as shown.
○ Application.User.PrivacyStatementOptions: Move CustomPolicy to the top of the list using the
buttons provided. The option at the top of the list is the one that's used.

 Note

To omit all links to a privacy policy, set Application.User.PrivacyStatementOptions to None,

and ignore the other parameters.

○ Application.User.CustomDataPolicyURL: Enter the URL to your organization's privacy policy.

○ Application.User.CustomDataPolicyName: Enter the display text for the URL link, for example, KST
Organization Privacy Statement.
○ Application.User.CustomPrivacyAgreement.Version: Enter the version number of the privacy
policy statement.

 Note

If you link your site to your organization's privacy policy, and your organization changes that policy,
make sure to increment the version specified by the parameter
Application.User.CustomPrivacyAgreement.Version. Changing the version number causes
the privacy notice popup to prompt users to consent to the policy again.

5. Click Save.

Related Information

Site configuration options for privacy policies [page 73]

Workflow for custom privacy policies [page 70]

Administration and data maintenance fundamentals

72 CONFIDENTIAL Topics about privacy policies
Site configuration options for privacy policies
The following privacy policies determine how policies are displayed to users.

Some of the functionality for this feature is controlled by site configuration parameters, which your administrator
can set in Ariba Administrator under Customization Manager Parameters .

 Note

If your site integrates SAP Ariba Procurement solutions with SAP Ariba Strategic Sourcing and Supplier
Management solutions, set these parameters from the procurement site of Ariba Administrator only
( Manage Core Administration ).

Application.User.PrivacyStatementOptions (enabled for self-service)

Determines whether users are prompted to consent to a privacy policy when they first log
in, and whether that privacy policy is the SAP Ariba Privacy Statement or your
organization's custom policy. Set the option you want by moving it to the top of the list
using the Move Up and Move Down buttons. Following are the available options in default
order (the SAP Ariba Privacy Statement is used by default):

● AribaPrivacyStatement
● CustomPolicy

 Note

With this option, you must specify the URL to the policy in
Application.User.CustomDataPolicyURL. Otherwise, the SAP Ariba Privacy
Statement is used.

● None

Changing the value of this parameter causes the relevant Privacy Statement popup to
appear the next time users log in. If you specify AribaPrivacyStatement, a link to the
privacy statement appears at the bottom of every page of the SAP Ariba solution. The
options CustomPolicy and None do not display a link on every page.

Application.User.CustomDataPolicyURL (enabled for self-service)

For customers who have their own data privacy policy, this parameter specifies the URL to
that policy. This parameter is applicable if
Application.User.PrivacyStatementOptions is set to CustomPolicy. If you
specify a URL here, when users first log in, the Privacy Statement popup requires them to
click a checkbox indicating their consent to your organization's policy. The popup includes a
link to the policy. The parameter value must be a valid URL. If this parameter doesn't
contain a value, the SAP Ariba Privacy Statement is used.

By default, the display text for the link uses the name of your SAP Ariba solution site, as in:
"[Site Name] - Privacy Policy." You can specify a display name for the link using
Application.User.CustomDataPolicyName.

 Note

If you change the URL, users are not automatically prompted to consent to the privacy
policy again. Therefore, when you change the URL, also increment the version by setting

Administration and data maintenance fundamentals

Topics about privacy policies CONFIDENTIAL 73
 Application.User.CustomPrivacyAgreement.Version. This ensures that users
are prompted to consent to the privacy statement that the new URL leads to.

Links to a custom data privacy policy replace the links to the SAP Ariba Privacy Statement
in the consent prompt users see when they first log in.
Application.User.CustomDataPolicyName (enabled for self-service)
For customers who have their own data privacy policy, this parameter specifies the name of
the policy. The name is displayed as a hyperlink to the custom policy URL in the Privacy
Statement popup users see when they log in. If no name is specified, the link uses the
name of your SAP Ariba solution site (which typically reflects the company name), as in:
"[Site Name] - Privacy Policy."

This parameter is applicable only if the parameter

Application.User.CustomDataPolicyURL contains a value. See also
Application.User.CustomPrivacyAgreement.Version.

Application.User.CustomPrivacyAgreement.Version (enabled for self-service)

For customers who have their own data privacy policy, this parameter specifies which
version of the policy is currently in use. The parameter value is an integer. Each time you
make a change to your organization's data privacy policy, increment the version.

Whenever you change the value of this parameter, users are again prompted to consent to
the privacy policy. The versions users consent to are recorded in the audit log.

This parameter is applicable only if Application.User.PrivacyStatementOptions is

set to CustomPolicy. SAP Ariba controls the versioning of the SAP Ariba Privacy
Statement.

Related Information

How to configure your SAP Ariba solution to link to a custom privacy policy [page 71]
Workflow for custom privacy policies [page 70]

Administration and data maintenance fundamentals

74 CONFIDENTIAL Topics about privacy policies
Topics about CSV file formats

In this section:

CSV file structure and data entry guidelines [page 75]

CSV syntax conventions [page 76]

CSV character encoding [page 78]

Fax number formats in CSV files [page 78]

Date formats [page 78]

Number formats in CSV files [page 79]

Boolean values in CSV files [page 79]

Codes for system data in CSV files [page 80]

CSV file structure and data entry guidelines

Many operations for data management require or allow importing of data in comma-separated value (CSV) files.
CSV files have the advantage of being human-readable and created easily in text editors.

CSV file structure

A CSV file consists of rows of data. The first two rows contain structural information about the encoding and layout
of the column heads in the file. Subsequent rows contain comma-delimited data:

● The first row is the character encoding. For more information, see CSV character encoding [page 78].
● The second row is the header row, which lists the column headings.
● The subsequent rows contain the data.

For example, the following CSV file consists of a character encoding row, a header row (shown in bold text), and
three lines of data:

UTF8
Column1,Column2,Column3
Value1,Value2,Value3
Value4,Value5,Value6
Value7,Value8,Value9

Administration and data maintenance fundamentals

Topics about CSV file formats CONFIDENTIAL 75
CSV data entry guidelines

When entering data in CSV files, there are general guidelines that should be followed.

Guidelines include:

● Save the sample CSV files to your local file system.

● Edit CSV files with a text editor such as vi, emacs, or Notepad.
● Do not use Microsoft Excel to edit CSV files. Excel handles line returns and other special characters incorrectly
and creates files that are not properly formatted.
● Do not choose UTF-8 encoding when saving CSV files in Notepad. This causes Notepad to save a byte-order
mark (BOM) at the beginning of the file, and the file cannot be imported into the SAP Ariba system.
● Do not use an Apple Macintosh computer to create CSV files. CSV files created on an Apple Macintosh
computer use a new line indicator of CR (carriage return) instead of the indicator used on Microsoft Windows
(CRLF) or Unix (LF). SAP Ariba solutions do not support CSV files that use the CR new line indicator.

Exported CSV file formats

The following are the guidelines for exported CSV file fromats:

● Data export tasks export all CSV files columns, including optional columns not included in imported files.
● The data in exported CSV files is always in en_US locale format, regardless of user and site default locale
settings.
● Numerical values in exported CSV files do not include the comma (“,”) separator.

Related Information

CSV character encoding [page 78]

CSV syntax conventions [page 76]

CSV syntax conventions

Each row of data in your CSV file must be structured identically, following standard syntax conventions.

Following are additional syntax conventions for CSV files that help ensure consistency.

● Do not change CSV filenames or column headings. If you modify the filenames or column headings, your data
will not import successfully.

 Note

When running individual data import tasks in the administration area, you can give the CSV file any name
you want.

Administration and data maintenance fundamentals

76 CONFIDENTIAL Topics about CSV file formats
 ● Every row must have the same number of columns, and each column must be separated by a comma.
● If you want to omit a column value, you must omit the value explicitly by using a comma. In the following
example, each row consists of three columns. The third row contains values for all three columns, the fourth
row contains values for the first and last column, and the last row contains a value only for the last column.

UTF8
Column1,Column2,Column3
Value1,Value2,Value3
Value4,,Value5
,,Value6

● Column order is insignificant. You can enter columns in any order you like. You do not have to match the
column order shown in the sample CSV files or in the data dictionary.
● If a column heading includes spaces, you must surround it in quotation marks.
● Each new line is a new entry. All white space is significant. Do not include spaces, line returns, or tabs unless
they are part of the content of the file.
● Extra spaces within a value are stored in the database but are displayed as a single space in the user interface.
For example, the value “MPSC 43976” is stored as MPSC 43976 in the database but is displayed as “MPSC
43976”.
● Trailing spaces in a value are stored in the database but are not displayed in the user interface. For example, the
value “MPSC ” is stored as “MPSC ” but is displayed as “MPSC”.
● Commas are significant. Each comma means “go to the next column.” If you want to include a comma in a
column value, surround the entire value in quotation marks. For example:

adams,"Norman Adams, Jr.",(415) 964-3063

A quoted value can span multiple lines.

● Quotes are significant. Each quote means “part of a matched pair surrounding a column value.” To include a
quote in a value, use an extra quote immediately before it. In the following example, the item description
includes an inch measurement. Notice the four quotation marks:

value1,"This flashlight is 5"" long",value3,value4

 Note

By default, two adjacent quotes in a column do not represent an empty string. This does not work for
removing existing data from a field. If you need to remove existing data by using adjacent quotes (or blank
values), request a data fix for the integration event from SAP Ariba Customer Support. The data fix will
allow you to use adjacent quotes to represent empty strings and to use blank values to represent empty
values.

● Backslash characters (\) are significant. The backslash acts as an escape character. For example, \" escapes
the quote (that is, it makes the quote a literal character in the value rather than treating it as part of a matched
pair surrounding the value).

 Note

The \" combination is treated as an escape sequence in the default configuration, as noted. If you
experience import issues caused by this combination, contact SAP Ariba Customer Support. There is a
parameter, Application.Messaging.Channels.Util.DisableBackslashDoubleQuoteEscape,
that determines how SAP Ariba cloud solutions treat the \" combination in integration events.

Administration and data maintenance fundamentals

Topics about CSV file formats CONFIDENTIAL 77
CSV character encoding
The first line of a CSV file indicates the character encoding of the data in that file.

For example, the following CSV file uses UTF-8 character encoding (the character encoding used by exported CSV
files):

UTF8
UniqueName,Name,Description,CategoryId
Auto_Commodity_Code,Auto_Commodity_Code,,5
BENEFIT:AUTOLEASE,BENEFIT:AUTOLEASE,,75

The character encoding can be any Java-supported value. For a list of supported character encodings, go to:

http://java.sun.com

Fax number formats in CSV files

Fax numbers entered in CSV files must follow specific US or international conventions prescribed by SAP Ariba.

Use the following fax number formats in CSV files for SAP Ariba:

United States: +1 (408) 555-1212

International: 86 (10) 65326057

The access code (+1) is optional.

 Note

Ariba Network automatically adds the international access code (+011) when dialing fax numbers outside of
the United States.

Date formats
When entering dates in CSV files for import into SAP Ariba, we recommend using this pattern: EEE MMM dd
HH:mm:ss z yyyy.

The following table describes each element in the date pattern.

Element Description

EEE The abbreviated day name of the week

MMM The abbreviated month name of the year.

dd The two-digit day of the month.

Administration and data maintenance fundamentals

78 CONFIDENTIAL Topics about CSV file formats
 Element Description

HH The two-digit hour of the day (24-hour clock).

mm The two-digit minute of the hour.

ss The two-digit second of the minute.

z The time zone in the form of a GMT +/- HH:mm offset. For example:

GMT+02:00

yyyy The four-digit year.

For example:

Tue Sep 26 09:26:32 GMT-07:00 2006

Number formats in CSV files

Numbers in CSV files imported into SAP Ariba must be in en_US locale format.

For example:

● 12,345.679
● 12345.67890123
● 3.14285714
● 1234567
● 0.333

Boolean values in CSV files

Boolean values in CSV files imported into SAP Ariba must be in en_US locale format.

For example:

● Yes
● No
● true
● false

Administration and data maintenance fundamentals

Topics about CSV file formats CONFIDENTIAL 79
Codes for system data in CSV files
SAP Ariba uses industry standard system codes for currency, country, states and provinces, locale, commodity,
and units of measure.

Refer to the reference data workbook when specifying the following codes in CSV files that will be imported into
SAP Ariba:

● Currency codes
● Country codes
● State/province codes
● Locale codes
● System commodity codes
● Units of measure

Administration and data maintenance fundamentals

80 CONFIDENTIAL Topics about CSV file formats
Default batch data import operations

The Import Batch Data task supports a certain set of files for each variant. When you perform a Full Load import
operation, each file in the batch has a default import operation for each file. Keep the following in mind:

● The information in this topic is applicable to the Full Load import operation. (In some cases, the default import
operation is different when the Incremental Load option is used.)
● Default import operations for batch data import files are not shown in the user interface.
● When you run a batch data import task using the Full Load option, objects that exist in the database but not in
the import file are deactivated if the default import operation for the CSV file is Load And Delete.
● For batch data import tasks that import translations (Import Master Data Translations and Import ERP
Master Data Translations), the default import operation for all supported files is Update.

In this section:

Default batch data import operations for PeopleSoft ERP [page 81]

Default batch import operations for SAP ERP [page 84]

Default batch import operations for generic ERPs [page 87]

Related Information

How to run batch data import tasks [page 34]

Default batch data import operations for PeopleSoft

ERP
The Import Batch Data task for PeopleSoft variants supports many import files along with default import
operations supported when the Full Load option is used.

File Default import operation (Full Load)

Account.csv Load and Delete

AccountingCombination.csv Load and Delete

AccountingCombinationGroup.csv Load and Delete

AccountType.csv Load and Delete

Address.csv Load and Delete

AdjustmentType.csv Load and Delete

Administration and data maintenance fundamentals

Default batch data import operations CONFIDENTIAL 81
File Default import operation (Full Load)

AllowableHierarchyChoice.csv Load and Delete

ApprovalQueues.csv Load

AutoType.csv Load and Delete

BankAccountIDType.csv Load and Delete

BankAccountType.csv Load and Delete

BankIDType.csv Load and Delete

BusinessUnit.csv Load and Delete

BuyerPaymentBankLocation.csv Load and Delete

ChargeType.csv Load

CurrencyConversionRate.csv Load

CustomGroup.csv Load

Department.csv Load and Delete

ERPCommodityCode.csv Load and Delete

ERPCommodityCodeMap.csv Load and Delete

ExpenseCodeMapping.csv Load and Delete

ExpenseHeaderCategoryMap.csv Load and Delete

ExpenseLineType.csv Load and Delete

ExpensePayment.csv Load and Delete

ExpenseTaxCodeLookup.csv Load and Delete

ExpenseTaxRateLookupByTaxCode.csv Load and Delete

ExpenseType.csv Load and Delete

ExpenseTypeToGroupMap.csv Load and Delete

GLBusinessUnit.csv Load and Delete

GroupChildGroupMap.csv Load

GroupParentGroup.csv Used by GroupChildGroupMap, not by itself

GroupPull.csv Load

GroupRoleMapPull.csv Update Elements Only

GroupRoleMapPull_Roles.csv Update Elements Only

GroupSharedUserMap.csv Load

GroupSharedUserMapPShrPull.csv Update Elements Only

GroupSharedUserMapPShrPull_Users.csv Update Elements Only

Level2Charge.csv Load

LocationType.csv Load and Delete

Administration and data maintenance fundamentals

82 CONFIDENTIAL Default batch data import operations
 File Default import operation (Full Load)

PaymentMethodType.csv Load and Delete

PaymentTerms.csv Load and Delete

PaymentTermStepDetails.csv Load and Delete

PaymentTermSteps.csv Load and Delete

PCard.csvPCard.csv Load and Delete

POConditions.csv Load

Product.csv Load and Delete

Project.csv Load and Delete

PurchasingUnit.csv Load and Delete

ReceiptByCommodityCode.csv Load and Delete

ReceiptByPartNumber.csv Load and Delete

RelationEntry.csv Load and Delete

RelationType.csv Load and Delete

RemittanceLocation.csv Load

RemittanceLocationDetails.csv Load

ResponsibleUser.csv Update

RolePull.csv Load and Delete

RuleCSVHelperfile.zip Load

SetId.csv Load and Delete

SharedUser.csv Load and Delete

SharedUserAlternateEmail.csv Update

SharedUserPSfinPull.csv Load

SharedUserPShrPull.csv Load

SharedUserShipToAddressMap.csv Update Elements Only

SharedUserSingleShipToAddressMap Update
.csv

SharedUserSupervisor.csv Update

SharedUserSupervisorPSCSVPull.csv Update

SLRemittanceInformation.csv Update

SLRemittanceInformationDetails.csv Update

Statistics.csv Load and Delete

Supplier.csv Load and Delete

SupplierIDs.csv Load and Delete

Administration and data maintenance fundamentals

Default batch data import operations CONFIDENTIAL 83
File Default import operation (Full Load)

SupplierLocation.csv Load and Delete

SupplierLocationSupplement.csv Update

SupplierOrganizations.csv Load and Delete

SupplierPaymentBankLocation.csv Load and Delete

SupplierSupplement.csv Update

TaxCodeHeader.csv Load

TaxCodeDetails.csv

TaxCodeLookup.csv Load

TaxRateLookupByTaxCode.csv Load

TaxCodeLookupFieldMapping.csv Load

TaxComponent.csv Load

TaxType.csv Load

TaxTypeMap.csv Load

User.csv Load and Delete

UserApprovalLimit.csv Update

UserParentGroup.csv Update (header file in GroupSharedUserMapUp­

date pull; not listed as a separate pull)

UserPCardMap.csv Load and Delete (in User pulls)

UserPSfinPull.csv Load

userPShrPull.csv Load and Delete

VATDefaults.csv Load and Delete

Default batch import operations for SAP ERP

The Import Batch Data task for SAP variants supports many import files along with default import operations
supported when the Full Load option is used.

File Default import operation (Full Load)

AccCategoryFieldStatusCombo.csv Load and Delete

AccountCategory.csv Load and Delete

AccountType.csv Load and Delete

AdjustmentType.csv Load and Delete

AllowableHierarchyChoice.csv Load and Delete

Administration and data maintenance fundamentals

84 CONFIDENTIAL Default batch data import operations
 File Default import operation (Full Load)

ApprovalQueue.csv Load

Asset.csv Load and Delete

AutoType.csv Load and Delete

BankAccountIDType.csv Load and Delete

BankAccountType.csv Load and Delete

BankIDType.csv Load and Delete

BuyerPaymentBankLocation.csv Load and Delete

ChargeType.csv Load

CompanyCode.csv Load and Delete

CompanyCodeIOCombo.csv Load and Delete

CompanyCodeWBSCombo.csv Load and Delete

CostCenter.csv Load and Delete

CurrencyConversionRate.csv Load

CustomGroup.csv Load

ERPCommodityCode.csv Load and Delete

ERPCommodityCodeMap.csv Load and Delete

ExpenseCodeMapping.csv Load and Delete

ExpenseHeaderCategoryMap.csv Load and Delete

ExpenseLineType.csv Load and Delete

ExpensePayment.csv Load and Delete

ExpenseTaxCodeLookup.csv Load and Delete

ExpenseTaxRateLookupByTaxCode.csv Load and Delete

ExpenseType.csv Load and Delete

ExpenseTypeGLMapping.csv Load and Delete (as part of Expense Type pull)

ExpenseTypeToGroupMap.csv Load and Delete

FieldStatusToAccountingFieldNameMap.csv Load and Delete

GeneralLedger.csv Load and Delete

GroupChildGroupMap.csv Load

GroupParentGroup.csv Used by GroupChildGroupMap, not by itself

GroupSharedUserMap.csv Load

InternalOrder.csv Load and Delete

ItemCategory.csv Load and Delete

Level2Charge.csv Load

Administration and data maintenance fundamentals

Default batch data import operations CONFIDENTIAL 85
File Default import operation (Full Load)

LocationType.csv Load and Delete

MinorityVendor.csv Update

PaymentMethodType.csv Load and Delete

PaymentTerms.csv Load and Delete

PaymentTermStepDetails.csv Load and Delete (part of Payment Terms pull)

PaymentTermSteps.csv Load and Delete (part of Payment Terms pull)

PCard.csv Load and Delete

Plant.csv Load and Delete

PlantPurchaseOrgCombo.csv Load and Delete

POConditions.csv Load

PurchaseGroup.csv Load and Delete

PurchaseOrg.csv Load and Delete

PurchaseOrgSupplierCombo.csv Load and Delete

PurchasingUnit.csv Load and Delete

ReceiptByCommodityCode.csv Load and Delete

ReceiptByPartNumber.csv Load and Delete

RelationEntry.csv Load and Delete

RelationType.csv Load and Delete

RemittanceLocation.csv Load

RemittanceLocationDetails.csv Load (part of Remittance Location pull)

ResponsibleUser.csv Update

RuleCSVHelperFile.zip Load

SharedUser.csv Load and Delete (part of Shared User pull)

SharedUserAlternateEmail.csv Update

SharedUserBillingAddressMap.csv Update

SharedUserShipToAddressMap.csv Update Elements Only

SharedUserSingleBillingAddressMap.csv Update

SharedUserSingleShipToAddressMap.csv Update

SharedUserSupervisor.csv Update

SLRemittanceInformation.csv Update

SLRemittanceInformationDetails.csv Update (part of SLRemittanceInformation pull)

Supplier.csv Load and Delete

Administration and data maintenance fundamentals

86 CONFIDENTIAL Default batch data import operations
 File Default import operation (Full Load)

SupplierIDs.csv Load and Delete (part of Supplier Organization

pull)

SupplierLocation.csv Load and Delete (part of Supplier pull)

SupplierLocationSupplement.csv Update

SupplierOrganizations.csv Load and Delete

SupplierPaymentBankLocation.csv Load and Delete

SupplierSupplement.csv Update

TaxCodeHeader.csvTaxCodeDetails.csv Load

TaxCodeLookup.csv Load

TaxRateLookupByTaxCode.csv Load

TaxCodeLookupFieldMapping.csv Load

TaxComponent.csv Load

TaxType.csv Load

TaxTypeMap.csv Load

User.csv Load and Delete (part of User pull)

UserApprovalLimit.csv Update

UserParentGroup.csv Update (part of GroupSharedUserMapUpdate­

Pull)

UserPCardMap.csv Load and Delete (as part of User pull)

VATDefaults.csv Load and Delete

WBSElement.csv Load and Delete

Default batch import operations for generic ERPs

The Import Batch Data task for generic variants supports many import files along with default import operations
supported when the Full Load option is.

File Default import operation (Full Load)

Account.csv Load and Delete

AccountingCombination.csv Load and Delete

AccountingCombinationGroup.csv Load and Delete

AccountType.csv Load and Delete

Address.csv Load and Delete

Administration and data maintenance fundamentals

Default batch data import operations CONFIDENTIAL 87
File Default import operation (Full Load)

AdjustmentType.csv Load and Delete

AllowableHierarchyChoice.csv Load and Delete

ApprovalQueue.csv Load

BankAccountIDType.csv Load and Delete

BankAccountType.csv Load and Delete

BankIDType.csv Load and Delete

BusinessUnit.csv Load and Delete

BuyerPaymentBankLocation.csv Load and Delete

ChargeType.csv Load

Company.csv Load and Delete

CostCenter.csv Load and Delete

CurrencyConversionRate.csv Load

CustomGroup.csv Load

ERPCommodityCode.csv Load and Delete

ERPCommodityCodeMap.csv Load and Delete

ExpenseCodeMapping.csv Load and Delete

ExpenseHeaderCategoryMap.csv Load and Delete

ExpenseLineType.csv Load and Delete

ExpensePayment.csv Load and Delete

ExpenseTaxCodeLookup.csv Load and Delete

ExpenseTaxRateLookupByTaxCode.csv Load and Delete

ExpenseType.csv Load and Delete

ExpenseTypeToGroupMap.csv Load and Delete

GroupChildGroupMap.csv Load

GroupParentGroup.csv Used by GroupChildGroupMap, not by itself

GroupSharedUserMap.csv Load

Level2Charge.csv Load

LocationType.csv Load and Delete

PaymentMethodType.csv Load and Delete

PaymentTerms.csv Load and Delete

PaymentTermsStepDetails.csv Load and Delete (part of Payment Terms pull)

PaymentTermSteps.csv Load and Delete (part of Payment Terms pull)

PCard.csv Load and Delete

Administration and data maintenance fundamentals

88 CONFIDENTIAL Default batch data import operations
 File Default import operation (Full Load)

POConditions.csv Load

Product.csv Load and Delete

Project.csv Load and Delete

PurchasingUnit.csv Load and Delete

ReceiptByCommodityCode.csv Load and Delete

ReceiptByPartNumber.csv Load and Delete

Region.csv Load and Delete

RelationEntry.csv Load and Delete

RelationType.csv Load and Delete

RemittanceLocation.csv Load

RemittanceLocationDetials.csv Load (part of Remittance Location pull)

ResponsibleUser.csv Update

RuleCSVHelperFile.zip Load

SharedUser.csv Load and Delete (as part of Shared User pull)

SharedUserAlternateEmail.csv Update

SharedUserBillingAddressMap.csv Update Elements Only

SharedUserShipToAddressMap.csv Update Elements Only

SharedUserSingleBillingAddressMap.csv Update

SharedUserSingleShipToAddressMap.csv Update

SharedUserSupervisor.csv Update

SLRemittanceInformation.csv Update

SLRemittanceInformationDetails.csv Update (part of SLRemittanceInformation pull)

SubAccount.csv Load and Delete

Supplier.csv Load and Delete

SupplierIDs.csv Load and Delete (part of Supplier Organizations

pull)

SupplierLocation.csv Load and Delete (part of Supplier pull)

SupplierLocationSupplement.csv Update

SupplierOrganizations.csv Load and Delete

SupplierPaymentBankLocation.csv Load and Delete

SupplierSupplement.csv Update

TaxCodeHeader.csv Load

TaxCodeDetails.csv

Administration and data maintenance fundamentals

Default batch data import operations CONFIDENTIAL 89
File Default import operation (Full Load)

TaxCodeLookup.csv Load

TaxRateLookupByTaxCode.csv Load

TaxCodeLookupFieldMapping.csv Load

TaxComponent.csv Load

TaxType.csv Load

TaxTypeMap.csv Load

User.csv Load and Delete (part of User pull)

UserParentGroup.csv Update (part of GroupSharedUserMapUpdate­

Pull)

UserPCardMap.csv Load and Delete (part of user pull)

VATDefaults.csv Load and Delete

Administration and data maintenance fundamentals

90 CONFIDENTIAL Default batch data import operations
Revision history

The following table provides a brief history of the updates to this guide. SAP Ariba updates the technical
documentation for its cloud solutions if:

● Software changes delivered in service packs or hot fixes require a documentation update to correctly reflect
the new or changed functionality
● The existing content is incorrect or user feedback indicated that important content is missing

SAP Ariba reserves the right to update its technical documentation without prior notification. Most documentation
updates will be made available in the same week as the software service packs are released, but critical
documentation updates may be released at any time.

Month/year of up­
date Updated chapter/section Short description of change

May 2019 All Full document edit and cleanup.

February 2019 Data encryption in SAP Ariba New topic.

Procurement solutions

October 2018 How to run individual data Updated descriptions of import operations.

import tasks

How to run batch data im­

port tasks

September 2018 Workspaces and tasks Mentioned the cloud integration gateway capability, enabled from the
Integration Manager workspace of Ariba Administrator. Added the
Managing dashboard tem­ topic "Enforcing confirmation before deleting approvables".
plates

Workflow for custom privacy Updated screenshot to reflect latest privacy prompt language.

policies

Privacy policy settings Updated text about downloading user information.

July 2018 Data import process over­ Added option to increase maximum size of approver lookup tables to 30
view MB.

IDs for addresses entered in New topic.

the user interface

May 2018 Reviewing the data definition Updated example URL for getting the WSDL.
in the data dictionary or
WSDL

April 2018 Topics about privacy policies Added topics for support of custom privacy policies.

Administration and data maintenance fundamentals

Revision history CONFIDENTIAL 91
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such links, you
agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by SAP at
any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Administration and data maintenance fundamentals

92 CONFIDENTIAL Important Disclaimers and Legal Information
Administration and data maintenance fundamentals
Important Disclaimers and Legal Information CONFIDENTIAL 93
www.ariba.com

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN