Ariba Catalog Management PDF
Ariba Catalog Management PDF
Ariba Catalog Management PDF
Catalog Management
Guide
Release: 44
April 2007
Document Version: A
Copyright © 1996–2007 Ariba, Inc. All rights reserved.
This documentation, as well as the Ariba software and/or services described in it, contain proprietary information. They are provided under a
license or other agreement containing restrictions on use and disclosure and are also protected by copyright, patent and/or other intellectual
property laws. Except as permitted by such agreement, no part of the document may be reproduced or transmitted in any form by any means,
electronic, mechanical or otherwise, without the prior written permission of Ariba, Inc.
Ariba, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in the documentation. The information contained in
the documentation is subject to change without notice.
Ariba, the Ariba logo, AribaLIVE and SupplyWatch are registered trademarks of Ariba, Inc. Ariba Spend Management, Ariba Spend Management.
Find it. Get it. Keep it., Ariba. This is Spend Management, Ariba Solutions Delivery, Ariba Analysis, Ariba Buyer, Ariba Category Management,
Ariba Category Procurement, Ariba Contract Compliance, Ariba Contracts, Ariba Contract Management, Ariba Contract Workbench, Ariba Data
Enrichment, Ariba eForms, Ariba Electronic Invoice Presentment and Payment, Ariba Invoice, Ariba Sourcing, Ariba Spend Visibility, Ariba
Travel and Expense, Ariba Procure-to-Pay, Ariba Workforce, Ariba Supplier Network, Ariba Supplier Connectivity, Ariba Supplier Performance
Management, Ariba PunchOut, Ariba QuickSource, PO-Flip, Ariba Settlement, Ariba Spend Management Knowledge Base, Ariba Ready, Ariba
Supply Lines, Ariba Supply Manager, Ariba LIVE and It’s Time for Spend Management are trademarks or service marks of Ariba, Inc. All other
brand or product names may be trademarks or registered trademarks of their respective companies or organizations in the United States and/or
other countries.
Ariba Sourcing solutions (On Demand and software) are protected by one or more of the following patents, including without limitation: U.S.
Patent Nos. 6,199,050; 6,216,114; 6,223,167; 6,230,146; 6,230,147; 6,408,283; 6,499,018; 6,564,192; 6,871,191; 6,952,682; 7,010,511; 7,072,061
and 7,130,815. Patents pending.
Other Ariba product solutions are protected by one or more of the following patents:
U.S. Patent Nos. 6,199,050, 6,216,114, 6,223,167, 6,230,146, 6,230,147, 6,285,989, 6,408,283, 6,499,018, 6,564,192, 6,584,451, 6,606,603,
6,714,939, 6,871,191, 6,952,682, 7,010,511, 7,047,318, 7,072,061, 7,084,998; and 7,117,165. Patents pending.
This documentation may reference trademarks of third parties, and the software and/or services described in this documentation may include
software licensed from third parties. For third-party trademark, software license and/or copyright information, go to http://www.ariba.com/
copyrights.cfm.
44a.0051.en
Table of Contents
Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Intended Audience and Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . v
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Ariba SN Documentation Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
About Ariba Supplier Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
This preface introduces the Ariba SN Catalog Management Guide. You will find
information on the intended audience and any required prerequisites, a breakdown of
the guide’s contents, and information on learning and getting help with the product.
• Chapter 4, “Using Test Accounts” describes how to use a test account to perform
basic and advanced testing of catalogs, PunchOut sites, and order routing.
• Chapter 5, “Editing Catalogs with Excel” explains how to create Excel catalogs
and upload them to Ariba SN.
Catalogs are text files stored on Ariba Supplier Network (Ariba SN) or on your own
company’s website that describe the products and services your organization offers
and the prices you charge. You can create catalogs for any product or service,
regardless of how it is measured, priced, or delivered. Your customers access your
catalogs through their procurement applications to see product and service offerings
and buy from you. Catalogs are the main communication channel between you and
your customers.
The following topics introduce the catalog types that Ariba SN supports, explain how
customers access and approve your catalogs, and point you to resources you can use
for creating catalogs:
• “Overview of Catalog Types” on page 12
• “Benefits of Storing Catalogs” on page 13
• “About CIF Catalogs” on page 14
• “About cXML Catalogs” on page 15
• “Resources for Catalog Creation” on page 17
For instructions on how to create catalogs. See the Ariba Catalog Format Reference.
Note: Ariba SN does not yet support CIF or cXML contract files, which are catalog
files that contain pricing information only. Ariba SN currently supports index files,
which contain both product and pricing information.
Ariba SN supports any catalog in CIF or cXML format. A CIF catalog can be either a
text file saved with a .cif extension or an Excel file saved with a .xls extension. You
can upload a catalog using either the wizard or the cXML CatalogUpload transaction.
If you use the wizard, the catalog file cannot exceed 95 MB or 400,000 lines. If you
use the cXML CatalogUpload transaction, it cannot exceed 3.8 MB.
Before uploading an Excel file as your catalog, be sure the file does not exceed 1 MB.
Compress any Excel file that exceeds that limit before trying to upload it.
See “Resources for Catalog Creation” on page 17 to find out how to get information
on creating each catalog type.
When deciding which catalog format to use, consider the source of your product and
service content:
For more information about the CIF format, see the Ariba Catalog Format Reference
(click Help at the top right of any screen to go to Help@Ariba to see this and other
Ariba SN documentation.).
Catalogs must be in one of the following supported file formats (templates and
samples for these formats are available on the Help@Ariba website):
Ariba SN converts Excel catalog template files to CIF 3.0 format during upload.
Excel files must be smaller than 1 MB (uncompressed).
CIF_I_V2.1
LOADMODE: F
CODEFORMAT: SPSC
CURRENCY: USD
DATA
942888711,34A11,C11,"Eames Chair, Black
Leather",11116767,400.00,EA,2,AMFG,,,450.00
942888711,56A12,C12,"Eames Ottoman, Blk
Leather",11116767,100.00,EA,2,AMFG,,,150.00
942888711,78A13,C13,"Folding Chair, Grey
Stackable",11116767,25.95,EA,2,AMFG,,,35.95
ENDOFDATA
11/20/99 14.24.21
ITEMCOUNT: 3
The following example catalog contains one item (with parametric search data). It
also specifies a UNSPSC version for Ariba Buyer 8.0 or later.
<SupplierPartID>pn12345</SupplierPartID>
</ItemID>
<ItemDetail>
<UnitPrice>
<Money currency="USD">60</Money>
</UnitPrice>
<Description xml:lang="en">
<ShortName>Men's Shoes</ShortName>
Black squeaky spectator shoes, with a big heal
</Description>
<UnitOfMeasure>EA</UnitOfMeasure>
<Classification domain="UNSPSC_V7.1">5136000</Classification>
<ManufacturerPartID>MBS3.12</ManufacturerPartID>
<ManufacturerName>Florsheim</ManufacturerName>
<URL>http://www.florsheim.com</URL>
<Extrinsic name="ManufacturerURL">http://www.shoo.com
</Extrinsic>
<Extrinsic name="Tier">Silver</Extrinsic>
</ItemDetail>
<IndexItemDetail>
<LeadTime>10</LeadTime>
<ExpirationDate>2004-06-01</ExpirationDate>
<EffectiveDate>2000-01-25</EffectiveDate>
<SearchGroupData>
<Name xml:lang="en">"DRESSSHOE"</Name>
<SearchDataElement name="SIZE" value="12"/>
<SearchDataElement name="COLOR" value="BLACK"/>
<SearchDataElement name="GENDER" value="MEN'S"/>
</SearchGroupData>
<TerritoryAvailable>US</TerritoryAvailable>
<TerritoryAvailable>GB</TerritoryAvailable>
</IndexItemDetail>
</IndexItemAdd>
</IndexItem>
</Index>
For complete instructions on how to create cXML catalogs, see the Ariba Catalog
Format Reference.
cXML also supports the communication of purchase orders and PunchOut catalogs.
To access these guides, log in to Ariba SN and click Help on the top right of any
screen to go to Help@Ariba.
Note: If your account is suspended, you cannot publish cXML and CIF catalogs to
specific customers. For more information on suspended accounts, see the Ariba SN
Account Management Guide.
After you have published your catalog, you can perform maintenance tasks, such as
updating it with a new version, editing, deleting, and downloading.
• Uploading transfers the catalog file from your local drive to Ariba SN. During the
upload process, you enter the catalog name and classify it so that buying
organizations that are looking for products and services of a specific type can find
your catalog.
• Validating checks the catalog for syntactic and semantic errors.
• Qualifying checks the catalog for compatibility with the catalog rules set by
specific customers.
• Publishing freezes the current catalog version and notifies your customer of its
availability.
• Setting Visibility allows you to specify whether that version is public or private,
which determines which buying organizations can access it.
For more information, see “About Catalog Validation and Qualification” on page 21,
“Uploading, Validating, and Qualifying Catalogs” on page 24, and “Publishing
Catalogs” on page 31.
4 Ariba Buyer analyzes catalog data, comparing it with any previous version and
listing the differences.
5 Ariba Buyer forwards the catalog and the list of differences for approval. Most
buying organizations assign the task of catalog approval to purchasing agents.
6 After purchasing agents approve the catalog, the Ariba Buyer administrator
promotes it, making it available to users.
Ariba Buyer does not delete superseded catalogs from its database; it simply
deactivates them and retains them so that buying organizations can include them in
reports.
• There are no empty values. Ariba SN generates an alert for items with zero or no
cost.
• Unit of measure (UOM)—An item’s unit of measure must be valid based on the
UOM code specified in the catalog header. If a catalog does not use the customer’s
canonical units of measure, the customer must define a mapping file to be sure that
the incoming terminology is interpreted correctly.
• Commodity code—An item must have at least one domain-specific commodity
code that maps to a supported commodity code specified in the catalog header. You
can override the commodity code at the line-item level. Ariba SN supports
UNSPSC, eCl@ss, NAICS, and ISICS commodity codes, but only validates
UNSPSC commodity codes. By default, Ariba SN uses UNSPSC version 12.2.
• Supplier ID—An item’s Supplier ID must match the ANID or D-U-N-S number
of your supplier organization as specified in the catalog header file.
• URL formats—The Supplier URL and Manufacturer URL must have http:// along
with the URL string.
• Start/Expiration Dates—The item’s Start Date must be before the Expiration
Date.
Your customers can redefine catalog currency, units of measure, or other parameters
in their Ariba Buyer systems. If a customer redefines these parameters, your catalog
must meet these standards, or they must relax their catalog validation rules (see the
following section) to ensure that your catalog passes semantic validation.
You can qualify a catalog for one customer or for multiple customers; however,
qualifying for multiple customers means that the catalog must pass the superset of the
customers’ catalog rules. If a catalog does not pass the superset, you can:
• Repair the catalog error generically so that it passes the rules for all customers
• Upload separate catalogs, each repaired differently to pass a specific customer’s
rules
If you modify and reload an existing catalog that Ariba SN validated in the past, it
might no longer pass validation because of one or both of the following:
• Ariba SN’s semantic qualification checking was less sophisticated
• Your customer’s catalog validation rules changed since you last validated the
catalog
Note: Large catalog files can take a long time to upload, depending on the speed of
your network connection. When uploading very large catalogs, you might encounter
time-out errors. To avoid these problems, you can zip your catalog files to compress
them, which substantially decreases upload time. Consider zipping catalogs that are
larger than 10 MB to avoid a time-out error. Ariba SN automatically unzips catalogs
after upload. You can use any zip utility, such as WinZip. Each zip file can contain
only one catalog, and the file name extension must be .zip. The filename should
contain only standard ASCII characters.
Uploading Catalogs
W To upload a catalog:
1 Click Catalogs on the left navigation bar. Ariba SN displays a list of any existing
uploaded catalogs. You can click a catalog to view more information about it.
2 Click Upload and validate a new catalog. Ariba SN displays the first page of the
upload wizard.
4 Enter brief description of your catalog. Buying organizations can search on this
information.
5 (Optional) Select a customer for which you want to qualify the catalog. If you do
not select a customer, Ariba SN validates the catalog using syntactic validation and
semantic validation rules based on regular catalog standards.
Note: After Ariba SN uploads the catalog, you can qualify it for additional
customers.
6 Click Next. Ariba SN displays the Catalog Commodities page, which lists all
UNSPSC (Universal Standard Products and Services Classification Code) names
and their two-digit codes. Buying organizations can search on this information.
a Click Add in the Description area. Ariba SN displays the Commodity Selection
page. If you have previously selected commodities, they will appear in the
Description area.
Note: If you are a supplier of all the items in a given commodity level, select the
name of the higher-level commodity category instead of adding all of the
lower-level commodities. For example, a furniture supplier should select the
category “Furniture, Furnishings,” not the hundreds of individual items it sells.
c To classify your products more granularly than by segment, click the arrowhead
icon next to the commodity segment description. You can use these arrowhead
icons to drill down through commodity families, classes, and finally individual
commodities.
d Repeat steps a-c to add other commodity classifications.
f To remove a commodity description from your catalog, select the checkbox next
to the commodity to remove and click Delete.
10 Click Upload. Your Web browser uploads the file to Ariba SN.
Do not navigate in the browser window until the next page displays. Interrupting
your Web browser aborts the upload process.
After the entire catalog has been uploaded, Ariba SN unzips it if necessary and begins
catalog validation. It can take several minutes to validate large catalogs. It stores new
catalogs in a queue and validates them one by one. You can upload other catalogs
while Ariba SN is validating. To see the current status, update the page by clicking
your browser's Refresh button.
After Ariba SN completes validation, it changes the catalog status from “Validating”
to one of the following statuses:
• Validated means that your catalog is error-free. You can then publish it or qualify
it for additional customers.
• HasErrors means that Ariba SN detected catalog content that violates syntactic
validation rules, standards-based semantic validation rules, or a customer’s catalog
rules. For information on fixing errors, see “Fixing Catalog Errors” on page 28.
11 After you receive a “Validated” status, publish the catalogs to enable customers
access them. To publish catalogs, see “Publishing Catalogs” on page 31.
A–Z
a–z
0–9
period (.)
dash (-)
underscore (_)
2 To customize your view of the error list, click the icon at the top right of the Catalog
Validation Errors table. Ariba SN displays a menu. Do one or all of the following:
• To add or remove columns from view, select or deselect them in the Show/Hide
Columns section of the table menu.
• To group errors by a specific column, select the column name in the Group by
Column section of the menu.
If the catalog contains numerous errors, it is easier fix the original file and upload it
again. If the error is in the catalog body, Ariba SN displays a page for editing the
line item.
If the error is in the catalog header, Ariba SN displays a text box for editing just the
header.
4 For each error, enter a new value to replace the old value.
For information about CIF syntax and format, see the Ariba Catalog Format
Reference on the Help@Ariba website.
5 Click Update to submit your changes. Ariba SN validates your changes and, if you
selected a customer during upload, qualifies the catalog for that customer. It also
re-validates the catalog against all qualified customers to ensure that you have
introduced no new errors.
To resolve a catalog error, you can either upload a modified version of the catalog that
meets their requirements or contact your customer to ask them to disable a
requirement.
After correcting catalog errors on Ariba SN, make the same changes to the catalog
file on your computer so the errors do not reappear.
Publishing Catalogs
After uploading a catalog and fixing any errors, publish it to make it available to
customers. When you publish a catalog, you specify which buying organizations can
access it.
W To publish catalogs:
1 Click Catalogs on the left navigation bar to display your catalogs.
You can publish only catalogs whose status is Validated. Ariba SN displays
information about the catalog.
3 Click the Publish tab. Ariba SN displays the Catalog Publish page.
This page lists only customers for whom the catalog is qualified. If you know
customers are registered on Ariba SN, but you cannot see them, contact them
directly and ask them to grant you permission to see them.
6 Click the Publish button at the bottom of the page. The catalog is now “frozen,” and
can no longer be edited.
For private catalogs, buying organizations receive notification only if you select them
and they request notification. Buying organizations that you do not select do not
receive notification, even if they request it.
Please log in to your Ariba SN account to view or download the catalog file.
If you have any questions regarding this catalog, please contact Work Chairs,
Inc. directly.
Customers can download catalogs manually from Ariba SN, or you can set up
subscriptions so that Ariba SN automatically updates your customer’s existing
catalogs when new versions are available. For information on setting up catalog
subscriptions, see “About Catalog Subscriptions” on page 20.
Note: You cannot edit catalogs over 4 MB in size online. Edit large catalogs locally
(on your computer) and then use the Update feature to upload them to Ariba SN.
3 If you previously published this catalog, click Edit. This operation duplicates the
catalog on Ariba SN to create a new, unpublished version.
4 Click the Contents tab. Ariba SN displays a list of the line items in the catalog.
After you click a line number, Ariba SN displays a page for editing that line.
6 Enter new values to overwrite existing ones. You can change any field.
For information about CIF syntax and format, see the Ariba Catalog Format
Reference on the Help@Ariba website.
To make more than a few minor changes, it is easier to make them locally (on your
computer) and upload the entire catalog. For more information, see “Updating
Catalogs” on page 38.
7 Click Update when done.
After you edit a catalog, Ariba SN validates it. When validation is complete, you can
publish it.
3 If you previously published this catalog, click Edit. This operation duplicates the
catalog on Ariba SN to create a new, unpublished version.
4 Click the Header tab. Ariba SN displays the catalog header in an editable text box.
After editing catalogs on Ariba SN, make the same changes to the catalog files on
your computer so the old values do not reappear.
Updating Catalogs
After uploading catalogs, you can change them by replacing them. Updating uploads
a new catalog file, validates it, and stores it on Ariba SN. If you published the catalog,
Ariba SN sends automatic notification to all customers that subscribed to it.
Upload the entire updated catalog, not just the changes; Ariba SN does not merge
partial catalogs. Do not change catalog formats (CIF or cXML). You must use the
same format for all versions of a catalog. Note that Ariba SN will not prevent you
from changing catalog formats during an update.
Ariba SN continues to store the previous versions of your catalog, but only the latest
version is visible. You can access previous versions by deleting the current version.
Note: If you update an existing catalog that Ariba SN validated in the past, it might no
longer pass validation when you upload it because of one or both of the following:
For more information, see “About Catalog Validation and Qualification” on page 21.
W To update catalogs:
1 Click Catalogs on the left navigation bar. Ariba SN displays all your uploaded
catalogs.
2 Click a catalog in the list. Ariba SN displays background information about the
catalog.
3 Click Update content. Ariba SN displays the Update New Catalog Content page.
4 Enter the file name of the new catalog on your hard disk, or click Browse to
navigate to it.
Use the same file name for all versions of a given catalog. Using the same name
makes catalog management easier for buying organizations.
5 Click Submit.
Your Web browser reads the file and transmits it to Ariba SN. Ariba SN then
automatically begins catalog verification.
Please log in to your Ariba SN account to view or download the catalog file.
If you have any questions regarding this catalog, please contact Work Chairs,
Inc. directly.
For private catalogs, customers receive notification only if you select them and they
request notification. Customers that you do not select do not receive notification, even
if they request notification.
Deleting Catalogs
Deleting catalogs removes them from Ariba SN. Customers can no longer view them
online or download them. Customers that subscribed to the catalog receive automatic
notification that it has been deleted.
W To delete catalogs:
1 Click Catalogs on the left navigation bar.
Note: Deleting a catalog from Ariba SN does not delete the catalog from your
customer’s Ariba Buyer system. Customers that previously downloaded these
catalogs and imported them into Ariba Buyer can still use them. To ensure that buying
organizations do not continue to use old catalogs, add an expiration date to your
catalogs (available in CIF 3.0 and cXML catalog formats).
Downloading Catalogs
You can download your catalogs from your Ariba SN account. You might want to
download them if you have lost your local catalogs or to verify the contents of
uploaded catalogs.
W To download catalogs:
1 Click Catalogs on the left navigation bar.
3 Click the Download tab. Ariba SN displays the available download formats:
a Click Convert to Excel. This step starts the conversion process, which can take
several minutes, depending on catalog size.
b Wait for the conversion to complete. Click Refresh Status to see the current
conversion status; when complete, the Download as Excel button becomes active.
6 Your browser prompts you for a location to store the downloaded file.
7 If your Web browser opens and displays the template, use the File > Save command.
You can download catalogs as Excel files if they are in CIF 3.0 format and they are
smaller than 400k bytes.
PunchOut catalogs are interactive catalogs stored on your website that use cXML to
enable two-way communication of electronic commerce details. For PunchOut
catalogs, procurement applications display a hyperlink instead of product or pricing
details. When users click this hyperlink, their Web browser displays a page from your
local website.
The following topics introduce PunchOut catalogs and websites, discuss the benefits
and tradeoffs of using them, and provides a procedure for adding a link to a PunchOut
website on Ariba SN.
• “About PunchOut Catalogs” on page 43
• “Linking to PunchOut Catalogs” on page 45
For information on how to implement a PunchOut website, see the cXML User’s
Guide and the cXML Solutions Guide on the Help@Ariba website, which you can
access by clicking Help at the top right of any screen.
PunchOut catalogs allow you to leverage existing resources from simple online
catalogs to advanced e-commerce sites. PunchOut catalogs can also use search
engines to find items on your website.
When deciding whether to use PunchOut catalogs, consider the following tradeoffs:
• They require all users to have full Internet access, which some companies do not
allow.
• They require you to implement and maintain an interactive website, accessible 24
hours a day, seven days a week.
• The Internet can be slow, depending on connection type and Internet load.
Note: If your account is suspended, your customers can access your PunchOut
catalogs, shop for products and services, and create a purchase order; however, Ariba
SN does not send you the purchase order. For more information on suspended
accounts, see the Ariba SN Account Management Guide.
PunchOut catalog users do not need to enter a user password for your site. They can
be pre-authenticated by Ariba SN.
3 Enter information about your PunchOut catalog as you would for a regular catalog.
Buying organizations can search each of these fields. Special notes:
• You must enter an “https://” prefix for the PunchOut URL value. This URL is no
longer used, but procurement applications require a value for this field.
• The UN/SPSC code field adds a UNSPSC code to the PunchOut index catalog.
• The Commodities field allows you to classify the types of products or services
you offer, which helps buying organizations searching for specific products or
services find your catalog. Click Add, and Ariba SN displays the Commodities
Chooser. For more information on classifying commodities, see “Uploading
Catalogs” on page 25.
Note: Ariba SN uses UNSPSC version 12.2 codes; however, it can translate any
UNSPSC version to 12.2 and translate version 12.2 to any UNSPSC version.
4 Click OK.
5 Publish the catalog as you would any other catalog. See “Publishing Catalogs” on
page 31.
Ariba SN now forwards all PunchOut requests to the URL specified in your cXML
profile. To specify the PunchOut URL, that is actually used, click Configuration >
Electronic Order Routing > Configure cXML setup.
A test account allows you and your customers to test catalogs, purchase order
generation, routing, and receiving. Test accounts are optional. The following topics
introduce testing:
• “About Test Accounts” on page 47
• “About Testing Methods” on page 48
• “About Basic and Advanced Catalog Test Modes” on page 49
• “Switching to a Test Account” on page 50
• “Running a Basic Test” on page 51
• “Running an Advanced Test on a PunchOut Website” on page 55
• “Troubleshooting” on page 59
Test accounts enable you and your customers to receive test purchase orders without
the risk of actually shipping products or disrupting production transactions.
Note: If your Ariba SN account is suspended, you can send documents to and receive
documents from customers through your test account, but not through your
production account. For more information on suspended accounts, see the Ariba SN
Account Management Guide.
For information about account modes, see the Ariba SN Account Management Guide.
The catalog tester also allows you to debug your interactive PunchOut website and
demonstrate it to prospective customers. The catalog tester sends out cXML 1.1
messages, and can receive both cXML 1.0 and 1.1 messages. It allows you to view
and edit these cXML messages.
• Testing with a customer lets you simulate the buying experience using the
customer’s procurement system. Perform this type of testing after debugging your
catalogs.
The testing method you use depends on the type of testing you perform. You must
weigh the advantages and limitations of both types of testing. You can perform both
types of testing, one after the other.
Most suppliers first test on their own to check basic functionality, then they ask their
customers to send orders and test catalogs and PunchOut.
In advanced test mode, you can even modify the cXML as you step through all the
phases of cXML PunchOut and OrderRequest transactions.
You can switch to your test account from your home page at any time. Alternatively,
you can log directly into your test account by using your test account username and
password.
5 If you have not used your test account before, Ariba SN prompts you for a new
username and password. Click OK. Ariba SN logs you into your test account.
6 Click Configuration to check your test account setup.
When you set up your test account, Ariba SN copies company profile information
from your production account. The rest of your test account settings are set to their
default state. You can change these settings at any time, and they do not affect your
production account.
The following table lists the default notation used for test account username, company
name, and organization ID (you can change any of these values, except organization
ID):
You can switch back to your production account by going to your Home page and
clicking Switch to Production. However, you cannot switch to your production account
if you logged directly into your test account.
Production orders can be sent only to a supplier’s production account, not to their test
account.
Upload your catalogs to your test account, unless test customers already have them.
Catalogs in your test account are visible only to customers’ test accounts, not to their
production accounts. Switching between testing and production requires action only
on the customer's side—they only need to modify Ariba Buyer settings.
For information about account modes, see the Getting Started with Ariba SN white
paper.
To prevent test orders from being interpreted as real ones, you might want to
configure your test account to use a different order routing method than your
production account. For example, if you use fax order routing for production, you
might want to use email order routing or online Inbox to test basic purchase order
functionality. However, for the most realistic testing, use the same order routing
method as you use for production, including an order receiving system if you have
one. Warn order processing personnel not to fill orders sent from the test customer.
2 Click Catalogs on the left navigation bar to display a list of all your catalogs. Only
the catalogs in your test account are visible.
You can test catalogs before or after publishing them, but they must first pass
validation. If the Test link is not clickable, the catalog failed validation or you are
not logged in to a test account.
Note: The catalog tester cannot test catalogs larger than four MB.
3 Click Test next to a catalog. Ariba SN displays the contents of the catalog. It
displays only the first 300 items. Partial items (items that do not have values for all
required fields) do not appear.
You can display additional items by clicking the column heading to sort the
catalog.
5 Click Show Details to see complete catalog information for all items. Click Hide
Details to return to the regular view.
• For PunchOut items, you can click Edit or Inspect to punch out again.
8 Click Submit to generates a cXML purchase order. You can view the cXML
contents and the cXML response from Ariba SN.
10 Click Inbox to view the orders online. Test transactions list “Catalog Tester” as the
customer.
11 If you configured your account to send cXML orders, examine the orders in your
order receiving system. Purchase orders route to you through your preferred order
routing method within a few minutes.
12 Delete the purchase orders from your order receiving system. Do not allow your
system to execute test orders.
You cannot delete test orders from Ariba SN. However, you can set their status to
“Shipped” so you can ignore them.
For more information about the online Inbox, see the Ariba SN Transactions Guide.
Viewing cXML contents can be extremely useful when developing and debugging
PunchOut websites.
Ariba Buyer 7.0, 8.0, 8.1 and 8.2.x generate slightly different PunchOutOrderMessage
and OrderRequest documents:
• Ariba Buyer 7.0:
The DOCTYPE element refers to
“http://xml.cXML.org/schemas/cXML/1.1.010/cXML.dtd.”
The included Extrinsics are “UserEmail,” “UniqueName,” and “CostCenter.”
There is a Contact element.
There are Shipping and Tax elements in the OrderRequest
In advanced testing, you perform the same tasks as in basic testing, but you have more
visibility and control of the underlying cXML documents.
2 Click Test next to a PunchOut catalog. By default, the catalog tester is in Advanced
Test mode.
Note: If the Test link is not clickable, the catalog failed validation or you are not
logged in to your test account.
5 Click Continue.
6 Proceed through each step in the process to review and, if desired, edit each cXML
document. You can edit both outgoing and incoming documents by:
• Selecting additional credentials for the From element. cXML documents
sometimes contain multiple credentials, so you might want to exercise your
PunchOut site’s credential-domain recognition. Your PunchOut site must
recognize the NetworkID of the catalog tester: AN01000002779-T.
• Changing the parts of cXML documents that appear in text-edit boxes. For
example, in PunchOutSetupRequest documents, you could edit or add Extrinsic
elements to simulate additional data passed by procurement applications.
Another example that you might try is to enter different values in the
SelectedItem element.
7 Click the appropriate button at the bottom of the page to continue to the next step
until you return to the catalog tester. After a successful PunchOut session, the items
you select appear in your shopping cart at the top of the page.
8 If necessary, initiate edit or inspect sessions to punch out again.
For a description of the PunchOut steps, see the cXML User's Guide. For additional
PunchOut information, see the cXML Solutions Guide. Both documents are available
on the Help@Ariba website.
Troubleshooting
Use this procedure to identify the source of any problems that occurred while testing
order routing.
3 Click the test transaction’s order number. Ariba SN displays the content of the
purchase order.
4 Click Order History. Ariba SN displays processing information for the purchase
order.
5 Click Status History to see additional processing information.
6 Click Configuration to examine your order routing configuration. Ensure that your
email address or website URL is correct.
7 After correcting the problem, click Resend on the Order Detail page to resend the
order and then check that there are no remaining problems.
8 Delete the purchase order from your order receiving and management system so
that your system does not execute the test order.
These topics explain how to create Excel catalogs and upload them to Ariba SN:
• “Downloading the CIF Template” on page 63
• “Editing the CIF Template” on page 64
• “Uploading and Downloading Excel Files” on page 67
• “Downloading CIF Files in Excel Format” on page 68
• “Manually Converting Excel Files to CIF” on page 69
• “Opening CIF Files in Excel” on page 70
• If your web browser opens and displays the template, choose File > Save As and
save the template to a local drive.
5 Log out of Ariba SN.
Field Description
Supplier ID Your ANID (Ariba Network ID) or D-U-N-S number:
• To view your ANID, log in to your Ariba SN account and click
Home at the top right of the screen.
• To look up your organization’s D-U-N-S number, go to
www.dnb.com.
The template contains useful descriptions of each field. To read them, put your
pointer on the red comment markers.
2 Review the catalog header to make sure the fields are correct. For example:
CODEFORMAT: UNSPSC
CURRENCY: USD
SUPPLIERID_DOMAIN: NETWORK_ID
Specify currency names with ISO 4217 three-letter (CodeA) currency codes.
3 Enter your catalog data into the body fields. For each line item, you must enter
values for the first seven fields (see the table above). Ensure that your entries do not
exceed the field sizes (field size is indicated in the comments).
4 To calculate the number of catalog items for the ITEMCOUNT field, subtract the
number of the last line of data from the number of the first line of data, and then
add one.
5 Save the file as an Excel (.xls) file.
For comprehensive information about CIF, see the Ariba Catalog Format Reference.
To access this guide, log in to Ariba SN and click Help at the top right of any screen to
go to the Help@Ariba website.
For a list of codes, go to www.unetrades.net. Click Repositories and Codes > Country &
Currency Codes > Country & Currency > Currency per country.
Ariba Buyer does not recognize Excel catalogs. Instead, it use CIF files. To convert
Excel catalogs to CIF, you can either use the Ariba SN Excel-to-CIF converter, or you
can convert them yourself.
You can compress Excel files using a zip utility. Zipped files must have a .zip
extension. The maximum size of Excel files that can be uploaded is one MB
(uncompressed).
6 Click Upload.
Ariba SN uploads the file, unzips it if necessary, converts it to CIF format, and starts
validation. Conversion from Excel to CIF can take several minutes depending on the
catalog size. As Excel files convert, their status is “Validating.”
Ariba SN does not retain the original Excel files you upload. After it converts them to
CIF, it deletes them.
3 Click the Download tab. If the Download page does not display the Excel Download
section, the catalog does not meet the requirements for Excel conversion.
4 Click Convert to Excel. Ariba SN begins the conversion process, which can take
several minutes depending on catalog size. You can click Refresh Status to view the
current conversion status. When Ariba SN completes the download, it enables the
Download as Excel button.
To download catalogs, they must be in CIF 3.0 format and smaller than 600K bytes.
To convert to CIF manually, you save the Excel files to CSV format and delete extra
commas with a text editor.
2 Select “CSV (MS-DOS)” as the file type. CSV stands for “comma-separated
variable.” Excel inserts a comma between each field.
3 Enter an intuitive name for the file. The recommended format is
<catalog_description>_<customer_name>—for example, workchairs_acme.
4 Click Save.
If you use Windows Notepad to edit catalogs, do not click the “Save as Unicode”
check box. For the same reason, if you use Microsoft Word, do not select “Unicode
Text” as the file type. Raw Unicode (also known as UCS-2) is not file-safe because its
byte order varies depending on the operating system.
2 Select the CIF file. Excel displays the Text Import Wizard.
4 Select “Comma” as the delimiter and quote (“) as the text qualifier. Deselect “Tab.”
5 Click Next.
6 Use Shift-click to select all columns, select “Text” as the column data format, and
then click Finish.
Treat all columns as text so that Excel retains any leading or trailing zeroes.
7 To make the resulting spreadsheet more readable, select all cells and select
Format > Column > AutoFit Selection.
The Excel template available on Ariba SN is a regular Excel file, so you can simply
double-click it to open it. There is no need to perform the steps below for the Excel
template.
A catalogs 11, 36
advanced test mode 49 adding items online 36
running 55 benefits of storing on Ariba SN 13
ANID (Ariba Network ID) 65 checking against customer rules 21
Ariba Buyer checking syntax of 21
OrderRequest documents generated 55 classifying by UNSPSC codes 26
PunchOutSetupRequest documents custom 13
generated 55 deleting 40
versions simulated in advanced test mode deleting items online 36
55 displaying 36
Ariba Network ID (ANID) 65 downloading 41
Ariba Ready program viii editing 36
Ariba SN documentation, accessing 17 encryption of 13
Ariba Supplier Advantage (ASA) program expiration and deletion policy 14
viii how suspended accounts affect 19, 44
Ariba Supplier Consulting program ix in test accounts 51
Ariba Supplier Services viii legal file name characters 28
maximum size of 12
notifying customers of availability 34
B publishing 31
PunchOut 12, 43
basic test mode 49
resources for creating 17
running 51
reviewing and fixing errors 28
security 13
C selecting a format 12
setting visibility 34
catalog headers, CIF, displaying and editing subscriptions 20
37 supported formats 14
catalog headers, errors in 30 supported types 12
Catalog Interchange Format, see CIF testing 51
catalog notifications 35 updating 38
catalog testing uploading 21
coordinating with customers 47 uploading large files 24
with or without customers 48 using Excel to edit 63
catalog versions 38 validating 21
versioning 13
U
unit of measure validation 22
UNSPSC codes 65
specifying for catalogs 26
updating catalogs 38
uploading catalogs 21
large catalog files 24
using the CatalogUploadRequest
transaction 28
URL validation 23
usernames, default notation for test accounts
50
V
validating catalogs 21
against a customer’s requirements 21
character set validation 22
CIF file header validation 22
decimal format validation 22
field validation 21
integer format validation 22
price format validation 22
syntactic validation 21
validation
errors 28
versions of catalogs 38
deleting 40
versions, of catalogs 13