BOD Connectors

This section contains enhancements in Infor Financials and Supply Management.

Changes for Sync_CreditTransfer_Outbound-- Local.ly

Local.ly changes required in SyncCreditTransfer_Out BOD for Australia, New Zealand, Mexico

Program/Business class/Process affected:

  • Files changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • IPD change: Added new nodes from 'CountryCheck' node to AU,NZ,MX countries.

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. Verify BOD triggered as per description.

Dependencies: None

JT-1706583

Changes for CreditTransfer_Outbound for Local.ly- Australia

Added/Changed in Sync.CreditTransfer_Outbound bod for Local.ly specific to Australia Country.

Program/Business class/Process affected:

  • Files Changed:
    • CashLedgerPayablesPayment.busclass
    • CreditTrasferJSON.txt
    • FSM_ION_SyncCreditTransfer_Out.lpd
  • Variable Added in JSON: Yes
    • Added 'CashManagementAccount' JSON Key
      • Added CashManagementAccount.SwiftID as "CashManagementAccSwiftID"
      • Added CashManagementAccount.BankClientIdentifier as "CABankClientIdentifier"
    • Added 'CashManagementAccount.FinancialInstitution' JSON Key
      • Added CashManagementAccount.FinancialInstitution.Description as "CAFinancialInstitutionDes"
    • Added PaidVendor.BankId as "VendorBankID"
  • IPA Changes: In FSM_ION_SyncCreditTransfer_Outbound IPA flow below changes have been made:
    • Added below variables in 'start' node
      • CashManagementAccSwiftID
      • CLBranchIdentifier
      • CLPPInstructionID
      • VendorBankID
      • DebtorPartIDName
      • DebtorName
      • FinancialInstitutionDes
    • Added below code in 'Assign6780' node
      if (IntegrationApplication == "Local.ly" && DebtorAddressCountry == "AU")
{
FinancialInstitutionDes=CAFinancialInstitutionDes;
DebtorName = CLPPayment_DerivedAccountingEntityName;
DebtorPartIDName=CABankClientIdentifier;
CLTranIdentifier = CashManagementAccSwiftID;
ClearingSystemMemberID = VendorBankID;
BankEntityBankNameValue = GetPInvoicePayment_DerivedVendorName;
ElectTransferID = CLPPInstructionID;
CleanSystemMemberID = CLBranchIdentifier;
ID_scheme="BankPartyIdentification";
}
else
{
FinancialInstitutionDes=BE_BankName;
DebtorName=PayablesCompanyName;
DebtorPartIDName=trimLeadingZeros(CashLedgerPayablesPayment["Company"]);
}
  • Modified XML's mappings.
  • Integration Specific: Yes. These changes are related to Local.ly Integration for Australia Country.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Enable the Service Definition and Processes.
  3. Do required setup for CreditTransfer flow.
  4. Create PayablesInvoice and release.
  5. Run 'Perform Cash Application' job.
  6. Check CashRequiremnetsResults records.
  7. Run ElectronicPaymentCreation job.
  8. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCreditTransfer_Out BOD.
  9. Verify the result. Verify the x-Path'setup.
    • CreditTransfer/CreditTransferPayment/FirstAgentParty/Name
    • CreditTransfer/CreditTransferPayment/DebtorParty/Name
    • CreditTransfer/CreditTransferPayment/DebtorParty/PartyIDs/ID
    • CreditTransfer/CreditTransferPayment/Description
    • CreditTransferPayment/PaymentTransaction/FinalAgentFinancialParty/ClearingSystemMemberID
    • CreditTransferPayment/PaymentTransaction/CreditorParty/FinancialAccount/Name
    • CreditTransferPayment/PaymentTransaction/InstructionID
    • CreditTransferPayment/FistrAgentParty/ClearingSystemMemberID

Dependencies: None

JT-1688896

Changes for Sync_CreditTransfer_Outbound-- Local.ly

Local.ly changes required in SyncCreditTransfer_Out BOD for Australia, New Zealand, Mexico

Program/Business class/Process affected:

  • Files Changed:
    • ElectronicPaymentCreation_ElectronicPaymentCreation.java
    • CashLedgerPayablesPayment.busclass

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 results. Verify BOD in which single credit transfer payment node and in that we need to send the Payment Transaction nodes.

Dependencies: None

JT-1688405

Changes in SyncAccountingEntity_In for FSM-M3-GHR Payroll integration

Changes for FSM-M3-GHR Payroll integration.

Program/Business class/Process affected:

  • Files Changed:
    • FSM_ION_SyncAccountingEntity_Inbound.lpd
    • PfiConfigurationProperty.xml
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • In start node added a variable IgnoreGenericDelimeter.
    • Added conditions in node Assign5650.
  • Integration Specific: Yes. FSM-M3-GHR PayrollIntegration.

Use these steps to test the enhancement:

  1. In Channels Administrator create record for Sync.AccountingEntity inbound BOD.
  2. Configure SyncAccountingEntity_In_IgnoreGenericDelimeterConcatination value in System Configuration.
  3. Send valid xml for Sync AccountingEntity BOD
  4. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncAccountingEntity_Inbound BOD.
  5. Verify the Result:
    • Check the record in AccountingEntity.
      • when SyncAccountingEntity_In_IgnoreGenericDelimeterConcatination = N then AE is splitted from the XPath AccountingEntity/IDs/ID using GenericDelimeter.
      • when SyncAccountingEntity_In_IgnoreGenericDelimeterConcatination = Y then AE is picked from the XPath AccountingEntity/IDs/ID.

Dependencies: None

JT-1692352

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.New Required Setup: Configure SyncAccountingEntity_In_IgnoreGenericDelimeterConcatination value in System Configuration.
  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-1705400

Load Bank Statement Development for .NAI format-- Australia

Added new flow in LoadBankStatement_In for .NAI format -- Australia.

Program/Business class/Process affected:

  • Files Changed: FSM_ION_LoadBankStatement_Inbound
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • New Required Setup: ConfigureAdded variables in Start node BKStatementCounter,BKStatementCount,TransactionTypeCount,NaiClosingBal.
    • Added conditions in Assign7070,BankAccount,Assign690,Assign470.
    • Added nodes Branch6440,Branch6720,Assign5210
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. In ChannelAdministrator enable the receiver FSM_ION_LoadBankStatement_Inbound.
  2. In ConfigutationParameter set value for LoadBankStatement_In_CashManagementGroup.
  3. Once the BOD gets processed BankStatement Created Successfully, Workunit will trigger without errors.
  4. Verify the Result. BankStatement and BankStatementLine should be successfully created for .NAI format.

Dependencies: None

JT-1695679

Need Date - EAM MaintenanceOrder (WO) Inbound

FSM_ION_SyncMaintenanceOrder_Inbound: Need Date adjustment (PurchaseOrderLine.EarlyDeliveryDate updated and WHDemandLine.EstimatedTransactionDate).

Program/Business class/Process affected:

  • Files changed:
    • FSM_ION_SyncMaintenanceOrder_Inbound
    • PfiConfigurationProperty.xml
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • In Start node added these variables:
      • Added new System Configuration Parameter "UpdateShipDateTimeFromWO" and assigned it to "UpdateShipDateTimeFromWO" variable RequisitionID,ReqLineID,ReqCompany, RequisitionArrayLen,RequisitionArray,RequisitionArrayID,WDLine_Item, UpdateEAMScheduledStartDate, POArrayLen,POArray,ListID,POArrayID,DemandDocumentType,p,r,i,q,t,j.
      • Added JavaScript code in "Assign3280" for reading documentreference values based on type "PurchaseOrder" and "Requisition" from MaintenanceOrderLine/DocumentReference = "PurchaseOrder"/DocumentID/ID and MaintenanceOrderLine/DocumentReference/LineNumber.
      • Passed EAMWorkOrderActivity.EAMScheduledStartDate in PurchaseOrderLine.EarlyDeliveryDate
      • Added following flow to update WHDemandLine.EstimatedTransactionDate: Branch7060,Assign2660,ReqLine,LMTxnWDLine,Assign3800,UpdateWDLine, Assign6650,Assign8340,Assign4850,Assign2640
  • Integration Specific: Yes. These changes are related to CSF-EAM Integration.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. In Channels Administrator, Activate the respective ION Inbox Receivers for FSM_ION_SyncMaintenanceOrder_Inbound.
    • Set value "Y" in System Configuration Parameter "UpdateRequestedDeliveryDateTimeFromWO"
    • Set value "Y" in System Configuration Parameter "UpdateShipDateTimeFromWO"
  3. When the bod is processed, Work Unit will be triggered.
  4. EAMWorkOrder will be Updated.
  5. Verify the result.
    1. PurchaseOrderLineScenario
      • When MaintenanceOrder_In receives new ScheduledStartDate value in Update scenario from XPath: MaintenanceOrder/MaintenanceOrderLine/ScheduledDateTime and
      • if UpdateRequestedDeliveryDateTimeFromWO = "Y" and ScheduledStartDate value is not same as existing ScheduledStartDate value and
      • if MaintenanceOrderLine/DocumentReference type= "PurchaseOrder", PO value is retrieved from MaintenanceOrderLine/DocumentReference/DocumentID/ID and PurchaseOrderLine from Xpath :MaintenanceOrderLine/DocumentReference/LineNumber and for that POLine PurchaseOrderLine.EarlyDeliveryDate field is updated.
    2. WarehouseDemandLineScenario:
      • When MaintenanceOrder_In receives new ScheduledStartDate value in Update scenario from XPath: MaintenanceOrder/MaintenanceOrderLine/ScheduledDateTime and

      • if UpdateShipDateTimeFromWO = "Y" and ScheduledStartDate value is not same as existing ScheduledStartDate value and AllocatedQuantity<Quantity or AllocatedQuantity = 0

      • if MaintenanceOrderLine/DocumentReference type= "Requisition", Requisition value is retrieved from MaintenanceOrderLine/DocumentReference/DocumentID/ID and RequisitionLine from Xpath :MaintenanceOrderLine/DocumentReference/LineNumber and for that ReqLine the WarehouseDemandLine is fetched and WarehouseDemandLine.EstimatedTransactionDate field is updated

Dependencies: None

JT-1694729