Hierarchy
⤷ EC-CS (Application Component) Consolidation
⤷ FC00 (Package) Cons: General consolidation (cannot be assign.to FC01-FC09)
IMG Activity
ID | SIMG_CFMENUCX01_MD30 | Define Breakdown Categories |
Transaction Code | S_ALR_87002880 | IMG Activity: SIMG_CFMENUCX01_MD30 |
Created on | 19981222 | |
Customizing Attributes | SIMG_CFMENUCX01_MD30 | Define Breakdown Categories |
Customizing Activity | SIMG_CFMENUCX01_MD30 | Define Breakdown Categories |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_CFMENUCX01_MD30 |
Depending on the FS items posted, different Subassignments are necessary for the transaction data.
For example, payables and receivables items require partner unit subassignments so that interunit payables and receivables can be eliminated. Some items require several subassignments, for example partner unit and transaction currency.
In this step, you group subassignments into breakdown categories, which you assign to FS items in their master data. Breakdown categories are defined for a particular chart of accounts.
When defining a breakdown category, the system offers you all standard subassignments and all custom subassignments. You specify the following per subassignment:
- Breakdown type
You determine through the breakdown category whether the FS item values should be expanded while creating and posting to this subassignment and how rigorously the system should check the account assignment of each subassignment. Inform yourself via the entry help about which breakdown types the system offers.
- Fixed value
When you specify an optional breakdown or a required breakdown for the subassignments Subitem category and Unit of measure, then you enter a fixed value. This means that the characteristic value of the subassignment is determined by this value, to be precise for all FS items with this breakdown category.
In exactly the same way you enter a fixed value with custom subassignments, if you have specified this in the definition of this custom subassignment (see also step Add characteristics).
- Default set
You can specify a Set for all subassignments with
optional or required breakdown, which have no fixed values. The system draws these sets from the Online-entry and the Online-entry of reported data as default values for item breakdowns, provided that you have set this appropriately.
- Fixed value
When you specify an optional breakdown or a required breakdown for the subassignments Subitem category and Unit of measure, then you enter a fixed value. This means that the characteristic value of the subassignment is determined by this value, to be precise for all FS items with this breakdown category.
In exactly the same way you enter a fixed value with custom subassignments, if you have specified this in the definition of this custom subassignment (see also step Add characteristics).
- Default set You can specify a Set for all subassignments with optional or required breakdown, which have no fixed values. The system draws these sets from the Online-entry and the Online-entry of reported data as default values for item breakdowns, provided that you have set this appropriately.
Standard settings
Various breakdown categories are preset in the standard system.
Breakdown category names consist of 4 freely definable numbers. Categories predefined in the standard system are named according to the following logic:
Position Breakdown Value per Characteristic
1 Subitem Subitem category number
2 Partner 1 (breakdown type 4) or
2 (breakdown type 3)
3 Currency 1
4 Year of acquisition 1
If a breakdown category is not intended for a breakdown by subitem, partner unit, transaction currency and/or year of acquisition, its digit has the characteristic value 0.
For example, the breakdown category "1200" has a breakdown by transaction types (subitem category 1) and a breakdown by partner units, which allows a default value.
Activities
Check the preset breakdown categories, and make any necessary additions or modifications.
Further notes
When you change breakdown categories, the system carries out consistency checks while saving. The system checks whether existing transaction data is affected. Changes could have the following effects:
- If you remove a subassignment from a breakdown category, the item values broken down by this subassignment must be balanced in the totals database. The system can do this automatically.
- If you add a new subassignment to a breakdown category, the affected transaction data must be broken down using this subassignment. According to breakdown type, the system either restarts the default value or asks you to enter values for the subassignments. According to the subassignment, it uses the following default values :
- Partner unit, subitem and custom subassignments (where the default value indicator is activated in Characteristic Maintenance):
Default value (see Customizing step Define Default Values for Subassignments) - Transaction currency: Local currency of the consolidation unit
- Year of acquisition: Valid year for the totals record
Note: you can deactivate the consistency check in step Check global system settings.
- You can not delete a breakdown category which is used by an FS item.
You can display the master data of the defined breakdown categories, for example, in order to make a printout. To print the master data, choose the Print function and enter selection criteria for the list. The system generates the list using the ABAP List Viewer. You can use the functions available in this tool to filter data or customize the display of the data columns (for more information, see the documentation on the ABAP List Viewer in the SAP Library).
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 1 | 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_CFMENUCX01_MD30 | 0 | HLA0100226 | Master Data |
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 |
CX1B | T - Individual transaction object | CX1I4 | 0000000001 | Define Breakdown Category |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |