The organizational entities that are required in SAP Central Business Configuration are defined by the selected deployment target and the selected scope. The deployment target specifies which SAP cloud solutions are included in the project, such as SAP S/4HANA Cloud, public edition. The scope specifies which business processes and countries/regionsare included in the project, such as sales or professional services. These choices determine which organizational units are required to run the underlying processes, such as company, business residence, sales organization, or project unit. Added partner content and system consistency checks do not define the organizational entities, but rather enhance or validate the configuration. References = SAP Central Business Configuration - Overview, page 5; Introducing SAP Central Business Configuration In SAP Central Business Configuration, the organizational entities that need to be defined for an SAP S/4HANA Cloud Public Edition implementation are influenced by two primary factors: the selected deployment target and the selected scope. The deployment target refers to the specific environment or system where SAP S/4HANA Cloud will be implemented. This choice can affect which organizational entities are necessary based on the technical and business requirements of that environment. The selected scope, on the other hand, pertains to the business processes and functions that the company intends to use within SAP S/4HANA Cloud. This determines the organizational structures, such as company codes, sales organizations, and purchasing organizations, that need to be set up to support the scoped processes. Both factors are integral to ensuring that the configuration supports the business's operational needs and strategic objectives.

You can complete the following activities in the Maintain Business Roles SAP Fiori app:
Assign business catalogs to a business role. Business catalogs are collections of SAP Fiori apps that are relevant for a specific business area or task. You can add one or more business catalogs to a business role to grant access to the corresponding apps1.
Maintain restrictions. Restrictions are rules that limit the access of a business role to certain data or functions based on predefined criteria, such as company code, plant, or sales organization. You can maintain restrictions for a business role in a new UI that provides an overview of the restriction types and values2.
You cannot complete the following activities in the Maintain Business Roles SAP Fiori app:
Maintain technical catalogs. Technical catalogs are collections of SAP Fiori apps that are grouped by technical criteria, such as application component or OData service. Technical catalogs are not assigned to business roles, but rather to business catalogs as dependencies3.
Assign PFCG profiles to a business role. PFCG profiles are authorization profiles that are created and maintained in the Profile Generator (PFCG) transaction in the SAP GUI. PFCG profiles are not assigned to business roles, but rather to business users as part of the user role assignment4. References
= Maintain Business Roles; Maintain Business Roles and Business Users; Maintain Business Roles - New (Preview); Maintain Business Catalogs

The Business Driven Configuration Questionnaire is a tool that helps you collect the values that are entered into the configuration activities in SAP Central Business Configuration. It is a web-based questionnaire that guides you through the configuration settings for each solution process. You can use the questionnaire to enter the values for the configuration activities, review the values, and export them to an Excel file. You can then import the Excel file to SAP Central Business Configuration and apply the values to the configuration activities. References = Business Driven Configuration Questionnaire, Importing Configuration Values from Business Driven Configuration Questionnaire, Using SAP Central Business Configuration to Activate Content in the SAP S/4HANA Cloud Starter System

When using the Local SAP S/4HANA Database Schema migration approach, you can upload multiple XML files at once by using a ZIP file. The total maximum permitted size for the XML files in the ZIP file is 160 MB. The limit for the ZIP file is also 160 MB. Therefore, the maximum file size is 160 MB per ZIP file and
160 MB per file. References = SAP Help Portal - SAP Online Help, SAP Help Portal - SAP Online Help

Indirect digital access occurs when humans, devices, or systems use the digital core indirectly through non-SAP intermediary software, such as a non-SAP front end, a custom-solution, or any other non-SAP application1. Indirect digital access is measured by the number of documents created, updated, or deleted in the SAP system as a result of the indirect use2. Examples of indirect digital access include:
A Defect document created through an industry application: This is an example of indirect digital access because the industry application is a non-SAP software that triggers the creation of a document in the SAP system.
A Time Sheet Record from a 3rd party application: This is also an example of indirect digital access because the 3rd party application is a non-SAP software that triggers the creation of a document in the SAP system.
An unattended bot in SAP Build Process Automation: This is not an example of indirect digital access because the bot is using SAP software to access the SAP system directly, not through a non-SAP intermediary software.
A Production Order created through a non-SAP front-end: This is not an example of indirect digital access because the production order is not a document type that is counted for indirect digital access. The document types that are counted are: Sales Order, Invoice, Purchase Order, Service and Maintenance Document, Manufacturing Document, Quality Management Document, Time Sheet, Financial Document, and Material Document2. References = Digital Access | SAP Help Portal, SAP Digital Access / SAP Digital Access Adoption Program (DAAP) Extension through December 31, 2021