1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 TBW10 - Data warehousing
43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81
82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
In SAP BW star Schema, The fact tables are referred to as Key Figures and the dimension attributes as Characteristics.
Master data information is stored in master data tables seperately for Attributes, Hierarchies and Texts and not in Dimensions. The SID tables connect master data tables to dimension tables in a Basic Cube.
It is not possible to create your own TIME characteristics.
Time characteristic with largest granularity is Calendar Day and smallest Granularity is Fiscal Year 0REQUID delivers the number the system allocated when loading requests.
0CHNGID delivers the number allocated during the aggregate change runs.
Display attributes can only be used as additionl information in reporting. i.e you cannot navigate with in the data set of a data target. The extensive use of navigational attributes leads to large number of tables and joins which reduce performance.
A Characteristic that is used as a navigation attribute, can also have its own navigational attibutes. These are called Transitive Attributes. You cannot create Hierarchies for characteristics that are referred to other characteristics.
Hierarchies can have a maximum of 98 levels.
Performance can be affected when compounded characteristics are used extensively, particularly when large number of characteristics are included in the compounding.
If a key figure is created with reference the additional tab page Elimination appears in the Infoobject maintenance. A Basic Cube consists of precisely one Fact table and Fact Table contain 233 Key figures.
A Basic Cube usually has 4 dimension tables. Units, Data Package, Time and Other Dimension
Data Package and Time Dimension exists always but Unit dimension only exists if atleast one key figure of type AMOUNT, QUANTITY exists. A maximum of 248 characteristics can be combined with in a dimension.
A Transactional Infocube is a special cube designed for SEM. The data is written to the Infocube from more than one users at a time and instantly read again when required.
A Text table is created when flagged the With Texts check box. Only one Text table is generated for each characteristic.
Text Table - T
Attribute Table + Not Time Dependent - P Attribute Table + Time Dependent - Q Hierarchies - H table
SID Table - S table
X table is generated when atleast one attribute is declared as Time Dependent Navigational Y table is generated when atleast one attribute is declared as Time Independent Navigational Each Basic cube generated 2 table F, E. After activation both have same columns.
There are 2 transfer methods. IDOC method and PSA transfer method.
With IDOC methood, IDOC interface technology is used to pack the data into IDOC containers.
With PSA, IDOC containers are not used, instead the data is tranferred directly in the form of Transfer Structure. The information is send from Source system by IDOC (Info IDOCS - information like No of data records etc)
Transfer rules transfer data from several transfer structures into a single communication structure.
Data Sources are used to transfer Master Data and Transaction Data. Extract Structure and Transfer Structure are two field structures. When a Data Source is replicated, fields from extract structure are used as an template to create the Transer structure in BW.
When the local transfer rules are activated, the Transfer structure is generated in both BW and SAP System. The fields in a communication structure can be assigned a CONSTANT
Transfer Structure is source system dependent Communication Structure is Target dependent.
Infosource with Flexible Update - Update rules are used to load the data from communication structure to data targets.
Infosource with Direct Update - The communication structure is used directly to update master data(Characteristics with Text, Attributes and Hierarchies) In performance view, uploading data from an ASCII file is more effective.
The sequence of column in communication structure does not have to correspond to the sequence of the columns in your flat file. The sequence of column in Transfer structure have to correspond to the sequence of the columns in your flat file.
Business content objects are delivered in D - Delivered Version, - Object exists but cannot be used
Active Version - A , Modified Version - M - active business content is changed. This overwrites the active older version and the ACTIVE version is not over written with a new release
BW Statistics is a tool for the analysis and optimization of business information warehouse processes. The information is provided by a Multi provider 0BWTC_C10.
BW Data Slice contains information about which characteristic combination of an infocube are to be loaded and with which request. This Infocube is filled from the selection conditions for the respective Infopackage.
Activating Technical content Role in Business content also activates all the required dependent objects for BW statistics.
The structure of the PSA tables corresponds to the Transfer structure and contains additional fields. If the transfer structure is changed, the system creates a new version of PSA table.
PSA table is based in the transfer structure and contains the key fields of the request number, datapackage number, and data record number. PSA table is partitioned dynamically by request number, hence increased performance during data load and also on deletion layer.
The BW uses the InfoIDOC to generate the traffic light indicators in the monitor.
A DataIDOC consists of a control record(ex: sender, reciever…), data record and a status record (Ex: Processed…). Netweaver provides an open integration platform and permits the integration of the Enterprise services architecture. SAP BW meta objects and their links are managed centrally in the HTML based SAP BW metadata repository.
Infoobjects are smallest available information modules. As a component of metadata repository contain the Master data and Transaction data InfoObjects are used to create structures and tables, and also used in the definition of reports to evaluate master and Transaction data. Unit Info objects can be specified along side the key figures.
Transaction RSD1 and RSD5 allows you to create objects (KF and CHAR) with out them being assigned to Infoobject catalogs. CHANOTASSIGNED and KEYNOT ASSIGNED are the infoobject catalogs under the NODESNOTCONNECTED infoarea.
When an Infoobject catalog is deleted, the infoobjects are not deleted and instead move to the CHANOTASSIGNED or KEYNOTASSIGNED.
While creating an Infoobject, if you use the option USE TEMPLATE, the characteristic assumes this characteristic properties and then an be edited. While creating an Infoobject, if you use the option REFERENCE, the new char assumes all properties. You can only edit the Technical properties. A maximum of 2 attribute tables can be created for a display attribute (Time Dependent and Time Independent).
Only one H table is created even if a characteristic contains several Hierarchies. The S(SID) table is created when a characteristic is activated.
The Key to the X & Y tables of the Navigation attribute is the SID of the SID table. After the Basic cube is activated the Dimension tables are created.
The structure of dimension table consists of a DIM ID column and of up to 248 SID columns.
The F table is always optimized for data loading, since the data is always automatically partitioned using the package dimension table. The E table is optimized for data requests.
LISTSCHEMA shows you tables for the structure of Infocube. You can display the attribute tables for the characteristics involved in the Cube. The text, Hierarchy and E tables are not displayed.
For each source system one Infosource can be assigned to a data source
With the Transfer rules, you determine which infoobjects from the communication structure are filled from which Transfer structure fields and which method is used. You have 1:1 update, Constant, Global Routine, Formula.
It is not possible to use an Infoobject as an Infosource with direct updating when a. The 0SOURCESYSTEM characteristic is involved.
b. The characteristic has no master data, Text or Hierarchy data c. A characteristic is not involved rather a unit or key figure. XML data is first made available to BW system via the SOAP.
The SOAP file is generated from the external application,and the XML data is analysed and parsed and written to the Delta Queue in SAP BW , and then data is extracted from the Delta Queue and then updated further.
Using UDCONNECT, you can access all relational and Multi Dimensional data sources. UDCONNECT transfer the data as Flat Data. Multi Dimensional data is converted into FLAT data when UD Connect is used.
You cannot create a Direct update Infosource on a Infoobject which has been created by refering other Infoobjects ( By Test)
In the PSA and Data Target in Parallel option: A dialog process is started by a data package, in which the data is written to PSA and on confirmation a second dialog process is started to update the data target. A second package to the first dialog process is being posted while the first package to the second process is being updated.
In the PSA and then Data Target option: Only one dialog process is used, First to update the PSA and then the Data Target. You can use the Selective Deletion to delete from a Basic Cube.
During the Extraction process, the Data requested for each request is taken from the source system and put into the packages with in the request before being loaded into SAP BW
When a Query is run , the data packages with Red or Yellow status cannot be included and any data packages loaded subsequently successfully can not be included as the consistency is not guaranteed.
If active aggregates containing data exists for the basic cube and you load a new request into basic cube, you need to rollup these new requests in aggregates as well.
When a basic cube is compressed, the data records are written to the E table of the basic cube and compressed requests are removed from the F table. The disadvantage of Compressing basic cube is that the request id cannot be used to delete the compressed data. The data can only be deleted by Selective Deletion or Delete completely. For performance gain SAP recomends compression.
Use the Reconstruct function to restore requests that have been rolled up into the basic cube and sub sequently deleted, only when data is stored in PSA. An Aggregate is build from the characteristic and navigation attributes in a basic cube.
Both time dependent attributes and time dependent Hierarchies can be used in Hierarchies. A Basic cube can containmore than one aggregate.
The process of OLAP processor selecting the aggregates depending on the query is exception for a aggregation Hierarchy. Aggregates are defined as
a. * - Inclusive , The characteristic is used in the summirization. b. ' ' - Exclusive, the characteristic is not used in the summrization. c. F - Inclusive with a fixed value of the Characteristic.
d. H - The characteristic is summarized for a specific Hierarchy level. Refer Page 317 of TBW10 Aggregates have Technical, Content and Status properties stored in RSDDAGGRDIR table.
If basic cube uses a key figure for which an exception aggregation has been defined, the characteristic has to be included in an aggregate and defined as * The combination of structurally time dependent Hierarchy and Time dependent characteristic is not possible.
Each Aggregate consists of two fact tables F and E and atleast two dimensions ( Package and Customer defined), Unit dimension is not must. The Technical construction of an Aggregate is different from a cube as
a. If upto 15 characterstics are included in an Aggregate, BW does not create a real dimension, a line item dimension is created called as Flat aggregates b. If above 15 characteristics- If 2 or more chars come from one dimension in the Basic cube, the DIM ID of the basic cube is stored as a key in Fact c. If above 15 chars - if one char comes from one dimension in the basic cube, the SID is stored as a key in the fact table.
ROLLUP is the process of loading the data into aggregates. This happens when the Basic cube request is loaded into the aggregates. The structure of Basic Cubes and ODS objects and chars must be available in the target BW before the data loading process.
Transactional ODS are available for reporting after you define an Infoset on them. Queries can be based on the Infosets.
The Requests to be deleted from the ODS have not been activated yet, The requests are simply deleted from the activation queue during deletion. If activated, all other PSA requests that are contained in the same change log request mus be deleted.
All the requets that are activated after the request that was to be deleted must also be deleted from the ODS object. Selective Deletion only has effect on the tables with the active data.
Repair request is a full upload.
A SAP Remote cube allows you to define queries with direct access to Transaction data in other SAP systems.
General remote cube alows reporting using data from non SAP systems. The external systems transfers the requested data to the OLAP processor via BAPI. Virutal infocube with service uses a user defined function module as the data source.
In SAP Remotecube, same extractors are used to select data in the source system that are also used when replicating the data into the BW. The characteristic selection and selection criteria are transformed to fields in transfer structure and are transferred to extractors.
The delivered data sets run through the transfer rules in BW and are filtered once again in the query.
Prerequisites: Must make sure that master data and Hierarchies are already in SAP BW when executing the query as they are not directly read by source system.
The source system ID must have been created for the source system in SAP BW.
Data sources from the source system must have been assigned to the infosource of the SAP remote cube
Can check if data source is released for direct access using SE16, in the ROOSOURCE table for VIRTCUBE fields values 1 or 2
When characteristic values are selected in the query using a remote cube, BW reverses the transfer rules and sends to the source system.
A virtual infocube with services can be used when data from non BW data sources is to be displayed in BW with out copying the data set in BW structure. An exception aggregation is an aggregate which you don’t want be in the aggregates and used in the reports.
The OLAP processor calculates the exception aggregation values.
cumulative storage doesn’t have any impact on the storage of the data in the Cube
Non Cumulative values have an impact on the storage of the values in the cube. It stores according to the vaue specified in the Exception Aggregation. You can make the following changes to a characteristic after master data has been loaded:
Time Independent Display attribute - Time Independent navigational Attribute Time Independent Display Attribute - Time Dependent Navigational Attribute. Time Independent Display Attribute - Time Dependent Display Attribute. Time Dependent Display attribute - Time dependent Navigational Attribute.
PSA table contains the Request Number, Data Package Number, Data Record Number, and the fields in the Transfer Structure Aggregates can be created for Characteristics, Attributes and Hierarchies.
You can use a Key figure as an Attribute only.
With One exception, the S table is generated when a characteristic is activated. The one exception occurs when a characteristic is defined exclusively as an attribute.
If you enhance the structure of the master data carrying characteristics after loading master data, you cannot delete fields of structure containing data,unless you delete the exisiting data.
If you want to remove time dependency of a display attribute, you must first delete the content of the table for the characteristic. Navigational Attributes enable you to view current data with past characteristic values and vice versa.
TB
W
20
1 Bex allows a wide spectrum of users to access information in SAP BW.
2 You can select a filter value directly from the results area of an executed report using Keep Filter Value
3 you can select one or more values from the value set. You can select filter values for characteristics using value selection in Bex by select Filter Value
4
You can sort specified values in ascending or descending order by selecting the hyperlink that has the name of the characteristic or structure. First click in
Ascending and second click in descending
5 Filter and Drill Down to set a characteristic at a certain value and at the same time drill down by a different characteristic on the same axis.
6 Fix Filter Value to Axis ,when want to see data for one characteristic value and want the characteristic value to continue to appear in the Drill Down
7 Goto function to reach documents and other targets using report / report interfaces.
8 Goto Display document on key figure reach the documents that correspond to the cell selection
9 Goto Display Document reach document in the master data area of the characteristic value.
10 Goto Document for Navigation Status reach documents that correspond to the selection cell.
11 You need SAP Internet Transaction server and the SAP GUI for HTML in all SAP systems in which you wish to call up transactions over the web.
12 You can export the query data to Microsoft Excel 2000 - forward
13 You can call the Currency Translation dialog box to determine the currency into which the key figure or a structural component of a query convert
14
The three places where you can all up a context menu with in the results of a report are: On the Name of the characteristic, On the Key value of the
Characteristic, On the name of the characteristic, on a key figure.
15 Conditions have no influence on results rows. The results row corresponds to the result row in the table without this condition.
16 Exception reporting allows you to determine critical objects in a query in your Web application.
17 You can activate the Hierarchy itself from the properties screen that you call up from the context menu for the characteristic.
18 To Use Drag & Relate with in BW unifier, you need SAP Enterprise portal 5.0, SAP BW 3.0, SAP BW Unifier
19 Bex Browser allows you to access all documents types of the BW that are assigned to your Role or stored in your Favourites
20 The term Role was called Activity Group in 2.0A and Channel in 1.2B
21 The Role display in the SAP Easy Access menu can be switched ON and OFF
22 You can manage any kind of file in the Bex Browser. These files are then stored in Business Document Service
23 A maximum of 32 folder symbols can be uploaded
24 You cannot transport folder symbols between BW systems. Upload the folder system to all BW Systems.
25 You cannot reposition folder and objects using Drag & Drop
26 In MetaData Repository you can display the definition of all active objects that are delivered in Business content as well as link to the other objects.
27 You can activate a query in the Business Content and then go on to execute it in the Query designer.
28 You use the Metadata Repository as an information source hat allows you to obtain an overview of delivered objects
29 Business Content has the advantage that all necessary and related objects can be activated at the same time.
30 Define Cell function is only available for the queries with two structures
31 With Define cell you can control the values of the cell at the intersection of the structural components
32
Free Characteristics do not display in the initial view of the results when you execute the query. You can integrate these characteristics into the results
using navigation steps
33 You can use the free characteristics for selecting the filter values in the report
34 Change Query Global Definition can change the query definition
35 Change Query Local View correspond to navigation in the report and are not saved in the Query definition
36 If you are in Change Query Local View , you can switch directly to the global definition by choosing Change Query Global Definition.
37 InfoProviders are objects for which you can create and execute queries in SAP BW.
38 Data Targets are the objects which have their own data store.
39
Characteristic InfoObjects have to be included in the InfoProvider tree in the AWB to make them available as Data Targets for Flexible updates and as
Infoproviders for Reporting.
40 ODS Objects are available for Transaction Data and Master Data.
41 Multiproviders combines data from several infoproviders and makes it available for use in reporting.
42 Multiproviders are based on a Union connection unlike joins in BW Infosets (Intersection).
43
The System generates the Key Figure Number of Records (1ROWCOUNT) for the characteristic infoproviders and for ODS objects and places them in
key Figures Folder.
44 For ODS Object the dimensions are Data Part and Key Part.
45
Two dimensions are provided for each Infoprovider in the Infoset. Attribute and Key part. Hence for an infosset composed of an ODS object connected to
a Characteristic, Four dimension display.
46 You can Stucture BW Infosets only from ODS Objects and or Character Info Objects.
47 Restricted Key Figures created a InfoProvider level, you are then able to reuse the Individual key figures in other reports.
48 Restricted Key Figures are key figures of InfoProvider that are restricted by one or more Characteristic selections.
49
The Key figure that is restricted by one or more characteristic selections can be a basic key figure , Calculated Key figure or a key figure that is already
restricted.
50
Unlike a filter whose restrictions are valid for entire query, for a Restricted key figure , only the key figure in question is restricted to its allocated
characteristic value.
51 RKF can be created at the Infoprovder level or Locally in the Query definition.
52
Constant Selection function allows you to mark a defined selection as being constant. Navigation and Filter no longer have an effect on selection in
question.
53 Constant selection allows you to select reference variables that does not change at the report run time.
54 Percentage Variance - PSV % ASV gives the percentage by which the ASV exceeds the PSV
55 Percentage Share - SV %A IC gives the percentage share of SV made up of IC.
56 Percentage Share Result - %CT SV gives the share of SV of each characteristic value.
57 Percentage Share of Overall Result - %GT SV gives the share to the overall result.
58 NDIV(Expr) - Delivers 0 if the expr gives a division by 0 in the calculation, otherwise is the result of the expression.
59 Result delivers the result of the operand in all rows or columns.
60 Overall Result delivers result of the operand
61 Calculated key Figures can be defined at both the Infoprovider level and Query Level.
62 Formula Collision can occur in the interfaces of the two formulas.
63 Boolean Operator - Costs < Sales Volume delivers 1 if true else delivers 0.
64 Formula Collsion function only displays in the properties dialog box if two structures are used in the query definition and both contain formulas.
65 Reusable Structures can be used in several queries for the same Infoprovider.
66
To Make local changes in a particular query you can choose Remove Reference in the context menu for the structure, and there by change Reusable to
Local.
67
A maximum of 2 structures can be defined in a query definition. One of these can contain Key figures. You use characteristic values in one and figures in
other structure.
68 In the Characteristics properties dialog box you can make settings for a range of functions that affect the key figures for this characteristic.
69 Display of Results - Determine whether rows are displayed always, never or With only one value.
70
Display of Results - Normalize To - When values are normalized, key figure displays as a percentage of chosen result. Charactertistic is normalized only if it
is in the Drill Down.
71 You cannot use the attribute that you have selected for Sorting in the display.
72
Can show the Display attributes in the report in drill down, but Navigation steps are not possible. - Cannot choose values from a display attribute as a
filter.
73
In order to use an attribute as an Navigation attribute, You have to flag the attribute as Navigation attribute in the Info Object Maintenance of the
characteristic.
74 In order to use an attribute as an Navigation attribute, select that attribute from the list of possible navigation attributes in Infocube maintenance.
75 You can display the characteristics included in the query definition as a hierarchy.
76 You can select an external hierarchy as a display heriarchy for a characteristic in the query definition.
77
You can display characteristics and key figures in the rows and in the columns as Hierarchies by selecting Display as Hierarchy from the context menu
of row or column header.
78 You can override the hierarchy properties in the query definition.
79 You can use Hierarchies to select the filter values for characteristics by selecting individual Hierarchy nodes.
80 Can Combine Hierarchy, structures in the display so that you can choose to display the characteristc in Non Hierarchical form and Hierarchical form
81 If Hierarchy and Structure combined but donot choose Display as Hierarchy, a Column and Row are used for both hierarchy and structure.
82 With the Hierarchy display, Hierarchy appears with a structure in a column or row.
83 To Create Hierarchies, In the Infoobeject maintenance for the characteristic concerned you have to set the With Hierarchies indicator
84 Leaves contain the characteristic values for the basic characteristics and cam therefor have entries in the Fact table.
85 Intervals contain a number of leaves that belong together described as Upper and Lower Limit.
86 Can create a hierarchy only for those characteristic that do not relate to another characteristic.
87 Hierarchy nodes appear twice in the Hierarchy when nodes that have the same Technical key and that appear more than once are leaves.
88
When Leaves are not attached to the same super ordinate, you can either set the nodes as Link Nodes or make the hierarchy structure as Time
Dependent.
89 Use Link nodes to include a subtree in a hierarchy more than once.
90 Link node is only a link to the original node that you cannot change independently.
91 Variables are query parameters that you define in the query designer and that are filled with values only when query is executed.
92 Variables act as placeholders for Characteristic values, Hierarchies, Hierarchy nodes, Texts and formula elements
93 Variables are Reusable objects
94 Variables donot depend on Infoprovider, but rather on the Infoobjects for which they are created.
95
If you are using variables when making interval selections, you can swap the limits by highlighting the relevant variables by choosing Swap Interval
Limits.
96 variable processing Types - User Entry / Default Value, Replacement Path, Authorization, Customer exit, SAP exit.
97 User Entry / Default value - can manually enter the required value for the variable in a dialog box when query executed.
98 Replacement Path - Enables you to specify the value that automatically replaces the variable when the query or web application is executed.
99 Authorization - Enables you to fill the variables automatically with the values from the Authorization of the user.
100 Customer Exit - Enables you to determine values for variables by means of a function module exit.
101 SAP Exit - is contained in variables that are delivered with SAP BW business content.
102 For Metadata, Master Data and Transaction data you can define and even link one or more documents in various formats, versions and languages.
103 You can store the individual files either on SAP database or an external content server using an HTTP interface.
104
To Link one document from any document calss to another document with out actually linking physically you have to save both documents in a format that
supports hyperlinks such as HTML, MS Word and MS Excel.
105 You can define documents for BW objects - Infoobjects, Infocube, Infoset, ODS object, Query.
106 The functions in the Exception reporting enables you to select and higlight unusual deviations of key figures in a query.
107 An apostrophe after a value means multiple by 1000, two apostrophe means multiply by Million, three apostrpohe means multiply by Billion - 1' = 1000.
108 You can assign your own color symbols. Choose format -> patterns
109 You have to list all characteristics that you defined in the cell restrictions in the drill down of the report to take exception effect.
110
You can define several exceptions on a query for different value assignment. If the threshold value ares overlap when you activate several exceptions, the
worst (Highest) alert level counts.
111 You can delete a condition from the context menu if you create the condition in the web application itself.
112
In Adhoc Query Designer you cannot use variables in the query definition, Only one structure can be used for key figures in rows or columns, cannot
create reusable structures, reusable restricted key figures or reusable calcualted key figures.
113
Pre calculated Web Queries make the results available and hence end users donot have to wait long time when they execute the report and can
analyze the results immediately.
114 The Disadvantage of this approach is query result is determined at the time of precalculation and thus current state of the data is not shown.
115 The access time is significantly reduced with the precalculated web templates(PCWT) with out having to execute the OLAP query.
116
By using the PCWT, the data is not requested at the run time of the query by OLAP,instead requested only by HTML enabled portion of query to be
produced.
117
PCWT uses the document and content management service of SAP content management framework for the administration of HTML and related MIME
documents.
118 The optional parameter DATA_MODE determines the data mode that is used when the web templates are called.
119 This Parameter also specifies whether the PCWT is executed in the background or whether just the HTML options are accessed.
120 If the DATA_MODE is not indicated, data access is given to the OLAP processor which reads the current data.
121 To call a web template with a certain mode, you must extend the URL produced by the Bex Web Application designer to include the parameter.
122 DATA_MODE = STORED - The system accesses the pre calcualted data exclusively, If no data available you will receive an error message.
123
DATA_MODE = HYBRID - The system uses the precalculated data. If no precalculated data presents the system request current data as in NEW mode
from OLAP.
124 DATA_MODE = STATIC - The system will access available pre calculated HTML options, If no data you will receive an error message.
125
DATA_MODE = STATIC_HYBRID - The System uses the Precalcualted HTML options. If no precalculated HTML are present the system looks to STORED
mode precalculation data. If no precalculated data is present, the system requests current data in new mode from the OLAP.
126
Control query is an auxillary query which is implemented before the queries is web template. The result of the control query is used to set parameter for
web template.
127 Control query is recommended if you have several computed web templates which differ only by filter values in one step.
128 Implement pre calcualted values when - with target group analyses because you assign a fixed value.
129 Implement pre calcualted values when - with complex selections to improve query performance
130 Implement pre calcualted values when - in place of variables which are filtered from a query result
131 The query must serve as a characteristic for that variable or as a substitute. The characteristic must be included in the result query.
132
SAP Enterprise portal(SAP-EP) enables you to access applications from other systems and sources such as internet or Intranet to reach both structured
and Uncsturctured information.
133 Can use iView concept to integrate SAP BW applications and bring individual web applications from SAP BW as iview into SAP -EP
135 With Drag & Relate you can link data together across system boundaries in order to obtain additional information.
136
The Portal content studio provides a central environment for developing and managing different types of portal content such as iViews, pages, layouts,
roles.
137 Worksets let you bundle iViews and pages in folder hierarchies like for roles. Worksets represent generic, reuable structures.
138
Portal Content Directory (PCD) is the central storage mechanism of the portal. It stores data from portal content objects such as roles, pages,
worksets..
139 You can also generate links in knowledge management in the portal roles view.
140
If you select a folder below knowledge management(KM) navigation iViews, this folder becomes a folder in KM and the system generates a link in
knowledge management
141 The Objects from ABAP based systems do not need any post processing in the portal. They are converted to portal objects when they are uploaded.
142
If you are publishing iViews in the enterprise portal using the Bex Web Application designer or Bex query designer, these iViews are Drag & Relate target
objects by default and can therefor be selected as targets in other iViews.
143 Drag & Relate function does not replace the report - Report Interface (RRI) function.
144
Bex Information Broadcasting allows you to make objects with business intelligence contents available to a wide spectrum of users according to
requirement.
145 Use Bex broadcaster to precalculate Bex web applications, queries and workbooks and publish them in SAP-EP or distribute them by e-mail.
146 If an e-mail address for a user you have specified under user in role has not been maintained in user maintenance, user will not receive the file by e-mail.
147 Instead user gets a messagein the business work place.
148
Transfer Navigational state means the system generates a bookmark with out data and then takes this bookmark into account when it generates
precalculated documents or the online link.
149
If you have selected
Online Link to current data
as the output format, the variable assignment is attached to the URL.When the reciepent calls up online
link, the query or web application is started with these variable values.
150 With the help of RRI user can jump from a report into another report in order to get detailed information aboout an item.
151 With RRI, you can link reports containing different characteristics of an application. This makes it possible to report on more objects.
152 With RRI, connect reports that were created in different application classes.
153 Bex Maps can be used to visualize economic connections and distributions.
154 Maps of different degress of detail can be layered on top of each other by different levels of characteristic values.
155
Bex Map advantages - Complete integration with SAP BW, Linkage of geographic analysis with SAP BW functions, Execution of Bex Maps in queries
possible after maintenance.
156 There are four types of Geo-Characteristics - Static, Dynamic, Dynamic with values as attributes and Static with geo characteristics.
157 Static geo Characteristics - Characteristics that do not change over a long period of time (Ex: Country, State, region ..)
158 Dynamic geo Characteristics - Characteristic that are subject to change (Ex: Customer, Sales Office..)
159
Dynamic geo characteristic with values as Attributes - characteristic subject to change and whose geo coordinates are derived from a referenced static geo
characteristic with geo attributes. (Ex:Customer referenced with postal code)
160
Static geo Characteristics with geo attributes - Static geo characterstic are enhanced with geo coordinates to determine geographic location.(Ex: postal
Code).
161
Under any circumstances do not change the order of the entries in the attribute table, for ex: sorting, deleting. If you change the order the attribute table
would no longer agree the index and the geometry files.
162
You can use a Query in the web Application designer as a data provider for Web Items and in a tabular display in crystal reports as a data source for
formatted reports.
164 4 Dimensions are displayed if you use an Infoset made of ODS and Characteristic InfoObject.
165 You can create the calcualted Key Figure at Infoprovider level and Query Level.
166 Structures can be used in several queries for the same Infoprovider.
167 Variables defined in the Query designer are available in all Infoproviders for use in the Query definition.
168
You enter a default value when you create the variable. This default value is then displayed for input enabled variables in the input field of the variable
screen. For fields that are not input enabled, the default value is used as the variable value.
169 You can activate the exceptions in the Report.
170 If you want to use exceptions selectively on specific key figures in your query definition, you have to define an exception for each key figure accordingly.
171
In Exception you can set the Alert colours red, yellow and Green. You change the colors from BW tool bar. For web applications the format is stored in
MIME.
172 In the Restriction tab page you can specify whether a restriction with regard to the use of the exception applies only to totals or all values.
173 You can change, create, activate and Deactivate exceptions using a list of exception web items, when you execute the report on web.
174 You can Delete an exception in the web from the context menu only when you created the exception in Web Application only.
175 You can define several exceptions on a query for different value assignment or for different versions.
176
By Defininig condition you have the option of analyzing the query results in more detail. You can analyze combination of characteristics using ranked lists,
there by displaying your 10 best customers by sales Revencue.
177 You can define multiple conditions for a query and then activate, deactivate them in the report itself to create different views of the data.
178
If the Condition has active status, the condition is used in the report as soon as you execute the query. If active flag is not set, you can activiate the
condition in the report itself.
179
You can set conditions for all characteristics, single characteristics and characteristic combination in the report drill down, i.e in the results area in Bex
Analyser.
180
If you restrict conditions for a report to a characteristic or a combination of characteristics, you have to ensure that the characteristic or combination is
integrated into the report drill down for the restriction defined to take effect.
181
The Condition related to a characteristic that is included through the activation of another condition , leading to collision and is therefore deactivated. You
can reactivate the condition and deactivate the last condition activated.
182 If you activate a condition for a combination of characteristics, the results row no longer displays.
183
If report executed on webm you can create, change, activate, deactivate conditions using list of condition web item. You can delete a condition in context
menu if you have created the condition in the web application itself.
184 You can use the webitem Adhoc Query Designer to create a new query or to change an existing query.
185 Use Adhoc query designer you can create queries for all infoproviders, execute query with out saving.
186
You cannot use variables in the query definition in Adhoc query designer. Only one structure can be used for the key figures. Cannot create reusable
global structures.
187 You can edit the existing queries if none of above mentioned points were used.
188 Precalcuated Web templates are static in nature and hence no additional drilldown is permitted on those templates.
189
The basis for the data transfer for the mobile applications is WAP( for WAP enabled devices), HTTPS & HTML(for PDA's) Compact HTML(cHTML - i-mode
enabled).
190
SAP Enterprise portal lets you retrieve data from information sources in your company and on the internet through the use of mini programs called
iViews.iViews can access Documents, e-mail, web sites, intranets and data in enterprise applications.
191
Portal content studio is the central environment in the enterprise portal for creating and managing portal content. You can use it to edit iViews, portal
pages, layout of portal pages, portal roles, worksets.
192 Bex Analyzer is the platform for creating and editing BW workbooks.
194 Role upload is a function that you can use for the following scenarios.
195 a. You want to continue to use exisiting role definition for BW system in the Enterprise Portal (EP).
196 b. You want to use objects form BW system as content objects to build your roles in EP, means that these objects are to be available in EP.
197
c. Initially you upload all relevant roles and objects from the BW system into the EP. In future you want to create and maintain your content
objects only in EP.
198
d. You upload newly created role definition from the back end system into the EP at regular time intervals.You do this when you use BW as the
leading system and yo create the roles in BW and upload to EP in regular time intervals.
199 The uploaded objects are converted in Portal objects.
200
Bex Broadcasting allows the distribution of BI information via different channels(e-Mail, EP), in different formats(HTML, Zip files, Bex Analyzer work
books), of different sources(Web Applications, Bex Analyzer work books, queries) in different modes(online, Pre calculated).
201
Using Bex Information broad casting you can precalculate Bex web applications and store them as documents in Knowledge Management(KM). The
precalculated web application contains historic data for specific times. These documents can be displayed as iView.
202
You can create linnks to Bex web application in KM. The Links show the current data from the BW report. In contrast to the Bex web application as iView,
the call takes place indirectly through the repository manager for BW metadata.
203
Collabaration with Bex web application as an iView doesnot is not possible because a direct call takes place in the BW system and there is no
representation in the KM as a document or link.
204 Collabaration can only be implemented with documents and links in knowledge management (KM).
205 You can precalculate workbooks and distribute them via email or publish them in a EP.
206
From a query the destination to which you branch is called Jump target. You need to have defined the sender/reciever assignment for the system to be
able to offer jump targets.
207
With in an RRI, if the infoobject 0FISCPER(2002.003) is handed over as paramater to the source system, then this must be divided again into two
individual fields YEAR 2000 and PERIOD 003. The source system doesnot have a data field which the compound information and could not otherwise
interpret the parameters transferred.
208 You can call Bex map from each query which contains Geo relevant characteristics.
209
For example, if a characteristic number in a query is used on Country, Region and Postal code levels, three layers in Bex Map can be indicated. The
respective characteristics for the geographical analysis must be activated.
1
Delta Support Rapid selection of changed records, Reduced transfer of records between OLTP and BW, reduced records through staging process, quicker roll up of aggregates and faster compression.
2 The DELTA queue which is made up of 3 tables, stores the Delta records on the source system. 3 Delta Type F - Flat files provides Delta.
4 Delta Type A - Uses ALE change pointers. 5 Delta Type D - Application determines Delta. 6 Delta Type E - Extractor determines the Delta.
7 Update Modes: FULL UPDATE sends all the requested data on the selection screen of Infopackage.
8 Delta Initialization - Send all requested data in the selection screen of Infopackage and allow me to Delta for the same Delta selections. 9 DELTA - Send just the records that changed or that were new since the last initialization or the prior Delta.
10 Repeat Delta - Send the current Delta records and also resend the records from prior Delta load as these were not loaded correctly. 11
Record Modes: Addresses the issue if exactly how the source system changes to Transaction Data. Before Image, After Image, Additive Image, After Image, Reverse Image, Delete Image.
12 Delta Processes : ODS - Delta with after, before, reverse images provided by the extractor. 13 FIL0 - Delta with file input using After Images, For ODS only
14 FIL1 - Delta with input using Additive images. For ODS and Infocubes. 15 Datasources coded FIL0 has to go to ODS set in overwrite mode.
16 Data Source on source system table ROOSOURCE or BW table RSOLTPSOURCE
17 You find the Delta process as a key in the table RODELTAM in the source system or BW system.
18 Repair Request allows loading a selective FULL UPDATE request even when the target already contains DATA from initial runs or Deltas. 19 RSA7 - Delta queue monitor- Shows status of all Delta queues.
20
Hierarchial data and Text data have completely fixed format requirements for FILE, while master data can have the attribute data fields in any order as long as it matches the file, but the keys have to be in the beginning of the layout.
21 In XML type, data cannot be Hierarchial, but need to be flat.
22 The SOAP RFC service provided by BASIS takes the data and passes it into the Delta Queue of BW. 23 XML method is used for single document and now for large volumes of Data.
24 Multiple Initialization provides features to split up a very large initial load of data into more manageable pieces.
25 Multiple data sources from the same FILE source system can be used to feed the same Infosource. Use create Datasource option. 26 Delta with new status will send the after image of a record.
27 If the legcay system ( Flat file) only know the current / new status of a change, the ODS's overwrite feature must be used.
28 Fake or Pseudo delta is not actually a Delta process. The goal is not to delete and reload the entire cube rather delete only data that could change. 29 DBCONNECT enables you to transfer data from external applications from the respective database tables or views directly in BW system.
30 A Data source is generated from the Table / View whose technical name is composed of 6DB_plus the technical name of the table / view.
31 The Technical name of the table or View is limited to 26 characters as datasource name is limited to 30. Field name limited to 16 characters in upper case . 32 Datasources are used to make data known to the BW.
33 Transfer Structure and Communication structure are generated from the Infosource. 34 XML format is typically not used for mass data Transfer.
35 Data in an XML cannot be Hierarchial, but must be Flat.
36 The SAP RFC service provided by BASIS takes data from XML and passed it to the Delta Queue of BW. 37 XML data loads is designed for single document data loads and not for large volumes of Data.
38 Datamart interface is used for data exchange between different BW systems and on the other hand for updating in datastorage in one BW system. 39 Basic forms of datamart archutecture: Aggregated Architecture, Replicating Architecture, Mixture of Aggregating and Replicating and myself architecture. 40 Aggregated Architecture - Data from one or more BW systems to One central BW system.
41 Replicating Architecture - One central BW system to one more BW systems. Better load performance. 42 Mixture - One or more BW systems to One central BW system to One or more BW systems Plus Self.
43 Myself System - is used to redistribute data with in a BW system itself -> Data transferred from one Infoprovider to another. 44 Generation of an Export Datasource takes place automatically by the activation of the ODS object.
45 For export datasource for a cube will 8plus cube/ODS/infoobject name. Hence name limited to 8 characters.
46 OPEN HUB SERVICE (OHS) comes into the scene when your business has repoting needs currently from a leagacy datawarehouse / Other database. 47 Open hub service provides a frame work for the scheduled and monitored extraction of consolidated and integarted data from BW to external destinations. 48 Open hub service can be used for the control of Outbound data, not directed to another My SAP product.
49 Using open Hub service you can create CSV files. 50 Open Hub service support ODS, Cube, Master Data. 51 OHS support Full Load and Delta (InfoCube and ODS). 52 OHS support transformation through BADI.
53 Infospoke defined the relation between the datasource (ODS/CUBE/Master Data) and the destination ( FILE / DB). 54 The collection of Infospokes emiting from BW make the BW a HUB of information.
55 All aspects of relationship between the OHS datasource and Destination is maintained in Infospoke except the scheduling information. 56
Scheduling is performed through the use of a process chain. The OpenHUB chain element will require a variant as the way to specify the specific infospoke to execute.
57 Creating Infospoke with extraction mode D will result in the addition of the Delta administration button and related cockpit. 58
For OHS data transfer for CUBE data, the Delta extraction must occur prior to the cube being compressed. If cube is compressed, the request ID is lost which is a pointer to the Delta.
59 For Infospoke that are Delta enabled , the Delta Administration LOG keeps track of what requests are in the cube and which one are not yet extracted to target. 60 At run time, the information from Delta Administration Log is used to extract new requests which are not yet extracted.
61 Delta Administration only appears as an option for Delta enabled Infospokes.
62 Deactivating the Delta process sets all existing requests as unread. If a specific request is reset, it will be loaded again in the next Delta load. 63 There is no need to initialize Delta if a Infospoke is created with Extraction mode of Delta.
64 Types of Extractors : Application Specefic, Cross Application
65 Application Specific: BW Content Extractors ( FI, HR, CO, SAP CRM, LO Cockpit), Customer Generated ( FI-SL, COPA, LIS) 66 Cross Application : DB View, Infoset, Function Module.
67 The process of loading data is triggered by a request IDOC to the source system.
68 If Source system is created manually, you have to create the RFC connection between the BW systen and SAP source system first. 69 RFC connection are based on ALE(Application Link Enabling) technology.
70
IDOC Transfer Method:A Data IDOC contains control record(administrative information as Reciever, sender and Client), data records and Status record(Status of IDOC).
71 PSA Transfer method uses the tRFC to transfer data directly from the source system to the SAP BW.
72 PSA : 1962 bytes, 255 fields and uses tRFC as transfer Log. Improves performance of loading since large data packets. 73 ALE : 1000 bytes, tRFC as transfer Log, Can be used with Hierarchies.
74 In Delta Queue data is stored in compressed form. The Delta queue can also be repeated and is specfic to target systems. 75 Early Delta Initialization , if used, donot have to stop updates to data in the source system during initialization.
76 The LO data flow bypasses the LIS infostructure. 77
The Logistics customizing cockpit is the central administration tool for extract structures. You use it to transfer logistics transaction data from OLTP system to BW system.
78
During the LO / LIS extraction, initialization should set up in the OLTP side. The setup fills the setup tables that are read during the initilization. Set up tables can be used for full update.
79 Once the LIS Structure if configured, two Transparent tables and one structure are generated for the special Infostructure. 80 Update Mode for Delta: F - Full Update, C - Delta Initialization, D - Delta, R - Repeat.
82 Record Mode: After Image - ' ', Before Image - 'X', additive Image - 'A'. New record - 'N', Delete - 'D', Cancel the Delete - 'R' 83
in ODS during activation, the data is sorted according to the available key in the active data and in the change log, which guarantees the load of data records in correct sequence and avoids table locks when the data is written.
84 COPA collects all of the OLTP data for calculating contribution margins (Sales, Cost of sales, Over head costs). 85
COPA also has a powerful reporting and Planning functions, but integrated cross application reporting is not available and High reporting work load in OLTP is negative for performance.
86
In COPA, Characteristics are the fields in an operating concern according to which the data can be differentiated in Profitability Analysis ( Divisions, Regions, Customer Groups..)
87 Each characteristic in an operating concern has a series of valid characteristic values ( Eastern Region, Northern Region ..) 88 A profitability segment is a fixed combination of valid characteristic values ( Computer Division , Eastern Region).
89 Apart from the fixed characteristics defined, you can define upto 50 characteristics.
90 Operating Concern is an organizational structure that groups controlling areas together in the same way as controlling areas group companies together 91 A Data source is always created at Operating concern and Client Levels.
92 Company code (CCODE) is a mandatory field if you select your datasource as an Account Based DataSource. 93
94 Generic Data Extraction tools are used when BCT does not include a Datasource for your application. 95
96 A Web service is a self contained, Modularized, executable entity which can be published, searched for and accessed across a network using open standards. 97 Web services provide integration with an enterprise, as well as across enterprise on top of any communication technology stack synchronously or aysnc. 98 SOAP provides a standard packing structure for transporting XML messages over various low level protocols such as HTTP ot SMTP
99 Web Services Description Language (WSDL) is an XML format describing webservices that are available on Internet. 100
Universal Description, Discovery and Integration (UDDI) describe as how to advertise and discover a web service. Holds metadata that can be used to search for servcies.
101 UDDi is a place to publish and retrieve web services. It differentiates Web Service provider, web service and web service type. 102 Source Data in XML format can be delivered into SAP BW Delta Queue using SOAP.
103
When you want to establish a direct open connection to other database which your BW doesn’t support by DB connect then UDI(Universal Data Integration) is used.
104 The BI Java connectors together with the UD connect or BI Java Software Development Kit are used to extract data from Non SAP Source systems.
105 SAP BW Netweaver supports an industry standards pluggable connector architecture. BW leverages and integrates with this architecture viw BI Java Connectors.
106
BI Java Integration : Enabled BI Data staging from a broader range of source systems, Provides access to Multi Dimensional and Relational Database management systems, Supports Transient Data Staging ( Does not store data in BW) and Persistent Staging ( Stores Data in BW), integration of external data into SAP BW queries Via Direct access.
107 UD Connect supports direct access between BW and the source system
108 UD Connect is comprised of Java Compoenent in the SAP Web AS and ABAP component in SAP BW.
109 Using the SAP Java Connector (JCO), UD connect provides stateless session beans which enable communication between the datasources and BW Server. 110 Based on the RFC connection between the BW and J2ee enginer, Session beans can call function modules or can be called by function modules in BW. 111 A Data Target can be supplied with data from several different infousources that in turn can be supplied with data from several different sources. 112 You need to assign an application component to an Infosource to update master data directly.
113 Installing business content - Replicate Datasources -> Activate the corresponding BCT -> Administrator work bench ( transfer data). 114
Control parameters that are maintained for all datasources- Max No of Parallell processes during transfer of data, max no of rows in data package, Max size of data package, Freequency. The last 2 can modified in Infopackage.
115 LO - LIS 116
The Logistics customizing cockpit is the central administration tool for extract structures. You use it to transfer logistics transaction data from OLTP system to BW system.
117 The cockpit contains the following functions: Maintaining extract structures, Maintaining Datasources, Activating updates, controlling updates. 118
LO Data Extraction scenario : Sales Document Data(R3) -> communication Structure(R3) -> extract Structure(in R3) -> Data / Info source(BW) -> Infocubes(BW)
119
The extract structure is supplied with data by R/3 communication structure assigned to it. You can enhance the extract structure by adding appends to the communication structure. Every extract structure can be maintained by you. The extract Structure is created Hierarchially according to R/3 Communication structure.
120
For BW Datasources are based on R3 Extract structures and when the R/3 is upgraded you can decide if you want to activate these modified datasources to Active(A) version or continue to use the one you have.
121
When you extract Transaction data using the LO method, you first need to set up the extraction. The extraction set up reads the dataset that you want to processs (Eg: customer orders with the table VBAK, VBAP..) and fills the relevant communication structure with data. The data is stored in cluster table(extract structure_SETUP) from where it is read when the initialization is run.
122 When you set the extract structures for update to active, the data is written to the extract structures both online when the set up tables are filled. 123
Before the data can be extracted from R/3, you have to initialize the dataset for the previous period on the OLTP side. The setup fills the set up tables that are read during the initialization.
124 V1 Update is considered when a document posting has multiple postings and after all are commited the data is moved to Delta Queue. 125 V2 Update is considered when a document posting is standalone and has no relevant postings into other tables, data is moved to Delta queue. 126
V3 is collective update. All the Transactions are moved to the Update tables and the data movement to Delta queue is scheduled in intervals explicitly called update collection run.
127 Serialized V3 update is updating the Delta records from extraction queue in the order it has arrived to Delta Queue. Useful when updating the ODS. 128
Unserialized V3 update is updating the Delta records in an undefined order and hence has an bad effect while updating ODS. Doesn’t have any effect on Cube as values are aggregated.
129 PI 2002.1 provides the following new update methods:
130 Direct Delta: With every posting, the extraction data is transferred directly into the BW delta queue. It is bad as load on source system is more. 131
Queued Delta: The extraction data is collected in Extraction queue and can be transferred to BW delta queue by an update collection run. Depending on the application up to 10000 Delta Extractions of documents per datasource are summarised and send.
132
Unserialized V3 Update: A V3 Update writes the extraction data for the application to update tables and moved to BW Delta queue when processed by update collection run.
133 LO Extraction Steps:
134 1. Maintain Extract Structures(R3). 135 2. Maintain Data Source (R3) 136 3. Replicate Datasource in BW (BW) 137 4. Assign Infosource(BW)
138 5. Maintain communication Structure and Transfer rules(BW). 139 6. Maintain Infocubes and Update Rules(BW).
140 7. Activate Extract Structure(R3).
141 8. Delete Setup tables / Set up Extraction(R3). 142 9. Infopackage for Delta Initialization(BW). 143 10. Setup periodic V3 Update(R3).
144 11. Infopackage for Delta Upload(BW).
145 With LO structure there is a communication structure available for every document level. 146
147 Steps for LIS Extraction to LO Extraction: 148 1. Maintain Extract structures(R3)
149 2. Maintain Datasource.(R3) 150 3. Replicate Datasource.(BW) 151 4. Assign Infosources.(BW)
152 5. Maintain Communication structure / Transfer rules.(BW) 153 6. Maintain Infocube and Update Rules (BW).
154 7. Activate Extract Structure + LIS update Off(R3).
155 8. Upload the Open Delta Queue (BW). ( This makes sure that no new records or changes are lost). 156 9. Empty Setup Tables(R3)
157 10. Set up /Start V3 Update(R3)
158 11. Simulate Delta Initialization(BW).(Optional) 159 12. Infopackage for Delta Upload(BW).
160
LIS Dataflow: Operative data (Eg: Sales, order, Billing..) stored in application data tables(VBAK, VBAP) is transferred from an operative document into communication structure(Eg: MCVBAK, MCVBAP) to update the data in the LIS. These communication structure in R3 fill LIS Infostructure in R3 which is then updated to BW by update Rules.
161 In the LIS extractor the data is transferred from LIS infostructure into BW.
162 Once the LIS environment has been configured, two transparent tables and one structure are generated for this special Infostructure. 163 LIS Extraction Steps:
164 1. Set up LIS environment(R3).
165 2. Generate Datasource in the R3 system(R3). 166 3. Replicate / Assign Data Source(BW). 167 4. Maintain Communication Structure(BW). 168 5. Maintain Transfer rules (BW).
169 6. Maintain Infocube and Update Rules (BW). 170 7. Generate Update of LIS Infostructure(R3). 171 8. Delta Upload in LIS & LIS activation(R3) 172 9. Infopackage for Delta Initialization.(BW) 173 10. Activate Update.(R3)
174 11. Infopackage for Delta upload.
175 Delta mode: F(Full Update), C(Delta Initialization), D(Delta), R(Repeat).
176 Record mode is an Infoobject and the corresponding field on R3 side that specifies the method in which Delta information is supplied. 177 Delta Method and Record Modes:
178 1. After Image = Record Mode is " " 179 2. Before Image = Record Mode is "X" 180 3. Additive Image = Record Mode is "A" 181 4. New Image = Record Mode is "N" 182 5. Delete Image = Record Mode is "D" 183 6. Reverse Image = Record Mode is "R"
184 Selective Delta Initilization is the process of accrying the load process step by step. 185 CO-PA can answer the queries like Top products and customers in different divisions.
186 Some characteristics like customer, Material, Company code etc are predefined in the each Operating Concern. You can define upto 50 of your own characteristics. 187 The CO-PA datasource can be defined at Operating concern and Client levels.
188 CO-PA datasource can be of Account based or Cost based. Account based do not contain characteritics. KOKRS, BUKRS, KSTAR are mandatory.
189
Delta Methos in CO-PA is valid for both cost based and Account based. I (Initialization), D(Delta request) replicated the all the new line items that have been posted previously at the time t sec(t=30 Minutes called as Security Delta). The system only extracts data that is atleast 30 minutes old.
190
192 1. Generate Datasource in the OLTP(R/3). 193 2. Replicate / Assign Datasource(BW). 194 3. Maintain Communication Structure(BW). 195 4. Maintain Infocube and Update Rules.(BW). 196 5. Infopackage for Delta Initialization.(BW). 197 FI-SL Extraction steps:
198 1. Generate an Extract Structure for a Summary table (R3). 199 2. Define / Assign a Datasource for a Ledger(R3).
200 3. Replicate Datasource(BW). 201 4. Assign Infosource(BW).
202 5. Maintain Communication Structure(BW). 203 6. Maintain transfer Rules(BW).
204 7. Maintain Infocubes and Update Rules(BW). 205 8. Create Infopackage(BW).
206 CRM Extraction Steps:
207 1. If necessary, Change SynchBDOC(R3)
208 2. Create new extraction structure with new fields(R3) 209 3. Maintain BW adpater metadata in BWA1.(R3) 210 4. Check Datsources in RSA3.(R3)
211 5. Check BDOC flow definition for BW adpater(R3) 212 6. Replicate new datasources(BW).
213 7. Create and Attach new Infosource(BW).
214 8. Maintain Transfer rules for new datasources.(BW) 215 9. Schedule and check data request(BW).
216 Early Delta Initialization: The data is written to Delta queue while the set up tables are reading data. Zero down time service for Delta Initialization. 217
Enhancement for the data extraction by BCT, Define the required fields in append structure of your datasource, write your function exit to call up relevant data sources, replicate the datasource in BW, Extract the data.
218
There are 3 options for Delta management for Flat files. Delta with New status(After Image), Additive Delta (Reverse Image+ After Image), Drop & Add ( Fake or Pseudo Delta).
219
Generic datasource supports Delta according to TimeStamp, Calendar Day, Numerical Pointer(Document Number, counter). Only one of these attributes are set as Delta attribute.
