固定资产资料5穆穆-movno1.ppt

Joerg HaaseSAP AG,Customizing of theAsset Transfer,,Contents,I) Customizing Transaction TypesII) Intracompany Transfer Transfer within Company Code (Release < 4.6)III) Intercompany Transfer Transfer between Company CodesIV) Intracompany Transfer since release 4.6Definition of company: Smallest organizational unit for which individual financial statements must be drawn up according to the relevant commercial law.,Customizing Transaction Types,Retirement TransfersTtype 300:Transfer of retiring old assets dataTtype 320:Transfer (retiring) of new acquisition,Acquisition TransfersTtype 310:Transfer of receiving old assets data Ttype 330: Receiving transfer of new acquisition,Transaction Types,Customizing Transaction Types,Customizing Transaction Types,Customizing flag for handling of acquisition in the same year(TBW-BWASLN):Needed for complete transfer of an asset that has both prior-year acquisitions and acquisitions in the current fiscal year.,Customizing Transaction Types,RetirementTransactionType 200,Customizing Transaction Types,Asset 1:Current year andprevious year acquisition Post full retirement with Ttype 200,Customizing Transaction Types,Asset 2:Only previous year acquisition Post full retirement with Ttype 200,Customizing Transaction Types,Result:,,,,Customizing Transaction Types,If Customizing flag ‚transfer adopting dep. start date‘ (TABW-XUMBHI) is set in the transaction type:Activation date is taken over from the sending assetDepreciation start date is taken over from the source assetIf Customizing flag ‚transfer adopting dep. start date‘ (TABW-XUMBHI) is not set:Activation date of the receiving asset is set to the asset valuation date of the transfer posting.Depreciation start date is determined out of the period control in the depreciation key.Until release 4.6 this flag has to be set on the sending part of a transfer,Intracompany Transfer,Reasons for an intracompany transfer:A master record has been created and posted to in the wrong classasset has changed location so that organizational allocations have to be changed too (e.g. asset class or business area)asset needs to be split:a portion of the original asset will be transferred to a new asset (by percentage or amount),Intracompany Transfer,Example:Complete transferPosting date e.g. July-1 2000Asset valuation date 1.1.2000:On the target asset depreciation should be calulated for the whole fiscal year according to the depreciation key.(TABW-XUMBHI = on)Takeover of dep. start date and depreciation parameters,Intracompany Transfer,Source Asset:Deactivation date is set according to customizing of the retirement transaction type.APC values are changed to 0.Planned depreciation is changed to 0 in CY. If the depreciation is already posted to G/L, this will be taken back by the next depreciation run.,Intracompany Transfer,Target Asset: Asset Master Data Activation date is taken over from the source asset(customizing flag TABW-XUMBHI = on)Asset value date of the first posting is set according to the asset valuation date of the transfer.Acquisition year and period is set according to the posting date of the transfer.Original asset number is set.Depreciation areas:expired useful life and depreciation start date of source asset are taken over (customizing flag TABW-XUMBHI),Intracompany Transfer,Target asset: handling of depreciation valuesDepreciation of previous fiscal years is completely taken over from source asset.Planned depreciation for the whole FY is calculated according to the new depreciation key.Depreciation run will handle this asset starting with period 7, because posting date is July-1 2000If catch-up method is switched on then the depreciation from period 1 - 7 is posted at once.,Still awake?,Inter-company Transfer,Intercompany Transfer,Use of Intercompany Transfer:sale between companiessale within one enterpriseasset has to be assigned to a new company codeorganizational structures of the affected company codes have changedphysical location of the asset has changed due to a sail,Intercompany Transfer,Control via transfer variantsAutomatic creation of new master recordOld master data fields copied according to copy rules,if new asset,Relationship Types,Two possible relationship types:Relationship type 1 The company codes are separate legal entities,if both company codes do not belong to the same company.(T001-RCOMP)Relationship type 2 The company codes are both part of the same legal entity if both company codes belong to the same company.Bukrs/Comp1 Bukrs/Comp2 Relationship Affiliated Companies? 1000 / 1 1500 / 1 2 No1000 / 1 3000 / 3 1 Yes1000 / 1 4000 / - 1 No5000 / - 4000 / - 1 NoBukrs = company code Comp = Company,Transfer Variant,CustomizingTransfer Variant:Relationship TypeCross-system Depreciation AreasTransfer MethodTransaction Types,Cross-system Depreciation Areas,Cross-system Depreciation Areas in the transfer variant:A cross-system depreciation area consists of a key and a description only.It has no control parameters of its own.If any cross-system depreciation areas are assigned to local depreciation areas in concerned charts of depreciation,then only assigned areas are transferred.It is not obligatory to define cross-system depreciation areas Cross-system depreciation areas are used if there are different depreciation areas with the same identifier in different charts of depreciationGeneric entry (*) This entry defines the Ttype for all (cross-system) depreciation areas that are not explicitely listed in the transfer variant.,。