fs_1

FUNCTIONAL DESIGN SAP BW REPORT

Analysis of income by country(F1428)

FUNCTIONAL REPORT SPECIFICATIONS

1 DESCRIPTION................................................................................................................................. 2

2 OWNERSHIP................................................................................................................................... 3

3 REPORT CONTENT......................................................................................................................... 4

3.1 REPORT INTERACTIVITY................................................................................................................43.2 FIELDS AND KEY PERFORMANCE INDICATORS.................................................................................43.3 SELECTION CRITERIA.................................................................................................................... 63.4 REPORTING PERIOD (GRANULARITY AT WHICH USER WILL REPORT)...................................................63.5 DRILL DOWN REQUIREMENT..........................................................................................................6

4 TECHNICAL REQUIREMENTS........................................................................................................6

4.1 SOURCE OF DATA........................................................................................................................ 64.2 RECONCILIATION PROCEDURES (R/3 OR LEGACY REPORTS TO RECONCILE AGAINST)..........................64.3 =HISTORICAL DATA REQUIREMENT (HOW MUCH HISTORICAL DATA IS NEEDED)..................................64.4 USAGE FREQUENCY (QUERY EXECUTION FREQUENCY)...................................................................64.5 REFRESH RATE OF DATA (HOW OFTEN DOES DATA NEED TO BE REFRESHED IN BW)..........................64.6 DEPENDENCIES (R/3 BATCH JOBS, MONTH END CLOSE, OTHER BW DATA LOADS, ETC).......................6

5 EXAMPLE REPORT FORMAT/LAYOUT.........................................................................................6

6 SECURITY....................................................................................................................................... 6

7 TESTING REQUIREMENTS.............................................................................................................6

7.1 TECHNICAL TEST CONDITIONS.......................................................................................................67.2 TESTING CONSIDERATIONS/DEPENDENCIES....................................................................................6

8 PEER REVIEW................................................................................................................................. 6

9 QUESTIONS AND NOTES...............................................................................................................6

10 SIGN-OFF..................................................................................................................................... 6

11 Change Log................................................................................................................................. 6

PAGE 1 OF 16document.doc




1 Description

Report Title: LR96 – Analysis of income by country (F1428)

Detailed Description/Purpose:

Analysis of Income by Country (F1428) - Shows Siebel opportunity value, invoices raised value and revenue recognised values where the head-office address of the customer is in the country being queried on.

The report will show:‘Country’‘Siebel Sector’, ‘Siebel Segment’, ‘Siebel Sub-Segment’‘Business Stream’‘Opportunity ID’‘Opportunity Name’‘Channel Manager’‘Profit Centre’ structure‘WBS’ (aka Project) and ‘WBS Description’‘WBS Status’‘WBS Type’‘WBS Manager’‘Contract Code’‘Customer ID’, ‘Customer Name’‘MRV’‘Opportunity Total Value’‘Opportunity Total Weighted Value’‘Invoices raised YTD’‘Total Revenue YTD’‘Invoices raised LTD’‘Total Revenue LTD’

The report will be able to be run by:‘Country’Financial Year & Accounting PeriodSiebel Structure‘Profit Centre’ structure‘Business Stream’

Assumptions: We are assuming that as a part of the conversion of live projects from FISP -> SAP, the value of sales invoices raised will also be migrated for each project and will be available by accounting period.

Functional Area(s) : SAP SD (FI,PS)

Created by: Srikanth

Date Created: 6th August 2007





2 Ownership

Business Requestor: Stuart Cartwright

Business Area Owner: Reporting

Key Contacts: Mast,Anna,Ashleigh

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

Date Required: To be defined





3 Report Content

3.1 Report Interactivity

Static Report Interactive Report Preferred Display Medium (if known)

X Drop to Excel

Other Expectations:

To be run daily. May require use of BW report scheduler functionality.

Data needs to be updated daily but the report may be viewed weekly may be sometimes daily also.

3.2 Fields and Key Performance Indicators

The cube 0PS_C041 can be used. It has the details like Proj def, WBS and also it’s liked to finance, controlling. Custom cube needs to be created to display Siebel data. The same data model can be used in many reports. For the SD data once the mast and business conforms the customer structure and also the invoices tables then the sales cube 0SD_C03 which has data source 2LIS_01_S262 billing document which suits the same can be used and also other FI related data like revenue related to orders needs to be identified once the COPA consultant arrives in august first week and added to same cube or identify if any standard exits.

Based on the above cubes the multiproviders needs to be created and enable the display of records in unique rows.

Description of Field

Fields (if known)

Table (if known) Formula / Restrictions

OR

Type of field

UOM

OR

Length

Navigation/Drill Down (Y/N) –see Section 3.5

Sort (Asc/Dsc)

Total Pg Brk

Country

SAP SD or Siebel

Customer master

Bill to address of the head office of

the company rather than where the bills are paid

KNA1-LAND1

If project is not linked to a contract in SAP SD then take county

from Siebel opportunity record





Project ID

SAP PS

Project definition PROJ-PSPID

WBS WBS level 1 PRPS-POSID

Project desc

SAP PS

Project description

PRPS-POST1

WBS level 1 description

SAP PS

WBS description PRPS-POST1

Siebel Sector

SAP PS/Siebel

Either SAP PS Z_PS_SIEBEL table or Siebel

directly

Siebel Segment

SAP PS/Siebel


directly

Siebel Sub-Segment

SAP PS/Siebel


directly

Business Stream

SAP PS/Siebel


directly

Profit Centre Groups

SAP

SAP SD team (Mast) and

Business would conform

Profit Centre

SAP PS / Siebel

SAP PS team (Ashleigh) and Business would

confirm

Project Manager

Text description

SAP PS

Person Responsible

PRPS-VERNA

Project Manager emp id

SAP PS

Person responsible

PRPS-VERNR .





Project Type

SAP PS

Project profile PROJ-PROFL

Project Status

SAP PS

System status CNJ_STAT-STTXT_INT

SAP PS team (Ashleigh) would give the detail of table as above mentioned is

structure.

Contract code

SAP SD

SAP SD,Customer

Contract Number

VBKD-BSTKD

Contract Customer ID

SAP SD

Query to SAP SD team(Mast)

Customer no

KNA1-KUNNR

Contract Customer name

SD

Customer desc KNA1-NAME1

If no SAP contract take from Siebel

opportunity account name

MRV

SAP PS

Max revenue value

MAX revenue value

PRPS-USR04

Billing Limit(k)

SAP

Removed

Business (Michael cutting) decides

we don’t need this field in the SAP

PS.

Removed

Opportunity ID

Siebel

s_opty.row_id

Refer column sources for logic.

Opportunity name

Siebel

s_opty.name





Channel manager name

Siebel

Pick from Siebel. Can be in Adrian’s

column sources

x_login_ml FROM s_opty

Siebel account ID

Siebel

Customer number in Siebel

Siebel account name

Siebel

Customer name in Siebel

name FROM s_org_ext

Opportunity Total value

Siebel

Pick from column sources document

from business (Adrian) Siebel

Opportunity Total weighted value

Siebel

Pick from column sources document

from business (Adrian) Siebel

Invoices raised YTD

SAP

Pick all the invoices based on

the AP for this year.

SAP SD team(Mast )

would give the information for

Key figure

Total revenue YTD

SAP

Pick total revenue based on the AP

for this year.

The controlling team (New Copa consultant) would

give the information for

Key figure

Invoices raised

Pick all the invoices based on

the AP for LTD





LTD

SAP

SAP SD team(Mast) would


Key figure

Total revenue LTD

SAP

Pick total revenue based on the AP

for LTD

The controlling team (New Copa consultant) would


Key figure





3.3 Selection Criteria

Field Selection Criteria‘Financial Year’Accounting Period‘Country’‘Profit Centre’ structureSiebel Structure‘Business Stream’

3.4 Reporting Period (Granularity at which user will report)

Day Week Month Quarter

Year Fiscal Week

Fiscal Period

Fiscal Quarter

Fiscal Year

Other

X

Comments: To be defined

3.5 Drill Down Requirement

Drill-Down Field Navigation Path

NA No drill-down required.

4 Technical Requirements

4.1 Source of Data





Source System(s) Structure (Transaction, Report, Tables, Flat File, etc.)

Siebel,SAP To be defined

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

Recon. Procedure Process

NA NA

4.3 =Historical Data Requirement (How much Historical Data is needed)

Time Horizon of Report Projects which are open in people soft are bought to SAP. Mostly the projects are bought with history 1 year but there may be some projects which are up to 7 years old.

The business would be interested to run this report on previous year and obviously for current year and this report would only give the report of open projects which are bought into SAP and there will be no reporting regarding Closed projects in people soft as they will be not be bought into SAP.

Known Conversion Issues To be defined

Retention / Aggregation To be defined

Maintain or Overwrite History

To be defined

4.4 Usage Frequency (Query Execution Frequency)

Hourly Daily Weekly Monthly Quarterly Yearly

X

Comments: Adhoc say once a month, once a week

Approx. Number of Users: TBD




FUNCTIONAL REPORT SPECIFICATIONS4.5 Refresh Rate of Data (How often does data need to be refreshed in BW)

On Demand Daily Weekly Monthly Quarterly Yearly

X

Comments: To be defined

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

Dependent Business Process Criteria

Revenue To be defined





5 Example Report Format/Layout

Example

generic column sources doc for Siebel





6 Security

Data Access Restrictions

Restriction Criteria Intended Audience Excluded Audience

To be defined To be defined To be defined To be defined

7 Testing Requirements

7.1 Technical Test ConditionsDocument all technical scenarios associated with this development. Examples would include 1) testing an error-free run; 2) testing the exception processes; 3) testing the error handling.

Technical Test Conditions

ID Condition Detail Expected results

1 Run this report for the following selection:

This Financial YearThis Accounting PeriodDefault CountryDefault Profit Centre Default Siebel StructureDefault Business Stream

A report

2Profit Center Hierarchy

Check that all levels of the profit centre hierarchy with the profit centre hierarchy in ECC6

Report field values to match origin system field values

3 Verify on the ECC 6 the fields and compare with the report fields

Verify the field values for the same selections on ECC 6:

Profit Centre Groups

Profit Centre

Project Manager

Text description






Project Manager emp id

Project Type

Project Status

Contract code

Contract Customer ID

Contract Customer name

MRV

Max revenue value

Invoices raised YTD

Total revenue YTD

4 Verify on the Siebel the fields and compare with the report fields

Report field values to match origin system field values:

Opportunity ID

Opportunity name

Channel manager name

Siebel account ID

Siebel account name

Opportunity Total value

Opportunity Total weighted value


5 Re-run this report for the following selection:

This Financial YearAnother Accounting PeriodDefault CountryDefault Profit Centre Default Siebel StructureDefault Business Stream

Repeat steps 3 and 4


Another Financial YearAnother Accounting PeriodDefault CountryDefault Profit Centre Default Siebel StructureDefault Business Stream







This Financial YearThis Accounting PeriodAnother CountryDefault Profit Centre Default Siebel StructureDefault Business Stream



This Financial YearThis Accounting PeriodDefault CountryAnother Profit Centre Default Siebel StructureDefault Business Stream



This Financial YearThis Accounting PeriodDefault CountryDefault Profit Centre Another Siebel StructureDefault Business Stream



This Financial YearThis Accounting PeriodDefault CountryDefault Profit Centre Default Siebel StructureAnother Business Stream


11 Verify the data load sequence and the report data refresh sequence.




FUNCTIONAL REPORT SPECIFICATIONS7.2 Testing Considerations/Dependencies

This test should be done after loading Master and Transactional data in SAP BW; ECC 6 data should have no changes so the transaction and master data can be compared.

This report can be tested by itself.

8 Peer Review

Reviewed By: Mukesh

Date Reviewed:

9 Questions and Notes

Issues:

1. If the report needs to be run for Periods before SAP was introduced, the user should go to MIR archive. i.e. it is assumed that the current CDW will exist and be available to users for ~18 months. Once in SAP, the report should allow data for up to the previous 12 months of SAP data.

10 Sign-Off

Reviewed By: Stuart Cartwright

Approved By:

Date Approved:

11 Change Log

Date Change Reason Who

26.06.2007 Initial draft Initial draft Srikanth

01/11/2007 Version 2.0 Added test procedure T Belmonte


fs_1

Documents

siebel data

report content

sd data

data needs

source of data

data source

data model

bw data loads