Ansicht
Dokumentation

FAA_TTY_AREALIMITTN - BAdI: Restrict Transaction Types to Depreciation Areas

Vendor Master (General Section)   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

This Business Add-In (BAdI) is used in the Asset Accounting (FI-AA) component.

In new Asset Accounting, it is genreally not necessary to restrict transaction types to depreciation areas (exceptions: revaluations and investment support). This is not necessary since, when you enter a transaction, you can restrict it to a depreciation area or accounting principle. In addition, in a posting transaction, you can select the depreciation areas to be posted. This can significantly reduce the number of transaction types that need to be defined in the system.

If you nonetheless restricted transaction types to depreciation areas (table TABWA or view cluster V_TABWA), this is ignored in the standard system.

However, using this BAdI, you can change the system behavior so that the system does take restrictions to transaction types into account.

Using this BAdI, you can influence the depreciation areas to be posted for an asset posting. The BAdI is called for each posting to an asset at the time the line items are created in Asset Accounting. Both document creation and the depreciation calculation access the results of this BAdI.

As a result of this BAdI, the number of line items to be posted can be reduced. However, it is not possible to add additional depreciation areas. Areas that are excluded by the implementation do not receive any values, and no line items (table ANEP) are written.

This BAdI is processed only if new Asset Accounting is active.

The BAdI is filter-dependent. The filter criterion is the posting transaction.

In the standard system, the BAdI is active for the transaction categories Revaluation and Investment Support. The SAP implementation uses the restrictions of table TABWA. The example implementation contains a corresponding implementation. Aside from this example, SAP does not provide a default implementation.

The BAdI can only be implemented once for each filter value. Possible filter values for transactions within Asset Accounting are:

ZUGA	Acquisition
UMZU	Acquisition from intercompany transfer
UMZI	Acquisition from intracompany transfer
ZUCO	Acquisition from CO settlement
NACH	Post-capitalization
ABGA	Retirement
UMAB	Retirement from intercompany transfer
UMAI	Retirement from intracompany transfer
AFAP	Manual depreciation posting
ZUSR	Write-up
ANZA	Down payment
AZUM	Down payment clearing
NABK	Subsequent retirement costs
NERL	Subsequent revenue

NERL

After you have called the IMG activity, proceed as follows:

1. In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.

If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.

1. In the corresponding field, enter a short text for implementation .
2. In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
3. Choose the tab Interface.

The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.

If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.

1. Save your entries and assign a package.
2. Position the cursor on a method. Call up the Class Builder by double-clicking it.
3. Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
4. Save and activate your coding, and navigate back to the screen Change Implementation.
5. Save on the screen Change Implementation.

Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.

1. Choose Activate.

When the application program is executed, the coding you have created will be run.

NERL

To display sample coding, choose Goto -> Sample Coding -> Display.

NERL

Method: FILTER_AREAS_TO_BE_POSTED

General Material Data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 6432 Date: 20240523 Time: 204212     sap01-206 ( 83 ms )