Do you have any question about this error?
Message type: E = Error
Message class: G3 - Messages for SAP Consolidation: Integration
Message number: 105
Message text: There is not cons unit for company &2 in dimension &1
Dimension &V1& does not have an integrated cons unit that can be
assigned according to the rules for ID combination for company &V2&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Check the assignments for company &V2& in Customizing of the Enterprise
Structure, and check the rules for ID combination in Customizing of
Consolidation.
If these settings are correct, see whether a cons unit with the same ID
exists in dimension &V1&. If so, check the integration data for this
cons unit. If such data is incorrect or does not exist, you can
integrate the cons unit in cons group hierarchy maintenance afterwards.
Error message extract from SAP system. Copyright SAP SE.
G3105
- There is not cons unit for company &2 in dimension &1 ?The SAP error message G3105, which states "There is not cons unit for company &2 in dimension &1," typically occurs in the context of SAP's Controlling (CO) module, particularly when dealing with cost centers, internal orders, or other controlling objects. This error indicates that there is no corresponding "consolidation unit" defined for the specified company code in the specified dimension.
Cause:
- Missing Configuration: The most common cause of this error is that the consolidation unit has not been defined for the specified company code in the relevant dimension (e.g., profit center, cost center).
- Incorrect Master Data: The master data for the company code or the dimension may be incomplete or incorrectly set up.
- Dimension Mismatch: The dimension specified in the error message may not be correctly linked to the company code in the system.
Solution:
Check Configuration:
- Go to the configuration settings in SAP for the relevant module (e.g., Controlling).
- Ensure that the consolidation unit is defined for the specified company code in the relevant dimension.
- You may need to access the transaction codes like
OBY6
(for company code settings) orOKB9
(for cost center settings) to verify the settings.Maintain Master Data:
- Check the master data for the company code and the dimension in question.
- Ensure that all necessary entries are made and that the consolidation unit is correctly assigned.
Use Transaction Codes:
- Use transaction codes such as
KSB1
(for cost center reports) orKOB1
(for order reports) to analyze the data and see if there are any discrepancies.- You can also use
S_ALR_87013611
to check the cost center hierarchy and ensure that the consolidation units are correctly assigned.Consult Documentation:
- Review SAP documentation or help files related to the specific module you are working with to understand the requirements for consolidation units and dimensions.
Contact SAP Support:
- If the issue persists after checking the configuration and master data, consider reaching out to SAP support for further assistance.
Related Information:
By following these steps, you should be able to identify the root cause of the G3105 error and implement the necessary corrections to resolve it.
Get instant SAP help. Start your 7-day free trial now.
G3104
Account &1 (chart &2) cannot be mapped to cons chart &3
What causes this issue? No group account, which can be portrayed in consolidation chart of accounts &V3&, is assigned to account &V1&...
G3103
Item &1 (cons chart &2) is a non-recordable totals item
What causes this issue? Values should be posted to FS item &V1& in consolidation chart of accounts &V2&. However this is not possible...
G3106
No number ranges exist for document type &2 in dimension &1
What causes this issue? In dimension &V1&, no number range is maintained for document type &V2& for the realtime update. Updating doc...
G3107
No integrated cons type defined in dimension &1 (please check)
What causes this issue? The system was unable to determine the <DS:GLOS.3526B7ABAFAB52B9E10000009B38F974>consolidation type</> for integr...
Click on this link to search all SAP messages.