solution manager is some thing just like a sap client in
that all issues are to be recorded if any issues is closed
it must recorded in that.

this is as per i know becz i saw the solution manager 

client is 200
user is solu
pas wad is : xxx

Hi,
Now a days solution manager is mandatory.  
1. it is used for generating keys and downloading support
packages 

2. it is used to document  user  requirements and preparing
scenarios what needs to to be adopted using solution
manager, where the blue print is the part of solution manager 

3. it is used for reporting, solution desk,to manage the
change requests and use to monitor entire landscape Central
message processing in the SAP Solution Manager:  

- Display customer data, problem description, priority,
attached documents, Service Level Agreements (SLA)
- Assign processor
- Send messages to the creator and other processors
- Forward message to other processors or support units
- Create documents and URLs
- Attach documents
- Status assignment and monitoring
- Create a worklist with selection conditions    
hope this would helpful to you.

hi frds

The fixed assets are valued differently for different
purposes ( business , legal etc). SAP manages different
valuations by means of  Depreciation Areas. There are
various depreciation areas like book depreciation , tax
depreciation, depreciation for cost accounting purposes etc.

A depreciation area decides how and for what purpose an
asset is evaluated. the depreciation area can be 'real' or a
'derived one' . You may need to use several depreciation
areas for a single asset depending upon the valuation and
reporting requirements.

thanking you
venkat
venkatanarayana.k@rediffmail.com
+91-9871905974

Hi,
Creating a new depreciation area after the production start
can really only represent a compromise. 
Define a new depreciation area in Customizing for Asset
Accounting. The new depreciation area cannot be solely for
handling investment support. Define the new depreciation
area so that it adopts its depreciation terms and posting
values from other depreciation areas. 
Check the depreciation terms in the asset class for the new
depreciation area, and change them if necessary. If you do
not want to manage the new depreciation area in all asset
classes, set it to inactive in the asset classes in which it
is not needed. 
Specify in FI-AA Customizing for the individual transaction
types, whether posting should always take place in the new
deprecation area, or whether posting is optional. Modify
especially the definitions for transaction types that only
post to certain depreciation areas (such as the
cost-accounting area), in case these transaction types
should also take the new area into account.
If you also want to manage investment support measures in
the new depreciation area.
the Asset Accounting component enables you to manage values
for assets in parallel in up to 99 depreciation areas. 
A depreciation area is always assigned to only one chart of
depreciation.
the keys for the automatic depreciation of assets in each
chart of depreciation. They are based on elements for
calculation (calculation methods, period controls, and so
on) that are available client-wide.
SAP supplies typical reference charts of depreciation for
each country. They have different depreciation areas and
depreciation keys depending on that country’s specific
requirements. You cannot use these charts of depreciation
directly. You must create your own chart of depreciation by
copying the reference chart of depreciation. Delete any
depreciation areas that are not needed.

The Depreciation component makes it possible to manage the
following types of depreciation in the system:

Automatically calculated depreciation types (can also be
planned manually):
Ordinary depreciation 
Special depreciation
Depreciation types that are normally planned manually:
Unplanned depreciation 
Transfer of reserves/reduction of APC
Depreciation keys control the automatic calculation of
depreciation in the system. These depreciation keys can be
modified. In this way, you can define your own methods for
calculating asset values.

Thank You.

In simple terms, Dep Area can be defined as the following.


Dep area = Dep method + Dep rate

Dep method is nothing but the method of depreciation like
the SLM (straight line method)or WDV (writtend down value
method)

Dep rate is nothing but the percentage of depreciation
applied like 6% or 8%

so dep area is a combination of both

special g/l transaction are in which advance payments are 
involved.We use spl.g/l indicator for making any splg/l 
transacion.


eg.for making adv.to vendor we use 'A' as sp.g/l indicator.

The G/L transactions other than AP & AR are known as special
G/l Transactions. Items like Advance to customers, Bills of
exchange, Interest etc are treated as Special g/l tnxs
Usually for Special G/l tnx there would be a reconciliation
account

Hi,
Special ledger Transactions are sub-ledger includes 
1) Advances
2) Bills of Exchanges
3) Guarantees.

eg: for Advance to vendor we use 'A' as sp.g/l indicator.
eg: for Bill of exchange we use 'W' as sp.g/l indicator.

Thank you.

Document Header does not control anything.

Document type controls only 2 fields in document Header 

i.e. Header Txt & referance.

field status variant controls document header control.

Document header controlled by Document type

Doc Header: Header Data 1. All master Data
control Attributes like : Patner Determination Proced
Text determination  procedure
Org Data profile
Date profile
Routines
Action Profile

field status

Document header controls the field status

No effect man...u can shift to a new company!! But, think
twicw before shifting. Competetion is very high in the
market.  If u think u have enough skills that u can survive
in any company, then u can surely shift to a new
company.Good Luck!!

No it is not possible to write inner join to trasperant 
table and cluster table.system will generate an error wen 
ever u try to join the table.

We can only use inner join in Transparent table not in pool 
or Cluster Table.

ABAP developers should not bother about the cluster and 
pool tables becoz we ABAPiers are mostly concerned with 
TRANSparent tables as it holds application data which is 
much more important to run a organization.

IF ur interested then go for R & D by joining SAPLABS there 
you get a better exposure to do this things..

Best of luck . anyways don't try to use joins between 
altogether different tables it won't work.

You can find this in the InfoPackage via scheduler at the
top menu or the key combination CTRl+SHIFT+F1.
Good luck.

If the request fails in the data target,in oreder to not to 
distrub the deltas we can go for the repair request.

If the request fails in the data target,in order not to 
distrub the deltas we can go for the repair full request. 
this brings up the full data (like full load in a cube) and 
this does not affect the changelog table, so that the 
deltas can be performed normally.

if you missed some delta (request fails) while loading to 
DSO, In order to go for full load since your data target is 
DSO  then you want go for full load again from the source 
then you should change the data mart status as red and do 
repair full request do the load agin.

You cannot post full loads just like that...caution needs 
to be excercised...as there could be sequencing issues. It 
is also used in cases where you want to initialize fisrt 
and then reload full.

In monitor screen ,check the technical status of the 
request for red status and then delete the request from the 
data target .

If it is delta update ,in the source system data target, 
reset the delta. retrigger the info package to load data 
again.

we perform repeat delta, for delta failure. the process 
involves setting the technical status to red in monitor 
screen, deleting the request in the requests tab of 
infotarget/manage and then scheduling the delta load 
normally. there will be an alert that the repeat delta is 
being performed, its ok and proceed to load the delta. this 
brings up the old delta records and any of the newly added 
delta records.

When we  access the data frequently for reporting and when 
the data is in huge quantity, we face delayed data retrival 
problem. 
To overcome this problem we can go for aggregates.

This improves the query performance.

In multiple inheritance when a class D is derived by two 
base classes B and C and both base class is also inherite 
by same class A then then class D will get duplicate copy 
of uppper most base class A.In this case class A will 
declare as virtual class

Bug tracking tool is a tool which helps you to organize the
issue's you find in testing.so that same can be checked
while re-testing or regression testing.so that your system
is error free.

It can also be used to prioritize the issue the development
team needs to fix.

In manual testing - bugzilla,VM's issue tracker is used
In Automation testing - realted test managment tool is used.

QA is preventive activity. its process oriented

QC is detective activity. its main job is to find the 
defects and to fix it.

Quality Assurance is a control of processes;
Quality Control is a control of products.

QA- 
>defect prevention, 
>concentrate on process, 
>involve in entire SDLC, 
>its a staff function 
>quality planning tools and techniqe and quality audit 
methods used.
>Verification
>responsible entire team
>It is planned and systematic set of activities necessary 
to provide adequate confidance that products and services 
will confirm to specified requirments and meet user needs.
QC- 
>Defect detection, 
>concentrate on product
>involve in testing
>its line function
>insepction control charts on basis of work results and 
quality managemnt plan method used
>validation
>responsible tester
>the process by which product quality is compared with 
applicable standards and the action taken when non 
confirmancies is detected.

s qtp supports japanis language

Whenever we want 2 test the Localization Testing.
QTP support Japanese and English languages.
But when u instal QTP.
U will select the Languages Option 
Is it correct?