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
BI Technical Specification
1. General Information Functional Design Spec ID: Report Title: Implement. Phase Message Class: Develop. Class: Module: Report Paper Size Report User/User Group:
Report ID:
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 Priority: Expected volume: Data Refresh Frequency
Languages Complexity:
Transport Information
Change Request #
Task #
Object Identifier (Program ID, Layout Set ID, etc)
Object Type (Program, Transaction, Layout Set)
Page 4 of 30
BI Technical Specification
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 TEXT TO BE REMOVED. GUIDANCE ONLY < 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
BI Technical Specification
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.
BW Object Type
Technical Name
Syst em
Description
BCT, Enhanced, 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 ID 01 02 03 n
Key Figure
Technical Name
Unit
Total credit postings Total Debit Postings Balance
0CREDIT 0DEBIT 0CKF_BLNC
0CURRENCY 0CURRENCY
Basic
CKF
RKF
Comments
X X X
=01-02
Page 6 of 30
BI Technical Specification
3.4.2. Characteristics Characteristic
Technical Name
Company Code
0COMP_CODE
Nav. Attr. Yes
Attr Yes
Text
Hier
Yes
No
Comments
3.4.3. Time Characteristics Characteristic Fiscal Year
Technical Name 0FISCYEAR
Comments
3.4.4. Unit Characteristics *Global Settings: Import Unit and Currency tables from R/3 Characteristic Currency
Technical Name 0CURRENCY
Comments
4. Issues TEXT TO BE REMOVED. GUIDANCE ONLY: END OF GUIDANCE TEXT
Issue #
Date Raised
Issue Description
Issue Resolution
5. Technical Solution TEXT TO BE REMOVED. GUIDANCE ONLY: BI Technical Specification • 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 TEXT TO BE REMOVED. GUIDANCE ONLY: < 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. > END OF GUIDANCE TEXT
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
BI Technical Specification
Description General Ledger: Leading Ledger Balances
Technical Name 0FI_GL_10
Datasource Type Transactional
Source System
BC/Generic/Generated
ECDCLNT120/ ECQCLNT220/ ECPCLNT300
Business Content (BC)
BC Enhanced (Y/N) No
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 Data Reconciliation Short Description Medium Description Long Description Extraction from DB View View/Table Extract Structure Extraction from SAP Query InfoSet Extraction from Function Module Function Module Extract Structure Generic Delta Settings for this Data Source: Delta Enabled Delta-Specific Field: Field Name Time Stamp (UTC) Time Stamp (Local) Calendar Day Numeric Pointer Settings: Safety Interval Upper Limit Safety Interval Lower Limit Real-Time Enabled New Status for Changed Records Additive Delta
e.g. FI-GL Yes/No
e.g. LFN1
Yes/No
X
Yes/No X
Page 9 of 30
BI Technical Specification 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 Description Direct Access Delta Update Data Source for Reconciliation Field Short Text Name
0FI_GL_X General Ledger: Line Items with Delta Extraction 1 supported (without preaggregation) Yes/No Yes/No
BELNR
X
Accounting Doc. Number
Selection
Hide Field
Inversion
Field Only Known in Customer Exit
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 Type
Data Type
Length
Decimal
Description
Page 10 of 30
P o s . 1 2 3 4 5 6 7
BI Technical Specification LO Cockpit Enhancements (LBWE): For logistics extractors only, detail any enhancements or fields that are to be added to the extractor here. Data Source Extract Structure Update Mode Table MCEKET
Field
2LIS_02_SCL MC02M_0SCL Unserialized V3 Update Field BUKRS
Description 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. Description Exter Key Conv. Lower Format SS Curren Sele Selection Options nal Field Routines case Conv. cy / ction Lengt Routine Unit h
Page 11 of 30
BI Technical Specification
6.2 DSO/ODS Detail Specification Technical Name
Description
0FIGL_O10
General Ledger (New): Transaction Figures
Settings Type of DataSource Object SID Generation upon Activation Unique data records Activate Data Automatically Set Quality Status to ‘OK’ Automatically Update Data Automatically Partition Condition: InfoArea
Standard/ Write optimised / Direct update During Reporting/During Activation/Never Create SIDs Yes/No Yes/No Yes/No Yes/No 0FIGL_ERP
Key Fields InfoObject Description
Technical Name
Data Type
Length
Technical Name
Data Type
Length
Technical Name
Data Type
Length
Technical Name
Data Type
Length
Data Fields InfoObject Description
Navigation Attribute InfoObject Description
Indexes 010 InfoObject Description
Page 12 of 30
BI Technical Specification 020 InfoObject Description
Technical Name
Data Type
Length
Page 13 of 30
BI Technical Specification
Transformation Transformation Description Target of Transformation: Object Type: Name Source of Transformation: Object Type Name Rule Group:
TRCS ZFI_GL_10 -> ODSO 0FIGL_O10
Start Routine: Fields Source Field
0GL_ACCOUNT
Method ( Direct Assignment = D, Constant = C, Read Master Data = M, Read from DataStore = RD, Formula = F, Initial = I ,Time Characteristics = T , Routine = R D
Target InfoObject
Conversion Exit
Perform Conversion Exit (Y/N)
0GL_ACCOUNT
ALPHA
No
End Routine:
Field Routines: < Write a sample code for each Field Routine used in the Transformation >
InfoObject
Field Routine: InfoObject
Field Routine: InfoObject
Page 14 of 30
BI Technical Specification Field Routine:
Data Transfer Process Data Transfer Process ID
BWD BWQ BWP
DTP Type
0FI_GL_10 / ECDCLNT120 -> 0FIGL_O10 DTP_4M5BHAO1MYHF7A73Q5WKM8SIE Standard
Extraction: Source of DTP (Technical Name) Description Data Source Type Source System Extraction Mode: Only get delta once Get one request only Retrieve until no more new data Parallel Extraction (Y/N)
0FI_GL_10 General Ledger: Leading Ledger Balances Data Source ECDCLNT120/ECPCLNT300 Full/Delta
50,000 Package Size Filter Condition:
Field
From (or Variable) 0I_CUFQU
Fiscal year/period Fiscal 001.2011 year/period
Selection of Key Fields for Error Stack: Key Field Field Name
To (or Routine)
012.2011
Long Description
Update: DTP Data Target Description Data Target Type Error Handling: Maximum Number of error per pack No Update without Master
0FIGL_O10 General Ledger (New): Transaction Figures DSO Update Valid Records: No reporting (Request Red) 100 NO Page 15 of 30
BI Technical Specification Data:
Execute: Technical Request Status Overall Status of Request Processing mode: Automatically Repeat Red Requests in Process Chains (Y/N)
Request Status is set to ‘green’ if warnings occur Set Overall Status Automatically Serial Extraction, Immediate Parallel Processing No
Page 16 of 30
BI Technical Specification
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).
Technical Name
Description
0FIGL_C10
General Ledger (New): Transaction Figures
Settings Type SubType BWA Status InfoArea Partition Condition
Standard InfoCube No BWA Index 0FIGL_ERP 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
BI Technical Specification
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 property
Display
Selection
Query Execution Filter Value
Navigation Attribute InfoObject Description
Technical Name
Data Type
Length
Key Figures InfoObject Technical Data Length Type Cumulat Description Name Type ive (Y/N) Cumulative 0BALANCE CURR 09 Amount Y Balance
Aggreg. Sum
Except. Aggreg. Last
Unit 0CURR ENCY
Key Figure Structure specific property InfoObject
Description
Decimal places
Display
Page 18 of 30
BI Technical Specification
Transformation Transformation Description Target of Transformation: Object Type: Name Source of Transformation: Object Type Name Rule Group:
ODSO 0FIGL_O10 -> CUBE 0FIGL_C10 InfoCube DSO
Start Routine: Fields Source Field
0GL_ACCOUNT
Method ( Direct Assignment = D, Constant = C, Read Master Data = M, Read from DataStore = RD, Formula = F, Initial = I ,Time Characteristics = T , Routine = R D
Target InfoObject
Conversion Exit
Perform Conversion Exit (Y/N)
0GL_ACCOUNT
ALPHA
No
End Routine:
Field Routines: < Write a sample code for each Field Routine used in the Transformation >
InfoObject
Field Routine: InfoObject
Field Routine: InfoObject
Page 19 of 30
BI Technical Specification Field Routine:
Data Transfer Process Data Transfer Process ID
BWD BWQ BWP
DTP Type
0FIGL_O10 -> 0FIGL_C10 DTP_4KPUR0N8AZEZ8JEFHA14N13VY Standard
Extraction: Source of DTP (Technical Name) Description Data Source Type Source System Extraction Mode: Only get delta once Get one request only Retrieve until no more new data Parallel Extraction (Y/N) Package Size Filter Condition:
0FIGL_O10 General Ledger (New): Transaction Figures Data Store Object BW Full/Delta
Yes 50,000 Field
From (or Variable) 0I_CUFQU
Fiscal year/period Fiscal 001.2011 year/period
Selection of Key Fields for Error Stack: Key Field Field Name
To (or Routine)
012.2011
Long Description
Update: DTP Data Target Description Data Target Type Error Handling: Maximum Number of error per pack No Update without Master Data:
0FIGL_C10 General Ledger (New): Transaction Figures InfoCube No Update, No Reporting 100 NO
Page 20 of 30
BI Technical Specification Execute: Technical Request Status Overall Status of Request Processing mode: Automatically Repeat Red Requests in Process Chains (Y/N)
Request Status is set to ‘green’ if warnings occur Set Overall Status Automatically Serial Extraction, Immediate Parallel Processing No
Page 21 of 30
BI Technical Specification
6.4 MultiProvider Detailed Specification Technical Name
Technical Name
Description Relevant InfoProviders Description InfoProvider Type Cube/DSO/InfoObject/HybridProvider/ InfoSets/Aggregation Levels
Dimensions InfoObject Data Package
Time
0CHNGID
Description
Change run ID 0RECORDTP Record type 0REQUID Request ID 0FISCPER Fiscal Year / Period
Data Type NUMC
Length
Identify
14
NA
NUMC CHAR NUMC
01 30 07
NA NA 0FIA_DS11
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
BI Technical Specification
Dimension 9 Dimension A Dimension B Dimension C Dimension D
Structure Specific Property InfoObject
Description
Constant
Document property
Display
Selection
Query Execution Filter Value
Navigation Attribute InfoObject Description
Technical Name
Data Type
Length
Key Figures InfoObject Technical Description Name Cumulative Balance
Data Type
Length Type
0BALANCE CURR 09
Cumulat ive (Y/N)
Amount Y
Aggreg.
Except. Aggreg.
Unit
Sum
Last
0CURR ENCY
Select (Assign )
Key Figure Structure specific property InfoObject
Description
Decimal places
Display
Page 23 of 30
BI Technical Specification
6.5 Reporting Requirements Desired Layout Design TEXT TO BE REMOVED. GUIDANCE ONLY
example embedded into word, but you may also insert an excel file for larger reports> END OF GUIDANCE TEXT Example: G/L Account Tr Rcvbls Domestic Invt - Trading Gds Machinery & Equipmt Accum Dpr - M & E Tr Pybls - Domestic Sales Tax AR State Invt - Initial (Trd) Sales Rev Sales Rev Services Cost of Gds Sold Extraord Exp/Inc Overall Result
JAN 2010 0010/121000
FEB 2010
MAR 2010
Overall Result
$ 0.00
$ 0.00
$ 0.00
$ 0.00
0010/135075
$ 0.00
$ 0.00
$ 0.00
$ 0.00
0010/160020
$ 2,150.00
$ 0.00
$ 0.00
$ 2,150.00
0010/170020 0010/211000
-$ 179.17 $ 0.00
$ 0.00 $ 0.00
$ 0.00 $ 0.00
-$ 179.17 $ 0.00
0010/216100
$ 0.00
$ 0.00
$ 0.00
$ 0.00
0010/399175 0010/410000
$ 0.00 $ 0.00
$ 0.00 $ 0.00
$ 0.00 $ 0.00
$ 0.00 $ 0.00
0010/410010
$ 0.00
$ 0.00
$ 0.00
$ 0.00
0010/500000 0010/701000
$ 0.00 -$ 1,970.83 $ 0.00
$ 0.00 $ 0.00 $ 0.00
$ 0.00 $ 0.00 $ 0.00
$ 0.00 -$ 1,970.83 $ 0.00
Page 24 of 30
BI Technical Specification Report Structure TEXT TO BE REMOVED. GUIDANCE ONLY END OF GUIDANCE TEXT
Criteria (InfoObject Description)
Interactive Selection Criteria InfoObject Mandatory * Default (Technical or optional value Name)
1
Company Code
0COMP_CODE
Mandatory
2
Calendar Month
0CALMONTH
Optional
3
Profit Center Group
0PROFIT_CTR
Optional
Order on Screen
Criteria (InfoObject Description)
InfoObject (Technical Name)
Constant Values
Fiscal Year Variant Fiscal Year / Period
0FISCVARNT
Z1
Controlling Area
0CO_AREA
blank
Global Filters SAP/Customer EXIT Variable Description
0FISCPER
Selection Type (Single value, range, etc.)
Variable Technical Name
Multiple Selection Range
0P_COCD
Hierarchy Node
0H_PCTR
Variable’s Technical Name
0I_CLMTH
Selection Type (Single value, range, etc.) Single Value
Current Fiscal Year/Period 1000
0FPER
Single Value Single Value Authorization
Reporting Data-Provider (InfoProvider): Technical Name
Description
0FIGL_C10
General Ledger (New): Transaction Figures
Page 25 of 30
BI Technical Specification
Rows Technical Name
Description
Description in Query
Display As
Text View
Sort Characteristic
Sort by
Sort Direction
Result Rows
Hierarchy Display
0PROFIT_CTR
Profit Center
Standard / alternative
Key and Text
Short
0PROFIT_CTR
Text
Ascending
Always Display
Active
Expand To Level 2
Columns Technical Name
Description
Description in Query
Display As
Text View
0FISCPER
Standard
Text
Medium Length
ZRKFBLNCP
Fiscal Year / Period Plan
ZRKFBLNCA
Actual
0SALES
Sales for the Period Balance Variance
ZCK_BLNC_VAR
Sort Characteristi c 0FISCPER
Sort by
Sort Direction
Result Rows
Hierarchy Display
Key
Ascending
Always Display
Inactive
Plan Balance Actual Balance Sales for the Period
Expand To Level
Ascending
Free Characteristics (Drill-down characteristics) Technical Name
Description
Description in Query
Display As
Text View
0GL_ACCOUNT
GL Account
Standard
Medium Length
0COSTCENTER
Cost Center
Standard
Text and Key Text
Medium Length
Sort Characteristi c
Sort by
Sort Direction
Result Rows
Hierarchy Display
Key
Ascending
Never
Inactive
Always
Page 26 of 30
Expand To Level
BI Technical Specification Calculated Key Figures Technical Name
Determine Characteristic Assignment Individual Characteristics and char. Combinations
Characteristic 0GL_ACCOUNT 0COSTCENTER
Exceptions Exception Description
Alert Level
Operator
Values
Exception Defined On
Exception Defined On (in case of
Exception Affects Data Cells
Exception Affects Characteris
Page 27 of 30
BI Technical Specification
Exception 1
Exception Description Exception 1
Good 1
EQ
0
Critical 1 Bad 1
LT BT
5 [-5;5]
Exception Affects Everything X
Balance
two structures) All Structure Elements
tic Cells Balance
Cell Restrictions Exception Only Characteristic Affects Results
Rows
Operator
Value
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 Technical Name
Variable Description
Processing by
Variable Represents
Mandatory or optional
Exit (Y/N) if Y then STEP
Default (If so, at what value?)
0CRM_CRD_AT
ZABC
New Variable…
Manual Input/Authorization
Single Value
Mandatory
Y (1)
Sy-date
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
BI Technical Specification Technical Name
Name
Technical Name
1 2 3 4
8. Error Messages Describe the expected error messages (Monitor Screen) for different error conditions during data loads. Error Message Number 1. 2. 3.
Error Message Text (70 characters)
Error Conditions
Page 29 of 30
BI Technical Specification
9. Security Requirements/ Authorization Details TEXT TO BE REMOVED. GUIDANCE ONLY END OF GUIDANCE TEXT
10. Additional Information and attachments Document Name/Attachment
File location(If for common access)
Comments
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 END OF GUIDANCE TEXT
