According toSAP Learning Hub – Course: SAP Ariba Procurement: Buying → Exploring Requisitions, when arequisitionis inSubmittedstatus, only therequestercan perform specific actions to return it toComposingstatus for modification or correction.
The relevant extract and explanation are as follows:
“A requester can return a submitted requisition to Composing status by selectingWithdraworEdit.
SelectingWithdrawremoves the requisition from the approval flow and allows changes before resubmission.
SelectingEditimmediately returns the requisition to Composing status where the user can modify the requisition details.”
FromSAP Learning Hub – Course: SAP Ariba Procurement: Buying → Exploring Catalogs, under the topic“PunchOut Catalogs and Integration Levels”, the official content explains:
“Level 1 PunchOut catalogs connect buyers from SAP Ariba to the supplier’s main catalog site or homepage. Users must perform all browsing and searching within the supplier’s website environment. Level 1 items are not indexed or searchable within SAP Ariba.”
“Level 2 PunchOut catalogs integrate the supplier catalog content into the SAP Ariba search index. This enables users to search and compare PunchOut items directly within the SAP Ariba interface alongside hosted catalog items.”
“When a Level 2 PunchOut item is selected from the search results, the user is directed to the supplier’s specific product or category page through a deep link. This eliminates the need to start from the supplier’s homepage, allowing faster access to relevant items.”
Verified Reference Source (Internal SAP Learning Content)
SAP Ariba Procurement: Buying → Exploring Catalogs
Learning Journey:Procure to Pay with SAP Ariba Buying and Invoicing
Extract from course section:
“Level 2 PunchOut catalogs enhance the user experience by enabling item search within SAP Ariba and supporting direct access to product or category pages on the supplier’s site.”
FromSAP Learning Hub – Course: SAP Ariba Procurement: Buying → Integration Overview, under the section“Supplier Data Sharing Across SAP Ariba Solutions”, the official content explains the concept of supplier master data synchronization betweenSAP Ariba Strategic Sourcing Suite(which includes Sourcing, Contracts, and Supplier Lifecycle and Performance) andSAP Ariba Buying and Invoicing.
“When an organization implements both SAP Ariba Strategic Sourcing solutions and SAP Ariba Buying and Invoicing, the system uses acommon supplier record. The common supplier represents a shared supplier entity across all connected solutions, ensuring data consistency for supplier profiles, identifiers, and key attributes.”
“This Common Supplier integration allows the supplier master data to be synchronized between the Strategic Sourcing applications and Buying and Invoicing. Updates to supplier information such as supplier name, ID, and contact details are reflected across all integrated SAP Ariba solutions, maintaining a single source of truth.”
Verified Reference Source (Internal SAP Learning Content)
SAP Ariba Procurement: Buying → Integration Overview
Learning Journey:Procure to Pay with SAP Ariba Buying and Invoicing
Extract from SAP Ariba Integration documentation:
“Supplier data is shared through aCommon Supplierwhen SAP Ariba Strategic Sourcing and SAP Ariba Buying and Invoicing are deployed together. The Common Supplier ensures master data alignment and prevents duplication between solutions.”
