Friday, 10 January 2014



Q) Different types in LO's ?
A) Direct Delta, Queued Delta, Serialized V3 update, Unserialized V3 Update.
Direct Delta: - With every document posted in R/3, the extraction data is transferred directly into the BW delta queue. Each document posting with delta extraction becomes exactly one LUW in the corresponding Delta queue.
Queued Delta: - The extraction data from the application is collected in extraction queue instead of as update data and can be transferred to the BW delta queue by an update collection run, as in the V3 update.

Q) What does LO Cockpit contain ?
* Maintaining Extract structure.
* Maintaining DataSources.
* Activating Updates.
* Controlling Updates.

Q) What are Process Chains ?
A) TCode is RSPC, is a sequence of processes scheduled in the background & waiting to be triggered by a specific event. Process chains nothing but grouping processes. Process variant (start variant) is the place the process chain knows where to start.
There should be min and max one start variant in each process chain, here we specify when should the process chain start by giving date and time or if you want to start immediately
Some of theses processes trigger an event of their own that in-turn triggers other processes.
Ex: - Start chain → Delete BCube indexes → Load data from the source system to PSA →
Load data from PSA to DataTarget ODS → Load data from ODS
to BCube → Create Indexes for BCube after loading data → Create database statistics → Roll-Up data into the aggregate → Restart chain from beginning.

Q) What are Process Types & Process variant ?
A) Process types are General services, Load Process & subsequent processing, Data Target Administration, Reporting agent & Other BW services.
Process variant (start variant) is the place the process type knows when & where to start.

Q) Difference between MasterData & Transaction InfoPackage ?
A) 5 tabs in Masterdata & 6 tabs in Transaction data, the extra tab in Transaction data is DATA TARGETS.

Q) Types of Updates ?
A) Full Update, Init Delta Update & Delta Update.

Q) For Full update possible while loading data from R/3 ?
A) InfoPackage → Scheduler → Repair Request flag (check).
This is only possible when we use MM & SD modules.

Q) Why it takes more time while loading the transaction data even to load the transaction without master data (we check the checkbox, Always Update data, even if no master data exits for the data) ?
A) Because while loading the data it has to create SID keys for transaction data.

Q) For what we use HIDE fields, SELECT fields & CANCELLATION fields ?
A) Selection fields-- The only purpose is when we check this column, the field will appear in InfoPackage Data selection tab.
Hide fields -- These fields are not transferred to BW transfer structure.
Cancellation - It will reverse the posted documents of keyfigures of customer defined by multiplying it with -1...and nullifying the value.
I think this is reverse posting

Q) Transporting.
A) When it comes to transporting for R/3 and BW, u should always transport all the R/3 Objects first………once you transport all the R/3 objects to the 2nd system, you have to replicate the datasources into the 2nd BW system…and then transport BW objects.
First you will transport all the datasources from 1st R/3 system to 2nd R/3 System. Second, you will replicate the datasources from 2nd R/3 system into 2nd BW system. Third, you will transport all the BW Objects from 1st BW system to 2nd BW system.
You have to send your extractors first to the corresponding R/3 Q Box and replicate that to BW. Then you have to do this transport in BW. Development, testing and then production

Q) When does a transfer structure contain more fields than the communication structure of an InfoSource ?
A) If we use a routine to enhance a field in the communication from several fields in the transfer structure, the communication structure may contain more fields.

Q) What is the PSA, technical name of PSA, Uses ?
A) When we want to delete the data in InfoProvider & again want to re-load the data, at this stage we can directly load from PSA not going to extract from R/3.

Q) Variables in Reporting ?
A) Characteristics values, Text, Hierarchies, Hierarchy nodes & Formula elements,

Q) Variable processing types in Reporting ?
A) Manual, Replacement path, SAP Exit, Authorizations, Customer Exit

Q) Why we use this RSRP0001 Enhancement ?
A) For enhancing the Customer Exit in reporting.

Q) What is the use of Filters ?
A) It Restricts Data.

Q) What is the use of Conditioning ?
A) To retrieve data based on particular conditions like less than, greater than, less than or equal etc.,

Q) What is NODIM ?
A) For example it converts 5lts + 5kgs = 10.

Q) What for Exception's ? How can I get PINK color ?
A) To differentiate values with colors, by adding relevant colors u can get pink.

Q) Why SAPLRSAP is used ?
A) We use these function modules for enhancing in r/3.

Q) Where are workbooks saved ?
A) Workbooks are saved in favorites.

Q) Can Favorites accessed by other users ?
A) No, they need authorization.

Q) What is InfoSet ?
A) An InfoSet is a special view of a dataset, such as logical database, table join, table, and sequential file, and is used by SAP Query as a source data. InfoSets determine the tables or fields in these tables that can be referenced by a report. In most cases, InfoSets are based on logical databases.
SAP Query includes a component for maintaining InfoSets. When you create an InfoSet, a DataSource in an application system is selected.
Navigating in a BW to an InfoSet Query, using one or more ODS objects or InfoObjects.
You can also drill-through to BEx queries and InfoSet Queries from a second BW system, that isConnected as a data mart.
The InfoSet Query functions allow you to report using flat data tables (master data reporting).
Choose InfoObjects or ODS objects as data sources. These can be connected using joins.
You define the data sources in an InfoSet. An InfoSet can contain data from one or more tables that are connected to one another by key fields.
The data sources specified in the InfoSet form the basis of the InfoSet Query.

Q) LO's ?
Synchronous update (V1 update)
Statistics update is carried out at the same time as the document update in the same task.
• Asynchronous update (V2 update)
Document update and the statistics update take place separately in different tasks.
• Collective update (V3 update)
Again, document update is separate from the statistics update. However, in contrast to the V2 update, the V3 collective statistics update must be scheduled as a job.
Successfully scheduling the update will ensure that all the necessary information
Structures are properly updated when new or existing documents are processed.
Scheduling intervals should be based on the amount of activity on a particular OLTPsystem. For example, a development system with a relatively low or no volume of new documents may only need to run the V3 update on a weekly basis. A full production environment, with hundreds of transactions per hour may have to be updated every 15 to 30 minutes.
SAP standard background job scheduling functionality may be used in order to schedule the V3 updates successfully. It is possible to verify that all V3 updates are successfully completed via transaction SM13. This transaction will take you to the “UPDATE RECORDS: MAIN MENU” screen. At this screen, enter asterisk as your user (for all users), flag the radio button 'All' and hit enter. Any outstanding V3 updates will be listed. While a non-executed V3 update will not hinder your OLTP system, by administering the V3 update jobs properly, your information structures will be current and overall performance will be improved.

No comments:

Post a Comment