SAP ABAP Data Element UC_DEFACC (Use Assignment as the Default)
Hierarchy
☛ SEM-BW (Software Component) SEM-BW: Strategic Enterprise Management
   ⤷ FIN-SEM-BCS (Application Component) Business Consolidation
     ⤷ UCT4 (Package) SEM-BCS: Target Account Assignment
Basic Data
Data Element UC_DEFACC
Short Description Use Assignment as the Default  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type X    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Default 
Medium 15 Default value 
Long 20 Default value 
Heading 10 Default 
Documentation

Definition



Use

This indicator determines how the subassignment of an item is posted:

  • If the indicator is selected, the values you specify for the subassignment are default values. When the item is posted manually or automatically, the system tries to derive the value for the subassignment from other information (for example, from other document line items). If this is unsuccessful, the system uses the value that has been specified for the item.
  • If you do not select the indicator, the system always uses the value of the subassignment that has been specified for the item. Then the system does not try to derive the value of the subassignment from other information.

Example

Example: Automatic Posting Items

Suppose you define the selected item for postings to "Clearing - Balance Sheet" and "Clearing - Income Statement". For this, you specify an item that is broken down by transaction types. Then you can enter a debit transaction type and, if desired, a credit transaction type. For "Debit" you specify transaction type 120 and you leave "Credit" blank.

  • You select the default indicator:
    • Suppose you post an entry that affects net income and specify transaction type 125 in all of the line items. In this case, the transaction type for the automatic posting item "Clearing - Balance Sheet" and "Clearing - Income Statement" is unambiguous: The automatic line item is posted with transaction type 125.
    • Suppose you post an entry that affects net income and consists of two line items. For the one line item you specify transaction type 125 and for the other line item you specify transaction type 135. In this case, a default value is used for the transaction type for the automatic posting item "Clearing - Balance Sheet" and "Clearing - Income Statement" because the transaction type cannot be uniquely derived from the other line items. In this example, the system uses transaction type 120, which was specified for the selected item. If no transaction type is specified for the selected item, the system uses the general default value for the transaction type.
  • You do NOT select the default indicator:

    Suppose you post an entry that affects net income. No matter which transaction types are entered in the various line items, the automatic posting item "Clearing - Balance Sheet" and "Clearing - Income Statement" is always posted with transaction type 120.

Example: Interunit Elimination

You define a method for the elimination of interunit payables/receivables. All payables and receivables items as well as the item for other differences are broken down by transaction types. You specify transaction type 120 for the differential item.

The reported data consists of payables and receivables with transaction types 121 and 122.

  • You select the default indicator for the differential item:
    • The differences are determined per transaction type. Thus, two differences are recorded: one for transaction type 121 and one for transaction type 122.
    • You add a receivable item, which has no breakdown by transaction type, to Selection 1; data has been reported for this item, as well. In this case, the system records three differences: one each for transaction types 121 and 122, and an additional difference with transaction type 120, which resulted from the receivable item you added.
  • You do NOT select the default indicator for the differential item:

    Only one difference is recorded. This difference is posted with transaction type 120.

Dependencies

When it is possible to maintain the default indicator for the subassignments when you maintain a selected item in the consolidation workbench, then the following dependencies generally exist for the breakdown types of the subassignments:

  1. Optional breakdown:

    If the subassignment is defined as an optional breakdown, you are not required to specify the subassignment. In this case, note that if the default indicator is not selected, the system posts an initialized value for the subassignment when the respective consolidation function (such as posting) is executed. If the default indicator is selected and the system cannot derive the value of the subassignment from other information, the subassignment is posted with an initialized value.

  2. Required breakdown:

    Note the following if the subassignment is defined as a required breakdown:

    1. The default indicator is selected:
      2. In this case, you do not need to enter a subassignment if a general default value exists. If there is no general default value, then you are required to specify a subassignment. When a consolidation function is executed, this subassignment is used for posting the item if the subassignment cannot be derived from other information.
    2. The default indicator is not selected:
      3. In this case, you are required to enter a subassignment. When a consolidation function is executed, this subassignment is used when posting the item.

History
Last changed by/on SAP  20041006 
SAP Release Created in 3.0A