BOD Connectors

This section contains enhancements in Infor Financials and Supply Management.

Process Shipment BOD to Carry Code Block value to be updated in Debit Account of Inventory Transaction

Program/Business class/Process affected:

  • Files Changed:
    • FSM_ION_ProcessShipment_Inbound
    • PfiConfigurationProperty.xml
  • New Required Setup: Added new configuration parameter DefaultDebitCodeBlock = Y/N
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • Added new configuration parameter DefaultDebitCodeBlock
    • Added Branch7000, Assign2330, Branch5390, Assign8980, Assign8190 ,Branch2210, Branch2630, FindInvTranLine, Assign330, XML1500
  • Integration Specific: Yes. FSM-IPS.

Use these steps to test the enhancement:

  1. Setup:
    1. In the Finance Enterprise Group, in Options, select the BOD Trigger check box.
    2. In the Channels Administrator, activate the respective ION Inbox Receivers for FSM_ION_ProcessShipment_Inbound.
    3. Configure the paramenter DefaultDebitCodeBlock = Y/N
  2. When FSM_ION_ProcessShipment_Inbound BOD is processed, Work Unit is triggered.
  3. A InventoryTransaction is created and released.
  4. Verify the Result:
    1. Verify that a InventoryTransaction is created and released without any errors.
    2. If Configuration parameter DefaultDebitCodeBlock == "Y", then the value from this xpath is the default in the InventoryTransaction and InventoryTransactionLine.
    3. BOD Element: When the dimensions are sent in Shipment/ShipmentHeader/UserArea they should update in InventoryTransaction: Default Debit Account.
    4. When the dimensions are sent in Shipment/ShipmentLine/UserArea they should update in InventoryTransactionLine: Debit Account.

Dependencies: None.

JT-1755696 / JR-3266780

Add scheme name for Endpointid SyncInvoice Outbound bod for Local.ly New Zealand

Program/Business class/Process affected:

  • File Changed: FSM_ION_SyncInvoice_Outbound.lpd
  • Variable Added in JSON: No.
  • IPA Changes: In FSM_ION_SyncInvoice_Outbound IPA flow below changes were made.
    • Start Node: added variable "CustomerPartySchemeName".
    • Assign1740:Modified javascript.For "Local.ly" && AddressCode != "" && AddressCode_PostalAddress_Country =="NZ" .CustomerPartySchemeName="TaxIdentificationNumber";
  • Integration Specific: Yes. These changes are related to Local.ly Integration specific to New Zealand (NZ).

Use these steps to test the enhancement:

  1. Setup: In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Setup: Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.
  3. Setup: Go to Service Definition and Enable "ReceivableInvoiceService" for "FSM_ION_SyncInvoice_Outbound.lpd" Processes.
  4. Create ReceivableInvoice and Release it.
  5. BOD will trigger and Work unit will generate With respective newly added element.
  6. Create BillingInvoice Release it.
  7. Perform InvoiceVerificationReport.
  8. Perform InvoiceAndRegisterPrint.
  9. Perform SubSystemUpdate.
  10. BOD will trigger and Work unit will generate With respective newly added element.
  11. Verify the Result: In InvoiceHeader/CustomerParty/PartyIDs/EndPointID@schemeName="TaxIdentificationNumber" added.

Dependencies: None.

JR-3297799

Scheme ID for Endpointid of customer in SyncInvoice Outbound bod for Local.ly for Germany (DE)

Program/Business class/Process affected:

  • File Changed: FSM_ION_SyncInvoice_Outbound.lpd.
  • Variable Added in JSON: No.
  • IPA Changes: In FSM_ION_SyncInvoice_Outbound IPA flow the below changes were made:

    Assign1740: Modified javascript."Local.ly" && AddressCode != "" && AddressCode_PostalAddress_Country =="DE" . AUschemeID = "DE:VAT";

  • Integration Specific: Yes. These changes are related to Local.ly Integration specific to Germany (DE).

Use these steps to test the enhancement:

  1. Setup: In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Setup: Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow. Go to Service Definition and Enable "ReceivableInvoiceService" for "FSM_ION_SyncInvoice_Outbound.lpd" Processes
  3. Create ReceivableInvoice and Release it.
  4. BOD will trigger and Work unit will generate With respective newly added element.
  5. Create BillingInvoice Release it.
  6. Perform InvoiceVerificationReport.
  7. Perform InvoiceAndRegisterPrint.
  8. Perform SubSystemUpdate.
  9. BOD will trigger and Work unit will generate With respective newly added element.
  10. Verify the Result. In InvoiceHeader/CustomerParty/PartyIDs/EndPointID@schemeID="DE:VAT" added.

JR-3269773

Changes made for LCLTaxReport_Outbound-- Local.ly (Country=UK)

If VatReportingLine.Source = "O" then it should consider both AR and BL TaxTransactions.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncLCLTaxReport.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes: Added nodes Branch1960, Tax,GLC, Assign5470, Tax1, Assign8150, Assign2370, Branch540, Assign7640, Assign2830, Branch5700, Assign9650, Branch7060, Assign7040, GBtx1, Assign7720, Assign390, Branch2050
  • Integration Specific:Yes. Local.ly Integration for GB country (UK).

Use these steps to test the enhancement:

  1. Setup: Enable the service "TaxReportService" for FSM_ION_SyncLCLTaxReport _Out.lpd.
  2. Setup: In SystemConfiguration give the value of IntegrationApplication == "Local.ly".
  3. Create a Payablesinvoice with tax and PayablesInvoice of type Credit memo and release it. Do the payment for the Invoice by performing actions:
    1. Perform cash Requirements
    2. Electronic Payment Creations
    3. PaymentClose
  4. Run VAT Return Report batch Job. BOD will trigger and Work unit will generate successfully.
  5. Verify the Result: If VatReportingLine.Source = "O" then it should consider both AR and BL TaxTransactions for GB Country.

JR-3323108

Add Bank ID in the Vendor for SyncSupplierPartyMaster outbound BOD for local.ly country AU

Program/Business class/Process affected:

  • Files changed:
    • FSM_ION_SyncSupplierPartyMaster
    • SupplierPartyMaster_Out.xlsx

    • FSM_SupplierPartyMaster_Outbound_Template.xls

  • New Required Setup: No.
  • New Variable Added in JSON: Yes. PayablesJSON.txt
  • New IPA Changes:
    • In start node added a new variable VendorBankID.
    • In JSON Parser assigned value to the variable VendorBankID.
    • In Assign_1 added the below condition in the javascript:
      if(IntegrationApplication == "Local.ly" && VendorPostalAddressCountry == "AU" )
{ ChannelCodePhone = "MobilePhone"
ChannelCodeFax = "Fax"
VendorBankID = VendorBankID;
}
else
{
VendorBankID = "";
}
  • Integration Specific: Yes. Local.ly and the country of Austrailia (AU).

Use these steps to test the enhancement:

  1. Setup: In the Finance Enterprise Group, in Options, select the BOD Trigger check box.
  2. Setup: Enable the service VendorGroupService for FSM_ION_SyncSupplierPartyMaster.
  3. Create,Update or Delete a Vendor and save it.
  4. BOD will trigger and IONOutbox queue will generate without error.
  5. Verify the Result. When IntegrationApplication is "Local.ly" and the Country is Australia (AU), the mapped value Vendor.BankID in the Xpath /SyncSupplierPartyMaster/DataArea/SupplierPartyMaster/FinancialParty/FinancialAccount/UserArea/Property/NameValue[@name='lcl.BankCode']

JR-3306074