Learn, Practice, and Improve with SAP C_ARSUM_2404 Practice Test Questions

Explanation:

When a survey-based KPI is left unmapped in a Supplier Performance Management (SPM) template, it means no automatic data source (like a survey question) is linked to it. As a result, the system cannot auto-populate a score. The KPI will appear on the generated scorecard as a manual entry field, allowing the scorecard owner or evaluator to input a value or rating directly based on their judgment or offline information.

Why other options are incorrect:

A (Tasks display an error):
No error occurs. Unmapped KPIs are a valid configuration; the system defaults to manual scoring.

B (Score of 0% is assigned):
The system does not automatically assign a zero. It leaves the score blank until manually entered.

C (Message: lower than Target Grade):
This type of message typically appears for mapped KPIs where the actual score is compared to a target. An unmapped KPI has no actual score to compare until manually entered.

Reference:
SAP Ariba SPM documentation on "Configuring KPIs and Scorecards" states that unmapped survey-based KPIs require manual score entry on the scorecard. This is a standard design for flexibility when quantitative survey data is unavailable.

Explanation:

In SAP Ariba Supplier Performance Management, KPI definitions and their target values are master data governed centrally to ensure consistency. The sourcing library serves as the single source of truth for reusable performance content. When a contractual KPI target changes (e.g., on-time delivery increases to 96%), the KPI library content document must be updated. This ensures the revised target is automatically inherited by all future performance projects, templates, and recurring reviews that reference that KPI, enforcing standardization and eliminating manual, error-prone updates across multiple projects.

Why other options are incorrect:

A (Master survey/scorecard in the SPM project):
This modifies only the active project instance, not the master definition. Future recurring reviews or new projects would still use the old target.

C (Survey/scorecard for the next recurrence):
This only updates the next cycle of that specific project series, but does not update the central KPI definition for use in other templates or new supplier performance projects.

D (SPM project template):
While templates pull from the library, editing a target directly in a template breaks the link to the library, creating a local copy. This defeats governance, as future library updates won't propagate to that template.

Reference:
SAP Ariba best practices for performance management are documented in the Supplier Performance Management Administration Guide, specifically the section “Managing Performance Content in the Sourcing Library.” It states that KPI definitions, including targets, should be maintained in the library to ensure consistent reuse and automatic updates across the performance management lifecycle.

Explanation:

The template upgrade feature in SAP Ariba Supplier Management allows you to apply updates from a revised template to an already-launched supplier project (e.g., a qualification or performance project). Specific safeguards ensure the upgrade is practical and doesn’t disrupt work in progress.

B is correct – The supplier organization is active.
The supplier must be in an Active status within the Supplier Master to be eligible for a project template upgrade. Archived or inactive suppliers cannot have their projects updated via this feature, as they are no longer part of the active supplier lifecycle.

C is correct – None of the project’s tasks have started OR all of the project’s tasks have completed.
This condition ensures the upgrade is applied only when it will not interfere with ongoing work. If no tasks have started, the project is still in a setup phase and can be safely updated. If all tasks are already completed, the upgrade can be applied for historical or archival consistency. Upgrading a project with tasks in progress is blocked to prevent data loss or workflow disruption.

Why A and D are incorrect:

A is incorrect – The supplier has at least one qualification.
A supplier’s existing qualifications are irrelevant to the technical ability to upgrade a project template. The upgrade mechanism depends on the project’s task status and the supplier’s system status (active/inactive), not on their prior qualification history.

D is incorrect – Updates to project questionnaires pass a system significance check.
While questionnaire changes are validated during the template design phase, the upgrade process itself does not perform a “system significance check” as a formal gate. The system focuses on structural compatibility and task status, not on evaluating the business significance of content changes.

Reference:
These conditions are documented in SAP Ariba Supplier Management guides on “Managing Project Templates” and “Upgrading Projects from Templates.” Refer to the official help portal or administration guide for the section detailing “Upgrading existing supplier projects when a template changes.”

Explanation:

The mass registration invitation feature in SAP Ariba Supplier Lifecycle supports controlled, phased (waved) onboarding. You can import all supplier master records at once via a spreadsheet or integration, but then manage the invitation process in batches using separate invitation files or waves. This allows the customer to control the volume of invitations sent out at a given time, preventing email overload and managing internal support capacity.

Why other options are incorrect:

B (Register on behalf):
This bypasses supplier self-registration entirely, which is not scalable for a large legacy group and defeats the purpose of having suppliers maintain their own profiles.

C (Import smaller groups sequentially):
This is inefficient and delays the overall process, as each group must fully register before importing the next. The system supports mass import with controlled invitation timing.

D (Ask suppliers to register for AN first):
This reverses the proper workflow. Suppliers should be invited through Ariba Supplier Lifecycle, which then triggers Ariba Network account creation. Asking them to register first can cause confusion and matching issues.

Reference:
SAP Ariba Supplier Management implementation guides on "Mass Onboarding" recommend loading all suppliers into the system first, then using "Manage Invitations" or "Upload Invitation List" features to send invitations in controlled waves. This is documented under supplier data import and invitation management.

Explanation:

Within the supplier request approval task in SAP Ariba Supplier Lifecycle, approvers have a specific "Request Additional Info" action. This returns the request to the original requester with comments, allowing them to provide missing details or clarification. The request remains in a pending state until the requester updates it, after which it routes back to the same approver. This is the standard, direct workflow for obtaining missing information without altering the approval chain.

Why other options are incorrect:

A (Use message board):
While the message board exists for collaboration, it is not the formal, system-tracked method for halting an approval for missing data. It also does not automatically return the request to the requester.

B (Invite supplier to complete request form):
The supplier request is an internal form filled out by an employee. Suppliers cannot access it. Supplier involvement begins only after approval, via a registration invitation.

D (Escalate to requester’s supervisor):
Escalation is for bypassing or adding higher-level approvers, not for obtaining missing information. It changes the approval flow, which is unnecessary if the original requester can provide the needed details.

Reference:
The "Request Additional Info" feature is documented in SAP Ariba Supplier Management user guides under "Approving Supplier Requests" or "Supplier Request Workflow Actions."

Explanation:

The Qualification area in the Supplier 360° view is the central workspace for managing a supplier’s category-specific qualifications (e.g., "IT Hardware", "Facilities Services") within the Supplier Lifecycle process.

A is correct – View the current status of qualifications started for the supplier.
This area displays a list or dashboard of all qualification projects associated with the supplier, showing each one’s current status (e.g., In Progress, Qualified, Expired, Disqualified), enabling quick status tracking.

B is correct – Start the requalification process for disqualified and expired categories.
For categories where a supplier’s qualification has expired or been disqualified, the Qualification area provides an action (e.g., "Requalify" or "Start New Qualification") to initiate a new qualification project for that category, restarting the evaluation process.

Why C and D are incorrect:

C is incorrect – Review approval comments for the supplier’s registration.
Registration approval comments are part of the Supplier Registration workflow, not category qualification. These are viewed in the Registration or Overview section of the Supplier 360, not within the dedicated Qualification area.

D is incorrect – Add a preferred category status for an existing qualification.
Preferred Supplier status is a segmentation attribute typically managed in the Supplier Segmentation or Supplier Master area, not within the Qualification workspace. The Qualification area focuses on compliance/eligibility status (Qualified/Not Qualified), not commercial segmentation like "Preferred."

Reference:
These functions are outlined in the SAP Ariba Supplier Management user guide under “Working with Supplier Qualifications” or “Using the Supplier 360° View.” The Qualification section is specifically for tracking and initiating category-based qualification projects.

Explanation:

Pre-grading automates the calculation of KPI scores based directly on quantitative responses from surveys or integrated data sources. By defining grading scales (e.g., 95–100% = "A") in the KPI setup, the system automatically assigns grades/scores without manual evaluator intervention. This increases process automation, reduces subjective bias, speeds up evaluation, and ensures consistency.

Why other options are incorrect:

B (Enables the Target Grade option):
Target Grade is a separate configuration used for comparison against actual scores. It functions independently of pre-grading.

C (Allows weight values higher than 100):
Weighting is configured in the scorecard structure. Total category weights typically sum to 100%; pre-grading does not affect weighting rules.

D (Allows team members to provide grading input):
This describes collaborative grading or manual evaluation, which is the opposite of pre-grading. Pre-grading automates scoring, reducing manual input.

Reference:
SAP Ariba SPM documentation on “Configuring KPIs and Grading” explains that pre-grading automates score calculation from survey data, enhancing efficiency and standardization.