C_S4CPS_2302 · Question #63
Which feature does Guided Buying Capability with SAP Ariba Buying (2NV) support?
The correct answer is B. Transfer of note texts and customer-specific fields in requisitions from SAP Ariba Buying to SAP. Option B is correct because the Guided Buying Capability with SAP Ariba Buying (2NV) specifically supports the transfer of note texts and customer-specific (extensible) fields when requisitions flow from SAP Ariba Buying into SAP S/4HANA - this data mapping is a core feature of…
Question
Which feature does Guided Buying Capability with SAP Ariba Buying (2NV) support?
Options
- AEditing a guided buying purchase requisition in SAP S/4HANA Cloud to add a new line item
- BTransfer of note texts and customer-specific fields in requisitions from SAP Ariba Buying to SAP
- CSupplier collaboration and request for proposals for lean services items in Ariba Guided Buying
- DTransfer of attachments at the header level of requests in Ariba
How the community answered
(27 responses)- A4% (1)
- B89% (24)
- D7% (2)
Explanation
Option B is correct because the Guided Buying Capability with SAP Ariba Buying (2NV) specifically supports the transfer of note texts and customer-specific (extensible) fields when requisitions flow from SAP Ariba Buying into SAP S/4HANA - this data mapping is a core feature of the integration scope.
Why the distractors are wrong:
- A is incorrect because requisitions transferred from Ariba Guided Buying into S/4HANA are read-only in S/4HANA; users cannot add new line items on the S/4HANA side.
- C is incorrect because supplier collaboration and RFP functionality for lean services belongs to SAP Ariba Sourcing scope, not the Guided Buying–to–S/4HANA integration.
- D is incorrect because the 2NV integration does not support attachment transfer at the header level; attachment handling in this integration is limited or handled at the line/item level.
Memory tip: Think of 2NV as a "data pipeline" from Ariba to SAP - its job is to faithfully carry requisition content (notes, custom fields) across the boundary. Anything that requires back-editing in S/4HANA (A) or involves sourcing workflows (C) or header attachments (D) falls outside that pipeline's scope.
Topics
Community Discussion
No community discussion yet for this question.