Beruflich Dokumente
Kultur Dokumente
Ans # 1:
Process chains exists in Admin Work Bench. Using these we can automate ETTL proc
esses. These allows BW guys to schedule all activities and monitor (T Code: RSPC
).
PROCESS CHAIN - Before defining PROCESS CHAIN, let us define PROCESS in any give
n process chain. Is a procedure either with in the SAP or external to it with a
start and end. This process runs in the background.
PROCESS CHAIN is set of such processes that are linked together in a chain. In o
ther words each process is dependent on the previous process and dependencies ar
e clearly defined in the process chain.
This is normally done in order to automate a job or task that has to execute mor
e than one process in order to complete the job or task.
1. Check the Source System for that particular PC.
2. Select the request ID (it will be in Header Tab) of PC
3. Go to SM37 of Source System.
4. Double Click on the Job.
5. You will navigate to a screen
6. In that Click "Job Details" button
7. A small Pop-up Window comes
8. In the Pop-up screen, take a note of
a) Executing Server
b) WP Number/PID
9. Open a new SM37 (/OSM37) command
10. In the Click on "Application Servers" button
11. You can see different Application Servers.
11. Go to Executing server, and Double Click (Point 8 (a))
12. Go to PID (Point 8 (b))
13. On the left most you can see a check box
14. "Check" the check Box
15. On the Menu Bar.. You can see "Process"
16. In the "process" you have the Option "Cancel with Core"
17. Click on that option. * -- Ramkumar K
2) What is data integrityand how can we achieve this?
Ans # 2:
Data Integrity is about eliminating duplicate entries in the database and achiev
e normalization.
3) What is index maintenance and what is the purpose to use this in real time?
Ans#3
Indexing is a process where the data is stored by
.. When we write some bodys number we write it as
and Rajesh's number would be in "R"... The phone
ilarly the storing of data by creating indexes is
8)what is partition
9) SAP batch process
10)how do you improve the info cube design performance
12)is there any diff between repair run/repair request. if yes then please tell
me in detail
13)difference between process chain and info package group
diff between partition/aggregate
Answers
3)how can you improve the performance of a query?
Q 3) Query Performance can be improved by making the Aggregates having all the C
hars & KF used in Query.
5) What is virtual cube? Its significance
Q 5) Virtual Cube: Info Provider with transaction data that is not stored in the
object itself, but which is read directly for analysis and reporting purposes.
The relevant data can be from the BI system or from other SAP or non-SAP systems
.
Virtual Providers only allow read access to data.
6)diff methods of generic data source
Q 6) Diff Methods of Generic data source using Transaction RSO2 :
a) Extraction from DB Table or View
b) Extraction from SAP Query
c) Extraction by Function Module
2)how and when can you control whether repeat delta is requested?
2) Important BW data source relevant tables
ROOSOURCE: Table Header for SAP BW OLTP Sources
RODELTAM: BW Delta Process
ROOSFIELD: Data Source Fields
ROOSGEN: Generated Objects for OLTP Source, Last changed date and who etc.
3) For Q 8) i think you mean table partition
you use partition to improve performance. You can only partition on 0CALMONTH or
0FISCPER
4) 1. ROOSOURCE
6. Generic Extraction using 1.Views 2. Info set Queries , 3. Function modules
5) Hi Santosh
Pls note down the Q& ANS
Some of the Real time question.
Q) Under which menu path is the Test Workbench to be found, including in earlier
Releases? Your browser may not support display of this image.
The menu path is: Tools - ABAP Workbench - Test - Test Workbench.
Q) I want to delete a BEx query that is in Production system through request. Is
anyone aware about it?
A) Have you tried the RSZDELETE transaction?
data source d
data source n
the top, whic
a chapter in
Generic delta services: Supports delta extraction for generic extractors according to:
Time stamp
Calendar day
Numeric pointer, such as document number & counter
Only one of these attributes can be set as a delta attribute.
Delta extraction is supported for all generic extractors, such as tables/views,
SAP Query and function modules Your browser may not support display of this imag
e.
The delta queue (RSA7) allows you to monitor the current status of the delta att
ribute
Q) Workbooks, as a general rule, should be transported with the role.
Here are a couple of scenarios:
1. If both the workbook and its role have been previously transported, then the
role does not need to be part of the transport.
2. If the role exists in both dev and the target system but the workbook has nev
er been transported, and then you have a choice of transporting the role (recomm
ended) or just the workbook. If only the workbook is transported, then an additi
onal step will have to be taken after import: Locate the Workbook ID via Table R
SRWBINDEXT (in Dev and verify the same exists in the target system) and proceed
to manually add it to the role in the target system via Transaction Code PFCG -ALWAYS use control c/control v copy/paste for manually adding!
3. If the role does not exist in the target system you should transport both the
role and workbook. Keep in mind that a workbook is an object unto itself and ha
s no dependencies on other objects. Thus, you do not receive an error message fr
om the transport of 'just a workbook' -- even though it may not be visible, it w
ill exist (verified via Table RSRWBINDEXT).
Overall, as a general rule, you should transport roles with workbooks.
Q) How much time does it take to extract 1 million (10 lacks) of records into an
info cube?
A. This depends, if you have complex coding in update rules it will take longer
time, or else it will take less than 30 minutes.
Q) What are the five ASAP Methodologies?
A: Project plan, Business Blue print, Realization, Final preparation & Go-Live support.
1. Project Preparation: In this phase, decision makers define clear project obje
ctives and an efficient decision making process ( i.e. Discussions with the clie
nt, like what are his needs and requirements etc.). Project managers will be inv
olved in this phase (I guess). Your browser may not support display of this imag
e.
A Project Charter is issued and an implementation strategy is outlined in this p
hase.
2. Business Blueprint: It is a detailed documentation of your company's requirem
ents. (i.e. what are the objects we need to develop are modified depending on th
e client's requirements).
3. Realization: In this only, the implementation of the project takes place (dev
elopment of objects etc) and we are involved in the project from here only.
4. Final Preparation: Final preparation before going live i.e. testing, conducti
ng pre-go-live, end user training etc.
End user training is given that is in the client site you train them how to work
with the new environment, as they are new to the technology.
5. Go-Live & support: The project has gone live and it is into production. The P
roject team will be supporting the end users.
Q) What is landscape of R/3 & what is landscape of BW. Landscape of R/3 not sure
.
Then Landscape of b/w: u have the development system, testing system, production
system
Development system: All the implementation part is done in this sys. (I.e., Anal
ysis of objects developing, modification etc) and from here the objects are tran
sported to the testing system, but before transporting an initial test known as
Unit testing (testing of objects) is done in the development sys.
Testing/Quality system: quality check is done in this system and integration tes
ting is done.
Production system: All the extraction part takes place in this sys.
Q) INFOSET QUERY.
Can be made of ODS's and Characteristic Info Objects with master data.
Q) IF THERE ARE 2 DATASOURCES HOW MANY TRANSFER STRUCTURES ARE THERE.
In R/3 or in BW? 2 in R/3 and 2 in BW
Q) ROUTINES?
Exist in the Info Object, transfer routines, update routines and start routine
Q) BRIEF SOME STRUCTURES USED IN BEX.
Rows and Columns, you can create structures.
Q) WHAT ARE THE DIFFERENT VARIABLES USED IN BEX?
Different Variable's are Texts, Formulas, Hierarchies, Hierarchy nodes & Charact
eristic values. Your browser may not support display of this image.
Variable Types are
Manual entry /default value
Replacement path
SAP exit
Customer exit
Authorization
Q) HOW MANY LEVELS YOU CAN GO IN REPORTING?
You can drill down to any level by using Navigational attributes and jump target
s.
Q) WHAT ARE INDEXES?
Indexes are data base indexes, which help in retrieving data fastly.
Q) DIFFERENCE BETWEEN 2.1 AND 3.X VERSIONS.
Help! Refer documentation
Q) IS IT NESSESARY TO INITIALIZE EACH TIME THE DELTA UPDATE IS USED?
No.
Q) WHAT IS THE SIGNIFICANCE OF KPI'S?
KPI's indicate the performance of a company. These are key figures
Q) AFTER THE DATA EXTRACTION WHAT IS THE IMAGE POSITION.
After image (correct me if I am wrong)
Q) REPORTING AND RESTRICTIONS.
Help! Refer documentation.
r a given load. You have that information in the monitor RSMO during and after d
ata loads. From RSMO for a given load you can determine how many records were pa
ssed through the transfer rules from R/3, how many targets were updated, and how
many records passed through the Update Rules. It also gives you error messages
from the PSA.
Q) Start routines?
A) Start routines u can write in both updates rules and transfer rules, suppose
you want to restrict (delete) some records based on conditions before getting lo
aded into data targets, then you can specify this in update rules-start routine.
Ex: - Delete Data Package ani ante it will delete a record based on the conditio
n
Q) X & Y Tables?
X-table = A table to link material SIDs with SIDs for time-independent navigatio
n attributes.
Y-table = A table to link material SIDs with SIDS for time-dependent navigation
attributes.
There are four types of sid tables
X time independent navigational attributes sid tables
Y time dependent navigational attributes sid tables
H hierarchy sid tables
I hierarchy structure sid tables
Q) What does the number in the 'Total' column in Transaction RSA7 mean? Your bro
wser may not support display of this image.
A) The 'Total' column displays the number of LUWs that were written in the delta
queue and that have not yet been confirmed. The number includes the LUWs of the
last delta request (for repetition of a delta request) and the LUWs for the nex
t delta request. A LUW only disappears from the RSA7 display when it has been tr
ansferred to the BW System and a new delta request has been received from the BW
System.
Q) How to know in which table (SAP BW) contains Technical Name / Description and
creation data of a particular Reports. Reports that are created using BEx Analy
zer.
A) There is no such table in BW if you want to know such details while you are o
pening a particular query press properties button you will come to know all the
details that you wanted.
You will find your information about technical names and description about queri
es in the following tables. Directory of all reports (Table RSRREPDIR) and Direc
tory of the reporting component elements (Table RSZELTDIR) for workbooks and the
connections to queries check Where- used list for reports in workbooks (Table R
SRWORKBOOK) Titles of Excel Workbooks in Info Catalog (Table RSRWBINDEXT)
Q) What is a LUW in the delta queue?
A) A LUW from the point of view of the delta queue can be an individual document
, a group of documents from a collective run or a whole data packet of an applic
ation extractor.
Q) Why does the number in the 'Total' column in the overview screen of Transacti
on RSA7 differ from the number of data records that is displayed when you call t
he detail view?
A) The number on the overview screen corresponds to the total of LUWs (see also
first question) that were written to the qRFC queue and that have not yet been c
onfirmed. The detail screen displays the records contained in the LUWs. Both, th
e records belonging to the previous delta request and the records that do not me
et the selection conditions of the preceding delta init requests are filtered ou
t. Thus, only the records that are ready for the next delta request are displaye
d on the detail screen. In the detail screen of Transaction RSA7, a possibly exi
sting customer exit is not taken into account. Your browser may not support disp
lay of this image.
Q) Why does Transaction RSA7 still display LUWs on the overview screen after suc
cessful delta loading?
A) Only when a new delta has been requested does the source system learn that th
e previous delta was successfully loaded to the BW System. Then, the LUWs of the
previous delta may be confirmed (and also deleted). In the meantime, the LUWs m
ust be kept for a possible delta request repetition. In particular, the number o
n the overview screen does not change when the first delta was loaded to the BW
System.
Q) Why are selections not taken into account when the delta queue is filled?
A) Filtering according to selections takes place when the system reads from the
delta queue. This is necessary for reasons of performance.
Q) Why is there a Data Source with '0' records in RSA7 if delta exists and has a
lso been loaded successfully?
It is most likely that this is a Data Source that does not send delta data to th
e BW System via the delta queue but directly via the extractor (delta for master
data using ALE change pointers). Such a Data Source should not be displayed in
RSA7. This error is corrected with BW 2.0B Support Package 11.
Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the l
oading procedure from the delta queue?
A) The impact is limited. If performance problems are related to the loading pro
cess from the delta queue, then refer to the application-specific notes (for exa
mple in the CO-PA area, in the logistics cockpit area and so on).
Caution: As of Plug In 2000.2 patch 3 the entries in table ROIDOCPRMS are as eff
ective for the delta queue as for a full update. Please note, however, that LUWs
are not split during data loading for consistency reasons. This means that when
very large LUWs are written to the Delta Queue, the actual package size may dif
fer considerably from the MAXSIZE and MAXLINES parameters.
Q) Why does it take so long to display the data in the delta queue (for example
approximately 2 hours)? Your browser may not support display of this image.
A) With Plug In 2001.1 the display was changed: the user has the option of defin
ing the amount of data to be displayed, to restrict it, to selectively choose th
e number of a data record, to make a distinction between the 'actual' delta data
and the data intended for repetition and so on.
Q) What is the purpose of function 'Delete data and meta data in a queue' in RSA
7? What exactly is deleted?
A) You should act with extreme caution when you use the deletion function in the
delta queue. It is comparable to deleting an Init Delta in the BW System and sh
ould preferably be executed there. You do not only delete all data of this Data
Source for the affected BW System, but also lose the entire information concerni
ng the delta initialization. Then you can only request new deltas after another
delta initialization.
When you delete the data, the LUWs kept in the qRFC queue for the corresponding
target system are confirmed. Physical deletion only takes place in the qRFC outb
ound queue if there are no more references to the LUWs.
The deletion function is for example intended for a case where the BW System, fr
om which the delta initialization was originally executed, no longer exists or c
an no longer be accessed.
Q) Why does it take so long to delete from the delta queue (for example half a d
ay)?
A) Import Plug In 2000.2 patch 3. With this patch the performance during deletio
n is considerably improved.
Q) Why is the delta queue not updated when you start the V3 update in the logist
ics cockpit area?
A) It is most likely that a delta initialization had not yet run or that the del
ta initialization was not successful. A successful delta initialization (the cor
responding request must have QM status 'green' in the BW System) is a prerequisi
te for the application data being written in the delta queue.
Q) What is the relationship between RSA7 and the qRFC monitor (Transaction SMQ1)
?
A) The qRFC monitor basically displays the same data as RSA7. The internal queue
name must be used for selection on the initial screen of the qRFC monitor. This
is made up of the prefix 'BW, the client and the short name of the Data Source.
For Data Sources whose names are 19 characters long or shorter, the short name
corresponds to the name of the Data Source. For Data Sources whose name is longe
r than 19 characters (for delta-capable Data Sources only possible as of Plug in
Your browser may not support display of this image. 2001.1) the short name is a
ssigned in table ROOSSHORTN.
In the qRFC monitor you cannot distinguish between repeatable and new LUWs. More
over, the data of a LUW is displayed in an unstructured manner there.
Q) Why are the data in the delta queue although the V3 update was not started?
A) Data was posted in background. Then, the records are updated directly in the
delta queue (RSA7). This happens in particular during automatic goods receipt po
sting (MRRS). There is no duplicate transfer of records to the BW system. See No
te 417189.
Q) Why does button 'Repeatable' on the RSA7 data details screen not only show da
ta loaded into BW during the last delta but also data that were newly added, i.e
. 'pure' delta records?
A) Was programmed in a way that the request in repeat mode fetches both actually
repeatable (old) data and new data from the source system.
Q) I loaded several delta in it's with various selections. For which one is the
delta loaded?
A) For delta, all selections made via delta in its are summed up. This means, a
delta for the 'total' of all delta initializations is loaded.
Q) How many selections for delta in its are possible in the system?
A) With simple selections (intervals without complicated join conditions or sing
le values), you can make up to about 100 delta in its. It should not be more.
With complicated selection conditions, it should be only up to 10-20 delta inits
.
Reason: With many selection conditions that are joined in a complicated way, too
many 'where' lines are generated in the generated ABAP source code that may exc
eed the memory limit.
Q) I intend to copy the source system, i.e. make a client copy. What will happen
with may delta? Should I initialize again after that?
A) Before you copy a source client or source system, make sure that your deltas
have been fetched from the Delta Queue into BW and that no delta is pending. Aft
er the client copy, an inconsistency might occur between BW delta tables and the
OLTP delta tables as described in Note 405943. After the client copy, Table ROO
SPRMSC will probably be empty in the OLTP since this table is client-independent
. After the system copy, the table will contain the entries with the old logical
system name that are no longer useful for further delta loading from the new lo
gical system. The delta must be initialized in any case since delta depends on b
oth the BW system and the source system. Even if no dump 'MESSAGE_TYPE_X' occurs
in BW when editing or creating an Info Package, you should expect that the delt
a have to be initialized after the copy. Your browser may not support display of
this image.
Q) Is it allowed in Transaction SMQ1 to use the functions for manual control of
processes?
A) Use SMQ1 as an instrument for diagnosis and control only. Make changes to BW
queues only after informing the BW Support or only if this is explicitly request
ed in a note for component 'BC-BW' or 'BW-WHM-SAPI'.
Q) Despite of the delta request being started after completion of the collective
run (V3 update), it does not contain all documents. Only another delta request
loads the missing documents into BW. What is the cause for this "splitting"?
A) The collective run submits the open V2 documents for processing to the task h
andler, which processes them in one or several parallel update processes in an a
synchronous way. For this reason, plan a sufficiently large "safety time window"
between the end of the collective run in the source system and the start of the
delta request in BW. An alternative solution where this problem does not occur
is described in Note 505700.
Q) Despite my deleting the delta init, LUWs are still written into the DeltaQueu
e?
A) In general, delta initializations and deletions of delta inits should always
be carried out at a time when no posting takes place. Otherwise, buffer problems
may occur: If a user started the internal mode at a time when the delta initial
ization was still active, he/she posts data into the queue even though the initi
alization had been deleted in the meantime. This is the case in your system.
Q) In SMQ1 (qRFC Monitor) I have status 'NOSEND'. In the table TRFCQOUT, some en
tries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What do
these statuses mean? Which values in the field 'Status' mean what and which valu
es are correct and which are alarming? Are the statuses BW-specific or generally
valid in qRFC?
A) Table TRFCQOUT and ARFCSSTATE: Status READ means that the record was read onc
e either in a delta request or in a repetition of the delta request. However, th
is does not mean that the record has successfully reached the BW yet. The status
READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that the record has
been written into the Delta Queue and will be loaded into the BW with the next d
elta request or a repetition of a delta. In any case only the statuses READ, REA
DY and RECORDED in both tables are considered to be valid. The status EXECUTED i
n TRFCQOUT can occur temporarily. It is set before starting a Delta Extraction f
or all records with status READ present at that time. The records with status EX
ECUTED are usually deleted from the queue in packages within a delta request dir
ectly after setting the status before extracting a new delta. If you see such re
cords, it means that either a process which is confirming and deleting records w
hich have been loaded into the BW is successfully running at the moment, or, if
the records remain in the table for a longer period of time with status EXECUTED
, it is likely that there are problems with deleting the records which have alre
ady been successfully been loaded into the BW. In this state, no more deltas are
loaded into the BW. Every other status is an indicator for an error or an incon
sistency. NOSEND in SMQ1 means nothing (see note 378903). Your browser may not s
upport display of this image.
The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
Q) The extract structure was changed when the Delta Queue was empty. Afterwards
new delta records were written to the Delta Queue. When loading the delta into t
he PSA, it shows that some fields were moved. The same result occurs when the co
ntents of the Delta Queue are listed via the detail display. Why are the data di
splayed differently? What can be done?
Make sure that the change of the extract structure is also reflected in the data
base and that all servers are synchronized. We recommend to reset the buffers us
ing Transaction $SYNC. If the extract structure change is not communicated synch
ronously to the server where delta records are being created, the records are wr
itten with the old structure until the new structure has been generated. This ma
y have disastrous consequences for the delta.
When the problem occurs, the delta needs to be re-initialized.
Q) How and where can I control whether a repeat delta is requested?
A) Via the status of the last delta in the BW Request Monitor. If the request is
RED, the next load will be of type 'Repeat'. If you need to repeat the last loa
d for certain reasons, set the request in the monitor to red manually. For the c
ontents of the repeat see Question 14. Delta requests set to red despite of data
being already updated lead to duplicate records in a subsequent repeat, if they
have not been deleted from the data targets concerned before.
Q) As of PI 2003.1, the Logistic Cockpit offers various types of update methods.
Which update method is recommended in logistics? According to which criteria sh
ould the decision be made? How can I choose an update method in logistics?
See the recommendation in Note 505700.
Q) Are there particular recommendations regarding the data volume the Delta Queu
e may grow to without facing the danger of a read failure due to memory problems
?
A) There is no strict limit (except for the restricted number range of the 24-di
git QCOUNT counter in the LUW management table - which is of no practical import
ance, however - or the restrictions regarding the volume and number of records i
n a database table). Your browser may not support display of this image.
When estimating "smooth" limits, both the number of LUWs is important and the av
erage data volume per LUW. As a rule, we recommend to bundle data (usually docum
ents) already when writing to the Delta Queue to keep number of LUWs small (part
ly this can be set in the applications, e.g. in the Logistics Cockpit). The data
volume of a single LUW should not be considerably larger than 10% of the memory
available to the work process for data extraction (in a 32-bit architecture wit
h a memory volume of about 1GByte per work process, 100 Mbytes per LUW should no
t be exceeded). That limit is of rather small practical importance as well since
a comparable limit already applies when writing to the Delta Queue. If the limi
t is observed, correct reading is guaranteed in most cases.
If the number of LUWs cannot be reduced by bundling application transactions, yo
u should at least make sure that the data are fetched from all connected BWs as
quickly as possible. But for other, BW-specific, reasons, the frequency should n
ot be higher than one DeltaRequest per hour.
To avoid memory problems, a program-internal limit ensures that never more than
1 million LUWs are read and fetched from the database per Delta Request. If this
limit is reached within a request, the Delta Queue must be emptied by several s
uccessive Delta Requests. We recommend, however, to try not to reach that limit
but trigger the fetching of data from the connected BWs already when the number
of LUWs reaches a 5-digit value.
Q) I would like to display the date the data was uploaded on the report. Usually
, we load the transactional data nightly. Is there any easy way to include this
information on the report for users? So that they know the validity of the repor
t.
A) If I understand your requirement correctly, you want to display the date on w
hich data was loaded into the data target from which the report is being execute
d. If it is so, configure your workbook to display the text elements in the repo
rt. This displays the relevance of data field, which is the date on which the da
ta load has taken place. Your browser may not support display of this image.
Q) Can we filter the fields at Transfer Structure?
Q) Can we load data directly into info object with out extraction is it possible
.
Yes. We can copy from other info object if it is same. We load data from PSA if
it is already in PSA.
Q) HOW MANY DAYS CAN WE KEEP THE DATA IN PSA, IF WE R SHEDULED DAILY, WEEKLY AND
MONTHLY.
a) We can set the time.
Q) HOW CAN U GET THE DATA FROM CLIENT IF U R WORKING ON OFFSHORE PROJECTS. THROU
GH WHICH NETWORK.
a) VPN
.Virtual Private Network, VPN is nothing but one sort of network where we can c
onnect to the client systems sitting in offshore through RAS (Remote access serv
er).
Q) HOW CAN U ANALIZE THE PROJECT AT FIRST?
Prepare Project Plan and Environment
Define Project Management Standards and
Procedures
Define Implementation Standards and Procedures
Testing & Go-live + supporting.
Q) THERE is one ODS AND 4 INFOCUBES. WE SEND DATA AT TIME TO ALL CUBES IF ONE CU
BE GOT LOCK ERROR. HOW CAN U RECTIFY THE ERROR?
Go to TCode sm66 then see which one is locked select that pid from there and go
to sm12
TCode then unlock it this is happened when lock errors are occurred when u sched
uled.
Q) Can anybody tell me how to add a navigational attribute in the BEx report in
the rows?
A) Expand dimension under left side panel (that is info cube panel) select than
navigational attributes drag and drop under rows panel.
out 'before image and after image' am currently in a BW project and have to writ
e start routines for delta load.
Q) I am very new to BW. I would like to clarify a doubt regarding Delta extracto
r. If I am correct, by using delta extractors the data that has already been sch
eduled will not be uploaded again. Say for a specific scenario, Sales. Now I hav
e uploaded all the sales order created till yesterday into the cube. Now say I m
ake changes to any of the open record, which was already uploaded. Now what happ
ens when I schedule it again? Will the same record be uploaded again with the ch
anges or will the changes get affected to the previous record.
A)
Q) In BW we need to write abap routines. I wish to know when and what type of ab
ap routines we got to write. Also, are these routines written in update rules? I
will be glad, if this is clarified with real-time scenarios and few examples?
A) Over here we write our routines in the start routines in the update rules or
in the transfer structure (you can choose between writing them in the start rout
ines or directly behind the different characteristics. In the transfer structure
you just click on the yellow triangle behind a characteristic and choose "routi
ne". In the update rules you can choose "start routine" or click on the triangle
with the green square behind an individual characteristic. Usually we only use
start routine when it does not concern one single characteristic (for example wh
en you have to read the same table for 4 characteristics). I hope this helps.
We used ABAP Routines for example:
To convert to Uppercase (transfer structure)
To convert Values out of a third party tool with different keys into the same ke
ys as our SAP System uses (transfer structure)
To select only a part of the data for from an info source updating the Info Cube
(Start Routine) etc.
Q) What is ODS?
A) An ODS object acts as a storage location for consolidated and cleaned-up tran
saction data (transaction data or master data, for example) on the document (ato
mic) level.
This data can be evaluated using a BEx query.
Standard ODS Object
Transactional ODS object:
The data is immediately available here for reporting. For implementation, compar
e with the Transactional ODS Object.
A transactional ODS object differs from a standard ODS object in the way it prep
ares data. In a standard ODS object, data is stored in different versions ((new)
delta, active, (change log) modified), where as a transactional ODS object cont
ains the data in a single version. Therefore, data is stored in precisely the sa
me form in which it was written to the transactional ODS object by the applicati
on. In BW, you can use a transaction ODS object as a data target for an analysis
process.
The transactional ODS object is also required by diverse applications, such as S
AP Strategic Enterprise Management (SEM) for example, as well as other external
applications.
Transactional ODS objects allow data to be available quickly. The data from this
kind of ODS object is accessed transactionally, that is, data is written to the
ODS object (possibly by several users at the same time) and reread as soon as p
ossible.
It offers no replacement for the standard ODS object. Instead, an additional fun
ction displays those that can be used for special applications.
The transactional ODS object simply consists of a table for active data. It retr
ieves its data from external systems via fill- or delete- APIs. The loading proc
ess is not supported by the BW system. The advantage to the way it is structured
is that data is easy to access. They are made available for reporting immediate
ly after being loaded.
Q) Does data packets exits even if you don't enter the master data, (when create
d)?
Q) When are Dimension ID's created? Your browser may not support display of this
image.
A) When Transaction data is loaded into Info Cube.
Q) When are SID's generated?
A) When Master data loaded into Master Tables (Attr, Text, Hierarchies).
Q) How would we delete the data in ODS?
A) By request IDs, Selective deletion & change log entry deletion.
Q) How would we delete the data in change log table of ODS?
A) Context menu of ODS
Manage
Environment
Q) How do we load the data if a Flat File consists of both Master and Transactio
n data?
A) Using Flexible update method while creating Info Source. Your browser may not
support display of this image.
Q) Steps in LIS are Extraction?
A)
Q) Steps in LO are Extraction?
A) * Maintain extract structures. (R/3)
* Maintain Data Sources. (R/3)
* Replicate Data Source in BW.
* Assign Info Sources.
* Maintain communication structures/transfer rules.
* Maintain Info Cubes & Update rules.
* Activate extract structures. (R/3)
* Delete setup tables/setup extraction. (R/3)
* Info Package for the Delta initialization.
* Set-up periodic V3 update. (R/3)
* Info Package for Delta uploads.
Posted by Sandhya R Mantha at 8:51 PM
Labels: SAP BW
Reactions:
3 COMMENTS:
huberDecember 18, 2010 at 4:56 AM
Hi
I read this post two times.
I like it so much, please try to keep posting.
Let me introduce other material that may be good for our community.
Source: Maintenance interview questions
Best regards
Henry
Reply
Sqiar BIJanuary 3, 2014 at 9:52 AM
Data Visualization Tableau
SQIAR (http://www.sqiar.com/solutions/technology/tableau) is a leading Business
Intelligence company and provides Tableau Software consultancy across United Kin
gdom and USA.
Reply
yektek onlinetrainingMay 22, 2014 at 2:25 AM
Amazing blog thanks for sharingRam
Reply
LINKS TO THIS POST
Create a Link
Newer Post Older Post Home
Subscribe to: Post Comments (Atom)
There was an error in this gadget
Search This Blog
Followers
Blog Archive
December (2)
October (1)
September (4)
About Me
Sandhya R Mantha
Sandhya R Mantha is a highly skilled business and SAP consultant specializing in
solving complex strategic, finance & accounting, customer-product, supply-deman
d, pricing-capacity and supply chain business problems using a variety of profes
sional services including corporate and competitive strategy, multi-geographic s
upply chain business reengineering, change management and business case benefits
realization through implementation and adoption of SAP R/3, ECC, and BW BI Visu
al Composer BusinessObjects 3.0. She has deep industry experience in the utility
, Biotechnology.
View my complete profile