Entering content frame

Function documentation Extraction Locate the document in its SAP Library structure

Use

In the first step of the conversion process (extraction), the data set that describes the composition of the product in a specific context is determined from a complex iPPE model.

Example

For example, work scheduling for a multi-variant product is to be done in a specific plant with specific values assigned during configuration. Scheduling only requires product data for these specific conditions (for example plant 0001 in Brazil, Model Luxury and Color Blue).

Prerequisites

The following overview contains the activities that you need to perform before extraction.

Activity

Result

Maintain iPPE product structure

You have maintained a consistent iPPE product structure in the iPPE workbench.

Decomposition of iPPE structure with reference to a focus

(alternative to filter)

You have maintained a focus record in the iPPE workbench.

Determination of iPPE data with reference to a filter

(alternative to focus)

You have maintained a filter master record in the iPPE workbench.

Define Settings for extraction and conversion

For example, you have defined which dialog steps are involved in the conversion, and how the BOM objects are created and deleted.

Features

Access for Evaluating a Product Structure

The following overview lists the possibilities for restricting the data in the exploded product structure.

Access Option

Use

This graphic is explained in the accompanying text  Focus

A focus defines conditions under which a product structure is valid and has direct influence on the status of a product structure.
Further criteria (such as selection of focus objects) restrict a product structure to a specific section of data.

This graphic is explained in the accompanying text  Filter

A filter collects values that serve as selection criteria for objects in the product structure. As a tool for data selection, a filter has no influence on the status of the product structure.

Structure Evaluation

Different product structures are maintained for one product, to provide different application areas or user groups with specific product data. For example, you maintain different views on a product structure. The level of detail for the structure evaluation is variable. Multi-level explosion is possible if an access is maintained for each explosion level (material and usage must be specified, the plant is optional).

In the General Settings, you can define whether the following evaluations take place for a multilevel product structure:

Scope of Data for Evaluation

The following overview contains the objects in the iPPE product structure that are always evaluated for the product designer.

iPPE Object

Use

Nodes

iPPE nodes represent general elements of the iPPE model.
For the conversion process for the product designer, the nodes from the application model
product structure and application object type CMP (component) are evaluated.

Variant

A variant is the concrete instance of an iPPE node. For the conversion process for the product designer, the following variants are evaluated, which are maintained at nodes of the product structure:

  • PVS access variant/Access variant

The materials that are to be configured are assigned to the variants of the access node.

  • PVS structure variant/Component variant

You assign the concrete materials to the variants of the structure node, which are used in the product instead of the structure node. The variant selected at a structure node usually depends on the evaluation of the object dependencies (characteristic values of the product description, for example).

Relationship

Relationships link the elements in the iPPE model. The system automatically selects the suitable relationship type when you link two iPPE elements, according to settings in Customizing. The relationship type does not appear on the user interface and is not visible when you create the structure.
Extraction for the product designer reads the relationships in the product model that have been modeled between nodes and variants.

Actions

See Process Flow for the Conversion Process

Leaving content frame