cancel
Showing results for 
Search instead for 
Did you mean: 

Automatic Posting in different depreciation area (4.7 and 6.0)

Former Member
0 Kudos

Dear all,

I want to understand how it is possible the procedure of automatic posting in different depreciation areas.

Exemple: I post a specific movement via ABAON, and automatically the system creates another document (with sequencial number, because uses THE SAME DOCUMENT TYPE), to another depreciation area (using ASKB). And that procedure happens in 4.7 version.

Now, in different version, like ECC 6.0, the system react the same as in 4.7, but uses another method when creates the document, as I say in the next path:

Financial Accounting >Asset Accounting>Integration with the General Ledger>Post APC Values Periodically to the General Ledger>Specify Document Type for Periodic Posting of Asset Values

This is the customization part to associate the new document (another depreciation area, as I've explained before).

This step is possible to choose only one document type. But in version 4.7 (at least it is what is happening in my client) the document type is choosen according to the first document, the one, I post in ABAON (or another transaction with similar characterics).

Please anyone can help me?

Thanks in advance,

CCT

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member205041
Active Contributor
0 Kudos

Hello,

I'm not sure, but the different documents could have the following reasons:

If you have configured a depreciation area to post with posting indicator "4" or "6" the postings in this area are technically processed via "V2-update". With this update a log table is written where all successul updates of this area are stored.

When you start RAPBER2000 this log table is compared against all postings (since the last run) and if there is

any posting missing RAPERB2000 collects this missing posting.

In the document you can see the transactions:

ASKBDN: direct posting

ASKBN: RAPERB2000 makes the posting.

regards Bernhard

Former Member
0 Kudos

Hi,

Thanks for answering my question.

The problem is the transaction ACCMAP (Maintain Posting Rules for Parallel Accounting Principles), in ECC 6.0 is obsolete.

And I think this is the t-code, that permits the automatic posting using the same document type. Unlike what's happening now in 6.0, the system chooses the document type in "Specify Document Type for Periodic Posting of Asset Values".

I dont's know any other way to change this customizing action.

Do you??

Thanks in advance,

CCT

former_member205041
Active Contributor
0 Kudos

Hi,

there is indeed a difference between older releases and the new release. I your old systems you have the tr. ACCMAP where you make the setting "post direct". Additionally you have to made the settings in OADB (2 Post assets periodically in General Ledger).

Now the ACCMAP is obsolete - you are right. In new releases all this settings have to be done in OADB.

Here you have the following possibilities:

0 Area Does Not Post

1 Area Posts in Realtime

2 Area Posts APC and Depreciation on Periodic Basis

3 Area Posts Depreciation Only

4 Area Posts APC Directly and Depreciation

5 Area Posts APC Only

6 Area Posts Only APC Directly

If you have T093-BUHBKT = 4 or 6, it is the same than bevor ACCMAP = post direct.

Do not hestiate if you have furhter questions.

Best regards Bernhard

former_member205041
Active Contributor
0 Kudos

Addendum:

The options in ECC 6.0 are:

0 Area Does Not Post

1 Area Posts in Realtime

2 Area Posts APC and Depreciation on Periodic Basis

3 Area Posts Depreciation Only

4 Area Posts APC Directly and Depreciation -> V2 update

5 Area Posts APC Only

6 Area Posts Only APC Directly -> V2 update

If in the area is set the posting indicator 4 or 6 (V2) than it means it's a virtual posting (like 'post direct'). The postings in those area area technically processed via "V2-update". With this update a log table is written where all successul updates of this area are stored.

When you start RAPBER2000 this log table is compared against all postings (since the last run) and if there is any posting missing RAPERB2000 collects this missing posting.

This means, if in background for some reason, that we cannot tell in retrospect, there was an update error, or an error occurs due to missing customizing (please check you ASKBN posting in transaction ARAL which should tell what happened during your posting) ASKBN will pick up the outstanding posting and created/posts the FI document.

In your case the difference might be that This documents is posted either directly per V2 posting (=realtime) or later with RAPERB2000 and this causes different document types.

regards Bernhard

Edited by: Bernhard Kirchner on Oct 15, 2010 5:34 PM

Former Member
0 Kudos

Hi Bern

I have a problem with depreciatin postings

We have a Dep Area cofig below

01 Book Dep Area - USGAAP (Posts in Local Currency) - 01

15 Tax Balance Sheet

25 German HGB - 03

32 Group Dep area - USD

35 Delta Dep Area - 05

When executing the depreciation (AFAB) its posted correctly in all the Ledgers. But When we do the retirement, scrapping, or sales the accumulated Depreciation not posting in Local ledger (the asset has the different usefull lifes in 01 and 25).

We are using Std Doc Types AA and AF

What could be the problem..?

I am suffering since long.

Thank you

former_member205041
Active Contributor
0 Kudos

Hi,

Conclusion: Online posted documents use different document types to realtime posted documents.

First: the difference "online" and "direct" posting area:

The area 01 (or the investment support area) books "Online" - real time and with synchronous update.

"Online" in this context is different "direct".

Direct is quasi-real time but asynchronously, may be slightly delayed. In the best case, direct means also real-time.

However, there is a difference.

This logic for direct postings was implemented with the internal number range conversion.

So there have been some "weak points" that are now resolved that for direct postings there is always used the RAPERB - document type. Now the direct postings use always the same number range, independent if it worked or if the RAPERB makes the posting.

The "direct" posted document is completely separated from the realtime posted document.

The logic that I have explained in my last answer concerns Option 4 and 6 means: It means RAPERB makes the posting when V2 posting don't works.

This is completely different to Option 2: this means: RAPERB makes the posting.

Regards Bernhard

Edited by: Bernhard Kirchner on Oct 29, 2010 10:01 AM