SAPBW Technical Specification Template

Consultancy Co.
Client Logo <XXXXXX> BI Technical Specification

Logo
Technical Specification – BI
<Name of the Specification>
Document Reference : <Document Reference name>

Version : <Version Number>
Document Status : Review [Draft/Review/Signed Off]
Author : < Author Name >
Last Revision Date : <DD-MON-YYYY>

Date Created : <DD-MON-YYYY>
Date Printed : <DD-MON-YYYY>
www.SAPBWConsulting.com
<XXXXXX> BI Technical Specification
Document Information
Business Area
GAP/CR ID
FS Definition Form ID
SAP BW Version SAP NetWeaver BW 7.3
Global / Local
Approval
Approved by Name Role Signature Date

Work stream
Team Lead
Development
Team Lead
Document History
Version Reason for change Date

1.0
1.1
1.2
1.3
Page 2 of 30
Table of Contents
1. GENERAL INFORMATION............................................................................................4
2. DESCRIPTION AND PURPOSE...................................................................................5
3. TECHNICAL DESIGN OVERVIEW...............................................................................5
3.1 Assumption............................................................................................................................ 5
3.2 Design Solution - Overview....................................................................................................6
3.3 Data Flow Diagram................................................................................................................ 6
3.4 Data Requirement..................................................................................................................6
4. ISSUES..........................................................................................................................7
5. TECHNICAL SOLUTION...............................................................................................7
6. BI OBJECT DETAIL DESIGN (DATA FLOW DESIGN).................................................8
6.1 InfoObject (Characteristics & Key Figure) Detail Specification...............................................8

6.2 Datasource/Extractor Detail Specification..............................................................................8
6.2 DSO/ODS Detail Specification.............................................................................................12
6.3 InfoCube Detail Specification...............................................................................................17
6.4 MultiProvider Detailed Specification.....................................................................................22
6.5 Reporting Requirements......................................................................................................24
7. WORKBOOK DESIGN................................................................................................28
8. ERROR MESSAGES .................................................................................................29
9. SECURITY REQUIREMENTS/ AUTHORIZATION DETAILS....................................30
10. ADDITIONAL INFORMATION AND ATTACHMENTS...............................................30
11. UNIT TEST PLAN......................................................................................................30
Page 3 of 30
1. General Information
Functional Design Spec ID: Report ID:

Report Title:
Implement. Phase
Message Class:
Develop. Class:
Module:
Report Paper Size
Report User/User Group:
Contact Details:
Prepared By Prep Date:
Phone Number:
Email Address:
Business/Functional Analyst:
Phone Number:
Email Address:
Functional Area User
Contact:
Primary:
Phone Number:
Email Address:
Secondary:
Phone Number:
Email Address:
Report Run Frequency Languages

Priority: Complexity:
Expected volume:
Data Refresh Frequency
Transport Information
Object Identifier Object Type

Change Task # (Program ID, Layout Set (Program, Transaction, Layout
Request # ID, etc) Set)
Page 4 of 30
2. Description and Purpose

TEXT TO BE REMOVED. GUIDANCE ONLY
< Description of the BI report/analytical application such as its purpose, how, when, why, where, who, as
appropriate. Provide additional information about the design of the application not covered in the other descriptions.
>
END OF GUIDANCE TEXT
3. Technical Design Overview
3.1 Assumption
< The technical designer should detail here all the procedures or configuration affecting the
report that the developer can take for granted. Other assumptions that the designer foresees
will better focus the scope of the enhancement should also be included here.
This is a very important part of the specification as it ensures that no unnecessary development
work is undertaken.
It is normal for assumptions to be thought up at the technical development stage as well as the
functional specification stage as development and testing may throw up more obscure
scenarios than thought out at a business level. These should be discussed during the
development stage and added to the spec when agreed.
Example assumptions:
1) All weights in the SAP system will be in kilograms
2) The user-exit will only be available to the Spanish users
3) Deliveries will have a maximum of 5 line items
4) The login language will be Spanish
5) Only Billing documents with Delivery documents (SD Preceding document category ‘J’) as
their preceding referenced document will be extracted
6) The lessee’s price will never be more than 7 characters long
7) Etc.> END OF GUIDANCE TEXT
Page 5 of 30
3.2 Design Solution - Overview

Provide a brief textual overview of the technical solution, noting data targets, sources of data, degree of
customization, etc. Business justification and requirements need not be addressed here, as these are more
appropriately covered in the BW Functional Specification document.
BCT,
Syst Enhanced,
BW Object Type Technical Name Description em Custom
Data Source
Info Source
ODS Object
InfoCube
MultiProvider
3.3 Data Flow Diagram

3.3.1. Flow of Transactional Data
Diagram the flow of transactional data from source to data target. Include such key components as Extractor,
DataSources, and Data Targets. Highlight significant data transformations (user exit logic, transfer rules, update
rules, etc.) in the flow at the point where they occur, and supplement this with additional textual description below
the diagram if necessary.
3.3.2. Flow of Master Data
For any “significant master data”, provide an overview of the master data flow through diagrams and/or textual
description. Include information such as primary source tables/files and highlights of significant data
transformations (user exits, transfer routines, etc.). Within the context of this section, “significant master data”
refers primarily to master data objects with complex customization (multi-table extraction, transformation logic,
etc.), although SAP-delivered master data objects with complex extraction and/or transformation may occasionally
be included as well.
3.4 Data Requirement

3.4.1. Key Figures/KPIs
Key Figure Key Figure Technical Name Unit Basic CKF RKF Comments
ID
01 Total credit postings 0CREDIT 0CURRENCY X
02 Total Debit Postings 0DEBIT 0CURRENCY X
03 Balance 0CKF_BLNC X =01-02
n
Page 6 of 30
3.4.2. Characteristics
Characteristic Technical Name Nav. Attr Text Hier Comments
Attr.
Company Code 0COMP_CODE Yes Yes Yes No
3.4.3. Time Characteristics

Characteristic Technical Name Comments
Fiscal Year 0FISCYEAR
3.4.4. Unit Characteristics
*Global Settings: Import Unit and Currency tables from R/3

Characteristic Technical Name Comments
Currency 0CURRENCY
4. Issues
TEXT TO BE REMOVED. GUIDANCE ONLY:
<This section should be used like a log during the creation of this document to outline any
outstanding issues that need to be resolved prior to continuing with the development work. Prior
to sign-off there should be no issues remaining.> END OF GUIDANCE TEXT
Issue Date Issue Description Issue Resolution

# Raised
5. Technical Solution

<This section highlights the key design issues. A series of bullet points summarizing the logic
chosen for the program and the main technical difficulties.
For Example:
• What assumptions are made in the technical specification and what they entail in technical
terms.
Page 7 of 30
• Key process steps.

• Why a particular function module was chosen.
• Why use multiple selects rather than just one.
• Why use a particular kind of logic for the main processing.
• What were the major technical problems with the design of the BI objects
• Etc. > END OF GUIDANCE TEXT
6. BI Object Detail Design (Data Flow Design)
6.1 InfoObject (Characteristics & Key Figure) Detail

Specification

< In this section, InfoObject specification and design needs to be maintained in excel format, as
provided in the attachment. Special logic for data updating of Master Data needs to be attached
separately. Detail specification for Master data InfoObject loads needs to be maintained. For
every Master Data load, a document needs to be inserted here. >
Detail Specification for Master data InfoObject Loads:
6.2 Datasource/Extractor Detail Specification

Extractor Summary:
In the table below, list all the extractors related to the data flow from the source system to the
DSO/Cubes in BW. These should typically be transactional data sources for the purpose of this
document as master data related data sources for loading master data objects will already be
specified in the previous section 6.1. If however the master data datasource is to be loaded
directly into a DSO/Cube, then it is considered part of the data flow and should be listed below.
Page 8 of 30
Description Technical Datasource Source System BC/Generic/Generated BC

Name Type Enhanced
(Y/N)
General Ledger: 0FI_GL_10 Transactional ECDCLNT120/ Business Content (BC) No
Leading Ledger ECQCLNT220/
Balances ECPCLNT300
Generic Data Source Details:

Specify the ECC Data Source design here for generic data sources. Leave blank or delete if
none used. (RSO2).
Name Value
Settings
Application Component e.g. FI-GL
Data Reconciliation Yes/No
Short Description
Medium Description
Long Description
Extraction from DB View
View/Table e.g. LFN1
Extract Structure
Extraction from SAP Query
InfoSet
Extraction from Function Module
Function Module
Extract Structure
Generic Delta Settings for this Data Source:

Delta Enabled Yes/No
Delta-Specific Field:
Field Name
Time Stamp (UTC)
Time Stamp (Local)
Calendar Day
Numeric Pointer X
Settings:
Safety Interval Upper Limit
Safety Interval Lower Limit
Real-Time Enabled Yes/No
New Status for Changed Records X
Additive Delta
Page 9 of 30
For all Data Sources (Generic or enhanced Business Content), please detail the Customer View
settings below from RSA6. For non-modified Business Content data sources, you can simply
include the official link to SAP’s online documentation.
Data Source 0FI_GL_X

Description General Ledger: Line Items with Delta Extraction
Direct Access 1 supported (without preaggregation)
Delta Update Yes/No
Data Source for Yes/No
Reconciliation
Field Short Text Selection Hide Inversion Field Only
Name Field Known in
Customer Exit
BELNR Accounting X
Doc.
Number
URL for Standard Data Source:
Function Enhancement:
Document function enhancements for each data source here if any.
Enhance Extraction Structure:

Document any includes or appends to the extraction structure here for each data source.
Append Name
Data Source
Component Component Data Type Length Decimal Description
Type
Page 10 of 30
LO Cockpit Enhancements (LBWE):

For logistics extractors only, detail any enhancements or fields that are to be added to the
extractor here.
Data Source 2LIS_02_SCL

Extract Structure MC02M_0SCL
Update Mode Unserialized V3 Update
Table Field Description
MCEKET BUKRS Company Code
BW Data Source Specification:

Specify the BW Data Source settings here for custom Data Sources. Use this form if needed for
enhanced Business Content Data Sources as well.
P Field Description Exter Key Conv. Lower Format SS Curren Sele Selection Options
o nal Field Routines case Conv. cy / ction
s Lengt Routine Unit
. h
1
2
3
4
5
6
7
Page 11 of 30
6.2 DSO/ODS Detail Specification
Technical Name Description

0FIGL_O10 General Ledger (New): Transaction Figures
Settings
Type of DataSource Object Standard/ Write optimised / Direct update
SID Generation upon Activation During Reporting/During Activation/Never
Create SIDs
Unique data records Yes/No
Activate Data Automatically Yes/No
Set Quality Status to ‘OK’ Automatically Yes/No
Update Data Automatically Yes/No
Partition Condition:
InfoArea 0FIGL_ERP
Key Fields
InfoObject Technical Name Data Type Length
Description
Data Fields
Description
Navigation Attribute
Description
Indexes
010
Description
Page 12 of 30
020
Description
Page 13 of 30
Transformation
Transformation Description TRCS ZFI_GL_10 -> ODSO 0FIGL_O10
Target of Transformation:
Object Type:
Name
Source of Transformation:
Object Type
Name
Rule Group:
Start Routine: <Insert your Start Routine Code here>
Fields
Source Field Method ( Direct Target InfoObject Conversion Perform
Assignment = D, Exit Conversion
Constant = C, Exit (Y/N)
Read Master Data
= M, Read from
DataStore = RD,
Formula = F,
Initial = I ,Time
Characteristics =
T , Routine = R
0GL_ACCOUNT D 0GL_ACCOUNT ALPHA No
End Routine: <Inset your End Routine Code here>
Field Routines:
< Write a sample code for each Field Routine used in the Transformation >
InfoObject
Field Routine: <Inset your Field Routine Code here>

InfoObject

InfoObject
Page 14 of 30
Data Transfer Process

Data Transfer Process 0FI_GL_10 / ECDCLNT120 -> 0FIGL_O10
ID BWD DTP_4M5BHAO1MYHF7A73Q5WKM8SIE
BWQ
BWP
DTP Type Standard
Extraction:
Source of DTP (Technical Name) 0FI_GL_10
Description General Ledger: Leading Ledger Balances
Data Source Type Data Source
Source System ECDCLNT120/ECPCLNT300
Extraction Mode: Full/Delta
Only get delta once
Get one request only
Retrieve until no more new data
Parallel Extraction (Y/N)
50,000
Package Size
Filter Condition: Field From (or To (or Routine)
Variable)
Fiscal 0I_CUFQU
year/period
Fiscal 001.2011 012.2011
year/period
Selection of Key Fields for Error Stack:

Key Field Field Name Long Description
Update:
DTP Data Target 0FIGL_O10
Description General Ledger (New): Transaction Figures
Data Target Type DSO
Error Handling: Update Valid Records: No reporting (Request Red)
Maximum Number of error per 100
pack
No Update without Master NO
Page 15 of 30
Data:
Execute:
Technical Request Status Request Status is set to ‘green’ if warnings occur
Overall Status of Request Set Overall Status Automatically
Processing mode: Serial Extraction, Immediate Parallel Processing
Automatically Repeat Red No
Requests in Process Chains
(Y/N)
Page 16 of 30
6.3 InfoCube Detail Specification

The following template takes into consideration most of the possible settings available with all
types of Cubes. Some fields may not be relevant to your InfoCube (e.g. Subtype is not required
for Standard InfoCubes).

0FIGL_C10 General Ledger (New): Transaction Figures
Settings
Type Standard InfoCube
SubType
BWA Status No BWA Index
InfoArea 0FIGL_ERP
Partition Condition 0CALMONTH/0FISCPER/Not Used
From To
Max No. of Partitions
This template provides enough rows for the maximum number of dimensions. Delete the
unused dimensions in this document when you are done.
Dimensions
InfoObject Description Data Type Length
Data Package 0CHNGID Change run NUMC 14
ID
0RECORDTP Record type NUMC 01
0REQUID Request ID CHAR 30
Time
Unit
Dimension 1 (replace with

Dimension’s name e.g.
Organizational Units)
Dimension 2
Dimension 3
Dimension 4
Page 17 of 30
Dimension 5
Dimension 6
Dimension 7
Dimension 8
Dimension 9
Dimension A
Dimension B
Dimension C
Dimension D
Structure Specific Property

InfoObject Description Constant Document Display Selection Query
property Execution
Filter Value
Description
Key Figures
InfoObject Technical Data Length Type Cumulat Aggreg. Except. Unit
Description Name Type ive (Y/N) Aggreg.
Cumulative 0BALANCE CURR 09 Amount Y Sum Last 0CURR
Balance ENCY
Key Figure Structure specific property

InfoObject Description Decimal places Display
Page 18 of 30
Transformation
Transformation Description ODSO 0FIGL_O10 -> CUBE 0FIGL_C10
Target of Transformation:
Object Type: InfoCube
Name
Source of Transformation:
Object Type DSO
Name
Rule Group:
Start Routine: <Insert your Start Routine Code here>
Fields
Source Field Method ( Direct Target InfoObject Conversion Perform
Assignment = D, Exit Conversion
Constant = C, Exit (Y/N)
Read Master Data
= M, Read from
DataStore = RD,
Formula = F,
Initial = I ,Time
Characteristics =
T , Routine = R
0GL_ACCOUNT D 0GL_ACCOUNT ALPHA No
End Routine: <Inset your End Routine Code here>
Field Routines:
< Write a sample code for each Field Routine used in the Transformation >
InfoObject

InfoObject

InfoObject
Page 19 of 30
Data Transfer Process

Data Transfer Process 0FIGL_O10 -> 0FIGL_C10
ID BWD DTP_4KPUR0N8AZEZ8JEFHA14N13VY
BWQ
BWP
DTP Type Standard
Extraction:
Source of DTP (Technical Name) 0FIGL_O10
Data Source Type Data Store Object
Source System BW
Extraction Mode: Full/Delta
Only get delta once
Get one request only
Retrieve until no more new data
Parallel Extraction (Y/N) Yes
50,000
Package Size
Filter Condition: Field From (or To (or Routine)
Variable)
Fiscal 0I_CUFQU
year/period
Fiscal 001.2011 012.2011
year/period
Selection of Key Fields for Error Stack:

Key Field Field Name Long Description
Update:
DTP Data Target 0FIGL_C10
Data Target Type InfoCube
Error Handling: No Update, No Reporting
Maximum Number of error per 100
pack
No Update without Master NO
Data:
Page 20 of 30
Execute:
Technical Request Status Request Status is set to ‘green’ if warnings occur
Overall Status of Request Set Overall Status Automatically
Processing mode: Serial Extraction, Immediate Parallel Processing
Automatically Repeat Red No
Requests in Process Chains
(Y/N)
Page 21 of 30
6.4 MultiProvider Detailed Specification
Relevant InfoProviders
Technical Name Description InfoProvider Type
Cube/DSO/InfoObject/HybridProvider/
InfoSets/Aggregation Levels
Dimensions
InfoObject Description Data Length Identify
Type
Data Package 0CHNGID Change run NUMC 14 NA
ID
0RECORDTP Record type NUMC 01 NA
0REQUID Request ID CHAR 30 NA
Time 0FISCPER Fiscal Year / NUMC 07 0FIA_DS11
Period
Unit
Dimension 1 (replace with

Dimension’s name e.g.
Organizational Units)
Dimension 2
Dimension 3
Dimension 4
Dimension 5
Dimension 6
Dimension 7
Dimension 8
Page 22 of 30
Dimension 9
Dimension A
Dimension B
Dimension C
Dimension D
Structure Specific Property

InfoObject Description Constant Document Display Selection Query
property Execution
Filter Value
Description
Key Figures
InfoObject Technical Data Length Type Cumulat Aggreg. Except. Unit Select
Description Name Type ive (Y/N) Aggreg. (Assign
)
Cumulative 0BALANCE CURR 09 Amount Y Sum Last 0CURR
Balance ENCY
Key Figure Structure specific property

InfoObject Description Decimal places Display
Page 23 of 30
6.5 Reporting Requirements
Desired Layout Design
TEXT TO BE REMOVED. GUIDANCE ONLY <Please attach file if available. Below is an

example embedded into word, but you may also insert an excel file for larger
reports> END OF GUIDANCE TEXT
Example:
G/L Account JAN 2010 FEB 2010 MAR 2010 Overall Result
Tr Rcvbls -
0010/121000 $ 0.00 $ 0.00 $ 0.00 $ 0.00
Domestic
Invt - Trading Gds 0010/135075 $ 0.00 $ 0.00 $ 0.00 $ 0.00
Machinery &
0010/160020 $ 2,150.00 $ 0.00 $ 0.00 $ 2,150.00
Equipmt
Accum Dpr - M & E 0010/170020 -$ 179.17 $ 0.00 $ 0.00 -$ 179.17
Tr Pybls - Domestic 0010/211000 $ 0.00 $ 0.00 $ 0.00 $ 0.00
Sales Tax AR -
0010/216100 $ 0.00 $ 0.00 $ 0.00 $ 0.00
State
Invt - Initial (Trd) 0010/399175 $ 0.00 $ 0.00 $ 0.00 $ 0.00
Sales Rev 0010/410000 $ 0.00 $ 0.00 $ 0.00 $ 0.00
Sales Rev -
0010/410010 $ 0.00 $ 0.00 $ 0.00 $ 0.00
Services
Cost of Gds Sold 0010/500000 $ 0.00 $ 0.00 $ 0.00 $ 0.00
Extraord Exp/Inc 0010/701000 -$ 1,970.83 $ 0.00 $ 0.00 -$ 1,970.83
Overall Result $ 0.00 $ 0.00 $ 0.00 $ 0.00
Page 24 of 30
Report Structure
TEXT TO BE REMOVED. GUIDANCE ONLY <Please list any selection criteria the users may
have for this report. Note if the filter should be Interactive in the first table (i.e. a selection by the
user and if it is optional or mandatory). For static and non-interactive filters list these in the
second table “Global Filters”. > END OF GUIDANCE TEXT
Interactive Selection Criteria

Order on Criteria InfoObject Mandatory * Default Selection Variable
Screen (InfoObject (Technical or optional value Type Technical
Description) Name) (Single value, Name
range, etc.)
1 Company Code 0COMP_CODE Mandatory Multiple 0P_COCD
Selection
2 Calendar Month 0CALMONTH Optional blank Range 0I_CLMTH
3 Profit Center 0PROFIT_CTR Optional Hierarchy Node 0H_PCTR

Group
Global Filters
Criteria InfoObject Constant SAP/Customer Variable’s Selection
(InfoObject (Technical Values EXIT Technical Type
Description) Name) Variable Name (Single value,
Description range, etc.)
Fiscal Year 0FISCVARNT Z1 Single Value
Variant
Fiscal Year / 0FISCPER Current Fiscal 0FPER Single Value
Period Year/Period
Controlling Area 0CO_AREA 1000 Single Value
Authorization
Reporting Data-Provider (InfoProvider):
0FIGL_C10 General Ledger (New): Transaction

Figures
Page 25 of 30
Rows
Technical Description Description Display Text Sort Sort Sort Result Hierarchy Expand
Name in Query As View Characteristic by Direction Rows Display To
Level
0PROFIT_CTR Profit Standard / Key Short 0PROFIT_CTR Text Ascending Always Active 2
Center alternative and Display
Text
Columns
Technical Description Description Display Text Sort Sort Sort Result Hierarchy Expand
Name in Query As View Characteristi by Direction Rows Display To
c Level
0FISCPER Fiscal Standard Text Medium 0FISCPER Key Ascending Always Inactive
Year / Length Display
Period
ZRKFBLNCP Plan Plan Ascending
Balance
ZRKFBLNCA Actual Actual
Balance
0SALES Sales for Sales for
the Period the Period
ZCK_BLNC_VAR Balance
Variance
Free Characteristics (Drill-down characteristics)
Technical Name Description Description Display Text Sort Sort Sort Result Hierarchy Expand
in Query As View Characteristi by Direction Rows Display To
c Level
0GL_ACCOUNT GL Standard Text Medium Key Ascending Never Inactive
Account and Length
Key
0COSTCENTER Cost Center Standard Text Medium Always
Length
Page 26 of 30
Calculated Key Figures
Technical Name Description Calculation Logic
ZCK_BLNC_VAR Balance Variance ZRKFBLNCP – ZRKFBLNCA
Restricted Key Figures
Technical Name Description Restriction Logic
ZRKFBLNCP Plan Balance 0VTYPE = 20 (Plan), 0VERSION = 0 (Plan/Actual Version),

0BALANCE
Formulae
Technical Name Description Calculation Logic
Variance % [(ZRKFBLNCP – ZRKFBLNCA) / ZRKFBLNCP] * 100
Selections
Technical Name Description Restriction Logic
Plan Balance 0VTYPE = 20 (Plan), 0BALANCE
Conditions
Condition Key Figure Operator Value Determine Characteristic Characteristic

Assignment
Condition 1 BALANCE LT 5 Individual Characteristics 0GL_ACCOUNT
and char. Combinations
0COSTCENTER
Exceptions
Exception Alert Operator Values Exception Exception Exception Exception

Description Level Defined On Defined On Affects Affects
(in case of Data Cells Characteris
Page 27 of 30
two tic Cells

structures)
Exception 1 Good 1 EQ 0 Balance All Structure Balance Rows
Elements
Critical 1 LT 5
Bad 1 BT [-5;5]
Cell Restrictions
Exception Exception Exception Only Characteristic Operator Value
Description Affects Affects Results
Everything
Exception 1 X
Customer Variables
Document any custom variables created for this report. Do not document standard variables.
For Replacement Paths, create a new section below the table clearly referencing the variable it
InfoObject Variable Variable Processing by Variable Mandatory or Exit (Y/N) Default
Technical Description Represents optional if Y then (If so, at
Name STEP what
value?)
0CRM_CRD_AT ZABC New Variable… Manual Single Value Mandatory Y (1) Sy-date
Input/Authorization
0CALMONTH ZCDF Optional N
belongs to.
Characteristic Customer Exit Variable Name Logic
7. Workbook Design
Document the queries used for the workbook here along with information on their InfoProviders.
Order Query Name Query InfoProvider InfoProvider InfoArea
Page 28 of 30
Technical Name Technical

Name Name
1
2
3
4
8. Error Messages
Describe the expected error messages (Monitor Screen) for different error conditions during
data loads.
Error Message Error Message Text Error Conditions

Number (70 characters)
1.
2.
3.
Page 29 of 30
9. Security Requirements/ Authorization Details
<Please describe any specific security requirements>
10. Additional Information and attachments
Document File location(If for

Comments
Name/Attachment common access)
TEXT TO BE REMOVED. GUIDANCE ONLY <

Any information the designer believes to be of benefit to the developer should be attached here.
Other objects necessary for the correct running of the enhancement should also appear here.
> END OF GUIDANCE TEXT
11. Unit Test Plan

USER GUIDANCE <Detail Test Plan & result should be maintained here> END OF GUIDANCE
TEXT
Page 30 of 30

SAPBW Technical Specification Template

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

SAPBW Technical Specification Template

Diunggah oleh

Hak Cipta:

Format Tersedia

Consultancy Co.

Client Logo <XXXXXX> BI Technical Specification

Document Reference : <Document Reference name>

Author : < Author Name >

Last Revision Date : <DD-MON-YYYY>

SAP BW Version SAP NetWeaver BW 7.3

Approved by Name Role Signature Date

Version Reason for change Date

2. DESCRIPTION AND PURPOSE...................................................................................5

3. TECHNICAL DESIGN OVERVIEW...............................................................................5

6. BI OBJECT DETAIL DESIGN (DATA FLOW DESIGN).................................................8

6.1 InfoObject (Characteristics & Key Figure) Detail Specification...............................................8

8. ERROR MESSAGES .................................................................................................29

9. SECURITY REQUIREMENTS/ AUTHORIZATION DETAILS....................................30

10. ADDITIONAL INFORMATION AND ATTACHMENTS...............................................30

11. UNIT TEST PLAN......................................................................................................30

Functional Design Spec ID: Report ID:

Report Run Frequency Languages

Object Identifier Object Type

2. Description and Purpose

END OF GUIDANCE TEXT

3. Technical Design Overview

3.2 Design Solution - Overview

3.3 Data Flow Diagram

3.4 Data Requirement

3.4.3. Time Characteristics

3.4.4. Unit Characteristics

*Global Settings: Import Unit and Currency tables from R/3

Issue Date Issue Description Issue Resolution

TEXT TO BE REMOVED. GUIDANCE ONLY:

• Key process steps.

6. BI Object Detail Design (Data Flow Design)

6.1 InfoObject (Characteristics & Key Figure) Detail

TEXT TO BE REMOVED. GUIDANCE ONLY:

Detail Specification for Master data InfoObject Loads:

6.2 Datasource/Extractor Detail Specification

Description Technical Datasource Source System BC/Generic/Generated BC

Generic Data Source Details:

Generic Delta Settings for this Data Source:

Data Source 0FI_GL_X

URL for Standard Data Source:

Enhance Extraction Structure:

LO Cockpit Enhancements (LBWE):

Data Source 2LIS_02_SCL

BW Data Source Specification:

6.2 DSO/ODS Detail Specification

Technical Name Description

End Routine: <Inset your End Routine Code here>

Field Routine: <Inset your Field Routine Code here>

Field Routine: <Inset your Field Routine Code here>

Field Routine: <Inset your Field Routine Code here>

Data Transfer Process

Selection of Key Fields for Error Stack:

6.3 InfoCube Detail Specification

Technical Name Description

Max No. of Partitions

Dimension 1 (replace with

Structure Specific Property

Key Figure Structure specific property

End Routine: <Inset your End Routine Code here>

Field Routine: <Inset your Field Routine Code here>

Field Routine: <Inset your Field Routine Code here>

Field Routine: <Inset your Field Routine Code here>