Do you have any question about this error?
Stop Googling SAP errors. Use our Free Essentials plan instead - instant AI help, no credit card needed. Start Now →
Message type: E = Error
Message class: CO - PPC order processing messages
Message number: 367
Message text: Number range & is not created for object &
The number ranges for &V2& have not been assigned to a number group.
Proceed as follows:
Call up the maintenance of number range objects.
Enter the object '&V2&' and press the function key <ZH>Number
ranges</>.
Press the function key <ZH>Maintain groups</>.
Select the menu options <ZH>Group -> Insert</>. Enter a text on the
popup (for example, production orders - internal number assignment) and
a number range. Press the function key <ZH>Insert interval</>.
Save your entry.
The system inserts the specified number range.
<DS:TRAN.SNRO>Proceed</>
Error message extract from SAP system. Copyright SAP SE.
CO367
- Number range & is not created for object & ?The SAP error message CO367 indicates that a number range has not been created for a specific object in the Controlling (CO) module. This typically occurs when you are trying to create or process a controlling object (like a cost center, internal order, etc.) and the system cannot find a defined number range for that object.
Cause:
- Missing Number Range: The primary cause of this error is that the number range for the specified object has not been defined in the system.
- Configuration Issues: The configuration settings for the number range may not have been properly set up in the system.
- Authorization Issues: Sometimes, the user may not have the necessary authorizations to access or create the number range.
Solution:
To resolve the CO367 error, you can follow these steps:
Check Number Range Configuration:
- Go to the transaction code SNRO (Number Range Objects).
- Look for the relevant number range object associated with the controlling object you are trying to create.
- If the number range does not exist, you will need to create it.
Create Number Range:
- If you need to create a new number range, you can do this in the transaction code SNUM (Number Range Maintenance).
- Define the number range intervals, ensuring that they do not overlap with existing ranges.
Assign Number Range to Object:
- After creating the number range, ensure that it is assigned to the relevant controlling object. This can typically be done in the configuration settings for the specific object (e.g., cost centers, internal orders).
- Use transaction codes like OKA0 (for cost centers) or KO01 (for internal orders) to check the configuration.
Check Authorizations:
- Ensure that the user has the necessary authorizations to create or modify number ranges. This can be checked with the help of your SAP security team.
Transport Changes:
- If you are working in a development environment, ensure that any changes made to the number range configuration are transported to the production environment.
Related Information:
Transaction Codes:
Documentation: Refer to SAP Help documentation for detailed steps on configuring number ranges and managing controlling objects.
SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide additional guidance related to number range configuration.
By following these steps, you should be able to resolve the CO367 error and successfully create or process the controlling object in SAP.
Get instant SAP help. Sign up for our Free Essentials Plan.
CO366
Status profile & not found (check entry)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CO365
Status profile & not found (check entry)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CO368
Changes to purchase req. & & not possible because of release status
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CO369
Changes in order & critical due to rel. status of requisition
What causes this issue? Order &V1& contains purchase requisitions which have the status 'released'. Once a purchase requisition is ...
Click on this link to search all SAP messages.