C_ACDET sample questions & answers

Bressettoni Industriale, an Italian industrial-pump manufacturer, is standing up a sourcing test site before its first guided event. You are the partner consultant applying the configuration baseline. The category team requested a field, Incoterm Override Justification, that must appear on the sourcing event header only when the existing Requires Incoterm Override field is set to Yes; when that control is No, the justification field must stay hidden. You created the justification field, set its label, data type, and help text, and saved it. In testing, the field renders correctly but is always visible regardless of the controlling field's value. The category lead confirms the requirement is a conditional display tied to another field on the same object, not a permanent addition. You verified both fields exist on the same class and that the controlling field already carries Yes and No values. Nothing you set on the field's general properties changed the always-visible behavior. The go-live checklist requires the field to honor the conditional rule before the baseline is shared to the customer's site. Which configuration action correctly enforces the conditional display?

As the consultant preparing the baseline, which configuration action makes the justification field appear only when the controlling field is set to Yes?

Norsk Foredling, a Norwegian seafood processor, is configuring its sourcing test site so that when a category manager selects a Commodity Group on a sourcing project, the Sub-Commodity field offers only the sub-values that belong to that group. You are the consultant. You created both fields as flex master data, loaded the commodity and sub-commodity value sets, and confirmed each value list displays correctly on its own. In testing, the Sub-Commodity field shows the entire sub-commodity catalogue regardless of which Commodity Group is chosen, so category managers can pick mismatched pairs. The data loads are complete and the values are spelled correctly; the problem is that the child field is not narrowing to the parent selection. You verified that both flex master data sets exist on the same realm and that the field configuration references the correct classes. The baseline cannot be shared until the dependent filtering behaves as specified, because mismatched commodity pairings corrupt downstream spend reporting. The customer's spend taxonomy is large, with many sub-commodities under each commodity group, so an unfiltered list also slows category managers down and makes incorrect pairings more likely the longer it stays unresolved. Which configuration action establishes the dependent filtering between the two fields?

As the consultant, which action makes the Sub-Commodity field display only the values related to the selected Commodity Group?

Aurelia Foods, a multinational packaged-foods group, is migrating an existing Strategic Sourcing configuration into an already-live production realm using a bluefield approach. You are the migration consultant. Your plan migrated flex master data, relations, enumerations, and translations, and you imported the field customizations from the source realm. During validation, the new custom fields and relations are present in production configuration, but they do not appear to buyers on sourcing documents, and reports do not yet recognize the new fields. The cutover runbook lists a step for handling data definition changes after configuration is migrated, which has not yet been performed. The base configuration objects migrated without error, and there were no failed Intelligent Configuration Manager packages. Business users are waiting to transact in production, and the project cannot extend the cutover window. You must make the migrated field customizations and relations effective for end users without re-running the entire migration. The cutover team has only a limited number of agreed business-downtime hours, and any approach that means re-importing the full configuration would push the go-live past the window the customer approved. Which action correctly completes the migration so the changes take effect?

As the migration consultant, which action makes the migrated field customizations and relations effective for buyers and reporting in production?

Cobreval Mining, a Chilean copper producer, is extending its sourcing test site so that RFP responses capture three new supplier-entered fields on a form template. You are the consultant building the template. You created the form template, added the three new fields, and attempted to publish it, but publication is blocked and the new fields cannot be activated on the template. Existing fields on the same template behave normally. You confirmed the new field definitions are valid and that the template structure is otherwise correct. Reviewing the template build guidance, you note that fields used in form templates depend on a preparatory step at the database level before they can be bound into a template. The customer's go-live depends on suppliers being able to complete the new fields in their RFP responses, and the test-site baseline cannot be shared while publication fails. Suppliers will begin completing the form within days, and the three fields capture information the category team needs to score responses, so the template cannot simply go live without them. The other fields on the same template, by contrast, published without any difficulty. Which action allows the new fields to be added to the form template and published?

As the consultant, which action lets the three new fields bind into the form template and publish successfully?

Helmsmark Logistics runs a Procurement configuration with a parent realm and several regional child realms for its operating units. You are the consultant asked to add a customer-specific field to a procurement object so it is available consistently across all regional child realms. Working in Customization Manager, you applied the field customization while connected to one regional child realm. The field now appears in that region but is absent in the other child realms, and regional teams report inconsistent forms. Re-applying the change individually in each child realm is being considered, but the customer wants a single, governed definition that all regions inherit, and expects to add two more regions next year. You confirmed the field definition itself is correct and that Customization Manager lists the available classes for the object. Each child realm currently shows slightly different forms to its regional buyers, which has already caused confusion in shared reporting, and the customer's governance team wants one definition it can point to as the source of truth rather than several regional variants that drift apart over time. Which approach correctly delivers the field consistently across the child realms while supporting future regions?

As the consultant, which approach makes the field available consistently across the existing and future child realms from one governed definition?

Velaterra Renewables, a mid-size wind-farm operator, is beginning a Strategic Sourcing deployment and must choose its deployment scenario during the prepare phase. You are the partner consultant. The customer has no existing sourcing configuration and no legacy sourcing data to carry forward; they want to adopt SAP best-practice configuration as closely as possible and reach go-live quickly with minimal custom rework. Their procurement team is small and has limited capacity to validate large volumes of migrated historical data. During the prepare-phase workshop, three directions are debated: starting from the standard solution baseline applied to a fresh test site; lifting an unrelated affiliate's heavily customized configuration; or planning a complex data carry-forward from spreadsheets the team has not validated. The steering committee wants a deployment scenario decision that fits a net-new adopter, supports the SAP Activate prepare-to-deploy path, and avoids unnecessary migration risk. Cost and timeline rise sharply if the scenario forces data validation effort the team cannot staff, and the steering committee is equally wary of taking on configuration the small procurement group will struggle to maintain after go-live. Which deployment scenario should you recommend?

As the partner consultant, which deployment scenario best fits this net-new adopter under the SAP Activate path?