Do you have a problem to log in to TecCom Portal? For login issues, please visit: Known Login Issues.
If you are not able to solve the issue, contact the TecAlliance Support Team. Please include as much information as possible, at least:
Claim ID: the claim identifier number.
Date and time of the error.
Description of the operation that produced the error.
Error code and error message text.
Internal Server Error.
Indicates an unexpected server-side error during request processing.
This error can be caused for several common reasons:
Failures in external service/API calls.
Missing configuration or required resources.
Forbidden.
This error can be caused for several reasons:
User is not permitted to perform the requested operation.
User has not access to the requested resource.
Invalid argument.
Error occurs when one or more provided arguments are invalid or not accepted by the function or API.
Invalid model.
Model has one or more validation errors.
Unsupported token type.
Invalid token data.
Token does not contain Claim Id nor Linked Id.
Entry to delete does not exist.
Entry was not found or entry with ID has been deleted.
Prohibited deletion.
Deletion is not allowed because this entry is used by some claim.
Value greater than other.
Error occurs in comparer function when specific object values are compared.
Possible reasons:
Concurrent request.
A previous request for the same claim or entity is still being processed. Wait until it has finished and repeat the action.
Invalid value.
Occurred when value has different types to process it.
Empty value.
Occurred when value is required and service cannot process an empty value.
Not empty value.
Occurred when value is not required and service cannot process an existing value.
Invalid length.
Occurred when length does not match the expected/predefined length.
Maximum allowed length exceeded.
Occurred when length exceeds the allowed value.
Duplication value.
Occurred when there is required unique values for other objects.
Multiple currencies.
Occurred when claim has different currencies for every part.
Multiple mileage measurement units.
Occurred when claim has different mileage measurement units.
Individual info sidebar duplication value.
Values in Individual info sidebar should be unique.
Invalid operation.
The requested action is not allowed in the current state or configuration.
This error can be caused for several reasons:
Dispute creation: dispute handling is not enabled for the receiver, the receiver is not a partner, the claim is not declined or partially accepted, a dispute is already pending, the maximum dispute level has been reached, the claim category is not enabled for disputes, or the dispute window has closed.
Allowance settings: creating an exception for an unlimited base allowance, changing the currency of a base allowance that still has exceptions, or editing allowances at branch level while the headquarter controls them.
Claim actions: Request Information or Reopen on a claim from a disconnected sender, or reopening a claim while ERP integration is active.
Stock clearance: the claim is no longer in draft status.
SAP response upload: SAP is not enabled for the receiver, or the combination of document type and claim category is not configured.
Invalid captcha.
Captcha verification failed during the license request. Repeat the captcha and submit the form again.
Base allowance setting not found.
An exceptional allowance setting has no matching base allowance setting. The base setting is identified by customer, allowance group and year, and must already exist or be part of the same import.
Possible reasons:
The allowance settings import contains an exception row without its corresponding base row.
An update refers to an allowance setting identifier that does not exist.
Previous year sales and fixed amount cannot be set together.
An allowance setting specifies both Previous year sales and Fixed amount. These are two mutually exclusive ways of sizing an allowance, so only one of them may be provided.
Allowance exceeded.
The stock clearance claim exceeds the allowance configured for at least one allowance group. The allowance is derived from the allowance settings, either as a percentage of the previous year sales or as a fixed amount. Claims that carry an authorization code are not checked against the allowance.
Validation expired.
The receiver-side validation of the uploaded stock clearance article list is no longer valid. The validation period is defined in the stock clearance settings. Upload the article list again to obtain a new validation.
TecComId out of control.
The submitted branch reference does not belong to your organisation. Permitted values are the branches of your headquarter and the headquarter itself. An organisation without a headquarter may only reference its own TecCom ID.
Customer group not found.
One or more customer group names in the request could not be resolved for your organisation. The names that could not be found are listed in the error message.
Possible cases:
Allowance settings import.
CMD customer price settings import.
Customer or group exclusive.
Exactly one of Customer and Customer group must be provided for a CMD customer price setting. The error occurs when both are filled in and when both are left empty.
Invalid receiver as claim creator.
Invalid sender as claim creator.
Sender change is not allowed.
Partnership is not valid.
Flow type is not allowed for receiver organization.
Selected flow type is not valid for the receiver.
Flow sequence is not allowed.
Flow sequence already exists for given TecComId.
Claim upload limit exceeds.
Claim upload limit in Claim import exceeds the allowed value.
Total number of parts allowed exceeded.
Occurred when parts amount exceeds in scope of a single claim creation.
Maximum allowed comment length exceeded.
Total number of comments allowed exceeded.
Decision or decision info is not defined.
There is no claim decision or decision info was not found.
Excessive decision info.
Decision info for part decision type is not consistent with items decision actions.
Part has not been decided.
Service has not been decided.
Decision Action is not allowed for current flow.
Invalid claim settings.
Individual questions were not found for provided responses.
Individual questions mismatch.
Individual question and response types are different.
Invalid personalized link.
Expired or nonexistent link can't be refreshed.
Claim does not contain credit note decision
Claim does not contain credit/quality note decision.
Claim was not found.
Claim was removed or cannot be found by claim ID.
Attachment was not found.
Attachment was removed.
Claim comment was not found.
Claim settings were not found.
Possible settings:
Unsupported claim settings type.
Attachment is in use.
License was not found.
Invalid TecComId.
Invalid user.
Invalid attachment identifier.
Status change is not supported.
Total number of personalized links allowed exceeded.
Incorrect flow type.
Invalid part identifier.
Partner connection already exists.
License in TecCom already exists.
Notification subscription was not found.
Invalid license.
License is invalid or license needs to be upgraded.
Parts does not exists.
Personalized links not found.
Information is not accessible in claim creation link.
Invalid claim identifier.
Occurred when claim ID does not contain a correct value.
Possible reasons:
Claim selection empty.
Claims have group.
Claims have no group.
Claim group not found.
Claims do not belong to same group.
Claim group limit exceeds.
Claim different senders.
Claim different receivers.
Invalid claim status.
TecComId was not found.
Supplier article list not found.
Claim category invalid.
Copy setting failed.
Forwarded parts already exist.
Forwarded parts already exist in child claims.
Claim different part receiver.
The article is not available from the target receiver of the claim. Occurs when parts are added to or imported into a stock clearance claim and the article cannot be found for that receiver.
Claim different part brand.
The brand of the part does not match the target brand of the claim.
Possible reasons:
A part with a different brand is added to a claim that is split by brand.
The brand of an article in a brand-split claim could not be resolved.
The brand of the part is not one of the target brands of the claim.
Claim different plant.
The new part belongs to a different plant than the parts already in the claim. All parts of one claim must belong to the same plant. The error message names both plant identifiers.
Claim generic article restricted.
A generic article can only be added by the receiver. Senders cannot add generic articles to a stock clearance claim.
Unsupported file format.
Possible cases:
Total number of files allowed exceeded.
Possible cases:
Total filesize allowed exceeded.
Invalid image dimensions.
Requested scheme was not found.
Claim import schema was not found.
Requested image was not found.
Occurred when image is not found by link or ID.
Invalid filename.
Invalid image resolution.
Unsupported image extension.
File items limit exceeds.
Possible cases:
Invalid file signature.
The content of the uploaded file does not match its declared file type. The file may be corrupted or manipulated. Occurs on agreement document upload.
Invalid TecDoc request.
Invalid Ebay request.
Wrong parameter.
Web service internal error.
Internal error in external application (not on TecCom platform).
ERP credit note forbidden.
Erp is not allowed. It is not possible to request credit/quality note/return order.
Maximum count exceeds.
Possible error cases:
No articles in request.
CMD article conflict.
One or more article numbers match more than one article. Provide the brand or a unique article number so that the article can be identified. Occurs when parts are added to a stock clearance claim and during article list import.
Invalid web service parameter: tenant.
The connected ERP web service rejected the request because the tenant is not valid.
Error codes 410 to 424 are reported by the ERP web service of the receiver. The detailed message of the web service is shown in the portal. If the parameter looks correct, the configuration in the connected ERP system should be checked.
Invalid web service parameter: branch.
The connected ERP web service rejected the request because the branch is not valid or cannot be reached. A common cause is a branch that has been deactivated in the ERP system.
Invalid web service parameter: buyer number.
The connected ERP web service rejected the request because the buyer number is not valid.
Invalid web service parameter: article number.
The connected ERP web service rejected the request because the article number is not valid.
Invalid web service parameter: supplier number.
The connected ERP web service rejected the request because the supplier number is not valid.
Invalid web service parameter: delivery note date.
The connected ERP web service rejected the request because the delivery note date is not valid.
Invalid web service parameter: file reference.
The connected ERP web service rejected the request because the file reference is not valid. The requested attachment cannot be retrieved.
Invalid web service parameter: year.
The connected ERP web service rejected the request because the year is not valid.
Invalid web service parameter: delivery note number.
The connected ERP web service rejected the request because the delivery note number is not valid.
Invalid web service parameter: invoice number.
The connected ERP web service rejected the request because the invoice number is not valid.
Invalid web service parameter: invoice date.
The connected ERP web service rejected the request because the invoice date is not valid.
Invalid web service parameter: claim reference.
The connected ERP web service rejected the request because the claim reference is not valid.
Invalid web service parameter: article price.
The connected ERP web service rejected the request because the article price is not valid.
Invalid web service parameter: currency.
The connected ERP web service rejected the request because the currency is not valid.
Invalid web service parameter: quantity.
The connected ERP web service rejected the request because the quantity is not valid.
Integer expected.
A cell of the imported Excel document must contain a whole number. The error names the affected column and cell address.
Empty article document.
The uploaded stock clearance article document contains no data rows. At least one article row is required.
Number must be positive.
A quantity must be greater than 0. Occurs during stock clearance Excel import, where the cell address is included, and when a part is added or edited manually.
Missing order contract.
Business relation could not be updated. The required supplier contract with GOLDA or PACT is missing.