Configuring Back Office Extension Integration
You must complete these tasks to configure the Back Office Extension integration.
Note: This section assumes that Infor ION and a supported ERP system
are already installed and configured according to the documentation delivered with
those products. Also see the Infor CRM Implementation
Guide for information about configuring Back Office Extension with
Infor CRM SLX.
The system administrator and users with the appropriate role can access these features. See What are Roles and Secured Actions?
To configure:
-
Run
theSLXConversionUtility.exe.
Note: This needs to be done only once to support all integrations.
- Sign in as the administrator.
- Select Back Office Extension in the Integrations list view. See Integrations list view
-
Verify that the Enabled check box is
selected.
Note: To turn off synchronization, clear the Enabled check box.
- Click Save.
-
Click the
Options
tab and
perform
these
steps:
- Select the Tenant row, click the Value column. Specify the Tenant name that is defined when configuring the ERP connection in ION Desk.
- Select the Logical ID row, click the Value column. Specify the Logical ID for Infor CRM SLX. The Logical ID is generated when configuring connection information for Infor CRM SLX in ION Desk.
-
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 never 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 never purged from the log.
- Local CRM Pricing Quote
- Use this field to enable or disable the local CRM pricing for quotes. The default Value is False.
- Local CRM Pricing Opportunity
- Use this field to enable or disable the local CRM pricing for opportunities. The default value is set to True.
- Local CRM Pricing Sales Order
- Use this field to enable or disable the local CRM pricing for sales orders. The default value is set to False.
- Log Success Messages
-
The default value is True, which means the log includes successful transactions. To exclude successful transactions from the log, click the Value column and specify False. Setting this option to False reduces the items that display in each record 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
- Defines the length of time 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)
- Defines the maximum delay Infor CRM SLX for the back office to respond to the Process BOD request with the Acknowledge response. The default value is 10.
- Outbound Retry Count
- The maximum number of times an outbound record is sent unsuccessfully. The default value is 3.
- Associate Roles to Unsynced Account
- Restricts the generation of new ship to or bill to records until after the associated account is successfully promoted. The default value is 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 duration in seconds between execution of inbound sync jobs. The duration is defined as the time period from the completion of one inbound sync job to the start of the next inbound sync job. The default value is 15.
- Outbound Poling Interval (in seconds)
- The duration in seconds between execution of outbound sync jobs. The duration is defined as the time period from the completion of one outbound sync job to the start of the next outbound sync job. The default value is 15.
- Default Quote Duration (in days)
- The default number of days between the start date and expiration date when creating a quote, if the expiration date is left blank.
- Numeric Culture
- Defines the Culture setting used by the Job Server when parsing numeric content contained in BODs. Although this field is editable, do not edit the default setting (en-US) unless instructed to do so by Infor CRM SLX Support Personnel.
- Click Save.
-
Click the
Outbound Message Settings
tab and
perform
these
tasks:
- Select the row to edit, and click the Entity or Parent column and specify the changes.
-
Infor CRM SLX
recommends leaving the remaining items as the default custom setting
values, but the items can
edited:
- Contact
- Contact reference defined by the integrated back office application.
- Account
- Customer reference defined by the integrated back office application.
- ERPBill To
- Bill To reference defined by the integrated back office application.
- ERPPay From
- Pay From reference defined by the integrated back office application.
- Address
- Address reference defined by the integrated back office application.
- ERPTrading Account
- Account reference defined by the integrated back office application.
- ERPBillTo Contact
- Contact reference defined by the integrated back office application. This a many-to-many relationship between Bill To and Contact.
- ERPBillTo Account
- Account reference defined by the integrated back office application. This a many-to-many relationship between Bill To and Account.
- ERPContact Account
- Contact relationship defined by the integrated back office application.
- Sales Order
- Sales order reference defined by the integrated back office application.
- Quote
- Quote reference defined by the integrated back office application.
- ERPShipTo Account
- Customer reference defined by the integrated back office application. This a many-to-many relationship between Ship To and Account.
- ERPShipToContact
- Customer reference defined by the integrated back office application. This a many-to-many relationship between Ship To and Contact.
- ERPBillTo ShipTo
- Customer reference defined by the integrated back office application. This a many-to-many relationship between Bill To and Ship To.
- ERPPayFrom BillTo
- Billing address defined by the integrated back office application. This a many-to-many relationship between Pay From and Bill To.
- ERPPayFrom Contact
- Contact relationship defined by the integrated back office application. This a many-to-many relationship between Pay From and Contact.
- Quote Item
- Quote item defined by the integrated back office application.
- Quote Address
- Quote address defined by the integrated back office application.
- SalesOrder Item
- Sales order item defined by the integrated back office application.
- Click Save.
-
Select the
desired back office link
in
the
Back Offices tab,
and use the
Back
Office
detail
view
to:
Note: If the desired back office does not exist, you must add a new back office first. See Adding a back office.
- Configure the back office information fields. See Using the Back Office detail view.
- Use the Accounting Entities tab to add a new accounting entity. See Adding an accounting entity (back office extension).
-
(Optional) Use the
ION
BOD Mapping
detail
view
to:
Note: If the desired ION BOD mapping does not exist, you must add a new ION BOD mapping first. See Adding a BOD mapping (back office extension).
- Edit an existing ION BOD mapping. See Using the BOD mappings detail view.
- Add a BOD field mapping. See Defining a BOD field mapping.
- Edit a BOD field mapping. See BOD Mappings Tab.
-
Grant
the appropriate
access.
- Add
the users to the Integration role
to
give individual users access
these
administrative integration
views:
- Back Office
- ION BOD Mappings
- ION Field Mappings
- ERP Persons
- 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)
- Add
the users to the Integration role
to
give individual users access
these
administrative integration
views: