ABUMN - Error AA498

Hi,
When i try to transfer the asset, Am getting he error "Posting with transaction type 330 to asset 3XXXX is not allowed.
When i enter small amount it is allowing me to use transaction type, but when i use large amount i am getting this error, I think it is something related to the Amounts or perhaps tolerance, Any Clues !
Regards
FI

Hi,
Check your asset AW01N
you are trying to execute amount morethan the asset capitalization amount
Ex: overal your asset balance is $ 10000
First Aqussation $ 7000 (It is happend Previous Year)
2nd time purchanse additional lien $ 3000 ( it is happend Curernt year)
Now you are trying to transfer / retaire while using TT 330 for the amount $ > $3000
here system will accept up to $ 3000, why? your TT indicates 330 Acquiring transfer of curr-yr acquis
Please use suitable TT based on Aqustation amount
Regards
Viswa

Similar Messages

ABUMN-error "Posting transaction is not possible (Value date not allowed)"

Hi,
When we are trying to transfer asset within company code thru Tcode ABUMN, we are getting a error as
"Posting transaction is not possible (Value date not allowed)"
What actually we are doing is we are trying to transfer the previous year asset for example say 01.04.2007 assets on today.
the Parameters are as below
Document date :26.03.2008
Posting Date :26.03.2008
Asset value date is 01.04.2007.
Then the system is throwing an error and not alloing to post the previous year transfers.
Can any one help me out.
Cheers
Sri

Hi,
I think, if you give old asset value date, system will give you the error. This may be because, you are trying to transfer the assets with old values, means in your examble the dep. from the 01.04.2007 to 29.02.2008 whould have been charged.
So, give the current year date means any date from 01.01.2008 to till date.
If you read F1 help for the value date column, it states,
Asset value date
The asset value date is the value date for Asset Accounting. It can deviate from the posting and document date and be in posting periods already closed for Financial Accounting. However, the posting year and asset value date year must be the same.
Since the asset value date can have a direct influence on the amount of depreciation, the system creates a default value when it can. You can specify in Customizing how the the default asset value date is determined by the system.
Hope it helps
Saravanan.A

ABUMN error while trying to transfer asset with credit balance

I am getting "Balance in transaction currency" while trying to transfer an asset with credit balance to another asset using the transaction code ABUMN.
Please help. Will be rewarded ASAP.

Thank you very much for your reply. It is working fine when we are transfering the assets with positive balance.
The error is occuring only when we are having a negative balance.
Our config didn't have two lines for transfer variant 4(intracompany transfer not Revaluation method) as you have mentioned.It looks as:
2 * Generic entry 1 300 310
Our transfer variant 3 (Revaluation method) looks exactly as you said.
However, using 3 ( Revaluation method) is also giving me same error " Balance in transaction currency"
I don't understand why we need to have another line with relationship type as 1 ( independant company codes) since it is intracompany transfer.
I want to know if you could tranfer the negative balance on the asset. Please try to post the credit memo to the asset with ABGL T-code and get a negative balance and then do the transfer of the negative balance to some asset using ABUMN.
Please clarify.
I await your reply.
Thanks
Sri
Edited by: Sri on Jul 8, 2008 8:31 PM

ABUMN error AAPO106

Whne trying to do a transfer of an asset with transfer variant 4 and we are getting this error message.
AAPO106
Data inconsistency: mandatory posting depr. area not posted
Message no. AAPO106
Diagnosis
You tried to post to asset 0121 10004-0 using transaction type 330. According to its Customizing settings, values are required in depreciation area 01, but the current transaction does not supply any values.
Procedure for System Administration
Check your Customizing settings to see if transaction type 330 was limited to only certain depreciation areas.
I have checked the transaction types and it seems it has nothing to do with the trnasaction types. Also a few of the other transfer transactions were posted without any issues. Another thing to note is this is an individual asset attached toa group asset.
I am not sure if it has to do with configuration or if it has to do with the asset.
Any clarification is appreciated.
Thank you
Siva

Any clarification on the above.
Thanks
Siva

ABUMN Intracompnay asset transfer error AA389 Transaction type 300 not pos

Hello,
I am getting the following error message while runinng ABUMN Transaction type 300 not possible (no affiliated company specified) Message no. AA389. Transfer variant 4 (transfer within a company) code is set as follows
Rel Type               Crs-sys.ar     Rel.crsyst area     trans me              retmt tr type   acq.trasn.typ
1                                   *                generic entry              1                        300                 310
2                                   *                 generic entry             2                        300                 310
The problem is that on t-code AO76   trans type 300 Posting type has "Post to affiliated company" and "Post gross" both checked on. In Company Code Global Data my Company code and Company are the same.
Transaction type 306 has posting type "Do not post to affiiliated co." and "Post net" checked on.
I changed transfer variant 4 to have retmt transaction type of 306 for relationship type 1 and 2 instead of 300 and I do not get an error and the posted depriciation is updated correctly.
Since 300 is the recommended SAP setting in note 327088 would their be any problem if I leave it at 306?
Thanks for any answers to this issue.

Hello Murali,
Thank you for your response.
I created a new tranaction type which was a copy of 300 and clicked on
Do not post to affiliated company
Post Net
Since 300 was set up for intercompany and it resolved my issue.
Rgds,
Dan

Assets transfer using ABUMN and getting error already retired.

Hi AA Gurus
I have two assets and want to move to sub assets of another asset.e.g asset 201,202 to be transfered to 203-1,203-2.
I created sub asset using AS11.I am transferring to sub assets using ABUMN. I get ever time error as "Transaction on asset 123 203-1 not possible, retirement already in document ". This asset is not retired. So I created 2 assets fresh ( doc date ,acqusition date of today to experiment ) and then created a sub asset using As11. When I tried ABUMN for transferring it came up with
same message retirement not possible ,retirement already in doc. What is happening here ? I have checked the asset using as03 and don't see as retired ( i just created the asset ). Kindly give me some idea how to transfer two assets to sub assets of another asset.
I have checked other similar question on forum but solution did not work for me.Kindly give me some idea why this error keep coming even though asset is not retired and created today itself to test ABUMN.
Thanks in advance
Satya

Bernhard
Here are my observation and question in itlaic .Kindly suggest me what should be done.
Please go to Financial Accounting -> Asset Accounting -> Master data -> Specific Time-Independent Management of Organizational Units
Not checked for any co code.
If you set this indicator, the system manages the organizational units 'business area' and 'cost center' (and thereby 'profit center') as not time dependent in the asset master records in this company code.
Any change to these organizational units during master data maintenance then automatically generates a transfer posting document.
If the indicator is not set, you have to create a new asset master record, and manually transfer the entire asset, when the business area changes (and you are using business area balance sheets).
I am doing it manually only.I don't think that there is organizationla units change is invloved.I have two assets and I am transferring it as two sub assets of a new asset ( created for this purpose only ).All the assets are of same class.
Also, please go to Asset accounting -> Integration with GL -> Post depreciation to General Ledger -> ... -> Activate account assignment objects
Please check if assignment object KOSTL has field "BalSh" ticked.
No it is not ticked. Other two active and agreement are ticked.
Account assignment objects that are relevant to the balance sheet can no longer be changed directly in the asset master record once the asset has been capitalized. Instead, such assets have to be transferred to a new asset master record to make this change.

Error in BDC but no error in front (ABUMN convert cost center)

I use SHDB to record the ABUMN 's steps.(Convert a FIXED ASSET to another)
such as I post Asset no 10000 001 (coset center Z001) to Asset no 10000 002(Z002)
And i create normally in front , but when i run it use the session by SHDB created
the system display error.
the main reason is i choose new asset-master datacheck the subno checkbox and input a same asset no and a new asset subno, then click addition data
then the difference occurs
1..when in front ,it is OK,you can modify the new asset subno's data
2..but in BDC,the system will do a check ,it display the subno already exist, because it think the previous step have already create the new asset subno
anybody could help me?
Message was edited by:
Changsheng Shi

Hi,
When you do recording, the data record will be created in the database. When you execute or test the recording, it throws error message saying that data record already exists. The reason being is, while recording itself, the record is being created in the database and system will not allow you to create the same data record( If it is master data).
So while testing the recording in frontend, you can change the field values and test it.if it works fine, you can use the recording to make your BDC program.
But if you want to run in background, you have to make BDC program to pick the flatfile with the required field values from the presentation server and pass it to BDC screen.
Obviously you will not be giving the same data records that you have used for the recording. Then your BDC works fine in the background.
Regards,
Sai Srinivas D

ABUMN code error

Hi,
I am posting a transfer using ABUMN code, within the same company code, but when i use the exisiting asset to be posted into, i get an error msg which says the asset value date is earlier than capitlisation date.but the asset has already been capitalized and the asset value date is 6 months post the capitalisation date.
thanks
ganesh

Dear:
Refer to OSS note 310515 which says
Symptom
During the final settlement of an investment measure (order / WBS element) or during the capitalization of an independent AuC (Transaction AIBU), the system displays the following messages:
AA322 "Posting not possible (Value date earlier than capitalization date)"
AA352 "Posting not possible (Value date earlier than acquisition date)"
Other terms
KO88, KO8G, CJ88, CJ8G
Reason and Prerequisites
The first acquisition was posted to the AuC in the current year which means that the capitalization date and the original acquisition date were set in the AuC.
During reposting of the AuC, you now want to settle to capitalized assets with an earlier asset value date.
Solution
In general, it is not permitted in FI-AA to transfer an asset being retired with a value date that is earlier than the capitalization or primary acquisition date. Due to an internal program change, stricter checks have occurred here since Release 4.6.
You can avoid message AA322 by already setting the asset value date (for example, beginning of the year) for the first acquisition on the AuC or by manually resetting the capitalization date in the AuC.
Since the FI-AA logic may cause handling problems of AuC repostings, you can allow reposting by making the following modification. This modification causes the system to generate messages AA322 and AA352 regarding the AuC only as warning messages.
The modification is only effective for the reposting of AuC current-year acquisitions because this constellation can only occur in the capitalization year of the AuC. The AuC prior-year acquisitions cannot be reposted with an asset value date date earlier than the capitalization date or original acquisition date of the AuC because the asset value date and the posting date must not be in different fiscal years (if you specify an asset value date in the previous year after the capitalization date and the original acquisition date of the AuC, the system displays error message AA310 ("Enter asset value date in the same year as posting date &.
Regards

AAPO 176 Error in ABUMN transaction

Hello Experts,
I have a problem in ABUMN (Transfer within company code) transaction.
In ABUMN, I choose "From cur.yr.acq" and partial transfer option.
Then I got AAPO 176 error and it said "Transaction type 250 cannot be used for activity 'Retirement from intracompany transfer".
But, I don't know where this message comes from and how to solve this issue.
Thank you for your help in advance.
BR,
Chris Kim

Hi,
in my experience following reasons:
- Transfer variant: note 327088 Point a
- Table TABWD: (SE16 TABWD TCODE ABUM*) Note 196012
- Transaction type: Tr. AO74
Regards Bernhard

AFAB Asset Depreciation Error KI 260 Even After ABUMN

Hi all,
We still cannot execute the SG01 deprecitation run due to error occurred. We are still trying to figure and will need time to wait till tomorrow after talking to solution architects.
Background:
1.     Executed AFAB for SG01 P4 2011
2.     Erorr: KI260 Asset 30001330 tagged to cost centre SG010042 (CCA ****42 is blocked)
3.     As CCA is not allowed to opened, we ABUMN asset 30001330 to new asset 30001828 => document 100000043
4.     Re run AFAB, still the same error
Hope someone can help.
Regards
Kenneth
Edited by: Kenneth Lee on Apr 11, 2011 3:35 PM
Edited by: Kenneth Lee on Apr 11, 2011 3:38 PM

Hi Bernhard,
Actually the cost centre was blocked by users intentially.
in config, change of cost centre is laso block as per business requirement.
Kindly share if ABUMN has been done, this should sovle the problem but test run for AFAB still show the same.
Regards
Kenneth

Error in ABUMN: Line Item Schema SAP_RET_XX0 is not defined

Hello Guru,
I have one problem when doing asset transfer (ABUMN) within same company code, because we want to drop some of depreciation areas. And in the new asset those depreciation areas are not existing. When I was trying to run ABUMN and simulate, the error came. Message no AC598 "Line Item Schema SAP_RET_XX0 is not defined". I tried to look in OSS Note, I found that error but the solution is for 4.0 while we are using 4.7 already but still the error is happening.
Please share whether you ever faces the error like this before.
Thanks in advance.
Kind regards,
Dodi

Hi,
Please refer to Note 703302 - Error AC 598 SAP_RET_RU0 is missing if it helps.
Summary
Symptom
Message AC 598 "Line item schemes are not found." is issued when trying to create assets postings with activity types 230, 300.
Other terms
SAP_RET_RU0 SAP_RET_RU1
Reason and Prerequisites
Line items schemes SAP_RET_RU1, SAP_RET_RU0 are incorrect. This is an error in the standard delivery for Russia.
Solution
Delete two records in the table T093H using transaction SE16 with the following data: LAND1 GLAFABER BWASL BUZSM
RU * 230 SAP_RET_RU1
RU * 300 SAP_RET_RU0
Header Data
Release Status: Released for Customer
Released on: 03.02.2004 14:58:55
Priority: Recommendations/additional info
Category: Customizing
Primary Component: XX-CSC-RU-FI Financial Accounting
Secondary Components: XX-CSC-RU Russia
Releases
Release Independant

ABUMN posting error

Hi,
When I am using ABUMN to tranfer one asset to another asset ordinary depreciation in value adjustments column is updated in 01 depreciation area. I need to update in the 10 depreciation area as well. But its not doing that...Please let me know is this SAP standard behaviour?? Any inputs are highly appreciated...

There is an OSS Note that lists all the ABUMN variants, and explains how they work.
You may not have set SAP to transfer from/to all depreciation areas, as someone hinted in answer.
Another thing you must check is the ODep Start dates on sender and receiver, for both your DAs.
View this on the Deprec areas tab, or on the Parameters tabs.
Since both areas show on the Deprec areas tab, I recommend it for easier viewing.
To a certain degree, the APC is truly transferred - but an asset transfer is not really a transfer when it comes to accumulated depreciation. This is said because the accumulated depreciation is actually recalculated for both assets after the ABUMN posts. So run ASKB and AFAB.
Remember that an AFAB Repeat may be necessary if the Planning run has already been processed for the month of transfer, yet before the transfer posted.
It will look like an accumulated depreciation transfer if the ODep Starts are the same for all 4 settings.
This may not be your issue, but is worth a glance. Regards

AA638 error when in Tcode ABUMN

Hi Gurus
When I am doing asset trasnfer within the company code I am getting an error:
AA638- Unplanned depreciation in area 33.
Can someone explain what is is it due to and how to overcome this ?
Thanks
Dasaradh

Hi
Depreciation area is active in that class.
But tere is a posting of Unplanned depreciation for the local reporting ( Only in Dep area 33)
How do we come over this?
Thanks

Posting of retirement/transfer not possible(error in asset)

Hi All,
this is regarding intra company asset transfer through transaction code ABUMN. The issue is like below :
Let's say asset code is 764 in 111 asset class & i am transferring this asset to 3615 in 112 asset class through ABUMN.
Actaully in 2004, a part of the asset value has already been retired with scrap.So now the requirement is complete transfer the remaining amount. So while trasfer, the error shows and not allowing to post the transaction.
There are several depreciation areas in the asset. The depreciation has been calculated for all the dep. area except 42(for US)
As this book has pending the dep. since 2004, system doesn't allow to trasfer this asset. For this purpose, i have tried AFAR, ASKB but the issue is not solved.
Kindly revert back with your valuable suggestions.
Thanks,
Raj

Hi Raj,
In most cases AA 465 is due to recalculation errors in the past on the asset in question. From your information I assume this is probaby due to depreciation area 42.
I do not know how you were able to close all following fiscal years if errors existed
on the assets with pending depreciation since 2004.
As you known, the indicator ANLC-XAFAR gives the information about errors in the calculation of depreciation.
0 No error occurred during depreciation calculation
1 Error occurred in depreciation calculation from previous yrs
2 Error occurred in depreciation calculation of current year
At this point it may be necessary to execute the report RACORR52 for the fiscal years
that may be closed now and for which the asset in question seems to have an incorrect entry for ANLC-XAFAR. You have to carefully check the asset beforehand though, to be sure that the values on the asset as such are correct as per your expectation. Only then should you consider using the correction report RACORR52.
Please review the attached note in this regard, and follow the instructions given:
103749     -   RAJABS00: Error message AU069
This report is not in your system until you manually apply this source code.
Also review SAP note 141656 as it might help, too.
I hope this information helps you further.
Kind regards,
Brigitte

ABUMN: Posting with trans.type 300 not possible (No acquisition posted)

Hello everyone,
I have seen a few threads on this topic, however I am still not finding a resolution to my issue. I am very new to the FICO configuration scene and probably need a little more hand holding than the others who have asked this question.
I am having and issue using ABUMN while transfering a Capital Investment Project (CIP Asset) under a asset class of AUC, to a standard fixed asset. The CIP has been capitalized. However, when I try to perform the transfer I am receiving the following error:
Posting with trans.type 300 not possible (No acquisition posted)
Message no. AA324
Diagnosis
Transaction type 300 belongs to a transaction type group, which can only be used to post to assets to which posting has already been performed. However, no postings have been made to this asset.
Procedure
Use a transaction type from a transaction type group, which can be used for the first acquisition to an asset.
I have read through SAP NOTE 327088 (for retirements transfer variant 4) and it just doesn't help me with the issue. I know it probably should, but I do not know enough about this process in order for it to make a whole lot of sense.
If anyone can help me with this, it would be greatly appreciated. Again, I am very new, so I will probably have several follow-up questions as well.
Thanks in advance for the help!
Rhonda

Okay...
I have finally figured this out on my own.
When trying to transfer a capital investment project asset with an AuC class (asset under construction), ABUMN is not to be used.
1st. The internal order needs to be fully settled (KO02). Create a settlement rule "FUL" for the designated fixed asset.
2nd. Run "Actual Settlement" run via KO88.
This should transfer everything from the CIP asset to the fixed asset. You can double check this via the S_ALR_87011967 - ... by Plant report. Run this report prior to performing the steps above and the money will show in the CIP asset account, run it again after the above steps. The CIP should be zeroed out and the fixed asset should now carry the amount.

ABUMN - Error AA498

Similar Messages

Maybe you are looking for