Troubleshooting delivered BOD integrations

This table provides possible solutions for problems that occur with delivered BOD integrations.

Problem Possible solutions
XM integration
  1. Verify that a one-way or two-way IMS connection exists in ION for Infor HR Talent and XM exists.
  2. Verify that the Document Flow is active that has Infor HR Talent as source application and XM as destination and Sync.Personnel and Sync.CodeDefintions BODS are part of the Document Flow.
  3. Verify that the Document Flow is active for GHR Sync.Personnel BOD to XM.
LN integration
  1. Verify that a one-way or two-way IMS connection exists in ION for Infor HR Talent and LN exists.
  2. Verify that the Document Flow is active that has Infor HR Talent as source application and LN as destination and Sync.Personnel and Sync.CodeDefintions BODS are part of the Document Flow.
  3. Verify that the Document Flow is active for GHR Sync.Personnel BOD to LN.
Infor Financials and Supply Management integration
  1. Verify that a one-way or two-way IMS connection exists in ION for Infor HR Talent and Infor Financials and Supply Management exists.
  2. Verify that the Document Flow is active that has Infor HR Talent as source application and Infor FSM as destination and Sync.Personnel and Sync.CodeDefintions BODS are part of the Document Flow.
  3. Verify that the Document Flow is active.

    For Legacy BOD for Source System Journal Entry, the Document Flow is:

    • (Outbound) GHR (Process.SSJE BOD) > GFC (XSLT bodxml MAPPING) (Sync.SSJE BOD) > CSF
    • (Inbound) GHR (Confirm/Acknowledge BOD) < GFC (BOD) < (Confirm/Acknowledge BOD) CSF