Setting SX.e Integration Parameters

  1. Open the SX.e Integration Parameters form. The SX.e Integration Parameters form is displayed.
  2. Select these check boxes in the Integrations section:
    • SX.e: To enable integration between Infor Service Management (ISM) and Distribution SX.e.
    • Enable ION API Servers: To activate the ION API servers for the effective transfer of information between the integrated applications through applicable BODs.
    Note: 

    You can also use these options:

    • Copy From Master Site: To copy some BOD parameters from default site.

      Note: Some parameters have foreign key dependencies and cannot be copied. These are left blank. You can set up these dependencies after consuming the appropriate CodeDefinition BODs.
    • Integration Parameters: To access the Integration Parameters form.
  3. Specify this information on the General tab:
    Company Number

    Specify the company number provided by Distribution SX.e.

    Logical ID
    Specify the logical ID that you used in Infor OS Portal or Infor Ming.le for the Distribution SX.e integration.
    User ID
    Specify the user ID provided by Distribution SX.e.
    Password

    Specify a password to use. The password is encrypted and is displayed as asterisks. A password is not required by Distribution SX.e.

    Confirm Password
    Specify the password again to confirm.
    Use OAuth 1.0
    Select this check box to authorize third-party applications to access the application data using temporary credentials, tokens, and cryptographic signatures, instead of passwords.
    Web Service URL
    Specify the web service URL provided by Distribution SX.e.
    ION API Credentials
    Specify the authentication information used to connect to ION API that you obtained in ION. See the Infor Distribution SX.e Integration Guide for Infor Service Management for more information.
    FetchWhere API URL
    The API endpoint to securely authenticate the client application with the service provider using OAuth.
    Consumer Key
    The identifier string for the client application that is provided by the API provider.
    Consumer Secret
    The password to access the client application that is provided by the API provider.
  4. Select the default setting to use for these fields on the Defaults tab:
    Auto Allocation Core Returns
    To enable the auto-allocation of dirty core items on service orders, select this option.

    When this option is selected and a dirty core return material transaction is entered on the Service Order Transactions form, the dirty core return material transaction is automatically allocated to the related remanufactured core item. The Core Trans Number field on the return material transaction identifies the transaction number of the related remanufactured core product.

    Cost Type
    Select a cost type from the list. This selected cost type from Distribution SX.e is used to populate service order material transactions. By default, the General Ledger cost type is selected.
    Check Ship To Required
    Select this check box to require the system to check the Ship To Required field on the Customers form. The Ship To Required field on the Customers form inherits its setting from the CustomerPartyMaster BOD and when checked, requires that a ship to exists for the customer on a service order or contract. If a ship to does not exist for the customer, then the service order or contract cannot be saved.

    Clear the Check Ship To Required check box if you do not want the system to check the Ship To Required field, thus allowing service orders or contracts to be saved when the customer does not have a ship to.

    Create SX.e Purchase Order
    This check box is selected by default. When it is selected, the Create SX.e Purchase Order check box is also selected on the SX.e Catalog/Non-Stock Query form, and a purchase order is created by default in Distribution SX.e when a planned material transaction is created.

    When this check box is cleared, it is also cleared by default on the SX.e Catalog/Non-Stock Query form, and a purchase order is not created. Instead, the item goes through the current Distribution SX.e PO RRAR process, which consolidates products fromService Management and Distribution SX.e into a single PO.

    Default Transaction Salesperson From
    This parameter sets the default value of the Salesperson field on the grid view of the Service Order Transactions form.
    To set the default value of the Salesperson field to the salesperson that is set on the SRO header, select SRO Header.
    Note: When the salesperson is changed on the SRO header, the value of the Salesperson field is not updated on the Service Order Transactions form.
    To set the default value of the Salesperson field to the salesperson associated with the partner that is set on SRO transaction, select Transactions
    Note: When there is a change in partner on the transaction, the Salesperson field is also updated with the salesperson associated with the new partner. If the value on the Salesperson field is changed after updating the partner, the new value on the Salesperson field will remain. Thus, it is possible that some of the transactions have the header salesperson, and others may have the partner or a third party as the salesperson.
    Enforce Allocations
    When this check box is selected, service order material transactions cannot be posted when the item/warehouse Item On Hand quantity is less than the Allocated Order quantity. This setting ignores the On Han Neg Flag on the Inventory Parameters form.

    This field also works to prevent material transactions from posting when the quantity on the material transaction is greater than the Ship Qty of the Distribution SX.e order line and the transaction type is not Return.

    Include Addons
    Select this check box to include add-ons.
    Inventory Adjustment
    Select an account number. This account number is used by low-level ISM routines to capture certain inventory adjustments. Because Distribution SX.e is the system of record for inventory management, these entries are not suitable for any aggregate analysis.
    Use Replacement Cost for Recover Billing Code
    When integrated to Distribution SX.e and the billing code for service orders is set to Recover, select this option to use the replacement cost from Distribution SX.e, instead of the journal cost, as the price for service order transactions.
    Validate Lot Quantity
    When this check box is selected, the transaction quantity of each Service Order material transaction that is posted is validated against the quantity of the allocated lot.

    When this check box is cleared, the allocated lot is not validated until invoicing.

  5. Specify this information on the BODs tab:
    Alphanumeric Ship To Starting Number
    Specify the starting integer value to use when the Distribution SX.e ShipTo value is alpha numeric.

    The default value is zero. You must reset the value before the initial BOD load to retain the numeric Distribution SX.e ShipToID in Service Management. For SX.e Alpha numeric ShipTo, the system assigns the next available Service Management customer ship to number that is greater than or equal to the starting number specified on this form. However, if the value of the Distribution SX.e ShipTo ID is numeric but greater than the starting number specified or the number already exists in Service Management, it will be treated as alpha numeric.

    We recommend that you specify 90000000 as the starting number. This will help to reduce potential errors.

    Display Alt Document ID
    Select this check box to use the alternate document ID from Distribution SX.e in the Invoice Number field on the output generated by these forms:
    • Order Invoicing
    • Contract Invoicing
    • Rental Check Out/In

    The Alternate Document ID and related fields are displayed on the Order Invoice Listing form and Contract Invoice Listing form.

    Selecting Display Alt Document ID causes these actions:

    • Order invoicing runs and generates the invoice number and assigns a Service Management number.
    • Automatic invoice posting is performed for the invoice number, which triggers the Process.Invoice BOD to be sent to Distribution SX.e.
    • Distribution SX.e responds to the process request with an Acknowledge.Invoice BOD, which contains the Distribution SX.e alternate document ID. Service Management then consumes the BOD and the information.
    • After the BOD is successfully consumed, Service Management initiates a print request using Background Task History and the report output contains the Alternate Document ID instead of the Service Management invoice number.
    Note: Visibility to the ISM Invoice number is available in Distribution SX.e. If an error occurs, the report might not be generated.
    Integrate Notes

    Select this check box to enable posting of invoice notes from Infor Service Management (ISM) to Distribution SX.e through the Process.Invoice BOD.

    In ISM, when the Order Invoicing report is generated for a Service Repair Order (SRO), or the Contract Invoicing report is generated for a contract, the Process.Invoice BOD is generated. The BOD includes consolidated notes at the header and line levels in the following scenarios:

    • Header level:
      • For SROs: A single header-level note is included in the BOD by consolidating SRO header notes and the reason or resolution notes from SRO operations.
      • For contracts: A single header-level note is included in the BOD by consolidating notes from the contract header.
    • Line level:
      • For SROs: A single line-level note is included in the BOD for each invoice line created by consolidating the notes from the associated SRO transaction.
      • For contracts: A single line-level note is included in the BOD for each invoice line created by consolidating the notes from each contract line.

    When the Process.Invoice BOD is received by Distribution SX.e, the header-level and line-level notes are posted to the associated sales order. These notes can be viewed in the Distribution SX.e application:

    • Header-level notes: Displayed for the sales order (with the appropriate suffix associated with the invoice) in the Notes context widget.
    • Line-level notes: Displayed in the Internal Comment section on the Comments tab of the Sales Order Inquiry-Line Detail screen.
    Maximum Number of Retries
    When the Retry Invoice BOD field is selected, specify the maximum number of times to retry sending the BOD.
    Retry Invoice BOD
    Select this check box if you want to automatically retry the Process.Invoice BOD when it fails.
    Retry After
    When the Retry Invoice BOD field is selected, specify the number of seconds to wait between receiving an acknowledgement and resending the Process.Invoice BOD.
    Retry Service Order BOD with Invoice BOD
    Select this check box if you want to automatically resend the Sync.ServiceOrder BOD when the Process.Invoice BOD fails with the reason "Sales order for service order not found."
    Roll Up Labor on Service Orders

    Select this check box to consolidate the labor transactions on the Sync.ServiceOrder and Process.Invoice BODs that are sent to Distribution SX.e.

    When this check box is:

    • Selected: Labor transactions are grouped when these values are identical across transactions:

      • SRO line
      • SRO operation
      • Labor type
      • Work code
      • Rate
      • Unit cost
      • Discount percentage

      The hours for the matching labor transactions are combined and sent as a single labor line. The Planned and Actual labor transactions are processed separately and are not combined into the same labor line.

    • Cleared: Individual labor transactions are sent as separate labor lines.
    Note: This functionality affects only the BOD data that is sent to Distribution SX.e. ISM invoices, TBI reports, work orders, and other ISM-generated paperwork are not affected.
    Salesperson Selection
    Select whether you want to use the internal Distribution SX.e salesperson on the sales order or an external salesperson.

    When Internal is selected, the salesperson or customer ship-tos are updated with the internal Distribution SX.e salesperson from the CustomerPartyMaster/ShipToPartyMaster BOD when the BOD is received from Distribution SX.e. When External is selected, the external salesperson is used instead.

    Validate Customer Address
    Select this check box to validate customer address when an SRO is created.
  6. Click Save.
When the Distribution SX.e integration is enabled, the salesperson commission, sales PTD, and sales YTD are not calculated.