1)How we do the SD and MM configuration for BW ? You need to activate the data sources in R3 system.
You need to maintain the login information for the logical system.sm59 : Choose
the RFC destination , BW system, Under logon Security, maintain the user
credentials. Maintain control parameters for data transfer. Filling in of setup
tables SBIW I feel that these are certain prerequisites. From an SD
perspective, you as a BW consultant should first understand the basic SD
process flow on the R3 side. (search the forum for SD process flow and you'll
get a wealth of information on the flow and the tables as well as transactions
involved in SD). Next you need to understand the process flow that has been
implemented at the clients place. How the SD data flows and what are the
integration points with other modules as well as how the integration happens.
This knowledge is essential when modeling your BW design. From a BW perspective
you need to first know all the SD extractors and what information they bring.
Next look at all the cubes and ODS for SD.
1. What is the t-code to see
log of transport connection? in RSA1
-> Transport Connection you can collect the Queries and the Role and after
this you can transport them (enabling the transport in SE10, import it in STMS
1. RSA1 2. Transport connection (button on the left bar menu) 3. Sap transport
-> Object Types (button on the left bar menu) 4. Find Query Elements ->
Query 5. Find your query 6. Group necessery object 7. Transport Object (car
icon) 8. Release transport (SE10 T-code) 9. load transport (STMS T-code)
2.Lo; mm inventory data
source with marker significance? Marker
is as like check point when u upload the data from inventory data source
2lis_03_bx data source for current stock and BF for movement type after
uploading data from BX u should rlise the request in cube or i menn to say
compress it then load data from another data source BF and set this updated
data to no marker update so marker is use as a check point if u dont do this u
getting data missmatch at bex level bcz system get confuse . (2LIS_03_BF Goods
Movement From Inventory Management-- -----Unckeck the no marker update tab)
(2LIS_03_BX Stock Initialization for Inventory Management-- ---select the no
marker update check box) 2LIS_03_UM Revaluations ----Uncheck the no marker
update tab) in the infopackege of "collaps"
3. How can you navigate to
see the error idocs ? If it is fine check the IDOCs in source system go to
BD87->give Ur user ID and date->execute->you can find Red status Idocs
select the erroneous Idoc->Rt.click and select Manual process. You need to
Reprocess this IDOC which are RED. For this you can take help of Any of your
Team (ALE IDOC Team or BAsis Team)Or Else youcan push it manually. Just search
it in bd87 screen only to Reprocess. Also, Try to find why this IDocs are stuck
there.
4)Difference between v1, v2,
v3 jobs in extraction? V1 Update:
when ever we create a transaction in R/3(e.g.,Sales Order) then the entries get
into the R/3 Tables(VBAK, VBAP..) and this takes place in V1 Update. V2 Update:
V2 Update starts a few seconds after V1 Update and in this update the values
get into Statistical Tables, from where we do the extraction into BW.
V3
Update: Its purely for BW extraction. But in the Document below, V1, V2 and V3
are defined in a different way. Can You please explain me in detial what
exactly V1, V2 and V3 updates means?
5.What are statistical update and document
update? Synchronous Updating (V1 Update) The statistics update is made
synchronously with the document update. While updating, if problems that result
in the termination of the statistics update occur, the original documents are
NOT saved. The cause of the termination should be investigated and the problem
solved. Subsequently, the documents can be entered again. Radio button: V2
updating
6.Do you have any idea how to improve the
performance of the BW..? Asynchronous Updating (V2 Update) With this update
type, the document update is made separately from the statistics update. A
termination of the statistics update has NO influence on the document update
(see V1 Update). Radio button: Updating in U3 update program Asynchronous
Updating (V3 Update) With this update type, updating is made separately from
the document update. The difference between this update type and the V2 Update
lies,however, with the time schedule. If the V3 update is active, then the
update can be executed at a later time. In contrast to V1 and V2 Updates, no
single documents are updated. The V3 update is, therefore, also described as a
collective update.
7)How can you decide the query performance is slow or fast ? You can check that in RSRT tcode. execute the query in
RSRT and after that follow the below steps Goto SE16 and in the resulting
screen give table name as RSDDSTAT for BW 3.x and RSDDSTAT_DM for BI 7.0 and
press enteryou can view all the details about the query like time taken to
execute the query and the timestamps
8)What is statistical setup and what is the
need and why? Follow these steps to filling the set up table. 1. Go to
transaction code RSA3 and see if any data is available related to your
DataSource. If data is there in RSA3 then go to transaction code LBWG (Delete
Setup data) and delete the data by entering the application name. 2. Go to
transaction SBIW --> Settings for Application Specific Datasource -->
Logistics --> Managing extract structures --> Initialization -->
Filling the Setup table --> Application specific setup of statistical data
--> perform setup (relevant application) 3. In OLI*** (for example OLI7BW
for Statistical setup for old documents : Orders) give the name of the run and
execute. Now all the available records from R/3 will be loaded to setup tables.
4. Go to transaction RSA3 and check the data. 5. Go to transaction LBWE and
make sure the update mode for the corresponding DataSource is serialized V3
update. 6. Go to BW system and create infopackage and under the update tab
select the initialize delta process. And schedule the package. Now all the data
available in the setup tables are now loaded into the data target. 7. Now for
the delta records go to LBWE in R/3 and change the update mode for the
corresponding DataSource to Direct/Queue delta. By doing this record will
bypass SM13 and directly go to RSA7. Go to transaction code RSA7 there you can
see green light # Once the new records are added immediately you can see the
record in RSA7. 8. Go to BW system and create a new infopackage for delta
loads. Double click on new infopackage. Under update tab you can see the delta
update radio button.. 9. Now you can go to your data target and see the delta
record.
9.Why
we have construct setup tables? The R/3 database structure for accounting
is much more easier than the Logistical structure.
Once you post in a ledger that is done. You can correct, but
that give just another posting. BI can get information direct out of this (relatively)
simple database structure. In LO, you can have an order with multiple
deliveries to more than one delivery addresses. And the payer can also be
different. When 1 item (orderline) changes, this can have its reflection on
order, supply, delivery, invoice, etc. Therefore a special record structure is
build for Logistical reports.and this structure now is used for BI. In order to
have this special structre filled with your starting position, you must run a
set-up. from that moment on R/3 will keep filling this LO-database. If you
wouldn't run the setup. BI would start with data from the moment you start the
filling of LO (with the logistica cocpit)
10.How can you eliminate the duplicate records in TD, MD?
Try to check the system logs through SM21 for the same.
No comments:
Post a Comment