C_ARP2P_2302 V2

Which of the following default invoice exception types occur at line level? Note: There are 2 correct answers to this question.
A . PO Received Quantity Variance
B. PO Price Variance
C. PO Payment Terms Mismatch
D. Invoice Currency Mismatch

View Answer

Answer: A,B

Explanation:

In SAP Ariba, the PO Received Quantity Variance and PO Price Variance are default invoice exception types that occur at the line level. These exceptions are triggered when there is a discrepancy between the invoice and the purchase order in terms of the quantity received or the price, respectively.

PO Payment Terms Mismatch and Invoice Currency Mismatch are not typically line-level exceptions. These exceptions would typically occur at the header level, as they relate to the overall invoice rather than individual line items.

Which data dictates the system behavior for tactical sourcing scenarios?
A . User group assignments
B. Ship-To location
C. Approval flows
D. Supplier policies

View Answer

Answer: B

Explanation:

In tactical sourcing scenarios within SAP Ariba, the Ship-To location data dictates the system behavior. This is because the sourcing and procurement processes can vary significantly depending on the destination of the goods or services.

User group assignments, Approval flows, and Supplier policies do not typically dictate the system behavior for tactical sourcing scenarios.

Which of the following are benefits of using the Spot Buy capability of SAP Ariba Catalog? Note: There are 2 correct answers to this question.
A . It provides commodity-specific requisitioning forms.
B. It increases visibility of low-dollar, one-time purchases.
C. It decreases the number of Non-Catalog requisitions created.
D. It streamlines sourcing for direct materials with high price volatility.

View Answer

Answer: B,C

Explanation:

The Spot Buy capability of SAP Ariba Catalog offers a way to manage ad-hoc, one-time purchases that are not covered by existing contracts or catalogs. This feature increases visibility into these low-dollar, one-time purchases, which are often overlooked in traditional procurement processes.

Additionally, by providing a platform for these purchases, Spot Buy can decrease the number of Non-Catalog requisitions created. This can simplify the procurement process and reduce the administrative burden on procurement teams.

Options A and D (providing commodity-specific requisitioning forms and streamlining sourcing for direct materials with high price volatility) are not typically benefits associated with the Spot Buy capability of SAP Ariba Catalog.

Which supplier master data is shared in a suite-integrated environment in SAP Ariba Buying and Invoicing?
A . Preferred ordering method
B. Tax ID
C. System ID
D. Supplier location

View Answer

Answer: D

Explanation:

In a suite-integrated environment in SAP Ariba Buying and Invoicing, Supplier Location is a piece of master data that is shared. This information is crucial for various processes such as shipping, invoicing, and tax calculations.

The other options (Preferred ordering method, Tax ID, System ID) are not typically shared as master data in a suite-integrated environment.

Which of the following contract types support discount pricing? Note: There are 2 correct answers to this question.
A . Commodity level
B. Supplier level
C. Catalog level
D. Item level

View Answer

Answer: B,D

Explanation:

In SAP Ariba, discount pricing can be applied at the Supplier level, meaning that the discount is applied to all items purchased from a specific supplier. It can also be applied at the Item level, meaning that the discount is applied to a specific item, regardless of the supplier.

Commodity level and Catalog level are not typically used for applying discount pricing in SAP Ariba.

Which transactional data element is a required ERP integration for SAP Ariba Buying and invoice implementations?
A . Payment request
B. Remittance advice
C. Purchase order
D. Receipt

View Answer

Answer: C

Explanation:

In SAP Ariba Buying and Invoicing implementations, Purchase Order is a required transactional data element for ERP integration. Purchase orders are crucial for the procurement process as they represent a legal offer to buy products or services.

Payment Request, Remittance Advice, and Receipt are not typically required data elements for ERP integration in SAP Ariba Buying and Invoicing implementations.

which integration channel do you use if your customer requests real-time transactional data synchronization between ERP and SAP Ariba buying and invoicing?
A . web services
B. File channel
C. SAP direct connectivity
D. EDI

View Answer

Answer: A

Explanation:

Web Services is the integration channel you would use for real-time transactional data synchronization between ERP and SAP Ariba Buying and Invoicing. Web Services allow for real-time, two-way communication between systems, making them ideal for this kind of synchronization.

File Channel, SAP Direct Connectivity, and EDI are not typically used for real-time data synchronization. They are more commonly used for batch processing or other types of data integration that do not require real-time synchronization.

Where can a Guided Buying user select suppliers from when creating a non-catalog item requisition? Note: There are 2 correct answers to this question.
A . A pre-defined list of incumbent suppliers responding to sourcing events
B. A predefined list of preferred suppliers generated by SAP Ariba Supplier Lifecycle and Performance
C. A global pool of supplier organizations available in Buying and Invoicing
D. A global pool of public suppliers available in the Ariba Network

View Answer

Answer: B,C

Explanation:

When creating a non-catalog item requisition in Guided Buying, users can select suppliers from a predefined list of preferred suppliers generated by SAP Ariba Supplier Lifecycle and Performance. This tool helps organizations manage their supplier relationships and performance, and it can generate a list of preferred suppliers based on various criteria.

Users can also select suppliers from a global pool of supplier organizations available in Buying and Invoicing. This pool includes all suppliers that are set up in the SAP Ariba Buying and Invoicing system.

A pre-defined list of incumbent suppliers responding to sourcing events and a global pool of public suppliers available in the Ariba Network are not typically sources from which Guided Buying users can select suppliers when creating a non-catalog item requisition.

Which of the following supplier data is synchronized between SAP Ariba Strategic Sourcing and SAP Ariba Procurement within a suite-integrated realm?
A . Supplier location
B. Partitioned supplier
C. Common supplier
D. Remittance location

View Answer

Answer: C

Explanation:

In a suite-integrated realm, Common Supplier data is synchronized between SAP Ariba Strategic Sourcing and SAP Ariba Procurement. This ensures that supplier information is consistent across both systems, facilitating seamless procurement and sourcing processes.

Supplier Location, Partitioned Supplier, and Remittance Location are not typically synchronized between SAP Ariba Strategic Sourcing and SAP Ariba Procurement in a suite-integrated realm.

Which of the following is the user for whom a document is created on behalf of?
A . Watcher
B. Preparer
C. Requester
D. Project owner

View Answer

Answer: C

Explanation:

In the context of SAP Ariba, the Requester is the user for whom a document is created on behalf of. This could be a purchase order, a requisition, or any other type of procurement document. The Requester is typically the person who needs the goods or services being procured.

The Preparer is the person who creates the document, the Watcher is someone who needs to be informed about the document but doesn’t necessarily take action on it, and the Project owner is typically responsible for overseeing a project, not a specific procurement document.