Services How-Tos

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Fill in one or more of the following search fields:
   • Keywords – Filters the results to apps that contain the entered Keywords in the Service Name, Publisher Name, Subscribing Entity Name, or Service Administrator fields.
   • Service Type – Only apps of the selected type return in the results table.
   • My Company's Role – Indicates the company's role within the app.
     • All
     • Publisher – Only apps that the company owns display in the results table.
     • Subscriber – Only apps that the company links to display in the results table.
   • Subscribing Entity Type – Indicates whether the company links to an app as a company or as a specific location. Available if My Company's Role is Subscriber.
     • All
     • Company – Only apps that the company links to as a company return in the results table.
     • Location – Only apps that the company links to as a location return in the results table.
3. Select Search.

   The results display in the table.

• To update the configuration after adding an application, select Configure Published Service for a row on the where My Company's Role is Publisher.
• To remove a Link, select Remove Subscription for a row where My Company's Role is Subscriber, and then select Confirm in the dialog box.

  Remove Subscription does not display if the Service Type is US Product Track.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
         1. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
         2. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
            • KU (Customer)
            • LI (Vendor)
            • LS (Logical System)
            • US (User)
            • B (Bank)
            • GP (Business Partner)
         3. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

         Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. Select Submit.

   The Manage Services screen displays, and TraceLink activates the application.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
9. On the National Market Reporting tab:
   • Select one or more Countries checkboxes to enable reporting to the EU Hub for that Target Market.

     Only Target Markets with National Systems connected to the EU Hub should be added.

10. Select Submit.

    The Manage Services screen displays, and TraceLink activates the application.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).

   3. Enter one or more alternate Service Aliases using the company's BR-CNPJ (e.g. MPC.6987324594337) if this app sends asynchronous messages to and from trade partners in Brazil and the Service ID uses the company's GLN because the company also sends EPCIS messages to and from Serialized Operations Manager through Multienterprise Process Connect (optional).

      Separate multiple aliases with commas.

5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
         1. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
         2. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
            • KU (Customer)
            • LI (Vendor)
            • LS (Logical System)
            • US (User)
            • B (Bank)
            • GP (Business Partner)
         3. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

         Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. Select Submit.

   The Manage Services screen displays, and TraceLink activates the application.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
   5. Select the Company Role in the pharmaceutical supply chain from the drop-down:
      • Manufacturer – The company manufactures product. This includes Pharmaceutical Manufacturers and CMOs.
      • Wholesale Distributor/Repackager – The company distributes product or repackages product.
      • Dispenser – The company dispenses product to end consumers, e.g. a pharmacy.
        • For Dispensers: Select the Can Resell Products checkbox to enable limited resale capabilities that allow the transfer of product from one dispenser to another (optional).
   6. For Wholesale Distributors / Repackagers and Dispensers: Select the Inbound Transactions – Enable automatic assignment of ASNs based on ShipToLocation ID checkbox to automatically assign receipts to the correct location based on the location identifier specified by the trade partner in the ASN (optional).

      If selected, set the Receiving Location Identifiers in Management.

   7. Select whether the outbound Transaction Histories include extra fields from the outbound Transactions checkboxes (optional):
      • Include Lot Number and Expiration Date in Outbound Transaction Histories for lot based picks – Transaction Histories include the lot number and expiration date of the products when shipments pick products based on the lot number.

        Wholesale Distributors and Repackagers should select this checkbox when a Dispenser indicates that they need the Lot Number and Expiration Date included in the outbound Transaction History (TH).

        Transaction Histories Can Only Include this Information If

        1. The Advanced Shipping Notice from the supplier includes the Lot Number and Expiration Date.
        2. The user chooses to pick products for a shipment by both the NDC and Lot Number.

      • Include Shipment Date and Transaction Date in Outbound Transaction Histories for lot based picks – Transaction Histories include the transaction and shipment dates when shipments pick products based on the lot number.

        Wholesale Distributors and Repackagers should select this checkbox when a Dispenser indicates that they need the Transaction Date and Shipment Date included in the outbound Transaction History (TH).

   8. Enter the Transaction statement that users must confirm to complete the transaction.

   9. Select the Include Transaction Statements in serialized shipments sold to downstream supply chain Partners in the US checkbox to include the a regulatory compliance Transaction (TS) information fields in all EPCIS serialized sale shipments (optional).

   10. Enter the regulatory compliance statement confirming that the seller has met all applicable compliance regulations (optional).

       User can modify the statement message. Defaults to "Seller has complied with each applicable subsection of FDCA Sec. 581(27)(A)–(G)". If the field is blank (" "), the EPCIS seialized shipment message will include Transaction Statement (TS) data fields without statement text.

   11. Select the Include Direct Purchase Statements in Serialized Shipments Sold to Downstream Supply Chain Partners in the US checkbox to include the Direct Purchase Statement in the serialized shipments delivered from a Pharmaceutical Manufacturer, Repackager, or Wholesale Distributor to a downstream supply chain partner (optional).

   12. Enter the Statement Text confirming that the seller has purchased the product directly from a Pharmaceutical Manufacturer or Repackager.

       User can modify the statement message. Defaults to "Seller affirms that indicated product(s) were purchased directly from the manufacturer, exclusive distributor of the manufacturer, or a repackager who purchased directly unless noted as being indirectly sourced". This field is required only if the Include Direct Purchase Statements in Serialized Shipments Sold to Downstream Supply Chain Partners in the US checkbox is selected.

   13. Select the Include Received Direct Purchase Statements in Serialized Shipments Sold to Downstream Supply Chain Partners in the US checkbox to include the Received Direct Purchase Statement sent to a downstream supply chain partner in the United States (optional).

   14. Enter the Statement Text confirming that the seller received the product from a company that directly purchased it from the Pharmaceutical Manufacturer or Repackager.

       User can modify the statement message. Defaults to "Seller affirms receipt of directly purchased statement from previous wholesale distributor for the indicated product(s)." This field is required only if the Include Received Direct Purchase Statements in Serialized Shipments Sold to Downstream Supply Chain Partners in the US checkbox is selected.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
   3. Enter one or more alternate Service Aliases, using the company's GLN (e.g. PT.8856277233311) if this app sends EPCIS messages to and from Serialized Operations Manager or another serialization system of record and the Service ID does not use the company's GLN (optional).

      Separate multiple aliases with commas.

5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. Select Submit.

   The Manage Services screen displays, and TraceLink activates the application.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then selectServices.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.
7. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

8. On the ATP Wallet Information tab:

   To use the authorized trade partner authentication services that the ATP Wallet Information tab provides, PIE owners must also link to one or more instance of PIM.

   1. Select Add requester Credentials or Add responder Credentials to add the appropriate Credential Type to the table:
      • Requester – The Owner must use digital credentials when requesting product information from other supply chain partners.
      • Responder – The Owner must use digital credentials when responding to product information requests from other supply chain partners.

      To update an existing credential, remove the row from the table, select Submit, and then return to this tab to enter the updated information.

   2. Select the name of the digital Wallet Host that the trade partner's digital credentials are associated with from the drop-down.
   3. Enter the Trade partner DID, which identifies Tracelink Owner's digital wallet on the wallet's host provider.
   4. Select one of the following checkboxes in the Authentication Status column to indicate whether a trade partner must be an authorized trader partner (i.e. verified to have digital credentials by TraceLink) in order to accept the product verification request or response (optional):
      • Accept request without authentication checkbox – When selected, Owners can accept product verification requests from trade partners without them being authorized trade partners. Only displays if the Credential Type is Responder and the digital wallet has been previously configured.
      • Accept response without authentication checkbox – When selected, Owners can accept responses to a product verification request from trade partners without them being authorized trade partners. Only displays if the Credential Type is Requester and the digital wallet has been previously configured.
9. Select Submit.

   The Manage Services screen displays, and TraceLink activates the application.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then selectServices.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Service Administrator.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. On the OMS Credentials tab:
   1. Select Add Foreign Credentials to add the Credential Type to the table:Foreign – The company manufactures product in a country other than Russia. Each company has a single set of credentials that is shared between all of its locations outside of Uzbekistan.
   2. Enter the OMS ID provided by the OMSin the text field.
   3. Enter the Client Token in the text field.

   4. Enter the identifier value of the MAH IDin the text field.

      This value must match the MAH ID entered in Product Master Data for each product with a target market of Kazakhstan and a Production Type of Imported. Enter the identifier value only, omitting the identifier type (e.g. GLN).

   5. Select Test to validate the credentials with the OMS.

      The screen displays a confirmation message indicating whether the credentials are validated successfully.

10. Select Submit.

    The Manage Services screen displays, and TraceLink activates the application.

11. Select the Delete icon to remove a Credential Type.

Russia Compliance supports exportable and non-exportable certificates to digitally sign reports that are submitted to MDLP. Owners who choose to use non-exportable certificates for domestic MDLP credentials must use the Web UI and also configure an app for digitally signing the reports. Owners who choose to use exportable certificates must use the Web UI and the Digital Certificate Upload REST API. Administrators use the Web UI to configure the app and the REST API to upload digital certificates to a secure TraceLink server in Russia, which MDLP requires for domestic credentials. See the Russia Compliance Help Center for more information.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. On the MDLP Credentials tab:

   To update an existing credential, remove the row from the table, select Submit, and then return to this tab to enter the updated information.

   1. Select Add Domestic Credentials or Add Foreign Credentials to add the appropriate Credential Type to the table:
      • Domestic – The reporting entity must use a digital certificate (exportable or non-exportable) when authenticating to MDLP (e.g. the reporting entity is a location in Russia).
      • Foreign – The reporting entity does not use a digital certificate when authenticating to MDLP (e.g. the reporting entity is an MAH in a country other than Russia).
   2. Enter the Russia Account Number registered with MDLP, which identifies the Reporting Entity.

      This value must be entered as an identifier in Company or Partner Master Data and must be unique within the application.

   3. Enter the Certificate ID if the Credential Type is Domestic and the certificate is non-exportable. Do not enter any value for exportable certificates.
   4. Enter the Certificate Digest if the Credential Type is Domestic and the certificate is non-exportable. Do not enter any value for exportable certificates.
   5. Enter the Login Information, which identifies the credentials that the Reporting Entity uses to log in to the MDLP portal:
      • MDLP User Name – The Russia-assigned user name that the reporting entity uses to log in to the MDLP portal.
      • Password – The Russia-assigned password for the MDLP User Name (displays and is required only if the Credential Type is Foreign).
   6. Enter the credentials for the Accounting System (i.e. TraceLink) that the Reporting Entity registered with MDLP:
      • Client ID – The Russia-assigned Client ID for the Accounting System.
      • Client Secret – The Russia-assigned Client Secret for the Accounting System.

      This information is available on the MDLP portal in Administration > Accounting System.

10. Select Submit.

    The Manage Services screen displays, and TraceLink activates the application.

11. For Domestic Credential Type:

    • For a non-exportable certificate, the User ID and Password generated by TraceLink display in the confirmation message. This User ID and Password must be used when configuring the Russia Report Signature Appender app to retrieve reports from Russia Compliance. Administrators must copy and retain the User ID and Password before dismissing the confirmation message. The User ID and Password are not displayed outside of the confirmation message and cannot be retrieved elsewhere. See the Russia Compliance Help Center for more information.

    • For an exportable certificate, generate a security token and upload a digital certificate to the TraceLink server in Russia :

      1. Select Configure Published Service Settings on the Manage Services screen to return to the Russia Compliance app configuration.
      2. Select the MDLP Credentials tab.

      3. Select Request Token for the Domestic Credential Type.

         The Token for Domestic Credentials dialog box displays with the security token used to upload the digital certificate.

         The security token is valid for 30 minutes after generation.

      4. Select Copy Token.

         The dialog box closes and the token is copied to the clipboard.

      5. Insert the token into the Digital Certificate Upload REST API to complete the digital certificate upload. See the Russia Compliance Help Center for more information.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Service Administrator.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. On the OMS Credentials tab:
   1. Select Add Domestic Credentials or Add Foreign Credentials to add the appropriate Credential Type to the table:
      • Domestic – The company manufactures product in Russia. The credentials are assigned to a single company location (each company location within Russia must use its own set of credentials to authenticate to the CRPT OMS).
      • Foreign – The company manufactures product in a country other than Russia. Each company has a single set of credentials that is shared between all of its locations outside of Russia.

      A company can have both Domestic and Foreign credentials if manufacturing takes place in Russia as well as in other countries.

   2. Enter the OMS ID provided by CRPT in the text field.
   3. Enter the Address that the credentials are assigned to in the text field (optional).
   4. Select Retrieve Connection ID to retrieve a connection ID from OMS and populate the OMS Connection ID field.
   5. If the Credential Type is Domestic, select the manufacturing Location within Russia that the credentials are assigned to from the drop-down.

      or

      If the Credential Type is Foreign, enter the identifier value of the MAH ID in the text field.

      This value must match the MAH ID entered in Product Master Data for each product with a target market of Russia and a Production Type of Imported. Enter the identifier value only, omitting the identifier type (e.g. GLN).

   6. Select Test to validate the credentials with the CRPT OMS.

      The screen displays a confirmation message indicating whether the credentials are validated successfully.

10. Select Submit.

    The Manage Services screen displays, and TraceLink activates the application.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then selectServices.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Service Administrator.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. On the OMS Credentials tab:
   1. Select Add Foreign Credentials to add the Credential Type to the table:Foreign – The company manufactures product in a country other than Russia. Each company has a single set of credentials that is shared between all of its locations outside of Uzbekistan.
   2. Enter the OMS ID provided by the OMSin the text field.
   3. Enter the Client Token in the text field.

   4. Enter the identifier value of the MAH IDin the text field.

      This value must match the MAH ID entered in Product Master Data for each product with a target market of Uzbekistan and a Production Type of Imported. Enter the identifier value only, omitting the identifier type (e.g. GLN).

   5. Enter the Contact Person in the text field.

   6. Select Test to validate the credentials with the OMS.

      The screen displays a confirmation message indicating whether the credentials are validated successfully.

10. Select Submit.

    The Manage Services screen displays, and TraceLink activates the application.

11. Select the icon to remove a Credential Type.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. On the DTTS Credentials tab:

   1. Select Add Credentials.

      A new row displays in the table.

   2. Enter the Location GLN that the credentials are assigned to.
   3. Enter the SFDA-assigned User Name for the credentials.
   4. Enter the Password associated with the user name.

   Credentials are required for each location that submits reports to the DTTS and must be entered in Production.

10. Select Submit.

    The Manage Services screen displays, and TraceLink activates the application.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
   5. Select which Serial Number Management System the company manages serial numbers with:
      • Enterprise Serial Number Manager – (default) The company manages serial numbers with the Enterprise Serial Number Manager.
      • TraceLink Serial Number Manager – The company manages serial numbers with the TraceLink Serial Number Manager.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. Select Submit.

   The Manage Services screen displays, and TraceLink activates the application.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
   5. Select how Serialized Operations Manager receives transfer shipments from the Generate Auto-Receipts options (optional):
      • Select the All Target Markets checkbox to automatically submit a Receipt message for all transfer shipments received at the Owner's location.

        Optionally, specify any Target Markets that must not automatically receive transfer shipments in the Exclude These Target Markets table.

        1. Select Add Another Target Market to add another Target Market to the table.
        2. Enter the country code of the Target Market.

        or

      • Add Target Markets to the Include these target markets table to automatically submit a Receipt message for transfer shipments received at the Owner's location in specific Target Markets.
   6. Select how Serialized Operations Manager verifies the lot number and expiration date on receipts by scanning the serialization barcode and matching it with inbound shipment data by enabling the Verify Lot Number and Expiration Date in Barcodes option (optional). By default, GTIN and serial number are verified:
      • Select the All Ship to Countries checkbox to verify the 4 fields for all countries.

        Optionally, to exclude specific Ship To Countries from verification of the 4 fields, add them to the Exclude These Ship To Countries table. By default, all 4 fields are verified for every country, except those listed in the exclusion list.

        1. Select Add Another Ship To Country to add another Ship To Country to the table.
        2. Enter a country code or name in the Ship To Country type-ahead field.

        or

      • Add Ship To Country to the Include these Ship To Countries table to enable verification of all 4 fields against the inbound shipment data during the receiving operation.
        • If the Ship To Country matches a country within the configured target market, Serialized Operations Manager will verify all 4 fields.
        • If the Ship To Country does not match a configured target market country, Serialized Operations Manager will only verify the GTIN and serial number by default.
   7. Select how Serialized Operations Manager sends multiple ESM sales shipments originating in the US by configuring Append ESM SOM Sales Shipment Feeds (US Only) (optional) to add new serial numbers to an existing shipment with the same delivery number, ensuring compliance and operational needs are met while enabling complete serial tracking.
      • Set the Ship To Country to US (the only available option).
        When set to US, TraceLink processes serial numbers included in the ESM sales shipments with the same delivery number and adds them to the existing outbound delivery in the Serialized Operations Manager. The existing outbound delivery file is then appended with the new shipment details, rather than overwriting the current outbound shipment.
        
      • By default, if the Ship To Country is not set to US, TraceLink processes the new ESM sales shipment by overwriting the existing outbound shipment.

      Serial numbers in incremental deliveries must be unique. They must not include duplicates from previous shipments, as this may lead to discrepancies while adding the order item quantity, resulting in processing errors.

   8. Select how Serialized Operations Manager handles SGTINs that are received without a corresponding master data entry and are either uncommissioned or not registered to the Serialized Operations Manager repository from the Commissioning Settings options (optional):
      • Select the Commission unknown SGTINs using the product information in the received EPCIS file and add the GTINs to Product Master Data checkbox to use the information contained within a Product Track US - Received SOM Serialized Sales Shipment EPCIS message to commission any unknown SGTINs included in a Product Track US - Received SOM Serialized Sales Shipment EPCIS message and add the GTIN's product information to Product Master Data if an existing Product Master Data entry cannot be found. If an existing Product Master Data entry cannot be found, TraceLink creates a new Product Master Data entry for the GTIN using the information contained in the Product Track US - Received SOM Serialized Sales Shipment EPCIS message to populate all fields required for a US target market.
      • Select the Register unknown SGTINs using NDC lookup results and add the GTINs to Product Master Data checkbox to locate the product information for any unknown SGTINs included in a SOM Registration message using either IBM Micromedex® RED BOOK® or TraceLink's NDC database, which relies on data from the FDA, register the unknown SGTIN in SOM, and use the GTIN's product information to populate all fields required for a US target market in Product Master Data if an existing Product Master Data entry cannot be found.
   9. Select whether SOM shipments containing fewer than the expected quantity of serial numbers for a given delivery number can be received from the Receive Partial Deliveries radio buttons:
      • No, do not allow partial deliveries (default) – When selected, SOM receipts that contain fewer than the expected quantity of serial numbers for a given delivery number cannot be submitted .
      • Yes, allow partial deliveries – When selected, SOM receipts that contain fewer than the expected quantity of serial numbers for a given delivery number can be submitted. When a partial receipt is submitted, SOM updates the received serial numbers with an Item Status of Available.
   10. Select whether the purchase order (with or without aggregation) needs to be associated with the serial number for shipments that contain one or more purchase orders from the Associate PO with Serial Numbers radio buttons:
       • No, do not associate the PO with serial numbers from the order item (default) – When selected, the purchase order is not associated with the serial number for the product in that order item.
       • Yes, associate the PO with serial numbers from the order item – When selected, the purchase order is associated with the serial numbers for the product in that order item. The association is also communicated to the receiver of the delivery.
   11. Select whether the recall information from Product Information Exchange (PIE) needs to be integrated with SOM from the Integrate Recall Information radio buttons:
       • No, do not integrate recall information (default) – When selected, the recall information is not integrated with SOM.
       • Yes, integrate recall information – When selected, the recalled product's NDC and lot number combinations from PIE are received by SOM.
         

       The ability to view and integrate recall information in the SOM UI will be available in future Product Information Exchange (PIE) and SOM on Opus releases along with associated licenses. Contact TraceLink Support to configure Product Information Manager (PIM) – Recalls to use this feature. Only the serial numbers currently in the Owner's SOM repository will be marked as recalled. Serial numbers received after the recalled information is integrated into SOM will not be marked as recalled.

4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. Select Submit.

   The Manage Services screen displays, and TraceLink activates the application.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
   5. Select whether to Allow sales shipments between South Korea legal entities under common ownership of my company from the radio buttons to specify how the South Korea Compliance app processes the inbound R01 Sales Shipment Notice from the KPIS:
      • No – (default) TraceLink produces an error when processing an R01 Sales Shipment Notice where the Supplier and Receiver are both locations within the Owner's company and have different South Korea Business Registration Numbers (i.e. the error occurs because the serial numbers in the notice already exist in the Owner's Serialized Operations Manager repository).
      • Yes – TraceLink successfully processes an R01 Sales Shipment Notice where the Supplier and Receiver are both locations within the Owner's company and have different South Korea Business Registration Numbers. Select this option if the company sends sales shipments between separate legal entities, which TraceLink represents as internal locations within the Owner's company.
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. Select Submit.

   The Manage Services screen displays, and TraceLink activates the application.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Publish New Service.
3. In the Service Information section:
   1. Enter the Service Name for the company's instance of the app.
   2. Select the Service Type to add.
   3. Enter a brief Description of the app, used in Link invitations sent to Partners.
   4. Select whether other Members can see the app in Community from the Visibility radio buttons:
      • No, only invited companies can subscribe – Only TraceLink Members invited by the company can see the app.
      • Yes, TraceLink members can request to subscribe – Any TraceLink Members can see the app in Community and request to Link to the app.
   5. Enter the Publishing Company Short Name displayed in the application.
   6. Enter the Print Screen Confidentiality Notice displayed when screens are printed (optional).
4. In the Identifiers in Messages My Company Sends section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages sent to Partners.

      This identifier must match the Publishing Company ID (Type/Value) entered by Partner companies and locations on their Configure Subscription Settings screen.

   2. Enter the unique Service ID that the company identifies the app with (formatted as [App Abbreviation].[My Company ID Value], e.g. SNX.888888202867).
5. In the Identifiers in Messages My Company Receives section:
   1. Enter the unique identifier Type and Value that identifies My Company ID in messages received from Partners.
   2. Enter the Partner Company ID Type assigned to Partner companies in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

   3. Enter the Partner Location ID Type assigned to Partner locations in messages sent to the company.

      The identifier type here must match the identifier type selected when adding Partners on the Set Identifiers screen.

6. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.

7. On the Transaction Delivery Rules tab:

   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
8. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

9. Select Submit.

   The Manage Services screen displays, and TraceLink activates the application.

• The Owner of the app must invite the company or location to Link to the app as a Partner.
• The company or location must accept the Link invitation.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Select Subscriber from the My Company's Role drop-down.
3. Fill in one or more of the other search fields.
4. Select Search.
5. Select Configure Subscription in the Actions column.
6. In the Identifiers in Messages My Company Sends and Receives:
   1. Select the unique Type and Value that identifies the Publishing Company ID in messages.

      This identifier must match the My Company ID (Type/Value) entered by the company that owns the app on their Configure Published Service Settings screen.

   2. Enter the unique Service ID that the Owner company identifies the app with.

      Formatted as [App Abbreviation].[Publishing Company ID Value].[My Company's Entity ID Value] (e.g. SNX.3614141123459.1627345896278).

   3. Select the unique Type and Value that identifies My Company's Entity ID in messages sent from the Owner of the app.

      If the company entity is a location, the value in this field comes from the Default Outbound Identifier set on the Manage Locations screen.

   4. For US Product Track or Multienterprise Process Connect Links: Enter one or more alternate Service Aliases (optional). For US Product Track, if the company sends EPCIS messages to and from Serialized Operations Manager or another serialized system of record and the Service ID does not use the company's GLN, enter the GLN here (e.g. PT.8856277233311). For Multienterprise Process Connect, if the company sends asynchronous messages to or from trade partners in Brazil and the Service ID uses the company's GLN because the company also sends EPCIS messages to and from Serialized Operations Manager through Multienterprise Process Connect, enter the company's BR-CNPJ here (e.g. MPC.6987324594337).
7. On the Service Administrators tab:
   1. Enter the User (Email) assigned to the app as a Manager.
   2. Select Add Another Service Administrator in the header of the tab to add another Manager.
8. On the Transaction Delivery Rules tab:
   1. Select what happens when a Partner sends a message from the If Partner Posts a Message Automatically Deliver radio buttons:
      • Yes - automatically deliver – TraceLink automatically delivers the message.
      • No - a user must request delivery – TraceLink does not deliver the message until a user requests the delivery.
   2. Repeat the previous step for each message in the tab.
9. On the SAP IDoc Settings tab (optional):
   1. In the SAP IDoc Receiver Settings section:
      1. Enter the SAP client number for the company in the My SAP Client Number field (optional).
      2. Enter the SAP logical system name for the company in the My Logical System Name field (optional).
      3. Enter the SAP logical system port for the company in the My Logical System Port (optional).
   2. In the SAP IDoc Partner Profile section:
      1. Enter the SAP Sender Partner Number of the Partner that sends messages to the company (optional).
      2. Enter the SAP sender Partner Port of the Partner that sends messages to the company (optional).
      3. Select the Sender Partner Type of the Partner that sends messages to the company (optional).
         • KU (Customer)
         • LI (Vendor)
         • LS (Logical System)
         • US (User)
         • B (Bank)
         • GP (Business Partner)
      4. Enter the Sender Partner Function of the Partner that sends messages to the company, based on the Sender Partner Type selected (optional).

      Disabled if the Sender Partner Type is US (User), B (Bank), or GP (Business partner).

10. Select Submit.

    The Manage Services screen displays, and TraceLink saves the updated configuration.

1. Hover over Company Administration on the User Profile drop-down in the top right of any screen, and then select Services.
2. Search for the app or Link that needs a Manager assigned.
3. Select Configure Published Service Settings or Configure Subscription in the Actions column.
4. On the Service Administrators tab:
   1. Select Add Another Service Administrator in the header of the tab.
   2. Enter the User (Email) assigned to the app as a Manager.
5. Select Submit.

   The Manage Services screen displays, and TraceLink saves the updated configuration.