Setting Integration Parameters

  1. Open the Integration Parameters form. The Integration Parameters form is displayed.
  2. Select these check boxes in the Integrations section:
    • Enable Error BODs: To make the Error (Confirm) BODs visible in ION. If this check box is cleared, you can review the inbound BOD processing errors on the BOD Error Processing form.
    • Enable IDM Integration for Reports: To enable the Infor Document Management (IDM) templates. When this check box is selected, the XML handling routines produce report outputs in the IDM format and are stored in IDM. The report includes searchable attributes.
    Note: You can click SX.e Integration Parameters to access the SX.e Integration Parameters form.
  3. Specify this information in the Defaults section:
    Auto Create Item U/M
    Select this check box if you want to automatically create a unit of measure for an item that was created through an ItemMasterBOD when a U/M has not already been provided through the CodeDefinitionBOD from Distribution SX.e.

    If you clear the check box, and the Distribution SX.e U/M does not fit in the Service Management field, an error BOD is produced and rejected. See Processing BOD errors for more information.

    Note: Distribution SX.e allows users to specify a new unit of measure on their items even if the U/M does not already exist in the unit of measure code definition. When the new U/M is sent to Service Management through the ItemMasterBOD, the Auto Create Item UoM field determines if Service Management will map it on the fly.

    Distribution SX.e allows four characters for U/M but Service Management only allows three characters.

    These rules are applied when processing a new U/M through the ItemMasterBOD:

    • If Distribution SX.e U/M <= three characters, create Service Management U/M using Distribution SX.e U/M.
    • If Distribution SX.e U/M > three characters, truncate Distribution SX.e U/M to two characters and add a number at the end.

    Example: BOOK --> BO1, BOTL --> BO2

    These rules are applied when processing a new U/M through the CodeDefinitionBOD:

    • If Distribution SX.e U/M <= three characters, create Service Management U/M using Distribution SX.e U/M.
    • If Distribution SX.e U/M > three characters, create Service Management U/M using the Alternate Doc ID field (which is the EDI U/M in Distribution SX.e) from the BOD. If Alternate Doc ID is not provided in the BOD, an error BOD is produced.
    Avoid Cost Update by Receive Delivery
    Select this check box to automatically update the cost of planned materials (stocked and non-stocked) for a Service Repair Order (SRO). This cost is updated when the material cost for the associated sales order is modified in Distribution SX.e. The modified cost from Distribution SX.e is then sent to Service Management (ISM) through the Update-Cost API.

    If this check box is cleared, the cost of planned materials for an SRO is updated only when the Sync.ReceiveDelivery BOD is processed.

    Bank Code
    This field is required for Distribution SX.e. Select the default bank code to use.
    Cost Method
    This field is required for Distribution SX.e. Select a method that determines how inventory items assign the cost of an item when removed from inventory:
    • Specific
    • FIFO
    • Standard
    • Average
    • LIFO
    • Unit/Serial
    Note: Because inventory costing is handled by Distribution SX.e, we recommend that you select Average to let low-level Service Management routines process straightforwardly.
    Default Obsolete Reason Code
    Select a reason code to use by default when an item becomes obsolete. These are set up on the Obsolete Slow Moving Reason Codes form.

    If you are integrated with Distribution SX.e, when Distribution SX.e sends a product status of Inactive, the item Material Status is updated to Obsolete and the associated Reason code is displayed on the Items form in Service Management.

    Default Warranty Code
    Select a warranty code to use by default. This code must be set up on the Warranty Codes form first, and should have a Warranty Type of Vendor and Warranty Start Date Basis of Manual.

    If you perform a quick start implementation, then this value is automatically set to a warranty code named SXE.

    This code is used to create a unit warranty record when the Sync.Invoice BOD is sent from Distribution SX.e. In Distribution SX.e, if a serialized product is invoiced on a sales order that has an associated warranty, that warranty is tracked on the created unit. This process is done through the consumption of the Sync.Invoice BOD.

    Mileage Misc Code
    This field is for use with the Warranty Claim BOD. Select the code to use for mileage on warranty claim SRO miscellaneous transactions. These miscellaneous transactions will be consolidated into transportation costs on the Warranty Claim BOD.
    Mileage U/M
    This field is for use with the Warranty Claim BOD. Select the unit of measure to use in the transportation code in the Warranty Claim BOD.
    Miscellaneous Receipt Reason Code
    Select the miscellaneous receipt reason code to use by default. These are set up on the Miscellaneous Receipt Reason Codes form.
    Salesperson Classification
    Select the salesperson classification to use by default. You can set up salesperson classifications on the Salesperson Classifications form.
    Sync Invoice Email
    This setting determines if order invoicing or contract invoicing tasks on the Customer Document Profile form are automatically created or updated. This is based on the invoice email addresses from Customer Setup records in Distribution SX.e. The invoice email addresses are included in the Sync.CustomerPartyMaster BOD, which is generated when the initial data load is performed, or a customer record is created or updated.
    Note: When you update an existing customer record, only changes to certain values generate a CustomerPartyMaster BOD. A change to the invoice email address field does not generate a BOD.

    If you do change another value on the customer record that generates a BOD, the invoice email addresses are included in the BOD. The Customer Document Profile is automatically maintained. If you do not change a value that generates a BOD, manually maintain the Customer Document Profile to keep the records in sync. You can determine if a BOD was generated in ION or ION Desk.

    Select one of these values:
    • Neither: Neither order invoicing or contract invoicing tasks are automatically created or updated, based on invoice email addresses. You must create the tasks manually.
    • Order Invoicing: If a customer and ship to record for order invoicing task does not exist, an order invoicing task is created. If a customer and ship to record for order invoicing exists, the Destination field is updated with the invoice email addresses in the BOD.
    • Contract Invoicing: If a customer and ship to record for order invoicing does not exist, a record is created. If a customer and ship to record for contract invoicing exists, the Destination field is updated with the invoice email addresses in the BOD.
    • Both: Creates and updates both order invoicing and contract invoicing tasks.
    Terms Code
    This field is required for Distribution SX.e. Select the default terms code to use. The terms code is used to identify specific billing terms that apply to this customer or this order. This value displays as the default when you enter invoice and debit transactions. The terms code is used when determining the transaction due date and the discount information. The code entered here must be in the terms code file.

    Because Distribution SX.e is the source for terms codes, set this parameter after those codes have been integrated from Distribution SX.e. These values integrate from Distribution SX.e through the CodeDefinition BOD.

    The terms code is used to identify specific billing terms that apply to a customer or order. This value is displayed as the default when you enter invoice and debit transactions. The terms code is used when determining the transaction due date and the discount information. The code entered here must be in the terms code file.

    Treat Leading Zeros in ShipTo As Alpha
    When this check box is selected, the Distribtion SX.e shipto ID values are converted to alphanumeric values, following the ShipTo conversion rules. For example, the ID 00010 is converted to an alphanumeric value of 00010 instead of treating it as a numeric value 10.
    U/M
    This field is required for Distribution SX.e. Specify the default unit of measurement to use.

    Because Distribution SX.e is the source for U/M values, set this parameter after those values have been integrated from Distribution SX.e. These values integrate from Distribution SX.e through the CodeDefinition BOD.

  4. Click Save.