Extractor question

Hai All,
I am extracting data from two tables. One is a Ztable(custom) and the other one is a sap standard table. I am creating a view on both the tables. I am incuding all the fields in custom table and only a couple of fields, date of change and person changing, in the standard table. The key field, changeid, is in the Custom table.
Now my question is, if I use the date field for delta, would the system catch up and get all the related data from the tables or do I need to get the date in the same table that has the key field? If it has to be be in same table, I wonder how the views work?
I would appreciate if any body can refer to me any documentation in this scenario.
Thank you very much.

Hi,
I assume that your ztable will be updated each time the standard table gets updated. If this is the case you can surely use the date field of the standard table as the delta field. You only need to make sure that the change date gets filled even if new data gets posted to that table. If there is a special creation date in that case you need to create your own fm to receive all records created or changed. (... and did you think about deletions?)
regards
Siggi

Similar Messages

PDF Image Extractor questions

I have 2 questions:
1) I mentioned in a previous post that I'm working on a PDF image extractor, mine is a commercial solution so I would like it to be as competitive as possible. I've researched many pdf image extractor tools and I've seen lots of tools that aren't that good (e.g. they extract corrupted images, distorted images, inverted images, not all images are extracted, etc). I'd like to know from the community which image extractor tool(s) they consider the best? Then I can compare my tool's results against them to see how I'm really doing.
2) I have thousands of PDF's to test with for my image extractor tool I'm working on and so far I've encountered images that use DeviceRGB, DeviceCMYK, DeviceGray, CalRGB, Lab, Indexed, and ICCBased....I've been able to handle all of those correctly so far. I've yet to find however ones that use CalGray, Pattern, DeviceN, or Separation. Does anyone have examples of PDFs with images that uses these colorspaces?

I would recommend that you look at some of the standard industry test suites such as the Altona Suite or the Ghent Workgroup Output Suite.

Custom ABAP extractor question

Hi Geeks,
I have written an ABAP report for a custom extractor.
My report pulls all necessary data & modify table ZTABLE.
Now I want to trigger event in BW using RSSM_RAISE_EVENT.
which I will use to trigget process chain in BW.
My question is how BW will recognize my report as custom extractor?
I am not using RSO2 , I am bit confused abt it.
Can anybody clear my understanding about how to go abt defining custom extractors using ABAP report, what r the steps..I know how to write the code & I have my code ready
Thanx in Advance.
Monica

Hi Monica,
You have to create a generic extractor.
Go to transaction RSO2 on your source system.
Fill in a name for the extractor.
In the next screen you have to choose for Extraction with Function Module. If you place you cursor on the FM field and push F1 (Help) you get an example of a FM: RSAX_BIW_GET_DATA_SIMPLE.
Copy this FM and change the logic for collecting the data in itab e_t_data.
Cheers,
Patrick

Generic Extractor Question

Hi
I would like to create a Generic Extractor on table QMFE which has Created Date and Changed Date fields.
If I have to get deltas, I can use only one field in Extractor for Delta option: Either Created Date or Change Date.
If I use Create Date, I'll miss Changes and vice versa.
I felt Function Module Extractor will be 2much complex.
Can any one suggest what is the best approach to get deltas in this scenario?
Thanks
Sree
Please search the forum before posting a thread
Edited by: Pravender on Aug 12, 2011 3:59 PM

Hi Sree,
1) The simplest approach will be to create a single extractor and set the delta pointer to Changed Date, but this is only possible if you populate changed date = Created date for the very first time you create records. So that by using changed date you will not miss any newly created delta records, check with your functional team whether this is possible or not?
2) Otherwise you can create two generic extractors and use two different delta pointers one with Created Date and other with changed date. In the generic extractor you simply need to set your delta pointer and modify the OPEN CURSOR statment to include the proper delta field in selection of data. Rest of your code will be same for both the extractors.
Now if you go for 1st approach then you will have to create only one IP in BW and include it in process chain but in 2nd approach you will have to create two IP (one for each DS) and include both in process chain. It will only increase your data loading time.
Regards,
Durgesh.

Generic extractor question/problem

Hello,
I want to create a generic extractor on custom table which should delta enabled . This custom table has ERDAT( creation date) and ERZET u2013 Entry time but the client is asking me to use both fields for delta functionality . I am not sure how to do this . Please help .
Regards,

As you said client want you to use both the date n time stamp field to extract delta you can follow the below steps.
- Create the generic data source as per you requirement in order to pic the delta
- Open you extract structre and append the field TZNTSTMP, this is the field which holds the time stamp.
- to setup deltas click on generic delta --> select time stamp(UTC)
Regards
KP

Extractor Type 'R' question

Dear all,

Mode -> Description
F -> Transfer all requested data
D -> Transfer delta since last request
I -> Transfer initial status for non-cumulative values
R -> Repeat the last delta transfer
C -> Initialize the delta transfer
S -> Simulate the initialization of the delta transfer
Mode 'R'
This mode must no longer be supported by the extractor under the following conditions:
1. The system has an R/3 Release >= 4.0B
2. The extractor is completely roll back-capable within an extraction process, meaning that no database-commit takes place in the extractor.
My question is,
Can someone explain point no.2 under mode type 'R' for me? I cant do a delta repeat for a master data.
Thanks in advance.
Simon

hi Simon,
try to check following
Error : Updatemode R
Update mode R is not supported by the extraction API
Update mode R is not supported by the extraction API
R mode should mean you can repeat delta, but since it's not supported in R/3 Release >= 4.0B, then what you have to do is re-init
hope this helps.

Cursor and wa_t_data question (extractor)

Hi ABAP-meisters,
I have a coding question for a generic extractor I am making.
The code below uses a cursor to read from table /bic/al_itm1c00
OPEN CURSOR WITH HOLD s_cursor FOR
      SELECT *
      FROM /bic/al_itm1c00
         WHERE /bic/l_loaddat IN r_udate.
    ENDIF.
*   Fetch records into interface table.
* Fetch records into interface table.
    IF c EQ space.
      FETCH NEXT CURSOR s_cursor
                 APPENDING CORRESPONDING FIELDS
                 OF TABLE i_itm1_c
                 PACKAGE SIZE s_s_if-maxsize.
      IF sy-subrc <> 0.
        CLOSE CURSOR s_cursor.
        c = 'X'.
      ENDIF.
    ENDIF.
Then, I want to look in table /bic/al_itm700 and see if this table contains records with the same key as in my previous cursor selection,so that I only transfer records from /bic/al_itm700 that also exist in /bic/al_itm1c00 with this key
LOOP AT i_itm1_c.
      SELECT * FROM /bic/al_itm700 INTO wa_t_data
      WHERE
      /bic/l_docnr = /bic/al_itm1c00-/bic/l_docnr
      AND
      /bic/l_posnr = /bic/al_itm1c00-/bic/l_posnr
      and
      /bic/yl_kcrdat = /bic/al_itm1c00-/bic/yl_kcrdat
      and
      /bic/sourcesys = /bic/al_itm1c00-/bic/sourcesys.
        wa_t_data-recordmode = ''.
        MOVE-CORRESPONDING wa_t_data TO e_t_data.
        APPEND e_t_data.
      ENDSELECT.
    ENDLOOP.
Now, in the end, records from /bic/al_itm1c00 AND /bic/al_itm700 must be in my e_t_data...
In my second piece of code, records are appended to e_t_data. But in my first code, this is not yet happening. Can this be done? Or would this not be the right way to do so?
Points will be awarded!
thanks in advance

Hi Aryan,
Make sure that your new fields are not hidden or checked as 'Field only in User Exit'. You can see this in RSA6 edit mode of the DS.
If you have done this, and still you can not see the fields, go to the Datasource/Trans Structure tab in the TRs and see if you see the field on the right hand side (DS). You should see it here. move it to the TS and you can see this field now in the TRs.
Hope this helps.
Thanks and Regards
Subray Hegde

0FI_AR_4 Extractor Enhancement without user exit code Question

Hi
I have a requirement to enhance 0FI_AR_4 Extractor with below Fields from BSID:
Field     DataElement
PRCTR       PRCTR
VPOS2       NUM06
VBUND       RASSC
As per SAP Note: 410799, I am assuming I don't need to write any ABAP code to populate these fields.
In the extract structure DTFIAR_3 of extractor 0FI_AR_4 Double clicked on the Include CI_BSID.
It prompted "Structure CI_BSID not available. Create the structure?"
After entering Access key it created new Structure "CI_BSID".
I have entered the Component and Component Type values as below:
Component   Component Type
YYPRCTR     PRCTR
YYVPOS2     NUM06
YYVBUND     RASSC
1. Please let me know Component and Component Type values and the steps I followed are correct or not?
2. And I hope I don't need to write the code in the User exit to populate these fields?
Thanks
Sree

Hi,
For any FI datasource enhancement there are two scenarios :-
1. All the fields of the customer enhancement in the customer include are available in the read structure BSID
Then no additional action is required. The fields of the customer enhancement are filled automatically by the datasource from the assigned read structure via "move-corresponding".
2. Fields of the customer enhancement in the customer include are not contained in the read structure BSID
In this case you have to program a function module to fill the field of the customer enhancement. To do this, there is a Business Transaction Event available (open FI interface for process 00005021). Create any function module you like and use function module SAMPLE_PROCESS_00005021 as a template for the interface (input parameter, changing parameter).
Hope this helps.
Reg,
Rahul

Questions on adding z fields to the standard extractor, Please reply !!!

We have 0material, 0customer in our daily process chains where we do full loads daily, now we need to make that delta loads so that we can reduce the time of the execution of the pc. I know that these extractors can be delta enables but the problem is we have a few z fields for these extractors, like 20 fields for 0material and 3 fields for 0customer and currently we are doing full loads for these 2 infobjects. I want to know if these can be delta enabled so that zfields will be delta enabled. I mean in short if we make these delta enabled, will the z fields will come along with the standard fields since we are adding the z fields to the standard tables. Do we need to handle the code separately or is their any complicated code written along with it in the CMOD or just adding the zfields will bring the delta to BI. Please provide some links or any information on this regard. Please let me know if you need any other information. Thanks in advance.

Hi Daniel,
Deltas would be extracted based on some specific fields such as timestamp, dates or some kind of numeric pointer.
In your case, lets say if you have some date field for eg. Changed on in your table on which delta would be picked up then that delta should also fetch up changes related with address.
If this address field is directly present into your main talbe then changes would be directly picked up without any need of logic because table containing changed on date <your delta relevant field> also contains this address field.
But if this address is coming up from some other table then some sort of logic should be written to populate the changes in address field with respect to that "changed on" date field.
Rgrds,
Nilima

Header/Item extractor data modelling question

Hi,
I have installed the Business Content for CRM Activities. In the Business Content they have a separate extractor and cube for header and item level.
However, for our reporting requirements we would like to use one cube. We don't consider a multicube as a valid solution since the item/header cubes have ofcourse not all fields in common what will lead to the famous not-assigned behaviour in Bex.
Therefore I'm trying to enrich each item line with all header fields. I don't want to write a user-exit to enhance the item extractor on datasource side since this will be a lot of work and also not sure this would be delta-compatible. I have bad experiences with this on a previous project.
So I would like to find a solution on BW (data modelling) side but at the moment I don't see any good alternatives. The only thing that I can think of is to build one ODS/master data object (transaction number) that contains all header information and to read this ODS/Master data object while loading the item lines from the ODS to the cube. This way I can copy all header fields to the item line. But this will force me to do FULL loads between the item ODS and the "global" cube and ofcourse I would like to avoid this. (if a header fields changes I want this to be changed in all item lines as well ofcourse)
Does anyone have better solutions ?
Thanks

What I finally did is the following :
1) Create a new cube with all characteristics and keyfigures from header/item level.
2) Load Header ODS to new cube
3) Load Item ODS to new cube but via a startroutine that enriches the item datasources with all header characteristics that are not yet available on item level.
4) Make a query and put constant selection on a restricted keyfigure that contains the following :
a) Product (item level) ==> CONSTANT SELECTION enabled
b) Nr. of activities (header level)
In Bex everything looks now fine with the nr. of activities header keyfigure, even when I do a filtering on material that still only exists on item level thanks to the constant selection but my result row is acting a little bit dissapointing. I hope that can be solved.
Let me give an example : (i'm even excluding the header line in this query)
1) all fine
   Transaction nr ; Nr. Of activities
   6000           ; 1
   ====================================
Resultrow           1
2) drilldown to material
   Transaction nr ; Material ; Nr of activities
   6000           ; 12D      ; 1
   6000           ; 13D      ; 1
=====================================================
Resultrow                      2
==> As you can see the resultrow changes to 2 after doing the drill-down.
Note that I am using "calculate result as summation". If I use "nothing defined" the result will be fine in this case but then it is not correct in the case where I do filterings on e.g. a material number. It will then show the number of activities for the WHOLE query.
Is there anything I can do to get the resultrow right in all circumstances using constant selection ?
Thanks
Message was edited by: Double U

Question about the data in 2LIS_04_P_COMP extractor (0pp_c05 infocube)

Hi gurus.
My Organization need to compare between the materials that go in to the production process and the materials that located inside the products that go out from the production process.
In the R/3 there is a calculation that divides the loss of material in the process amongst the final productions, so the loss material goes back to the full picture.
This calculation called DUV (Distribution of Usage Variances).
I want to know if the data that extract to BW through 2LIS_04_P_COMP is after this calculation or not.
An answer from what table dose this extractor takes the data can help as well.
I can not find any documentation about it.
Maybe some one can help me.
Thanks in advanced
Hagai Jacoby BW advisor

Dear Adir,
This datasource gets data from AFKO and AFPO tables in R/3
Hope it helps.
Thanks,
Krish

A question about Generic Extractor

Hi everyone,
I excuted Generic Extractor to extract customer reference data to MDM server. I deselect "Local download" and select "Upload via FTP", there is no error and the reference data was transfered to corresponsing mdm port directories. But xml files of the reference data were also downloaded into the local directory from where I upload Ports and Check-Tables.
Could you give some suggestion about it.
best regards,

Hi Lionsir,
It could be the case that you have given the local file directory address in the generate XSD option.
Just check the same.
Hope it helps.
Thanks,,
Minaz

Front end and back end questions

Hi,
If I want to develop a web base SOA application by using Jcaps, I have several question want to ask.
1.) In the front end, if i create the page by using eVision to create the page
flow and the page layout, how can I match the fields of the page (such
as the username, email, tel no... with the back end web services?
2.) Does the flow of the front end web pages are control by the page flow in
eVision? When will the eVision supported AJAX or JSF?
3.) What is the use of the eInsight Business process manager, does it
control all the back end flow, such as the flow of each web services?
Does Jcaps has the Bpel engine to control the flow of web services?
4.) I know that in JBoss, there is a jBPM server to control the flow of the front
end pages, does JCAPS has this kind of server?
5.) If i want to connect to the Database? I know that there is a eTL to extract
the data from the database, it is true? Or do u recommend to connect the
database directly through the web services by using JDBC or other
framework as well?
6.) If I have an existing application that is developed by .Net (With no web
services). How can i integrate with other systems? What can I do in order
to reuse the system? Or what Jcaps can do in this manner?
Thanks for you reply! ^ ^

Generally, back-end would consist of the taks associated with configuration of data targets (ODS, Cubes), working with extractors, mapping data to the data targets, writing transfer/start rtn/update rules, and creating Infopkgs/ Process Chains.
Front-end deals with the use of the BW - writing queries, workbooks, web (although I think some of the infrastructure aspects of web reporting. e.g. javascript/templates might really could be considered backend). Think of Front-end as all of the client/customer/user facing components.

SAP BI INTERVIEW QUESTIONS

Hi Friends,
I was face some Interview.
Please send answers to the questions?
How many data Fields and key fields we can create in DSO?
You can overwrite key fields or Data Fields?
Which up date we use in Delta queue extraction( v1 or v2 or v3)
Which message we get when transported request is failed?
what is the Structural difference between Infoucbe and DSO
Data Loading is taking huge time when we extract data from source system to BI system/ how to solve?(Before it took 3-4 Hours now data loading takes 4 days)

What is the difference between Display Attribute and
Navigational Attribute? How to make display attribute and navigational
attribute?
How to load flat file data?
How to load Hierarchy file data?
What is HACR?
How to maintain HACR?
If any issue in HACR then how to resolve the issue?
What is Baby Cube?
Why we are creating Aggregates?
What is the use of Aggregates?
Is there
any particular field on that we can create Aggregates or we can maintain
Aggregate on any field?
What is
the different DSO available? And what is the difference between those DSO?
What is
replacement path?
What are
the extractor types?
• Application Specific
o BW Content FI, HR, CO, SAP CRM, LO Cockpit
o Customer-Generated Extractors
LIS, FI-SL, CO-PA
• Cross Application (Generic Extractors)
o DB View, InfoSet, Function Module
2. What are the steps involved in LO Extraction?
• The steps are:
o RSA5 Select the DataSources
o LBWE Maintain DataSources and Activate Extract Structures
o LBWG Delete Setup Tables
o 0LI*BW Setup tables
o RSA3 Check extraction and the data in Setup tables
o LBWQ Check the extraction queue
o LBWF Log for LO Extract Structures
o RSA7 BW Delta
Queue Monitor
3. How to create a connection with LIS InfoStructures?
• LBW0 Connecting LIS InfoStructures to BW
4. What is the difference between ODS and InfoCube and MultiProvider?
• ODS: Provides granular data, allows overwrite and data is in transparent
tables, ideal for drilldown and RRI.
• CUBE: Follows the star schema, we can only append data, ideal for primary
reporting.
• MultiProvider: Does not have physical data. It allows to access data from
different InfoProviders (Cube, ODS, InfoObject). It is also preferred for
reporting.
5. What are Start routines, Transfer routines and Update routines?
• Start Routines: The start routine is run for each DataPackage after the data
has been written to the PSA and before the transfer rules have been executed.
It allows complex computations for a key figure or a characteristic. It has no
return value. Its purpose is to execute preliminary calculations and to store
them in global DataStructures. This structure or table can be accessed in the
other routines. The entire DataPackage in the transfer structure format is used
as a parameter for the routine.
• Transfer / Update Routines: They are defined at the InfoObject level. It is
like the Start Routine. It is independent of the DataSource. We can use this to
define Global Data and Global Checks.
6. What is the difference between start routine and update routine, when, how
and why are they called?
• Start routine can be used to access InfoPackage while update routines are
used while updating the Data Targets.
7. What is the table that is used in start routines?
• Always the table structure will be the structure of an ODS or InfoCube. For
example if it is an ODS then active table structure will be the table.
8. Explain how you used Start routines in your project?
• Start routines are used for mass processing of records. In start routine all
the records of DataPackage is available for processing. So we can process all
these records together in start routine. In one of scenario, we wanted to apply
size % to the forecast data. For example if material M1 is forecasted to say
100 in May. Then after applying size %(Small 20%, Medium 40%, Large 20%, Extra
Large 20%), we wanted to have 4 records against one single record that is
coming in the info package. This is achieved in start routine.
9. What are Return Tables?
• When we want to return multiple records, instead of single value, we use the
return table in the Update Routine. Example: If we have total telephone expense
for a Cost Center, using a return table we can get
expense per employee.
10. How do start routine and return table synchronize with each other?
• Return table is used to return the Value following the execution of start
routine
11. What is the difference
between V1, V2 and V3 updates?
• V1 Update: It is a Synchronous update. Here the Statistics update is carried
out at the same time as the document update (in the application
tables).
• V2 Update: It is an Asynchronous update. Statistics update and the Document
update take place as different tasks.
o V1 & V2 don't need scheduling.
• Serialized V3 Update: The V3 collective update must be scheduled as a job
(via LBWE). Here, document data is collected in the order it was created and
transferred into the BW as a batch job. The transfer sequence may not be the
same as the order in which the data was created in all scenarios. V3 update
only processes the update data that is successfully processed with the V2
update.
12. What is compression?
• It is a process used to delete the Request IDs and this saves space.
13. What is Rollup?
• This is used to load new DataPackages (requests) into the InfoCube
aggregates. If we have not performed a rollup then the new InfoCube data will
not be available while reporting on the aggregate.
14. What is table partitioning and what are the benefits of partitioning in an
InfoCube?
• It is the method of dividing a table which would enable a quick reference.
SAP uses fact file partitioning to improve performance. We can partition only
at 0CALMONTH or 0FISCPER. Table partitioning helps to run the report faster as
data is stored in the relevant partitions. Also table maintenance becomes
easier. Oracle,
Informix, IBM DB2/390 supports table partitioning while SAP DB, Microsoft SQL
Server, IBM DB2/400 do not support table portioning.
15. How many extra partitions are created and why?
• Two partitions are created for date before the begin date and after the end
date.
16. What are the options available in transfer rule?
• InfoObject
• Constant
• Routine
• Formula
17. How would you optimize the dimensions?
• We should define as many dimensions as possible and we have to take care that
no single dimension crosses more than 20% of the fact table size.
18. What are Conversion Routines for units and currencies in the update rule?
• Using this option we can write ABAP
code for Units / Currencies conversion. If we enable this flag then unit of Key
Figure appears in the ABAP code as an additional parameter. For example, we can
convert units in Pounds to Kilos.
19. Can an InfoObject be an InfoProvider, how and why?
• Yes, when we want to report on Characteristics or Master Data. We have to
right click on the InfoArea and select "Insert characteristic as data
target". For example, we can make 0CUSTOMER as an InfoProvider and report
on it.
20. What is Open Hub Service?
• The Open Hub Service enables us to distribute data from an SAP BW system into
external Data Marts, analytical applications, and other applications. We can
ensure controlled distribution using several systems. The central object for
exporting data is the InfoSpoke. We can define the source and the target object
for the data. BW becomes a hub of an enterprise data warehouse.
The distribution of data becomes clear through central monitoring from the
distribution status in the BW system.
21. How do you transform Open
Hub Data?
• Using BADI we can transform Open Hub Data according to the destination
requirement.
22. What is ODS?
• Operational DataSource is used for detailed storage of data. We can overwrite
data in the ODS. The data is stored in transparent tables.
23. What are BW Statistics and what is its use?
• They are group of Business Content InfoCubes which are used to measure
performance for Query and Load Monitoring. It also shows the usage of
aggregates, OLAP and Warehouse management
http://www.ittestpapers.com/articles/713/3/SAP-BW-Interview-Questions---Part-A/Page3.html
Communication Structure and Transfer
rules
• Create and InfoPackage
• Load Data
25. What are the delta options available when you load from flat file?
• The 3 options for Delta Management with Flat Files:
o Full Upload
o New Status for Changed records (ODS Object only)
o Additive Delta (ODS Object & InfoCube)
Q) Under which menu path is the Test Workbench to be found, including in
earlier Releases?
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?
Q) Errors while monitoring process chains.
A) During data loading. Apart from them, in process chains you add so many
process types, for example after loading data into Info Cube, you rollup data
into aggregates, now this rolling up of data into aggregates is a process type
which you keep after the process type for loading data into Cube. This rolling
up into aggregates might fail.
Another one is after you load data into ODS, you activate ODS data (another
process type) this might also fail.
Q) In Monitor----- Details (Header/Status/Details) à Under Processing (data
packet): Everything OK à Context menu of Data Package 1 (1 Records): Everything
OK ---- Simulate update. (Here we can debug update rules or transfer rules.)
SM50 à Program/Mode à Program à Debugging & debug this work process.
Q) PSA Cleansing.
A) You know how to edit PSA. I don't think you can delete single records. You
have to delete entire PSA data for a request.
Q) Can we make a datasource to support delta.
A) If this is a custom (user-defined) datasource you can make the datasource
delta enabled. While creating datasource from RSO2, after entering datasource
name and pressing create, in the next screen there is one button at the top,
which says generic delta. If you want more details about this there is a
chapter in Extraction book, it's in last pages u find out.
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
The delta queue (RSA7) allows you to monitor the current status of the delta
attribute
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
never been transported, and then you have a choice of transporting the role
(recommended) or just the workbook. If only the workbook is transported, then
an additional step will have to be taken after import: Locate the WorkbookID
via Table RSRWBINDEXT (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 has no dependencies on other objects. Thus, you do not receive an error
message from the transport of 'just a workbook' -- even though it may not be
visible, it will 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 lackhs) of records into
an infocube?
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
objectives and an efficient decision making process ( i.e. Discussions with the
client, like what are his needs and requirements etc.). Project managers
will be involved in this phase (I guess).
A Project Charter is issued and an implementation strategy is outlined in this
phase.
2. Business Blueprint: It is a detailed documentation of your company's
requirements. (i.e. what are the objects we need to develop are modified
depending on the client's requirements).
3. Realization: In this only, the implementation of the project takes place (development
of objects etc) and we are involved in the project from here only.
4. Final Preparation: Final preparation before going live i.e. testing,
conducting 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 Project 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.,
Analysis of objects developing, modification etc) and from here the objects are
transported 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
testing is done.
Production system: All the extraction part takes place in this sys.
Q) How do you measure the size of infocube?
A: In no of records.
Q). Difference between infocube and ODS?
A: Infocube is structured as star schema (extended) where a fact table is
surrounded by different dim table that are linked with DIM'ids. And the data
wise, you will have aggregated data in the cubes. No overwrite functionality
ODS is a flat structure (flat table) with no star schema concept and which will
have granular data (detailed level). Overwrite functionality.
Flat file
datasources does not support 0recordmode in extraction.
x before, -after, n new, a add, d delete, r reverse
Q) Difference between display attributes and navigational attributes?
A: Display attribute is one, which is used only for display purpose in the
report. Where as navigational attribute is used for drilling down in the
report. We don't need to maintain Navigational attribute in the cube as a
characteristic (that is the advantage) to drill down.
Q. SOME DATA IS UPLOADED TWICE INTO INFOCUBE. HOW TO CORRECT IT?
A: But how is it possible? If you load it manually twice, then you can delete
it by requestID.
Q. CAN U ADD A NEW FIELD AT THE ODS LEVEL?
Sure you can. ODS is nothing but a table.
Q. CAN NUMBER OF DATASOURCES HAVE ONE INFOSOURCE?
A) Yes of course. For example, for loading text and hierarchies we use
different data sources but the same InfoSource.
Q. BRIEF THE DATAFLOW IN BW.
A) Data flows from transactional system to analytical system (BW). DataSources
on the transactional system needs to be replicated on BW side and attached to
infosource and update rules respectively.
Q. CURRENCY CONVERSIONS CAN BE WRITTEN IN UPDATE RULES. WHY NOT IN TRANSFER
RULES?
Q) WHAT IS PROCEDURE TO UPDATE DATA INTO DATA TARGETS?
FULL and DELTA.
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.
Q) Why we delete the setup tables (LBWG) & fill them (OLI*BW)?
A) Initially we don't delete the setup tables but when we do change in extract
structure we go for it. We r changing the extract structure right, that means
there are some newly added fields in that which r not before. So to get the
required data ( i.e.; the data which is required is taken and to avoid
redundancy) we delete n then fill the setup tables.
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) WHERE THE PSA DATA IS STORED?
In PSA table.
Q) WHAT IS DATA SIZE?
The volume of data one data target holds (in no. of records)
Q) Different types of INFOCUBES.
Basic, Virtual (remote, sap remote and multi)
Virtual Cube is used for example, if you consider railways reservation all the
information has to be updated online. For designing the Virtual cube you have
to write the function module that is linking to table, Virtual cube it is like
a the structure, when ever the table is updated the virtual cube will fetch the
data from table and display report Online... FYI.. you will get the information
: https://www.sdn.sap.com/sdn
/index.sdn and search for Designing Virtual Cube and you will get
a good material designing the Function Module
Q) INFOSET QUERY.
Can be made of ODS's and Characteristic InfoObjects with masterdata.
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 InfoObject, 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 &
Characteristic values.
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
targets.
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.
Q) TOOLS USED FOR PERFORMANCE TUNING.
ST22, Number ranges, delete indexes before load. Etc
Q) PROCESS CHAINS: IF U has USED IT THEN HOW WILL U SCHEDULING DATA DAILY.
There should be some tool to run the job daily (SM37 jobs)
Q) AUTHORIZATIONS.
Profile generator
Q) WEB REPORTING.
What are you expecting??
Q) CAN CHARECTERSTIC INFOOBJECT CAN BE INFOPROVIDER.
Of course
Q) PROCEDURES OF REPORTING ON MULTICUBES
Refer help. What are you expecting? MultiCube works on Union condition
Q) EXPLAIN TRANPSORTATION OF OBJECTS?
Dev---àQ and Dev-------àP
Q) What types of partitioning are there for BW?
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).
Q) How can I compare data in R/3 with data in a BW Cube after the daily delta
loads? Are there any standard procedures for checking them or matching the
number of records?
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.
To use RSA3, go to it and enter the extractor ex: 2LIS_02_HDR. Click execute
and you will see the record count, you can also go to display that data. You
are not modifying anything so what you do in RSA3 has no effect on data quality
afterwards. However, it will not tell you how many records should be expected
in BW for a given load. You have that information in the monitor RSMO during
and after data loads. From RSMO for a given load you can determine how many
records were passed 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) Types of Transfer Rules?
A) Field to Field mapping, Constant, Variable & routine.
Q) Types of Update Rules?
A) (Check box), Return table
Q) Transfer Routine?
A) Routines, which we write in, transfer rules.
Q) Update Routine?
A) Routines, which we write in Update rules
Q) What is the difference between writing a routine in transfer rules and
writing a routine in update rules?
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.
Q) Routine with Return Table.
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?
X-table = A table to link material SIDs with SIDs for time-independent
navigation 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) Filters & Restricted Key figures (real time example)
Restricted KF's u can have for an SD cube: billed quantity, billing value, no:
of billing documents as RKF's.
Q) Line-Item Dimension (give me an real time example)
Line-Item Dimension: Invoice no: or Doc no: is a real time example
Q) What does the number in the 'Total' column in Transaction RSA7 mean?
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.
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
Analyzer.
A) There is no such table in BW if you want to know such details while you are
opening 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
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)
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 application
extractor.
Q) Why does the number in the 'Total' column in the overview screen of
Transaction RSA7 differ from the number of data records that is displayed when
you call the 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
confirmed. The detail screen displays the records contained in the LUWs. Both,
the records belonging to the previous delta request and the records that do not
meet the selection conditions of the preceding delta init requests are filtered
out. Thus, only the records that are ready for the next delta request are
displayed on the detail screen. In the detail screen of Transaction RSA7, a
possibly existing customer exit is not taken into account.
Q) Why does Transaction RSA7 still display LUWs on the overview screen after
successful delta loading?
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?
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 DataSource with '0' records in RSA7 if delta exists and has
also been loaded successfully?
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.
Q) Do the entries in table ROIDOCPRMS have an impact on the performance of the
loading procedure from the delta queue?
A) The impact is limited. If performance problems are related to the loading
process from the delta queue, then refer to the application-specific notes (for
example 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
effective 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 DeltaQueue, the actual package size may
differ 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)?
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.
Q) What is the purpose of function 'Delete data and meta data in a queue' in
RSA7? 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 InitDelta in the BW System and
should preferably be executed there. You do not only delete all data of this
DataSource for the affected BW System, but also lose the entire information
concerning 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
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)?
A) Import PlugIn 2000.2 patch 3. With this patch the performance during
deletion is considerably improved.
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) 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 DataSource. For DataSources whose name are 19 characters long or shorter,
the short name corresponds to the name of the DataSource. For DataSources whose
name is longer than 19 characters (for delta-capable DataSources only possible
as of PlugIn 2001.1) the short name is assigned in table ROOSSHORTN.
In the qRFC monitor you cannot distinguish between repeatable and new LUWs.
Moreover, 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
posting (MRRS). There is no duplicate transfer of records to the BW system. See
Note 417189.
Q) Why does button 'Repeatable' on the RSA7 data details screen not only show
data 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 inits with various selections. For which one is the
delta loaded?
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) With simple selections (intervals without complicated join conditions or
single values), you can make up to about 100 delta inits. 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 exceed 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 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) 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
requested 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
handler, which processes them in one or several parallel update processes in an
asynchronous 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
DeltaQueue?
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 initialization was still active, he/she posts data into the queue even
though the initialization 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
entries have the status 'READY', others 'RECORDED'. ARFCSSTATE is 'READ'. What
do these statuses mean? Which values in the field 'Status' mean what and which
values 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
once either in a delta request or in a repetition of the delta request.
However, this 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 DeltaQueue and will be loaded into the BW
with the next delta request or a repetition of a delta. In any case only the
statuses READ, READY and RECORDED in both tables are considered to be valid.
The status EXECUTED in TRFCQOUT can occur temporarily. It is set before
starting a DeltaExtraction for all records with status READ present at that
time. The records with status EXECUTED are usually deleted from the queue in
packages within a delta request directly after setting the status before
extracting a new delta. If you see such records, it means that either a process
which is confirming and deleting records which 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 already 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 inconsistency. NOSEND in SMQ1
means nothing (see note 378903).
The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
Q) The extract structure was changed when the DeltaQueue was empty. Afterwards
new delta records were written to the DeltaQueue. When loading the delta into
the PSA, it shows that some fields were moved. The same result occurs when the
contents of the DeltaQueue are listed via the detail display. Why are the data
displayed differently? What can be done?
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.
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
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.
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 should 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
DeltaQueue 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-digit QCOUNT counter in the LUW management table - which is of no practical
importance, however - or the restrictions regarding the volume and number of
records in a database table).
When estimating "smooth" limits, both the number of LUWs is important
and the average data volume per LUW. As a rule, we recommend to bundle data
(usually documents) already when writing to the DeltaQueue to keep number of
LUWs small (partly 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 with a memory volume of about 1GByte per work
process, 100 Mbytes per LUW should not be exceeded). That limit is of rather
small practical importance as well since a comparable limit already applies
when writing to the DeltaQueue. If the limit is observed, correct reading is
guaranteed in most cases.
If the number of LUWs cannot be reduced by bundling application transactions,
you 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 not 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 DeltaRequest. If this
limit is reached within a request, the DeltaQueue must be emptied by several
successive DeltaRequests. 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 report.
A) If I understand your requirement correctly, you want to display the date on
which data was loaded into the data target from which the report is being
executed. If it is so, configure your workbook to display the text elements in
the report. This displays the relevance of data field, which is the date on which
the data load has taken place.
Q) Can we filter the fields at Transfer Structure?
Q) Can we load data directly into infoobject with out extraction is it
possible.
Yes. We can copy from other infoobject 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.
THROUGH WHICH NETWORK.
a) VPN…………….Virtual
Private Network, VPN is nothing but one sort of network
where we can connect to the client systems sitting in offshore through RAS
(Remote access server).
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
CUBE 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
goto sm12
TCode then unlock it this is happened when lock errors are occurred when u
scheduled.
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 infocube panel) select than
navigational attributes drag and drop under rows panel.
Q) IF ANY TRASACTION CODE LIKE SMPT OR STMT.
In current systems (BW 3.0B and R/3 4.6B) these Tcodes don't exist!
Q) WHAT IS TRANSACTIONAL CUBE?
A) Transactional InfoCubes differ from standard InfoCubes in that the former
have an improved write access performance level. Standard InfoCubes are
technically optimized for read-only access and for a comparatively small number
of simultaneous accesses. Instead, the transactional InfoCube was developed to
meet the demands of SAP Strategic Enterprise Management (SEM), meaning that,
data is written to the InfoCube (possibly by several users at the same time)
and re-read as soon as possible. Standard Basic cubes are not suitable for
this.
Q) Is there any way to delete cube contents within update rules from an ODS
data source? The reason for this would be to delete (or zero out) a cube record
in an "Open Order" cube if the open order quantity was 0.
I've tried using the 0recordmode but that doesn't work. Also, would it
be easier to write a program that would be run after the load and delete
the records with a zero open qty?
A) START routine for update rules u can write ABAP code.
A) Yap, you can do it. Create a start routine in Update rule.
It is not "Deleting cube contents with update rules" It is only
possible to avoid that some content is updated into the InfoCube using the
start routine. Loop at all the records and delete the record that has the
condition. "If the open order quantity was 0" You have to think also
in before and after images in case of a delta upload. In that case you may
delete the change record and keep the old and after the change the wrong
information.
Q) I am not able to access a node in hierarchy directly using variables for
reports. When I am using Tcode RSZV it is giving a message that it doesn't
exist in BW 3.0 and it is embedded in BEx. Can any one tell me the other
options to get the same functionality in BEx?
A) Tcode RSZV is used in the earlier version of 3.0B only. From 3.0B onwards,
it's possible in the Query Designer (BEx) itself. Just right click on the
InfoObject for which you want to use as variables and precede further selecting
variable type and proce

Delta with reversal into cube from LO extractors

Hi SDN,
In our LO extraction design we have write-optimized DSO used as EDW as the first layer in BI. Then data is sent to Business Content infocubes, such as 0PUR_C01 though we are using their copies and instead of Update Rules/Transfer Rules, we are using PSA, Transformation, Write Optimized DSO, another transformation and onto the cube. DS and all other objects in the data flow are BI 7.
What we are not clear about is the role or ROCANCEL when passed to both STORNO and RECORDMODE and its impact on the cube after the write-optimized DSO. Some key figures are reversed for 'R' but others are not.
We had thought that 2LIS_02_ITM via a Write Optimized DSO will pass on STORNO and RECORDMODE to the cube which should have reversed all key figures in the cube if the value is 'R'. But it is not happening. Whatever key figures were reversed in the source system, they remained reversed, others are still there and adding another row in the cube with some positive values.
Can anyone shed light on this or provide reference to documentation regarding delta processing in the cube, especially from LO extractors like 2LIS_02_ITM, etc.?
Thanks
SM

Friends,
Thanks for the reply.
My question is more fundamental.
In 3.5 There was expected to be no DSO between Source system and the cube. How were the Update, add and delete handled then?
As I see it, write-optimized DSO is no hindrance because essentially the data is coming into the cube as if there was no DSO in the middle. I do not see SAP suggesting a DSO anywhere between the source and business content cubes, especially in our case dealting with 2LIS_02_ITM, SCL, etc. to handle delta.
Are you saying that no delta management is possible without inserting a DSO before the cube? Please realize that WO DSO only brings data request by request without any summation and overwrite confusion.
What I puzzled at is the lack of comprehensive unfied and detail information either in documentation or a blog.
Please advise.
SM

Extractor question

Similar Messages

Maybe you are looking for