Reviewing configuration elements & core operational functionalities

The Configuration Mover functionality within SAP Fieldglass is a highly technical and administrative offering, allowing buyers the ability to import pre-configured tenant setups for their implementation, as well as migrate their own established configurations from test landscapes into a live production setting. This self-service tool provides an efficient level of automation, removing labor-intensive configuration tasks, as well as reducing manual errors and overall time to implement.

For learners to comprehend and utilize the information provided throughout this Configuration Mover course successfully, it is strongly recommended that preceding learning modules and/or learning journeys be completed before beginning this content. Completing these elements will establish a baseline of knowledge required for learners to successfully implement and understand the more advanced data covered within.

Several offerings are available to learners and are highly suggested as prerequisites to this course. Details of these are seen below:

Introducing SAP Fieldglass (Learning Journey) (Course ID FG111)

This learning journey guides the learner through an introduction of SAP Fieldglass, explaining different functionalities of the solution and how it can be used to simplify the procuring and managing of workforce.

Discovering SAP Fieldglass Contingent Workforce Management (Learning Journey)

This learning journey will guide the learner through the basic set up and administration of SAP Fieldglass, and the administrative and transactional aspects of Contingent Workforce Management.

Discovering SAP Fieldglass Services Procurement (Learning Journey)

This learning journey will guide the learner through the basic configuration and administration of SAP Fieldglass, and the administrative and transactional aspects of Services Procurement. This Learning Journey includes:

As the referenced learning journeys and courses explain in detail, it is important to recall that the SAP Fieldglass application is made up of primarily two types of interrelated data when a buyer implements their tenant. These can be seen as company, site, and administrative configurations within the tool, as well as master data, which is core foundational data that is referenced and associated to transactions executed within the application. This delineation is an important notation, as the Configuration Mover functionality primarily supports the management of true configuration elements and is not considered a solution to manage foundational data. Configuration data, for example, would include the setup and enablement of approval groups associated with Contingent Labor workflows, while master data would encapsulate the creation and management of cost centers and business unit objects within a buyer instance.

The initial required configuration of a buyer’s tenant in SAP Fieldglass is known as the Company Configuration. This is an administrative setting in which a buyer selects and defaults all the core functions, tools, and offerings they will be implementing when operating the SAP Fieldglass system. Once established, the company configuration settings do not typically change unless a buyer implements an additional service or function as their program advances in both size and operational complexity. Also, when new functionality is released and becomes available to a buyer company within SAP Fieldglass, this can require additional configuration updates to be enabled and activated.

Administrative (admin) configuration objects, however, are more flexible and often undergo continuous management and update within the system. This "structure" reflects objects like approval workflows, approval rules, custom fields, classifications, job codes, categories, and reasons, as well as more intricate backend configurations for their integration processes.

The available sections and settings that the Configuration Mover functionality supports include high-level core company configurations and more defined admin configuration items.

Master data objects, in contrast to configuration objects, are the core foundational attributes that define the buyer as a distinct organization within the application. These are database elements that specify cost and billing like cost centers, legal entities, or purchase units - as well as hierarchical structures like departments, business units, and sites or locations that function as the underlying makeup of the larger operating organization. Master data, within SAP Fieldglass, does not fulfill admin or operational transactions in the system, but instead reflects who or what the transactional data and workflows executed in the system apply against. While a buyer is required to maintain this core data within SAP Fieldglass to operate, this is not an area that Configuration Mover currently supports. Standard best practices reflect buyers manage their master data through available integration channels that feed and update SAP Fieldglass accordingly.

This lesson introduced the Configuration Mover functionality in SAP Fieldglass, which allows users to import and migrate preconfigured tenant setups efficiently. Additionally, it provided guidance on prerequisite courses and key concepts related to configuration and master data objects.

• Configuration Mover Functionality: Allows buyers to import preconfigured tenant setups and migrate their configurations efficiently, reducing manual errors and implementation time.
• Prerequisite Learning: Completing suggested learning journeys (e.g., 'Introducing SAP Fieldglass') establishes baseline knowledge for this course.
• Configuration and Master Data: Configuration data (e.g., approval groups) and master data (e.g., cost centers) are distinct types, with Configuration Mover primarily supporting configuration elements.
• Company Configuration: Includes the initial setup of core functions and tools, typically stable unless new functionality is added.
• Master Data Management: Managed through integration channels and not supported by Configuration Mover, it defines the buyer's organizational attributes in the application.