Professional Documents
Culture Documents
Agenda ...
1. Start Up 2. Extraction 3. Data Model 4. Custom Hierarchies
Agenda ...
"There is no terror in the bang, only in the anticipation of it. - Alfred Hitchcock
1. Start Up
System Landscape Business Needs Data Design Business Content
5
System Landscape
System Landscape
Develop.
Current
Start Up
BW
2.0B
3.0B
R/3
Start Up
Plant Maintenance
Start Up
Standardized Yet Flexible Long Data Life for Trending Summary and Details Focus on:
Basic Purchasing Information Basic Stock Information Basic Material Movement Info Inventory by Vendor Inventory and Cost
8
Start Up
Data Design
Start Up
Inventory
Transfer BW: Stock (2LIS_40_S278) Material Movements (2LIS_03_BF)
Agenda ...
"Any sufficiently advanced technology is indistinguishable from magic. - Arthur C. Clarke
2. Extraction
Logistics Cockpit Process Keys DataSources
11
Logistics Cockpit
Logistics Cockpit
Transaction LBWE Set Update Mode for Entire Application Original Design & Construction Used V3 Update Chose Queued Delta When Made Available in PI 2002.1
12
Extraction
Process Keys
R/3 Applications Create Many Key Figures Process Keys Are Assigned Based on the Business Process in Logistics Extractors
Extraction
Process Keys
Generic Key Figures (Value & Quantity) In BW, Process Keys Make Transaction Key Figures Meaningful Process Keys Must Be Activated Via R/3 Transaction MCB_
- Extensive Reference White Paper from SAP Service Marketplace, Business Content 2.0B - Retail/CP
13
Extraction
Process Keys
Process Key = 1 (Purchase Order) Generic Key Figure Value = 4,000.00 (PO Value) Generic Key Figure Quantity = 40.000 (PO Qty)
14
Extraction
Process Keys
Process Key = 2 (Goods Receipt) Generic Key Figure Value = 4,000.00 (PO Receipt Value) Generic Key Figure Quantity = 40.000 (PO Receipt Qty)
15
Illustration
Process Key 001 Characteristics Value 100.00 Quantity 1
Characteristics
Value 100.00
Quantity 1
R/3
Extraction
Process Keys
BW
Generic Key Figures
Process Key 001 Process Key 002 Characteristics Value 100.00 Value 100.00 Quantity 1
PSA
Characteristics Quantity 1
Characteristics
PO Value $100.00
PO Quantity 1
PO Data Target
16
Extraction
Process Keys
17
DataSource Overview
Purchasing
Purchasing Schedule Line (2LIS_02_SCL) MRO PO Data (Custom)
Additional Fields Specific to MRO Only Transparent Table Populated by ABAP
Extraction
DataSources
Extending 2LIS_03_BF
Execute RMCSBWCC to Check for Possible Errors
Normal Errors Include Data in Setup Tables or Delta Q Resolve Errors (Delete Setup Tables, Process Deltas)
Extraction
DataSources
Add User Exit to Populate New Fields Via RSA6 Function Enhancement or CMOD
Create Project (EG: ZBW) Enhancement Assignment RSAP0001 Component EXIT_SAPLRSAP_001 (Transaction)
19
Extraction
DataSources
This Must Be a CASE Structure The Exit Is Executed for Every DataSource
(See Notes For Code)
20
Agenda ...
"To the man who only has a hammer in the toolkit, every problem looks like a nail. - Abraham Maslow
3. Data Model
Corporate ODS Layer and Data Marts Purchasing Schedule Line Material Movements and Stocks
21
Strategy ...
Corporate ODS Layer & Data Marts
Data Model
Data Marts
22
Data Model
Attributes
Historical Foundation One DataSource : One Data Target Isolated Special Business Knowledge Always Archived With Longest Retention Period Cleansing & Transformation In PSA & Update Rules Comprehensive Data Storage Atomic Level Of Detail In ODS Objects
23
Data Model
Data Consistency
Single Origin & Reduced Ambiguity
Historical Foundation
Trusted Source Across Application Areas
Data Mart
Application-Specific Business Facts Subset Of Corporate ODS Layer Used For Data Consolidation & User Reporting
Data Model
Data Model
Agility
Easier To Modify
Flexibility
Departmental Interpretation Of Facts
Scalability
As Much Or As Little Data As Needed
26
Multi-Level Model
Corporate ODS Layer & Data Marts ODS Key Design
Corp. ODS Layer: Enables Transactional Uniqueness Reporting: Determines Level Of Detail
Data Model
ODS Facts
BEx Reporting Flag Only Set For Report Level Automatic Activation Flag Is Not Set Automatic Data Target Update Flag Is Not Set Quality Flag Is Always Set All ODS Updates Are Overwrite
28
Usually Filter Between Corporate ODS & Data Mart Custom Extractor Selection & Filter Criteria Identical Filters: Update Rule Start Routine Executed Just Before Updates Applies to Entire Data Package
Data Model
29
Purchasing
Reporting Consolidation & Transformation
Data Model
Purchasing
MRO Combined Standard Purchasing Schedule Line Data + Custom Characteristics All Purchasing Schedule Line Transactions MRO Custom Characteristics
Purchasing Filters
Between ODS 3 & ODS 4
Keep Purchase Order Entry Transactions (Process Keys 1, 4, 11, 14, 21, 24)
Data Model
Purchasing
31
Data Model
3 Purchasing
Purchase Document Number Item Number of Purchasing Document Schedule Line Number Process Key
32
Data Model
Purchasing
1
Situation No Actual Process Key from Custom DataSource for ODS2. Dummy Process Key set to 999 in Transfer Rules.
(See Notes For Code)
33
Data Model
Data Model
35
Data Model
Keys For All ODSs Document Number Document Year Document Item Stock Type Process Key Remains Unique With These Keys
Data Model
Data Model
Data Model
39
Data Model
Outflow (Issues)
Non-Cumulative (Stock)
40
Data Model
Data Model
Quantity Received To Consignment Stock Quantity & Value Received to Valuated Stock
Data Model
Stock Levels - Close of Business Day No Movements for Remainder of Day Several Hours - Plan Ahead 2LIS_03_BF Deltas After Activation Delta Queue Job Must Wait BW Deltas Must Wait Minimize Impacts (Queued Delta)
(See Notes For Details)
43
Data Model
44
Data Model
Update ODS2 from ODS 1 (Initial) Update ODS3 & InfoCube from ODS2 (Initial) Compress InfoCube -- No Marker Update
Rolls Back Stock Level Updates From History
(See Notes For Details)
45
Agenda ...
"I have not failed. I've just found 10,000 ways that don't work. - Thomas Edison
4. Custom Hierarchies
Why a Custom Hierarchy? The Solution InfoRec Vendor Hierarchy
46
Situation Material Activity by Supplying Vendor Vendors Supply Many Materials Any Material Supplied by Several Vendors How Does BW Represent Many-To-Many? Hierarchies What If It Isnt in Business Content? Create a Custom Hierarchy!
47
The Solution
Custom Hierarchies
The Solution
Create a Hierarchy of Vendor/Material Use Level 1 (Vendor) as Query Filter Create an R/3 ABAP to Extract the Data Hierarchy Flat File Extract Layout
Record Number; Node Name; (Characteristic Name) Node Value ; (Characteristic Key) Blank; Parent Node Record Number
Example:
1;0HIER_NODE;VENDORS; ;0 2;0VENDOR;123456 ; ;1 3;0MATERIAL;MRO12345 ; ;2 4;0MATERIAL;MRO67890 ; ;2
Custom Hierarchies
Construction Steps
Create ZMROMATL w/ Hier
InfoRec Vendor
Create ZMROVEND Create & Activate Hierarchy Load Texts for ZMROMATL Load Texts for ZMROVEND Create an InfoSource for the Hierarchy Execute ABAP to Extract the InfoRec Relationship Load & Activate the Hierarchy
49
Closing Thoughts
Ideas are like rabbits. You get a couple, learn how to handle them, and pretty soon you have a dozen. -- John Steinbeck
50
Key Topics
Corporate ODS Layer + Data Marts Multi-Level ODS Model Process Keys Purchasing Schedule Line Material Movements & Stocks Non-Cumulative Key Figures Custom Hierarchies
51