How to implement connectors for Infor CSD

Implementation notes

This article provides a list of suggested tasks to follow and review during the implementation of this connector.

Turn on the connector

Connector enablement settings are global.

  1. Enter the parameters for Company and Refresh Warehouse.

    • The CSD Web Order Number represents the field in CSD that the B2B Web Order Number value will be submitted to.

    • The CSD Integration Connection is the connection that will be used for CSD API calls. The setup of this connection is outlined below.

  1. Set up the Integration Connection for API endpoints. This will be used for API refreshes and real-time calls.

      1. Select the type of SXe API.

      2. Ensure that the API Endpoint is the URL to the API that is accessible from the website (for example, https://mycompany.com:port/)

    • Since CSD is a multitenant solution, we recommend explicitly denoting the full API endpoint (for example, https://DOMAIN/TENANT/SX/web/sxapirestservice/).

Note: We automatically append the default path of the ION API, "infor/SX/rest/sxapirestservice/", to the end of the API endpoint if a specific path is not designated.

  1. Set up the Integration Connection for Fetchwhere.

    1. Select the type of SXe API.

    2. Ensure that the API Endpoint is the FetchWhere endpoint URL that is accessible from the website (for example, https://domain/tenant/SX/rest/serviceinterface/proxy/FetchWhere).

Note: We automatically append the default path of the ION API, "infor/SX/rest/sxapirestservice/", to the end of the API endpoint if a specific path is not designated.

  1. Enter the Company Number we intentionally have the company associated with the API connection separate from the one used for refreshes.

    • This allows for the circumstance where data is acquired from multiple CSD companies yet the API must have a single, numeric company number for calls.

    • The App Server Host is not required for V11, as it uses the REST APIs.

  1. Enter the User Name and Password conforming to the security and user setup in CSD.

    • The Client ID and Client Password are the credentials from CSD for accessing the API.

    • The Token User Name and Token Password are the credentials for retrieving the authorization token from CSD.

    • The Token Endpoint is the URL from which to retrieve the bearer token.

  1. Assign the connection to the generated integration jobs in the Admin Console.

    • Optionally, you may chain the jobs together. It is a common practice to set up the first job as recurring so that it runs every night and then chains from job to job through the chain of refreshes ending with rebuilding the search index. This keeps your jobs from attempting to run concurrently.

    Business considerations

    The following section outlines business considerations for particular B2B Commerce CSD integration jobs. Based on how a customer has implemented & configured CSD, various jobs may need to be adjusted accordingly.

    CSD 03: Product

    • Determine whether you want to have the Catalog (ICSC) table retrieved by B2B Commerce in addition to the ICSP table

    • ICSC exists as a separate job step within the Product job. It can be deleted if you do not wish to retrieve items from ICSC.

CSD 04: Customers

  • Decide whether you want to assign inside or outside sales reps to the customer. The default is the outside sales rep. This drives the ability for a sales rep to sign into B2B Commerce and access the customers they are assigned to.

CSD 05: Order History

  • This job, by default, retrieves unlimited data. Update the filtering to retrieve a limited amount of data once the job is set.

  • Fill in the Order Status Mapping table in the B2B Commerce Admin Console for order status codes to get the descriptions desired. Below is an example default setup:

    • 0 = Entered

    • 1 = Ordered

    • 2 = Picked

    • 3 = Shipped

    • 4 = Invoiced

    • 5 = Paid

    • 9 = Canceled

  • We suggest you backfill order history by adjusting this job so the WHERE clause using the transdt uses a range of orders or has an enterdt to retrieve only orders from a certain date.

CSD 06: Invoice History

The strategy for invoices is identical to orders, especially since the data comes from the same source tables (OEEH, OEEL). This set of queries will only return records in Invoiced and Paid status to limit its scope. Follow the Order History instructions above to load the initial tables and then set the job for ongoing refreshes.

CSD 07: Shipments

This job is optional if you do not have any OEEHP records. It takes up almost no resources so it is not required to be deleted for performance concerns if these records do not exist.