Describing SAP Ariba 2505 Release Features

You must ensure the following:

• The ICM parameter Use single-use virtual cards to pay suppliers (Application.Common.SupportsvCardBasedOrder) parameter is enabled in your environment.
• The Use ad hoc vendors for non-catalog items (Application.Common.UseAdHocVendorsForNonCatalogItem) parameter is enabled in your environment.
• The ad hoc vendors are enabled with virtual card support.

Use the following GHS codes in your CIF or cXML catalog file to display the associated hazardous material symbols for this feature.

When this feature is enabled, hazardous material information displays in the following places:

• Hazardous Material Information on the Item Details Page
• Hazardous Material Information in the Search Results
  Note

  When an item contains multiple hazardous materials, the generic hazardous material symbol displays and you can hover over it to view all the hazardous materials types present.
  

Set the following existing guided buying parameters to true:

• PARAM_ENHANCED_PRODUCT_DETAIL_VIEW
• PARAM_ENABLE_IMPROVED_SEARCH_EXPERIENCE
• PARAM_ENABLE_IMPROVED_SEARCH_EXPERIENCE_2
• PARAM_ENABLE_HAZARDOUS_MATERIAL_CLASSIFICATION

You configure hazardous material details when you load your suppliers' catalogs in your SAP Ariba Buying solution. To configure this feature, do the following:

1. Work with your SAP Ariba Catalog Expert to implement the new extensible type HazMatClassification, including all the fields required for the new item type. The following type definition file displays the new extensible type HazMatClassification:
   Code Snippet

   Copy codeSwitch to dark mode

   1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162
   <TypeDefinition>
   <TypeProvider name="System">
   <OrganizationID>
   <Credential domain="NETWORKID">
   <Identity>2</Identity>
   </Credential>
   </OrganizationID>
   </TypeProvider>
   <Comments/>
   <Type name="CatalogItem" extends="System:CatalogItemInternal">
   <Name xml:lang="en-US">Catalog Item</Name>
   <Name xml:lang="fr">Article de Catalogue</Name>
   <Name xml:lang="de">Katalogeinzelteil</Name>
   <Description xml:lang="en-US">Type describing Supplemental attributes of any catalog item data</Description>
   <TypeAttribute name="HazMatClassification" type="Name" isRefinable="yes" isSearchable="yes" isCollection="yes">
   <Name xml:lang="en_US">HazMatClassification</Name>
   <EnumerationValue>
   <Name xml:lang="en_US">GHS01</Name>
   <Extrinsic name="CanonicalValue">GHS01</Extrinsic>
   </EnumerationValue>
   <EnumerationValue>
   <Name xml:lang="en_US">GHS02</Name>
   <Extrinsic name="CanonicalValue">GHS02</Extrinsic>
   </EnumerationValue>
   <EnumerationValue>
   <Name xml:lang="en_US">GHS03</Name>
   <Extrinsic name="CanonicalValue">GHS03</Extrinsic>
   </EnumerationValue>
   <EnumerationValue>
   <Name xml:lang="en_US">GHS04</Name>
   <Extrinsic name="CanonicalValue">GHS04</Extrinsic>
   </EnumerationValue>
   <EnumerationValue>
   <Name xml:lang="en_US">GHS05</Name>
   <Extrinsic name="CanonicalValue">GHS05</Extrinsic>
   </EnumerationValue>
   <EnumerationValue>
   <Name xml:lang="en_US">GHS06</Name>
   <Extrinsic name="CanonicalValue">GHS06</Extrinsic>
   </EnumerationValue>
   <EnumerationValue>
   <Name xml:lang="en_US">GHS07</Name>
   <Extrinsic name="CanonicalValue">GHS07</Extrinsic>
   </EnumerationValue>
   <EnumerationValue>
   <Name xml:lang="en_US">GHS08</Name>
   <Extrinsic name="CanonicalValue">GHS08</Extrinsic>
   </EnumerationValue>
   <EnumerationValue>
   <Name xml:lang="en_US">GHS09</Name>
   <Extrinsic name="CanonicalValue">GHS09</Extrinsic>
   </EnumerationValue>
   <Extrinsic name="inSearchView">yes</Extrinsic>
   <Extrinsic name="inDetailView">yes</Extrinsic>
   </TypeAttribute>
   <TypeAttribute name="CnC" type="Flag">
   <Name xml:lang="en_US">Click and Collect</Name>
   <Extrinsic name="inDetailView">yes</Extrinsic>
   </TypeAttribute>
   </Type>
   </TypeDefinition>
   

2. Extend the type definition files that contains the HazMatClasification attribute with the GHS codes (GH01, GH02, etc.). Upload your CIF or cXML catalog with the new attribute. The following customer catalog includes items with the hazardous material attributes:
   Code Snippet

   Copy codeSwitch to dark mode

   123456789101112
   CIF_I_V3.0
   LOADMODE: F
   SUPPLIERID_DOMAIN: buyersystemid
   COMMENTS: Generated on Thu Mar 20, 2025
   UNUOM: TRUE
   CURRENCY: USD
   CHARSET: UTF-8
   FIELDNAMES: Supplier ID, Supplier Part ID, Manufacturer Part ID, Item Description, SPSC Code, Unit Price, Unit of Measure, Lead Time, Manufacturer Name, Supplier URL, Manufacturer URL, Market Price, Currency, PunchOut Enabled, Supplier Part Auxiliary ID, Language, Parametric Name, Parametric Data, Expiration Date, Effective Date, Classification Codes, Territory Available, Short Name, IsPartial, IsInternalPartId, Delete, Image, Thumbnail, InKitOnly, PunchoutLevel, DefaultRelevance, Price Unit Quantity, Price Unit, Unit Conversion, Price Unit Quantity Description, Promotion Rank, Is Preferred Item, storagelocations, plant, cnc, hazmatclassification, stockidentifier, materialnumber, materialgroup, green, bestprice, hazardousmaterials
   DATA
   "sid496","Part123","Part123","Monitor Adapter",,"222.22","EA","13","Hallmark Cables","s.html","config/SampleImages/hallmark_cables.html","34","USD","false",,"en_US",,,,,"{UNSPSC=43211800;}",,,"false","false","false",,,"false",,,,,,,,"false",,,"false","(ghs01,ghs02,ghs03,ghs04,ghs05,ghs06,ghs07,ghs08,ghs09)",,,,"false","false","true"
   ENDOFDATA
   

   Hint

   Follow these guidelines when implementing this new attribute type:

   • Only use the GHS code in your CIF or cXML catalog, not the GHS code name.
   • Only use English for the HazMatClassification type attribute.
   • The symbols used to identify each type of hazard cannot be changed as per European Union (EU) laws.

   For more information on configuring your catalog, see Customer Catalogs in Guided Buying.

Administrators enable WalkMe for their organization. SAP Ariba will enable it for all customers in a future release, but administrators will have the ability to disable it.

Organizations can configure WalkMe to display custom content by first purchasing WalkMe Premium for SAP Ariba and developing their own content.

WalkMe works in conjunction with SAP Companion and the Guided Buying Help Community. You can enable it while you use those other help systems.

WalkMe is controlled by new parameters in the Admin→Manage parameters page:

• PARAM_ENABLE_WALKME

  ID	Default Value
  PARAM_ENABLE_WALKME	false

  Enables the WalkMe Digital Adoption Platform for all users and shows the question mark icon for displaying the WalkMe panel.

  If set to false (default), the WalkMe question mark and content do not display.

  If set to true, the WalkMe question mark and content display to all users.

• PARAM_WALKME_CUSTOMER_SYSTEM_URL

  ID	Default Value
  PARAM_WALKME_CUSTOMER_SYSTEM_URL	(empty)

  Optionally specifies the URL of custom WalkMe content that was developed in WalkMe Premium for SAP Ariba. For more information, see https://www.walkme.com.

  If this parameter is empty (default), WalkMe displays standard content.

  If this parameter contains the URL of premium content, WalkMe displays custom content to all users. You must also set the parameter PARAM_ENABLE_WALKME. The URL you enter must have the form https://*.walkme.cloud.sap/*.

• PARAM_ENABLE_WALKME_ANALYTICS

  ID	Default Value
  PARAM_ENABLE_WALKME_ANALYTICS	true

  Enables the collection of WalkMe analytical data.

  WalkMe collects a small amount of data that it uses for internal analytics. SAP uses the information derived from these analytics to develop better, more intuitive features and flows. However, you might prefer not to send analytical data.

  If set to true (default), WalkMe collects the following data from each user session:

  Description	Purpose
  Unique User Identifier	Unique identifier
  Timezone	Static data
  Device type	Static data
  Browser name and version	Static data
  Operating system	Static data
  Display height	Static data
  Display Width	Static data
  Session ID	Generated identifier for the visit
  Page URL	The URL in which the event occurred
  Page title	The page in which the event occurred
  WalkMe account ID	The identifier of the system that sent the event
  WalkMe environment	The context that sent the event (such as Production or Test)
  WalkMe end user ID source	Method of extracting EUID (Identifier, Generated, Cache)

  If set to false, WalkMe collects no analytical data.

To understand the process flow for setting up SAPO buyer account for embedded virtual cards, refer to Buyer Account for the Virtual Card Account – Process Flow.

1. To use single-use embedded virtual cards to pay suppliers, you must first set up an SAP buyer account for embedded virtual cards.

   For more information, refer to the following topics:

   • SAP Buyer Account for Virtual Cards
   • Setting Up a Buyer Account for a Virtual Card
   • Viewing Details of a Virtual Card Account for Buyers
   • Modifying the Details of a Buyer Account for the Virtual Card

2. Then, you can send the following master data that needs to be sent from the SAP Ariba buying solution to SAP:

   • Buying organization
   • Suppliers

   For more information, refer to the following topic: Master Data to SAP

3. After the successful transfer of master data, you can enable the support of embedded virtual cards to suppliers.

   For more information, refer to the following topics:

   • Enabling Virtual Card Support for New Suppliers
   • Enabling Virtual Card Support for Existing Suppliers

To understand the process flow for procuring items using a virtual card order (VCO), refer to Procurement Using a Virtual Card Order – Process Flow.

1. To buy catalog or non-catalog items and pay for them using embedded virtual cards, you can create a purchase requisition for the items you want to buy. In the requisition, you can specify a supplier enabled with the support of the embedded virtual card. Then you can create a purchase order using the purchase requisition. This purchase order is known as a virtual card order (VCO).

   For more information, refer to the following topics:

   • Virtual Card Order
   • SAP Ariba Virtual Card Order Method

2. After the supplier receives VCO in the supplier’s account in SAP Business Network, the buyer sends the request for the embedded virtual card to SAP. Then, SAP contacts the card provider, and the card provider contacts the buyer's bank. Then, the card provider shares the embedded virtual card number for the virtual card order with the supplier.

   For more information, refer to the following topic: Virtual Card Details for Suppliers

To understand the process flow for charge reconciliation and payment, refer to Charge Reconciliation and Payment – Process Flow.

• After the successful delivery of goods to buyers, the supplier charges the embedded virtual card of the buyer. Then, you can import the charge that the bank paid to the supplier using a .csv file, create a reconciliation document, perform reconciliation against the VCO, and export the embedded virtual card charge payment request to your ERP system.

  For more information, refer to the following topics:

  • Charge a Virtual Card and Perform Charge Reconciliation Against the Virtual Card Order
  • Importing Charges
  • Viewing the Details of Virtual Card Charges
  • Creating the Virtual Card Charge Reconciliation Document
  • Reconciling Charges
  • Exporting Virtual Card Charge Payment Requests to the Buyer's ERP system

Enable the ICM parameter Export Virtual Card Charge Payment Requests.

To set up an SAP buyer account for embedded virtual cards, the buyer administrator must be part of the Virtual Card Manager group.