Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Profile vs. User How many selections you can have in a structure
- Profile are collection of roles
- Roles are collection of authorization objects For naming Conventions
for the users (URL parameter)
o Helps user grouping
- User have atleast one role in SAP system Z consultant
to be activated Y customer
X not go to production system, only testing
RSECADMIN purpose
- Change of authorization BW cubes
Questions fromTextbook
How to improve query performance - Analysis system for Excel access via HANA
- Read Mode ( A X H) Local and Composite Providers
- Most optimized is X if you have hierarchy o Two additional
- A if few data Might be a question what is BW Workspace
- Default is A - Central infoprovider
- Helps BW consultant to merge different
Design Studio providers for special queries
- Options to save in DS application - Bridge gap for central requirement and
o BI Platform other local requirement
- Analytic View Transactional Data
Fiori Launch Pad - Calculation View view data from various
- Web Launchpad complex scenarios
- Allows mobile users to access tiles which -
connect to transaction or reports
Baseline Testing UAT Integration Testing
BOBJ Tools Package Regression Testing (Auditors) Live Production
RRMX
Authorization for InfoCube Subsets of Character Info Objects
- S_RS_iCube - Text
- Hierarchy
RFC - Attribute
- Connector between SAP Systems
BICS ( BI Consumer Services) Component for Historical Reporting
- Connector between BEx queries and BI - In dashboard
Reporting Tools
Purpose of embedded BW
Steps to Authorize an InfoObject in Info Users - Local Reporting
- RSA 1 - Easy Integration
- Business Exporer Tab
- Autorization Tab Optimal number of activated conditions in BEx
- Role assignment Query Designer
- SE01 as user
- PSCG to the user Number of conditions can we create in query
unlimited but recommend is 16
Solman
- PM BarChar, VarChar
Data: Raw
Information: Cleansed
ODP
- ODP BW
- Offers real time and near real time
- For real time extraction of data
- ODP SLT
o Unique way of performing
replication
SBIW: Generic or Custom Built DataSoURCE Full Load vs. Delta Load
- BW not yet recognize it, REPLICATE - Full Upload vs. Increment changes only
DATASOURCE updated
o ACTIVATED - Doing always Full Load is not best practices
- InfoPackage - Done in the InfoPackages
o Replicate from DS to BW - Full Load first before Delta Load
o Data Selection Tab
Individual selection of RSD1 : Open InfoObject Characteristic
InfoObject RSD2: Open Key Figure
o Extraction Tab RSD3: Time Measure
Adapter RSD4: Time
o Processing RSD5: Tech Characteristics
Only PSA
Older version, can upload up
to Cube] Transaction Data goes immediately to DSO
o Schedule Tab - Transaction data cant be processed
Start Data Load Immedietely InfoObjects since it can only process master
or later In background data.
- Transfer Rule (in the Context Menu) o DSO structure of a Table, rows and
o Mapping columns
Created before InfoPackage
Prerequisite of Creating SID Generation
InfoPackage is creating a - During activation, SID (Surrogate ID)
Transfer Rule to do the generation
mapping o For faster reporting but data loading
STEPS slower.
Load Data from Source o Vice Versa if this is disabled
Identify DS
Replicate DS to BW InfoObject Catalog
BW will know DS exist - Folder only for InfoObjects
DS Activated in BW
PSA Table is generated in PSA Area DataSource
Mapping(1st) to after DS goes to BW in Transfer - Extractor
Rule - Load data from Source to BW
Create InfoPackage - Extract Structure and Logic
Do Mapping in Transformation into Fields - Always originate from source system
Once Mapping is done, execute with DTP o Replicate
- Grouping of mapping rule, Rule Group o Activate (PSA in DS)
- Extraction Tab o Data is replicated into application
o W and component
- Update Tab - Create DataPackage from DataSOurce
o Target Object o Do the mapping
o Error Handling - Data is transferred from source to PSA
Whenever errors, what o Cant run report in PSA since its raw
system would happen data
- We create generic DataSource in SBIW
3 References only applicable in Generic DataSOure DataSource
(accessed by SBIW) - Generic datasource
- Extraction From Views o Extract view, query FM
- Extraction From Queries - Attibute to attibure, text to text
- Extraction by Functional Modules (FM) - Application components where
- datasources are stored
* 3 sources for creating a generic datasource - SAP, ODP, DS, Flat file, UD, DB,
- Datasources needed to be replicated to BW
Option to Create Views SE11 before
Master data is loaded in InfoObject XSL Type only used if BW will connect with
BigData
SID # is created when activation of InfoObject
Reporting
Reporting tool Connects to Analytical Engine - Designed to use InfoCube & MultiProvider
Checks SID Corresponding Master Data - DSO is not authorized by default since it is
in tabular format
Compounding
- Material-plant combination T-Code to Directly access In
ALPHA CONVERSION ROUTINE
- Master data has leading zeroes
Trasitive Attributes
- Provides multiple attributes in the master
data
- Business Partner (Customer, etc etc)
-
Reference InfoObject
Rule group
- Transformation settings in rule group
InnerJoin Intersection
Outer Join Union