The scenario describes a situation where a custom field's default value is not being re-evaluated after the initial calculation. This behavior can be caused by several distinct configuration settings at different levels.

1. (B) The trigger for re-evaluation is often a screen refresh initiated by the source field. If the dependent field (the one that changes) does not have the Refresh screen on value change property enabled, the system is not prompted to re-run the defaulting logic for other fields.

2. (C) There is a global application parameter, Application.Base.RecomputeValueOnFieldChange, that acts as a master switch. If this parameter is disabled, the system will not re-evaluate field values upon changes in other fields, regardless of individual field settings.

3. (E) The Respect User Value property is designed to preserve manual entries. If this is enabled on the custom field, the system will set the default value initially but will not override it if a user has manually changed it, even if the dependent field's value changes later.

A. "Lock Initial value" is not a standard property in SAP CPQ. The closest equivalent is "Read-Only," which would prevent any change, not just prevent re-defaulting.

D. A validity condition violation would likely result in an error message or prevent the invalid value from being set, rather than silently causing the field to retain its old value.

1. SAP CPQ - Setup and Administration Guide: The guide details the properties of custom fields.

Respect User Value: "If this checkbox is selected

the system won't overwrite the value that a user has manually entered in the field." (This directly supports option E).

Refresh screen on value change: "When this checkbox is selected

the page is refreshed every time a user changes the value of the custom field." (This explains the trigger mechanism required for re-computation

supporting option B).

Reference Location: SAP Help Portal

SAP CPQ Documentation

Setup and Administration Guide

section on "Custom Fields".

2. SAP CPQ - General Application Parameters: This documentation lists system-wide settings that control application behavior.

RecomputeValueOnFieldChange: "When set to True

formulas are re-evaluated when a field value is changed. When set to False

formulas are not re-evaluated on field change." (This directly supports option C as a global cause).

Reference Location: SAP Help Portal

SAP CPQ Documentation

Setup and Administration Guide

section on "General Application Parameters".

When a new custom field is created and marked as reportable, its metadata is not automatically available to the reporting framework. A synchronization process is required to update the reporting schema with the new field definition. The "Retrieve flexible fields metadata for reporting" task is an administrative job specifically designed to perform this synchronization. Running this task manually ensures that the reporting tools recognize and can access the newly created custom field, making it available for inclusion in reports.

A. Wait 2 hours for the schema to refresh automatically.

This is incorrect. While some system jobs are scheduled, there is no guaranteed automatic refresh within a specific timeframe. A manual task is required for immediate availability.

B. Custom fields must be created in the same module where reports are generated.

This is an incorrect architectural assumption. Custom fields are associated with business objects, and as long as they are marked reportable, they can be pulled into reports regardless of the module.

C. You did not assign the custom field to the appropriate report category.

This is not the primary reason. The key step is marking the field as "reportable." The failure to appear in reports is due to a metadata synchronization lag, not a categorization error.

1. SAP Knowledge Base Article 2318769 - Custom fields are not available in Reporting - SAP for Me.

Section: Symptom / Resolution

Content: This KBA directly addresses the issue. The resolution states: "Run the 'Retrieve flexible fields metadata for reporting' job from Reporting Manager to sync the new custom fields to reporting. This job will sync the custom fields created via UI or through data model changes." This confirms that running the specified task is the correct procedure.

2. SAP Help Portal - Implementing and Managing Reporting and Analytics in SAP SuccessFactors HXM Suite

Section: Ad Hoc Report Builder > Enabling Custom Fields for Reporting

Content: The documentation explains that after adding custom fields to the data model and marking them as reportable

a synchronization step is necessary. It details that an administrator must run a job to make these fields visible in the reporting tools

which corresponds to the action described in the correct answer.

The SAP Activate Methodology is structured into distinct phases. The Deploy phase is specifically designed for the final preparation and execution of the system's transition to a live, productive environment. A critical activity within this phase is the cutover, which involves migrating the fully tested and approved configurations, along with necessary data, from the Quality Assurance (QAS) system to the Production (PRD) system. This ensures that the production environment is ready for business operations upon go-live.

A. Migrate: "Migrate" describes an action (data migration, configuration migration) that occurs within the Deploy phase, but it is not the name of the phase itself.

B. Move: This is a generic verb and does not represent an official phase name within the structured SAP Activate Methodology.

D. Push: Similar to "Move," this is a common IT term for deploying changes but is not the formal name of an SAP Activate phase.

---

1. SAP Activate Roadmap Viewer. (2023). SAP Activate Methodology for RISE with SAP S/4HANA Cloud

private edition. SAP SE.

Reference: In the "Deploy" phase

the deliverable "Production System Go-Live" contains the task "Execute Cutover and Go-Live." The purpose of this task is explicitly stated as: "This task covers the execution of the cutover plan to move the business processes and data to the production environment." This includes transporting the final configuration.

2. SAP Help Portal. (2023). Phases in SAP Activate Methodology. SAP SE.

Reference: The documentation for the "Deploy" phase outlines its purpose as setting up the production system

executing the cutover

and transitioning all operations to the new environment. This inherently includes the final migration of configuration.

3. SAP Learning. (2023). SAP Activate for SAP S/4HANA Cloud

public edition - Project Management. SAP SE.

Reference: In the learning journey

the "Deploy and Run" unit details the activities of the Deploy phase. It describes the cutover process where the solution

including all configurations built and tested in the Realize phase

is moved to the production system to prepare for go-live.

The visibility of the "Editable in full Contract Amendment" option within the field configuration's advanced tab is context-sensitive and depends on two primary factors.

First, this setting is specific to the contract amendment lifecycle. Therefore, it will only be displayed for fields that are part of the Contract Workspace (ariba.contract.core.Contract) or Contract Request (ariba.contract.core.ContractRequest) object classes. If the field belongs to any other object (e.g., Sourcing Project), this option is irrelevant and thus not shown.

Second, SAP Ariba distinguishes between standard (system) and custom fields. Many properties of standard fields are locked to maintain system integrity and ensure core processes function as designed. The ability to change editability during a critical process like an amendment is often restricted for standard fields, making this configuration option unavailable.

A. System-level configuration in a template is independent of the status of any single, transactional contract document. The available customization options do not change based on a specific contract being in an amendment state.

B. An in-flight customization might prevent saving or publishing new changes, but it would not typically cause a specific configuration option to be hidden from the user interface.

1. SAP Ariba Contracts Administration Guide: In the sections discussing contract workspace template administration and field configuration

it is specified that amendment-related field properties are exclusive to the contract business objects. The guide states

"Certain field properties are only available for certain types of projects." This supports the conclusion that the field must be in a contract-related class. (Reference: SAP Ariba Contracts Administration Guide

Chapter on "Contract Workspace Template Administration").

2. SAP Ariba Help Portal - "About Custom and System Fields": The official documentation consistently differentiates between the flexibility of custom fields and the restrictions on system (standard) fields. It notes that for system fields

"You cannot edit most of the properties... such as its name

field type

or whether it accepts multiple values." This restriction often extends to advanced behavioral properties like state-based editability. (Reference: SAP Ariba Procurement and Invoicing Help

Section on "Managing Custom and System Fields").

3. SAP Intelligent Configuration Manager (ICM) Documentation: The ICM documentation outlines the object-oriented nature of configurations. Properties available for configuration are dependent on the selected class (e.g.

Contract Workspace). The absence of an option indicates it is not applicable to the selected field's class or that the property is non-configurable for that specific field (a common case for standard fields). (Reference: SAP Ariba Intelligent Configuration Manager Guide

Section on "Field Configuration").

Flex Master Data (FMD) is the standard SAP Ariba framework designed specifically for creating custom master data objects that are not native to the system. This approach allows an administrator to define a new "Storage Location" template with necessary attributes like name and address. Data can then be loaded from the external system into this FMD object. When a custom field is created and its type is set to this new FMD object, it provides users with a rich, searchable chooser, fulfilling all aspects of the customer's requirement for a scalable and user-friendly solution.

A. A text field with a custom validation list is not scalable for data loaded from an external system and provides a poor user search experience.

B. Enumerations are intended for simple, relatively static lists of values, not for complex master data with multiple attributes (like an address) that require searching.

C. A Date field is functionally inappropriate for storing and searching location data; its purpose is to handle calendar dates, not structured master data.

1. SAP Ariba Help Portal

"Common data import and administration guide for SAP Ariba Strategic Sourcing and Supplier Management solutions": In the section "Flexible master data

" the documentation states

"Flexible master data allows you to define custom master data objects with their own fields

import data for them

and refer to them in other business objects... For example

you can create a custom master data object for cost centers and then create a custom field in sourcing projects that refers to it." This directly supports using FMD for custom objects like "Storage Locations."

2. SAP Ariba Help Portal

"Contract Management configuration guide": The section on "Custom fields" details the process of creating custom fields in contract workspaces. It specifies that the "Data Type" for a field can be set to a custom flexible master data object. This enables the creation of a field that links to and allows searching within the custom "Storage Location" data created via an FMD template.

The Intelligent Configuration Manager (ICM) is a tool designed to migrate configuration data between SAP Ariba realms, such as from a test realm to a production realm. It handles objects like templates, custom forms, and AML customizations. SupplierContact represents master data, not configuration data. Master data, such as supplier information, users, and contacts, is managed through separate data import/export processes or integration and is outside the scope of ICM's functionality.

A. DynamicForm — custom form templates (dForms): This is incorrect because DynamicForm is a standard configuration type for custom forms that is explicitly supported for migration by the Intelligent Configuration Manager.

C. AMLExtension — AML customizations such as custom fields: This is incorrect because AMLExtension is a supported configuration type, allowing for the migration of Ariba Markup Language (AML) file customizations between realms.

D. Template — project templates such as Contract templates: This is incorrect because project templates (SourcingProjectTemplate, ContractWorkspaceTemplate, etc.) are a core configuration type that the Intelligent Configuration Manager is designed to migrate.

1. SAP Ariba Help Portal: Intelligent Configuration Manager overview

Reference: In the section "Configuration types supported by Intelligent Configuration Manager

" the documentation provides a comprehensive list of migratable objects. This list includes AMLExtension

DynamicForm

and various Template types (e.g.

SourcingProjectTemplate

ContractWorkspaceTemplate). The list does not include master data objects like SupplierContact. This explicitly confirms that supplier contacts are not a configuration type managed by ICM.

Custom partner bundles are pre-packaged solutions containing best practices, pre-configured processes, and accelerators. They are designed to establish a project baseline, which is a foundational element of the SAP Activate methodology's Fit-to-Standard approach. This approach is central to the Greenfield deployment scenario, where a new SAP system is implemented from scratch. By leveraging a partner bundle, organizations can accelerate their Greenfield project, reduce risks, and adopt standardized processes without the constraints of an existing legacy system.

A. Bluefield: This is a selective data transition approach. While it involves a new system shell, the process is driven by migrating specific historical data and processes, which may not align with a standardized partner baseline.

B. Grayfield: This term typically describes a complex, phased, or hybrid implementation. The inherent complexity and non-standard nature of such a project make it unsuitable for applying a pre-packaged, standardized baseline.

D. Brownfield: This scenario involves a system conversion of an existing SAP system. The focus is on migrating and adapting the current configuration and data, not on replacing it with a new baseline from a partner bundle.

1. SAP Activate Roadmap Viewer: In the "SAP Activate Methodology for RISE with SAP S/4HANA Cloud

private edition

" the Explore phase details the Fit-to-Standard workshops. The procedure notes state

"The initial system for the workshops is based on SAP Best Practices content and additional partner templates." This directly links partner content (bundles/templates) to the methodology used in Greenfield implementations. (Source: SAP Activate Roadmap Viewer

specific task: "Fit-to-Standard Analysis and Design").

2. SAP Help Portal - SAP Activate Methodology: The documentation on implementation strategies clarifies that the "New Implementation (Greenfield)" approach involves starting with a clean system and leveraging pre-configured content like SAP Best Practices. Partner solutions are presented as extensions of this pre-configured content to accelerate deployment. (Source: SAP Help Portal

SAP Activate Methodology

Section: "Transition to SAP S/4HANA").

3. Official SAP White Paper - "Your Transformation Journey to SAP S/4HANA": This document outlines the different transition scenarios. It describes the Greenfield approach as an opportunity to "re-engineer your business processes and standardize them based on modern best practices." Partner packages are a primary vehicle for delivering these pre-configured best practices. (Source: SAP SE

"Your Transformation Journey to SAP S/4HANA" white paper

Section: "The Greenfield or New Implementation Approach").

The import process for form templates in SAP Ariba solutions requires that the folder structure from the source environment (Test) exists in the target environment (Production). The exported package contains metadata that specifies the destination folder path. If this folder does not exist in the Production site, the import operation will fail. The correct and standard procedure to resolve this error is to manually create the necessary folder(s) in the Production site, replicating the structure from the Test site, and then re-attempt the import.

B. Upload the templates to any existing folder regardless of its purpose.

This would lead to an incorrect and disorganized folder structure, potentially causing issues with user permissions, template visibility, and system logic that relies on specific paths.

C. Modify the form template files locally to bypass folder restrictions.

Altering system-generated export files is an unsupported practice that can easily lead to data corruption, import failures, or unpredictable behavior within the application.

D. Skip the import and inform the team the templates cannot be migrated.

This is not a solution. The inability to import is a common and resolvable issue, typically caused by a configuration mismatch between environments, which should be addressed.

1. SAP Ariba Contracts Administration Guide: In the section on "Form Template Management

" the process of importing and exporting templates is detailed. The guide implicitly supports the principle that the target environment must be correctly configured to accept the imported data. A common point of failure in such migrations is the absence of prerequisite structures

such as folders. The import process expects to place the template in a specific path defined in the export file. (Reference: SAP Ariba Contracts Administration Guide

Chapter on "Managing Form Templates").

2. SAP Help Portal - Data Import and Export for SAP Ariba: General documentation on data migration for SAP Ariba solutions consistently emphasizes the need for preparing the target realm (Production) to match the source realm's (Test) configuration for a successful data load. This includes creating necessary master data

configurations

and folder structures before initiating an import. (Reference: Common data import and administration guide for SAP Ariba Strategic Sourcing and SAP Ariba Supplier Management solutions

Section on "Importing Data").

Within the SAP Activate methodology, the SAP Deployment Lead is the key role from SAP responsible for the overall successful deployment of the cloud solution. This leadership position entails managing the end-to-end delivery, which critically includes overseeing and coordinating all Suite Integration activities. They ensure that different SAP cloud solutions (e.g., S/4HANA Cloud, SuccessFactors, Ariba) are integrated correctly to deliver a cohesive and functional Intelligent Enterprise Suite for the customer. Their responsibility is to ensure all project workstreams, including integration, align to deliver the planned scope and value.

A. SAP Support: This team is engaged for post-go-live incident management and technical support, not for leading project implementation activities like integration.

C. Partner/Customer Functional Lead: This role leads a specific business process area or module. While they contribute to integration design, they do not lead the overall, cross-solution integration effort.

D. Customer Success Manager: This is a post-sales relationship management role focused on customer adoption and value realization, not the technical execution or leadership of a deployment project.

1. SAP Activate Roadmap Viewer: In the "SAP Activate Methodology for RISE with SAP S/4HANA Cloud

private edition

" the role of the SAP Project Manager/Deployment Lead is defined. Their accountability for the "overall project delivery" implicitly and necessarily includes the leadership of critical workstreams like Suite Integration. (Access via SAP Roadmap Viewer > Roles).

2. SAP Press Publication: In the book "SAP Activate: Project Management for SAP S/4HANA and SAP S/4HANA Cloud

2nd Edition

" Chapter 4

Section 4.2.2

"SAP Roles

" describes the SAP Deployment Lead as being "responsible for the successful deployment of the SAP cloud solution" and managing the "overall delivery of the project." This overarching responsibility includes leading the integration strategy and execution.

3. SAP Learning Hub (Course ACT200 - Agile Project Management with SAP Activate): Unit 2

"SAP Activate Roles and Responsibilities

" details the SAP Deployment Lead's function. The course materials explicitly position this role as the leader from the SAP side

accountable for the entire solution delivery

which is impossible without successfully leading the integration of all suite components.

In the SAP S/4HANA Cloud extensibility framework, once a custom field is saved using the "Custom Fields" app, its fundamental properties, such as the Field Type, are locked and cannot be changed. This is because the system prepares the metadata for the eventual generation of data dictionary (DDIC) objects upon publishing. Since the field in the scenario has not yet been published, it has not been activated in the system's repository or transported. Therefore, the correct and cleanest procedure is to delete the erroneously configured field and create a new one with the same name and the intended field type.

A. Clear and recreate the field with the same field name and the intended field type: The term "Clear" is not a standard function within the "Custom Fields" app; the correct action is "Delete".

B. Mark the field as Hidden, and create a new field with a slightly different name and the intended field type: This is an inefficient workaround that leaves an incorrect artifact in the system and prevents the use of the desired field name.

D. Change the field type by selecting the intended type in the dropdown and Save: The field type is immutable after the initial save to ensure consistency during the code and database object generation process.

1. SAP Help Portal

SAP S/4HANA Cloud

"Custom Fields" Documentation: In the section on "Editing Custom Fields

" the documentation explicitly states: "You can edit a custom field as long as it has not been transported to your production system. However

you cannot change the field type after you have created the field." This directly invalidates option D.

2. SAP Help Portal

SAP S/4HANA Cloud

"Custom Fields" Documentation: The section on "Deleting Custom Fields" states: "You can delete a custom field as long as it has not been transported to your production system." This confirms that deletion is a valid action for an unpublished field

making option C the correct procedure.

3. openSAP Course: "Extending SAP S/4HANA Cloud and SAP S/4HANA" (e.g.

s4h12)

Week 2

Unit 2: Creating a Custom Field: The course material demonstrates the lifecycle of a custom field. It shows that after the initial "Create and Edit" step where the type is set

subsequent edits before publishing do not allow the type to be altered. The only recourse for a wrong type is deletion and recreation.