SAP Knowledge Base Article - Public

3785456 - Error – Owner GLN Missing In Envelope

Symptom

Messages are shown as Error or Failed status with the Status Description: javax.script.ScriptException: java.lang.Exception: java.lang.IllegalStateException: 0033: Internal Server Error@ line 558 in readPartnerDirectory.groovy, cause: java.lang.IllegalStateException: 0033: Internal Server Error

Environment

SAP Traceability Hub

Cause

• The message fails because the Owner GLN is missing in the message envelope.
 
• Since the Owner GLN is not provided, partner determination fails and the system returns error 0033: Internal Server Error.
 
• Example from the failed payload:
 
<message>
<id>1A76FF233B071FD19EA604DC5CC00E88</id>
<owner agency="GS1" scheme="GLN"/>
</message>

Resolution

• To avoid message failures, ensure that a valid Owner GLN is maintained in the message envelope.
 
• Regenerate and resend the message after correcting the Owner GLN value.

• Verify that the Owner GLN field is maintained in the source system.
 
• Review the payload and confirm that the Owner GLN is not empty.
 
• Ensure the corresponding GLN is correctly maintained in the business master data.

Keywords

Message failed, 0033 Internal Server Error, Owner GLN missing, readPartnerDirectory.groovy, Partner determination, SAP Traceability Hub, ICH envelope, Owner GLN not maintained, GLN missing. , KBA , IS-LS-TH-NET-SCP , SAP Traceability Hub Message Exchange Issues SNR and EPCIS , IS-LS-TH , SAP Traceability Hub , Problem

Product

SAP Traceability Hub all versions