---
doc_type: fsd_product_capabilities
source: SAP S/4HANA Cloud Public Edition 2602 Feature Scope Description (v2.0, 2026-03-12)
module: Professional Services / R&D / Engineering / Product Lifecycle Management / Product Compliance
fsd_pages: 166–192
kb_version: 2602
last_updated: 2026-04-04
---

# SAP S/4HANA Cloud Professional Services, R&D / Engineering & PLM Capabilities

This document captures the Feature Scope Description (FSD) capabilities for Professional Services (Chapter 3.12), R&D / Engineering (Chapter 3.13) — including Enterprise Portfolio and Project Management, Product Lifecycle Management, Advanced PLM, Product Compliance, and Circular Economy — from the SAP S/4HANA Cloud Public Edition 2602 release.

---

## 3.12 Professional Services

### 3.12.1 Customer Project Management

> 📄 FSD Reference: p166

**业务背景 (Business Background)**:

The following features enable your project manager to create, manage, and monitor customer projects and internal projects. Project managers plan work packages and efforts, staff resources, and create billing plans for services. Subsequently, when efforts have been recorded, billing data is prepared, which are later used in the creation of invoices.

Project managers can also monitor projects for financial performance, using criteria such as cost, revenue, margin, and variance.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Create customer projects** | You can create and plan customer projects. You can plan several aspects such as high-level schedules, the type of project roles and people required to deliver the project, and plan costs and expenses. You can also create project-specific prices for delivered services, create billing plans, and thereby plan the project revenue and margin. |
| **Manage customer projects** | You can manage customer projects for which you are the responsible project manager. You can search for projects, copy existing projects, and edit your projects to plan work packages, effort, resources, and billing, recalculate cost and revenue, and analyze financial key performance indicators (KPIs). |
| **Monitor customer projects** | You can monitor customer projects from the perspective of financial performance. Project managers can keep track of cost, revenue, and margin, compare planned and actual values, analyze variance between planned and actual values, and use the information to review the project plan, or initiate follow-up activities. |
| **Review customer projects** | You can carry out monthly reviews of projects to measure progress and forecast project outcomes such as estimated cost at completion (EAC) and margin. You can improve the accuracy of costs at the completion of a project, with the ability to adjust ETC or deviations from planned quantities against roles and staffing. You can also simulate the effect of ETC changes on project EAC, percentage of completion (PoC), and margin. You can manage statuses and trends, and view a historical record of statuses and trends across a project's lifecycle. |
| **Fixed price billing** | By creating a fixed price billing plan as part of your project, you can bill customers a predetermined amount for the services that you will provide to them. |
| **Periodic billing processes** | You can create billing plans at item level to trigger periodic billing (at predetermined due dates) of customers. You can also bill based on customers' usage behavior (usage-based billing). |
| **Resource-related intercompany billing** | Intercompany billing enables you to generate invoices between separate accounting units within a corporate group. This is necessary if one accounting unit within the group provides services for another unit, or if one unit needs to bill another unit for expenses to another unit (for example, travel costs). You can: create customer projects; check for intercompany sales orders in the list of sales orders; create and change intercompany sales orders; create intercompany billing documents; process open customer invoices and monitor incoming payments; view key performance indicators (KPIs) for invoices and process invoices. |
| **Time and material and WIP clearance bills** | You can bill customers for the time, materials, and other expenses incurred by their projects. |
| **On-account billing** | You can bill customers for partial amounts of the final cost to be invoiced. The billed amount is recorded to the customer account as revenue. |
| **Billing for projects** | You can get an overview of all billing elements within the projects assigned, prepare the billing details and subsequently trigger billing processes. |
| **Create internal projects** | You can create and plan internal projects. You can plan several aspects such as high-level schedules, the type of project roles and people required to deliver the project, and plan costs and expenses. |
| **Manage internal projects** | You can manage internal projects for which you are the responsible project manager. You can search for projects, copy existing projects, and edit your projects to plan work packages, effort, and resources, recalculate cost, and analyze financial key performance indicators (KPIs). |
| **Monitor internal projects** | You can monitor internal projects from the perspective of financial performance. Project managers can keep track of cost and margin, compare planned and actual values, analyze variance between planned and actual values, and use the information to review the project plan, or initiate follow-up activities. |
| **Staff external employees** | You can search for and staff third-party employees for whom master data (including cost center assignment) exists. |
| **Distribute effort by months** | You can adjust the distribution of planned effort between the months of the work package. |
| **Authorize access to project apps** | You can decide the project information for which a user has access to, by specifying service organizations in the business role. |
| **Automatically adjust project dates while copying projects** | When copying projects, you can specify the project's start date. The system automatically adjusts the project and work package dates based on the duration of the project you are copying. |
| **Automatically adjust project dates** | Project dates are automatically adjusted if work package start or end dates lead to the project start getting advanced or the project end getting postponed. |
| **Plan revenue for expenses** | You can plan revenue from expenses, and later on bill such expenses to clients during downstream processes. |
| **Increased visibility of revenues as planned and revenues as sold** | You can assess the impact of project planning on as-sold revenues, and also while making changes to project during execution. |
| **Analyze project margins** | Key stakeholders such as project managers or project controllers can benefit from broader coverage of project reporting. |
| **Enhanced extensibility of projects** | Using tools for key user extensibility, designated key users can extend the usage of customer and internal project apps. For example, key users can add customized fields, rename labels, hide fields, and rearrange fields. Key users can also extend standard reporting and analytical content to suit individual or organizational needs. |
| **Project plan versions** | You can view the automatically-created baseline version, update the baseline version for selected work packages (if necessary), and view a comparison of plan figures in the baseline, the current plan, and EAC. |
| **Integration with resource management** | During the process of planning customer or internal projects, you can create resource requests for a resource manager to act on. |
| **Set the forecast month** | As a project manager or a key user, you can use an application job to set the forecast month for customer projects you are responsible for. This enables project managers to review and prepare project forecasts. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
⊙ Project information such as planned effort, planned cost, planned revenue, and estimate to complete (ETC) are stored and reported per month following the Gregorian calendar.
⊙ Periodic billing plans are only available for customer projects in professional services.

**关联Scope Items**: —

---

### 3.12.2 Integration with External Resource Management Services

> 📄 FSD Reference: p170

**业务背景 (Business Background)**:

SAP S/4HANA Cloud Public Edition supports the integration with external resource management services (for example, the resource management capability in SAP Project and Resource Management) to efficiently manage your resources and improve their utilization.

**核心功能 (Key Features)**:

*(No Key Features table in the FSD for this section — integration capability described in Business Background.)*

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

## 3.13 R&D / Engineering

### 3.13.1 Enterprise Portfolio and Project Management

#### 3.13.1.1 Project Financial Control

> 📄 FSD Reference: p170

**业务背景 (Business Background)**:

Managing projects, such as developing new products or running new investment projects, requires controlling-related financial aspects. With Project Financial Control, you can define projects and its underlying elements to serve as accounting structures for subsequent project financial accounting tasks such as cost planning, actual cost and revenue collection or settlement.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Maintenance of template projects** | You can define a project and its related elements for operative usage. This serves as a template for creating other operative projects. A project can contain individual elements that structure the project hierarchy, general organizational data, control profiles and default values. |
| **Maintenance of operative project** | You can create projects, or change and display existing projects and project parts. A project comprises of a header or definition, which serves as binding framework for all organizational elements created within a project. It can contain underlying elements, which describe either a certain task or a partial task that can be subdivided further. The structure tree displays the project object that you have selected in its hierarchical context. You can manually change the dependencies and assignments of individual project objects in the structure tree. Templates are available during processing to create new objects or structures in the current project by adding new project objects or copying project structures. For quicker access, you can store frequently used project data (project and project elements) in the worklist. |
| **Generating project settlement rules** | Costs are often collected in project, however, only temporarily. They are settled to one or more receivers as part of period-end processing. A settlement rule is essential for each object you want to settle. The settlement rule contains the receiver, the apportionment rule, and other settlement parameters. You can change the profile settings in the settlement rule parameters for an object. You can pass down the settlement rule defined for an investment project to the child WBS elements. The settlement rule is passed down until you explicitly define a WBS element as the settlement element. |
| **Reporting of project costs and budgets and display of actual project cost line items** | You can monitor the planned and actual costs as well as budgets for a project and use this for reporting purposes. You can use the actual line item report for projects to obtain flexible analysis of individual actual cost postings per various criteria. You can also view the real time costs of assigned orders. A number of functions support you in analyzing line items in reporting. These include sorting, filtering, or totaling. |
| **Monitoring project related procurements** | Using project control analytics you can monitor purchase requisitions, purchase orders, and account assigned to projects or project elements. |
| **Using the approval process and monitoring project release** | You can use the workflows for releasing a project. The workflow allows you to use one-step or multi-step approval process. From the overview of projects they are responsible for, the approvers can either approve or reject them, and add comments, if required. Based on the workflow configuration approvers can also send back the work items to requestors for rework. You will be notified if your project release has been rejected or sent back to you for rework. In case of rework, you can read the comments from the approver, make the required changes and resubmit. You can monitor the status of the project and also see who is responsible for an approval step. |
| **Archiving objects** | You can archive objects that have reached the end of the retention period. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

#### 3.13.1.2 Project Logistics Control

> 📄 FSD Reference: p172

**业务背景 (Business Background)**:

With Project Logistics Control, you can define, trigger and monitor demands that are related to a project or a WBS element. It complements the planning of project activities by enabling the planning and assignment of human resources as well as the planning and triggering of service and material procurement for projects and WBS elements. This prevents business disruptions and improves all the logistics-related execution aspects of a project.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Managing material and service demands** | You can create material and service demands and trigger and monitor the procurement of the requested materials and services for your project or WBS element. |
| **Managing resource demands** | You can create resource demands related to a project or WBS element, assign human resources to the demands, and monitor the actual efforts recorded during project execution. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

#### 3.13.1.3 Project Management

> 📄 FSD Reference: p173

**业务背景 (Business Background)**:

Project Management enables you to monitor your internal projects, for example R&D projects, and to steer them through your company's organization. You are supported to keep all involved stakeholders in the loop about your ongoing projects, for example during the regular steering committee meetings.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Displaying overview of projects** | As a project manager or as a member of project steering committees, you can get an overview of the most important details of your projects, for example: Upcoming milestones; Cost information; Status information. |
| **Displaying and updating projects** | You can display or update summarized project information that is essential for project review in steering committee meetings, such as the following: Milestones; Cost information; Status information; Team members; Related documents. |
| **Project collaboration** | SAP S/4HANA Cloud Public Edition supports the integration with a collaboration tool (currently the project management capability in SAP Project and Resource Management) to enable users to initiate the creation of a project-related collaboration in the collaboration tool and to access the project-related collaboration from SAP S/4HANA Cloud Public Edition. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

### 3.13.2 Product Lifecycle Management

#### 3.13.2.1 Integrated Product Development for Discrete Industries

##### 3.13.2.1.1 Bills of Material

> 📄 FSD Reference: p174

**业务背景 (Business Background)**:

A bill of material (BOM) is a formally structured list of the components that make up a product or assembly. The list contains the object number of each component, together with the quantity and unit of measure. The components are known as BOM items. BOMs are used in various situations where a finished product is assembled from several component parts or materials. They contain important basic data for numerous areas of a company.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Manage bills of material** | You can create a complete, formally structured list of components that make up a product or an assembly. You can create BOMs and also maintain BOMs for configurable materials. You can create and maintain manufacturing structures (manufacturing bill of materials (MBOMs)) from an engineering structure (engineering BOM (EBOM)). You can create MBOMs from EBOMs from an external data source, currently it is SAP Integrated Product Development. You can display and maintain the hierarchical tree structure of a multilevel BOM. SAP S/4HANA Cloud Public Edition supports the integration with a requirements management system (currently the requirements management capability of SAP Integrated Product Development). When a requirements management system is integrated, you can assign BOMs to requirements or models. |
| **Find where materials are used in BOMs** | You can search for a BOM header using a component that can be filtered for a plant, BOM usage, alternative BOM, etc. and view the where-used details of a material and replace a material with another material. |
| **Order bill of material** | You can create and maintain sales order-specific bills of material to meet your requirements. |
| **Comparing bills of material** | You can compare two different BOMs or same BOM with different date effectivities with each other to understand the similarities and differences between the compared BOMs. You can analyze the comparison based on the comparison result. You can explode the two BOMs down to the lowest level and compare in multilevel comparison. |
| **Mass maintenance of bills of material** | You can mass maintain several BOM headers or BOM items at a time thus reducing the effort of performing similar changes across many BOM headers or BOM items one at a time. You can simulate the operations (add, edit, or delete) to view the output before committing the changes to the database. You can view the processing details of a background job maintained in the job log. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

##### 3.13.2.1.2 Classification

> 📄 FSD Reference: p175

**业务背景 (Business Background)**:

The classification system allows you to use characteristics to describe various types of objects, and to group similar objects in classes – to classify objects, in other words, so that you can find them more easily later. You then use the classes to help you to find objects more easily, using the characteristics defined in them as search criteria. This ensures that you can find objects with similar or identical characteristics as quickly as possible.

Classes allow you to group objects together according to criteria that you define.
- You create classes for certain object types such as, for example, material.
- You use the class type to determine which object types can be classified in a class.
- You can assign characteristics to your class. These describe the objects that you classify in your class. When you assign a characteristic to a class, you can adapt (overwrite) the characteristic.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Classification handling** | You can define classes and their characteristics including characteristic values and organize classes into class hierarchies if the class type allows it. |
| **Finding objects** | Once you have set up a classification system in your company, you can search for the objects you have classified. You can also identify where a given characteristic and characteristic value is used. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

##### 3.13.2.1.3 Engineering Change Management

> 📄 FSD Reference: p176

**业务背景 (Business Background)**:

Engineering change management capabilities can be used to manage various aspects of product data (for example, bills of materials, materials, and documents) within a structured and controlled change process. Support for additional capabilities (including problem report, change request, change order, and change notice) orchestrated by structured and ad-hoc workflows ensure an effective change handling in product development.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Change master record handling** | You can define change master records. Change master records contain descriptive data, such as the reason for the change, and data with control functions, such as valid-from date and indicators for object types. In addition to this data, which you can maintain directly, there is data that the system updates automatically, such as administrative data. |
| **Revision level assignment** | You can identify material changes that are made with reference to a change number by using revision levels. A revision level can be assigned on a valid-from date when an object is changed with reference to a change number. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

###### 3.13.2.1.3.1 Change Records

> 📄 FSD Reference: p176

**业务背景 (Business Background)**:

Change record helps you to effectively manage changes by connecting people, processes, and products. This solution allows businesses to drive the end to end change management processes by handling change requests up until their implementation and release.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Detailed information about the change** | The Change record acts as a single source of truth for product changes. It contains the details such as the reason for change, expected completion date, participants involved in the change, objects involved in the change, required attachments, and status information. |
| **Business objects for change records** | You can integrate business objects from the process and discrete industries, such as materials, bill of materials, documents, master recipes, etc. |
| **Enhanced workflows with process route parallel-, ad-hoc-, and background tasks** | Workflow tasks can be parallel or sequential, and can be added ad-hoc or via a template; executed by the user or in the background. You can set processing times or deadlines, priorities, and recipients. You can switch from tabular to graphical view of workflow process to get a visual representation of process routes. |
| **Improved user experience in change record** | Change record provides an improved user experience with the overview chart that contains the change items added in the change record, graphical representation of process routes, integrated visual logs for status transitions, and color coded labels for change record status. Default classes can be maintained for the change record type and these classes are automatically assigned when a change record of the specific change record type is created. |
| **BOM Components** | You can use this feature to view valid BOM components for BOM or EBOM based on its change number, data of the change number header, or the current system date, whichever is available in the mentioned order. |
| **Change Record Hierarchies** | Product changes in change records can be efficiently structured using hierarchies created by split and merge functions. Split allows to divide a change record into two and moves the objects from one change record to another. Merge integrates the fragmented change requests by merging multiple change records into one and creates a successor that contains all items and attachments copied from the source change records. You can view the hierarchy of records to track changes to a change record and get the details of changes the original record has undergone. |
| **Visual status change** | Progress indicator allows to view the progress and get an instant overview of the change process using the record statuses. |
| **Dynamic field control** | The visibility of fields can be controlled per change record status and the behavior can be changed based on the type of fields and where they appear in the UI. |
| **Option to comment** | Commenting option is available at change record header and at change item levels for quick information exchanges. |
| **Integration with Classification System** | You can identify the classified objects using specific characteristics and characteristic values with the help of classification system. |
| **Integration with Attachment Service** | You can link business objects based on document management with the help of attachment service. |
| **API support for change record** | Change record API enables you to generate change records together with the change items and do multiple operations in bulk, faster and in parallel. |
| **Impact analysis scenarios for change record** | You can define impact scenarios and set up rules or constraints. When impact analysis is performed, the impact scenario identifies the objects that are impacted by the proposed change. |
| **Define process route Email template** | You can maintain an Email template for a Change Record Type. For every Process Route related foreground activity, the system triggers an Email based on the configuration. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

###### 3.13.2.1.3.2 Process Route Templates

> 📄 FSD Reference: p178

**业务背景 (Business Background)**:

You can use the process route workbench to activate and search for global process route templates.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Ability to search existing global process route templates** | You can search for global process route templates. The system will provide you an overview of which global templates exist, and whether or not they have been activated or changed since their last activation. |
| **Global process route templates activation** | You can activate the global process route templates, which enables you to use in the change record. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

###### 3.13.2.1.3.3 Flexible Workflow Templates

> 📄 FSD Reference: p178

**业务背景 (Business Background)**:

You can configure workflows to optimize the approval process for legal transactions in change records. You can define workflow templates according to various scenarios in the change process.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Managing workflow templates** | You can define new workflow templates, create new workflow templates based on existing templates, or edit existing templates. |
| **Defining workflow steps** | You can create workflow steps, assign specific users or entire roles to your workflow steps, define preconditions for the workflow tasks, and define exception handling. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

###### 3.13.2.1.3.4 Engineering Cockpit

> 📄 FSD Reference: p179

**业务背景 (Business Background)**:

You can filter and display an overview of engineering changes and engineering progress for different business objects. You can analyze the data with the help of graphic charts and initiate actions based on your insights.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Change processes overview** | You can view the ongoing change processes and trace their execution statuses. |
| **Quick links** | You can navigate easily to the related apps. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

###### 3.13.2.1.3.5 Impact Analysis Models

> 📄 FSD Reference: p179

**业务背景 (Business Background)**:

You can create impact analysis scenarios, which can be used to perform impact analysis in change records. With impact analysis, you can identify business objects that are impacted during change evaluation.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Impact analysis scenarios** | You can create, edit, or delete impact scenarios. The impact scenario represents the model or the association the object has with the other objects. Change constraints or rules can be assigned to the model which decide the scope of the impact. |
| **Graphical and Tabular views** | You can view two different versions of the same data in tabular and graphical format and can easily switch between them. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

##### 3.13.2.1.4 Embedded Systems Management

> 📄 FSD Reference: p180

**业务背景 (Business Background)**:

Embedded software is computer software that is embedded in one or multiple products. It provides functions together with various hardware and systems. For example, embedded software can be used to control or optimize the functions of the mechanical part or the electrical part of a product.

If you work with products that have one or multiple pieces of embedded software, you can use embedded software management to view and manage your software.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Embedded Software Management** | You can use a specific material type to define software. You can also use a specific document type to define software versions. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

##### 3.13.2.1.5 Product Structure Management

> 📄 FSD Reference: p180

**业务背景 (Business Background)**:

Product structure management can be used in early development phases. Product structures consist of a set of hierarchically ordered objects with the purpose of documenting one product or a set of similar products. They use abstract representations of products and components.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Manage product structure** | You can create new product structures and maintain them (product families, product items, product views, and software items). You can also view the product structures in a customizable table. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
⊙ The features for Product Structure Management are only available for customers who have licensed these features before SAP S/4HANA Cloud 1908 including maintenance for these features. For further information, please contact your SAP Account Executive.

**关联Scope Items**: —

---

##### 3.13.2.1.6 SAP Integrated Product Development Integration

> 📄 FSD Reference: p181

**业务背景 (Business Background)**:

SAP S/4HANA Cloud Public Edition can be integrated with SAP Integrated Product Development to enable data exchange from SAP Integrated Product Development to SAP S/4HANA Cloud Public Edition.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Bill of material integration** | You can transfer BOM data from SAP S/4HANA Cloud Public Edition to SAP Integrated Product Development (read and write access). |
| **Change object integration** | You can transfer change object data from SAP S/4HANA Cloud Public Edition to SAP Integrated Product Development (read access). |
| **Document info record integration** | You can transfer document info record data from SAP S/4HANA Cloud Public Edition to SAP Integrated Product Development (read access). |
| **Product integration** | You can transfer product data from SAP S/4HANA Cloud Public Edition to SAP Integrated Product Development (read access). |
| **Plant integration** | You can transfer plant data from SAP S/4HANA Cloud Public Edition to SAP Integrated Product Development (read access). |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

### 3.13.3 Advanced Product Lifecycle Management

#### 3.13.3.1 Integrated Product Development for Discrete Industries

##### 3.13.3.1.1 Advanced Variant Configuration

> 📄 FSD Reference: p182

**业务背景 (Business Background)**:

Variant configuration is for manufacturing complex products. Manufacturers often have to offer new variants of their products, and new variants can be created by modifying existing product designs as they process the order. The important thing is to react quickly to customers' requirements.

The customer determines the features of the product. A customer buying a car, for example, can choose the features of the car and combine these features as required. The product configurator improves information exchange between sales, engineering, and production. Variant configuration helps the customer or salesperson to put together specifications for the product and ensure that the product can be produced from these specifications.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Manage configuration model** | You can use a configurable product to cover all variants of a product in your company. A class is used to hold the characteristics that describe a configurable product. By linking the class to the configurable product, you allow the product to be configured using the characteristics of the class. You can create a super BOM for a configurable product, containing all the components for producing all variants of the product. Often not all combinations of features are possible for either technical or marketing reasons. You can use dependencies and constraints to control which combinations are allowed. In configuration profiles for configurable objects, you define central settings for configuring the object. You can use variant conditions to influence the price of a configurable product depending on the characteristic values assigned. You can use single-level and multi-level variant configuration models. You can use configurable routings. |
| **Manage product variants** | You can create a product variant, which is a product that can be kept in stock and that arises from an individual configuration of a configurable product. |
| **Interactive configuration** | During configuration, in the sales order for example, the user assigns values to characteristics. Dependencies and constraints coming from the configuration model are brought into consideration. Advanced variant configuration is also integrated into the purchase order. |
| **Configuration simulation** | You can use the configuration simulation to check your configuration model. In the configuration simulation, you can test whether you have created the objects correctly and whether your dependencies work. |
| **Low-level configuration** | Low-level configuration refers to "background" explosions of configurable objects, like bills of material (BOMs). For example, it's used in material requirements planning (MRP). Here characteristic values from the sales order are automatically used to determine the BOM components. |
| **Variant configuration data in embedded analytics** | This feature allows you to generate CDS views. You can use these CDS views to publish the classification/configuration information and to visualize it with application data. You can use these to model your own CDS view queries, in which variant configuration data can be combined with other objects, such as a sales order. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

##### 3.13.3.1.2 Embedded Systems Development

> 📄 FSD Reference: p184

**业务背景 (Business Background)**:

Embedded systems development combines the development of embedded software and systems engineering.

Embedded software has a specific requirement on the hardware and software that allows it to function accurately. To manage the compatibility information between software and other parts of a product, you can use constraint management.

As part of systems engineering, you can also link objects from external system models to the business objects in your system for full traceability.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Managing Constraints** | You can view and maintain the compatibility information of embedded software, including: Hardware constraints: the compatibility between embedded software and hardware; Software constraints: the compatibility between embedded software and other software. |
| **Checking Software Compatibility** | You can check software compatibility in a bill of material (BOM). |
| **Managing Model Object Assignments** | You can assign objects from external system models to the business objects in your system to support full traceability. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
⊙ The features for Embedded Systems Development are only available for customers who have licensed these features before SAP S/4HANA Cloud 1908 including maintenance for these features. For further information, please contact your SAP Account Executive.

**关联Scope Items**: —

---

##### 3.13.3.1.3 Handover to Manufacturing

> 📄 FSD Reference: p185

**业务背景 (Business Background)**:

You use this business process to create and maintain manufacturing bills of material (MBOMs) by using the engineering bills of material (EBOMs) or product structures.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Managing planning scope alternative** | You can start planning for an MBOM by creating a planning scope using the bill of material, product structure, or already existing planning scope. The business application allows you to create, change, or delete existing planning scope. On creation of a new planning scope alternative for a bill of material, a new alternative MBOM is created. |
| **Planning hand over of EBOMs or product structures** | You can use EBOMs or product structures for planning the MBOM by: Making a direct copy of the EBOM or product structures; Adding or removing the components from the MBOM; Creating an MBOM; Restructuring the planned MBOM to get the desired target MBOM. |
| **Creating or maintaining BOM** | You can create or overwrite existing BOMs by adding or removing BOM components. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
⊙ The features for Handover to Manufacturing are only available for customers who have licensed these features before SAP S/4HANA Cloud 1908 including maintenance for these features. For further information, please contact your SAP Account Executive.

**关联Scope Items**: —

---

##### 3.13.3.1.4 Product Structure Management

> 📄 FSD Reference: p186

**业务背景 (Business Background)**:

Product structure management can be used in early development phases. Product structures consist of a set of hierarchically ordered objects with the purpose of documenting one product or a set of similar products. This is effective for high-volume, repetitive manufacturing, for example, in the automotive industry, as well as for complex machinery and equipment.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Manage variants in product structure** | You can manage product variants, product item variants, or software variants in product structures. You can assign materials to product variants, product item variants, or software variants. |
| **Manage software in product structure** | You can manage software in product structures. For example, you can check whether a software material version is compatible with other software and hardware materials in the product structure. You can also specify a version for a software. |
| **Change BOM in product structure with product view** | You can change bill of material items in product structures with product view. |
| **Simulate product structure** | You can simulate the product configuration and check the correctness of object dependency maintenance. You use simulation to simulate the explosion of a product structure for a specific set of configuration parameters. |
| **Manage object dependencies in product structure** | You can control the selection of variants for a particular product item or software item in product structures. You can do this using the dependency maintenance table. |
| **Trigger product structure handover to manufacturing BOM** | You can trigger product structure handover to manufacturing bills of materials (BOMs). You can create and update a manufacturing BOM. |
| **Manage product structures** | You can create new product structures and maintain the objects of existing product structures. You can also view the objects that are related to their respective product structures in a customizable worklist. |
| **Enable product structure variants in change record** | You can manage the change of product structure variants in change record. You can select existing variants in product structures to add into a change record as a change object and navigate to the target product structure to apply changes. |
| **Enable the where-used function in product structures** | You can maintain product structure nodes where the selected product structure node is used to assemble product bottom-up. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
⊙ The features for Product Structure Management (Advanced PLM) are only available for customers who have licensed these features before SAP S/4HANA Cloud 1908 including maintenance for these features. For further information, please contact your SAP Account Executive.

**关联Scope Items**: —

---

##### 3.13.3.1.5 External PLM System Integration

> 📄 FSD Reference: p187

**业务背景 (Business Background)**:

SAP S/4HANA Cloud Public Edition can be integrated with external Product Lifecycle Management systems to enable data exchange from the external PLM system to SAP S/4HANA Cloud Public Edition.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Change management integration** | You can receive data for an engineering change triggered in the external PLM system. |
| **Document version management integration** | You can send and receive document data from an external PLM system. |
| **Product version management integration** | You can create material masters in the SAP S/4HANA Cloud Public Edition Cloud system, based on data created in an external PLM system and business semantics. You can send and receive product data from an external PLM system. |
| **Structure version management integration** | You can receive bills of material in the SAP S/4HANA Cloud Public Edition system. |
| **Production operation list integration** | You can receive production operation lists that are created in an external PLM system and transfer them to classic PP routings in the SAP S/4HANA Cloud Public Edition system. |
| **Variant definition integration** | You can receive variant definitions that were created in an external PLM system and use them for variant configuration in the SAP S/4HANA Cloud Public Edition system. |
| **Vendor integration** | You can send and receive vendor data from an external PLM system in the SAP S/4HANA Cloud Public Edition system for business partner integration. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

### 3.13.4 Product Compliance

#### 3.13.4.1 Product Marketability and Chemical Compliance

> 📄 FSD Reference: p188

**业务背景 (Business Background)**:

With the product marketability and chemical compliance solution, you manage chemical compliance for your products across your organization. The features of this business solution support you to ensure product marketability and brand protection, and to reduce compliance costs. They enable you to manage regulatory requirements and compliance assessments of your product portfolio.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Management of compliance requirements for product marketability** | You can manage product-related and substance-related compliance requirements based on legislation, industry standards, and customer or corporate-specific requests. Regulatory information and calculations are the basis for the compliance requirements that your products need to meet. |
| **Management of marketability assessment process** | You can assess the marketability of your products: You can start or request the initial assessment of a product and determine the relevant compliance requirements for your product. The system carries out compliance checks, thus supporting you to fulfill relevant compliance requirements for your products. If the compliance results are affected after a change, the compliance checks are reprocessed. You can perform market assessments of your products. |
| **Product marketability data embedded in other business processes** | Marketability assessment can be used in processes within the value chain: Requests for marketability assessment are automatically created based on changes in the product master. Marketability checks are integrated into sales and delivery processes to verify whether a product is marketable in a specific country/region. Based on the market assessment, the document could be blocked. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

#### 3.13.4.2 Dangerous Goods Management

> 📄 FSD Reference: p189

**业务背景 (Business Background)**:

The dangerous goods management solution enables you to manage data that is needed to assess and classify products according to dangerous goods regulations. The solution also provides the classification information for specific processes within the value chain, such as sales and delivery, where the information can be used for a check and for printing.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Management of compliance requirements for dangerous goods** | You can manage compliance requirements based on dangerous goods regulations. The compliance requirements contain dangerous-goods-related regulatory information that you can use in the dangerous goods assessment process. |
| **Management of dangerous goods assessment processes** | You can assess and classify unpackaged and packaged products according to different dangerous goods regulations. |
| **Integration of dangerous goods data in other business processes** | Dangerous goods information can be used in processes within the value chain: A transport permissibility check is carried out in business documents in sales, outbound delivery, purchasing, and transportation processes. It verifies whether the transport of a product is allowed in a certain country/region by a specific mode of transport. If not, the business documents could be blocked. Dangerous goods data can be printed on sales, outbound delivery, and transportation documents. Dangerous goods data is provided in electronic messages (EDI) in sales, outbound delivery, and transportation processes. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

#### 3.13.4.3 Safety Data Sheet and Label Management

> 📄 FSD Reference: p190

**业务背景 (Business Background)**:

With this business solution, you manage safety data sheets (SDS) and labels according to chemical regulations and requirements.

A safety data sheet is legally required in most countries/regions of the world to ensure safe handling of chemicals and other hazardous products. Safety data sheet formats can vary from source to source within a country/region, depending on national requirements. Safety data sheets are a widely-used system for cataloging information on chemicals, chemical compounds, and chemical mixtures. Safety data sheet information may include instructions for the safe use and potential hazards associated with a particular material or product. The safety data sheet should be available for reference in the area where the chemicals are being stored or in use.

A product label is legally required in most countries/regions of the world to ensure safe transportation of hazardous products. Label layout can vary depending on regulations and other factors such as product size. Label layout and printing are carried out in external systems and supported by provided open interfaces.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Management of compliance requirements for safety data sheets and labels** | You can manage compliance requirements for safety data sheets and labels based on legislation and countries/regions. Safety data sheet-related regulatory information is the basis for the compliance requirements that your products need to meet. |
| **Management of safety data sheet process** | You can upload safety data sheets in different languages into Product Compliance and organize the legally required safety data sheets by country/region and regulation. |
| **Management of label process** | You can maintain label information for a product in the SAP S/4HANA system, such as a relevant compliance requirement and label template (designed in an external system). You can print the label via an external system. |
| **Integration of safety data sheets in other business processes** | Safety data sheet information can be used in processes within the value chain: You can send safety data sheets in the required languages to your customers and to relevant authorities electronically. The automatic shipment of safety data sheets is integrated into delivery processes. Updated versions of safety data sheets are resent automatically. Checks in purchasing, sales and delivery processes are carried out to prevent products from being sold into markets if the required safety data sheets are not available. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

### 3.13.5 Circular Economy

#### 3.13.5.1 Responsible Design and Production

> 📄 FSD Reference: p191

**业务背景 (Business Background)**:

SAP Responsible Design and Production is a service on SAP Business Technology Platform that supports you in managing your product design and production decisions in line with regulatory and non-regulatory drivers for sustainable business practices.

**核心功能 (Key Features)**:

| 功能 (Feature) | 说明 (Use / Description) |
|---------------|------------------------|
| **Integration with External Extended Producer Responsibility Solutions** | SAP S/4HANA Cloud Public Edition supports the integration with external extended producer responsibility solutions (currently SAP Responsible Design and Production) to fulfill your extended producer responsibility (EPR) and packaging taxes based on information from SAP S/4HANA Cloud Public Edition. |

**⚠ 限制与注意事项 (Constraints / Notes)**:
*(无)*

**关联Scope Items**: —

---

## Summary of FSD Sections Covered

| Section | Application Area | FSD Pages |
|---------|-----------------|-----------|
| 3.12 | Professional Services | p166–170 |
| 3.12.1 | Customer Project Management | p166–169 |
| 3.12.2 | Integration with External Resource Management Services | p170 |
| 3.13 | R&D / Engineering | p170–192 |
| 3.13.1 | Enterprise Portfolio and Project Management | p170–173 |
| 3.13.1.1 | Project Financial Control | p170–172 |
| 3.13.1.2 | Project Logistics Control | p172–173 |
| 3.13.1.3 | Project Management | p173 |
| 3.13.2 | Product Lifecycle Management | p174–182 |
| 3.13.2.1.1 | Bills of Material | p174–175 |
| 3.13.2.1.2 | Classification | p175–176 |
| 3.13.2.1.3 | Engineering Change Management | p176 |
| 3.13.2.1.3.1 | Change Records | p176–178 |
| 3.13.2.1.3.2 | Process Route Templates | p178 |
| 3.13.2.1.3.3 | Flexible Workflow Templates | p178–179 |
| 3.13.2.1.3.4 | Engineering Cockpit | p179 |
| 3.13.2.1.3.5 | Impact Analysis Models | p179–180 |
| 3.13.2.1.4 | Embedded Systems Management | p180 |
| 3.13.2.1.5 | Product Structure Management (PLM) | p180–181 |
| 3.13.2.1.6 | SAP Integrated Product Development Integration | p181–182 |
| 3.13.3 | Advanced Product Lifecycle Management | p182–188 |
| 3.13.3.1.1 | Advanced Variant Configuration | p182–184 |
| 3.13.3.1.2 | Embedded Systems Development | p184–185 |
| 3.13.3.1.3 | Handover to Manufacturing | p185–186 |
| 3.13.3.1.4 | Product Structure Management (Advanced PLM) | p186–187 |
| 3.13.3.1.5 | External PLM System Integration | p187–188 |
| 3.13.4 | Product Compliance | p188–191 |
| 3.13.4.1 | Product Marketability and Chemical Compliance | p188–189 |
| 3.13.4.2 | Dangerous Goods Management | p189–190 |
| 3.13.4.3 | Safety Data Sheet and Label Management | p190–191 |
| 3.13.5 | Circular Economy | p191–192 |
| 3.13.5.1 | Responsible Design and Production | p191–192 |

---

*Document generated from SAP S/4HANA Cloud Public Edition 2602 Feature Scope Description, pages 166–192.*
