Do you have any question about this error?
Message type: E = Error
Message class: SIPT - SIPT: Digital Signature Portugal
Message number: 706
Message text: Lead.doc.type and series changed in Customizing for number range no. &1
You tried to post a document for which a digital signature is required.
The number of your document is derived from a number range interval for
which digital signature generation has been activated in Customizing.
The combination of leading document type and series has been changed in
the Customizing entry for the relevant number range interval. However,
this change is not permitted, because digital signatures have already
been created for documents using this number range interval.
The system prevents the posting.
In Customizing for digital signatures (Portugal), change the leading
document type and series back to the values that were originally used.
The document can then be posted.
Error message extract from SAP system. Copyright SAP SE.
SIPT706
- Lead.doc.type and series changed in Customizing for number range no. &1 ?The SAP error message SIPT706 indicates that there is a mismatch in the document type and number range configuration for a specific document type in the system. This typically occurs when the document type has been changed in the customizing settings, but the associated number range has not been updated accordingly.
Cause:
- Document Type Change: The document type for a specific transaction has been modified in the SAP Customizing settings.
- Number Range Configuration: The number range associated with the document type has not been updated or is not aligned with the new document type settings.
- Inconsistent Settings: There may be inconsistencies between the document type and the number range settings in the configuration.
Solution:
To resolve the SIPT706 error, follow these steps:
Check Document Type Configuration:
- Go to the SAP Customizing Implementation Guide (SPRO).
- Navigate to the relevant area where the document type is defined (e.g., Financial Accounting, Sales and Distribution, etc.).
- Verify the settings for the document type in question.
Check Number Range Configuration:
- In the same SPRO area, check the number range settings associated with the document type.
- Ensure that the number range is correctly defined and is active.
Align Document Type and Number Range:
- If the document type has been changed, ensure that the number range assigned to it is appropriate and matches the new configuration.
- If necessary, create a new number range or adjust the existing one to align with the document type.
Transport Changes:
- If changes were made in a development environment, ensure that they are transported to the quality and production environments properly.
Testing:
- After making the necessary adjustments, test the transaction that triggered the error to ensure that it is resolved.
Related Information:
SNRO
(Number Range Objects) to manage number ranges or OBA7
for document type configuration.By following these steps, you should be able to resolve the SIPT706 error and ensure that your document types and number ranges are correctly configured in SAP.
Get instant SAP help. Start your 7-day free trial now.
SIPT704
Deleting the entry for number range number &1 is not recommended
What causes this issue? You have deleted a Customizing entry for a particular number range number. Since the system has already digitally signed docu...
SIPT703
Digital signature for number range number &1 is inactive in Customizing
What causes this issue? You tried to post a document that requires a digital signature, but digital signature generation is not activated in Customiz...
SIPT708
Company code changed in Customizing for number range number &1
What causes this issue? You tried to post a document for which a digital signature is required. The number of your document is derived from a number ...
SIPT709
Company code &2 already used for dig. signature and must not be changed
What causes this issue? You have changed the company code that is specified for a number range number. However, digital signatures have already been ...
Click on this link to search all SAP messages.