BOD Connectors

This section contains enhancements in Infor Financials and Supply Management.

Changes to Acknowledge.BROrderToReceipt inbound BOD - Local.ly integration for Brazil (BR)

Changes made to the Acknowledge.BROrderToReceipt inbound BOD with rejected status. The temporary hold field is updated to "Rejected By Engine" in the line and header level and then the Receipt is deleted.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes: Yes.
  • Integration Specific: Yes. Local.ly integration for Brazil (BR).

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup BODTrigger check box should checked.
  2. In Channel Administrator, activate FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd BOD - Acknowledge.BROrderToReceipt.
  3. When the "FSM_ION_AcknowledgeBROrderToReceipt_Inbound" BOD is consumed, in PurchaseOrderReceiptLines and PurchaseOrderReceipt TemporaryHold field should be set to "Rejected By Engine" and the receipt is deleted.

JR-3320530

Changes to Acknowledge.BROrderToInvoice inbound BOD - Local.ly integration for Brazil (BR)

Changes made to the Acknowledge.BROrderToInvoice inbound BOD to update the Temporary Hold field to "Rejected by Engine" and delete the shipment when the inbound BOD has a response of "Rejected".

Program/Business class/Process affected:

  • Files Changed: FSM_ION_AcknowledgeBROrdrToInv_Inbound.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes: Yes.
  • Integration Specific: Yes. Local.ly integration for Brazil (BR).

Use these steps to test the enhancement:

  1. The Acknowledge.BROrderToInvoice inbound BOD in consumed with a "Rejected" resonse.
  2. It will find the record in WarehouseShipment.
  3. It will update the WarehouseShipment record with TemporaryHold field as "R" (Rejected By Engine)
  4. It will perform Undo Action (ship ,pick and Pack).
  5. It will delete the Shipment.

JR-3323115

Changes to Sync_ShiptoPartyMaster_Outbound outbound BOD - Local.ly integration for Brazil (BR)

Changed the LocationID value in Sync_ShiptoPartyMaster_Outbound Sync.ShipToPartyMaster_Outbound BOD.

Program/Business class/Process affected:

  • File Changed: FSM_ION_SyncShipToPartyMaster_Out.lpd
  • Variable Added in JSON: Yes. Added CustomerGroup variable in "JSONParser5230"
  • IPA Changes: Yes. Changes in FSM_ION_SyncShipToPartyMaster_Out IPA flow:
    • Start node: Added LocationID in start node.
    • In Assign:Added javascript."Local.ly" && Country Brazil . location value as "CustomerGroup@@Customer@@ShipTo"
    • In Ship_To-XML:for LocationID x-path earlier passed as location now changed as LocationID and @NoNullTag@ added.
  • Integration Specific: Yes. Local.ly integration for Brazil (BR).

Use these steps to test the enhancement:

  1. Configuration: In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Configuration: Enable the Service Definition and Processes for FSM_ION_SyncShipToPartyMaster_Out IPA flow.
  3. Configuration: Go to Service Definition and Enable "CustomerShipToService" for " FSM_ION_SyncShipToPartyMaster_Out.lpd" Processes.
  4. Create/Update /delete CustomerShipTo record.
  5. BOD will trigger and Work unit will generate With respective newly added element.
  6. Verify Result:
    1. In the ApplicationArea for BODID we are sending the location value as "CustomerGroup@@Customer@@ShipTo"
    2. DataArea/Sync/LocationID-- Is blank.

JR-3342137

Changes to Acknowledge.BROrderToReceipt_Inbound inbound BOD - Local.ly integration for Brazil (BR)

Updated the Temporary Hold field in the Purchase Order record, Acknowledge.BROrderToReceipt_Inbound. When the "Acknowledge.BROrderToReceipt" BOD is received with rejected status then the temporary hold field status is updated to "Rejected by Engine" and the receipt record is deleted. After that the Temporary hold field status is updated in Purchase Order Line level and Purchase Order Receipt level also updated to "Rejected by Engine".

Program/Business class/Process affected:

  • Files Changed: FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes: Yes.
  • Integration Specific: Yes. Local.ly integration for Brazil (BR)

Use these steps to test the enhancement:

  1. Configuration: In FinanceEnterpriseGroup BODTrigger check box should checked.
  2. In Channel Administrator, activate FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd BOD - Acknowledge.BROrderToReceipt.
  3. Consume "FSM_ION_AcknowledgeBROrderToReceipt_Inbound" BOD.
  4. After deleting the PurchaseOrderReceipt, in PurchaseOrderLines and PurchaseOrder TemporaryHold field should be updated to RejectedByEngine.

JR-3351245

Changes to AcknowledgeBROrderToReceipt_Inbound inbound BOD - Local.ly integration for Brazil (BR)

Updated theTemporary field status to Blank in Purchase Order Header and line when receiving "AcknowledgeBROrderToReceipt_Inbound" bod with Rejected status

Program/Business class/Process affected:

  • Files Changed: FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes: Yes.
  • Integration Specific: Yes. Local.ly integration for Brazil (BR)

Use these steps to test the enhancement:

  1. Configuration: In FinanceEnterpriseGroup BODTrigger check box should checked.
  2. In Channel Administrator, activate FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd BOD - Acknowledge.BROrderToReceipt.
  3. Consume the "FSM_ION_AcknowledgeBROrderToReceipt_Inbound" BOD.
  4. Work Unit should trigger without any errors.
  5. The TempHold flag updates to blank in PurchaseOrder and PurchaseOrderLines.

JR-3353770

Changes to Sync_BROrderToInvoice_Inbound inbound BOD - Local.ly integration for Brazil (BR)

For a shipment number in Shipment range when running Order Entry Daily Shipment Journal in "Sync_BROrderToInvoice_Inbound"
  • When receiving the SYnc_BROrderToInvocie_Inbound then, run the Order Entry Daily Shipment Journal. Specify our Shipment value in "OrderEntryDailyShipmentJournal. FromShipment" and "OrderEntryDailyShipmentJournal.ToShipment"
  • While running OrderEntryDailyShipmentJournal we need Shipment range for "Sync_BROrderToInvoice_Inbound" BOD.

Program/Business class/Process affected:

  • Files changed: Sync_BROrderToInvoice_Inbound.ipd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes: Yes. In OEDailyShip Node: added FromShipment and ToShipment field for Shipment range. Removed SelectOption field.
  • Integration Specific: Yes. Local.ly integration for Brazil (BR).

Use these steps to test the enhancement:

  1. Configuration: In FinanceEnterpriseGroup BODTrigger check box should checked.
  2. In Channel Administrator, activate FSM_ION_SyncBROrdrToInv_Inbound BOD -Sync.BROrderToInvoice.
  3. Consume "FSM_ION_SyncBROrdrToInv_Inbound" BOD.
  4. The record in TaxEngineTaxHeader is created.
  5. The record in TaxEngineTaxDetail is created.
  6. The record in TaxEngineTaxLine is created.
  7. The record in WarehouseShipment is found.
  8. Updates the WarehouseShipment record with TemporaryHold field as "A" (Approved By Engine).
  9. Releases the WarehouseShipment.
  10. Performs the OrderEntryDailyShipmentJournal action and passes the Shipment range.

JR-3353781

Changes to AcknowledgeBROrderToReceipt_Inbound inbound BOD - Local.ly integration for Brazil (BR)

Updated Workunit of AcknowledgeBROrderToReceipt_Inbound" BOD with Rejected status.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes: Yes.
  • Integration Specific: Yes. Local.ly integration for Brazil (BR).

Use these steps to test the enhancement:

  1. Configuration: In FinanceEnterpriseGroup BODTrigger check box should checked.
  2. In Channel Administrator, activate FSM_ION_AcknowledgeBROrderToReceipt_Inbound.lpd BOD - Acknowledge.BROrderToReceipt.
  3. Consume the "FSM_ION_AcknowledgeBROrderToReceipt_Inbound" BOD.
  4. Work Unit should trigger without any errors.

JR-3367199

Implimented discount functionality in the Sync_BROrderToReceipt_Inbound - Local.ly integration for Brazil (BR)

When the discount is sent from the tax engine, the discount amount is recieved in the OrderToReceiptLine/DicountAmount node. For Match Invoice, a Add On Charge record is created with the AOC code from the system Configuration Parameter. For Expense Invoice, the Distribution is created using the negative sign amount and AOC code from the system configuration.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncBROrdrToReceipt_Inbound.lpd
  • New Required Setup: No.
  • .New Variable Added in JSON: No.
  • New IPA Changes: Yes.
  • Integration Specific: Yes. Local.ly integration for Brazil (BR).

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup BODTrigger check box should checked.
  2. In Channel Administrator,activate FSM_ION_SyncBROrdrToReceipt_Inbound BOD - Sync.BROrderToReceipt.
  3. When we consume "FSM_ION_SyncBROrdrToReceipt_Inbound" BOD .
  4. For MatchInvoice and ExpenseInvoice Scenario.
  5. If we reeceive discount amount from the Xpath OrderToReceiptLine/DicountAmount then PayablesInvoice should be created and released with those discount amounts.

JR-3410424

Changes to Sync_BROrderToInvoice_Inbound BOD - Local.ly integration for Brazil (BR)

Updated to call "TaxEngineApprove" action instead of updating Temporary Hold field value directly when receiving the Sync_BROrderToInvoice_Inbound as part of the Vendor return Process. For the goods.return scenario, process the TaxEngineApprove" action to update Temporary Hold field value in VendorReturn Sync_BROrderToInvoice_Inbound.

Program/Business class/Process affected:

  • Files Changed: Sync_BROrderToInvoice_Inbound.ipd
  • New Required Setup: No.
  • .New Variable Added in JSON: No.
  • New IPA Changes: Yes.
  • Integration Specific: Yes. Local.ly integration for Brazil (BR).

Use these steps to test the enhancement:

  1. Consume the "FSM_ION_SyncBROrdrToInv_Inbound" BOD goods.return scenario:
  2. Create the record in TaxEngineTaxHeader.
  3. Create the record in TaxEngineTaxDetail.
  4. Create the record in TaxEngineTaxLine.
  5. Find the VendorReturn Record.
  6. Perform TaxEngineApproveAuthorizedByVendor Action on Vendor Return and update Temporary Hold field as "A" (Approved By Engine).
  7. Perform ShipAuthorizedByVendor Action on Vendor Return.
  8. If the VendorReturn.VendorClaimType == "CM" , it will create MatchInvoiceimport.
  9. Perform InterfaceInvoices on MatchInvoiceimport.

JR-3395419

Changes to SyncInvoice Outbound BOD - Local.ly integration for New Zealand (NZ)

Added the GLN Scheme ID on Customer Tax ID in SyncInvoice Outbound BOD. Updated the Customer Tax ID and Endpoint ID to the correct test identifier.

Program/Business class/Process affected:

  • File Changed: FSM_ION_SyncInvoice_Outbound.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes: Yes.
  • Integration Specific: Yes. Local.ly integration for New Zealand (NZ).

Use these steps to test the enhancement:

  1. Configuration: Enable FSM_ION_SyncInvoice_Outbound BOD in Service definitions.
  2. Configuration: Set IntegrationApplication as Local.ly.
  3. Create Receivable invoice for Newzealand country with Local.ly,
  4. BOD will trigger and Work unit will generate Without any errors.
  5. Verify the Result: Verify the SchemaID in Customer Tax ID.

JR-3353781

Currency Exchange rate record should be created with action code "Replace"

CurrExchangeRate record should create even if ActionCode is Replace by checking its existence if record not present.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncCurrencyExchangeRateMaster_Inbound.lpd
  • New Required Setup:Configure GeneralLedger_BODS_FinanceEnterpriseGroup value in System Configuration.
  • New Variable Added in JSON: No
  • New IPA Changes: Added nodes Branch5070,Find.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. Configuration: In Channels Administrator create record for Sync.CurrencyExchangeRateMaster Inbound BOD.
  2. Configure GeneralLedger_BODS_FinanceEnterpriseGroup value in System Configuration.
  3. Send valid xml for Sync CurrencyExchangeRateMaster BOD.
  4. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCurrencyExchangeRateMaster_Inbound BOD.
  5. Verify the Result: CurrExchangeRate record should create even if ActionCode is Replace by checking its existence if record not present.

JR-3345093

Changes to SupplierInvoice BOD

SupplierInvoice BOD did not populate Description and Reference fields of the Invoice Distribution line. That has been changed.

  • Xpath for Description is SupplierInvoice/SupplierInvoiceHeader/Distribution/UserArea/Property
  • Xpath for Reference is SupplierInvoice/SupplierInvoiceHeader/Distribution/UserArea/Property
  • Send new parameter in UserArea of Header, “ApprovalRequired” = Y/N, based on this flag, we will modify invocation of Release action in IPA flow. The Xpath is SupplierInvoice/SupplierInvoiceHeader/UserArea/Property
  • Added new fields(Description, Reference) in PayablesInvoiceDistribution through process supplier invoice BOD. Send new parameter in UserArea of Header, “ApprovalRequired” = Y/N, based on this flag, we will modify invocation of Release action in IPA flow. The Xpath is SupplierInvoice/SupplierInvoiceHeader/UserArea/Property

Program/Business class/Process affected:

  • Files Changed: FSM_ION_ProcessSupplierInvoice_Inbound.lpd
  • Variable Added in JSON: No.
  • IPA Changes: Changes is FSM_ION_ProcessSupplierInvoice_Inbound IPA flow.
    • Added new variable in start node.
    • Modified java script in "Assign7510" node.
    • Modified Branch condition in "Branch8680" node.
    • Modified java script in "Assign2650" node.
    • Modified java script in "Assign9110" node.
    • Modified java script in "Assign6300" node.
    • Modified java script in "Assign4720" node.
    • Modified java script in "Assign4420" node.
    • Modified "CreateDist" transaction node.
    • Modified "MsgBuilder9790" node.
    • Modified "MsgBuilder2660" node.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. Configuration: Enable FSM_ION_ProcessSupplierInvoice_Inbound BOD in channels Adminstrator.
  2. Set the Configuration parameter value for "ProcessSupplierInvoice_Batch" to online/interface.
  3. Send the ApprovalRequired value Y/N in Header user area level.
  4. Send the xml with description and reference values in distribution user area level.
  5. BOD will trigger and Work unit will generate Without any errors.
  6. Verify the Result:
    • If ApprovalRequired value set to Y the PayablesInvoice will create in unreleased state.
    • If ApprovalRequired value set to N the PayablesInvoice will create in Released state.
    • If ProcessSupplierInvoice_Batch set to online verify the PayablesInvoice and Distribution records in FSM with description and reference fields.
    • If ProcessSupplierInvoice_Batch set to interface verify the PayablesInvoiceImport and Distribution records in FSM with description and reference fields.

JR-3359597

Toggle for User Fields for BOD changes for IPA

Added new System Configuration Parameter "ProcessSSJE_Payroll_Integration_UserFields" with default value of N.
  • When the value is set to "N", the BOD values for Pay Code, Job Code, Position Code and Deduction Code will be populated in the user fields JOB, PAYCODE, POSITION and DEDUCTIONCODE.
  • When the Value is set to "Y", the BOD values for Pay Code, Job Code, Position Code and Deduction Code will be populated in the new user fields UserJob, UserPayCode, UserPosition, UserDeduction.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_ProcessSourceSystemJournalEntry_Inbound.lpd
  • Variable Added in JSON: No.
  • IPA Changes: Changes in FSM_ION_ProcessSourceSystemJournalEntry_Inbound IPA flow.
    • Added new variables in start node.
    • Modified java script in "ExtractHeader" node.
    • Modified "GLTransactionInterface" transaction node.
    • Modified java script in "IncCounters" node.
    • Integration Specific: Yes. FSM-Payroll.

Use these steps to test the enhancement:

  1. Configuration: Enable FSM_ION_ProcessSourceSystemJournalEntry_Inbound BOD in channels Adminstrator.
  2. Create user fileds.
  3. Set the Configuration parameter value for "ProcessSSJE_Payroll_Integration_UserFields" to Y/N.
  4. Consume the XML from source system.
  5. BOD will trigger and Work unit will generate Without any errors.
  6. Verify the Result: Verify the GLTransactionInterface records in FSM.

JR-3359942