Skip to content

Ariba Catalog History

The Ariba Catalog History list shows every catalog built for an Ariba buyer or the public catalog, newest first. It contains catalogs downloaded with Download Catalog and catalogs that went to SAP Business Network with Send Catalog or automatically. Each entry keeps the file as it was built then. This way you can check which version a buyer got and download the same file again. For catalogs sent, the entry also shows the answer of SAP Business Network. The list is read-only.

Opening the Page

  • Via search: Ariba Catalog History
  • From the Marketplace Card on the row ARIBA: select the buyer in the Sales Channels list → Catalog History in the Ariba Buyer part (only the catalogs of this buyer)
  • From the Dashboard: choose the column Last Catalog or Catalog in Ariba in the list of buyers
  • From the Ariba Catalog Items → Catalog History

Getting the Catalog into SAP Business Network

Every catalog is for one buyer and complete. It contains all items added to this buyer, with the prices of its sales price list, and replaces the previous one at the buyer. Whether and in which form a buyer accepts catalogs is something you clarify with the buyer.

The sales channel determines where a catalog goes:

  • The catalog of a buyer is a private catalog to its buyer ANID. SAP Business Network accepts it only if the buyer is listed as a customer in your account, see Rejected with 403.
  • The public catalog goes to SAP Business Network itself and is visible to every buyer, also without a trading relationship.

There are two ways:

  • Send Catalog (recommended): Business Central builds the catalog and sends it to SAP Business Network through the merchantCENTRAL gateway, into the account of the buyer (test account for a buyer ANID ending in -T, otherwise the production account). There it replaces the catalog with the buyer's Ariba Catalog Name. With Auto Send Catalog, the job queue does this, see below.
  • Download Catalog: you download the CIF file and upload it yourself in the SAP Business Network portal.

Publishing Once in the Portal

SAP Business Network cannot publish a new catalog automatically; SAP allows this only for updates. The first time, therefore:

  1. Choose Send Catalog. If SAP Business Network has no catalog with the Ariba Catalog Name yet, it is uploaded as a new catalog (field Uploaded As New).
  2. In the SAP Business Network portal, open the catalog under Catalogs and publish it, privately to the buyer or publicly. Publish the public catalog publicly. For public catalogs, SAP requires a complete company profile.
  3. From then on, every catalog sent is published automatically after the validation.

If you uploaded the catalog in the portal before, enter its name as Ariba Catalog Name on the buyer. The catalogs sent then replace that one.

The buyer still has to approve and activate a new version before its requesters see it. If the buyer subscribed to the catalog, this happens without the buyer's action.

What Happens After Sending

SAP Business Network accepts the catalog and validates it. The Upload Status shows where it stands:

Upload Status Meaning
Sending The catalog is built and being sent. If the status stays, the session ended during the upload. Send again.
Accepted SAP Business Network received the catalog and validates it. It reports the result later.
Validated The catalog is free of errors but not published (yet).
Published The catalog is published to the buyer.
Rejected SAP Business Network did not accept the catalog, for example because of an invalid commodity code (461), because it is too large (468), because too many catalogs were sent per hour (561) or because there is no trading relationship with the buyer (403, see below). Status Message and Status Code give the reason.
Has Errors SAP Business Network found errors in the catalog during validation. Open the catalog in the portal to see the faulty lines. Then correct the items and send again.
Failed The gateway could not be reached or refused the data (for example a catalog over 10 MB). Send again after correcting it.

Rejected, faulty and failed catalogs also appear in the Ariba Sync Errors, with the sales channel code of the buyer.

SAP Business Network reports the final status (Validated, Published, Has Errors) after the validation, which can take minutes to hours. If a Catalog Notification Email is set in the Ariba Setup, this address gets it by email. In the portal, you see it under Catalogs.

Rejected with 403: No Trading Relationship

SAP Business Network accepts a private catalog only for buyers listed as customers in your supplier account (in the portal under Customer Relationships). Otherwise it refuses the upload with status 403 ("Cannot upload catalog to buyer with whom there is no valid trading relationship").

Business Central then shows the catalog as Rejected with Status Code 403 and a hint on what to do: in the Status Message of the catalog history, in the error message when sending, and in the Ariba Sync Errors.

  1. Set up the trading relationship with the buyer, so that it is listed in the portal under Customer Relationships.
  2. Then send the catalog again (Send Catalog). The job queue does not send a rejected, unchanged catalog again by itself.

Items that every buyer is to see, also without a trading relationship, can go to the public catalog instead.

Catalog Tester in the test account

The SAP test buyer Catalog Tester is not a customer of your test account. SAP Business Network therefore refuses private catalogs to it with 403.

If SAP Business Network refuses the public catalog with 403, a trading relationship is not the cause. Check in the portal that your account may publish public catalogs and how many it has already.

Sending Automatically

With Auto Send Catalog on the buyer, the job queue checks every four hours whether the buyer's catalog changed. This covers the prices of the sales price list, added or removed items, and descriptions. It sends the catalog only then. To do so, it reads the prices of the sales channel again and compares the new catalog with the last one sent. After Failed or a passing rejection (too many catalogs per hour, previous version still being validated, maintenance), it also sends an unchanged catalog again. Sales channels that are switched off are left out.

Business Central creates the job queue entry (codeunit ALN MCAR Job Queue Handler, parameter SEND_CATALOGS) when you switch the setting on for the first buyer. You can change its schedule there.

Limits

  • A catalog may be at most 10 MB zipped. The gateway zips catalogs above 3 MB itself.
  • The catalog tester in the test account checks catalogs up to 4 MB and shows the first 300 items.
  • SAP Business Network accepts private catalogs only for buyers listed as customers in your account (see above).
  • According to SAP, at most three public catalogs are possible without customer relationships.

Fields

Field Description
Entry No. Number of the entry. It is also part of the file name when downloading.
Buyer ANID, Address ID The Ariba buyer the catalog was built for.
Customer No. Customer of the buyer when the catalog was built. The descriptions follow its language.
Currency Code Currency of the prices – that of the buyer's sales price list.
Item Count How many items the catalog contains.
Created At When the catalog was built.
User ID Who built it. When sent automatically, the user of the job queue.
Upload Status Whether the catalog was sent and what SAP Business Network answered (see above). Empty for a catalog that was only downloaded.
Status Message The answer of SAP Business Network or the gateway, or what to do next.
Catalog Name Name of the catalog in SAP Business Network.
Sent At When the catalog was sent.
Automatic The catalog was sent by the job queue.

With Choose Columns you can also show Auto Publish, Status Code (cXML status of SAP Business Network, e.g. 201 = being validated, 470 = has errors), Status Updated At, Account (test or production account) and Payload ID. The payload ID identifies the upload; SAP Business Network refers to it in the later status.


Actions

Action Description
Download Again Downloads the catalog file of the selected entry once more, exactly as it was built then.

See also: Ariba Catalog Items · Ariba Buyers (Sales Channels)