Add B2B connections

Select the Main Menu icon.

Select Extensible Tracelink Transfer Exchanges.

Select B2B Connections in the side menu.

Select SAP Ariba.

Select New. The General Connection page displays.

In the General section, fill in the following information:

• Connection Name field – Required. The unique name of the B2B connection.
• Inbound Ariba Endpoint field – Auto-populated. The OPUS URL where SAP Ariba can send inbound messages to TraceLink. This field is auto generated after the connection is created.
• Outbound Ariba Endpoint field – SAP Ariba URL for XTT Exchanges to send outbound messages.

In the Ariba Certificates section, fill in the following information:

• Certificate (leaf + intermediates) field – Required. The Privacy Enhanced Mail (PEM) server certificate chain that includes the leaf, intermediate certificates, and the root certificate.

  Self-signed leaf certificates are not supported. Use certificates signed by a trusted Certificate Authority (CA).

• Description field – A brief description to label the certificate for internal tracking.

In the Customer Certificates section, fill in the following information:

• Private Key field – The private key or encrypted private key.
• Password field – The password if the private key is encrypted.
• Certificate (leaf + intermediates) field – Required. The Privacy Enhanced Mail (PEM) server certificate chain that includes the leaf, intermediate certificates, and the root certificate.

  Self-signed leaf certificates are not supported. Use certificates signed by a trusted Certificate Authority (CA).

• Description field – A brief description to label the certificate for internal tracking.

Select the Main Menu icon.

Select Extensible Tracelink Transfer Exchanges.

Select B2B Connections in the side menu.

Select GHX.

Select New. The General Connection page displays.

In the General section, fill in the following information:

• Connection Name field – Required. The unique name of the B2B connection.
• GHX Interchange ID Qualifier field – Specifies the EDI standard code qualifier that defines the format and system of the Interchange ID. Corresponds to the ISA05 element in the ANSI X12 interchange header.
• GHX Interchange ID field – Required. A unique X12 sender identifier assigned to the customer account on GHX. This identifier is used by the gateway to resolve the owning company context and route inbound X12 transactions to the correct OPUS business application.
• Wait for recipient Functional Acknowledgment before responding? drop-down – Optional. Indicates whether or not to wait for an inbound Functional Acknowledgment before returning the final processing status for an outbound B2B message (such as a Purchase Order).

  • Yes – Select this option to wait for the recipient's Functional Acknowledgment before sending a response to the business application. For X12, TraceLink waits for a correlated 997. For EDIFACT, TraceLink waits for a correlated CONTRL. During this time, the outbound message remains in the Processing state, and the corresponding Functional Acknowledgment record is displayed with the status Pending acknowledgment from the receiving partner. If a valid Functional Acknowledgment is received within this period, TraceLink returns a success response. If the acknowledgment indicates an error, the response reflects the failure. If no Functional Acknowledgment is received within 24 hours, the outbound message times out.

  • No – Select this option to send the response after the outbound B2B message completes using the connection's delivery confirmation.

Select the Main Menu icon.

Select Extensible Tracelink Transfer Exchanges.

Select B2B Connections in the side menu.

Select IBM Sterling.

Select New. The General Connection page displays.

In the General section, fill in the following information:

• Connection Name field – Required. The unique name of the B2B connection. The name can be alphanumeric and must contain only uppercase letters (e.g. TEST123 or TEST).
• Interchange Sender ID Qualifier field – Specifies the EDI standard code qualifier that defines the format and system of the Interchange Sender ID. Corresponds to the ISA05 element in the ANSI X12 interchange header.
• Interchange Sender ID field – Specifies the unique identifier of the sending partner or enterprise originating the EDI interchange. Corresponds to the ISA06 element in the ANSI X12 interchange header.
• Wait for recipient Functional Acknowledgment before responding? drop-down – Optional. Indicates whether or not to wait for an inbound Functional Acknowledgment before returning the final processing status for an outbound B2B message (such as a Purchase Order).

  • Yes – Select this option to wait for the recipient's Functional Acknowledgment before sending a response to the business application. For X12, TraceLink waits for a correlated 997. For EDIFACT, TraceLink waits for a correlated CONTRL. During this time, the outbound message remains in the Processing state, and the corresponding Functional Acknowledgment record is displayed with the status Pending acknowledgment from the receiving partner. If a valid Functional Acknowledgment is received within this period, TraceLink returns a success response. If the acknowledgment indicates an error, the response reflects the failure. If no Functional Acknowledgment is received within 24 hours, the outbound message times out.

  • No – Select this option to send the response after the outbound B2B message completes using the connection's delivery confirmation.

Select the Main Menu icon.

Select Extensible Tracelink Transfer Exchanges.

Select B2B Connections in the side menu.

Select SAP Ariba.

See the information that displays for each B2B connection

• Connection Name – The unique name of the B2B connection.
• Inbound Ariba Endpoint – The OPUS URL where SAP Ariba can send inbound messages to TraceLink.
• Outbound Ariba Endpoint – SAP Ariba URL for XTT Exchanges to send outbound messages.
• Last Updated By – The name of the Application Administrator who updated the SAP Ariba connection.
• Last Updated – The date and time the SAP Ariba connection is updated.

Select the Main Menu icon.

Select Extensible Tracelink Transfer Exchanges.

Select B2B Connections in the side menu.

Select SAP Ariba.

The View/Edit SAP Ariba B2B Connection screen displays.

Select the Main Menu icon.

Select Extensible Tracelink Transfer Exchanges.

Select B2B Connections in the side menu.

Select GHX.

See the information that displays for each B2B connection

• Connection Name – The unique name of the B2B connection.
• Interchange Sender ID Qualifier field – Specifies the EDI standard code qualifier that defines the format and system of the Interchange Sender ID.
• Interchange Sender ID field – Specifies the unique identifier of the sending partner or enterprise originating the EDI interchange.
• Last Updated By – The name of the Application Administrator who updated the GHX connection.
• Last Updated – The date and time the GHX connection is updated.

Select the Main Menu icon.

Select Extensible Tracelink Transfer Exchanges.

Select B2B Connections in the side menu.

Select GHX.

The View/Edit GHX B2B Connection screen displays.

Select the Main Menu icon.

Select Extensible Tracelink Transfer Exchanges.

Select B2B Connections in the side menu.

Select IBM Sterling.

See the information that displays for each B2B connection

• Connection Name – The unique name of the B2B connection.
• Interchange Sender ID Qualifier field – Specifies the EDI standard code qualifier that defines the format and system of the Interchange Sender ID.
• Interchange Sender ID field – Specifies the unique identifier of the sending partner or enterprise originating the EDI interchange.
• Last Updated By – The name of the Application Administrator who updated the IBM Sterling connection.
• Last Updated – The date and time the IBM Sterling connection is updated.

Select the Main Menu icon.

Select Extensible Tracelink Transfer Exchanges.

Select B2B Connections in the side menu.

Select IBM Sterling.

The View/Edit IBM Sterling B2B Connection screen displays.