How To Fix OT432 - Package &1 must be signed with test certificate or signed

OT432 - Overview

• Message type: E = Error

• Message class: OT - SAP Online Correction Support (SOCS)

• Message number: 432

• Message text: Package &1 must be signed with test certificate or signed

What causes this issue?

You have tried to lock package &V1& in status "New" without signature.
This is not possible if the package is not signed.

System Response

The system cancels the required action.

How to fix this error?

At least one of the following activities must be executed when locking a
package:
Execute the signature. This locks the package and executes the digital
signature with the final certificate. This information is then
replicated on the SMP.
Lock the package and select "Test Signature" or "Final Signature". The
digital signature is executed as part of this action using a test
certificate or final certificate. This information is then replicated on
the SMP.

Procedure for System Administrators

Select one of the actions named above.

Error message extract from SAP system. Copyright SAP SE.

OT432 - Details

• The SAP error message OT432 indicates that a package (or transport request) must be signed with a test certificate or must be signed in general. This error typically arises in the context of SAP transport management, where packages or transport requests need to be properly signed to ensure their integrity and authenticity.
  
  Cause:
  
  Unsigned Package: The package or transport request has not been signed, which is a requirement for it to be transported between systems (e.g., from development to quality assurance or production).
  Missing Test Certificate: The system is configured to require a test certificate for the package, and it is either missing or not properly configured.
  Transport Layer Configuration: The transport layer settings may not be correctly set up to allow for the signing of packages.
  
  
  Solution:
  
  
  Sign the Package:
  
  Go to the Transport Organizer (transaction code SE09 or SE10).
  Locate the transport request/package that is causing the error.
  Right-click on the transport request and select the option