Configuration Guide | PUBLIC

Document Version: 1.0 – 2022-05-03

Configuration Guide for PLM System Integration

for SAP S/4HANA
2.0 FP02
© 2022 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 Initial Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 PLMSI Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.1 Define Domain Model Code Lists. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.2 Define Scenario and Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3.3 Number Range Maintenance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Maintain Range: Constraint Net ID Number Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Maintain Range: Variant Definition ID Number Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Maintain Range: Variant Option ID Number Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Maintain Range: Variant Table ID Number Range. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.4 Define Change Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.5 Define Document Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

3.6 Define Factory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

3.7 Define Product Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.8 Define Production Operation List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

3.9 Define Structure Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3.10 Define Variant Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.11 Business Add-Ins (BAdI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

BAdI: Define Custom Conversions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

BAdI: Document Version Setting of SAP Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

BAdI: Filter Relevant ECN for CO Outbound Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

BAdI: Variant Configuration Selection Condition for Structure Version. . . . . . . . . . . . . . . . . . . . 30

BAdI: Variant Configuration Selection Condition for POL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

BAdIs for Inbound Post-Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4 Additional Settings for SAP S/4HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.1 Define Variant Configuration Processing Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.2 BAdI: Change Object Responsible. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

4.3 BAdI: Filter Relevant CR for CO Outbound Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Configuration Guide for PLM System Integration for SAP S/4HANA

2 PUBLIC Content
1 About This Guide

This guide describes the configuration of PLM system integration for SAP S/4HANA for the integration with an
external PLM system.

For more information about the installation as well as security and operations, refer to the Administration
Guide in the SAP Help Portal.

Product Information

Product PLM system integration for SAP S/4HANA

Release 2.0 FP02

Released Q2, 2022

This guide addresses the following target audience:

● System administrators
● Technical consultants
● Key users

Configuration Guide for PLM System Integration for SAP S/4HANA

About This Guide PUBLIC 3
2 Initial Configuration

Make sure you carry out the initial configuration steps outlined here.

Configuration Content

We provide standard content in the form of BC Sets for the integration of an external PLM system.

You can leverage this content for the initial configuration of your SAP system. You can change and extend the
configuration wherever necessary, to fit your needs.

Prerequisites

Before you can activate standard content, you need to carry out the following activity:

● In Customizing, choose Cross-Application Components Document Management General Data

General Data Define Data Carrier . Choose Define data carrier type "server, front end" and verify if an
entry with description Default is maintained for type PC. If no such entry is maintained, create it and save
your entry.

Content Activation

1. Use transaction SCPR3 to view the available content in /PLMF/BCS_OVERALL and /PMLS/BCS_CO.
2. Use transaction SCPR20 to select and activate /PLMF/BCS_OVERALL and /PMLS/BCS_CO.

 Note

If there are activation issues, please choose the Expert Mode and start the activation again.

3. On the same screen, verify that the activation has been successful.

Content Server Settings

You can use the built-in content repository DMS_C1_ST to test your content server setup. For more information,
see the chapter Installing the SAP Content Server in the Administration Guide for PLM system integration.

 Note

You need to make the following settings to ensure correct data exchange when using the built-in content
repository DMS_C1_ST: Call up the Display Content Repositories: Detail screen and ensure the following
settings are active:

● HTTPS on frontend: HTTPS required

● HTTPS on backend: HTTPS required

Configuration Guide for PLM System Integration for SAP S/4HANA

4 PUBLIC Initial Configuration
3 PLMSI Configuration

This chapter outlines the configuration activities you need to carry out to make full use of system integration
via this add-on.

You carry out all necessary configuration settings in Customizing under Cross-Application Components
PLM System Integration. Here, you find all necessary customizing activities to configure this add-on.

For general information on Customizing, search for the chapter The IMG Structure on the SAP Help Portal.

Version Configuration

You can configure which scenario is selected for a certain business process (based on a list of pre-defined
scenarios), which key and value mappings are to be used on which fields, and which fixed values (for example,
material industry sector, default document type, default class for documents, and so on) are used.

Value Mapping

This version supports 1:1 value mapping. Use Customizing for Define Domain Model Code Lists [page 5] to
view and enhance the list of fields for which a value mapping is possible.

Implement the configuration in the following order:

1. Define Domain Model Code Lists [page 5]

2. Define Scenario and Version [page 6]
3. Define Product Version [page 19]
4. Define Document Version [page 15]
5. Define Structure Version [page 24]
6. Define Change Object [page 12]
7. BAdI: Define Custom Conversions [page 27]

3.1 Define Domain Model Code Lists

In this Customizing activity, you define code lists that provide field values for the data exchange between the
SAP system and the external PLM system.

The Meta Domain Model uses code lists to define allowed or expected values for certain fields. These values
can then be used, for example, to map certain values from an external PLM system to the respective values in
the SAP system (for example, material type).

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 5
Depending on your deployment, you can find sets of preconfigured values in this Customizing activity. You can
modify or delete these values as required, or add additional values to enhance your customizing options.

In real-time business scenarios, fields can have different sets of valid values based on the context. For example,
while creating a document in SAP S/4HANA, the list of possible values for DocumentType may be different
from the valid list of DocumentTypes in the external PLM system.

In addition, it's also possible for the source of the valid document types to be different in each of these
scenarios. For example, the list of valid document types for an SAP document can come from the SAP system,
while the list of valid document types for a document from an external PLM system can come from a domain.
This means that the source of valid values is different depending on the software version. Code Lists have been
developed to cater to these scenarios.

 Note

Default code lists are provided via BC Sets (see PLMSI Configuration [page 5]). You can enhance and
modify the default code lists.

3.2 Define Scenario and Version

In this Customizing activity, you carry out a number of definitions for the scenario and version. These settings
are used to differentiate between integration configuration setups.

These settings will be used to distinguish between different sets of integration configurations. A scenario
includes settings for inbound and outbound messages. The external application selects the relevant scenario
either as defined by an incoming message or based on the following attributes:

● External application
● API version
● Component version
● Logical instance

Inbound, the external application is the sending application. Outbound, it’s the receiving application. We
recommend that you follow the following configuration steps in the given order.

 Note

A scenario can only exist with a version.

Prerequisites

For a specific integration configuration, you first create a scenario and an initial version. Subsequently, you can
create additional scenario versions for each scenario. A scenario version defines a certain set of configurations.
Scenario versions can be maintained independently.

You define specific scenario determination criteria that are used to determine which scenario and scenario
version is used for a specific integration run.

Configuration Guide for PLM System Integration for SAP S/4HANA

6 PUBLIC PLMSI Configuration
Activities

1. Create a new scenario ID or select an existing scenario ID.

2. Choose a Scenario.
3. Choose Scenario Version and define detailed data for the required scenario:
Enter Scenario Version, Key Mapping Mode, and Scenario Description. You can define the following key
mapping modes:
○ Acceptance Mode
○ Uniqueness check isn’t performed, no message raised
○ Key mapping is updated with new assignment to store multiple assignments
○ Overwrite Mode
○ Uniqueness check isn’t performed, no message raised
○ Key mapping is updated, if a row with the same PLM ID or BUS ID is found
○ Exclusive Mode
○ A check for uniqueness by part of PLM ID or BUS ID is performed and error message raised in case
of violation.
○ Creation of object aborted -> no change of key mapping for found rows

 Note

The default setting is Overwrite. This allows that the sending system changes the key mapping, thus
creating a new object for a certain time.

4. Select if AIF logging is active (on) or not (off).

5. Define which object-related messages are returned in the message result. Select the relevant SAP message
type using the Send API System Message Type (Send Type) dropdown list:
○ All Types (I-Info, S-Success, E-Error, W-Warning)
○ Error
○ Error and Warning
○ Error and Success
For more information, see Error Handling.
○ Additionally, you can define generic values that will be used for the determination, in case no specific
value is defined. Moreover, you can define an option to use the highest available version of a scenario.
When you transfer a basic material from an external PLM system to the SAP system, you don't need to
maintain a change number manually. The SAP system will exchange existing change numbers with the
an external PLM system and map them, based on the configuration made in the step Define Value
Mapping.

 Note

You can find the change number in Create Change Number (transaction CC01) or Display Change
Number (transaction CC03) in the SAP system.

6. If Compatibility Mode is selected, a key mapping is created between inbound object IDs and SAP PLM
entities if existing objects have not been created by the integration and if preconditions are met. You can
set Compatibility Mode as follows:
○ Off - Compatibility mode is inactive. If a key mapping does not exist but the object exists in the SAP
system, then the error message “No integration for bus.ID &1 exists, but the SAP object already exists”
is logged and the process flow is stopped.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 7
 ○ By ID - Compatibility mode is active. If a key mapping does not exist but the object exists in the SAP
system, then a key mapping is created for the object.
7. Define Value Mapping: In this activity, you can map values coming from the an external PLM system to
values in the SAP system. You can use or create a value mapping ID and assign specific values to this value
mapping ID.
Example: Mapping
You want to map an external value for a Basic Material to a basic material in the SAP system.
1. Select a scenario and scenario version.
2. Choose Define Value Mapping and choose a value mapping ID.
The Mandatory checkbox controls if the system issues a warning or an error in case a value is missing.
Select the checkbox according to the desired result:
○ Mandatory checkbox is selected: If a value is missing, an error is issued, and processing is
interrupted at this step.
○ Mandatory checkbox isn’t selected: If a value is missing, a warning is issued, and the default value
from the mapping is used.
3. Choose Define Inbound Mapping Values and assign the external value, in this case a basic material:
○ In the External Value field, enter the material, for example, Metal.
○ In the Internal Value field, enter the internal material you would like to map to, for example, SAP
Metal.
4. Choose Define Outbound Mapping Values and assign the external value, in this case a basic material:
○ In the External Value field, enter the material, for example, Metal.
○ In the Internal Value field, enter the internal material you would like to map to, for example, SAP
Metal.
You can now use this value when creating a product version, document version, structure version (inbound
values only) or change object (inbound values only).
8. Define Parallel Processing Settings for Inbound: Here, you define how to parallelize and package the
processing of the objects included in one payload, in order to improve performance. You can make these
settings for the object type ProductVersion and the request type Maintain. Choose the Object Type,
Request Type, Logon/Server Group, and Default Package Size.

 Note

The default package size defines the ideal size for packages. Depending on the available data, the
package size may differ.

Select the Active checkbox to activate parallel processing.

You can disable parallelization for your user by setting the /PLMF/DISABLE_PAR parameter in transaction
SU03. This disables parallelization even it is activated in Customizing for the respective scenario version
combination. If parallelization is active but disabled via the user settings, the system issues a warning.
9. Define Scenario Determination Rules: In this activity, you define the necessary scenario determination
criteria. You can specify attributes to be valid for any received value by flagging them as generic, as
required.
You can select the Highest Available Version option or enter a specific version to use in the Version field.
The highest version is determined by sorting the versions in alphabetical order.
You can configure that the Scenario ID and Scenario Version to be used is defined by the sender. To do so,
select the option Scenario Determination by Message.

Configuration Guide for PLM System Integration for SAP S/4HANA

8 PUBLIC PLMSI Configuration
  Note

If Scenario Determination by Message is selected, the following conditions apply:

○ The relevant lines are defined by External Application, API Version, Logical Instance, and
Component Version.
○ The scenario ID and scenario version are selected according to the values defined in the payload
message header data for configuration and configurationVersion.
○ It is not possible to enter a scenario and scenario version in the configuration.
○ The Highest Available Version option can't be set.
○ If no relevant scenario and scenario version can be found, an error message is generated, and data
processing stops.

Define Scenario Determination - Configuration Example for Siemens Teamcenter Integration

Sce­
nario Sce­
Exter­ Deter­ nario ID
Exter­ nal Ap­ Compo­ Logical mina­ (sce­ Highest
nal Ap­ plica­ API Compo­ nent Logical In­ tion by nario to Sce­ Availa­
plica­ tion Ge­ API Version nent Version In­ stance Mes­ be nario ble Ver­
tion neric Version Generic Version Generic stance Generic sage used) Version sion

X X X X SAP_De X
fault

TEAM­ 1 20 SAP_De 002

CEN­ fault
TER

TEAM­ 2 20 SAP_Sp 001

CEN­ ecific1
TER

TEAM­ X 21.1 SAP_Te 004

CEN­ amcen­
TER ter_21.1

TEAM­ 2 X SAP_ot 001

CEN­ her_ex­
TER ample

10. Define External System: Here, you define the external system for outbound data transfer. You define the
receiving (target) systems for sending data from the SAP system to an external PLM System.
For an External Logical System and External Application, specify RFC Destination (mandatory), APIVersion
(default is 0), and Component Version. Note that as of release 2.0 FP02, the API version must be 2. For
more information, see Installing PLM System Integration for SAP S/4HANA.
You can designate one logical system to be the default destination for change objects and product versions
by selecting Change Object Default Destination and Product Version Default Destination.
For existing objects by receiving DM object type, the external system configuration is used to determine
the logical instance, RFC destination and external application. The scenario determination logic uses
values from the external system configuration to retrieve the scenario/version that will be used to build up
the payload.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 9
 For new objects by receiving DM object type and with no logical instance, the external system
configuration, based on the default setting for the DM object type, is used to call the scenario
determination logic to retrieve the scenario and version that will be used to build up the payload. The
values for Time Zone and Time Rounding define the time zone of the external system and how the SAP
system handles and converts the validity of incoming and outgoing object data (ValidFrom), for example,
for change objects:
○ The SAP system converts incoming timestamp data (ValidFrom) in accordance with the customizing
settings for the external system: You can choose to round up or down. Internally, the SAP system only
uses date format for validity. For empty (ValidFrom) data, the system uses the default date 01.01.1900.
The default valid-from date may be overridden by object-specific customizing. It is not considered
when processing objects with a change master.
○ When returning time data to the external system, the SAP system interprets the stored valid-from
value with the customized time zone of the target system.

3.3 Number Range Maintenance

This node groups several activities for number range maintenance.

3.3.1 Maintain Range: Constraint Net ID Number Range

In this Customizing activity, you make the required settings for the number ranges used for generating unique
names for constraints and constraint nets in order to restrict available values.

Prerequisites

● At least one interval should be created. Without an interval for number ranges, constraints and constraint
nets cannot be created and the restriction of available values for characteristics is not possible.

Activities

1. Display Intervals: Here, you can see the existing intervals.

2. Change Intervals: Here, you can add a new interval, and change or delete existing intervals for a number
range.
3. Change NR Status: Here, you specify the status for a number range.

Configuration Guide for PLM System Integration for SAP S/4HANA

10 PUBLIC PLMSI Configuration
3.3.2 Maintain Range: Variant Definition ID Number Range

In this Customizing activity, you make the required settings for the number ranges used for generating unique
names for variant definitions in order to restrict available values.

Prerequisites

● At least one interval should be created. Without an interval for number ranges, variant definitions cannot
be created and the restriction of available values for characteristics is not possible.

Activities

1. Display Intervals: Here, you can see the existing intervals.

2. Change Intervals: Here, you can add a new interval, and change or delete existing intervals for a number
range.
3. Change NR Status: Here, you specify the status for a number range.

3.3.3 Maintain Range: Variant Option ID Number Range

In this Customizing activity, you make the required settings for the number ranges used for generating unique
names for variant options in order to restrict available values.

Prerequisites

● At least one interval should be created. Without an interval for number ranges, variant options cannot be
created and the restriction of available values for characteristics is not possible.

Note: If the length of a variant option ID exceeds the length of the Characteristic Name (ATNAM) field of 30
characters, the ID cannot be used for a variant option. In this case, the number range must be defined in the
Customizing activity Maintain Range: Variant Option ID Number Range. This is then used to determine the
variant option ID name.

Activities

1. Display Intervals: Here, you can see the existing intervals.

2. Change Intervals: Here, you can add a new interval, and change or delete existing intervals for a number
range.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 11
3. Change NR Status: Here, you specify the status for a number range.

3.3.4 Maintain Range: Variant Table ID Number Range

In this Customizing activity, you make the required settings for number ranges for naming variant tables. The
numbers are used to generate unique names for variant tables, which are created for constraints and
constraint nets in order to restrict available values.

Prerequisites

● At least one interval should be created. Without an interval for number ranges, variant tables cannot be
created and the restriction of available values for characteristics is not possible.

Activities

1. Display Intervals: Here, you can see the existing intervals.

2. Change Intervals: Here, you can add a new interval, and change or delete existing intervals for a number
range.
3. Change NR Status: Here, you specify the status for a number range.

3.4 Define Change Object

In this Customizing activity, you maintain all necessary definitions to map the change object data from the
Meta Domain Model to the respective SAP change object.

The SAP change object represents a change number from the change master and its revision.

We recommend that you follow the configuration steps below in the given order.

Prerequisites

● You have made all relevant settings in Customizing for Define Domain Model Code Lists [page 5]. You can
add additional values as required before you start mapping or during the mapping process.
● Scenarios and versions have been configured in the system, in Customizing for Define Scenario and
Version [page 6].
● You have maintained a change master (CM) profile in Customizing for Maintain Profile under Cross-
Application Components Engineering Change Management .

Configuration Guide for PLM System Integration for SAP S/4HANA

12 PUBLIC PLMSI Configuration
Activities

1. In the dialog box, select a Scenario ID and Scenario Version to specify the scenario ID and version for which
you would like to define structure version data. Choose Continue.
2. Define Mapping of Change Object Type: Here, you map a Domain Model change object type to the SAP
change object type.
Choose the Domain Model change type, default authorization group, and Change Master (CM) profile. For
outbound mapping, you can select and set a Default Output Type, and if the Outbound Communication ID
Mode will be defined by the SAP system or the exernal PLM system. You can also set a Valid From date. For
more information on the Valid From date, see Define Scenario and Version [page 6].
You can maintain a change master profile in Customizing for Maintain Profile under Cross-Application
Components Engineering Change Management .
When you integrate the following objects, please ensure that the profile enables ECN usage as outlined in
the table below:

Object Type Profile

ECN Object Type DM Object Type

Material BOM SV

Task List POL

Document DV

Material PV with revision

Characteristics of Class Variant Model

Object Dependencies SV/POL with selection conditions

Variant Table Variant Model

For mapping during inbound processing (sending from an external PLM system to the SAP system):
○ Change Object Type specifies whether the Domain Model change type is mapped to a change master
(ECN) or a change record.
○ Change Record Type specifies the type for change record. You can maintain change record types in
Customizing for Logistics – General under Product Lifecycle Management (PLM) Change Records
Settings for Engineering Changes Define Engineering Change Record Types .
○ Change Record Responsible sets the Business Partner ID of the person responsible for the change
record if no Business Partner ID can be determined based on information from the external PLM
system.
For mapping during outbound processing (sending from the SAP system to an external PLM system):
○ Default Outbound Type indicates that this is the default CO type. You can set this only once per CO
type.
○ Default Outbound Item Type specifies the default item type for the CO type.
This field is used only for the ECN scenario. For the CR scenario, the Item type is determined based on
the settings in Define Relation Type (when Outbound Relevant is selected).
○ Outbound Communication ID Mode sets how the change object ID is determined:
○ Defined by SAP – The Domain Model ID is sent as the change object ID to the external system
○ Defined by external PLM – The change object is sent with an empty Domain Model ID and external
PLM system sets the change object ID

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 13
 ○ For change records only, Solution Item Relevance indicates why the item is included in the change
record. You can maintain relevance types in Customizing for Logistics – General under Product
Lifecycle Management (PLM) Change Records Settings for Engineering Changes Define Item
Relevance .
Set a default Valid From date. This is used if the external system does not provide a valid from date. If you
leave this field empty the system uses a fallback date.

 Note

For change objects, the valid from date is used from the change object payload. For production
operation lists, the valid from date is used from the production operation payload.

3. Define Change Object Status: Here, you define a combination of Domain Model status, maturity code, and
SAP ECN status. If there is a change, the change object status will be modified as set here. Select the
conditions under which the update happens. The following update modes are available:
○ Update always: This value will be updated during create and update actions.
○ Update only when initial: The system sets the planned status only when no status has been set yet for
the document in the SAP system.
○ Ignore during update: You can use this mode to block the configured status value from being used
during the update.
4. Define Inbound Field Mapping and Define Outbound Field Mapping:
Use field mapping to decide how fields from the source structure are transferred to fields in the target
structure. You can use F4 help to find the respective values. The help provides all fields including fields from
the structure and included structures. To define field mapping, you do the following:
○ Choose Create, Update, or Modify in the column MapMode, to define what is valid for this line. (Modify
includes Create and Update).
○ Define an SAP Target structure and SAP Target Attribute to define which field in the SAP system shall
be set
○ Define a source structure and source field to define which data shall be mapped to the target system.
○ Define a conversion in case you want to transform the inbound data before setting it to the target field.
For more information, see BAdI: Define Custom Conversions [page 27].
○ Define a default value if you want to set the standard value in case no data is received in the source
field or if no source field is mapped. Note that you must define a value in internal format.
Field and value mapping supports customer field extensibility by extension fields.
You can select the following structures:
○ SAP Target Structure
○ SAP Target Attribute: Choose F4 to see the available values. If the Overwrite checkbox is selected, the
system uses the stored value instead of an incoming empty value from the payload. This checkbox is
for information purposes only and the setting can't be changed.
○ Domain Model Source Structure: Here you can also use <EXTENSION_FIELDS>
○ Domain Model Source Attribute
○ Conversion: You can use preconfigured as well as customer-specific or target-data-specific
conversions. For more information, see BAdI: Define Custom Conversions [page 27].
You can use <EXTENSION_FIELDS> to map extension fields that are sent from the external PLM system to
a standard field or classification in the SAP system. The name of the extension field must be passed to the
source attribute field.
The assignment is done using standard technical conversion rules. You can define a domain value mapping
in order to do data conversions via tables. You can also define a conversion function. The system offers a

Configuration Guide for PLM System Integration for SAP S/4HANA

14 PUBLIC PLMSI Configuration
 set of standard conversion functions. You can extend these functions using a BAdI. For more information,
see BAdI: Define Custom Conversions [page 27]. Use the Timestamp conversion function to map date
information from a text field into a timestamp in the SAP system, if a data type other than DATS is used.
This enables the conversion between the long timestamp used in the Meta Domain Model and the SAP
format.
5. Define Inbound Class Assignment: Here, you can assign classes and class types that will be added to a
change object when creating and updating, when the change object is sent from the external PLM system
to the SAP system. You can choose a conversion routine, if needed, set default values, or set a value
mapping for the value transfer. You can also use these class assignments as a mapping target. You can
map to an SAP characteristic (target) and define which Domain Model source field from the Domain Model
input structure will be used, for example, to map a status to a characteristic.
○ Define Inbound Characteristics Mapping: Here, you define the value mapping for the characteristics of
the class. You map values of the Domain Model characteristics to the SAP target fields and extension
fields of the change object.
6. Define Outbound Class Assignment: Here, you can assign classes and class types that will be added to a
change object when creating and updating, when the change object is sent from the SAP system to the
external PLM system. You can choose a conversion routine, if needed, set default values, or set a value
mapping for the value transfer. You can also use these class assignments as a mapping source. You can
map a characteristic and define which DM target field in the DM target structure will be used, for example,
to map a characteristic to a status.
○ Define Outbound Characteristics Mapping: Here, you define the value mapping for the characteristics
of the class. You map values of the characteristics to the Domain Model target fields and extension
fields of the change object.
7. Define Relation Type: Here, you define which reference type will be used in the SAP change record for the
Domain Model relation type of the change order.
Fields Domain Model Relation Type, Object Type and Relevance are mandatory. Only the following object
types are supported: BOM, DOC and MAT.
8. Define ECN Status for CO Update in Ext Syst: Here, you set ECN status values to be used as a filter to
determine relevant COs that are sent to the external PLM system.
9. Define CR Status for CO Update in Ext Syst: Here, you set CR status values to be used as a filter to
determine relevant COs that are sent to the external PLM system.

3.5 Define Document Version

In this Customizing activity, you make the required settings for the document version integration.

You define the mapping of Domain Model document version types to the SAP document types. In addition, you
can define the required details like semantic file types, status and maturity codes, and so on. We recommend
that you follow the configuration steps below in the given order.

Prerequisites

● You have made all relevant settings in Customizing for Define Domain Model Code Lists [page 5]. You can
add additional values as required before you start mapping, or during the mapping process.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 15
● Scenarios and versions have been configured in the system, in Customizing for Define Scenario and
Version [page 6].
● You have maintained a change master (CM) profile in Customizing for Maintain Profile under Cross-
Application Components Engineering Change Management .
● SAP Document Management and the SAP Content Server are installed and running. For information about
how to access the SAP Content Server via HTTPS (we recommend using HTTPS, not HTTP), see SAP Note
712330 . For the subsequent introduction of the Security Level for Documents (URL Signature), see
792366 .
For the general setup of the SAP Content Server, go to the SAP Help Portal and browse for SAP Content
Server. Make sure to use the latest version of the documentation.

Activities

1. In the dialog box, select a Scenario ID and Scenario Version to specify the scenario ID and version for which
you would like to define structure version data. Choose Continue.
2. Map MIME Types: Map the Domain Model MIME types to the file extensions for PLM. You can enter a
workstation application and an SAP storage category. Use the Outbound-Relevant checkbox to define the
mapping in case of outbound requests.
3. Define Mapping of Document Type: Here, you map a Domain Model document type to the SAP document
type.
○ CAD Indicator: Sets the CAD indicator in the document info records for documents of this type to
indicate that a document is managed by CAD integration.
○ Version Schema for Document indicates how version numbers are assigned for the document. Select
External numbering to use the version number from the payload, or Internal numbering for the version
number to be generated internally.
To be able to use internal numbering, in Define Document Types (transaction DC10) configuration must
be set to use internal numbering and internal versioning. This is indicated by setting Number
Assignment to Only internal number assignment and by selecting Version Assigned Automatically for
the document type.
○ Document Version Revision Level indicates that a revision level is automatically assigned for a
document revision. You can only set this if Version Schema for Document is set to Internal numbering.
○ Document Version Attachment: Attach a document version to a change object. This document acts as
a supporting document for the change object:
○ When activated, the document version gets created as an attachment to change object.
○ When deactivated, the document version gets created but without an attachment to the change
object.
4. Define Document Status: Here, you define a combination of status and maturity code. If there is a change,
the document status is modified as set here. Select under which conditions the update happens. The
following update modes are available:
○ Update always: This value will be updated during create and update actions.
○ Update only when initial: The system sets the planned status only when no status has been set yet for
the document in the SAP system.
○ Ignore during update: You can use this mode to block the configured status value from being used
during the update.
Use the Outbound-Relevant checkbox to define the relevant SAP status to DM status & DM maturity
mapping in case of outbound requests.

Configuration Guide for PLM System Integration for SAP S/4HANA

16 PUBLIC PLMSI Configuration
 5. Define Inbound Field Mapping and Define Outbound Field Mapping: Use field mapping to decide how fields
from the source structure are transferred to fields in the target structure. You can use F4 help to find the
respective values. The help provides all fields including fields from the structure and included structures.
To define field mapping, you do the following:
○ Choose Create, Update, or Modify in the column MapMode, to define what is valid for this line. (Modify
includes Create and Update).
○ Define a target structure and target field to define which field in the SAP system shall be set
○ Define a source structure and source field to define which data you want to map to the target system.
○ Define a conversion in case you want to transform the inbound data before setting it to the target field.
For more information, see BAdI: Define Custom Conversions [page 27].
○ Define a default value if you want to set the standard value in case no data is received in the source
field or if no source field is mapped. Note that you have to define a value in internal format.
Field and value mapping supports customer field extensibility by extension fields.
For Inbound Field Mapping, you can select the following structures:
○ SAP Target Structure
○ SAP Target Attribute: Choose F4 to see the available values. If the Overwrite checkbox is selected, the
system uses the stored value instead of an incoming empty value from the payload. This checkbox is
for information purposes only and the setting can't be changed.
○ Domain Model Source Structure:
○ Domain Model Source Attribute
○ Conversion: For more information, see BAdI: Define Custom Conversions [page 27].
Inbound payloads may contain sections for extension fields. The values in these fields can be mapped to
the target API structures of standard fields or classifications in the SAP system. Use structure
name:<EXTENSION_FIELDS> to map these values. The name of the extension field should be passed to
the source attribute field.
For Outbound Field Mapping, you can select the following structures:
○ Domain Model Target Structure: Here you can also use <EXTENSION_FIELDS>
○ Domain Model Target Attribute
○ SAP Source Structure
○ SAP Source Attribute
○ Conversion: For more information, see BAdI: Define Custom Conversions [page 27].
You can add extension fields to outbound payloads: Use structure name:<EXTENSION_FIELDS> as Domain
Model target structure and add the attribute as plain text.
The assignment is done using standard technical conversion rules. You can define a domain value mapping
in order to do data conversions via tables. You can also define a conversion function. The system offers a
set of standard conversion functions. You can extend these functions using a BAdI. For more information,
see BAdI: Define Custom Conversions [page 27].
6. Define Class Assignment: Class Assignments enable the mapping and storage of Domain Model attributes
or values to SAP classifications. Here, you can assign class numbers and class types that will be added to a
document info record when creating and updating. You can select a class that is to be allocated to the SAP
object during its creation or update. In a second step, you define the characteristic that shall be the target
of the mapping
○ Define Characteristics Mapping: Here you can choose a conversion routine, if needed, set default
values, or set a value mapping for the value transfer. You can also use these class assignments as a
mapping target. You can map to a characteristic (target) and define which source field from the input
structure will be used, for example, to map a status to a characteristic.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 17
3.6 Define Factory

In this Customizing activity, you assign a factory to an SAP plant. You can use this assignment during product
configuration as part of plant-specific material configuration.

You can assign a combination of factory ID and type to an SAP plant. The assignment enables you to set a
plant-specific status for this assignment in the activity Define Product Version [page 19]. When you create a
product in a specific plant, the status will be mapped according to this assignment. Moreover, you can select
the maintained plant-specific data in field mapping dialogues, for example in Define Inbound Field Mapping for
a product version.

We recommend that you follow the configuration steps below in the given order.

Prerequisites

● You have made all relevant settings in the Customizing for Define Domain Model Code Lists [page 5],
including a Sourcing Strategy Code. You can add additional values as required before you start mapping, or
during the mapping process.
● Scenarios and versions have been configured in Customizing for Define Scenario and Version [page 6].

Activities

1. In the dialog box, select a Scenario ID and Scenario Version to specify the scenario and version for which
you would like to define a factory. Choose Continue.
2. Define Factory Assignment: Here, you assign the factory to an SAP plant. Choose the Domain Model factory
ID and the Domain Model factory type. Then, choose the plant you want to assign. Select the Outbound-
Relevant checkbox if you want to send the data for the factory assignment to an external PLM system
during outbound processing.

 Note

You can only enter and save one record for each combination of Plant and Outbound-Relevant.

3. Define Work Area and Work Center: Here, you can map incoming work area data to a work center in the SAP
system. You can use the Domain Model work area ID and type to assign the work center.

Subsequently, you can define a plant-specific status and template material, and define inbound field mapping
for plant data in Define Product Version [page 19].

Configuration Guide for PLM System Integration for SAP S/4HANA

18 PUBLIC PLMSI Configuration
3.7 Define Product Version

In this Customizing activity, you maintain all necessary definitions to map the product version data from the
Meta Domain Model to the respective SAP product version.

The SAP product version represents a material from the material master and its revision. We recommend that
you follow the configuration steps below in the given order.

Prerequisites

● You have made all relevant settings in Customizing for Define Domain Model Code Lists [page 5]. You can
add additional values as required before you start mapping, or during the mapping process.
● Scenarios and versions have been configured in the system, in Customizing for Define Scenario and
Version [page 6].
● You have maintained a change master (CM) profile in Customizing for Maintain Profile under Cross-
Application Components Engineering Change Management . Most objects that are received from the
external PLM system include a valid-from date. The SAP system uses this date in combination with the
data from the change master profile to create the change master for the object.

Activities

1. In the dialog box, select a Scenario ID and Scenario Version to specify the scenario ID and version for which
you would like to define product version data. Choose Continue.
2. Define Mapping of Product Type: Here, you map a Domain Model product type to the SAP product type.
Confirm your selections and save. In Workflow for Auto UoM, enter the workflow to be triggered after the
creation of an alternative unit of measure (UoM) (instead of the base UoM of the BOM), as specified by
Create Alternative Product Version UoM under Define Mapping of Structure Type in Customizing activity
Define Structure Version [page 24].
3. Define Product Templates: Here, you define a reference product as a template for a certain product type.
This template will be used during product creation in the SAP system. When a product version is received
for creation in the SAP system, and the data below is missing in the payload, the system will create this
data based on the existing template for the respective product type. The following material views are used:
○ Basic data 1 and 2
○ MRP1
○ MRP2
○ MRP3
○ MRP4
○ Plant Stock Data
However, if this data is already included in the incoming payload, the received data will be used during
creation. If the data is sent later, during update, it will replace the data previously created based on the
template.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 19
  Note

If the template comprises plant data, this data will be copied, too, without creating key mapping for the
factory. Therefore, you cannot receive factory data from subsequent payloads from the external PLM
system for this factory. You can customize factory-specific template data in Define Factory [page 18].

4. Define Product Status: Here, you define which combination of status and maturity code results in which
cross-plant product status. Select under which conditions the status is set. The following update modes
are available:
○ Update always: This value will be updated during create and update actions.
○ Update only when initial: The system sets the configured status only when no status has yet been
assigned to the created product in the SAP system.
○ Ignore during update: You can use this mode to block the configured status value from being used
during the update.
Use the Outbound-Relevant checkbox to define the relevant SAP status to DM status and DM maturity
mapping to be sent to an external PLM system during outbound processing.

 Note

You can only enter and save one record for each combination of Cross-Plant Product Status and
Outbound-Relevant.

5. Define Factory-Specific Status: Here, you define which combination of status and maturity code results in
which plant-specific status in the SAP system. If you have assigned a factory to an SAP plant in the
Customizing activity Define Factory [page 18], you can set a plant-specific status for this assignment here.
The system will use this status when processing a status record that includes a Domain Model status for a
specific factory. The available update modes and other settings correspond to those described above for
Define Product Status.
6. Define Factory Template Material: Here, you can define a product template for a specific factory. You can
define one template per factory. The system uses this template during the creation of factory data, if no
based-on material is provided as part of incoming data, or as described in the step Define Product
Templates above.
7. Define Factory Template Views: Here, you define which views you want to process when creating a plant-
specific product. These views are maintained in Customizing under Logistics-General Material Master
Field Selection Maintain Field Selection for Data Screens .

 Note

The APIs will only create the view if data is provided via field and value mapping. Likewise, if a view
doesn't contain any fields, the view will not be created.

8. Define Inbound Field Mapping and Define Outbound Field Mapping: Use field mapping to decide how fields
from the source structure are transferred to fields in the target structure. You can use F4 help to find the
respective values. The help provides all fields including fields from the structure and included structures.
To define field mapping, you do the following:
○ Choose Create, Update, or Modify in the column MapMode, to define what is valid for this line. (Modify
includes Create and Update).
○ Define an SAP target structure and SAP target attribute to define which field in the SAP system shall
be set.
○ Define a source structure and source field to define which data you want to map to the target system.

Configuration Guide for PLM System Integration for SAP S/4HANA

20 PUBLIC PLMSI Configuration
 ○ Define a conversion in case you want to transform the inbound data before setting it to the target field.
For more information, see BAdI: Define Custom Conversions [page 27].
○ Define a default value if you want to set the standard value in case no data is received in the source
field or if no source field is mapped. Note that you must define a value in internal format.
Field and value mapping supports customer field extensibility by extension fields, for example, to map
plant data from product and factory data.
For Inbound Field Mapping, you can select the following structures:
○ SAP Target Structure
○ SAP Target Attribute: Choose F4 to see the available values. If the Overwrite checkbox is selected, the
system uses the stored value instead of an incoming empty value from the payload. This checkbox is
for information purposes only and the setting can't be changed.
○ Domain Model Source Structure: Here you can also use <EXTENSION_FIELDS>. Example: Use
<PRODUCT-EXTENSION_FIELDS> and <FACTORY-EXTENSION_FIELDS> to map plant data for
product and factory data.
○ Domain Model Source Attribute
○ Conversion: Define a conversion in case you want to transform the inbound data before setting it to the
target field. For more information, see BAdI: Define Custom Conversions [page 27].
Inbound payloads contain sections for extension fields then can be mapped to the target API structures.
You can use<EXTENSION_FIELDS> to map extension fields that are sent from the external PLM system to
a standard field or classification in the SAP system. The name of the extension field should be passed to
the source attribute field.
For Outbound Field Mapping, you can select the following structures:
○ Domain Model Target Structure: Here you can also use <EXTENSION_FIELDS>
○ Domain Model Target Attribute
○ SAP Source Structure
○ SAP Source Attribute
○ Conversion: For more information, see BAdI: Define Custom Conversions [page 27].
Outbound payloads for data federation contain sections for extension fields in which mapped values can be
added. You can use <EXTENSION_FIELDS> to map standard fields or classifications that will be sent to the
external PLM system. The name of the extension field should be passed to the target attribute field.
The assignment is done using standard technical conversion rules. You can define a domain value mapping
in order to do data conversions via tables. You can also define a conversion function. The system offers a
set of standard conversion functions. You can extend these functions via the enhancement spot /PLMF/
ES_FVM_CONVERSION. For more information, see BAdI: Define Custom Conversions [page 27].
9. Define Class Assignment: Here, you can assign classes that will be added to products when creating and
updating. You can choose a conversion routine, if needed, set default values, or set a value mapping for the
value transfer. You can also use these class assignments as a mapping target. You can map to a
characteristic (target) and define which source field from the input structure will be used, for example, to
map a status to a characteristic.
○ Define Characteristics Mapping: Here, you define the value mapping for the characters of the class. The
functionality corresponds to the one for field and value mapping.
10. Define Product Fields for Outbound Scenario: Here, you define which fields in the materials tables are sent
to the external PLM system when they are updated in the SAP system. Only those fields specified in
Attribute Name for the selected Product Table Name are sent to the external PLM system.
○ Value From: If the configuration contains a value in the Value From field, the original value of the
material must correspond to this value to be valid.
○ Any Value From: If Value From Any is selected, the actual original material value is not relevant, only the
fact that the attribute was changed.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 21
 ○ Value To: If the configuration contains a value in the Value To field, the change of the material must set
this value for the defined field to be valid.
○ Any Value To: If Value To Any is selected, the actual target material value is not relevant, only the fact
that the attribute was changed.

Related Information

Define Domain Model Code Lists [page 5]

Define Scenario and Version [page 6]

3.8 Define Production Operation List

In this Customizing activity, you make the required settings for routing integration. You define the mapping of
Domain Model production operation list types to the SAP product types and routing types. In addition, you can
define essential control parameters for routing management. We recommend that you follow the configuration
steps below in the given order.

Prerequisites

● You have made all relevant settings in the Customizing for Define Domain Model Code Lists [page 5].
Domain Model code lists have been defined. You can add additional values as required before you start
mapping, or during the mapping process.
● Scenarios and versions have been configured in Customizing activity Define Scenario and Version [page 6].
● You have maintained a change master (CM) profile in Customizing for Maintain Profile under Cross-
Application Components Engineering Change Management . Most objects that are received from the
external PLM system include a valid-from date. The SAP system uses this date in combination with the
data from the change master profile to create the change master for the object. For more information on
the Valid From date, see Define Scenario and Version [page 6].

Activities

1. In the dialog box, select a Scenario ID and Scenario Version to specify the scenario ID and version for which
you would like to define structure version data. Choose Continue.
2. Define Mapping of Production Operation List Type: Here you map a Domain Model production operation list
type to the SAP product type and routing types. Confirm and save your selections.
○ Set default Valid From date. Used if external system does not provide a valid from date. The system
uses a fallback date if you leave this field empty. For more information on the Valid From date, see
Define Scenario and Version [page 6].

Configuration Guide for PLM System Integration for SAP S/4HANA

22 PUBLIC PLMSI Configuration
  Note

For change objects, the valid from date is used from the change object payload. For production
operation list, the valid from date is used from the production operation payload.

○ Enforce Internal Numbering: When this checkbox is selected, internal numbering range will be
consumed to generate the routing group ID for the provided external business ID.
○ Suboperation Mode: Determines how suboperations received from an external PLM system are
handled in the SAP system. Select DM sub-operation as sub-operation for suboperations to be used 1:1,
or select DM sub-operation as operation for suboperations to be flattened and handled as operations.
○ Initial Operation/Activity Number: Sets the first number of the operation.
○ Operation/Activity Increment: Sets the increment for automatically increasing the number for the
operation.
○ Effectivity Type: Here, you can assign an effectivity type to specify that the validity of changes is
determined by the parameters of the effectivity type, instead of by a valid-from date.
○ Model Unit Template ECN: Template change number used to uniquely identify a change master record.
It defines a template change number that is used when operations in a product operation list or bill of
material (BOM) items are received without dedicated model unit effectivity but the object is under
model unit control.
3. Define Production Operation List Status: Here, you define a combination of status and maturity code. In
case of a change, the routing status will be modified as set here. Select the conditions under which the
update happens. The following update modes are available here and in the subsequent activities:
1. Update always: This value will be updated during create and update actions.
2. Update only when initial: The system sets the planned status only when no status has been set yet for
the structure created in the SAP system.
3. Ignore during update: You can use this mode to block the configured status value from being used
during the update.
4. Define Inbound Field Mapping: Here, you use field mapping to decide how fields from the source structure
are transferred to fields in the target structure. You can use F4 help to find the respective values. The help
provides all fields including fields from the structure and included structures. To define field mapping, you
do the following:
○ Choose Create, Update or Modify in the MapMode column to define what is valid for this line. (Modify
includes Create and Update).
○ Define an SAP target structure and SAP target attribute to define which field in the SAP system you
want to set.
○ SAP Target Attribute: Choose F4 to see the available values. If the Overwrite checkbox is selected,
the system uses the stored value instead of an incoming empty value from the payload. This
checkbox is for information purposes only and the setting can't be changed.
○ Define source structure and source field to define which data you want to map to the target system.
○ Define a conversion in case you want to transform the inbound data before setting it to the target field.
For more information, see BAdI: Define Custom Conversions [page 27].
○ Define a default value if you want to set the standard value in case no data is received in the source
field or if no source field is mapped. Note that you must define a value in an internal format.
5. Define DM Parameters Mapping: Here, you define the mapping of DM unit effectivity to effectivity
parameters in the SAP system. You define effectivity parameters in Customizing for Engineering Change
Management under Parameter Effectivity Define Parameters .

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 23
6. Define DM Range Parameter Mapping: Here, you define the mapping of DM unit effectivity to an open
interval effectivity parameter in the SAP system. This setting is used for mapping the value of the unitTo
and unitFrom fields from the payload for a production operation list.

3.9 Define Structure Version

In this Customizing activity, you maintain all necessary settings for structure version integration.

You define the mapping of Domain Model structure types to the product types and BOM types. In addition, you
can define essential control parameters for BOM management. You can create plant-specific structure
versions. We recommend that you follow the configuration steps below in the given order.

Prerequisites

● You have made all relevant settings in Customizing for Define Domain Model Code Lists [page 5]. You can
add additional values as required before you start mapping, or during the mapping process, for example a
Default Plant.
● Scenarios and versions have been configured in the system, in the Customizing activity Define Scenario
and Version [page 6].
● You have maintained a change master (CM) profile in Customizing for Maintain Profile under Cross-
Application Components Engineering Change Management .

Activities

1. In the dialog box, select a Scenario ID and Scenario Version to specify the scenario ID and version for which
you would like to define structure version data. Choose Continue.
2. Define Mapping of Structure Type: Here, you map a Domain Model structure type to the SAP product type
and BOM types.
In Default Plant, you can specify the plant to be set by default for a BOM if the Domain Model structure type
is not plant-specific.
Select Create Alternative Product Version UoM to specify that an alternative unit of measure (UoM)
(instead of the base UoM of the BOM) is created in the product of the corresponding BOM item.
If PV Implicit Plant Creation is enabled, then materials are automatically assigned to the plant for a plant-
specific BOM, and the product version is created with one or more plant assignments. All plant-specific
data is transferred from the template product.
In Effectivity Type, you can assign an effectivity type to specify that the validity of changes is determined by
the parameters of the effectivity type, instead of by a valid-from date.
Confirm your selection and save.

Configuration Guide for PLM System Integration for SAP S/4HANA

24 PUBLIC PLMSI Configuration
 3. Define Structure Status: Here, you define a combination of status and maturity code. In case of a change,
the BOM status will be modified as set here. Select the conditions under which the update happens. Under
UpdateMode, select one of the following update modes here and in the subsequent activities:
○ Update always: This value will be updated during create and update actions.
○ Update only when initial: The system sets the planned status only when no status has been set yet for
the document in the SAP system.
○ Ignore during update: You can use this mode to block the configured status value from being used
during the update.
4. Define Field Mapping:
Use field mapping to decide how fields from the source structure are transferred to fields in the target
structure. To do so, you do the following:
○ Choose Create, Update or Modify in the column MapMode, to define what is valid for this line. (Modify
includes Create and Update).
○ Define an SAP target structure and SAP target attribute to define which field in the SAP system shall
be set.
○ Define a source structure and source field to define which data shall be mapped to the target system.
○ Define a conversion in case you want to transform the inbound data before setting it to the target field.
For more information, see BAdI: Define Custom Conversions [page 27].
○ Define a default value if you want to set the standard value in case no data is received in the source
field or if no source field is mapped. Note that you must define a value in internal format.
Field and value mapping supports customer field extensibility by extension fields.
You can select the following structures:
○ SAP Target Structure
○ SAP Target Attribute: Choose F4 to see the available values. If the Overwrite checkbox is selected, the
system uses the stored value instead of an incoming empty value from the payload. This checkbox is
for information purposes only and the setting can't be changed.
○ Domain Model Source Structure: Here you can also use <EXTENSION_FIELDS>
○ Domain Model Source Attribute
○ Conversion: For more information, see BAdI: Define Custom Conversions [page 27].
○ You can use <EXTENSION_FIELDS> to map extension fields (as mentioned above) that are sent from
the external PLM system to a standard field or classification in the SAP system. The name of the
extension field must be passed to the source attribute field.
The assignment is done using standard technical conversion rules. You can define a domain value
mapping in order to do data conversions via tables. You can also define a conversion function. The
system offers a set of standard conversion functions between elementary data types. In addition, a
JSON-conform timestamp is produced or consumed if a to/from date or time value is assigned. You
can extend these functions via the enhancement spot /PLMF/ES_FVM_CONVERSION. For more
information, see BAdI: Define Custom Conversions [page 27].
5. Define DM Parameters Mapping: Here, you define the mapping of DM unit effectivity to effectivity
parameters in the SAP system. You define effectivity parameters in Customizing for Engineering Change
Management under Parameter Effectivity Define Parameters .
6. Define DM Range Parameter Mapping: Here, you define the mapping of DM unit effectivity to an open
interval effectivity parameter in the SAP system. This setting is used for mapping the value of the unitTo
and unitFrom fields from the payload for a structure version.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 25
3.10 Define Variant Configuration
In this Customizing activity, you make the required settings to the define the mapping of Domain Model variant
configuration types to the SAP variant definition types and variant option types. We recommend that you follow
the configuration steps below in the given order.

Prerequisites

● You have made all relevant settings in Customizing for Define Domain Model Code Lists [page 5]. Domain
Model code lists have been defined. You can add additional values as required before you start mapping, or
during the mapping process.
● Scenarios and versions have been configured in Customizing for Define Scenario and Version [page 6].
● You have maintained a change master (CM) profile in Customizing for Maintain Profile under Cross-
Application Components Engineering Change Management . Most objects that are received from the
external PLM system include a valid-from date. The SAP system uses this date in combination with the
data from the change master profile to create the change master for the object. Confirm and save your
selections.

Activities

1. In the dialog box, select a Scenario ID and Scenario Version to specify the scenario ID and version for which
you would like to define structure version data. Choose Continue.
2. Define Variant Definition Type: Here, you define a variant definition type by class type and change
management (CM) profile.
3. Define Mapping of Variant Definition Status: Here, you define which Domain Model variant definition status
maps to which class status for a class type. In case of a change, the class status will be modified as set
here. Select the conditions under which the update happens. The following update modes are available:
1. Update always: This value will be updated during create and update actions.
2. Update only when initial: The system sets the planned status only when no status has been set yet for
the structure created in the SAP system.
3. Ignore during update: You can use this mode to block the configured status value from being used
during the update.
4. Define Field Value Mapping: Here, you can define value mappings which can be used to define inbound and
outbound field mappings. These are used to map values coming from the external PLM system to values in
the SAP system. You can create or maintain a value mapping ID and assign specific values to this value
mapping ID. You can use preconfigured as well as customer-specific or target-data-specific conversions.
For more information, see BAdI: Define Custom Conversions [page 27].
5. Define Variant Option Type: Here, you map a Domain Model variant data type to the SAP data type. You
specify the attributes of the SAP data type.
○ In the SAP Boolean True and SAP Boolean False fields, you specify the true and false values that are set
in the SAP system for variant options of type Boolean that are loaded from the external PLM system.
You can maintain language-dependent descriptions for the Boolean values in step Define Variant
Option Boolean Value Description.

Configuration Guide for PLM System Integration for SAP S/4HANA

26 PUBLIC PLMSI Configuration
 ○ ChangeMaster Profile: Set the ChangeMaster Profile as selected in Define Mapping of Change Object
Type under Customizing for Define Change Object This ensures that the business objects created use
the same profile and are enabled to attach an ECN.
○ Select the Default ECN Creation checkbox to create an ECN when a variant option payload is sent with
no referenced change objects or all the change object attributes in the requested payload are empty.
○ Not selected (default): No ECN created for VC update/creation when no CO referenced in payload.
○ Selected: ECN created for VC update/creation when necessary.
6. Define Mapping of Variant Option Status: Here, you define which Domain Model variant option status maps
to which characteristic status. In case of a change, the characteristic status will be modified as set here.
Select the conditions under which the update happens. The available update modes correspond to those
described above.
7. Define Variant Option Boolean Value Description: Here, you maintain descriptions for the Boolean values
that are specified in Define Variant Option Type. You can enter descriptions in different languages and set
the language in Language Key.
8. Define Field Value Mapping: Here, you can define value mappings which can be used to define inbound and
outbound field mappings. These are used to map values coming from the external PLM system to values in
the SAP system. You can create or maintain a value mapping ID and assign specific values to this value
mapping ID. You can use preconfigured as well as customer-specific or target-data-specific conversions.
For more information, see BAdI: Define Custom Conversions [page 27].

 Note

SAP can handle a maximum of 512 variant options in a selection condition.

3.11 Business Add-Ins (BAdI)

3.11.1 BAdI: Define Custom Conversions

/PLMF/ES_FVM_CONVERSION

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to extend the preconfigured conversion functions for the integration.

This BAdI offers standard conversions that you can use as a template. You can choose one or several of the
offered conversion possibilities from the value help in the activities Define Inbound Field Mapping and Define
Outbound Field Mapping in Customizing activities, for example Define Product Version. For more information
about the standard settings (filters, single or multiple uses), see the Enhancement Spot Element Definitions tab
in the BAdI Builder (transaction SE18).

The following standard BAdIs are available:

● /PLMF/BI_FVM_CONV_CONDENSE: Field and Value Mapping: Condense Values: Use this BAdI to remove
leading and trailing spaces.
● /PLMF/BI_FVM_CONV_ALPHA: Field and Value Mapping: Alpha Conversion: Use this BAdI to convert
incoming data to the internal SAP format, for example, leading zeros: For inbound messages, missing zeros
are added to the input, for outbound messages, zeros from internal table data are removed.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 27
● /PLMF/BI_FVM_CONV_UPPER: Field and Value Mapping: Convert to Upper Case: Use this BAdI to convert
all letters in the character string of incoming values from the payload to upper case.
● /PLMF/BI_FVM_CONV_HOURS: Field and Value Mapping: Convert Hours: Use this BAdI to convert
incoming data in ISO format ValueDuration to hours.
● /PLMF/BI_FVM_CONV_MINUTES: Field and Value Mapping: Convert Minutes: Use this BAdI to convert
incoming data in ISO format ValueDuration to minutes.
● /PLMF/BI_FVM_CONV_SECONDS: Field and Value Mapping: Convert Seconds: Use this BAdI to convert
incoming data in ISO format ValueDuration to seconds.
● /PLMF/BI_FVM_CONV_TZNTSTMPL: Field and Value Mapping: Convert Timestamps: Use this BAdI to
convert date information from a text field to the correct format, to map the data into a timestamp in the
SAP system, if a data type other than DATS is used.

Activities

1. Create the implementation of the enhancement spot.

2. Adapt the data from the template as required.

Example

You need a custom field mapping, for example, the field Labor for a product version. You want to create an
implementation that derives the value via a custom table access.

3.11.2 BAdI: Document Version Setting of SAP Key

/PLMF/BD_DV_SET_SAP_KEY

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI).

You can use this BAdI to modify the SAP document version key in order to have control over documents to be
created. The SAP document version key consists of document type, document number, document version, and
document part. It is derived from the business ID.

The BAdI implementations can be filtered by the document version type received in the messages from
external systems.

Prerequisites

The SAP document ID has been derived from the business ID as part of the incoming data flow of document
version creation.

Configuration Guide for PLM System Integration for SAP S/4HANA

28 PUBLIC PLMSI Configuration
Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

3.11.3 BAdI: Filter Relevant ECN for CO Outbound Scenario

/PLMF/BD_OUTBOUND_CO_ECN

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI).

You can use this BAdI to specify the engineering change numbers (ECN) that are sent as change objects (CO)
to an external PLM system.

Standard Settings

This BAdI returns ECNs:

● For which the status is in the list of relevant statuses specified in Define Change Object Define ECN
Status for CO Update in Ext Syst
● Which have not been created in the external PLM system (that is, no key mapping in exists in /PLMF/
CO_KM)
● For which object management records refer to objects integrated by PLMSI, for example, document
version or product version

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

1. In the activity, choose Create. Create the implementation of the enhancement spot.
2. Adapt the data from the template as required.
3. Save your entries.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 29
3.11.4 BAdI: Variant Configuration Selection Condition for
Structure Version

/PLMF/BD_VC_SELECTION_COND

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI).

You can use this BAdI to modify the selection condition for structure version.

The BAdI implementation enhances the converted internal format

Prerequisites

The incoming Structure Version data must contain a selection condition in the external format.

Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

3.11.5 BAdI: Variant Configuration Selection Condition for

POL

/PLMF/BD_POL_SELECTION_COND

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI).

You can use this BAdI to modify the selection condition for production operation list.

The BAdI implementation enhances the converted internal format

Prerequisites

The incoming production operation list data must contain a selection condition in the external format.

Configuration Guide for PLM System Integration for SAP S/4HANA

30 PUBLIC PLMSI Configuration
Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

3.11.6 BAdIs for Inbound Post-Processing

You can use these BAdIs to enhance the SAP integration with customer-specific steps after all inbound
processing has been performed.

3.11.6.1 BAdI: Change Object Post-Processing

/PLMF/BD_CO_CUST_POSTPROC_STEP

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to enhance the SAP integration with customer-specific steps after all change object processing has been
performed for inbound maintain request types.

You can use this BAdI to enhance the SAP integration with customer-specific steps after all change object
processing has been performed for inbound maintain request types.

This BAdI can raise messages that influence the overall status. Additional messages are added to the existing
messages and are written to the logs after the SAP process flow. The status is set accordingly based on the
error category.

Note: You cannot use this BAdI to change the payload or process structure.

This BAdI is has no default implementation. For more information about the standard settings (filters, single or
multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 31
3.11.6.2 BAdI: Document Version Post-Processing

/PLMF/BD_DV_CUST_POSTPROC_STEP

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to enhance the SAP integration with customer-specific steps after all document version processing has been
performed for inbound maintain request types.

You can use this BAdI to enhance the SAP integration with customer-specific steps after all change object
processing has been performed for inbound maintain request types.

This BAdI can raise messages that influence the overall status. Additional messages are added to the existing
messages and are written to the logs after the SAP process flow. The status is set accordingly based on the
error category.

Note: You cannot use this BAdI to change the payload or process structure.

This BAdI is has no default implementation. For more information about the standard settings (filters, single or
multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

3.11.6.3 BAdI: File Upload Confirmation Post-Processing

/PLMF/BD_FC_CUST_POSTPROC_STEP

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to enhance the SAP integration with customer-specific steps after all file upload confirmation processing has
been performed for inbound maintain request types.

You can use this BAdI to enhance the SAP integration with customer-specific steps after all change object
processing has been performed for inbound maintain request types.

This BAdI can raise messages that influence the overall status. Additional messages are added to the existing
messages and are written to the logs after the SAP process flow. The status is set accordingly based on the
error category.

Note: You cannot use this BAdI to change the payload or process structure.

This BAdI is has no default implementation. For more information about the standard settings (filters, single or
multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Configuration Guide for PLM System Integration for SAP S/4HANA

32 PUBLIC PLMSI Configuration
Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

3.11.6.4 BAdI: Product Version Post-Processing

/PLMF_BD_PV_CUST_POSTPROC_STEP

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to enhance the SAP integration with customer-specific steps after all product version processing has been
performed for inbound maintain request types.

You can use this BAdI to enhance the SAP integration with customer-specific steps after all change object
processing has been performed for inbound maintain request types.

This BAdI can raise messages that influence the overall status. Additional messages are added to the existing
messages and are written to the logs after the SAP process flow. The status is set accordingly based on the
error category.

 Note

You cannot use this BAdI to change the payload or process structure.

This BAdI is has no default implementation. For more information about the standard settings (filters, single or
multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

3.11.6.5 BAdI: Product Version Post-Processing – Read

Extension Fields

/PLMF/BD_PV_READ_EXTN_FLD

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to enhance the SAP integration with customer-specific steps after all product version processing has been
performed for inbound read request types.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 33
This BAdI can read extension fields to add into the outbound data. Additional extension fields are added to the
existing ones.

 Note

You cannot use this BAdI to change the payload or process structure.

This BAdI offers the example BAdI implementation /PLMV/PV_READ_EXTN_FLD: Product Read Request:
Aggregated Stock Prices. For more information about the standard settings (filters, single or multiple uses), see
the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

3.11.6.6 BAdI: Product Version Key Reservation Post-

Processing

/PLMF/BD_PV_KR_CUST_PSTPR_STEP

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to enhance the SAP integration with customer-specific steps after all product version key reservation
processing has been performed for inbound maintain request types.

This BAdI can raise messages that influence the overall status. Additional messages are added to the existing
messages and are written to the logs after the SAP process flow. The status is set accordingly based on the
error category.

Note: You cannot use this BAdI to change the payload or process structure.

This BAdI is has no default implementation. For more information about the standard settings (filters, single or
multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

Configuration Guide for PLM System Integration for SAP S/4HANA

34 PUBLIC PLMSI Configuration
3.11.6.7 BAdI: Production Operation List Post-Processing

/PLMF/BD_POL_CUST_POSTPRC_STEP

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to enhance the SAP integration with customer-specific steps after all production operation list processing has
been performed for inbound maintain request types.

You can use this BAdI to enhance the SAP integration with customer-specific steps after all change object
processing has been performed for inbound maintain request types.

This BAdI can raise messages that influence the overall status. Additional messages are added to the existing
messages and are written to the logs after the SAP process flow. The status is set accordingly based on the
error category.

Note: You cannot use this BAdI to change the payload or process structure.

This BAdI is has no default implementation. For more information about the standard settings (filters, single or
multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

3.11.6.8 BAdI: Structure Version Post-Processing

/PLMF/BD_SV_CUST_POSTPROC_STEP

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to enhance the SAP integration with customer-specific steps after all structure version processing has been
performed for inbound maintain request types.

You can use this BAdI to enhance the SAP integration with customer-specific steps after all change object
processing has been performed for inbound maintain request types.

This BAdI can raise messages that influence the overall status. Additional messages are added to the existing
messages and are written to the logs after the SAP process flow. The status is set accordingly based on the
error category.

Note: You cannot use this BAdI to change the payload or process structure.

This BAdI is has no default implementation. For more information about the standard settings (filters, single or
multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 35
Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

3.11.6.9 BAdI: Variant Definition Post-Processing

/PLMF/BD_VD_CUST_POSTPROC_STEP

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to enhance the SAP integration with customer-specific steps after all variant definition processing has been
performed for inbound maintain request types.

You can use this BAdI to enhance the SAP integration with customer-specific steps after all change object
processing has been performed for inbound maintain request types.

This BAdI can raise messages that influence the overall status. Additional messages are added to the existing
messages and are written to the logs after the SAP process flow. The status is set accordingly based on the
error category.

Note: You cannot use this BAdI to change the payload or process structure.

This BAdI is has no default implementation. For more information about the standard settings (filters, single or
multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

3.11.6.10 BAdI: Variant Option Post-Processing

/PLMF/BD_VO_CUST_POSTPROC_STEP

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to enhance the SAP integration with customer-specific steps after all variant option processing has been
performed for inbound maintain request types.

You can use this BAdI to enhance the SAP integration with customer-specific steps after all change object
processing has been performed for inbound maintain request types.

Configuration Guide for PLM System Integration for SAP S/4HANA

36 PUBLIC PLMSI Configuration
This BAdI can raise messages that influence the overall status. Additional messages are added to the existing
messages and are written to the logs after the SAP process flow. The status is set accordingly based on the
error category.

Note: You cannot use this BAdI to change the payload or process structure.

This BAdI is has no default implementation. For more information about the standard settings (filters, single or
multiple uses), see the Enhancement Spot Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

1. In the activity, choose Create.

2. Enter the custom enhancement implementation you have created.
3. Save your entries.

Configuration Guide for PLM System Integration for SAP S/4HANA

PLMSI Configuration PUBLIC 37
4 Additional Settings for SAP S/4HANA

4.1 Define Variant Configuration Processing Mode

In this Customizing activity, you set the default processing mode for variant configuration.

Prerequisites

● Scenarios and versions have been configured in the system, in Customizing for Define Scenario and
Version [page 6].

Activities

1. In the dialog box, select a Scenario ID and Scenario Version to specify the scenario ID and version for which
you would like to define structure version data. Choose Continue.
2. Select one of the following processing modes:
○ LO-VC – SAP – Standard Variant Configuration Profile: This is the default value for the configuration.
○ Advanced VC – Advanced Variant Configuration in SAP S/4HANA: This uses the same database tables
for configuration and master data, but has some additional features, for example, this mode allows you
to customize sales, planning, production, and engineering with process and data integration.

4.2 BAdI: Change Object Responsible

/PLMS/BD_CR_RESPONSIBLE

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to change the mapping of a change object (CO) stakeholder to an SAP business partner.

Configuration Guide for PLM System Integration for SAP S/4HANA

38 PUBLIC Additional Settings for SAP S/4HANA
Standard Settings

This BAdI offers a default implementation which is called at runtime but can be overridden.

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

You need a custom field mapping, for example, the field Labor for a product version. You want to create an
implementation that derives the value via a custom table access.

1. Create the implementation of the enhancement spot.

2. Activate your implementation.

4.3 BAdI: Filter Relevant CR for CO Outbound Scenario

/PLMS/BD_OUTBOUND_CO_CR

This Business Add-In (BAdI) is used in the component PLM System Integration (PLMSI). You can use this BAdI
to specify the change records (CR) that are sent as change objects (CO) to an external PLM system.

Standard Settings

This BAdI returns CRs:

● For which the status is in the list of relevant statuses specified in Define Change Object Define CR
Status for CO Update in Ext Syst
● Which have not been created in the external PLM system (that is, no key mapping in exists in /PLMS/
CO_CR_KM)
● For which change items refer to objects integrated by PLMSI, for example, document version or product
version

For more information about the standard settings (filters, single or multiple uses), see the Enhancement Spot
Element Definitions tab in the BAdI Builder (transaction SE18).

Activities

1. Create the implementation of the enhancement spot.

Configuration Guide for PLM System Integration for SAP S/4HANA

Additional Settings for SAP S/4HANA PUBLIC 39
2. Adapt the data from the template as required.

Configuration Guide for PLM System Integration for SAP S/4HANA

40 PUBLIC Additional Settings for SAP S/4HANA
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities,
genders, and abilities.

Configuration Guide for PLM System Integration for SAP S/4HANA

Important Disclaimers and Legal Information PUBLIC 41
www.sap.com/contactsap

© 2022 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN