A chart of depreciation is used to map asset values to the general ledger True False.
Charts of depreciation are managed at the client level True False.
Depreciation areas are limited to a two space alphanumeric key True False.
A depreciation area can manage more than one currency True False.
More than one depreciation area can be mapped to post into the general ledger True False.
Assets can be attached to more than one cost center in case two or more cost centers manage the asset True False.
All additional account assignment objects for the posting of depreciation are enabled and ready for use True False.
Asset classes are managed at the company code level True False.
Depreciation on an asset can only be charged to cost centers and internal orders True False.
Asset classes can have default values set for depreciation keys, useful life, and screen layout rules True False.
Asset classes must be created for assets under construction and low value assets True False.
Asset classes must be created for assets under construction and low value assets True False.
SAP supplies sample charts of depreciation that are based on the requirements of each country True False.
Business areas must be assigned to company codes True False.
Multiple financial statement verstions do not have to be defined if more than one area posts to the general ledger True False.
Asset classes are used as a template for the creation of asset master records in a company code True False.
Multiple company codes can share the same asset True False.
Asset classes are used as a template for the creation of asset master records in a company code True False.
Default values are defined by the combination of asset class and depreciation areas True False.
The account determination key provides account assignment by the combination of chart of depreciation and chart of accounts True False.
Number ranges for asset master records can only be internally assigned True False.
number ranges for asset master records are independent of organizational object True False.
Number ranges for asset master records can be shared by company codes in asset accounting True False.
The screen layout rule table defines field status, maintenance level, and number ranges for the assets True False.
The evaluation group field labels can be changed in configuration True False.
One of the key factors in determining whether to use one client or multiple clients for a live system, is the amount of data sharing required by the company True False.
Maintenance levels of the asset are only at the asset class and main asset number levels True False.
Assets under construction and managed at the summary level True False.
Assets under Construction have deprecition key 0000, which denotes that depreciation will not be calculated True False.
Assets under Construction can be used to monitor details of capital investments from Investment Management True False.
Areas can only be deactivated at the asset class level True False.
User entries are company defined values used for the posting of asset values True False.
User entries can be defaulted into the master record True False.
SAP delivers depreciation area 10 for standard cost accounting entries True False.
If a capital investment order or WBS is referenced in the asset master record, real postings can be made to those objects True False.
For low value assets, amount checks can be set at the individual or quantity level True False.
Low value asset values are only checked if the posting originated in A/P or a standard asset only postings True False.
When creating multiple assets, populateing the number of similar assets field streamlines asset creation True False.
Post capitalization will post depreciation from prior years into the current year True False.
Master data time-dependent intervals can be made when creating an asset True False.
Asset changes can be viewed at the asset or field level True False.
Equipment master records can be synchronized down at the plant and object type level True False.
Scrap value sets a floor for the end of depreciation on an asset True False.
Changeover year set at the asset level will override configuration settings True False.
Assets with subnumbers can't be retired until the main asset it references is retired as well True False.
Personal value lists set a cap on how much any individual can post to an asset True False.
Personal value lists are limited to 99 lines, but all values can be displayed as well True False.
Master data substitutions are limited to constant value entries True False.
Mass processing in assets always originates from the report environment True False.
If workflow is not desired, worklists should not be assigned to any specific user True False.
Only one field can be substituted for any given step True False.
Substitutions can be entered in the form builder or expert modes, or both True False.
The 4 types of mass processing are master data changes, retirements, transfers, and scrapping True False.
Assets are considered to be a subledger to the general ledger True False.
Postings can be made directly to the general ledger account for assets True False.
The 3 types of postings are integrated, non-integrated, and through logistics True False.
Postings using non-integrated transactions offset to a clearing account that should be set as open item managed True False.
The transaction document is generated based on the transaction type set by internal postings True False.
Asset Explorer cannot handle simulation scenarios True False.
Fields ubdated in the master record after the original posting include the posting information and depreciation area fields True False.
Capitalization date is created by the posting date True False.
If the initial transaction to an asset is driven by a vendor entry, the origin field is populated True False.
Net postings capitalize an asset with the discount taken at time of payment True False.
Acquisition transactions types determine whether an asset will be capitalized True False.
Transaction type groups are used for reporting purposes as well as restricting asset transactions to certain classes True False.
Transaction type groups can be user defined and are changeable True False.
Goods receipts can be set as non-valuated transaction True False.
Group assets can take values from main assets for any area True False.
Asset sale postings can be posted to any revenue account, provided the account field status is set correctly True False.
Retirements with revenue constitute a true revenue to the company selling the asset True False.
The revenue options for mass asset sales are based either on APC or net book value True False.
Asset transfers create a new asset on the receiving entity True False.
For intracompany assets transfers, transfer variant 1 should be used True False.
The 3 delivered methods for asset transfers are gross, net, and new value True False.
A transfer variant contains the method, the relationship type, and the transaction type group affected True False.
The cross company depreciation area does not hold any asset values True False.
Assets under construction are managed at the summary level True False.
Asset master record subnumbers can either be internally or externally assigned True False.
The account assignment category in the PO drives whether an asset will be posted or not True False.
Indexes are used for inflation management and insurance reasons True False.
Fiscal year change is done with regard to balance carryforward for the G/L close True False.
The 3 types of depreciation SAP supports are ordinary, special, and unplanned True False.
Special depreciation also allows for depreciation based on units of production True False.
When creating dependent areas, the transfer of APC values are the only transfers that can be created True False.
Assets can carry negative net book value True False.
When posting unplanned depreciation, only area 1 will get posted True False.
Calculation methods replace the internal calculation key of the depreciation key True False.
If a method won't be considered by the type of depreciation it doesn't have to be entered into the depreciation key True False.
Depreciation keys can b e entred as a default value for a particular company code or depreciation area True False.
The 5 calculation methods are base, declining-balance, maximum amount, multilevel, and period control True False.
The 4 period control moethods are based on acquisition, retirement, transfer, and settlement True False.
Asset value dates canbe derived only by SAP delivered logic True False.
In ECC 5.0, period intervals refine the calculation of depreciation True False.
Parameteres that can be changed on a time dependent basis are depreciation key, useful life, variable depr. amount, absoulute scrap and percentage scrap True False.
Index values can have only year based calculations True False.
All errors must be resolved before the depreciation can post in 4.7 and above True False.
Only real CO objects can be posted, although statistical postings can be made to other objects True False.
Depreciation can be posted to the day, given that the proper setting is made in the depreciation key True False.
Document types are not necessary for periodic APC postings, only realtime postings True False.
Sort characteristics for asset reports can include up to 10 different fields True False.
The asset history sheet report depends on transaction type groups to summarize postings for the report True False.
Simulations can be done using both asset explorer and reporting True False.
Simulation versions can either use substitutions or characteristic combinations True False.
The 3 callup points for validations are header, line item, and company code. True False.
The statuses of activation for validations are inactive and active True False.
Message settings for validations are information, warning, error, and cancel True False.
The character for wild card values in validation messages is "&" True False.
Comparisons in validations can include partial field comparisons, field constant comparisons, and pattern comparisons True False.
Substitution methods are constants, user exits, and field comparison True False.
The three sets are basic, single, and multi sets True False.
Single sets can mix characteristics True False.
Rules can use sets for more efficient validation and substitution formulas True False.
|
