The "Sales Processing using Third-Party without Shipping Notification" (BDK) process is a standard SAP S/4HANA Cloud scope item. In this scenario, a sales order automatically generates a purchase requisition. This is converted into a purchase order, which may require approval and release (D). The third-party vendor ships the goods directly to the customer and sends an invoice to your company. The receipt and entry of this vendor invoice (B) is the crucial step that confirms the transaction and makes the sales order due for billing. Subsequently, your company creates a billing document (A) to invoice the end customer. This process variant explicitly omits any goods receipt or delivery document creation in your system.

C. Create outbound delivery: This is incorrect because the goods are shipped directly from the third-party vendor to the customer, not from your company's own stock. Therefore, no outbound delivery is created.

E. Create inbound delivery: This is incorrect as the goods are never received at your company's premises. The vendor ships directly to the final customer, so no inbound delivery is processed.

1. SAP Best Practices Explorer: Scope Item "Sales Processing using Third-Party without Shipping Notification (BDK)". The official process flow diagram for this scope item clearly shows the sequence: Create Sales Order -> Convert Purchase Requisitions to Purchase Orders -> Approve Purchase Orders -> Create Supplier Invoice -> Create Billing Document. The diagram explicitly shows no delivery-related steps. (Access via SAP Best Practices Explorer for SAP S/4HANA Cloud

Public Edition).

2. SAP Help Portal - Third-Party Processing: "In third-party processing without a shipping notification

the sales order is relevant for billing as soon as the invoice from the vendor has been posted in Financial Accounting. The quantity from the vendor invoice is automatically copied to the billing document." This documentation confirms that the vendor invoice (B) precedes and triggers the customer billing document (A). (SAP S/4HANA Cloud -> Sales -> Sales -> Third-Party Processing).

The Digital Discovery Assessment (DDA) is a self-service tool used during the Discover phase of the SAP Activate methodology. Its purpose is to capture the customer's high-level requirements to define the initial project scope. This assessment explicitly includes a section for identifying the known integrations required for the customer's solution landscape. The output, the Digital Discovery Assessment Report, serves as a primary input for the subsequent Prepare and Explore phases, providing the foundational list of integrations for the project team.

A. In the Fit-to-Standard Workshops: These workshops occur in the Explore phase to analyze and validate standard processes. The initial integration list from the DDA is an input to these workshops, not where it is first documented.

B. In SAP Cloud ALM: While integration requirements are managed and tracked in SAP Cloud ALM during the project, the initial list is captured earlier in the Digital Discovery Assessment to first define the scope.

C. In the Business Driven Configuration Questionnaire: This questionnaire is used during the Explore phase to gather detailed configuration values for specific scope items, which is a more granular activity that follows the initial scope definition.

1. SAP Activate Roadmap Viewer for SAP S/4HANA Cloud

Public Edition:

Phase: Discover

Task: Complete Digital Discovery Assessment

Details: The official description for this task states

"The purpose of this task is to complete the Digital Discovery Assessment to determine the required scope items

localizations

and integrations for the customer." This confirms the DDA is the tool for the initial documentation of integrations. (Accessed via SAP Activate Roadmap Viewer).

2. SAP Learning Hub - S4C01e - Introduction to SAP S/4HANA Cloud:

Unit: SAP Activate for SAP S/4HANA Cloud

Public Edition

Section: Discover Phase

Content: Course materials describe the Digital Discovery Assessment as the key tool for customers to self-declare their implementation scope

including required integrations

before the project formally begins. The output is a report that forms the basis for the project contract and initial planning.

The fundamental difference between the "Sell from Stock" and "Free of Charge Delivery" processes in SAP S/4HANA Sales is the Sales Document Type. This document type is the primary control element for the entire transaction. It dictates the subsequent process flow, including the determination of item categories, pricing procedures, delivery relevance, and billing relevance. A "Sell from Stock" process uses a standard sales document type (e.g., OR) configured for revenue-generating transactions, leading to a standard invoice. Conversely, a "Free of Charge Delivery" uses a specific sales document type (e.g., FD) configured for non-revenue transactions, which results in no billing or a pro-forma invoice.

A. Delivery document type: The delivery document type is proposed based on the sales document type. While it can be different, it is a consequence, not the primary cause of the process difference.

B. Billing type: The billing relevance and the specific billing document type are determined by the sales document type and the item category. This is an outcome of the initial process choice.

C. Picking document type: Picking is a warehouse management activity within the delivery process and does not have a controlling document type that defines the overall sales scenario in this context.

1. SAP S/4HANA Cloud

Public Edition 2402 Documentation

SAP Best Practices Explorer:

Scope Item BD9 (Sell from Stock): The process flow is initiated by creating a sales order with the standard sales document type 'OR'.

Scope Item BDG (Free-of-Charge Delivery): This process is initiated by creating a sales order with the specific sales document type 'FD'. This demonstrates that the sales document type is the initial and defining element that separates the two processes.

2. SAP Help Portal

SAP S/4HANA

Sales Document Types: "The sales document type categorizes the sales documents and is the most important control element for a sales transaction... For example

the sales document type determines... which billing types are proposed for billing." This confirms the sales document type's role as the primary controller for the entire transaction

including subsequent documents like billing.

3. SAP Learning Hub

Course S4600 (Business Processes in SAP S/4HANA Sales)

Unit 3: Sales Document: This course material explains that the sales document type is a key organizational element in sales processing that controls which fields are required

which partner functions are used

and how the system processes the transaction

including proposing subsequent delivery and billing documents. The choice between a standard sale and a free-of-charge delivery is made at this initial step.

When an SAP Fiori app tile is missing from the Fiori Launchpad for a user, despite the correct business role assignment, the issue typically lies within the configuration of the business role itself. The troubleshooting process involves three key checks:

1. Business Catalogs: A business role must contain the specific business catalog that grants authorization for the app (the tile and its target mapping). If the catalog is missing, the user lacks the permission to see or use the app.

2. Spaces and Pages: In the current Fiori Launchpad design, visibility is controlled by spaces and pages. The app's tile must be on a page, which is part of a space, and that space must be assigned to the business role.

3. Role Maintenance App: These checks are performed using the dedicated Fiori app, such as Maintain Business Roles, which is the central tool for analyzing and correcting the role's content.

A. Check the business role template.

A template is only used to create a business role. The active, assigned role is a separate object, and subsequent changes to the template do not affect it.

B. Check the restrictions for the role.

Restrictions control data-level access within an app (e.g., which company codes are visible), not the visibility of the app tile on the launchpad.

1. SAP S/4HANA Cloud

Public Edition 2402 Documentation

SAP Help Portal: How to Maintain a Business Role. This guide details the structure of a business role within the Maintain Business Roles app. It explicitly shows the tabs for "Assigned Business Catalogs" and "Assigned Launchpad Spaces

" confirming that these are the primary components to check for app access and visibility. (Supports C

D

E).

2. SAP S/4HANA Cloud

Public Edition 2402 Documentation

SAP Help Portal: Troubleshooting for Administrators. In the section on "Tiles

Target Mappings

and Catalogs

" the guide states: "If a user complains about a missing tile on the launchpad

you first need to check if the user has a role that contains the catalog with the tile." It further explains the need to check space and page assignments. (Supports D

E).

3. SAP Learning Hub Course S4C01 - SAP S/4HANA Cloud Onboarding Fundamentals: Unit 4: Identity and Access Management. This course explains that a business role is composed of business catalogs (granting authorizations) and that spaces are assigned to the role to define the launchpad layout. This confirms the direct link between catalogs

spaces

and the role for app visibility. (Supports D

E).

In the SAP S/4HANA Cloud Public Edition Sell from Stock (BD9) process, the sales order is the central document that confirms a customer's intention to buy. It is a contractual agreement between the sales organization and the customer that formalizes the purchase of specific products in agreed-upon quantities for a set price. The creation of the sales order is the trigger for all subsequent logistics and fulfillment activities, such as checking material availability, scheduling delivery, and ultimately, shipping the goods.

A. Sales quotation: This is a legally binding offer made by the seller to the customer. It does not confirm the customer's intent to buy until it is accepted and referenced in a sales order.

B. Outbound delivery: This document is created after the sales order to manage the shipping and goods issue process. It is a fulfillment step, not the initial confirmation of purchase intent.

C. Sales inquiry: This is a customer's non-binding request for information about products and pricing. It carries no obligation to purchase and precedes a quotation or order.

1. SAP Best Practices Explorer: Scope Item "Sell from Stock (BD9)" for SAP S/4HANA Cloud. The official process flow diagram shows that "Create Sales Order" is the step that represents the customer's firm request and initiates the fulfillment process. The description states

"The process starts with the creation of a customer's standard sales order."

Source: SAP Best Practices Explorer

SAP S/4HANA Cloud

Scope Item BD9

Process Flow section.

2. SAP Help Portal: The documentation for Sales Order Management in SAP S/4HANA Cloud defines a sales order as the primary document for a sales transaction. "A sales order is a contractual agreement between a sales organization and a sold-to party..." This definition confirms its role as the document solidifying the customer's intention.

Source: SAP Help Portal

SAP S/4HANA Cloud

"Sales Orders".

3. SAP Learning Hub: The course S4C30 (SAP S/4HANA Cloud

public edition - Sales) explains the sales process flow. In the "Sales Document Processing" unit

it clearly distinguishes pre-sales documents (inquiry

quotation) from the sales order

which is the legally binding document that confirms the sale and triggers logistics.

Source: SAP Learning Hub

Course S4C30

Unit: "Sales Document Processing".