Configuring Back Office Extension Integration

You must complete these tasks to configure the Back Office Extension integration.

Note: It is assumed that Infor ION and a supported ERP system are already installed and configured according to the documentation delivered with those products. For more information about configuring Back Office Extension with Infor CRM SLX, see the Infor CRM Implementation Guide.

The system administrator and users with the appropriate role can access these features. See What are Roles and Secured Actions?

To configure:

  1. Run the conversion utility provided for the selected version of Infor CRM SLX.
    Note: These options are not mandatory, are optional but have significant ramifications and must be enabled based on implementation-specific recommendations from the integrator or the Infor CRM SLX support team.
    • Master Data Consolidation
    • Isolate integrated content by logical ID
  2. Sign in as the administrator.
  3. Select Integrations from Administration or Integrations on the navigation bar. The Integrations list view is displayed.
  4. Select Back Office Extension in the Integrations list view. See Using the Integrations list view.
  5. Verify that the Enabled check box is selected.
    Note: You must clear the Enabled check box, to turn off synchronization.
  6. Click Save.
  7. Click the Options tab to specify the required data.
    • Select the Tenant row, click the Value column. Specify the implementation specific Infor LTR Tenant ID provided by your integrator or Infor CRM SLX support team.
    • Select the Logical ID row, click the Value column. Specify the Infor CRM SLX Logical ID defined in the Infor LTR based ION Desk Connection Point editor.
    • Infor CRM SLX recommends leaving the remaining items as the default values, but the items can be edited:
      Success Message Expiration
      The number of minutes after which success messages are purged from the log. The default setting is 4320. A value of -1 means that success messages are not purged from the log.
      Error Message Expiration
      The number of minutes after which error messages are purged from the log. The default setting is -1 which means that error messages are not purged from the log.
      Local CRM Pricing Quote
      Indicate if local CRM pricing is allowed for quotes. By default, this value is set to False.
      Local CRM Pricing Opportunity
      Indicate if the local CRM pricing is allowed for opportunities. The By default, this value is set to True.
      Local CRM Pricing Sales Order
      Indicate if local CRM pricing is allowed for sales orders. By default, this value is set to False.
      Log Success Messages
      Indicate if the log can include successful transactions. To exclude successful transactions from the log, click the Value column and type False. Setting this option to False reduces the items that are displayed for each record on the Sync History tab.
      Inbound Process List Size
      The number of BODs to be processed by a single job service thread. The default value is 10.
      Inbox Message Fetch Size
      The maximum number of BODs processed at any given time. The default value is 1000.
      Out of Sequence Message Expiration
      The length of time for which missing relationship information is stored in a log file. When BODs arrive out of sequence and have missing dependent data, the system stores the missing relationships in a log. The default value is 24 hours.
      Acknowledge Message Timeout (in minutes)
      The maximum delay for Infor CRM SLX back office to respond to the Process BOD request with the Acknowledge response. The default value is 10.
      Associate Roles to Unsynced Account
      The option to restrict the generation of new Ship to or Bill to records until after the associated account is successfully promoted. By default, this value is set to False. When set to True, Ship to or Bill to records can be created for an account, that has not yet been promoted.
      Inbound Poling Interval (in seconds)
      The time duration (in seconds) between inbound sync jobs. The duration is defined as the time period between the completion of one inbound sync job and the start of the next inbound sync job. The default value is 15.
      Outbound Poling Interval (in seconds)
      The time duration (in seconds) between outbound sync jobs. The duration is defined as the time period between the completion of one outbound sync job and the start of the next outbound sync job. The default value is 15.
      Default Quote Duration (in days)
      The default time duration (in days) between the start date and expiration date when creating a quote, if the expiration date is not specified.
      Numeric Culture
      The Culture setting used by the Job Server when parsing numeric content saved in BODs. Although this field is editable, you must not modify the default setting (en-US) unless instructed to do so by Infor CRM SLX Support Personnel.
      Type of Order Location
      The Quote and Sales Order location lookup filter criteria for the selection of the transaction's integrated location value. Type Office, Warehouse or Site to indicate the type of location required by the host ERP system. To hide the Quote and Sales Order location lookup controls, the field value must be blank. The type of Order location by ERP:
      • SX: Warehouse
      • LN: Office, Site or Warehouse
      • M3: Warehouse
      • CSI: Warehouse
      • Visual: Site
      Price Overrides enabled
      Indicates if the Infor CRM SLX users can override integrated quote or sales order unit pricing. If set to True, this setting enables the Infor CRM SLX price override feature for authorized users. Enabling the Price Override feature requires the corresponding Price Adjustment feature to be disabled. These host ERP systems support integrated Infor CRM SLX Sales Order price overrides:
      • Infor Syteline
      • Infor CloudSuite Industrial
      • Infor Distribution SX.e
      • Infor LN
      Note: Infor CRM SLX also supports price overrides for quote-based unit pricing. However, promoting quotes containing Infor CRM SLX-based price overrides is not supported.
      Price Adjustments enabled
      Indicates if the Infor CRM SLX users can apply price adjustments to the integrated quote or sales order unit pricing. If set to True, this setting enables the Infor CRM SLX price adjustment feature, for authorized users. Enabling the Price Adjustment feature requires the Price Override feature to be disabled. The Price Adjustment feature also depends upon the ERP Price Override Reason Code and CRM Price Override Reason Code custom settings. These host ERP systems support integrated Infor CRM SLX Sales Order containing price adjustments:
      • Infor Syteline
      • Infor CloudSuite Industrial
      • Infor LN
      Note: Infor CRM SLX supports price adjustments for Quote-based unit pricing. However, promoting Quotes containing CRM SLX-based price adjustments is not supported.
      CRM Price Override Reason Code
      The implementation-specific line-level Distributed Charge Reason Code, published for the combined ERP and Infor CRM SLX-based price adjustment percentage. Possible scenarios:
      • SyteLine or CSI integrations: The Data Value field must be blank.
      • LN integrations: Set the Data Value to the implementation-specific line-level Distributed Charge Reason Code, published for the summary CRM-based SalesOrderLine/DistributedCharge Bod element.
      Note: For assistance defining this unique Distributed Charge Reason Code, check with the LN administrator or integrator.
      ERP Price Override Reason Code
      The implementation-specific line-level Distributed Charge Reason Code, published for the combined ERP and Infor CRM SLX-based price adjustment percentage. Possible scenarios:
      • SyteLine or CSI integrations: Set the Data Value to Discount.
      • LN integrations: Set the Data Value to the implementation-specific line-level Distributed Charge Reason Code, published for the summary ERP-based SalesOrderLine/DistributedCharge Bod element.
      Note: For assistance defining this unique Distributed Charge Reason Code, check with the LN administrator or integrator.
      Filter products by transaction
      The option to specify the Quote and Sales Order Product filtered lookup criteria, based on the transaction’s location settings. Select one of these options based on the requirements of the integrated host ERP system:
      • Logical ID
      • Accounting Entity
      • Warehouse
      • Site
      Filter products by fixed Logical Id
      Tthe option to specify the Quote and Sales Order filtered Product lookup criteria, based on a specified Logical ID. Enter The Back Office Logical ID that publishes the host ERP system's products to be used for all Quotes and Sales Orders. This value is considered only if, the Filter products by transaction custom setting is not specified.
    • Click Save.
  8. Click the Outbound Message Settings tab to define the parent-child relationships that can auto-promote parent records based on modifications to one or more of the dependent child records.
    • Infor CRM SLX recommends leaving the remaining Outbound Message Settings with the out of the box settings unless otherwise instructed by CRM SLX support.
      Contact
      The contact reference defined by the integrated back office application.
      Account
      The customer reference defined by the integrated back office application.
      ERPBill To
      The Bill To reference defined by the integrated back office application.
      ERPPay From
      The Pay From reference defined by the integrated back office application.
      Address
      The address reference defined by the integrated back office application.
      ERPTrading Account
      The account reference defined by the integrated back office application.
      ERPBillTo Contact
      The contact reference defined by the integrated back office application. A many-to-many relationship exists between Bill To and Contact.
      ERPBillTo Account
      The account reference defined by the integrated back office application. A many-to-many relationship exists between Bill To and Account.
      ERPContact Account
      The contact relationship defined by the integrated back office application.
      Sales Order
      The sales order reference defined by the integrated back office application.
      Quote
      The quote reference defined by the integrated back office application.
      ERPShipTo Account
      The customer reference defined by the integrated back office application. A many-to-many relationship exists between Ship To and Account.
      ERPShipToContact
      The customer reference defined by the integrated back office application. A many-to-many relationship exists between Ship To and Contact.
      ERPBillTo ShipTo
      The customer reference defined by the integrated back office application. A many-to-many relationship exists between Bill To and Ship To.
      ERPPayFrom BillTo
      The billing address defined by the integrated back office application. A many-to-many relationship exists between Pay From and Bill To.
      ERPPayFrom Contact
      The contact relationship defined by the integrated back office application. A many-to-many relationship exists between Pay From and Contact.
      Quote Item
      The quote item defined by the integrated back office application.
      Quote Address
      The quote address defined by the integrated back office application.
      SalesOrder Item
      The sales order item defined by the integrated back office application.
    • Click Save.
  9. Select the required back office link in the Back Offices tab, and use the Back Office detail view to:
    1. Configure the back office information fields. See Using the Back Office detail view.
    2. Add a new accounting entity using the Accounting Entities tab. See Adding an accounting entity (back office extension).
    Note: If the required back office does not exist, the standard Bod Pack for the integrated host ERP system must be installed.
  10. Use the BOD Mapping detail view to:
    1. Modify an existing BOD mapping. See Using the BOD mappings detail view.
    2. Add a BOD field mapping. See Defining a BOD field mapping.
    3. Edit a BOD field mapping. See BOD Mappings tab.
    Note: 
  11. Add the users to the Integration role to give individual users access these administrative integration views:
    • Back Office
    • BOD Mappings
    • Field Mappings
    • ERP Persons
  12. Add the users to the BackOffice role to give individual users access to these non-administrative integration views:
    • Invoices
    • Receivables
    • Shipments
    • Bill To
    • Ship To
    • Pay From
    • ERP Persons (View)
Related topics