Depreciation, delta areas and revaluation

Hello wise people - I have a query for you:
In our leading ledger, buildings are set to depreciate and we do not report unrealised gains or losses, so revaluations do not post to the leading ledger. Revaluation only is meant to post to the non-leading ledgers. However, since buildings do not depreciate in the non-leading ledgers, the depreciation areas for the non-leading ledgers post the revaluation, and the delta depreciation areas reverse the posting, for a net effect of 0. In the other ledgers buildings do not depreciate.
We have attempted to set the indicators for revaluation of acquisition and production costs in the non-leading ledger depreciation areas and leave this indicator de-selected in the delta depreciation areas, but then our depreciation runs do not work. We have searched OSS and found nothing, yet this appears to be a program error in the depreciation run, as revaluation should post as APC and not depreciation.
The configuration is set as follows:
In transaction OABW we have the following depreciation areas, configured with regards revaluation of APC and Depn as follows:
01     Book depreciation                    no settings
02     Local Depreciation                    Reval APC & Reval Depn
03     Local Delta Depreciation Area               Reval APC
04     Local Depreciation L2                    Reval APC & Reval Depn
05     Local Delta Depreciation L2               Reval APC
15     Tax                              Reval APC & Reval Depn
16     Tax Delta                         Reval APC
32     Book depreciation in parallel currency          no settings
42     Book depreciation in group currency          no settings
In transaction OABN all of the above are configured (checked) for ordinary depreciation.
The posting to the GL occurs using the following configuration (from Asset Accounting - lean implementation --> Organiastional Structures --> Depreciation Areas --> Define how depreciation areas post to the general ledger --> :
1     Book depreciation                    Real Depn Area          Realtime GL          Leading Ledger
2     Local Depreciation                    Real Depn Area          Depreciation Only     Local GAAP Ledger
3     Local Delta Depreciation Area               -nothing specified-     Only APC Directly     Local GAAP Ledger
4     Local Depreciation L2                    Real Depn Area          Depreciation Only     Local Consolidation Ledger
5     Local Delta Depreciation L2               -nothing specified-     Only APC Directly     Local Consolidation Ledger
15     Tax                              Real Depn Area          Depreciation Only     Local Tax Ledger
16     Tax Delta                         -nothing specified-     Only APC Directly     Local Tax Ledger
32     Book depreciation in parallel currency          Real Depn Area          Area does not post     nothing specified
42     Book depreciation in group currency          Real Depn Area          Area does not post     nothing specified
We have an asset class for buildings and wish to revalue specific assets using transaction ABAW. We will process upward and downward revaluations.
Any ideas? Any input would be greatly appreciated!
My best
Rodney

Hi Nagarjuna,
You can maintain different GL accounts in AO90.
COD --> COA --> Account Determination --> Depreciation --> Depreciation Area --> Account assignment on Revaluation on Deprecition.
Hope it helps.
Thanks,
Deepanshu

Similar Messages

What are the delta mechanisms and tables used for Lo Extraction & COPA

Hi all
what are the delta mechanisms and tables used for Lo Extraction & COPA.
please explain clealry.
Thanks & Regards,
James

James,
Please go through Roberto's weblog :
/people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
Anyways,
As you know LO cockpit consists of different modules(MM, PP, SD, etc)
They are called appl components. Each of them have a number (eg.MM=02) and for each appl comp they might be different Data sources and for each DS they might be different tables. So, unless you be specific we cant tell a specific table for a DS.
coming to the delta mechanisms, there are " direct delta, queqed delta and serialized delta".
Copa is based on the oepration concern. it can be created on " accouting based" or "costing based".
Assign points if helpful
Kalyan

Tax depreciation area and non-leading ledger

I want to know how to post assets retirement and transfer transaction into non-leading ledger.
I setup one depreciation area 50 for local tax depreciation and accordingly one non-leading ledger ZZ for local satuary report.
Depreciation area posting indictor
01: Book depreciation             1
50: Tax depreciation               3 (only post depreciation)
90: Variance (50 minue 01)      6
system was able to peform below:
1) for acquisition transaction, same APC value was updated into both ledger
2) for depreciation, different depreciation amount can post into each ledger
But I don't understand below results:
1) For retirnment transaction, there is only one FI document posted into leading ledger with APC and accumulated depreciation. But I could not find any related document in non-leading ledger.
2) Same as assetes transfer transaction
3) But in assets explorer, the APC, accumulated depreciation was cleared correctly, also there is difference of accumulated depreciation in area 90(derived area)
I think it was different with my expectation: I thought SAP can post FI document to each ledger with APC and different accumulated depreciation.
My question was how to get the APC and accumulated account balance in non-leading ledger with local tax depreciation based.
Thanks in advance!

Thanks first.
ASKB was "Periodic Assets posting" but in our IMG the G/L posting indictor of prallel depreciation area was 3 (only post depreciation) and 6(only APC directly).
The setting was configured through the SAP wizard "Setup Areas for Paralle valuation".
Can you give further advice?

What is global Area and why is depreciation Area 01 considered global Area

Hello Forum,
What is global Area and why is depreciation Area 01 considered global Area
Thanks
Best Regards
D. Swathi

Hello Forum,
What is global Area and why is depreciation Area 01 considered global Area
Thanks
Best Regards
D. Swathi

AS91 and Revaluation Keys

When creating Assets via AS91 (Legacy Asset Creation) we are having trouble getting the revaluation keys to come across. The system issues an error message for our revaluation areas saying we need to provide a depreciation start date and an expired useful life. The Associated Configuration Table is already set mapping the specific Mexican Asset Classes to the appropriate Revaluation Keys. Funny thing is that it works for AS01 (Create Asset) in that we can create these and the corresponding Revaluation key gets associated to the individual record per the table mapping. Some reason AS91 is having trouble with this.
The odd thing is when I break this configuration table link (Asset Class to Associated Revaluation Key) then I can load the asset via AS91 succesfully. The only thing I have to do is provide the link manually when loading.
Any Ideas?
Thanks in Advance

Dear,
Hennylin.
AS91 & ABUMN both are completely different transactions.
AS91 :- Create Legacy Asset.
ABUMN :- Trasfer Asset within company code.
If you want to transfer the asset from one company code to another company code then ABUMN is used. And when you transfer the legacy of Asset into SAP then old assets are created through AS91 for uploading with old values of respective assets.
I hope it is helpful to clear your doubt. If you have any doubts feel free to share.
Regards,
Pankaj A Bhalerao.

Loading through Process Chains 2 Delta Loads and 1 Full Load (ODS to Cube).

Dear All,
I am loading through Process chains with 2 Delta Loads and 1 Full load from ODS to Cube in 3.5. Am in the development process.
My loading process is:
Start - 2 Delta Loads - 1 Full Load - ODS Activation - Delete Index - Further Update - Delete overlapping requests from infocube - Creating Index.
My question is:
When am loading for the first am getting some data and for the next load i should get as Zero as there is no data for the next load but am getting same no of records for the next load. May be it is taking data from full upload, i guess. Please, guide me.
Krishna.

Hi,
The reason you are getting the same no. of records is as you said (Full load), after running the delta you got all the changed records but after those two delta's again you have a full load step which will pick whole of the data all over again.
The reason you are getting same no. of records is:
1> You are running the chain for the first time.
2> You ran this delta ip's for the first time, as such while initializing these deltas you might have choosen "Initialization without data transfer", as such now when you ran these deltas for the first time they picked whole of the data.Running a full load after that will also pick the same no. of records too.
If the two delats you are talking are one after another then is say u got the data because of some changes, since you are loading for a single ods to a cube both your delta and full will pick same "For the first time " during data marting, for they have the same data source(ODS).
Hope fully this will serve your purpose and will be expedite.
Thax & Regards
Vaibhave Sharma
Edited by: Vaibhave Sharma on Sep 3, 2008 10:28 PM

Deltas are not updating to next ODS?

Hi,
The deltas are loading from R/3 to Two ODS(O1 and O2) from Two Different data sources(Delta).Again these deltas from O1 and O2 are loaded to ODS O3.The problem is the O2 deltas are upadating to O3 ODS correctly.But the O1 deltas are not being loaded to O3 ODS.All these are loadings are happening through the process chain.Can any one help me to understand why the deltas are not being loaded to O3 ODS from O1 ODS.
Points will be definitely assigned .
Thanks,
Vasu.

Hi,
The next delta will all the request data from Source ODS to target ODS which have not yet been pulled.
You can confirm this by checking the Datamart status (Tick sign) besides each request in the source ODS.
All those without this tick will be updated in the next delta.
All those requests that have this tick is already availble or loaded into target ODS.
So once this delta is loaded things will stabilize.
Hope this helps.
Thanks,
JituK

What is a delta migration and is there any tool that support delta migration?

Hi,
We are migrating from MOSS 2007 to SharePoint 2013.
What is a delta migration and is there any tool that supports delta migration...Please help me understand.

hi
there are many tools are availabe in market like DocAve,Metalogic-Content migration and Quest Migration
so as per my experince Content Matrix is good to support all the feature while migration form Sharepoint 2007 and Sharepoint 2010 or Sharepoint 2013.
See the below link
http://www.metalogix.com/help/Content%20Matrix%20Console/SharePoint%20Edition/002_HowTo/003_MigrationActions/020_IncrementalCopying.htm
Please mark the answer if this help full..

Delta are pointing Old BW system instead of new BW system

Hi,
We are doing upgrade and as part of upgrade BI 7.0 we have copied existing BW system into new BW system.
I have a extracted data from R/3 to BI system.All the full loads went through successful except Delta data load into BI system.
Delta data source are pointing Old BW system instead of new BW system.
I have checked RSA7 where all the deltas are pointing to Old BW system instaed of new BW syste.
I beleive some thing might have happend during System copy from Old BW system to New BW system.
Please correct me if i am wrong about my scenario
I would like to delete delta init which is pointing to BW old system and would like to do new delta .
For that i would like to delte entries in R/3 source table ROOSPRMSF,ROOSPRMSC.
In BW side RSSDLINIT and will extract data using full update and then will do delta init without data transfer and do delta on it.
Please some advise me which is best way
to check with basis do ask them to correct it,other wise deleting deltafrom delta queue.
Its urgent

Hi,
You have to check the TRFCQOUT table to see if the Delta queues are still pointing to the old system ID.
Using ABAP program you can change the System ID. you can use the below code by creating a custom report( executable Program) you can change the System ID's . You should have done this before pulling delta's
anyway, you can try to change and see if you can pull deltas.
Tables: TRFCQOUT, RFCATTRIB.
Data: count type i.
parameters:
       ssystem like trfcqout-dest obligatory default 'Production System Id here',
       tsystem like RFCATTRIB-rfcdest obligatory default 'Non Production System Id here',
       tmod as checkbox default 'X'.
if ( sy-sysid = 'R/3 Production system id here' or sy-sysid = 'BW production system id here' ).
write:/ 'You are not permitted to run this program in production.'.
stop.
endif.
if tmod = 'X'.
Select count( * ) into count from TRFCQOUT where dest = ssystem.
if sy-subrc <> 0.
    write:/ 'Cannot process request, return code ', sy-subrc.
    stop.
else.
    write:/ count, 'entries in TRFCQOUT will be converted.'.
endif.
else.
This will update the qRFC queue by changing all specified queues
related to a source logical system to a target logical system.
This enables the copied systems to remain consistent without
having to run any loads.
UPDATE TRFCQOUT SET   DEST = tsystem
                  WHERE DEST = ssystem.
if sy-subrc <> 0.
    write:/ 'Examine return code not equal to zero.'.
    stop.
else.
    write:/ sy-dbcnt, 'entries were updated in table TRFCQOUT.'.
endif.
endif.
Thanks

Require material on Delta's and how they posted from LO extraction to BW

Hi All,
Can any body send "material on Delta's and how they posted from LO extraction to BW and tell the scenario's"
Plz reply back me to [email protected]
Regards,
Kiran

Hi Kiran,
I have sent some information that what are delta that we use for
delta and how they work.
If you need any clarification let me know.
Thanks
If useful assign some points

How to do delta detection and delta creation

Hi
i am new to OWB , please help me in
how to do delta detection and delta creation using OWB
Thanks

Hi Bassem,
for delta detection in your data source there are three possibilities:
1. the source data has some identifier when it has been modified and deleted data is marked an not physically deleted
In this case you just filter the data that has been changed in your owb mappings.
2. you use some change data capture technologies
You have to install this manually when using owb 11.1 or older versions (google for oracle and cdc). owb 11R2 brings built in support for change data capture.
3. you get all the data and identify the delta manually
In the owb mapping you left outer join the data from your source with the existing data in your target and filter for the data that is new or has been modified. In a second step you identify the deleted data by selecting the data in your target minus the data from your source.
Which approach is the best depends on your specific system architecture.
Regards,
Carsten.

ABR delta extractor and entries written to the delta queue

Hello Everyone,
We have an ABR extractor and it's behaving like this:
For example fields: PM Order Number, Post Goods Issue Date, Start Date, Work Qty, Projected Qty
Create the PM order the entry is written perfect to the delta queue:
10019987, blank, 04/29/2009, 100 PC, 90 PC
Now, if we perform a confirmation on the PM order we see the following:
10019987, 04/29/2009, blank, 0 PC, 90 PC
Now if we change something on the PM order header we see the following:
10019987, blank, blank, 100 PC, 0 PC
When this comes over to BW we don't get good results in our ODS.
Basically we don't get our Post Goods Issue date and Work Qty gets blanked out. Basically, the last change to the order gets written to the ODS and isn't correct.
Shouldn't it do the following:
10019987, blank, 100 PC, 90 PC
10019987, 04/29/2009, 100 PC, 90 PC
10019987, 04/29/2009, 100 PC, 90 PC
10019987, 04/29/2009, 04/29/2009, 100 PC, 90 PC------this gets sent as last record with all fields updated. We choose all these fields in the extract structure.
Thanks

Hello Martin,
Below is a snapshot of the delta queue (you can see the Cancel). Question: How do you control what record is updated and what others are not? We thought the cancel won't update and the others will in order they were updated to the delta queue (and that appears how it's behaving):
Scenerio #1 (sorry, can't remember sequence of steps done in system, but thought I'd mention)
Cancel, Order Number, Release Date, Posting Date, Material, Plan Qty, Confirmed Qty
blank, 10019987, 04/29/2009, blank,       , 4415, 100, 0
blank, 10019987, 04/29/2009, 04/30/2009, 4415, 0,    100
blank, 10019987, 04/29/2009, blank,         4415, 100, 100
X,       10019987, 04/29/2009, blank,         4415, 100, 100
Scenerio #2
cancel, order, release date, posting date, material, plan qty, confirm qty
blank, 100019989, 04/29/2009, blank, 4415, 50, 0
then we perform a confirmation for 50 pieces and this is how the delta queue looks like
cancel, order, release date, posting date, material, plan qty, confirm qty
blank, 100019989, 04/29/2009, blank, 4415, 50, 0
blank, 100019989, 04/29/2009, 04/30/2009, 4415, 0, 50 <----
second line
Notice the second line now has plan qty at 0 and confirm at 50. Plan should always show 50 (or whatever the plan amount is. Something doesn't seem correct here??
Now, if we change something on the order header, we get the correct plan qty of 50 (and confirmed still 50), but then the posting date is blank. So when this comes over to BW we get correct plan and confirmed qty, but posting date is blank. This really makes no sense because if you have confirmed qty populated with a quantity then you have a posting date.
Thanks!

What is differences extraction queue, delta queue and uddate queue ?

hi guru's
What is differences between extraction queue, delta queue and uddate queue ? can u describe briefly?
Thanks & Regards
nandi

Dear Prabha,
Basically when any document is posted in R/3, it is updated to the update table, from there it is taken to our delta queue for send it to BW side.
When extraction starts, data is sent to BW from delta queue. then again this cycle starts.
When you post any document in OLTP system (eg SAP R3),
say create sales order by VA01, then posting is made to application tables (VBAK/VBAP) through V1 and also to sm other tables through V2, Communication structure written to update queue/extraction queue/delta queue(directly) as per the update mode selected. V3 is always followed by V2 and we are supposed to schedule it.
From this delta queue, data is extracted by BW infopackages.
There are various update methods according to which extraction or delta queue are used, so when document posting takes place it also write data into extraction queue (through V1 update) and if we use queued delta method then this data is collected in collection run and written to delta queue and from this delta queue we request for data from BW.
There are lots of posts on SDN for this, please have a look on those.
one for your reference...
https://www.sdn.sap.com/irj/sdn/profile?userid=3507509
Hope it helps...
Message was edited by:
Ashish Tewari

Cost Center Variance and revaluation of activities at actual prices

Dear experts:
1. I'd like to know, given the complexity of setting up in customizing and entering data by users, as well as interpretting the results of variance calculations based on actual activity price calculations, I am wondering how many percentage (roughly) of SAP implementations actually use actual activity price calculation, splitting structures, and revaluation at actual activity prices at month-end.
2. Do you calculate actual activity prices for those consumed in production order via routing and revaluate to get actual production costs?
Those of you who have been on many implementations are requested to share their insights. This will help me assess how deeply I need to study AC412.
Your words of wisdom will be truly appreciated with reward of points.

Hi Mohan
Usage of SAP functionalities like actual activity price calculations, splitting structures and revaluation depends on client. If the client is sure of its impact and is confident of ensuring posting correct data they use it. If the client has an environment where they cannot enforce or control activity confirmation corrections in plant, the costing guy does not go for these functionalities. There are two situations
1) Actual activity qty is entered and costing is done with plan prices, in which case the variance is purely quantity variance
2) Else plan qty is consdered as actuals and also the price, in which case no activity cost variance occurs
Or u can do following
The usage of these functionalities are purely dependent on client
Where accuracy of data is ensured u can use the above functionalities and yes we calculate actual activity prices and also revaluate the production orders at month end to get actual production costs
Pls assign points if the above helped ur cause

Difference between delta load and full load

HI,
i am getting confused with full load and delta load.
The scenario is as follows:
I have 4 records which i need to pass to DSO.(Standard DSO)
These are the fields and records.
IO_amount          io_QTY         0UNIT     0CURRENCY     Matnr
1519     195     EA     USD     MM01
2643.85     12     EA     USD     MM02
3580.4     10     EA     USD     MM03
6049.8     12     EA     USD     MM04
Now i need to change the record as
IO_amount          io_QTY         0UNIT     0CURRENCY     Matnr
1500     195     EA     USD     MM01
2643.85     12     EA     USD     MM02
3580.4     10     EA     USD     MM03
6049.8     22     EA     INR     MM04
When i passed it as full and delta load but could not make out any difference..
I can see the data only in active data and change log tables.how can i see that in DSO?
please help out,Points for sure.

Hello Susmitha,
You are right & your view of data is also correct
But only thing here is ODS which you are using mait have Overwright option in its Update Rules /Transformations
Here Q is
Which fields are in KeyFields in DSO Design
If
this Field Values are same in Delta are Full Upload
it will overwrite the records in ODS / DSO
If not
it will add the records to DSO /ODS
Comming to Delta & Full Loads
If you use Full always all data Present will be loaded
if you use Delta always changed & New records will be updated
This happens through Pointers Set ( Snap Shot of Previous Load )
Some tables where you can see RSOLTPSOURCE,RODELTAM etc
Try to wiew this ,Its tough to get
Thanks
Hari

Depreciation, delta areas and revaluation

Similar Messages

Maybe you are looking for