SAP ABAP IMG Activity FAA_TTY_AREALIMITTN (BAdI: Restrict Transaction Types to Depreciation Areas)
Hierarchy
☛ EA-FIN (Software Component) EA-FIN
   ⤷ FI-AA-AA (Application Component) Basic Functions
     ⤷ FAA_CUS_IMG (Package) Everything Related to the IMG
IMG Activity
ID FAA_TTY_AREALIMITTN BAdI: Restrict Transaction Types to Depreciation Areas  
Transaction Code S_EE7_91000002   IMG Activity 
Created on 20130821    
Customizing Attributes FAA_TTY_AREALIMITTN   BAdI: Restrict Transaction Types to Depreciation Areas 
Customizing Activity FAA_TTY_AREALIMITTN   BAdI: Restrict Transaction Types to Depreciation Areas 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FAA_TTY_AREALIMITATION    

Use

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

In new Asset Accounting, it is not necessary to restrict transaction types to depreciation areas (exceptions: revaluation and investment support). This is not necessary since, when you enter a transaction, you can restrict it to a depreciation area or ledger group. 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.

Requirements

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

Standard settings

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

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

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

See also

Method: FILTER_AREAS_TO_BE_POSTED

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20130912 
SAP Release Created in