Tracelink University

Table of contents

General

Administrators assign roles that limit users' access to different functions. Depending on the role assigned, users might not see certain items in the Process drop-down or the side menu. If you cannot see a specific menu item that you should see based on a role, verify that you are assigned the correct role. If you still cannot see the appropriate menu items, work with your System Administrator to ensure that you are assigned the correct roles and permissions.

If you are looking for an item you added or for the edits you made to an item, you might not see them right away. A banner message displays that confirms your updates will display shortly. If you want to see the updates, wait a minute or two before refreshing the page, and your updates will be reflected.

Help center

There is a known issue in the documentation where some API guidelines that are exported to Excel via the Download icon display only a portion of the entire guideline. This issue will be fixed in a future revision.

There is a known issue in the documentation where the example might have extra spaces or quotation marks added if copied through a Chromium-based browser (e.g. Google Chrome, Microsoft Edge). This issue will be fixed in a future revision. For now, if this problem results in a validation error, either:

  • Manually copy the example by highlighting the full text, right-clicking, and selecting Copy.

    or

  • Use a non-Chromium-based browser (e.g. Apple Safari) to copy the example.

The table contains detailed guidelines for errors occurring in MINT and displays error banners for users. Also, the notification delivery option for the owner and partner includes workflow step failure and the cause of failure.

Error message Description

Invalid Workflow Step Encountered
  • Description - The following are the reasons for the error:
    • Ensure that only one object entry is present in the workflow or MPF.
    • Verify that all steps in the workflow are valid.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Payload Not Found at Specified S3 Path
  • Description - The following is the reason for the error:
    • Ensure the required business transaction object is available in the S3 bucket.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Unknown Error During Canonical Copying or Master Data Lookup
  • Description - The following are the reasons for the error:

    • Verify the canonical copy process and master data lookup settings, as an unknown error was encountered during execution.

    • Please review the code implementation, as an unknown failure has occurred.

  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Attachment failure.
  • Description - The following is the reason for the error:
    • Review the Workflow Validation (WV) configuration, as the S3 file tagging process has failed.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - Yes
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Company details are missing or unavailable in the master data
  • Description - The following is the reason for the error:
    • Ensure company details are populated and available in the master data.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Missing Identifier in Master Data
  • Description - The following is the reason for the error:
    • Ensure the required identifiers are available in the master data.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Unhandled Exception While Retrieving Owner or Partner Details
  • Description - The following is the reasons for the error:
    • Review the configuration settings, as an unhandled exception was encountered while fetching owner or partner details.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Invalid Last Step Detected in Draft Submission Flow
  • Description - The following is the reason for the error:
    • Adjust the final step configuration, as an invalid step was identified in the draft-to-submit workflow.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Invalid Result Code in Workflow
  • Description - The following is the reason for the error:
    • Correct the result code, as an invalid value was found in the draft-to-submit workflow.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Invalid message type: ${incomingMessageType}
  • Description - The following is the reason for the error:
    • Ensure appropriate handling is configured for the message type when it is not processed via the inbound flow or JSLT map transformation.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Missing B2B response during JSLT map processing
  • Description - The following is the reason for the error:
    • Ensure safeguards are in place for scenarios where B2B does not generate a response during JSLT MAP processing.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Unexpected Error During JSLT MAP Transformation
  • Description - The following is the reason for the error:
    • Review the configuration settings, as an unexpected error was encountered during the JSLT MAP transformation.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Failure in Canonical to Business Transaction Object Transformation
  • Description - The following is the reason for the error:
    • Examine the JSLT transformation logic, as the conversion from Canonical to Business Transaction Object encountered a failure.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - Yes
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Transformation result not found.
  • Description - The following is the reason for the error:
    • Verify that the transformation is properly set up, as it did not produce any result.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Inbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Invalid message type: ${incomingMessageType}
  • Description - The following is the reason for the error:
    • Ensure appropriate handling is configured for the message type when it is not processed via the inbound flow or JSLT map transformation.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Outbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Missing B2B response during JSLT map processing
  • Description - The following is the reason for the error:
    • Ensure safeguards are in place for scenarios where B2B does not generate a response during JSLT MAP processing.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Outbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Canonical processing failed.
  • Description - The following is the reason for the error:
    • Review the configuration settings, as the presigned URL generation for the S3 BTO object failed.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Outbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Invalid Workflow Step Encountered
  • Description - The following are the reasons for the error:
    • Ensure that only one object entry is present in the workflow or MPF.
    • Verify that all steps in the workflow are valid.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Outbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Failure in Canonical to Business Transaction Object Transformation
  • Description - The following is the reason for the error:
    • Examine the JSLT transformation logic, as the conversion from Canonical to Business Transaction Object encountered a failure.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Outbound
  • Stack Trace available - Yes
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Transformation result not found.
  • Description - The following is the reason for the error:
    • Verify that the transformation is properly set up, as it did not produce any result.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Prepare Outbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Invalid message type: ${incomingMessageType}
  • Description - The following is the reason for the error:
    • Ensure appropriate handling is configured for the message type when it is not processed via the inbound flow or JSLT map transformation.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Trigger Outbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Outbound Trigger Failure for Transaction
  • Description - The following is the reason for the error:
    • Ensure safeguards are in handle situations where B2B fails to generate a response.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Trigger Outbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

${b2bResponse}
  • Description - The following are the reasons for the error:
    • Configure B2B to send outbound failure notifications directly to the UI.

    • Review the canonical outbound map configuration, as the transformation has failed.

    • Ensure the canonical data complies with the schema, as a validation error was encountered.

    • Review the B2B connection configuration, as a connection failure has been detected.

    • Verify the Integration Principal configuration, as a failure has occurred.

  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Trigger Outbound
  • Stack Trace available - No
  • Notification Type - The sender and receiver receives notifications (via bell icon and email) if they are subscribed.

Transformed File Missing at Presigned URL Provided by B2B
  • Description - The following is the reason for the error:
    • The B2B transformation was successful; however, ensure the presigned URL for the transformed file is generated and available.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Trigger Outbound
  • Stack Trace available - No
  • Notification Type - The sender and receiver receives notifications (via bell icon and email) if they are subscribed.

Invalid message type: ${incomingMessageType}
  • Description - The following is the reason for the error:
    • Ensure appropriate handling is configured for the message type when it is not processed via the inbound flow or JSLT map transformation.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Process Outbound
  • Stack Trace available - No
  • Notification Type - The sender and receiver receives notifications (via bell icon and email) if they are subscribed.

Outbound Processing Failure
  • Description - The following is the reason for the error:
    • Ensure safeguards are in handle situations where B2B fails to generate a response.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Process Outbound
  • Stack Trace available - No
  • Notification Type - The sender and receiver receives notifications (via bell icon and email) if they are subscribed.

Invalid Workflow Step Encountered
  • Description - The following are the reasons for the error:
    • Ensure that only one object entry is present in the workflow or MPF.
    • Verify that all steps in the workflow are valid.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Conclude Outbound
  • Stack Trace available - No
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Exception in instantiating transaction to Conclude Outbound Stage
  • Description - The following is the reason for the error:
    • Review the code and ensure all exceptions are properly handled, as the error resulted from a failure or unhandled exception.
  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Conclude Outbound
  • Stack Trace available - Yes
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.
${b2bResponse}
  • Description - The following are the reasons for the error:

    • Review the B2B transaction for the source of the error.

    • Review the mapping configuration to resolve the error.

    • Identify and add missing transforms to correct the error.

  • Corrective Action - Retry the transaction, and if the issue persists, contact support for assistance.
  • Direction - Submit
  • Stack Trace available - Yes
  • Notification Type - The sender receives notifications (via bell icon and email) if they are subscribed.

Table of contents