Before the first Fit-to-Standard workshop, the consultant should do the following activities:
* Deactivate scope items that are NOT part of the Statement of Work/Digital Discovery Assessment. This is to ensure that the Starter system reflects the agreed scope of the project and does not include any unnecessary or out-of-scope items. The consultant can use the Scope Item Management app to deactivate scope items1.
* Review the integration requirements collected from the Digital Discovery Assessment. This is to understand the customer's integration needs and prepare for the integration topics that will be discussed in the Fit-to-Standard workshop. The consultant can use the Integration Solution Advisor tool to review the integration requirements and the recommended integration scenarios2.
The consultant should NOT do the following activities before the first Fit-to-Standard workshop:
* Upload customer master data in the Starter system using migration templates. This is not required before the first Fit-to-Standard workshop, as the customer master data is not relevant for the process validation. The consultant should upload the customer master data in the Quality system after the Fit-to- Standard workshop, using the SAP S/4HANA Migration Cockpit3.
* Evaluate the L2 Business-Driven Configuration Questionnaire responses. This is not required before the first Fit-to-Standard workshop, as the L2 Business-Driven Configuration Questionnaire is not available at this stage. The consultant should evaluate the L2 Business-Driven Configuration Questionnaire responses after the Fit-to-Standard workshop, using the SAP Activate Methodology.
References =
* 1: Scope Item Management App
* 2: Integration Solution Advisor Tool
* 3: SAP S/4HANA Migration Cockpit
* : [SAP Activate Methodology]

In the Organizational Structure app within SAP Central Business Configuration, the structure of an organization is defined by specifying various entities that reflect the business's operational and functional areas. Under the Company root node, entities such as Sales Organization and Purchasing Organization can be added:
* Sales Organization: This entity is responsible for the distribution and sale of goods and services. It defines the scope of sales activities, including customer negotiations, sales orders, and distribution.
Adding a Sales Organization under the Company root node allows for the management and configuration of sales-related processes within SAP S/4HANA Cloud Public Edition.
* Purchasing Organization: This entity manages procurement activities, including the negotiation of purchasing conditions, ordering, and the receipt of goods. By adding a Purchasing Organization under the Company root node, the system can handle procurement processes, vendor relationships, and purchasing analytics.
These entities are crucial for defining how the organization operates within the SAP S/4HANA Cloud Public Edition environment, facilitating the alignment of the software's functionality with the company's business processes.