SAP ABAP IMG Activity SIMG_CFMENUORFAVOR71 (Define Transaction Types for Manual Depreciation)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM (Application Component) Customer Relationship Management
     CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       AC (Package) Application Development R/3 Assets: Customizing
IMG Activity
ID SIMG_CFMENUORFAVOR71 Define Transaction Types for Manual Depreciation  
Transaction Code S_ALR_87009094   IMG Activity: SIMG_CFMENUORFAVOR71 
Created on 19981222    
Customizing Attributes SIMG_CFMENUORFAVOR71   Define Transaction Types for Manual Depreciation 
Customizing Activity ORFA_BEWEG_AUSSER   Define Transaction Types for Unplanned Depreciation 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CFMENUORFAVOR71    

Manual corrections to values, such as

  • unplanned depreciation
  • other manually planned depreciation (ordinary or special depreciation) and
  • write-ups

are made by posting in Asset Accounting. In this step, you define the transaction types for the manual value corrections. In addition, you can specify that certain transaction types propose only certain depreciation areas for posting. The system then generates a popup window showing the depreciation that can be posted in the posting transaction. If you want to specify that all depreciation areas should always be posted, you do not need to carry out this step. The popup window then does not appear in the posting transaction.

Transaction types classify the varying business transactions in Asset Accounting. Every transaction type is assigned to a specific transaction type group. The transaction type groups are fixed in the system, and cannot be expanded (or changed) by the user. You have to enter a transaction type for every posting transaction that involves Asset Accounting. The posting transaction is controlled by the features of the transaction type, and the respective transaction type group.

Requirements

You must have defined your own chart of depreciation.

Standard settings

SAP provides transaction types for manual depreciation.

Recommendation

You should use the standard transaction types. You do not have to do anything else here in that case. However, if the scenario below applies to you, it may be necessary for you to define your own transaction types:

You need transaction types

  • that only post to certain depreciation areas in your chart of depreciation and
  • there are no corresponding standard transaction types that have the limitations you need.

Activities

  1. Create new transaction types according to your requirements. When you create the three-letter key for the transaction type, use the letter X, Y or Z somewhere in the key. Using one of these letters (at any position in the key) will prevent your key from being overwritten by future SAP updates.
  2. Define the characteristics of the new transaction types in the detail screen.
  3. Limit your transaction types, if necessary, to certain depreciation areas.

    If you do not make any selections, then all depreciation areas will be posted at all times.

Further notes

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 3   Nonrequired activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG SIMG_CFMENUORFAVOR71 0 HLA0001311 O  
SIMG SIMG_CFMENUORFAVOR71 1 HLA0001301 O  
SIMG SIMG_CFMENUORFAVOR71 2 HLA0001303 Manual Depreciation 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
V_TABWT_01 V - View AO78 Define Transaction Types for Unplanned Depreciation 
V_TABWA C - View cluster OAXE Limit Transaction Types to Depreciation Areas 
History
Last changed by/on SAP  20000505 
SAP Release Created in