Type = How-tos, Technical Guides, Technical Tools,; Topic = Multienterprise Information Network Tower (MINT), Administration, Technical Documentation,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Commerce, Clinical Supply,; Function = Supply Chain, Operations, Procurement,

Add B2B connections for XTT Link Actions

Application Administrators can add and update Opus B2B connections via (Undefined variable: local.XTT LA) (JavaScript snippets), which allows the exchange of files between TraceLink and customer's external ERP system, e.g. (Undefined variable: local.NetSuite). Application Administrators must create an (Undefined variable: local.XTT LA) Catalog Item before creating the B2B connection via XTT Link Actions.

Contact the TraceLink implementation team for assistance in performing the one-time task of creating and associating an (Undefined variable: local.XTT LA) Catalog Item with the B2B connection.

Opus B2B connections do not affect existing Track & Trace Services (TTS) B2B connections. TTS apps that are available to Opus Platform users via Opus iFrame can continue to use their existing TTS B2B connections. Apps built on the Opus Platform cannot use TTS B2B connections and must create a new Opus B2B connection via XTT Link Actions.

Add and update B2B connections

Currently, TraceLink only supports connecting to NetSuite Enterprise Resource Planning systems.

  1. Select the Main Menu icon.

  2. Select Extensible Tracelink Transfer Link Actions.

  3. Select B2B Connections in the side menu.

  4. Select NetSuite.

  5. Select the Add icon. The New NetSuite Connection page displays.

  6. In the General section, fill in the following fields:

    • Connection Name field – Required. The unique name of the B2B connection.

      All letters in the Connection Name must be in uppercase.

    • Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data.

      Currently, only the OAuth2 authentication type is supported.

    • Token URL field – Required. The specific endpoint provided by the NetSuite Server where XTT Link Actions exchanges an authorization grant for an access token.
    • JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
    • Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with NetSuite.
    • Client Secret field – The confidential key used by XTT Link Actions to authenticate with NetSuite within the secure OAuth 2.0 framework.
    • Connection URL field – The entry point for XTT Link Actions to communicate with NetSuite.
    • SuiteQL Url field – The endpoint used by XTT Link Actions to execute SuiteQL queries, enabling the querying and extraction of NetSuite records in a structured, efficient manner.
    • Date Format field – The date format set by the NetSuite administrator during system setup.
    • Time Format field – The time format set by the NetSuite administrator during system setup.
    • Date Time Format field – The date and time format set by the NetSuite administrator during system setup.

  7. Click the Add icon in the Inbound Link Actions section to configure inbound link actions.

  8. Fill the following fields in the Add Inbound Entry side panel:

    • B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
    • Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
    • Link Action Version field – The version of the link action.
    • Polling Interval (Min) field – Required. The frequency at which XTT Link Actions polls data from the NetSuite application.

  9. Click Apply to save the configuration.

  10. Click the Add icon in the Outbound Link Actions section to configure outbound link actions.

  11. Fill the following fields in the Add Outbound Entry side panel:

    • B2B Transaction Type field – Required. The type of document exchanged, e.g. Purchase Order.
    • Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
    • Link Action Version field – Required. The version of the link action.
    • Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the NetSuite application.

  12. Click Apply to save the configuration.

  13. Click the Save icon.

    The NetSuite B2B connection appears in the list of all B2B connections.

Tips

  • Contact the TraceLink Support for assistance in associating a link action from the Catalog Manager with the B2B connection.

View B2B connections

  1. Select the Main Menu icon .

  2. Select Extensible Tracelink Transfer Link Actions.

  3. Select B2B Connection in the side menu.

  4. Select NetSuite.

    • Connection Name – The name given to a NetSuite connection.
    • Authentication Type – The type of authentication used to protect the company against unauthorized access to data.
    • Date Created – The date and time the NetSuite connection is created.
    • Last Updated – The date and time the NetSuite connection is updated.
    • Created By – The name of the Application Administrator who created the NetSuite connection.
    • Updated By – The name of the Application Administrator who updated the NetSuite connection.

  1. Select the Main Menu icon .

  2. Select Extensible Tracelink Transfer Link Actions.

  3. Select B2B Connection in the side menu.

  4. Select NetSuite.

  5. Select the link for the connection name from the results table. Select Apply.

  6. The View / Edit NetSuite Connection Details screen displays.

  • Connection Name field – Required. The name of the B2B connection.
  • Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data.

    Currently, only OAuth 2.0 authentication type is supported.

  • Token URL field – Required. The specific endpoint provided by the NetSuite Server where XTT Link Actions exchanges an authorization grant for an access token.
  • JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
  • Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with NetSuite.
  • Client Secret field – The confidential key used by XTT Link Actions to authenticate with NetSuite within the secure OAuth 2.0 framework.

    • In the Link Action Configuration section, view the following fields:

  • Connection URL field – The entry point for XTT Link Actions to communicate with NetSuite.
  • SuiteQL Url field – The endpoint used by XTT Link Actions to execute SuiteQL queries, enabling the querying and extraction of NetSuite records in a structured, efficient manner.
  • Date Format field – The date format set by the NetSuite administrator during system setup.
  • Time Format field – The time format set by the NetSuite administrator during system setup.
  • Date Time Format field – The date and time format set by the NetSuite administrator during system setup.
  • B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
  • Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
  • Link Action Version field – The version of the link action.
  • Polling Interval (Min) field – Required. The frequency at which XTT Link Actions polls data from the NetSuite application.
  • B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
  • Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
  • Link Action Version field – The version of the link action.
  • Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the NetSuite application.