Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

When I carry out an FI-AA posting why does the error message GU 444 (still) occur?

0
Posted

When I carry out an FI-AA posting why does the error message GU 444 (still) occur?

0

See Note 1094630 first. In certain circumstances, the error message GU 444 can still occur in asset accounting. This happens when a ledger group assigned to a depreciation area contains exactly one ledger, and this ledger is not used for the company code currently being used. However, if there are ledger groups with more than one ledger, and one of these ledgers is not used in a company code, you can still make a posting. Reason: If asset accounting permitted this configuration, values and line items would still occur in the relevant depreciation areas in FI-AA, but values would not be updated in the corresponding account / ledger. This means that the RAABST02 report would always show differences, even though there are none. Solution: – New customers / new implementation: Distribute the company codes across different valuation plans – Existing customers: All company codes of a valuation plan use the same ledger Example: 1. Ledger Company Code H1 1000 H1 2000 H2 1000 Ledger Ledger Group

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123