SAP Ariba P2P Certification

Interested in FI/CO Video Training? Click here for a free 30 minute Video

SAP Ariba P2P Certification Exam Questions with Answers & Explanations -Online Quiz

SAP Ariba P2P Certification Exam Questions

These questions are similar to the ones asked in the actual Test.

How should I know?  I know, because although I got my SAP Ariba P2P Certification five years back, I have re-certified with the latest version of the Associate Certification test.

Before you start here are some Key features of the SAP Ariba P2P Certification Exam

– The exam is Computer based and you have three Hours to answer 80 Questions.

– The Questions are (mostly) multiple choice type and there is NO penalty for an incorrect answer.

– Some of the Questions have more than one correct answers. You must get ALL the options correct for you to be awarded points.

– The Official Pass percentage is 65% (But this can vary). You will be told the exact passing percentage before your begin your test.

Sample Questions

1. Which of the following statements are true regarding Auto-Selection Reevaluation?

Please choose the correct answer.

a. Auto-selection cannot be triggered after a contract has been attached to a requisition

b. Reevaluation will only occur as long as the requisition is not in ordered state

c. Reevaluation may cause a price change, a contract to be detached, or a new contract to be attached

d. Only b and c

e. All of the above

Answer: d

Explanation:

Auto-Selection Reevaluation

Can be triggered after a contract has been attached to a requisition

  • Requisition must not yet be in Ordered state
  • Item prices may change
  • A different contract may be attached
  • No contract may be attached

Auto-selection can also be triggered after a contract has been attached to a requisition. This feature is referred to as auto-selection reevaluation.

Reevaluation will only occur as long as the requisition is not in ‘Ordered’ state. Reevaluation may cause a price change, a contract to be detached, or a new contract to be attached. This is necessary because a requisition may take a long enough time to process such that there is a change in the relevant contracts.

2. For Punchout Requisition Item Type, discount may be applied to which of the following contract types?

Note: There are 3 correct answers to this question.

a. Supplier Level

b. Commodity Level

c. Item Level – Catalog

d. Item Level – Non-Catalog

e. Header Level

Answer: a, b, d

Explanation:

Auto-Selection Release and Discount:

The system attaches a contract to a requisition line item either via the manual or the auto-selection release methods.

When the system attaches a contract to a requisition line item, this does not guarantee that a price discount will be applied.

The system determines whether the discount is applicable based on the type of requisition line item. There are three different possibilities:

  • Catalog Item – the item exists in a local system catalog
  • Punchout Item – the item exists in an external, supplier-managed catalog
  • Non-Catalog Item – the item does not exist in a local catalog

The table below indicates the rules which determine pricing. Check marks identify the scenarios when the discount is applied.

3. In which of the following cases can Catalogs be used?

Note: There are 2 correct answers to this question.

a. The number of items is relatively higher

b. Changes/Updates to items and pricing is frequent

c. Training business resources with new system is possible

d. If the contract owner has ownership of the contract pricing terms

Answer: a, b

Explanation:

Release Order Contract or Catalog?

There is some overlap in the functionality of catalogs with functionality available through release order contracts. The below diagram has some guidelines for when it makes the most sense to use a contract versus a catalog.

4. Accumulators allow the system to determine which of the following?

Note: There are 3 correct answers to this question.

a. When to notify users that a contract is approaching its limit

b. When to reopen a contract based on limits and tolerances

c. When to apply a cumulative tiered pricing discount to an item

d. When to reload a catalog subscription to remove a non-catalog item when its tolerance is exceeded

e. When to keep a contract on hold based on limits and tolerances

Answer: a, c, d

Explanation:

Accumulators Overview

Contract Accumulators are fields used by Ariba Contract Compliance to track the quantities and amounts that are released and invoiced against contracts.

Accumulators are automatically updated by certain triggers to provide an accurate balance at all times.

Accumulators allow the system to determine:

  • When to notify users that a contract is approaching its limit
  • When to close a contract based on limits and tolerances
  • When to apply a cumulative tiered pricing discount to an item
  • When to reload a catalog subscription to remove a non-catalog item when its tolerance is exceeded

The detailed configuration of accumulators allows an organization to track contract spend at different points in the process based on the business requirements.

5. Which of the following statements are true regarding Preload Accumulators?

Note: There are 3 correct answers to this question.

a. The preload amount field lets users specify an amount of prior spend against an existing contract

b. Preload amounts are tracked at the header level only

c. They are used to update item or commodity level accumulators

d. They only affect pricing discounts in supplier level contracts

e. They affect tiered pricing calculation in all types of contracts

Answer: a, b, d

Explanation:

Preload Accumulators

  • Used to indicate prior spend against existing contracts
  • Tracked only at the header level
  • Affect spend accumulation and tiered pricing only in supplier level contracts

 

The preload amount field lets users specify an amount of prior spend against an existing contract.

Preload amounts are tracked at the header level only, and are not used to update item or commodity level accumulators. For this reason, they only affect pricing discounts and tiered pricing calculation in supplier level contracts.

6. Which of the following statements are true regarding Accumulator Updates?

Please choose the correct answer.

a. In contracts for which invoicing is enabled, invoicing-related accumulators are updated when invoice reconciliation documents are approved

b. In contracts for which receiving is enabled, receiving-related accumulators are updated when receipts are processed.

c. Both a and b

d. None of the above

Answer: c

Explanation:

Preload Accumulators:

The preload amount field lets users specify an amount of prior spend against an existing contract.

Preload amounts are tracked at the header level only, and are not used to update item or commodity level accumulators. For this reason, they only affect pricing discounts and tiered pricing calculation in supplier level contracts.

Accumulator Updates:

  • Invoice related accumulators updated when invoice reconciliation is approved
  • Receiving related accumulators updated when receipts are processed

In contracts for which invoicing is enabled, invoicing-related accumulators are updated when invoice reconciliation documents are approved.

In contracts for which receiving is enabled, receiving-related accumulators are updated when receipts are processed.

7. Which of the following statements are true regarding Agreements without Releases?

Please choose the correct answer.

a. No-release Order Contracts do not allow release orders to be issued against them

b. May allow direct receiving and invoicing

c. Provide additional pricing terms

d. Only a and b

e. All of the above

Answer: e

Explanation:

  • No-release Order Contracts do not allow release orders to be issued against them
  • May allow direct receiving and invoicing
  • Provide additional pricing terms
    • Fixed and Recurring fee items
    • Costs and Expenses
    • Milestones

Agreements without release orders are a good way to manage categories that do not use the typical purchase order process. This is a common need for services contracts as well as those involving facilities and maintenance.

These types of contracts are usually created to allow direct invoicing and receiving. In addition, they provide access to additional pricing terms for fixed and recurring fee items and costs and expenses.

To create an agreement without release orders, set the Release Required? Indicator in the contract request wizard to No.

8. No-release order contracts are typically used for services and need to handle which of the following aspects of service procurement?

Note: There are 3 correct answers to this question.

a. Complexity

b. Deliverables and milestones

c. Recurring and fixed costs

d. Need for more detailed effort analysis

e. Need for more detailed analysis of resource utilization

Answer: a, b, c

Explanation:

No-release Order Contracts:

  • Non-PO process often used for services
  • More complex than PO-based procurement
  • Deliverables and milestones
    • Payment may be based on their completion
  • Recurring and fixed costs
  • Service costs may not be able to be forecast exactly
  • Monitoring more involved:
    • Quality of work, completion of deliverables
    • Services delivered / charged
    • Ongoing payments

No-release order contracts are typically used for services and need to handle the following aspects of service procurement:

  • Complexity – doesn’t fit the standard PO-based procurement process
  • Deliverables and milestones – requires a way to track milestone completion for payment
  • Recurring and fixed costs – requires direct invoicing, sometimes on a recurring schedule
  • Difficulty in forecasting costs – details of what was provided may not be available until work is completed
  • Need for more detailed monitoring – requires ways of tracking quality, completion, what was delivered, what was invoiced, and when to release payment

You can use agreements without release orders for service procurement processes that do not use purchase orders. In addition to service contracts, there are other ways you can use non-release order contracts.

9. Which of the following statement(s) is/are true?

Note: There are 2 correct answers to this question.

a. In the absence of a purchase order, the three-way match becomes Invoice-Contract-Receipt

b. If receiving is enabled, Ariba will perform a two-way match between the Contract and Invoice.

c. When creating a contract without release orders, users can receive directly against the contract

d. If receiving is not enabled, Ariba will perform a three-way match between the Contract, Receipt, and Invoice

Answer: a, c

Explanation:

Invoicing and Receiving Against the Contract

Receiving

When creating a contract without release orders, users can receive directly against the contract. When direct receiving is enabled for a contract, users can receive against items on the contract in much the same way as they receive against items on a purchase order.

Three Way Match

The advantage of enabling invoicing and receiving in non-release order contracts is that it enables you to do three-way matching in the invoice reconciliation process. In the absence of a purchase order, the three-way match becomes Invoice-Contract-Receipt.

If receiving is not enabled you can do a two-way match between the invoice and contract.

10. Which of the following are the approvable documents that are used in contract receiving?

Please choose the correct answer.

a. Receipt

b. Milestone Tracker

c. Both a and b

d. None of the above

Answer: c

Explanation:

Receiving Approvables:

  • Receipt for materials and services
    • Users with Direct Release permission (Contract Managers)
  • Milestone tracker for milestones
    • User selected as verifier for milestone

There are two approvable documents that are used in contract receiving:

Receipt – used to track the receipt of material and service items. This is the same approvable used to track receipts against purchase orders. In order to receive material and service items directly against a contract, a user needs the DirectReleaseContract permission (in the default configuration this is granted to Contract Managers).

Milestone Tracker – used to track completion of milestones. Users may approve milestones when they are selected as the verifier for that milestone.

Specific approval rules determine the approval flow for these two approvables.

 

More Questions? Have a look at:

SAP Ariba P2P Certification Exam Questions with Answers & Explanations