The SAP S/4HANA Cloud scope item "Automated Invoice Settlement (2LH)" automates the Evaluated Receipt Settlement (ERS) process. The core function of ERS is to allow a company to settle goods movements based on purchase order and goods receipt data, thereby creating an invoice on behalf of the supplier without receiving a physical or electronic invoice from them. The "automated" aspect of scope item 2LH is achieved by scheduling a recurring background job that automatically processes all eligible goods receipts and posts the corresponding supplier invoices.

B. Post the appropriate invoices yourself while using evaluated receipt settlement.

This describes a manual action. The scope item 2LH specifically focuses on the automation of the ERS process via scheduled jobs, not manual posting.

C. Use the evaluated receipt settlement without the supplier's approval.

ERS is a collaborative business process that requires a prior agreement with the supplier, which is then maintained in the supplier master data and purchase orders.

1. SAP Best Practices Explorer, Scope Item 2LH (Automated Invoice Settlement): The process description states, "Evaluated Receipt Settlement (ERS) is the process of settling goods receipts automatically. The system creates the corresponding invoices for the goods receipts." One of the key process steps listed is "Schedule job for evaluated receipt settlement." This directly supports answers A and D.

(Source: SAP Best Practices Explorer for SAP S/4HANA Cloud, Scope Item ID 2LH, Test Script, Section "Purpose")

2. SAP Help Portal, SAP S/4HANA Cloud, "Schedule ERS Jobs": The documentation for the relevant Fiori app states, "With this app, you can schedule and monitor jobs for Evaluated Receipt Settlement (ERS). The system uses the settings you make to create the invoices for the goods receipts." This confirms that scheduling a job (Option A) is the method for automation.

(Source: SAP Help Portal, SAP S/4HANA Cloud, Application Help, "Schedule ERS Jobs")

3. SAP Help Portal, SAP S/4HANA Cloud, "Evaluated Receipt Settlement (ERS)": The general documentation on ERS explains the prerequisite: "You have agreed with the vendor that you will use ERS." This makes option C incorrect. The documentation also defines the process as settling goods receipts without a vendor invoice, which supports option D.

(Source: SAP Help Portal, SAP S/4HANA Cloud, Sourcing and Procurement, "Evaluated Receipt Settlement (ERS)", Section "Prerequisites" and "Features")

SAP Cloud ALM for Implementation is the designated application lifecycle management tool for SAP S/4HANA Cloud Public Edition projects. It is designed to guide the implementation team through the project by providing a pre-configured workspace based on the SAP Activate methodology. The tasks and deliverables from the selected SAP Activate Roadmap are loaded directly into SAP Cloud ALM, where they can be assigned to team members, tracked, and executed. This provides a central platform for managing the entire implementation project, from the Prepare phase through to Deploy.

A. SAP Central Business Configuration: This tool is used for scoping business processes and performing configuration activities, but it is not the primary tool for managing or accessing the overall project tasks from the roadmap.

B. SAP Cloud ALM for Service: This component of SAP Cloud ALM is focused on the post-go-live phase, specifically managing service delivery, incident resolution, and ensuring business continuity, not implementation tasks.

D. SAP Cloud ALM for Operations: This component of SAP Cloud ALM is used after the system is live. It focuses on monitoring, alerting, and maintaining the health and performance of the cloud solution.

---

1. SAP Help Portal, SAP Cloud ALM, "What Is SAP Cloud ALM?": "SAP Cloud ALM for implementation supports you during the implementation of cloud solutions from SAP... by providing preconfigured implementation workspaces based on SAP Activate methodology and Best Practices content." This document establishes that SAP Cloud ALM for Implementation is the tool that consumes SAP Activate content for project execution.

(Source: SAP Help Portal, Document: "What Is SAP Cloud ALM?", Section: "SAP Cloud ALM for implementation")

2. SAP Activate Roadmap Viewer, "SAP S/4HANA Cloud Public Edition (3-system landscape)": In the "Prepare" phase, the deliverable "Project Management" includes the task "Set Up Project in SAP Cloud ALM." This task explicitly states: "The project is set up in SAP Cloud ALM to manage the scope, schedule, budget, resources, and tasks." This directly links the roadmap tasks to management within SAP Cloud ALM.

(Source: SAP Activate Roadmap Viewer, Roadmap: "SAP S/4HANA Cloud Public Edition (3-system landscape)", Task ID: "PM010")

3. SAP Help Portal, SAP S/4HANA Cloud, "Implementation Tools for 3-System Landscape": The official documentation outlines the toolset for the 3-system landscape. It positions SAP Cloud ALM as the tool for "Project and Task Management" and SAP Central Business Configuration for "Business Configuration." This clearly separates the roles of the two systems.

(Source: SAP Help Portal, Product: SAP S/4HANA Cloud, Section: "Implementation Tools")

In SAP S/4HANA Cloud, an inbound delivery, which documents the physical receipt of goods, can be created through several methods. The standard manual process involves creating it directly with reference to a purchase order using the relevant Fiori app. Automation is achieved in two primary ways: first, by receiving an Advanced Shipping Notification (ASN) from a supplier via electronic data interchange (EDI) or an API, which automatically generates the inbound delivery. Second, a scheduled background job can be configured to automatically create inbound deliveries based on purchase orders that are due for delivery, which is particularly useful when ASNs are not part of the business process.

B. A supplier invoice is a financial document created after goods receipt. It does not trigger the creation of an inbound delivery, which is a logistics document preceding goods receipt.

E. The goods receipt is posted with reference to an inbound delivery. You cannot create an inbound delivery with reference to a goods receipt that has already occurred; this reverses the process flow.

1. SAP Help Portal for SAP S/4HANA Cloud, "Create Inbound Deliveries - From Purchase Orders": This official documentation describes the manual creation process. It states, "You can use this app to create inbound deliveries with reference to a purchase order." This supports option A.

2. SAP Help Portal for SAP S/4HANA Cloud, "Inbound Processing of ASNs": This document details the automated creation of inbound deliveries upon receipt of an Advanced Shipping Notification from a vendor. It states, "When the system receives an ASN, it can automatically create an inbound delivery." This supports option C.

3. SAP Help Portal for SAP S/4HANA Cloud, "Schedule Inbound Delivery Creation": This source describes the application used for automated creation via background jobs. The documentation explains that the app allows you to "schedule jobs for the creation of inbound deliveries from open purchase orders." This supports option D.

4. SAP Best Practices Explorer, Scope Item "Procurement of Direct Materials (J45)" for SAP S/4HANA Cloud: The process flow diagram for this scope item clearly illustrates the standard sequence: Purchase Order → (ASN → Inbound Delivery) → Post Goods Receipt → Create Supplier Invoice. This flow demonstrates that invoicing (Option B) follows goods receipt and that goods receipt (Option E) follows the inbound delivery, making both options incorrect process steps for creating an inbound delivery.

In SAP S/4HANA Cloud Public Edition, extending an existing product (material) to new organizational levels, such as a new plant or sales organization, can be done using specific Fiori applications.

The Manage Product Master Data app is the modern, primary Fiori application designed for all lifecycle activities of a product master, including creation, changes, and extensions.

The Create Material app, which is the Fiori equivalent of the classic MM01 transaction, is also used for this purpose. When a user enters a material number that already exists, the system automatically transitions into an "extend" mode, allowing the user to add the material to new organizational levels.

B. Change Material: While technically possible to extend a material using this app (the equivalent of MM02), its primary design is to change data within already existing organizational views, making the "Create Material" app a more direct method for extension.

D. Manage Source Data Products: This application is specifically designed for data migration activities, such as the initial loading of product master data into the system, and is not used for routine master data maintenance like extending a product.

1. SAP Help Portal, SAP S/4HANA Cloud, Manage Product Master Data: "Key Features: You can use this app to: ... Create, change, and display product master data ... Extend a product with new organizational levels." (This confirms the functionality of the 'Manage Product Master Data' app).

2. SAP Help Portal, SAP S/4HANA Cloud, Create Material (Initial Screen): "With this app, you can create a new material in the system. You can also use this app to extend an existing material by creating new organizational level data for it." (This explicitly confirms that the 'Create Material' app is used for extension).

3. SAP Fiori Apps Reference Library, App ID F1602 (Manage Product Master Data): The application documentation lists "Extend a product with new organizational levels" as a core feature for the Product Master Specialist role (SAPBRPRODMASTERSPECIALIST).

When an SAP Fiori app is not visible on the launchpad despite the user having the correct business role, the issue lies within the configuration of the role itself. The troubleshooting process involves using the "Maintain Business Roles" app (D) as the central tool. Within this app, two primary areas must be checked:

1. Content: The business catalog (A) that contains the Fiori app's tile and target mapping must be assigned to the role. If the catalog is missing, the app definition is not available to the user.

2. Layout: In the modern Fiori launchpad, visibility is controlled by spaces and pages (C). The app must be placed on a page, which in turn must be part of a space, and both must be assigned to the business role.

B. Check the restrictions for the role.

Restrictions control data-level access within an app (e.g., which company codes are visible). While severe authorization failures can sometimes prevent a tile from loading, it's not the primary reason for a tile not being displayed on the launchpad.

E. Check the business role template.

A business role template is only a starting point for creating a custom role. Once the role is created and assigned, the template is no longer relevant to the user's access.

1. SAP S/4HANA Cloud, Identity and Access Management Documentation: The official documentation outlines the structure of a business role. It specifies that a business role is composed of business catalogs (for content), spaces and pages (for layout), and restrictions (for authorizations). The "Maintain Business Roles" app is the designated tool for managing these components. (Refer to SAP Help Portal: Maintain Business Roles and How to Structure an SAP Fiori Launchpad).

2. SAP Help Portal - Troubleshooting Missing Tiles: The guide "How to analyze missing tiles in the SAP Fiori launchpad" for SAP S/4HANA Cloud explicitly lists the key checks:

Verify the business role assignment.

Verify the business catalog assignment to the role. (Confirms A)

Verify the space and page assignment to the role. (Confirms C)

The entire process is managed via the "Maintain Business Roles" app. (Confirms D)

(See SAP Knowledge Base Article 2927348 - How to analyze missing tiles in the SAP Fiori launchpad for SAP S/4HANA Cloud)