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

 You can launch the Cloud Integration Automation Service (CIAS) through the following applications:

SAP for Me: SAP for Me is your digital companion along your whole SAP customer journey. It provides you with full transparency into your SAP product portfolio, including your licenses, systems, users, orders, contracts, and invoices. You can also access the CIAS from the SAP for Me mobile app.

SAP Cloud ALM: SAP Cloud ALM is a cloud-based application lifecycle management solution that helps you implement, operate, and optimize your cloud solutions. It offers various tools and services to support your end-to-end business processes, such as process management, task management, test management, and integration monitoring. You can access the CIAS from the SAP Cloud ALM launchpad. References = SAP for Me - Apps on Google Play, SAP for Me - Your digital companion along your whole SAP customer journey, The Future of Our Customer Relationships with SAP for Me | SAP News, SAP for Me: New Entry Point for SAP Support | SAP News Center, [SAP Cloud ALM], [SAP Cloud ALM - Overview], [SAP Cloud ALM - Application Lifecycle Management], [Cloud Integration Automation Service | SAP Help Portal], [What Is Cloud Integration Automation Service? | SAP Help Portal]

The SAP Fiori Launchpad provides embedded support offerings that can help users learn and perform tasks more efficiently. These offerings include:

Digital assistance from generative AI (SAP Joule): This is a conversational AI assistant that can answer user questions, provide guidance, and execute tasks using natural language. SAP Joule can be accessed by selecting the headphones icon in the top right corner of the SAP Fiori Launchpad and choosing the chat option.

Recorded system simulations from the Learning Center: These are interactive tutorials that show users how to perform common tasks and scenarios in the SAP S/4HANA Cloud system. Users can access the simulations by selecting the question mark icon in the top right corner of the SAP Fiori Launchpad and choosing the graduation cap icon. The simulations are created with the SAP Enable Now tool and can be customized by customers if needed.

Video tutorials from the SAP Help Portal: These are short videos that explain the features and functionalities of the SAP S/4HANA Cloud system and the SAP Fiori Launchpad. Users can access the videos by selecting the question mark icon in the top right corner of the SAP Fiori Launchpad and choosing the megaphone icon. The videos are also available on the SAP Help Portal website.

The other options are not embedded support offerings in the SAP Fiori Launchpad. Recorded webinars from the SAP Learning Website and assessment questions from the SAP Learning Hub are external learning resources that users can access separately from the SAP Fiori Launchpad. References = Using the Embedded Support Capabilities and the Joule Generative AI Assistant > Using the Embedded Support Capabilities and the Joule Generative AI Assistant > SAP Fiori Launchpad Embedded Help and Support. SAP Fiori Launchpad for SAP S/4HANA Cloud > SAP Fiori Launchpad > What is SAP Fiori launchpad? SAP Fiori Launchpad – Overview > Services.

 To integrate SAP S/4HANA Cloud Public Edition with another SAP public cloud solution, you should use SAP Integration Suite and predelivered APIs. SAP Integration Suite is a cloud-based integration platform that provides a comprehensive set of capabilities to connect applications, data, and processes across different environments. Predelivered APIs are predefined interfaces that enable communication and data exchange between SAP S/4HANA Cloud Public Edition and other SAP public cloud solutions, such as SAP SuccessFactors, SAP Ariba, SAP Fieldglass, and SAP Concur. SAP Process Orchestration and SAP Cloud Connector are not the correct technologies for this scenario, as they are mainly used for integrating SAP S/4HANA Cloud Public Edition with on-premise or hybrid systems. References = SAP S/4HANA Cloud Public Edition - Integration, SAP Integration Suite, SAP S/4HANA Cloud Public Edition - API Hub

Sandbox system: This is an optional system that can be used to explore the SAP S/4HANA Cloud Public Edition capabilities and features before the implementation project starts. It is not connected to the starter system or the test system and does not have any data migration or configuration tools. It can be refreshed on demand by the customer1.

Starter system: This is the first system that is provisioned for the customer after the contract is signed. It is used to perform the fit-to-standard workshops, where the customer validates the standard processes and identifies the gaps and requirements. It also serves as the configuration system, where the customer configures the business processes using the SAP Central Business Configuration tool. The starter system is connected to the test system and can transfer the configuration and master data to it2.

Test system: This is the second system that is provisioned for the customer after the starter system is configured. It is used to perform the integration testing, user acceptance testing, data migration, and cutover activities. It also serves as the production system, where the customer runs the live business processes after the go-live. The test system is connected to the starter system and can receive the configuration and master data from it3.

The systems that are not used to implement SAP S/4HANA Cloud Public Edition for a customer are:

Trial system: This is a system that can be used to experience the SAP S/4HANA Cloud Public Edition solution for a limited time. It is not connected to any other system and does not have any data migration or configuration tools. It is not part of the implementation project and does not require a contract4.

Development system: This is a system that can be used to develop custom applications or extensions using the SAP Business Technology Platform. It is not part of the SAP S/4HANA Cloud Public Edition landscape and does not have any data migration or configuration tools. It requires a separate contract and license.

References = [SAP S/4HANA Cloud Public Edition - System Landscape], [SAP S/4HANA Cloud Public Edition - Setting up Systems and Authorizations], [SAP S/4HANA Cloud Public Edition - Trial System], [SAP S/4HANA Cloud Public Edition - Development System].

SAP S/4HANA Cloud Business Workflows are designed to enhance and automate business processes within the organization. They serve multiple purposes:

To create complex, repeated work processes with iterative cycles: These workflows are designed to handle intricate processes that occur regularly within the business environment, allowing for automation and efficiency in tasks that require repetition and involve multiple steps or conditions.

To create cross-product workflow procedures: This capability allows for the integration of various SAP products and services into a cohesive workflow, ensuring smooth and interconnected operations across different aspects of the business. It enables workflows that span across different SAP applications and solutions, providing a unified approach to managing business processes.

To create business processes with a high number of people involved in a pre-defined sequence: SAP S/4HANA Cloud Business Workflows are capable of handling processes that involve many participants, orchestrating the sequence of tasks to be completed by different individuals or departments. This ensures that each step of the process is executed in the right order by the right person, enhancing collaboration and efficiency.

 The SAP S/4HANA Migration Cockpit is a tool that facilitates the transfer of business data from a source system to SAP S/4HANA. It uses migration objects to identify and transfer the relevant data for a specific business object. The SAP S/4HANA Migration Cockpit has the following characteristics1:

It allows mapping source values to SAP S/4HANA target values, as well as converting values that are migrated from source fields to target fields. This ensures data consistency and quality in the target system.

It provides guidance and simulation of the migration process, as well as error handling and monitoring. This helps to reduce the complexity and risk of data migration, and to ensure a smooth and successful data transfer.

It does not support extensibility using the Legacy System Migration Workbench (LSMW), which is a tool for data migration from legacy systems to SAP systems. The SAP S/4HANA Migration Cockpit has its own extensibility framework, the SAP S/4HANA Migration Object Modeler, which allows creating and enhancing migration objects2.

It does not combine the local and remote schema approaches into one migration project. The SAP S/4HANA Migration Cockpit offers three options for transferring data to SAP S/4HANA: using files, using staging tables, or using direct transfer from an SAP system1. Each option requires a separate migration project and has its own advantages and limitations3. References = 1: SAP S/4HANA Migration Cockpit | SAP Help Portal 2: [SAP S/4HANA Migration Object Modeler | SAP Help Portal] 3: [Options for Transferring Data | SAP Help Portal]