How To Fix AU176 - Contrôle requis implémenation BAdI pr calcul amortissem. ; cf. txt descr.

SAP Error Message - Details

• Message type: E = Error

• Message class: AU - FI-AA utility program error messages

• Message number: 176

• Message text: Contrôle requis implémenation BAdI pr calcul amortissem. ; cf. txt descr.

Quelle est la cause de ce problème?

You have at least one active implementation for the Business Add-In <AB>
FAA_DC_CUSTOMER</> or <AB>FAA_EE_CUSTOMER</>.
SAP had to make technical changes. To ensure you will still get correct
values from the depreciation calculation, it may be necessary to adjust
the implementation of one or both BAdIs.
Note:
The depreciation calculation uses the result of the respective BAdI
implementation(s); it is <ZH>not</> possible to say how correct the
implementation is at this point.

Réponse du système

Le système émet un message d'erreur et ne vous permettra pas de poursuivre cette transaction tant que l'erreur n'est pas résolue.

Comment corriger cette erreur?

You might have one of the following situations:
(a) New BAdI implementation
You have created a new BAdI implementation for one of the BAdIs
mentioned above. It is a single implementation for one of the BAdIs
mentioned above.
In this case, <ZH>no</> release upgrade is responsible for the
appearance of this message, therefore <ZH>no</> steps on your part are
necessary. You can hide this message (see the section '&SYS_ADMIN&?
below for this).
(b) Existing BAdI implementation
You get this message after a release upgrade.
Proceed as follows:
Check whether your implementation(s) of the above-mentioned BAdIs are
correct. Please read the detailed information on the changed BAdIs
below.
Recalculate the depreciation again. A recalculation without differences
indicates that the implementation is correct (or that the im
plementations are correct).
After a successful check, you can hide this message (see the section '
&SYS_ADMIN&' for this).
<ZH>Detailed Information on the Changed BAdIs</>
Changes for BAdI <AB>FAA_DC_CUSTOMER</>:
Tables <AB>MTS_HLPSEG</>, <AB>MT_PARAMETER</>, <AB>MT_TRANSACTION</> and
<AB>MT_TRANSACTION_POST</> gets the <LS>currency type</> (field <AB>
CURR_TYPE</>) as a further key field.
Because of this, you should only access these tables with <LS>
depreciation area</> and <LS>currency type</> (<AB>CURR_TYPE</>). You
can find the currency type using table <AB>T093A</> or using <AB>
LEADOBJ</>.
The table <AB>MTS_AREA</> has changed; the currency type has been
included amongst other things.
In structure <AB>MS_ASSET_KEY</> the fields <AB>ASSET_MAIN_NUMBER</> and
<AB>ASSET_SUB_NUMBER</> have been replaced by structure <AB>S_ASSET_KEY
</>.
Table <AB>MT_VIRTAREA</> has been replaced by table <AB>MT_VIRTAREA_S4
</>.
For more information about the BAdI, see the documentation under
<DS:SIMG.FAA_DC_CUSTOMER>FAA_DC_CUSTOMER</>.
Changes for BAdI <AB>FAA_EE_CUSTOMER</>:
In the structure of the import parameter of <AB>ISX_IDATA</>, table <AB>
T_VIRAREA</> has become obsolete and has been replaced by the new table
<AB>T_VIRTAREA_S4</>.
In addition to this, table <AB>T_PARAMETER</> has been enhanced with
<AB>CURR_TYPE</>.
Otherwise the structures have stayed the same.
For more information about the BAdI, see the documentation under
<DS:SIMG.FAA_EE_CUSTOMER>FAA_EE_CUSTOMER</>.
Example:
The following example should illustrate the changes:
There is a posting for an asset for depreciation area 01 (with currency
type 10) and accordingly for the parallel currency area 02 (with
currency type 30).
Until now, table <AB>MT_TRANSACTION</> contained two entries: an entry
for depreciation area 01 and an entry for depreciation area 02.
From now on, table <AB>MT_TRANSACTION</> still contains two entries but
with depreciation area 01 and currency type 10, plus an entry with
depreciation area 01 and currency type 30.

Procédure pour les administrateurs système

INCLUDE AA_MESSAGE_CONTROL OBJECT DOKU ID TX

Extrait du message d'erreur du système SAP. Copyright SAP SE.