Ansicht
Dokumentation

/CPD/VCPWS_VIEW_COND - Define Components for Commercial Project Structure

Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

In this Customizing activity, you define the master project structure which represents the business objects that form the master project. This Customizing setting allows you to decide which business object types are visible in the master project structure and in what order.

To define your master project structure, do the following:

1. Define user-specific keys to indicate the business object types that can be displayed in a hierarchy. Each component must consist of a main business object type (from which the hierarchy originates) and specify the other business object types that can form the hierarchy based on a transactional relationship between business object types. For example, a hierarchy consisting of project definitions, work breakdown structures (WBS), and sales documents, or a hierarchy consisting of sales orders, WBS, and related newtork activities.
2. Create view IDs to set up flexible grouping of master project structure components for different business scenarios. For example, separate view IDs for a hierarchy of objects that are specific to procurement or project monitoring.
3. Assign the components that are relevant for each view ID. For example, to view a hierarchy of project definition, WBS, and sales order items, or a hierarchy of sales order items, WBS, and network activities.

During runtime, the system displays the master project structure in the following way:

• Creates root structure elements for each unique component provided a corresponding business object is also assigned to the master project. Thereafter, the system displays a hierarchy of objects that are logically linked to the main structure element, even if these objects are not assigned to the master project.

• When a view ID consists of business objects and view options that are interrelated to each other, then the system displays separate root structure elements for the selected components in the view ID.

Suppose a view ID contains options to display a hierarchy of sales order items below WBS elements, and another hierarchy of WBS elements below sales order items.

Scenario A - If both sales orders and WBS elements are assigned to the master project, the system displays two hierarchies - one from WBS elements and the other from sales orders.

Scenario B - If only WBS elements are assigned, the system displays only one hierarchy beginning with WBS elements.

Note:

By assigning view IDs to master project types in the Customizing activity Make Settings for Master Projects, you can allow usage of customized master project structure views to view procurement information or document attachments.

Project Workspace (CA-CPD-WS) delivers the following default component IDs for the master project structure:

Component ID	Description
ICPRO	Include cProject Structure
ICRMO	Include CRM Opportunity
ICWBS	Show WBS Structure Below cProject Struc.
IMWBS	Show WBS Structure Below SD Order Line
INWA	Include Networks and Activities
INWAE	Include Network Activity Elements
INWAM	Include Network Activity Material
IPS	Include Project Definition and WBS
ISD	Include SD Header and Items
ISDC	Include SD Contract
ISDI	Include SD Inquiry
ISDQ	Include SD Quote
IWBSB	Show Only WBS Billing Elements
IWBSI	Show Sales Order Items Below WBS

IWBSI

To include additional business objects such as objects from third-party systems, do the following in Customizing for SAP Commercial Project Management > Master Data > Master Project:

1. Define the new object type in Make Settings for Objects.
2. Specify the technical structure of the object type and the logical system in Define Object Links and Logical Systems.
3. Create your own implementation of BAdI: Additional Components for Master Project Structure to include the new object type in the master project structure.
4. Add the constant for the object type used in your implementation in Define Components for Master Project Structure.

IWBSI

The following examples explain some of the typical scenarios for viewing business objects in the master project structure, the needed components in the view, and the hierarchy of objects.

Scenario 1: Only PS Project-Related Objects

Components in the View:

• IPS (Include Project Definition and WBS)

• INWA (Include Networks and Activities)

Resulting Master Project Structure Hierarchy:

Project Definition
	WBS 1
		WBS 1.1
		WBS 1.2
		Network AB
			Activity 10
			Activity 20
	WBS 2

Scenario 2: PS Project-Related Objects and SD Objects

Components in the View:

• IPS (Include Project Definition and WBS)

• INWA (Inlcude Networks and Activities)

• ICRMO (Include CRM Opportunity)

• ISDC (Include SD Contract)

• ISDI (Include SD Inquiry)

• ISDQ (Include SD Quote)

• IWBSI (Include Sales Order Items Below WBS)

Resulting Master Project Structure Hierarchy:

Project Definition
	WBS 1
		WBS 1.1
		WBS 1.2
		Network AB
			Activity 10
			Activity 20
	WBS 2
		Sales Order Item
		WBS 2.1
SD Inquiry
SD Quote
SD Contract
CRM Opportunity

Scenario 3: PS Project Objects (only Billing) and SD Objects

Components in the View:

• IPS (Include Project Definition and WBS)

• IWBSB (Only WBS Billing Elements)

• ICRMO (Include CRM Opportunity)

• ISDC (Include SD Contract)

• ISDI (Include SD Inquiry)

• ISDQ (Include SD Quote)

• IWBSI (Include Sales Order Items Below WBS)

Resulting Master Project Structure Hierarchy:

Note that in such a scenario, the hierarchy also displays WBSs that are not billing elements but are in the hierarchy between two WBS billing elements.

Project Definition
	WBS 2 (Billing Element)
		Sales Order Item
	WBS 3 (Billing Element)
		WBS
		WBS 4 (Billing Element)
			Sales Order Item

SD Inquiry

SD Quote

SD Contract

CRM Opportunity

Scenario 4: SD Objects with PS Project-Related Objects

Components in the View:

• IMWBS (Show WBS Structure Below SD Order Items)

• INWA (Inlcude Networks and Activities)

• ICRMO (Include CRM Opportunity)

• ISDC (Include SD Contract)

• ISDI (Include SD Inquiry)

• ISDQ (Include SD Quote)

Resulting Master Project Structure Hierarchy:

SD Order
	Item 10
		WBS 1
		WBS 1.1
			Network AB
			Activity 10
			Activity 20
	Item 20
		WBS 3
SD Contract
SD Inquiry
SD Quote
CRM Opportunity

Scenario 5: Only SD Objects

Components in View:

• ISD (Include SD Header and Items)

• ISDC (Include SD Contract)

• ISDI (Include SD Inquiry)

• ISDQ (Include SD Quote)

• ICRMO (Include CRM Opportunity)

Resulting Master Project Structure Hierarchy:

SD Order
	Item 10
	Item 20
SD Contract
SD Inquiry
SD Quote
CRM Opportunity

Scenario 6: Only cProject Structure

Components in View:

• ICPRO (Include cProject Structure)

Resulting Master Project Structure Hierarchy:

cProject Header
	Phase 1
		Task 1
		Task 2
	Phase 2

Scenario 7: cProject Structure with PS Project Definition

Components in View:

• ICWBS (Show WBS Structure Below cProject Struc.)

Resulting Master Project Structure Hierarchy:

BAL_S_LOG - Application Log: Log header data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 20864 Date: 20240417 Time: 013840     sap01-206 ( 139 ms )

cProject
	Phase 1
		Task 1
		WBS 1
			WBS 1.1
			WBS 1.2
		Task 2
	Phase 2
		WBS 2
PS Project Definition
	WBS 1
		WBS 1.1
		WBS 1.2
		Network AB
			Activity 10
			Activity 20
	WBS 2