Project Systems Dates and SD reporting

FUNCTIONAL SPECIFICATIONS

1 Description
Solution Area

Project Systems and S & D reporting from SAP BW

Detailed
Description/Purpose

Provides a reporting environment both for Ad Hoc (power user) and canned
report development within BW to support those LCs that manage complex
orders via the PS module

Assumptions

Nortel usage of PS (Technical and dates) is not changed as a result of Release

6. the CATS (Resource Management), Profit Centre Accounting and Financials
build out of PS is NOT in scope for Release 6.
Appropriate changes are made to the SD (ZSD_C03 and ZSD_C14) content to
allow effective multi-cubes to be built.

Functional Area(s)

Sales & Distribution, Market Project Management

Created by

Mark Chapman, P Daze, Karen Sprinkle

Date Created

11/10/2004

Date Updated

11/14/2004

2 Ownership
Business Requestor

Vickie Wintrich, Isabelle Landry , Michelle Armstrong

Business Area Owner

Key Contacts

Vickie Wintrich Wireless NA SME

Isabelle Landry Optical NA SME
Michelle Armstrong EMEA S&PA reporting Prime
Don Hepp S&PA Programme Lead
Ian Franks Projects Process Prime

Priority: (Low/Med/High/Show Stopper)

High

Date Required

Jan, 2005

PAGE 1 OF 11

264973563.DOC

Project Systems Dates and SD reporting

FUNCTIONAL SPECIFICATIONS

3 Overview
As a result of the Scope review and agreed content for SAP Release 6 (January 23 rd 2005) the proposed
full build out of S&PA (Services and Project Accounting) has been deferred to later in 2005. However,
there are parts of the Nortel Business that are (and have been for some time) making use of parts of the
PS Module functionality specifically linking Sales Orders within Project Structures to manage complex
orders where various milestones occur within a contract with a customer and its is required to track
these events. In addition, as part of the Legacy Financials for CONLED (Feed to ECMS) certain
businesses require to associate complex projects to a single Leadership Category irrespective of the
materials contained within the Sales Order items. This is achieved by assigning Orders to Project WBS
Elements and assigning a single Product Line id to a WBS Element.
The full design for the Project Systems configuration for Nortel is still yet to be completed, so at this time
the desire is to permit only very minimal customization delivered content of the PS Module into BW as
significant deviation would be likely to be reworked once the final design for PS was implemented.
The SAP BW delivered content for PS covers;

In the configuration for PS in Nortels current state of SAP R/3 we only have content for the Object
0PS_C02 Project System-Dates, as well as the technical content for the Infosets. No financials (Costs,
Revenues etc )_are (as yet) tracked within the SAP R/3 PS modules.
Therefore at this time, it is only relevant to look at deploying the 0PS_C02 object, and any associated
master data.

PAGE 2 OF 11

264973563.DOC

Project Systems Dates and SD reporting

FUNCTIONAL SPECIFICATIONS

The default schema for the 0PS_C02 is:

Network activity
Network Activity element
Network
Network activity
Milestone Network
Project Definition
PS Object Type
System Status
Work Breakdown Structure E
lem
Project Objects

Time Fiscal

year / period
Fiscal year variant
Posting period
Fiscal year variant
Fiscal year
Fiscal year variant

Project System - Dates ( 0PS_C02 )

Value Type Date

Organizational Units

Controlling area

Float Date Duration Time

event
Origin of appointment
Value Type for Reporting

Events

Reporting Time

Unit

Unit buffer Duration unit

PAGE 3 OF 11

264973563.DOC

Project Systems Dates and SD reporting

FUNCTIONAL SPECIFICATIONS

A small number of enhancements to this basic Structure have been identified:

Optical (NA) identified enhancements:
1. Field Product ID (on the Custom Enhancement tab), "PRPS-ZZPROD_ID". This should be
modeled as a navigable attribute of the Dimension Project Objects
2. Relate WBS ELEMENT for Level 1 to Sales Order Header for merchandise, and SOME Furnish
only orders : PRPS-PSPNR WHERE PRPS-STUFE = 1
3. Relate WBS ELEMENT for Level 2 to Sales Order Header for MOST Furnish only orders and
Complex orders: PRPS-PSPNR WHERE PRPS-STUFE = 2
Wireless NA identified enhancements:
1. Product Description (PRPS-EQUNR) as Navigable attribute of Dimension Project Objects
2. Product Description Text (EQUI-EQKTX) text associated with PRPS-EQUNR. This is
equipment (0EQUIPMENT) Master data.
3. PRPS-ERDAT (WBS Element Created on Date) 0CREATEDON attribute in 0PS_C02 already.
Wireless usage as OE Date
4. PRTE-PENDE (is Basic Finish Date for Project Item Scheduling Data) usage as M3 PLAN. Note
this would be a RESTRICTED Key Figure as BASIC (PLAN) dates are loaded to the BW for all
Project Item Activities.
5. PRPS-PSPRI (WBS Element Priority) 0PRIORITY attribute in 0PS_C02 already
a. PSPRI = A translate to Test
b. PSPRI = B translate to Open
c.

PSPRI = C translate to Complete

d. PSPRI = D translate to Hold

e. PSPRI = E translate to Closed
f.

PSPRI = F translate to Cancelled

6. AFVC-AUFPL (Operation within an order - Routing Number for Operations) not in BW extract
Wireless Usage not clearly identified currently not proposed to include.
7. AFVC-PROJN (Operation within an order - WBS Element: Operation level) ) not in BW extract
Wireless Usage not clearly identified currently not proposed to include.
8. AFVC-APLZL (Operation within an order - Counter for Order: Operation) ) not in BW extract
Wireless Usage not clearly identified currently not proposed to include.
9. AFVC-VORNR (Operation within an order - Operation Number) 0ACTIVITY already in
0PS_C02 cube
10. AFVV-NTEND (quantities/dates/values in the operation Constraint for finish of Activity (Basic)) not in BW extract Wireless Usage not clearly identified currently not proposed to include.
11. AFVV-AUFPL (quantities/dates/values in the operation - Routing number for operation) - not in
BW extract Wireless Usage not clearly identified currently not proposed to include.
12. AFVV-APLZL (quantities/dates/values in the operation - Counter for Order: Operation) - not in
BW extract Wireless Usage not clearly identified currently not proposed to include.

PAGE 4 OF 11

264973563.DOC

Project Systems Dates and SD reporting

FUNCTIONAL SPECIFICATIONS
The Principle usage will require Ad-Hoc and Canned capability where the (modified) 0PS_C02 (as
ZPS_C02) is linked in the form of a multi-cube to both ZSD_C03 and ZSD_C14.

The common linkage is the WBS ELEMENT: 0WBS_ELEMT in ZPS_C02.

This Element is in Logistics Structure 2LIS_11_VAHDR and is already present in ODS ZSD_O11 (Open
Sales Order Items), but is not promoted to the Cubes:

ZSD_C03

ZSD_C14.

The Data-flows for these two cubes will need to be modified to include this object in the Data Model.
Proposal is to add them to:

ZSD_C03: Dimension Document Classification so as to make the object relate correctly to all
Document types (Orders, Deliveries and Invoices) as per the other Objects like NT Control Id.

ZSD_C14: Dimension Sales Document. As Navigable Attribute. Again Model should allow all
related dimensional objects (like Customer PO#, NT_Control_Id, Nortel PO# (BW:Document))
to be combined with Characteristics from the ZPS_C02 Cube.

4 Combinational Requirements
4.1

Project Systems and Sales Document data

All currently combinable objects in the ZSD_C03 cube should be retained, and enhanced with the ability
to SELECT / Group By, from the ZPS_C02 content:
Project Definition (AA-nnnnn)
WBS Element (AA-nnnnn-mmm)
WBS Element Level (Select on = 1, 2,3 or any combination)
WBS Element Priority (Select on any / combination of A to F)
Typical Questions would include:
Select for Given WBS Element (Range)
WHERE WBS ELEMENT LEVEL = 2
Display all WBW ELEMENT LEVEL 3, and their Network Activity (Code, Description) and display their
BASE END Date.
Display all Sales Order #, and Invoice #s by WBS ELEMENT (LEVEL 3) with Qty and Value Invoiced,
and display the Actual Billing Date

PAGE 5 OF 11

264973563.DOC

Project Systems Dates and SD reporting

FUNCTIONAL SPECIFICATIONS

4.2

Project Systems and Open Orders Data

All currently combinable objects in the ZSD_C14 cube should be retained, and enhanced with the ability
to SELECT / Group By, from the ZPS_C02 content:
Project Definition (AA-nnnnn)
WBS Element (AA-nnnnn-mmm)
WBS Element Level (Select on = 1, 2, 3 or any combination)
WBS Element Priority (Select on any / combination of A to F)
Typical questions would include;
Select for Given WBS Element (Range)
WHERE WBS ELEMENT LEVEL = 2
Display all WBW ELEMENT LEVEL 3, and their Network Activity (Code, Description) and display their
BASE END Date.
Display all Sales Order #, Sales order Lines with their Confirmed Qty and Confirmed Date; so as to
compare the SD Confirmed Schedule with the PS BASE (planned) Date schedule.

5 General Ad-Hoc capability

It is required that the user of these reporting domains should be able to build queries that are able to
search / Select on any of (and combination of)

Customer

Sales Area Object (Org, Division, Distribution Channel)

Product Hierarchy (Design Question: approaches may include select/drill via:

o

SEG5 Hierarchy attached to 0Prod.Hier object (Attribute of Sales Order Line captured at
Sales order creation)

SEG5 Hierarchy attached to 0MATERIAL_0Prod.Hier (Attribute of Material Master)

SEG5 Hierarchy attached to Product Line from WBS Element (Optical Model)

SEG5 Hierarchy attached to Product Description (PRPS-EQUNR) as per the Wireless

Model

Customer Market Code (and via the SEG4 TORG Hierarchy)

Project Definition

WBS ELEMENT

WBS LEVEL

WBS ELEMENT PRIORITY

CALENDAR and Fiscal Period Selections;

o

Date objects that should align within the TIME Dimension are;
PAGE 6 OF 11

264973563.DOC

Project Systems Dates and SD reporting

FUNCTIONAL SPECIFICATIONS
Order Entry Date (SD and PS definitions)

Invoice Date

Shipment Date

Network Activity BASE / LATEST / ACTUAL Dates

Report Content

At this time there are no documented, specific reports required.

As part of the validation exercise, and to permit assessment by the Optical and Wireless teams for
accuracy and definition of the PS content , a BW equivalent of the ZVRPROJECTSYSTEMSDATE report
will be created. This should aim to replicate the contents, and layout (excel downloaded version) of the
ABAP report.

6.1

Fields and Selection Criteria

Each metric is available as content on the report. They are display only.
Field

Prompt

Project Definition

List

Company Code

Individual Value

WBS Element

List , Range, Options

Mandatory or Optional
Optional
Mandatory
Optional

6.2
Page 1 of layout

Page 2 of Layout (Cont)

PAGE 7 OF 11

264973563.DOC

Project Systems Dates and SD reporting

FUNCTIONAL SPECIFICATIONS

Page 3 of layout (cont)

PAGE 8 OF 11

264973563.DOC

Project Systems Dates and SD reporting

FUNCTIONAL SPECIFICATIONS

6.3

Report Interactivity

Static Report

Interactive Report

Preferred Display Medium (if known)

X
Other Expectations:

6.4
Day

Reporting Period (Granularity at which user will report)

Week

Month

Quarte
r

Year

Fiscal
Week

Fiscal
Period

Fiscal
Quarte
r

Fiscal
Year

Other

X
Comments

6.5

This report is just for Validation Purposes only.

Drill Down Requirement

Drill-Down Field

Navigation Path

PAGE 9 OF 11

264973563.DOC

Project Systems Dates and SD reporting

FUNCTIONAL SPECIFICATIONS

7 Technical Requirements
7.1

Source of Data

Source System(s)

Structure (Transaction, Report, Tables, Flat File, etc.)

SAP R/3
Data Central (CHM)

7.2

Product (Seg 5) and Market (Seg 4) Hierarchies

Reconciliation Procedures (R/3 or Legacy reports to Reconcile against)

Recon. Procedure

Process
As listed in Section 6 reconcile test BW report vs the
ZVRPROJECTSYSTEMDATE report for Given Company Code / Project
Definition range.

7.3

Historical Data Requirement (How much Historical Data is needed)

Time Horizon of Report

From Jan 2003 onwards

Known Conversion Issues

None at this time

Retention / Aggregation

??

Maintain or Overwrite
History

7.4

Usage Frequency (Query Execution Frequency)

Hourly

Daily

Weekly

Monthly

Quarterly

Yearly

Comments:
Approx. Number of Users:

20 at the Release 6 stage will increase after Release 7

PAGE 10 OF 11

264973563.DOC

Project Systems Dates and SD reporting

FUNCTIONAL SPECIFICATIONS

7.5

Refresh Rate of Data (How often does data need to be refreshed in BW)

On Demand

Daily

Weekly

Monthly

Quarterly

Yearly

X
Comments:

7.6

Dependencies (R/3 batch jobs, month end close, other BW data loads, etc)

Dependent Business Process

Criteria

None known at this time.

Security
Data Access
Restrictions

Restriction Criteria

Currently to fit
within OM Roles as
defined in BW

Intended Audience

Excluded Audience

OM Primes

8 Questions and Notes

9 Sign-Off
Reviewed By
Approved By
Date Approved

10 Change Log
Date

Change

Reason

Who

11/15/2004

New Document

To get x-LC, region alignment

M Chapman

PAGE 11 OF 11

264973563.DOC