Kontakt

Ansicht
Dokumentation

Planing Matrix (Enhanced) ( RELNAPO_401_PPS_RPM )

Planing Matrix (Enhanced) ( RELNAPO_401_PPS_RPM )

ABAP Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Planing Matrix (Enhanced)

Use

In SAP APO 4.0, the planning matrix has been enhanced by the following new functions:

  • Planning Phantom Assemblies
From this release it is now also possible to plan phantom assemblies using the planning matrix. You can plan configurable phantom assemblies and non-configurable phantom assemblies.
You represent a configurable phantom assembly using a single-level product variant structure. You create the phantom assembly itself as an access node. And you create the components of the phantom assembly as component variants of structure nodes which are linked to the access node. You create non-configurable phantom assemblies using assembly groups. And you create the components of the phantom assembly as assembly items.
You use a reference to link the phantom assembly to the component variant in the product variant structure of the finished product.
If you want to execute an ATP check for the components of the phantom assembly or if you want to firm the components in the planned order of the finished product then you have to create a material master record for the phantom assembly and enter this material number in the access node of the phantom assembly or in the assembly header of the phantom assembly.
For more information on phantom assemblies in integrated Product and Process Engineering, refer to the corresponding iPPE Release Information.
The planning matrix creates separate rows in the matrix for the phantom assembly and for the components. If you make multiple use of a phantom assembly in a product variant structure, separate rows are created in the matrix for each use.
Limitations
  • There is no comparitive key in the APO product master for the special procurement key 50 (phantom assembly) in the material master. Therefore, SAP APO cannot take this special procurement key into account. The planning of phantom assemblies in SAP APO is only possible via iPPE product structures.

  • As for the BOMs in R/3, it is not possible within a product structure to define different plant-dependent splits for a phantom assembly. This means that you cannot plan the phantom assembly in one plant as a phantom assembly and in another plant as a 'normal' assembly.

  • The use of colored materials is not possible for phantom assemblies. However, the components of the phantom assembly can be colored.

  • The use of product interchangeability is only possible for the components of a phantom assembly. You execute the product replacement for the components in the planned order for the finished product using the ATP check. See also: Release Information on Product Interchangeability

  • The configuration of a phantom assembly is determined by the configuration of the order for the finished product. Therefore, the characteristics you use for maintaining the dependencies of the phantom assembly must be included in the class of the finished product.

  • If you create an assembly group for the phantom assembly and assign different activities to the assembly items and then you assign these activities to different line elements during line balancing, the planning matrix will also determine the line element where the components are to be assembled. When backflushing, on the other hand, all the components are backflushed at the first reporting point irrespective of planning.

  • Introduction of a Characteristics Filter in the Transaction Matrix Evaluations
A characteristics filter is now available in the matrix evalutaions (transaction RPMEVAL) for filtering out planned orders with selection conditions based on characteristics and characteristic values. Using the characteristics filter, you can define a certain selection condition.
Example
You can define that out of all the orders that were selected according to your selection criteria, you only want to see the orders for vehicles with sunroofs. You achieve this by creating a characteristics filter with the dependency Sunroof = 'YES' in the initial screen of the matrix evaluation.
  • Technical Improvements in the Planning Run of the Planning Matrix
The planning run of the planning matrix has been optimized so that the existing component variant matrix and, if necessary, the activity matrix remain valid until planning has completed the creation of the new matrices and has activated them. The old matrices are not deleted until the new ones have been activated by the system. This provides you with the following advantages:
  • For the first time, it is possible for the system to read data in the matrix (component variant matrix and the activity matrix) parallel to the planning run. This is particularly useful for backflushing. You can now execute a backflush in APO at the same time as the planning run.

  • Another advantage is that up-to-date matrices as still available even if the planning run is terminated. As the 'old' matrices are not deleted until the planning run has been executed successfully, these 'old' matrices continue to be available if no 'new' matrices could be created in the planning run.

  • Maintaining Additional Data
Using the transaction 'maintain additional data' (MDRPM), you can now make the settings for the RPM products dependent on the planning version. This means you can define different settings for inactive and active planning versions.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information






General Data in Customer Master   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 6889 Date: 20240425 Time: 025632     sap01-206 ( 117 ms )