Do you have any question about this error?
Message type: E = Error
Message class: IAOM - Account Assignment Manager Messages
Message number: 028
Message text: Object not known in CO
You want to post to the object with technical key &v1& belonging to the
<DS:GLOS.31CE1B848009D511BCBC0800060D9C68>business scenario</> &v2&.
However, there is no
<DS:GLOS.3526B5B0AFAB52B9E10000009B38F974>Controlling object</>
assigned to this object.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
INCLUDE NA_ALLG_NOVERARBEITUNG OBJECT DOKU ID TX LANGUAGE ENExample:
You bill an order item in an external system and transfer the billing
document to Accounting. An error occurs when the
<DS:GLOS.3526B886AFAB52B9E10000009B38F974>CO account assignment</> is
determined because the order item is not yet assigned to a Controlling
object. The error occurs either when the order item is transferred to
Accounting, or while the transferred order item is being processed:
Check the transfer log for the <ZH>order item</> in the external system,
and start the transfer of the order item again.
Then start the transfer of the <ZH>billing document</> to Accounting
again.
Error message extract from SAP system. Copyright SAP SE.
IAOM028
- Object not known in CO ?The SAP error message IAOM028: Object not known in CO typically occurs in the context of Controlling (CO) when the system cannot find a specified object, such as a cost center, internal order, or other controlling objects. This can happen for various reasons, including data entry errors, missing master data, or configuration issues.
Causes:
- Incorrect Object Code: The object code entered may be incorrect or misspelled.
- Missing Master Data: The object (e.g., cost center, internal order) may not exist in the system or may not be activated.
- Data Deletion: The object may have been deleted or archived in the system.
- Authorization Issues: The user may not have the necessary authorizations to access the object.
- Configuration Issues: There may be issues with the configuration of the controlling area or the object type.
Solutions:
- Verify Object Code: Check the object code you are entering for typos or errors. Ensure that it is the correct code for the intended object.
- Check Master Data: Use transaction codes like KS03 (Display Cost Center) or KO03 (Display Internal Order) to verify if the object exists in the system.
- Recreate Missing Objects: If the object is missing, you may need to create it again using the appropriate transaction (e.g., KS01 for cost centers, KO01 for internal orders).
- Check Authorizations: Ensure that the user has the necessary authorizations to access the object. This can be checked with the help of your SAP security team.
- Review Configuration: If the issue persists, review the configuration settings for the controlling area and the specific object type to ensure everything is set up correctly.
- Consult Documentation: Refer to SAP documentation or help files for additional context on the error and potential fixes.
Related Information:
By following these steps, you should be able to identify the cause of the IAOM028 error and implement a solution.
Get instant SAP help. Start your 7-day free trial now.
IAOM027
Hierarchy level &2 not defined in business scenario &1
What causes this issue? In <DS:GLOS.31CE1B848009D511BCBC0800060D9C68>business scenario</> '&v1& ', <DS:DE.IAOM_OBJEC...
IAOM026
Errors in prerequisite object &3 &4
What causes this issue? You want to determine a <DS:GLOS.3526B5B0AFAB52B9E10000009B38F974>Controlling object</> for &V1& &V2&...
IAOM029
&1 &2 is not controlling-relevant
What causes this issue? In Customizing for the Controlling integration for the <DS:GLOS.31CE1B848009D511BCBC0800060D9C68>business scenario</...
IAOM030
Error occurred during creation of object number
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
Click on this link to search all SAP messages.