Creating a Project for a Complex Product Using the Manage Major Assembly Projects App

Objective

After completing this lesson, you will be able to create a complex assembly project using the Manage Major Assembly Projects app to integrate product assembly and project management.

PEO Integration with SAP S/4HANA Project Management

The complex assembly process starts with the creation of a project for a new model and unit of an end item. The project coordinates the subsequent process steps such as product engineering, production engineering, production planning, and production execution. The process aims at fulfilling the following objectives:

  • Tight integration of engineering and production execution
  • Support individually configured end items by means of parameter effectivity
  • Top-down project planning
  • Support the collaboration of people with different roles
  • Check and validate user entry to prevent errors early and make the process more robust
  • Automate process steps that can be automated. In the figure, Complex Assembly Process, the clock indicates a periodic job
  • Record all process steps for later reference, root-cause analysis, and process improvement activities

The following figure shows an overview of the complex assembly process. This unit explains the details of the process.

chart showing Complex Assembly Process in a flow chart
Complex Assembly User Roles as described in the bwlow text

Design Engineer: The process starts with design engineering where product engineers develop engineering BOMs (EBOMs) for the end item and major assemblies. They tailor BOM items based on customer preferences and restrict their validity accordingly.

Production Engineer: Once the EBOMs are created and released, production engineering takes over. Production engineers design the assembly process, organizing major assembly components into installation kits and creating routings for each. By releasing MBOMs and routings, they signal production planners that the design phase is complete.

Production Planner: In production planning, the production planner initiates a project for the end item, scheduling start and end dates for each installation kit by organizing network activities. MRP uses these schedules to set requirement dates, automatically generating planned orders, which convert to production orders when ready.

Production Supervisor: Although major assemblies are not directly seen in production planning, they are reflected in project networks, allowing supervisors to manage and oversee the assembly processes as depicted by project system networks.

Production Operator: Production operators follow scheduling and sequence control dictated by these network activities to ensure smooth production flow.

Installation kits are represented both in the project system and PEO, captured as activities within a major assembly’s network.

Chart showing the divide between project system and SAP PEO as described

The production orders are managed and executed in production operations. Production supervisors release the production orders as soon as all prerequisites for starting production have been fulfilled. This communicates to the production operators that they can start work on the production order. The production operators then assemble installation kit components into the major assembly as instructed by the installation order (production order for the installation kit). On completion of the installation order, an artificial inventory for the installation kit is posted. This inventory is cleared automatically by a periodic job.

Project Creation

END Item: When deciding to build an end item like an aircraft or ship, the production planner creates a new project. Each end item requires at least a separate WBS element. Projects handle costs and define activity sequences for end items.

Major Assembly: Initially, projects contain few WBS elements/networks for different major assemblies. Resources and production sequences for major assemblies are planned. Major assemblies are engineered/configured to meet specific customer requirements.

Installation Kit: After installation kits are created, network activities are added for each kit.Non-valuated project stock ensures separation of installation kits across projects.

Assembly: Projects copy network activities/relationships from previous assemblies, adapting for BOM changes.Components are added by BOM transfer upon BOM explosion of major assemblies.

Note

This is the classic project management way of creating a project, whereby reference points have to be maintained manually in BOM items and in network activities.
Screenshot of project creation settings
Screenshot showing the project setup screen

Every project and WBS element needs a unique name. Naming conventions should be agreed to make sure that WBS elements can be copied from the template project and new names can be determined with little effort. In the test system, a project copy replaces the first 10 characters of every WBS element in the project with the first 10 characters in the project. Ideally, every WBS element in the project should differ in the characters 11 to 24. Then, the WBS elements can be copied into the new project without adjusting names. If the name of a WBS element is not unique, you will be prompted to make it unique when copying the project.

The project must use non-valuated project stock to make sure that major assemblies and installation kits of different projects are separated.

Screenshot showing project builder with Non-valued stock.

Major assemblies are specially engineered or configured to meet customer requirements. Usually, every major assembly is different. If parameter effectivity is used, then BOM explosion selects the components needed for a specific unit of the product. The project’s end item unit is defined by means of parameter effectivity. Select a network and choose Extras→Parameter effectivity to update the parameter effectivity values.

screenshot showing Parameter Effectivity Values

Subsequent processes (BOM explosion in particular) have to differentiate the demand from different end items. BOM explosion needs every end item’s individual parameter effectivity (such as model and unit). If a new project is created for every end item, then every project has a separate set of networks. All networks of the same project must have the same parameter effectivity.

If several end items are made using the same project, then separate networks and WBS elements are required for every end item. Different networks of the same project have different model-units in this case, and a validation is not possible.

Summary

This lesson covers creating complex assembly projects using SAP S/4HANA's Manage Major Assembly Projects app for project integration.

  • Coordinate design, production, and planning stages for seamless assembly project execution.
  • Utilize project networks and WBS elements to organize major assemblies and installation kits.
  • Apply parameter effectivity for customized BOMs and optimized product assembly.
  • Manage assembly projects with unique naming conventions and non-valuated stock.
  • Automate and record steps for efficient project oversight and improvement analysis.

Create a New Project Using the Manage Major Assembly Projects App

Business Example

Janice is a production planner with the low-volume A&D Company focusing on the final assembly of complex products. She has been told to set up a new project to start the planning process for a specific model/unit of one of A&D’s products. For the initial creation of the project, she uses the Manage Major Assembly Projects app.