Académique Documents
Professionnel Documents
Culture Documents
Part - 3
Q) AS WE USE Sbwnn, sbiw1, sbiw2 for delta update in LIS
THEN WHAT IS THE PROCEDURE IN LO-COCKPIT?
No LIS in LO cockpit. We will have datasources and can be maintained
(append fields). Refer white paper on LO-Cockpit extractions.
To refresh the statistical data. The extraction set up reads the dataset
that you want to process such as, customers orders with the tables
like VBAK, VBAP) & fills the relevant communication structure with the
data. The data is stored in cluster tables from where it is read when
the initialization is run. It is important that during initialization phase,
no one generates or modifies application data, at least until the tables
can be set up.
Q) SIGNIFICANCE of ODS?
It holds granular data (detailed level).
Q) INFOSET QUERY.
Can be made of ODS's and Characteristic InfoObjects with masterdata.
Q) ROUTINES?
Exist in the InfoObject, transfer routines, update routines and start
routine
Q) AUTHORIZATIONS.
Profile generator
Q) WEB REPORTING.
What are you expecting??
There are two Partitioning Performance aspects for BW (Cube & PSA)
Query Data Retrieval Performance Improvement:
Partitioning by (say) Date Range improves data retrieval by making
best use of database [data range] execution plans and indexes (of say
Oracle database engine).
B) Transactional Load Partitioning Improvement:
Partitioning based on expected load volumes and data element sizes.
Improves data loading into PSA and Cubes by infopackages (Eg.
without timeouts).
A) You can go to R/3 TCode RSA3 and run the extractor. It will give
you the number of records extracted. Then go to BW Monitor to check
the number of records in the PSA and check to see if it is the same &
also in the monitor header tab.
A) RSA3 is a simple extractor checker program that allows you to rule
out extracts problems in R/3. It is simple to use, but only really tells
you if the extractor works. Since records that get updated into
Cubes/ODS structures are controlled by Update Rules, you will not be
able to determine what is in the Cube compared to what is in the R/3
environment. You will need to compare records on a 1:1 basis against
records in R/3 transactions for the functional area in question. I would
recommend enlisting the help of the end user community to assist
since they presumably know the data.
Q) Transfer Routine?
Q) Update Routine?
A) If you are using the same InfoSource to update data in more than
one data target its better u write in transfer rules because u can assign
one InfoSource to more than one data target & and what ever logic u
write in update rules it is specific to particular one data target.
A) Update rules generally only have one return value. However, you
can create a routine in the tab strip key figure calculation, by choosing
checkbox Return table. The corresponding key figure routine then no
longer has a return value, but a return table. You can then generate as
many key figure values, as you like from one data record.
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 loaded 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
condition
Q) X & Y Tables?
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 next delta request. A LUW only
disappears from the RSA7 display when it has been transferred to the
BW System and a new delta request has been received from the BW
System.
You will find your information about technical names and description
about queries in the following tables. Directory of all reports (Table
RSRREPDIR) and Directory of the reporting component elements
(Table RSZELTDIR) for workbooks and the connections to queries
check Where- used list for reports in workbooks (Table
RSRWORKBOOK) Titles of Excel Workbooks in InfoCatalog (Table
RSRWBINDEXT)
A) Only when a new delta has been requested does the source system
learn that the 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 must be kept for a possible
delta request repetition. In particular, the number on 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?
It is most likely that this is a DataSource that does not send delta data
to the BW System via the delta queue but directly via the extractor
(delta for master data using ALE change pointers). Such a DataSource
should not be displayed in RSA7. This error is corrected with BW 2.0B
Support Package 11.
A) With Plug In 2001.1 the display was changed: the user has the
option of defining the amount of data to be displayed, to restrict it, to
selectively choose the number of a data record, to make a distinction
between the 'actual' delta data and the data intended for repetition
and so on.
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 outbound queue if there are no more
references to the LUWs.
The deletion function is for example intended for a case where the BW
System, from which the delta initialization was originally executed, no
longer exists or can no longer be accessed.
Q) Why does it take so long to delete from the delta queue (for
example half a day)?
Q) Why is the delta queue not updated when you start the V3
update in the logistics cockpit area?
A) It is most likely that a delta initialization had not yet run or that the
delta initialization was not successful. A successful delta initialization
(the corresponding request must have QM status 'green' in the BW
System) is a prerequisite for the application data being written in the
delta queue.
Q) Why are the data in the delta queue although the V3 update
was not started?
A) For delta, all selections made via delta inits are summed up. This
means, a delta for the 'total' of all delta initializations is loaded.
Q) How many selections for delta inits are possible in the
system?
A) Before you copy a source client or source system, make sure that
your deltas have been fetched from the DeltaQueue into BW and that
no delta is pending. After 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 ROOSPRMSC 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 logical system. The delta must be initialized in any case since
delta depends on both the BW system and the source system. Even if
no dump 'MESSAGE_TYPE_X' occurs in BW when editing or creating an
InfoPackage, you should expect that the delta have to be initialized
after the copy.
Q) Despite my deleting the delta init, LUWs are still written into
the DeltaQueue?
Make sure that the change of the extract structure is also reflected in
the database and that all servers are synchronized. We recommend to
reset the buffers using Transaction $SYNC. If the extract structure
change is not communicated synchronously to the server where delta
records are being created, the records are written with the old
structure until the new structure has been generated. This may have
disastrous consequences for the delta.
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 load for certain reasons, set the request in the monitor
to red manually. For the contents 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.