Do you have any question about this error?
Message type: E = Error
Message class: COINT_ERR - Cockpit for Controlling Integration
Message number: 015
Message text: Object is not recognized in Accounting
The cockpit for controlling integration was called up for an external
object that is not yet recognized in Accounting. An account assignment
object (internal order) was not created for the object, nor was a
message issued during the attempt to create an account assignment
object.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Call up the cockpit again after the creation of the account assignment
object has been started.
Error message extract from SAP system. Copyright SAP SE.
COINT_ERR015
- Object is not recognized in Accounting ?The SAP error message COINT_ERR015, which states "Object is not recognized in Accounting," typically occurs in the context of controlling (CO) and financial accounting (FI) when there is an issue with the integration between these modules. This error can arise due to various reasons, including incorrect or missing master data, configuration issues, or inconsistencies in the accounting documents.
Causes:
- Missing Master Data: The object (such as a cost center, internal order, or profit center) may not be defined in the system or may not be active.
- Incorrect Configuration: The configuration settings for the controlling area or the relevant accounting settings may not be properly set up.
- Data Inconsistencies: There may be inconsistencies between the controlling and financial accounting data, such as mismatched object types or incorrect assignment of objects.
- Authorization Issues: The user may not have the necessary authorizations to access the object in question.
- Document Type Issues: The document type used may not be compatible with the object being referenced.
Solutions:
- Check Master Data: Verify that the object (cost center, internal order, etc.) exists in the system and is active. You can do this by navigating to the relevant master data transaction (e.g., KS03 for cost centers).
- Review Configuration: Ensure that the configuration for the controlling area and the relevant accounting settings are correctly set up. This may involve checking the settings in SPRO (SAP Reference IMG).
- Data Consistency Check: Use transaction codes like KAH3 (for cost centers) or KO03 (for internal orders) to check for inconsistencies in the data.
- Authorization Check: Ensure that the user has the necessary authorizations to access the object. This can be checked in transaction SU53 or by consulting with your security team.
- Document Type Verification: Check if the document type used in the transaction is appropriate for the object being referenced. This may involve reviewing the configuration of document types in the system.
Related Information:
If the issue persists after checking the above points, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in controlling and financial accounting.
Get instant SAP help. Start your 7-day free trial now.
COINT_ERR014
Automatic check possible
What causes this issue? Several messages, which can be automatically checked or postprocessed, were triggered by an application within controlling in...
COINT_ERR013
Processing stopped without messages
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
COINT_ERR020
This cockpit jump is only available for internal order and PS project
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
COINT_ERR021
Functionality from cockpit only available for internal ordser
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.