In SAP Ariba Supplier Risk and broader procurement integration,master datarefers to the foundational data required to properly configure and run the system. This data is typically imported from the customer's existing ERP or sourcing systems during initial setup or data integration processes.
Two essential types ofrequiredmaster data include:
User Groups:User group data is vital for assigning roles and access within SAP Ariba, including permissions for engagement requests, risk assessments, approvals, and data visibility. User groups help determine who can perform specific actions, such as managing risk controls or viewing supplier information.
Suppliers:Supplier master data is a core requirement for the system to evaluate risk. Without supplier data, the system cannot create supplier 360° profiles, run risk exposure calculations, or trigger risk assessments. Supplier information includes company identifiers, addresses, regions, categories, and contact data.
Whilehistorical spend data(Option C) andpayment terms(Option D) may be useful for procurement analytics and transactional processes, they arenot mandatory master data elementsrequired for SAP Ariba Supplier Risk to function.
Extract Reference from SAP Documentation:
“Import site master data including commodity, region, department, user, and risk master data…”
“Importing supplier data... is a prerequisite to evaluating supplier risk and enabling engagement projects.”
—Understanding SAP Ariba Supplier Risk.docx
—SupplierRiskSetup (2).pdf – Importing Supplier-Related Data in SM Administration
Therefore:
A is correct because user groups are essential for permissions and project role assignments.
B is correct because supplier data is foundational to risk evaluation.
C is incorrect because historical spend is optional and more relevant to spend analysis.
D is incorrect because payment terms are relevant for invoicing, not for supplier risk setup.
Reference Documents Used:
Understanding SAP Ariba Supplier Risk.docx
SupplierRiskSetup (2).pdf – Master Data Import Sections
SAP Ariba Integration Guidelines and Best Practices
Submit