Do you have any question about this error?
Message type: E = Error
Message class: 06 -
Message number: 667
Message text: Sequence & does not exist
In the step <ZH>Define sequence</>, no entry was made with the sequence
&V1&. For this reason your input is not allowed.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Use the input help to choose a valid entry.
Error message extract from SAP system. Copyright SAP SE.
06667
- Sequence & does not exist ?The SAP error message "06667 Sequence & does not exist" typically occurs in the context of document processing, particularly when dealing with document numbers or sequences in SAP. This error indicates that the system is unable to find a specific sequence number that is expected for a particular operation, such as creating or processing a document.
Causes:
- Missing Number Range: The number range for the document type you are trying to use may not be defined or may have been deleted.
- Incorrect Configuration: The configuration for the document type or number range may not be set up correctly in the system.
- Document Type Not Defined: The document type you are trying to use may not be defined in the system.
- Authorization Issues: The user may not have the necessary authorizations to access the number range or document type.
- System Migration or Changes: If there have been recent changes or migrations in the system, the number ranges may not have been properly migrated or configured.
Solutions:
Check Number Range Configuration:
- Go to transaction code SNRO (Number Range Objects) and check the configuration for the relevant number range object.
- Ensure that the number range is defined and active for the document type you are working with.
Define Number Range:
- If the number range does not exist, you may need to create it. This can be done in transaction code SNRO or OBA7 (for financial documents).
- Make sure to define the intervals correctly.
Check Document Type Configuration:
- Use transaction code OBD2 (for document types) to check if the document type is correctly configured and linked to the appropriate number range.
Authorization Check:
- Ensure that the user has the necessary authorizations to access the document type and number range. This can be checked with the help of your SAP security team.
Consult SAP Notes:
- Check for any relevant SAP Notes that may address this specific error. You can search for notes in the SAP Support Portal.
System Logs:
- Review system logs for any additional error messages or warnings that may provide more context about the issue.
Related Information:
If the problem persists after checking the above points, it may be necessary to involve your SAP Basis or technical team for further investigation.
Get instant SAP help. Start your 7-day free trial now.
06666
Special proc. type & not allowed with external procurement
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
06665
Not all chosen items could be taken into account
What causes this issue? A condition record has already been created for a contract item.System Response The system issues an error message and will ...
06668
No condition types found
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
06669
No condition types with access sequences found
What causes this issue? No <GL:access_sequence>access sequences</> have been defined for the <GL:condition_type>condition types<...
Click on this link to search all SAP messages.