In the standard SAP S/4HANA procurement lifecycle, a Request for Quotation (RFQ) is a formal request sent to potential suppliers to solicit bids for goods or services. The process is typically initiated when a need is identified and documented in a Purchase Requisition (PR). Creating an RFQ with reference to a PR is a standard, streamlined procedure. This action copies relevant data, such as materials, quantities, and required dates, from the PR to the RFQ, ensuring data consistency and reducing manual effort. The RFQ is a key step in the sourcing process to determine the best source of supply before a binding purchasing document is created.

A. Scheduling Agreement: This is a long-term purchasing agreement with a pre-selected vendor. An RFQ is used before establishing such an agreement to select the vendor.

C. Purchase Contract: Similar to a scheduling agreement, a contract is an outline agreement with a chosen vendor. The RFQ process precedes the creation of a contract.

D. Purchase Order: A purchase order is a formal commitment to a vendor created after the sourcing and quotation evaluation process is complete. It is a result of, not a source for, an RFQ.

1. SAP S/4HANA Cloud Documentation: In the "How to Create Requests for Quotation" guide

it is explicitly stated: "You can create a request for quotation (RFQ) in the following ways: [...] With reference to a purchase requisition."

Source: SAP Help Portal

SAP S/4HANA Cloud

Public Edition 2402

Sourcing and Procurement > Operational Procurement > Request for Quotation (RFQ) > How to Create Requests for Quotation.

2. SAP S/4HANA Fiori App Documentation: The documentation for the "Manage Purchase Requisitions (Version 2)" Fiori app lists its key features

including the ability to: "Create follow-on documents

for example

purchase orders or requests for quotation."

Source: SAP Help Portal

SAP S/4HANA 2023

Product Assistance > Enterprise Business Applications > Sourcing and Procurement > Operational Procurement > Purchase Requisition > Fiori Apps for Purchase Requisitions > Manage Purchase Requisitions (Version 2).

3. SAP S/4HANA Training Courseware: The official SAP training course for Sourcing and Procurement outlines the standard process flow where a Purchase Requisition is a precursor to an RFQ. The creation of an RFQ with reference to a PR is a fundamental exercise in the sourcing unit.

Source: SAP Learning Hub

Course S4500 (SAP S/4HANA Sourcing and Procurement - Functions & Innovations)

Unit 4: Sourcing

Lesson: Creating Requests for Quotation.

The "My Outbox" Fiori application is designed to provide users with a view of workflow tasks they have already processed. It serves as a tracking tool for a user's past actions within the workflow system. This includes tasks that have been successfully finished (Completed) as well as tasks that the user has temporarily put on hold (Suspended). It essentially shows the trail of tasks that have left the user's active worklist.

B. Your tasks that the deadline were passed.

Overdue tasks that still require action are typically displayed and managed within the "My Inbox" application, often with a visual indicator highlighting their overdue status.

C. Your tasks that are not completed yet.

This describes the function of the "My Inbox" application, which is the central worklist for all pending, ready, and in-progress tasks assigned to a user.

D. Your tasks that are to be sent to your manager.

This describes a specific workflow action (e.g., forwarding for approval) rather than the overall purpose of the "My Outbox" app, which tracks already processed items.

1. SAP Fiori Apps Reference Library

App ID F1368 (My Outbox):

Reference: In the app description

it states

"With the My Outbox app

you can track the tasks that you have already processed. You can see the tasks that are completed

suspended

or canceled." This directly supports that the app shows completed and suspended tasks.

Source: SAP Fiori Apps Reference Library

(https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F1368')/S29)

2. SAP Help Portal - SAP S/4HANA Cloud - My Outbox:

Reference: The documentation for the "My Outbox" app explicitly details its features

including the ability to "View tasks that are completed

suspended

or canceled." This confirms the app's role in displaying tasks that are no longer in the active inbox.

Source: SAP Help Portal

SAP S/4HANA Cloud

Product Assistance

Cross-Components

My Outbox.

3. SAP Learning - S4C30 - SAP S/4HANA Cloud for Professional Services:

Reference: Unit 5

"Extensibility

Integration

and Analytics

" discusses workflow management concepts. The distinction is made between the "My Inbox" app for active tasks and other apps for tracking processed items. The "My Outbox" is presented as the tool for viewing tasks that have been acted upon by the user.

Source: SAP Learning Hub

Course S4C30

Unit 5.

In the SAP S/4HANA subcontracting process, components provided to a vendor are managed as a special stock category called "Stock of Material Provided to Vendor". This stock remains the legal property of the company and is therefore managed as part of its own total valuated stock. This ensures it is included in inventory valuation and is visible to Material Requirements Planning (MRP). This special stock is tracked at the plant level and is assigned to the specific subcontractor. It is not managed at the storage location level because the materials are physically located at the vendor's site, not within a company's own storage facility.

B. This special stock is explicitly managed at the plant level, not the storage location level, as it is physically located at the vendor's premises.

D. The components remain the company's property and part of its valuated stock; ownership does not transfer to the supplier during this process.

1. SAP S/4HANA Product Assistance

"Stock of Material Provided to Vendor": In the section on Subcontracting within Inventory Management

the documentation states: "This special stock has the following features: It is part of your own valuated stock. It is managed at plant level because the stock is not stored in your company but on the vendor's site." (Path: SAP S/4HANA -> Product Assistance -> Enterprise Business Applications -> Sourcing and Procurement -> Inventory -> Subcontracting -> Stock of Material Provided to Vendor).

2. SAP Learning

Course S4525 "Inventory Management and Physical Inventory in SAP S/4HANA": Unit 5

"Special Forms of Stock"

explains that special stock 'O' (Stock of material provided to vendor) is a type of company-owned special stock that is managed at the plant level per vendor

not at the storage location level.

The data retention period for a migration project is an optional parameter set during the project's creation in the SAP S/4HANA Migration Cockpit. A newly created project, before any migration activities have begun, has the status "Not Started". This setting determines how long the data in the staging tables will be kept after the project is finished. It is configured at the beginning to establish the data governance rules for the project's entire lifecycle, ensuring compliance and proper data management from the outset.

A. When the project status is "Completed": This status indicates the project is finalized and archived; settings cannot be changed at this stage.

B. When the project status is "Finished": This status means all migration objects are processed; it is too late to define the data retention policy.

C. When the project status is "In Progress": The retention period is a foundational setting defined during creation, not while migration activities are actively running.

1. SAP Help Portal

SAP S/4HANA 2023

Creating a Migration Project: In the procedure for creating a new migration project using staging tables

Step 5 explicitly lists "Data Retention Period" as an optional field to be filled in during the creation process. A project that has just been created has the status "Not Started".

Source: SAP Help Portal

SAP S/4HANA 2023

"Migrate Data Using Staging Tables"

Section: "Creating a Migration Project".

2. SAP Help Portal

SAP S/4HANA Cloud

Public Edition 2402

Creating a Migration Project: The documentation for the cloud edition also confirms this. When using the "Migrate Your Data – Migration Cockpit" app

the "Data Retention Period" is specified on the "New Project" screen.

Source: SAP Help Portal

SAP S/4HANA Cloud

Public Edition 2402

"SAP S/4HANA Migration Cockpit"

Section: "Creating a Migration Project".

3. OpenSAP Courseware

Migrating Your Business Data to SAP S/4HANA – New Implementation Scenario: Course demonstrations show that the "Data Retention Period" field is part of the initial project creation screen. Once created and before any data is loaded or processed

the project's status is "Not Started".

Source: OpenSAP Course

"Migrating Your Business Data to SAP S/4HANA – New Implementation Scenario"

Week 2

Unit 3: "SAP S/4HANA Migration Cockpit – Staging Approach".

According to the SAP Activate methodology for SAP S/4HANA Cloud Public Edition, a specific set of systems is provisioned and utilized to guide the implementation project. The process begins with the Starter system, which is used during the Prepare and Explore phases for activities like fit-to-standard workshops and solution scoping. Following this, the permanent 3-system landscape is provisioned. Within this landscape, the Development system is used for all configuration and extensibility, and the Test system is used for quality assurance, integration testing, and user acceptance testing before deployment to the Production system. These three systems are fundamental components of the implementation lifecycle.

B. Trial system: A trial system is provided for evaluation or training purposes before a customer commits to a project and is not part of the official implementation landscape.

E. Sandbox system: A sandbox is an optional, separately licensed system for isolated testing or proof-of-concepts and is not a standard part of the core implementation landscape.

1. SAP Activate Roadmap Viewer: In the SAP S/4HANA Cloud Public Edition roadmap

the "System Landscape and Transport Management" workstream details the provisioning sequence. The task "Request SAP S/4HANA Cloud Systems" explicitly lists the Starter system

followed by the Development

Test

and Production systems as the standard landscape.

2. SAP Help Portal - SAP S/4HANA Cloud

Public Edition: The documentation on "System Landscapes" describes the standard 3-system landscape (Development

Test

Production) and the initial role of the Starter system for fit-to-standard workshops. It clarifies that the Starter system is a temporary environment used at the beginning of the project.

3. SAP Learning - S4C01e (SAP S/4HANA Cloud

public edition Implementation Fundamentals): Unit 2

Lesson "System Landscape"

outlines the systems used during an implementation. It confirms the use of a Starter system for initial workshops

which is then replaced by the permanent 3-system landscape (Development

Test

Production)

with the Development and Test systems being actively used throughout the project before go-live.