Académique Documents
Professionnel Documents
Culture Documents
Catalog Management
Guide
Release: 44
April 2007
Document Version: A
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
Chapter 1 About Catalogs . . . . . . . . . . . . . . . . . . . . . . 11
Overview of Catalog Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Benefits of Storing Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
About CIF Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
About cXML Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Resources for Catalog Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 2 Publishing CIF and cXML Catalogs . . . . . . . 19
Making Catalogs Available to Your Customers . . . . . . . . . . . . . . . . . 19
About Catalog Validation and Qualification. . . . . . . . . . . . . . . . . . . . 21
Uploading, Validating, and Qualifying Catalogs . . . . . . . . . . . . . . . . 24
Uploading Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Fixing Catalog Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Publishing Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Displaying and Editing Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Updating Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Deleting Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Downloading Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Chapter 3 Linking to PunchOut Catalogs . . . . . . . . . . 43
About PunchOut Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Linking to PunchOut Catalogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
iii
Table of Contents
iv
Preface
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 guides contents, and information on learning and getting help with the product.
Preface
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.
See
Register on Ariba SN
Manage your
organizations Ariba SN
account
vi
Preface
If you want to
See
Connect to suppliers so
you can buy from them
vii
Preface
If you want to
See
viii
Preface
ix
Preface
Chapter 1
About Catalogs
Catalogs are text files stored on Ariba Supplier Network (Ariba SN) or on your own
companys 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:
For instructions on how to create catalogs. See the Ariba Catalog Format Reference.
11
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:
If you...
12
If you...
13
both the earlier CIF format (CIF 2.1) and the newer CIF 3.0, which has all the features
being introduced in cXML.
Catalogs must be in one of the following supported file formats (templates and
samples for these formats are available on the Help@Ariba website):
Format
Extension
CIF 2.1
.cif
CIF 3.0
.cif
Excel
.xls
Ariba SN converts Excel catalog template files to CIF 3.0 format during upload.
Excel files must be smaller than 1 MB (uncompressed).
14
15
<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.
16
Implement a PunchOut
website
To access these guides, log in to Ariba SN and click Help on the top right of any
screen to go to Help@Ariba.
17
18
Chapter 2
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.
19
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.
20
4 Ariba Buyer analyzes catalog data, comparing it with any previous version and
21
22
URL formatsThe Supplier URL and Manufacturer URL must have http:// along
with the URL string.
Start/Expiration DatesThe items Start Date must be before the Expiration
Date.
Territory and LanguageThe Territory and Language codes must validate
against the ISO 3166-1 and 3166-2 codes and Java locale codes.
23
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.
24
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.
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.
25
6 Click Next. Ariba SN displays the Catalog Commodities page, which lists all
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
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.
e Click OK to save your changes.
f To remove a commodity description from your catalog, select the checkbox next
to the commodity to remove and click Delete.
26
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.
27
HasErrors means that Ariba SN detected catalog content that violates syntactic
validation rules, standards-based semantic validation rules, or a customers 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
28
If you have just finished the catalog upload process for a short catalog, Ariba SN
automatically displays the Errors tab.
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.
To expand or collapse the groupings, click an option in the Grouping Expansion
section of the menu.
3 When you are ready to view an error, click a line number or an error description.
29
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.
30
Publishing Catalogs
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.
31
Publishing Catalogs
To publish catalogs:
1 Click Catalogs on the left navigation bar to display your catalogs.
32
Publishing Catalogs
You can publish only catalogs whose status is Validated. Ariba SN displays
information about the catalog.
33
Publishing Catalogs
3 Click the Publish tab. Ariba SN displays the Catalog Publish page.
Private. Ariba SN makes your catalog visible only to buying organizations that
you specify. Select this option for catalogs that contain contract prices. This
option automatically creates a subscription to the catalog for all customers you
select.
Public. Ariba SN makes your catalog visible to all buying organizations. To
receive a catalog, a buying organization must establish a relationship with you.
For instructions, see Publishing Catalogs on page 31.
5 Select customers to subscribe and notify. This step creates the catalog subscriptions
34
Publishing Catalogs
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.
Note: If your account is suspended, you cannot publish catalogs to specific
customers, so Ariba SN does not display your customers at the bottom of this page.
6 Click the Publish button at the bottom of the page. The catalog is now frozen, and
Ariba SN
Ariba SN.
Customers can download catalogs manually from Ariba SN, or you can set up
subscriptions so that Ariba SN automatically updates your customers existing
catalogs when new versions are available. For information on setting up catalog
subscriptions, see About Catalog Subscriptions on page 20.
35
(on your computer) and then use the Update feature to upload them to Ariba SN.
W
36
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.
W
37
Updating Catalogs
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:
38
Updating Catalogs
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.
Publishing your updated catalog sends automatic notification to any buying
organizations that subscribed to it. They receive an email similar to the following:
From: Work Chairs, Inc.
To: mark@acme.com
Subject: Work Chairs, Inc. catalog notification from Ariba SN
Work Chairs, Inc. has updated a catalog on Ariba SN.
Catalog Name: Fall Prices
Description: This catalog lists our premier-level prices for popular office
furniture.
39
Deleting Catalogs
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.
2 Click the name of one of your catalogs.
3 Click one of the Delete links:
40
Downloading Catalogs
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.
2 Click the name of one of your catalogs.
3 Click the Download tab. Ariba SN displays the available download formats:
41
Downloading Catalogs
You can download catalogs as Excel files if they are in CIF 3.0 format and they are
smaller than 400k bytes.
42
Chapter 3
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 Users
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.
43
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.
44
3 Enter information about your PunchOut catalog as you would for a regular catalog.
UNSPSC version to 12.2 and translate version 12.2 to any UNSPSC version.
45
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.
46
Chapter 4
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:
Test accounts enable you and your customers to receive test purchase orders without
the risk of actually shipping products or disrupting production transactions.
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.
47
For information about account modes, see the Ariba SN Account Management Guide.
Benefits
Without customer This testing method does not depend on customers, so you can
perform testing iterations more rapidly.
To use the catalog tester, you do not need to modify your
catalogssimply upload them to your Test account.
The catalog tester tests only catalogs that are smaller than four
MB and displays only the first 300 catalog items. The catalog
tester ignores partial catalog itemsthose that do not have
values for all required fields.
48
Test Method
Benefits
With customer
Most suppliers first test on their own to check basic functionality, then they ask their
customers to send orders and test catalogs and PunchOut.
49
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):
Property
Notation
Example
Username
test-judy@workchairs.com
50
D-U-N-S: 94-288-8710-T
NetworkId: AN01000123-T
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 suppliers 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 sidethey 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.
production accounts.
51
2 Click Catalogs on the left navigation bar to display a list of all your catalogs. Only
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.
52
5 Click Show Details to see complete catalog information for all items. Click Hide
Details to return to the regular view.
To test a non-PunchOut item, click Add in its Actions column. Ariba SN displays
the item you selected under Order Contents.
To test a PunchOut item, click Shop. A new browser window opens and displays
the web page for that item. Navigate your website, select items, and check out.
Ariba SN returns to the catalog tester and displays the items you selected under
Order Contents.
7 Do one or both of the following to test the order contents:
For non-PunchOut items, you can change item quantities or delete items. Click
Update Quantity to update the Total Price.
53
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
customer.
54
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
55
Test mode.
Note: If the Test link is not clickable, the catalog failed validation or you are not
logged in to your test account.
3 Click Shop next to a catalog item.
56
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 sites credential-domain recognition. Your PunchOut site must
recognize the NetworkID of the catalog tester: AN01000002779-T.
57
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.
9 Click Submit to generate a cXML OrderRequest document.
58
Troubleshooting
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.
The destination of PunchOutSetupRequest documents is determined by your cXML
profile or your accounts PunchOutSetupRequest URL field, not by the URL within
those documents.
Troubleshooting
Use this procedure to identify the source of any problems that occurred while testing
order routing.
W
transactions.
2 Find the test transaction in the list to ensure that it was logged. Test transactions
59
Troubleshooting
3 Click the test transactions 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
60
Troubleshooting
7 After correcting the problem, click Resend on the Order Detail page to resend the
61
Troubleshooting
62
Chapter 5
If your browser prompts you to specify a location for storing the downloaded
file, select a folder on a local drive.
63
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.
64
Description
Supplier ID
Enter the price per unit for the catalog item. Specify numbers as
you want them to appear to users. For example, for $19.50, enter
19.50 (include the trailing zero). Do not include the currency
symbol ($).
Unit of Measure Enter the unit of measure for the catalog item using the UNUOM
(United Nations Units of Measure). For information on this
standard, go to www.unece.org/cefact/codesfortrade/rec20.xml or
the Catalog Documentation area of Help@Ariba.
65
template.
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.
Use Excel 95 or later to edit the template.
For a list of codes, go to www.unetrades.net. Click Repositories and Codes > Country &
Currency Codes > Country & Currency > Currency per country.
66
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.
67
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.
5 Click Download as Excel.
6 Do one of the following:
If your browser prompts you to specify a location for storing the downloaded
file, select a folder on a local drive.
If your web browser opens and displays the template, use File > Save As to save
the template to a local drive.
To download catalogs, they must be in CIF 3.0 format and smaller than 600K bytes.
68
example, workchairs_acme.
4 Click Save.
W
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.
69
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.
70
Index
A
advanced test mode 49
running 55
ANID (Ariba Network ID) 65
Ariba Buyer
OrderRequest documents generated 55
PunchOutSetupRequest documents
generated 55
versions simulated in advanced test mode
55
Ariba Network ID (ANID) 65
Ariba Ready program viii
Ariba SN documentation, accessing 17
Ariba Supplier Advantage (ASA) program
viii
Ariba Supplier Consulting program ix
Ariba Supplier Services viii
B
basic test mode 49
running 51
C
catalog headers, CIF, displaying and editing
37
catalog headers, errors in 30
Catalog Interchange Format, see CIF
catalog notifications 35
catalog testing
coordinating with customers 47
with or without customers 48
catalog versions 38
catalogs 11, 36
adding items online 36
benefits of storing on Ariba SN 13
checking against customer rules 21
checking syntax of 21
classifying by UNSPSC codes 26
custom 13
deleting 40
deleting items online 36
displaying 36
downloading 41
editing 36
encryption of 13
expiration and deletion policy 14
how suspended accounts affect 19, 44
in test accounts 51
legal file name characters 28
maximum size of 12
notifying customers of availability 34
publishing 31
PunchOut 12, 43
resources for creating 17
reviewing and fixing errors 28
security 13
selecting a format 12
setting visibility 34
subscriptions 20
supported formats 14
supported types 12
testing 51
updating 38
uploading 21
uploading large files 24
using Excel to edit 63
validating 21
versioning 13
71
72
cXML catalogs
downloading 41
fixing errors in 28
how suspended accounts 19
maximum size of 12
D
DATA and ENDOFDATA token validation 22
decimal validation 22
deleting catalogs 40
deletion policy for catalogs 14
description field validation 22
displaying catalogs 36
documentation roadmap viviii
documentation, for catalog creation 17
downloading catalogs 41
E
editing catalogs 36
editing items online 36
email
notification for catalog updates 39
notification for published catalog 35
encryption, catalog 13
errors, fixing in catalogs 28
Excel
downloading CIF catalogs as 41
editing catalogs with 63
using to edit catalogs 14
Excel files
converting to CIF 67
converting to CIF catalogs 14
converting to CIF manually 69
downloading 68
uploading and downloading 12, 67
Excel-to-CIF converter 67
expiration date validation 23
expiration policy for catalogs 14
preface v
price format validation 22
private catalogs
designating 34
email notifications for catalog updates 40
notifications for 35
production account, switching to from test
account 51
public catalogs, designating 34
publishing catalogs 31
overview 19
PunchOut catalogs 12, 43
how suspended 44
introduction to 43
linking to 45
testing 51
PunchOut websites
testing 48, 49, 55
PunchOutSetupRequest documents
generated by Ariba Buyer 55
purchase order, test 60
field validation 21
file names, catalog, legal characters 28
Find 59
From Credentials, viewing 57
H
HTTPS protocol, for catalog encryption 13
I
index files, catalog 12
integer validation 22
Internet catalogs, see PunchOut catalogs
ISO code versions, used to validate territory
and language 23
L
language validation 23
linking to PunchOut catalogs 45
logging in to test accounts 50
Q
qualifying catalogs for customers 22
N
S
notifications 35
for catalog availability 34
for catalog updates 39
O
online manuals, accessing 17
order routing testing 48, 51
partial catalog items ignored 48
troubleshooting 59
OrderRequest documents
generated by Ariba Buyer 55
organization IDs, default notation for test
accounts 50
security 13
semantic qualification 21
semantic validation 22
start date validation 23
subscriptions, catalog 20
Supplier ID 65
supplier ID validation 22
Supplier ID, modifying for testing with
customers 49
supplier services ??ix
suspended accounts
restrictions on PunchOut catalogs 44
restrictions on test accounts 47
syntactic validation 21
P
partial catalog items 48
73
Z
-T suffix for Supplier ID 49
territory validation 23
test accounts 47
catalogs in 51
example test purchase order 60
how account suspension affects 47
Inbox 59
notation used in 50
switching to 50
test modes, advanced 49
test modes, basic 49
To Credentials, viewing 57
troubleshooting order routing testing 59
zipping catalogs 24
zipping Excel files 67
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 customers 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
74
ARIBA, INC.
807 11th Avenue
Sunnyvale, CA 94089 USA
Telephone: 650.390.1000
Fax: 650.390.1100
www.ariba.com