BOD Connectors

This section contains enhancements in Financials and Supply Management.

When a Customer Order Return has been processed in Taxengine the Temporary Hold field updates to be approved directly – Brazil Integration

For CustomerOrderReturn Scenario Changes done for updating Temporary Hold field in Sync_BROrderToReceipt_Inbound.

  • File Changed:
    • FSM_ION_SyncBROrdrToReceipt_Inbound.lpd
    • New Required Setup:No
    • New Variable Added in JSON: No
  • New IPA Changes:
    • Changed action to TaxEngineApprove in COReturn node
    • Integration Specific: Local.ly, Brazil
  1. Configuration:
    1. In Finance Enterprise Group BODTrigger checkbox should be checked
    2. In Channel Administrator activate FSM_ION_SyncBROrdrToReceipt_Inbound BOD - Sync.BROrderToReceipt.
  2. How to Test:
    1. When we consume FSM_ION_SyncBROrdrToReceipt_Inbound BOD.
    2. For CustomerOrderReturn Scenario, in CustomerOrderReturn and CustomerOrderReturnline TemporaryHold field should be set to ApprovedByEngine.

JR-3476816

Run Interface Match Invoice through BOD as part of the Load_SupplierInvoice_Inbound--Local.ly

  • Files Changed:

    FSM_ION_LoadSupplierInvoice_Inbound.lpd

    • Added new condition in Branch9150 branch.
    • Added new transaction node "IMInv".
    • Modified java script in "Assign3050" node.
    • New Required Setup:No
    • New Variable Added in JSON: No

    .Integration Specific: Local.ly

    1. Configuration:
      1. Enable Load_SupplierInvoice_Inbound in Channels adminstrations.
      2. Configure FinanceEnterpriseGroup value in system configuration for LoadSupplierInvoice_In_Locally_FEG.
    2. How to Test:
      1. Create PurchaseOrder, PurchaseOrderReceipt and Release.
      2. Send the valid input xml and it should trigger the BOD without any errors.
    3. Verify the Result:
      1. Check the Payables Invoice record and it should have all required information.

    JR-3539125

When the Acknowledge.BROrderToReceipt is received with a rejected status for Customer Order Return then the Temporary Hold field needs to update to Rejected By Engine in Customer Order Return – Brazil Integration

For CustomerOrderReturn Scenario Changes done for Updating TemporaryHold field with RejectedByEngine in AcknowledgeBROrderToReceipt_Inbound bod
  • Files Changed:
    • FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd
    • New Required Setup:No
    • New Variable Added in JSON: No
  • New IPA Changes:
    • In Start Added varaibles doclength,Return,ReturnSuffix
    • Added conditions in node Assign820,Branch6950
    • Added node COR
  • Integration Specific: Local.ly, Brazil
  1. Configuration:
    1. In FinanceEnterpriseGroup BODTrigger checkbox should checked.
    2. In Channel Administrator,activate FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd BOD - Acknowledge.BROrderToReceipt.
  2. How to Test:
    1. When we consume FSM_ION_AcknowledgeBROrderToReceipt_Inbound BOD .
    2. For CustomerOrderReturn Scenario, in CustomerOrderReturn and CustomerOrderReturnlineTemporaryHold field should be set to RejectedByEngine.

JR-3476814

When the Acknowledge.BROrderToInvoice is received with a rejected status for Vendor Return then the Temporary Hold field needs to update to Rejected By Engine – Brazil Integration

  • File Changed:
    • FSM_ION_AcknowledgeBROrdrToInv_Inbound.lpd
    • Variable Added in JSON: No
  • IPA Changes:

    In FSM_ION_AcknowledgeBROrdrToInv_Inbound IPA flow below changes done:

    • In Start Node - Added CustomerOrder and VendorReturn variable.
    • In Assign870 : Mapped x-path for CustomerOrder - Parse_BOD_XML_output.*::DataArea.*::BROrderToInvoice[0].*::OrderToInvoiceHeader.*::CustomerOrder
    • In Branch2410 : Added condition for VendorReturn rejected scenario . If CustomerOrder value not defined go to Assign7400.
    • In Assign7400 : Added this Node - Mapped value for VendorReturn.
    • Added FindVendorReturn Transaction node - Find the VendorReturn Record.
    • Added Branch1390 - If FindVendorReturn record exist it will update the VendorReturnLine and VendorReturn else go to end.
    • Added FindVRLine , UpdateVRLine and UpdateVendorReturn Transaction node.
  • Integration Specific: Local.ly, Brazil
  1. Configuration:
    1. In FinanceEnterpriseGroup, BODtrigger checkbox should be checked.
    2. In Channel Administration , Enable the Receiver for FSM_ION_AcknowledgeBROrdrToInv_Inbound IPA flow.
  2. How to Test:
    1. Trigger the bod for Acknowledge.BROrderToInvoice with rejected status.
    2. When we receive the Acknowledge.BROrderToInvoice with rejected status for Vendor Return scenario It will update the Temporary Hold status to Rejected By Engine.

JR-3476787

Changes needed for Receivables Tracker_Outbound – Local.ly to add/Change mappings for Mexico (MX).

Changes done for SyncReceivableTracker BOD when source of BillingInvoice is for Local.ly Integration MX country.

  • Files Changed:
    • FSM_ION_SyncReceivableTracker_Out.lpd
    • Variable Added in JSON: No
  • IPA Changes:
    • Added new flow Branch Node :4010 for Local.ly Integration MX country and added a Branch Node :2310.
  • Integration Specific: Yes; Mexico
  1. Configuration:
    1. In Finance Enterprise Group, BODtrigger checkbox should be checked.
    2. Enable the Service Definition and Processes.
  2. How to Test:
    1. Do required setup for Receivable Tracker flow.
    2. Create Billing Invoice, add Invoice Lines and release
    3. Run Invoice Verification Report
    4. Run Invoice And Register Print
    5. Run Sub System Update
    6. Verify the Receivable Invoice
    7. Create the Payment Record and Release
    8. Apply cash payment
    9. BOD will trigger and work unit will generate successfully without any error for FSM_ION_SyncReceivableTracker_Out BOD
  3. Verify the Result:
    1. Verify whether the requirements are working as expected.
    2. Result: Mappings shoulod be correct when user process through Billing Invoice.

JR-3266781

AR Receivable Invoice Scenario Add the Original Document ID node in SyncInvoice Outbound for Local.ly

For Receivable Invoice scenario (AR) PEPPOL access countries added InvoiceHeader/Correction/OriginalDocumentID/ID - SyncInvoice Outbound BOD Local.ly PEPPOL Access countries.

For Receivable Invoice scenario (AR) PEPPOL access countries updated Item Quantity under the dummy Invoice Line to -1 - SyncInvoice Outbound BOD Local.ly PEPPOL Access countries.

  • File Changed:
    • FSM_ION_SyncInvoice_Outbound.lpd
    • Variable Added in JSON: No
  • IPA Changes:

    In FSM_ION_SyncInvoice_Outbound IPA flow below changes done:

    • In Start node: added DummyQuantity variable.
    • In Assign 4190: Modified Java script for PEPPOL access countries DummyLine scenario - TransType=="C" (CreditMemo ) --> Quantity mapped as -DummyQuantity = -1

      In InvoiceLine/Quantity mapped the x-path as DummyQuantity.

    • In Assign1740 - Modified javascript.

      If SystemID ReceivableInvoice(AR) and Local.ly and specific to Australia(AU) Germany(DE) Netherlands(NL) NewZealand(NZ) Poland(PL) UnitedKingdom(GB) countries mapped OriginalBLInvoiceNumber = document1;

  • Integration Specific: Yes; Australia (AU) Germany (GE), Netherlands (NL), New Zealand (NZ), Poland (PL), United Kingdom (GB) countries.
  1. Configuration:
    1. In FinanceEnterpriseGroup, BODtrigger checkbox should be checked.
    2. Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound.Ipd Processes. Go to Service Definition and Enable ReceivableInvoiceService for FSM_ION_SyncInvoice_Outbound.Ipd Processes.
  2. How to Test:
    1. Create ReceivableInvoice and Release it.
    2. BOD will trigger and Work unit will generate With respective x-path values.
  3. Verify the Result:
    1. Create ReceivableInvoice (Credit Memo) and Release it.
    2. BOD trigger and Work unit will generate with respective x-path values InvoiceLine/Quantity as -1.

JR-3503363

ProcessInvoice_In BOD changes for Saudi Arabia (SA).

  • Files Changed:

    FSM_ION_ProcessInvoice_Inbound.lpd

    • Added new java script in Assign9440 node.
    • Added new branch condition in Branch6360 node.
    • New Required Setup:No
    • New Variable Added in JSON: No
  • Integration Specific: Local.ly; Saudi Arabia (SA)
  1. Configuration:
    1. Enable FSM_ION_ProcessInvoice_Inbound in Channels adminstrations.
    2. Configure IntegrationApplication value in system configuration as Local.ly.
  2. How to Test:
    1. Create Billing Invoice and Release.
    2. Send the valid input xml and it should trigger the BOD without any errors.
  3. Verify the Result:
    1. If the status is Failed/Rejected in input xml billing invoice should be in unrelease state.
    2. If the status is Registered in input xml billing invoice should be in Release state and FolioAuthorizationCode value also update.

JR-3543761

ProcessInvoice_In BOD changes for all PEPPOL applicable countries

  • Files Changed:

    FSM_ION_ProcessInvoice_Inbound.lpd

    • Added new variable in start node.
    • Modified java script in Assign6370 node.
    • Added new java script in Assign9440 node.
    • Added new branch condition in Branch6360 node.
    • New Required Setup: No
    • New Variable Added in JSON: No
  • Integration Specific: Local.ly; Australia (AU), New Zealand (NZ), Netherlands (NL), United Kingdon (GB), Poland (PL), Germany (GE) and other applicable countries
  1. Configuration:
    1. Enable FSM_ION_ProcessInvoice_Inbound in Channels adminstrations.
    2. Configure IntegrationApplication value in system configuration as Local.ly
  2. How to Test:
    1. Create Billing Invoice and Release.
    2. Send the valid input xml and it should trigger the BOD without any errors.
  3. Verify the Result:
    1. If the status is Failed/Rejected in input xml billing invoice should be in unrelease state.
    2. If the status is Forwarded in input xml billing invoice should be in Release state.

JR-3509902

When we receive the Acknowledge.BROrderToInvoice with rejected status for Vendor Return then we need to update the Temporary Hold status to Rejected By Engine

  • Files Changed:
    • FSM_ION_AcknowledgeBROrdrToInv_Inbound.lpd
    • Variable Added in JSON: No
  • IPA Changes:

    In FSM_ION_AcknowledgeBROrdrToInv_Inbound IPA flow below changes done:

    • In Start Node - Added CustomerOrder and VendorReturn variable.
    • In Assign870 : Mapped x-path for CustomerOrder

    Parse_BOD_XML_output.*::DataArea.*::BROrderToInvoice[0].*::OrderToInvoiceHeader.*::CustomerOrder

    • In Branch2410 : Added condition for VendorReturn rejected scenario . If CustomerOrder value not defined go to Assign7400. - In Assign7400 : Added this Node - Mapped value for VendorReturn.
    • Added FindVendorReturn Transaction node - Find the VendorReturn Record.
    • Added Branch1390 - If FindVendorReturn record exist it will update the VendorReturnLine and VendorReturn else go to end.
    • Added FindVRLine , UpdateVRLine and UpdateVendorReturn Transaction node.
  • Integration Specific: Yes; Brazil
    1. Configuration:
      1. In FinanceEnterpriseGroup, verify that the BODtrigger check box is selected.
      2. In Channel Administration, enable the Receiver for FSM_ION_AcknowledgeBROrdrToInv_Inbound IPA flow.
    2. How to Test:
      1. Trigger the BOD for "Acknowledge.BROrderToInvoice" with rejected status.
      2. When we receive the "Acknowledge.BROrderToInvoice" with rejected status for Vendor Return scenario, the Temporary Hold status is updated to "Rejected By Engine.

JR-3476787

When we receive the Acknowledge.BROrderToReceipt with rejected status for Customer Order Return then we need to update the Temporary hold field status to Rejected By Engine in Customer Order Return

  • Files Changed:

    FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd

    • New Required Setup: No
    • New Variable Added in JSON: No
  • New IPA Changes:
    • In Start Added varaibles doclength,Return,ReturnSuffix.
    • Added conditions in node Assign820,Branch6950.
    • Added node COR.
  • Integration Specific: Local.ly, Brazil
  1. Configuration:
    1. In FinanceEnterpriseGroup BODTrigger checkbox should checked.
    2. In Channel Administrator,activate FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd BOD - Acknowledge.BROrderToReceipt.
  2. How to Test:
    1. When we consume "FSM_ION_AcknowledgeBROrderToReceipt_Inbound" BOD.
    2. For CustomerOrderReturn Scenario, in CustomerOrderReturn and CustomerOrderReturnline TemporaryHold field should be set to RejectedByEngine.

JR-3476814

Run Interface Match Invoice through BOD as part of the Load_SupplierInvoice_Inbound-- Local.ly

  • Files Changed:

    FSM_ION_LoadSupplierInvoice_Inbound.lpd

    • Added new condition in Branch9150 branch.
    • Added new transaction node "IMInv".
    • Modified java script in "Assign3050" node.
    • .New Required Setup:No
    • New Variable Added in JSON: No
  • Integration Specific: Local.ly
  1. Configuration:
    1. Enable Load_SupplierInvoice_Inbound in Channels adminstrations.
    2. Configure FinanceEnterpriseGroup value in system configuration for LoadSupplierInvoice_In_Locally_FEG
  2. How to Test:
    1. Create PurchaseOrder, PurchaseOrderReceipt and Release.
    2. Send the valid input xml and it should trigger the BOD without any errors.
  3. Verify the Result:
    1. Check the Payables Invoice record and it should have all required information.

JR-3539125