Error Message encountered AAPO189 for Fund Account Assignment Object

[former_member337453]

Dear All,

When I try to acquire asset through T-Code F-43 in ECC 6.0, I receive the following error:

Account object Fund differs from that in asset master record

Message no. AAPO189

Diagnosis

Account assignment object Fund with its value PTFUND1 is not the same as the value entered in the asset master record.

System Response

The system keeps the current account assignment object Fund with the value PTFUND1, or the posting is rejected.

Procedure

Check the account assignment.

I have checked and followed the solution provided for Thread: Unable to Acquire Asset in ECC 6.0 as below:

-

---

"Please go to SPRO -> Financial Accounting -> Asset accounting -> Integration with GL -> Additional account assignment objects

Select KOSTL -> Please click on the top on "EDIT" -> Change fields contents -> Agreement indicator for KOSTL.

This would remove the indicator for Agreement.

Once the indicator is removed, you will be able to acquire assets."

-

---

I did it for Fund GEBER, but the same error appears.

Please advice.

Thanks a lot.

Regards.

[former_member184992 · Accepted solution]

Hi Jimmy,

If the agreement field is not the reason, the cause of error AAPO189 might be that in Customizing of Asset Accounting in the Integration with G/L under node 'Change the Field Status Variant of the Asset G/L Accounts' you have the status of field GEBER set to 'required'.

This needs to be suppressed or set to 'optional' in order for AAPO189 not to be raised from the system, i.e. so that no check regarding the fund takes place.

Both solutions (agreement check and field status variant) solved 99% of similar cases, I hope that solve yours too

Best Regards,

Vanessa Barth.

[former_member337453 · Accepted solution]

The Client has indicated that their current system has to set "Fund" field as required for the Field Status Variant so that it is always required for Transaction Postings.

I have suppressed it in the Asset master data however.

Maybe I will display it as optional and see what happens..

THanks all for the various suggestions and help.

[former_member184992 · Accepted solution]

Hi Jimmy,

I am glad that my suggestions will be considered by you and your client.

It should resolve the issue and if you set as optional I think is an intermediary solution, and more flexible than supress.

Have a nice day !

Kind Regards,

Vanessa Barth.

[Former Member]

Hi,

According to my experience this meesage could be misleading. If the error is caused by the 'Agree' indicator for Fund you should get AAPO190 with the mentioned text. If AAPO189 comes up with the same text as AAPO190 (error for Fund), most likely it is caused by the 'Agree' indicator for Funds Center. This is because your FMDERIVE probably derives Fund from the Funds Center. So, go ahead and remove the 'Agree' indicator for funds Center and test it again.

You might want to give it some thoughts in terms of what that means to your organization if the asset aquisition postings have different FM account assignment than that of asset master. It was not an acceptable practice for my business owner.

Thanks,

Ming

[meet_waseem]

Dear Minghong Ji,

I am facing the similar issue as trying to purchase the asset with Vendor through F-90 but getting error message no: AAP0190.

I read your above comments and looking for your best recommendation in order to deal with AAP0190.

I have already set derivation rules in FM for asset accounting.

Notably Funds Center in asset master records is same as if you match it with Funds Center derived in FMDERIVE.

I have checked and compared Funds Center by clicking MEHR button during processing F-90 as below:

Screenshot below is from FMDERIVE.

and this screen shot from Asset master record (to compare account assignments being derived as per derivation rules set).

Looking for your advise (preferring to keep account assignments derived as automatic).

Regards

[former_member184992]

Hello Jimmy,

As you know, in Enterprise releases, cost object determination in asset accounting has changed a lot.

The account assignment objects have to be activated explicitly in Customizing and allowed entries have to be defined for respective account assignment rules:

You can find this new customizing in:

SPRO -> Financial Accounting -> Asset Accounting ->

Integration with the General Ledger -> Additional Account Assignment

Objects

Here you will find all the object active for asset accounting (like cost center, orders, functional area and so on).

If you set the flag 'agreement' it means that you want to prevent the account assignment object being changed when account assignment is made. This ensures that account assignment is only possible to

the account assignment object entered in the asset master record.

As per your information you have changed this for Fund GEBER but the message stays clearly that you need to do this.

Somehow it seems that this is not being fullfilled so error AAPO189 is displayed.

This is really strange, all similar cases was solved with the same that you did (uncheck the 'Agreement' box) , as follow:

You can 'untick' the field 'agreement' by doing the following:

Asset Accounting -> Integration with the General Ledger -> Additional Account Assignment Object -> Activate Account Assignment Objects

Menu:

> Edit, Change field selection. Turn off indicator for 'Agreement'

for GEBER.

Error message AAPO189 always indicates wrong customizing. Therefore please check all settings as described in note 684659, specially point 6. Maybe it is something else missing in your customizing. Therefore, please kindly check the note with your customizing settings.

I hope it helps you.

Best Regards,

Vanessa Barth.

[iklovski]

Hi,

Check the following note 437076.

Regards,

Eli