Select language:
Entering content frame!--a11y-->

Function documentation Phantom Assembly 

Use

Phantom assemblies are assemblies that have their own product structure, but whose assembly does not actually physically exist. The components of the phantom assembly are incorporated directly in the superordinate product. The product structure of the superordinate product contains a reference to the phantom assembly.

A phantom assembly can be referenced more than once in the same product structure. Changes are visible and effective immediately at all usage locations.

Integration

·  Phantom assemblies do not trigger any dependent requirements. Only the components of the phantom assembly trigger dependent requirements.

·  During backflush, only the goods movement for the phantom assembly components are posted. The phantom assembly is marked as backflushed but does not trigger any goods movement.

·  In iPPE, you use the assembly to maintain non-configurable phantom assemblies and a single-level PVS to maintain a configurable phantom assembly.

See also: Creating an Assembly for a Material

The assembly factor is specified for the phantom assembly at the usage location (the current component variant or assembly item). This factor determines how many times the assembly is used. The components of the phantom assembly are multiplied with the assembly factor.

Example

The phantom assembly D consists of the following components:

·  2 x Component A

·  1 x Component B

·  The assembly header contains the quantity 2.

·  The assembly factor 3 is contained in the component variant PV in which the phantom assembly is used.

The explosion for the order results in the following components:

·  6 x Component A

·  3 x Component B

·  6 x Phantom Assembly D (is only visible as text in the order and does not trigger any requirements)

·  Assigning a phantom assembly to activities when using a phantom assembly more than once in the product structure

¡  Single occurances of a phantom assembly can be assigned to different activities of the iPPE process structure. You do this by assigning the usage locations to the various activities (structure nodes, component variants, or assembly items).

¡  You can also assign the individual components of the phantom assembly to the activities. This assignment is then valid for all occurences / instances of the phantom assembly if it is used more than once in a product structure.

·  You can create multi-level phantom assemblies.

·  The planning matrix in the SAP APO creates instances for all usages of a phantom assembly in the product structure. In the matrix, there are rows for the material in the header of the phantom assembly as well as rows for the individual components of the phantom assembly available.

·  If a phantom assembly is assiged to a routing activity, the continuous consumption indicator must not be set.

Prerequisites

·  For Requirements Planning for a Single-Level Explosion of iPPE Data in ERP:

You have entered phantom assembly as the special procurement type 50 on the Material Requirements Planning 2 tab page in the material master of the material that is located in the header of the phantom assembly. The special procurement type 50 is included in the standard delivery.

·  Requirements Planning with the Planning Matrix and the iPPE Single Explosion in the SAP APO:

You have entered the phantom assembly for the material in the component variant or assembly item for the Phantom Assembly.

See also: Maintaining Details for the Component Variants of a Structure Node

·  A material / product must always be available for the header of the phantom assembly so that the requirements planning can determine the components of the phantom assembly.

 

 

Leaving content frame