SAP ABAP Data Element UC_BREAKDOWN_TXT (Breakdown Type)

Hierarchy

☛ SEM-BW (Software Component) SEM-BW: Strategic Enterprise Management
   ⤷ FIN-SEM-BCS (Application Component) Business Consolidation
     ⤷ UCMI (Package) SEM-BCS: Item, Breakdown Cat., ...

Basic Data

Data Element	UC_BREAKDOWN_TXT
Short Description	Breakdown Type

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	TEXT60
Data Type	CHAR	Character String
Length	60
Decimal Places	0
Output Length	60
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	Brkdn.Type
Medium	15	Breakdown Type
Long	20	Breakdown Type
Heading	2	BT

Documentation

Definition

Determines whether you can break down an item (to which a breakdown category has been assigned) by the subassignment during data entry or posting.

Use

For each subassignment you can define a breakdown type within a breakdown category.

The following breakdown types are available:

• If you do not specify a subassignment in the breakdown category, or if you specify breakdown type 0 (no breakdown) for a subassignment in the breakdown category, then the associated items cannot be broken down by the subassignment.
• If you specify breakdown type 1 (optional breakdown) for a subassignment in the breakdown category, then you can break down the associated items by the subassignment; but it is also possible not to break down the items by the subassignment. The values permitted for the subassignment are all values permitted by the data type of the subassignment, including the initialized (blank) value.
• All other breakdown types (2, 3 and 4) make the breakdown mandatory, that is, the associated items must be broken down by the subassignment; the initialized value is not permitted for the subassignment. These required breakdown types differ as follows:
• If you specify breakdown type 2 for a subassignment in the breakdown category, then a value does not need to be specified for the subassignment. If no value is specified, the system uses the general default value.
• If you specify breakdown type 3 for a subassignment in the breakdown category, then a value must be entered for the subassignment. Manual transactions, such as data entry or manual posting, prompt you to enter a value. Automatic posting produces an error message.
• If you specify breakdown type 4 for a subassignment in the breakdown category, then a value must be entered - just like breakdown type 3. However, the general default value is not permitted.

Special Considerations:

• If a subassignment has no general default value, breakdown types 2 and 3 are not permitted.
• Only breakdown types 0 and 3 are permitted for subassignments that have a breakdown category with a fixed value.
• Note the following for subassignments that belong to a compound of characteristics: If there is breakdown by the dependent characteristic, there must also be a breakdown by the independent characteristic. If the dependent characteristic has a required breakdown, the independent characteristic must also have a required breakdown.
• The subassignment "transaction currency" only permits breakdown types 0 and 2.

Dependencies

Example

• Suppose you want to break down your receivables, payables, and revenue by partner units. For these items you would specify a breakdown category that has the breakdown types 1, 2, 3 or 4 for the partner unit. Consider the following scenario:
• You want to enter revenue for each partner unit. The partner unit should always be specified for revenue. If, at first, only the total revenue is known for a consolidation unit, and the details are reported at a later date, the data entry should still be possible. To do this, you create the consolidation unit "Third Parties" and define this unit as the general default value for the partner unit. To the revenue item you assign a breakdown category with breakdown type 2 for the partner unit. Now you no longer need to enter a partner unit when entering revenues. Data entry then saves partner unit "Third Parties". Later on, when the details are reported, you can nullify the value for partner unit "Third Parties" and allocate the value to the reported partner units.
• For the receivables and payables you select a different procedure because the partner unit details are always known. You distinguish between the items for receivables/payables to/from third parties, for which you have no partner breakdown, and the items for receivables/payables to/from affiliated companies. For the latter items you define breakdown type 4 in the breakdown category because you want to prevent these items from being posted with partner unit "Third parties".
• Suppose, in Interunit Elimination, you want to allocate elimination differences to currency-related and other differences. To do this, for the items to be eliminated and the differential items you specify breakdown categories with breakdown type 2 for the transaction currency.
• Suppose you want to translate the transferred asset items with historical exchange rates. For this, you want to break down the items by the year of acquisition. To do this, you assign breakdown type 2 or 3 for the year of acquisition in the respective breakdown categories.
• Suppose you use country and region as custom characteristics, both of which are a compound of characteristics. In Characteristic Maintenance you define for both subassignments that there is no general default. Then only the breakdown types 0, 1 and 3 are allowed. Because of the compound (in which the country is the independent characteristic) only the following combinations of breakdown types are permitted:

Country    Region

0     0

1     0    <--    Here a country breakdown exists,

3     0    <--    but no regional breakdown exists!

1     1

3     1

3     3

History

Last changed by/on	SAP	20041006
SAP Release Created in	350