BOD Connectors

This section contains enhancements in Infor Financials and Supply Management.

Add Scheme ID for Endpointid of customer in SyncInvoice Outbound BOD for Local.ly and Country Great Britain

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncInvoice_Outbound.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes: In FSM_ION_SyncInvoice_Outbound IPA flow these changes were made:
    • In Assign1740 : Javascript modified ,For IntegrationAppicationnLocal.ly GreatBritain(GB).AUschemeID = "GB:VAT";
  • .Integration Specific: Yes. These changes are related to Local.ly Integration GreatBritain(GB).

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.
  3. Go to Service Definition and Enable "ReceivableInvoiceService" for "FSM_ION_SyncInvoice_Outbound.lpd" Processes.
  4. Created ReceivableInvoiceBatch and Released.
  5. BOD Triggered and Work unit generated.
  6. Verify Xpath: InvoiceHeader/CustomerParty/PartyIDs/EndPointID@schemeID -->Mapped as "GB:VAT"

Dependencies: None.

JT-1688619

Changes for Bank Statement-- Local.ly

Fixed changes for ANZ format of FSM_ION_LoadBankStatement_Inbound.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_LoadBankStatement_Inbound
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • Added variables in Start node TransactionID,PartyReference,PartyRef.
    • Added conditions in Assign470.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. In ChannelAdministrator enable the receiver FSM_ION_LoadBankStatement_Inbound.
  2. After the BOD is processed BankStatement Created Successfully.
  3. Workunit will trigger without errors.
  4. Verify the Result: If the transaction type is "000" or "001" then Text Reference value is if BankStatementAccount/AccountEntry/EntryDetail/EntryTransaction/ExternalReferences/Reference/NameValue = Party Reference

Dependencies: None.

JT-1687685

Changes made in AccountingChart_In

Changes related to M3-FSM-GHR integration.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncAccountingChart_Inbound
  • New Required Setup: Configure GeneralLedger_BODS_FinanceEnterpriseGroup value in System Configuration.
  • New Variable Added in JSON: No.
  • New IPA Changes: Added conditions in Assign5650.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. In Channels Administrator, create a record for Sync.AccountingChart Inbound BOD.
  2. Configure GeneralLedger_BODS_FinanceEnterpriseGroup value in System Configuration.
  3. Send a valid xml for Sync AccountingChart BOD.
  4. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncAccountingChart_Inbound BOD.
  5. Verify the Result. View the record in ReportingChart.

Dependencies: None.

JT-1663473

Changes made in SyncCodeDefinition_Inbound

Changes related to M3-FSM-GHR integration.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncCodeDefinition_Inbound
  • New Required Setup:
    • Configure the parameters SyncCodeDefinition_Inbound_FinanceEnterpriseGroup, SyncCodeDefinition_Inbound_StructureName, IntegratingApplication in System Configuration.
  • New Variable Added in JSON: No.
  • New IPA Changes: Added conditions in BranchListID,Assign6560.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. In Channels Administrator create record for Sync.CodeDefinition Inbound BOD.
  2. Configure the parameters SyncCodeDefinition_Inbound_FinanceEnterpriseGroup, SyncCodeDefinition_Inbound_StructureName, IntegratingApplication in System Configuration.
  3. Send valid xml for Sync CodeDefinition BOD .
  4. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCodeDefinition_Inbound BOD.
  5. Verify the Result: Check the record in AccountingUnit.

Dependencies: None.

JT-1670667

Changes made in SycChartOfAccount_In for FSM-M3-GHR Payroll integration

Changes related to M3-FSM-GHR integration.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_ChartOfAccounts_Inbound.lpd
  • New Required Setup: Configure GeneralLedger_BODS_FinanceEnterpriseGroup value in System Configuration.
  • New Variable Added in JSON: No.
  • New IPA Changes: Added conditions in Assign7490.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. In Channels Administrator create record for Sync.ChartOfAccounts Inbound BOD.
  2. Configure GeneralLedger_BODS_FinanceEnterpriseGroup value in System Configuration.
  3. Send valid xml for Sync ChartOfAccounts BOD.
  4. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_ChartOfAccounts_Inbound BOD.
  5. Verify the Result: Check the record in GeneralLedgerChartAccount.

Dependencies: None.

JT-1651383

Changes made in SyncAccountingEntity_In for FSM-M3-GHR Payroll integration

Changes related to M3-FSM-GHR integration.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncAccountingEntity_Inbound.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • In FSM_ION_SyncAccountingEntity_Inbound IPA flow below changes made:
      • In Assign5650 : Added Javascript For AccountingEntity Split Logic - Based upon Generic_Delimiter.
      • In Assign5650 : Added Javascript ,if Currency is null or blank it will pick the value from AccountingEntity/BaseCurrency x-path.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. In Channel Administrator run the Sync.AccountingEntity Inbound BOD.
  3. Using these existing System Configuration Properties:
    • For FinanceEnterpriseGroup -->GeneralLedger_BODS_FinanceEnterpriseGroup.
    • For CloseConfiguration -->SyncAccountingEntity_In_CloseConfiguration.
    • For CurrentPeriod-->SyncAccountingEntity_In_CurrentPeriod.
  4. Parse the inbound xml for Sync.AccountingEntity Inbound.
  5. BOD will trigger ,Work unit will generate.
  6. Record will Create in AccountingEntity.
  7. Verify the results:
    • From concatenated value AccountingEntity value will pick correctly.
    • For Currency if AccountingEntity/CurrencyCode x-path blank or null it will pick from AccountingEntity/BaseCurrency x-path.

Dependencies: None.

JT-1651382

FSM-Local.ly: Changes required in SyncCreditTransfer_Out BOD for Australia

Local.ly changes required in SyncCreditTransfer_Out BOD for Australia

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • IPD change: Added related assignment variable in Assign5940,Assign6300

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Do required setup for CreditTransfer flow.
  3. Create PayablesInvoice and release.
  4. Run'Perform Cash Application' job.
  5. Check CashRequiremnetsResults records.
  6. Run ElectronicPaymentCreation job.
  7. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCreditTransfer_Out BOD.
  8. Verify the result. X-path: SyncCreditTransfer/DataArea/CreditTransfer/ CreditTransferPayment/PaymentTransaction/ CreditorParty/FinancialAccount/Name

Dependencies: None.

JT-1684845

FSM-Local.ly: New elements to be added in Credit Transfer BOD for Austraila

Local.ly changes required in SyncCreditTransfer_Out BOD for Australia

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • IPD change:

    Added related assignment variable in Assign1110

    .

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Do required setup for CreditTransfer flow.
  3. Create PayablesInvoice and release
  4. Run'Perform Cash Application' job.
  5. Check CashRequiremnetsResults records.
  6. Run ElectronicPaymentCreation job
  7. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCreditTransfer_Out BOD.
  8. Verify the Result. X-path:CreditTransferPayment/ PaymentTransaction/ CreditTransferAgreement/ CategoryPurposeCode

Dependencies: None.

JT-1689089

ION Content and JSON Files Delivery

Latest IPA JSON files and FSM_ION_CONTENT* delivery

  • JSONFILES_ST record updtaed in \iefin\wfdata\SampleDocumentTemplate.
  • FSM_ION_CONTENT* record updated in \iefin\plugins\iefinconnector\ipa_content.

Program/Business class/Process affected:

  • \iefin\wfdata\SampleDocumentTemplate.

  • \iefin\plugins\iefinconnector\ipa_content\SampleDocumentTemplate.

Use these steps to test the enhancement:

  1. Go to Application -->Application Administrator -->Supply Management -->Shared Processes -->Sample Document Template.
  2. Open Sample Document.
  3. In the All tab, search for JSONFILES_ST, the record updated with attachment.
  4. In Fact Sheets tab, search for FSM_ION_CONTENT*, three records updated with attachment.
    • FSM_ION_CONTENTPACK_ST
    • ,FSM_ION_CONTENT_PACK_IONCE_IMS_ST
    • FSM_ION_CONTENT_PACK_IONCE_ST.

Dependencies: None.

JT-1695570

LCL Tax report GB Code changes

Solved errors in workunit when report is run for periods with zero transaction.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncLCLTaxReport.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • In start node added new variable GLCurrency,MXCompany.
    • Updated conditions in nodes Assign4650,RptHdr,Assign8050.
    • Added node Branch7310.
  • Integration Specific: Yes. Local.ly Integration,for MX,GB countries.

Use these steps to test the enhancement:

  1. Enable the service "TaxReportService" for FSM_ION_SyncLCLTaxReport _Out.lpd.
  2. 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:Solved errors in workunit when report is run for periods with zero transaction.

Dependencies: None.

JT-1692594