How To Fix SIPT660 - Address number &1 assigned to customer number &2 cannot be changed

SAP Error Message - Details

• Message type: E = Error

• Message class: SIPT - SIPT: Digital Signature Portugal

• Message number: 660

• Message text: Address number &1 assigned to customer number &2 cannot be changed

What causes this issue?

You tried to assign a new address number to an existing customer number.
The customer is not uniquely identified by a VAT registration number,
that is, either the number is empty or it contains a generic value.
Unless the customer is uniquely identified by a VAT registration number,
the address number cannot be changed if the customer has been used in
documents that have been posted with a Portuguese digital signature (in
a Portuguese company code or in a Portuguese organizational unit of a
foreign company code). This restriction applies to all changes,
including the correction of errors.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

The system prevents the change if the situation described under
<LS>Diagnosis </>applies.

How to fix this error?

You can do one of the following:
Create a new customer master record with the required address number.
Assign a valid VAT registration number to the existing customer master
record. Note that you must save the VAT registration number before you
change the address number.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SIPT660 - Address number &1 assigned to customer number &2 cannot be changed ?

  The SAP error message SIPT660 indicates that there is an issue with changing the address number assigned to a specific customer number. This error typically arises in the context of customer master data management within the SAP system.
  Cause:
  The error message SIPT660 occurs when you attempt to change the address number associated with a customer that is already assigned in the system. This can happen for several reasons, including:
  
  Address Assignment Restrictions: The address number is locked or restricted from being changed due to business rules or configurations in the system.
  Data Integrity Constraints: The system enforces data integrity rules that prevent changes to certain fields once they have been set, especially if the customer has transactions or dependencies linked to that address.
  Customizations or Enhancements: There may be custom logic implemented in the SAP system that restricts changes to address numbers for specific customer types or statuses.
  
  Solution:
  To resolve the SIPT660 error, you can consider the following steps:
  
  
  Check Address Assignment: Verify if the address number is indeed assigned to the customer and if it is currently in use. If it is, you may need to unassign it or change the customer’s status before making modifications.
  
  
  Review Configuration Settings: Check the configuration settings in the SAP system related to customer master data. Ensure that there are no restrictions preventing the change of address numbers.
  
  
  Consult with Business Process Owners: Discuss with relevant stakeholders or business process owners to understand if there are specific business rules that prevent changing the address number.
  
  
  Use Transaction Codes: Utilize transaction codes like XD02 (Change Customer) or VD02 (Change Customer) to attempt the change. Ensure you have the necessary authorizations to make changes.
  
  
  Check for Open Transactions: Ensure that there are no open transactions or documents linked to the customer that would prevent changes to the address.
  
  
  SAP Notes and Support: If the issue persists, check for any relevant SAP Notes that may address this specific error. You can search the SAP Support Portal for updates or patches that may resolve the issue.
  
  
  Contact SAP Support: If you are unable to resolve the issue through the above steps, consider reaching out to SAP Support for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to customer master data management, such as XD01 (Create Customer), XD02 (Change Customer), and XD03 (Display Customer).
  User Authorizations: Ensure that you have the necessary authorizations to make changes to customer master data.
  Data Consistency Checks: Regularly perform data consistency checks to ensure that customer master data is accurate and up-to-date.
  
  By following these steps, you should be able to identify the cause of the SIPT660 error and implement a solution to resolve it.