Describing SAP Ariba 2405 Release Features

• Applicable Products
  • SAP Ariba Buying
  • SAP Ariba Buying and Invoicing

• User Type
  • Buyer
• Enablement Model
  • Customer configured

Users can now copy non-PO invoices in guided buying. Copying invoices allows users to quickly create new invoices using the same information as an existing invoice, such as line items, tax, split accounting, invoice header fields, and custom fields.

By default, when you copy an invoice, the invoice number copies onto the new invoice. If you want a new invoice number to automatically generate on the new invoice, your administrator must configure the following parameter in Ariba Administrator under the Intelligent Configuration Manager → Manage Configurations:

• Automatically generate invoice number on copied non-PO invoice (Application.GuidedBuy.AutoGenerateInvoiceNumberForCopyInvoice)

With this feature, users can copy existing non-PO invoices in guided buying and use the information of the copied invoice to create new invoices.

Comments, attachments, and the approval flow from the previous invoice don’t copy onto the new invoice.

Invoices created using a form cannot be copied.

The feature enhanced the Non-PO Invoice capability with the addition of a Copy Invoice functionality in guided buying. Invoice created in Buying and Invoicing can also be copied in guided buying.

When this feature is enabled, the Copy button displays on non-PO invoices after they've been submitted.

To enable this feature, go to Admin → Manage Parameters and enable the following parameter:

PARAM_ENABLE_COPY_NON_PO_INVOICE

Displays a Copy button on non-PO invoices in guided buying after they’ve been submitted.

If set to true, the Copy button displays on non-PO invoices.

If set to false (default), the Copy button doesn’t display on non-PO invoices.

• Applicable Products
  • SAP Ariba Buying
  • SAP Ariba Buying and Invoicing

• User Type
  • Buyer
• Enablement Model
  • Customer configured

When suppliers that have purchasing contracts respond to RFQs, they need to know the contract numbers to provide accurate quotes. Guided buying can now include those numbers when users create RFQs, so suppliers can see them when they view events.

When users create RFQs, guided buying displays a new Selected contract(s) section that lists valid contracts for each preferred and qualified supplier.

If a valid contract is available, guided buying includes its number in the RFQ, as illustrated below.

To enable this feature, go to Admin → Manage Parameters and set the following parameter:

PARAM_ENABLE_CONTRACT_SELECTING_RFQ

Enables guided buying to include purchasing contract numbers in RFQs so the supplier can view them in events to provide more accurate quotes.

If set to false (default), guided buying doesn't include contract numbers in RFQs.

If set to true, guided buying lists valid contracts for preferred and qualified suppliers in RFQ forms and automatically includes their numbers in submitted RFQs. For each preferred or qualified supplier that the user invites, guided buying selects the contract that fulfills the following conditions:

• The contract is for a commodity.
• The contract’s commodity code is the same as an RFQ line-item’s commodity code.
• The contract’s end date is later than the RFQs Respond by date.

If multiple contracts match, guided buying selects the one with the latest contract-expiration date or contract-creation date.

Guided buying sends the contract number to the supplier as a fixed term in the line item in the RFQ. Later, it appears in the quote from the supplier, and at the line-item level when the user creates a requisition from the quote.

• Applicable Products
  • SAP Ariba Buying
  • SAP Ariba Buying and Invoicing

• User Type
  • Buyer
• Enablement Model
  • Customer configured

This feature allows you to choose which user's currency is used for header-level costs on purchase requisitions: requester's or preparer's. Previously, requisitions might have been submitted with two different currencies in header-level costs. If the requester and preparer used different currencies, header-level costs displayed two different currencies. Now, On Behalf Of (OBO) requisitions can default to the preparer's or requester's currency.

When this feature is enabled, OBO requisitions use the requester's currency for header-level costs. In the following figure, Total cost, Discount, Taxes,and Charges use the requester's (user with initials GH) currency: USD (United States dollar).

If this feature isn't enabled, OBO requisitions use the preparer's currency for header-level costs. In the following figure, Total cost, Discount, Taxes, and Charges use the preparer's (user with initials AR) currency: SEK (Swedish krona).

To use the requester's currency for OBO requisitions, enable the Display the total amount of a purchase requisition in the requester’s local currency (Application.Purchasing.DisplayTotalAmountOfPurchaseRequisitionInRequesterLocalCurrency) parameter in the Intelligent Configuration Manager (ICM).

This feature doesn't apply to the following scenarios:

• Purchase requisitions for services.
• Purchase requisitions created before enabling this feature.

Previously, if the first line-item currency was different from the user's currency, header-level costs used two different currencies; the following figure demonstrates this scenario. Header-level costs (Charges, Taxes, Discounts, Net amount) use the first line item's currency: AED currency (United Arab Emirates Dirham), but the Total cost uses the user's currency: USD (United States Dollar).

Now, all header-level costs (Charges, Taxes, Discounts, Net amount and Total cost) default to the user's currency (USD) regardless of the first line item's currency.