VMLINUZ的专栏

The issue is caused by the use of the "Standard Transport" activated for the transport of BEx objects. In this case a dynpro screen is called when save a new view. But in the web front end dynpro scre

Start with analyzing the STAD record in order to understand where the time is spent (CPU time, DB time, RFC + CPIC time, ...). For CPU time you can continue with ST12 / SE30, for DB time you n

Using ST12 with Current Mode:In the "Current Mode" Scenario you are going to trace the execution of a program or transaction. Before you trace, it is recommended to execute your program or trans

Facts and dimensions form the core of any business intelligence effort. These tables contain the basic data used to conduct detailed analyses and derive business value. In this article we take a l

It only need to empty and fill set uptable by LBWG and corresponding ABAP program

Your transport request may have the locked object. If you delete this directly you will have to confirm for each object. To avoid this you can goto SE03, select unlock object and then give all of your

1.Check the query in table RSZCOMPDIR2.The version value is 120, which means the version is BI 710 SP63.After changing the values to 110 which means BI 710 SP5, you can edit it with the BEX

Record Mode:                   Delta is feature of extractor, which refers to changes (new/modified entries), occurred in the source system.Record Mode is used in Delta process that is being u

=========================4/19==========HA_100Exercise page 170Exercise 3 doneAtrribute ViewExercise 4 doneAnalyic View for ActualsExercise 5 doneAnalytic View for Planning dataEx

This error appears when you try to execute BW functions on BPC (real time) cube and at least one request is still in yellow.To avoid this go to Context Menu of that cube and select "Change Real

Only InfoCubes physically contain data in the database. By doing so, they are alsodata targets, as data can be loaded into them. In contrast, VirtualProviders onlyrepresent logical views of a data

IntroductionThe error “Lock Table Overflow” is encountered when the configured lock table limit is too small. Lock entries are maintained with the Parameter enque/table_size. Parameter enque/table_s

refer tohttp://www.sap-perf.ca/run-sap-st12/