Feature Name & Description |
SAP Ariba Solutions |
Automatically On |
Customer Enabled/ Customer Configurable |
Contact SAP Ariba To Enable |
Learn More |
Catalog
|
|
|
|
|
|
Changing the sequence of execution of catalog content rules [CM-4290] This feature enables you to configure the sequence in which catalog content rules are executed. You can move the rules within each category by dragging and dropping them to rearrange the order in which they are executed. |
Q4
|
 |
|
|
 |
Synchronizing incremental catalog subscriptions from Ariba Network in CMS-enabled sites For CMS enabled sites, the Ariba Network Full Subscription synchronization schedule task synchronizes all versions of a catalog (incremental or full) uploaded to the Ariba Network with the buyer CMS service.
|
Q3
|
 |
|
|
 |
Support for retaining supplier location to supplier organization mapping information in catalog subscriptions With this feature, when catalogs are imported, the associated supplier location to supplier organization mapping information is retained in SAP Ariba Procurement solutions. This ensures that all catalogs from different supplier subsidiary accounts are associated under the mapped supplier organization. As a result, users attempting to buy punchout items are directed to the correct punchout site. |
Q3
|
 |
|
|
 |
Support for determining catalog item prices dynamically This feature enables catalog managers to define different prices for a CIF catalog item based on different values of a mapped entity configured as a price lookup key. The price of the item displayed in the catalog search results and item details pages is determined dynamically based on the business scenario and the value of the mapped entity. |
Q2 |
|
|
|
 |
Catalog filename-based filtering of catalog data extraction in JSON format When extracting catalog data in JSON format from SAP Ariba Catalog, users can now request for filtered data based on specific catalog files. To filter data based on catalog filenames, one must specify a relevant value for the new CATALOGPREFIX parameter in the request from SAP SRM or another external system for catalog data extraction. |
Q2 |
 |
|
|
 |
Item Specification field for specifying additional catalog item attributes This feature introduces a new Item Spec catalog field to specify the additional attributes or specifications of an item that help describe and identify the catalog item better. |
Q1 |
 |
|
|
 |
Support for exporting catalog comparison report The catalog approval screen does not have an option for the approver to export the comparison summary and the catalog content changes for further analysis. This becomes a problem when approving catalog items with a large number of items with changes. This feature provides functionality in the catalog approval screen,in buyer, to export the comparison summary and catalog content changes(rows) into Excel. |
Q1 |
 |
|
|
 |
Support for multiple product classification systems in BMEcat catalogs With this feature, SAP Ariba catalogs in BMEcat format provide support for multiple product classification systems and enable users to shop for items based on the classification systems. A new Classification System option is now displayed in the Shop By section of the catalog home page. |
Q1 |
|
|
 |
 |
Support for BMEcat FEATURE element With this feature, SAP Ariba solutions support the ARTICLE_FEATURE element within the ARTICLE_FEATURES element in BMEcat catalogs. The ARTICLE_FEATURE element describes the additional features or specifications of an item that help describe and identify the catalog item better. |
Q1 |
 |
|
|
 |
Configuring catalog approval workflow This feature allows the ability to configure a customer realm such that second-level approval of catalog subscriptions is not triggered after the associated catalog content document-level approval requests have been approved by approvers in the CMS. If a customer desires, both levels of approval can be configured as well. |
Q1 |
|
|
 |
 |
Republishing denied catalog content documents This feature is related to whether Catalog Approvals raised based on Approval Lookup feature in CMS. When catalog approval requests are denied, the content document moves to the Approval Denied status. This feature allows catalog content documents that were denied to be republished. A new version is created and rerouted for approval. |
Q1 |
 |
|
|
 |
Catalog approval workflow enhancements With this feature, different approvers can approve different sets of items in a catalog. Catalog Managers can define catalog content approval rules based on lookup files, to group the items in the catalog into separate sets, and assign an individual user (or a group) to each set as an approver. |
Q1 |
 |
|
|
 |
Support for consuming and displaying imported CLID fields Contract line items documents (CLIDs) contents from SAP Ariba Contracts can now be consumed by SAP Ariba Procurement solutions when creating compliance contract requests. They can also be displayed in the catalog search results, purchase requisitions, and all related documents in SAP Ariba Procurement solutions. |
Q1 |
|
|
 |
 |
Spot Buy Catalog
|
|
|
|
|
|
New Spot Buy network seller This feature allows buyers to purchase from Walmart.com through the Ariba Network seller channel on Spot Buy. |
Q2 |
|
 |
|
 |