TutorialKart.comCreate Project Types for WBS Elements in SAP PS
In SAP Project System (PS), a project type classifies WBS elements according to an organisation’s reporting or business requirements. This tutorial explains how to create project types for WBS elements with transaction code OPSO.
A project type is a short key and description maintained in Customizing. It should not be confused with the project profile, which contains important control settings for a project definition and its WBS structure.
OPSO Transaction and IMG Path for WBS Project Types
| Access method | Value |
|---|---|
| SAP R/3 Role Menu | Maintain Project Types |
| Transaction Code | OPSO |
| SAP IMG Path | SPRO > Project System > Structures > Operative Structures > Work break down structure > Create Project types for WBS element |
You need permission to maintain SAP Customizing settings. In systems with transport management enabled, saving the entry may also require a Customizing request.
Steps to Configure a Project Type with Transaction OPSO
1. Open the Maintain Project Types activity
Enter OPSO in the SAP command field and execute the transaction. You can also open the activity through the IMG path listed above.
2. Add a project type entry
On the Change View Project Types: Overview screen, review the existing entries to avoid creating a duplicate key. Choose New Entries to maintain a project type required by the organisation.
3. Enter the WBS project type key and description
On the new entries screen, maintain the following values:
- Typ: Enter the two-character key that identifies the project type in SAP. Follow the naming convention defined for your implementation.
- Description: Enter a clear description that explains the category represented by the project type.
4. Save the SAP PS project type
Choose Save to store the project type. If SAP requests a Customizing transport, select an appropriate existing request or create one according to your transport procedure.
How Project Types Relate to WBS Elements
A work breakdown structure represents the hierarchical organisation of work within a project. Project types provide an additional way to classify WBS elements. They can help users distinguish categories in master data and reporting where the project type field is available.
Creating an entry in OPSO does not create a project definition or a WBS element. Project definitions and WBS hierarchies are created separately, commonly through Project Builder, and the available master-data fields depend on the SAP release and configuration.
Project Type and Project Profile in SAP PS
| SAP PS setting | Purpose |
|---|---|
| Project type | Provides a short key for classifying WBS elements according to defined business categories. |
| Project profile | Supplies central default and control parameters used when creating and processing a project. |
| Project definition | Represents the top-level master record under which the WBS hierarchy is organised. |
| WBS element | Represents a hierarchical project task, phase, deliverable, or responsibility area. |
Use each setting for its intended purpose. Do not create multiple project types merely to reproduce controls that belong in project profiles, field selection, status management, or other SAP PS configuration.
Checks After Saving a WBS Project Type
- Reopen OPSO and confirm that the project type key and description are displayed correctly.
- Verify that the key follows the project’s agreed SAP naming convention.
- Confirm that no existing project type already represents the same business category.
- If a transport was created, check that the Customizing entry is recorded in the correct request.
- Test the project type in a non-production client before relying on it in project master data or reports.
Common OPSO Project Type Configuration Issues
- Duplicate key: Each project type requires a unique key. Review existing entries before adding another one.
- Unclear description: Use a description that identifies the business category without requiring users to interpret an internal abbreviation.
- Save or transport error: Confirm that the client permits Customizing changes and that the user has the required authorisation.
- Project type not available as expected: Check the relevant master-data configuration, field status, client, and transported settings.
- Confusion with the project profile: Review whether the requirement is classification or project control before changing configuration.
FAQs About Project Types for WBS Elements in SAP
Which transaction creates project types for WBS elements?
Use transaction code OPSO to maintain project type keys and descriptions for WBS elements in SAP PS.
Does OPSO create a project or WBS hierarchy?
No. OPSO maintains project type configuration. A project definition and its WBS hierarchy must be created separately through the appropriate SAP PS project-processing application, such as Project Builder.
Is a project type the same as a project profile?
No. A project type is used to classify WBS elements, while a project profile provides defaults and control parameters for project processing.
Why does SAP request a transport when saving an OPSO entry?
OPSO is a Customizing activity. In a transport-managed landscape, SAP may record the new or changed project type in a Customizing request so that it can be moved to subsequent systems.
Can an existing project type be changed after it is used?
Changes should be assessed carefully because existing master data and reports may already use the key. Review usage and test the effect in a non-production system before changing or removing an established project type.