BOD Connectors

This section contains enhancements in Infor Financials and Supply Management.

Changes for Sync_CustomerPartyMaster_Outbound for Brazil (Local.ly Integration)

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncCustomerPartyMaster_Out.lpd
  • Variable Added in JSON: No.
  • IPA Changes: Changed made to FSM_ION_SyncCustomerPartyMaster_Out IPA flow.

    Assign5830:Modified javascript.for IntegrationApplication == "Local.ly" && AddressCountryCode == "BR" .

    TaxIDXML:

    <TaxID schemeAgencyName = "BR_IM">{CLocaleIDNumber}@NoNullTag@</TaxID>

    <TaxID schemeAgencyName = "BR_IE">{CStateProvinceIDNumber}@NoNullTag@</TaxID>

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

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    2. For Outbound BOD, Enable the service "CompanyCustomerService" for FSM_ION_SyncCustomerPartyMaster_Out.lpd.
  2. Create,Update and Delete a CompanyCustomer for Local.ly (Brazil.
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCustomerPartyMaster_Out BOD.
  4. Verify the Result:
    1. CustomerPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IM"-- CompanyCustomer.PostalAddress.LocaleIDNumber.
    2. CustomerPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IE"-- CompanyCustomer.PostalAddress.StateProvinceIDNumber.
Note: These changes are related to Local.ly Integration specific to Brazil (BR). Customer.PostalAddress.Country should be Brazil (BR)

Dependencies: None.

JT-1720524

Changes for Sync_ShipFromPatyMaster_Outbound for Brazil (Local.ly Integration)

Program/Business class/Process affected:

  • File Changed: FSM_ION_SyncShipFromPartyMaster_Out.Ipd
  • Variable Added in JSON: No.
  • IPA Changes: Changes to FSM_ION_SyncShipFromPartyMaster_Out.Ipd IPA flow.

    AssignVars:Modified javascript.for IntegrationApplication == "Local.ly" && Country == "BR".

    IE_TaxID = StateProvinceIDNumber;

    IM_TaxID = LocalIDNumber;

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

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    2. For Outbound BOD, Enable the Service Definition "VendorLocationService" and Process "FSM_ION_SyncShipFromPartyMaster_Out".
  2. Create, Update and Delete VendorLocation
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncShipFromPartyMaster_Out BOD.
  4. Verify the Result:
    1. ShipFromPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IE"-- VendorAddress.StateProvinceIDNumber
    2. ShipFromPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IM"-- VendorAddress.LocaleIDNumber
Note: 

These changes are related to Local.ly Integration specific to Brazil (BR). VendorAddress.Country should be Brazil (BR)

Dependencies: None.

JT-1720503

Changes required for SyncRemitToPartyMaster for Brazil (Local.ly Integration)

Program/Business class/Process affected:

  • Files Changed:
    • FSM_ION_SyncRemitToPartyMaster_Out.Ipd
    • SyncRemitToPartyMasterJSON.txt
  • Variable Added in JSON: Yes. Added VendorTaxNationalIDNumber and VendorTaxStateProvinceIDNumber in JSON.
  • IPA Changes: Changes in FSM_ION_SyncRemitToPartyMaster_Out IPA flow.
    • In Start node:Added VendorTaxCNPJNationalIDNumber and VendorTaxIEStateProvinceIDNumber.
    • In AssignVars:Added javascript.for IntegrationApplication == "Local.ly" && VAddressCountry == "BR".

      VendorTaxCNPJNationalIDNumber=VendorTaxNationalIDNumber;

      VendorTaxIEStateProvinceIDNumber= VendorTaxStateProvinceIDNumber;

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

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    2. For Outbound BOD, Enable the Service Definition "RemitToLocationService" and Process "FSM_ION_SyncRemitToPartyMaster_Out".
  2. Create/ Update VendorLocation of Location Type of RemitTo
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncRemitToPartyMaster_Out BOD.
  4. Verify the Result:
    1. RemitToPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_CNPJ"-- VendorAddress.NationalIDNumber
    2. RemitToPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IE"-- VendorAddress.StateProvinceIDNumber
Note: These changes are related to Local.ly Integration specific to Brazil (BR). VendorAddress.PostalAddress.Country should be Brazil (BR). VendorAddress Country Brazil (BR)

Dependencies: None.

JT-1722580

Changes required for Sync_BilltoPartyMaster_Outbound for Brazil (Local.ly Integration)

Program/Business class/Process affected:

  • File Changed: FSM_ION_SyncBillToPartyMaster_Out.Ipd
  • Variable Added in JSON: No.
  • IPA Changes: Changes inFSM_ION_SyncBillToPartyMaster_Out IPA flow :
    • AssignVars:Modified javascript.for IntegrationApplication == "Local.ly" && CustomerCountry == "BR" .

      IM_TaxID = LocalIDNumber;

      IE_TaxID = StateProvinceIDNumber;

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

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    2. For Outbound BOD, Enable the Service Definition "CustomerBillToService" and Process "FSM_ION_SyncBillToPartyMaster_Out".
  2. Create, Update and Delete CustomerBillTo
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncBillToPartyMaster_Out BOD.
  4. Verify the Result:
    1. CustomerPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IM"-- CustomerBillTo.PostalAddress.LocaleIDNumber
    2. CustomerPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IE"-- CustomerBillTo.PostalAddress.StateProvinceIDNumber
Note: 

These changes are related to Local.ly Integration specific to Brazil (BR). Customer.PostalAddress.Country should be Brazil (BR)

Dependencies: None.

JT-1720527

Changes required for Sync_SupplierMaster_Outbound for Brazil (Local.ly Integration)

Program/Business class/Process affected:

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

    Assign_1:Modified javascript.for IntegrationApplication == "Local.ly" && VendorPostalAddressCountry == "BR".

    TaxIDXML:

    <TaxID schemeAgencyName = "BR_IM">{VLocaleIDNumber}@NoNullTag@</TaxID>

    <TaxID schemeAgencyName = "BR_IE">{VStateProvinceIDNumber}@NoNullTag@</TaxID>

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

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    2. Enable the service "VendorGroupService" for FSM_ION_SyncSupplierPartyMaster_Out.lpd
  2. Create,Update or Delete a Vendor and save it.
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncSupplierPartyMaster_Out.lpd BOD.
  4. Verify the Result:
    1. SupplierPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IE"-- VendorAddress.StateProvinceIDNumber
    2. SupplierPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IM"-- VendorAddress.LocaleIDNumber
Note: These changes are related to Local.ly Integration specific to Brazil (BR).

Dependencies: None.

JT-1720491

ION Content and JSON Files Delivery

Latest IPA JSON files and FSM_ION_CONTENT* delivery.

  • JSONFILES_ST record updated 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.
    1. FSM_ION_CONTENTPACK_ST
    2. FSM_ION_CONTENT_PACK_IONCE_IMS_ST
    3. FSM_ION_CONTENT_PACK_IONCE_ST

Dependencies: None.

JT-1730492

Issue with Sync_CreditTransfer_Outbound (Local.ly integration)

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • Variable Added in JSON: No.
  • IPA Changes: Modified code in javascript Assign6780 node
  • Integration Specific: Yes. These changes are related to Local.ly Integration.

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    2. Enable the Service Definition and Processes.
  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_SyncPayableTracker_Out BOD.
  8. Verify the Result. Verify this X-Path: CreditTransferPayment/PaymentTransaction/CreditorParty/FinancialAccount/BBANID

Dependencies: None.

JT-1724198

New elements to be added in SupplierPartyMaster Outbound BOD for Australia (Local.ly integration)

Program/Business class/Process affected:

  • Files Changed:
    • FSM_ION_SyncSupplierPartyMaster_Out.lpd
    • SupplierPartyMaster_Out.xlsx
    • FSM_SupplierPartyMaster_Outbound_Template.xls

  • Variables Added in JSON: No.
  • IPA Changes: Changes in FSM_ION_SyncSupplierPartyMaster_Out.
    • In Assign_1 node modified javascript for Address XML- Added below line for Local.ly and Country AU:
      <CitySubDivisionName>{VendorDeliveryAddressLine4}@NoNullTag@</CitySubDivisionName>
    • In Assign_1 node modified javascript for getting BankAccountNumber when Vendor.BankAccountValidationType is Standard AccountNumber
      if(VBankAccountNumber != "" && IntegrationApplication == "Local.ly" && VendorPostalAddressCountry == "AU" && ((BankAccountValidationType == "Y") || (BankAccountValidationType == "Z") || (BankAccountValidationType == "") ))
      {
      VIBBankAccountNumber = VBankAccountNumber;
      }
  • Integration specific: Yes. These changes are related to Local.ly Integration for Australia (AU).

Use these steps to test the enhancement:

  1. Setup:
    1. Enable the service "VendorGroupService" for FSM_ION_SyncSupplierPartyMaster_Out.lpd.
  2. Create, Update or Delete a Vendor and save it.
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncSupplierPartyMaster_Out.lpd BOD.
  4. Verify the Result:
    1. Mapped VendorAddress.PostalAddress.DeliveryAddress.AddressLine4 in Xpath SupplierPartyMaster/Location/Address/CitySubDivisionName
    2. Passed Vendor.BankAccountNumber when Vendor.BankAccountValidationType is Standard Account Number in Xpath FinancialParty/FinancialAccount/IBANID

Dependencies: None.

JT-1723981

SyncInvoice BOD changes -lcl.AccountingDate for Argentina ( Local.ly Integration)

SyncInvoice BOD changes.

Program/Business class/Process affected:

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

    Assign1740:Modified javascript.if IntegrationApplication == "Local.ly" && AddressCode != "" && AddressCode_PostalAddress_Country =="AR"

    PROPERTIES_XML +=

    <Property><NameValue name="lcl.AccountingDate" type="StringType">{BLInvPostingDate}@NoNullTag@</NameValue></Property>;

  • Integration Specific: Yes. These changes are related to Local.ly Integration specific to Argentina (AR).
Use these steps to test the enhancement:
  1. Setup:
    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.
  2. Create BillingInvoice Release it.
  3. Perform InvoiceVerificationReport
  4. Perform InvoiceAndRegisterPrint
  5. Perform SubSystemUpdate
  6. BOD will trigger and Work unit will generate With respective newly added element.
  7. Verify the Result. In InvoiceHeader/UserArea/Property@Name@="lcl.AccountingDate" and value same as fsm.PostingDate.

Dependencies: None.

JT-1726646

SyncInvoice BOD changes to pass BillingInvoice.CertificationNumber in DisplayID for Chile (Local.ly integration)

SyncInvoice BOD changes

Program/Business class/Process affected:

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

      Assign4010:Modified javascript.if IntegrationApplication == "Local.ly" && AddressCode != "" && AddressCode_PostalAddress_Country =="CL"

      DisplayID = BL_CertificationNumber_AR;

  • Integration Specific: Yes. These changes are related to Local.ly Integration specific to Chile (CL).
Use these steps to test the enhancement:
  1. Setup:
    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.
  2. Create BillingInvoice Release it.
  3. Perform InvoiceVerificationReport.
  4. Perform InvoiceAndRegisterPrint.
  5. Perform SubSystemUpdate.
  6. BOD will trigger and Work unit will generate With respective newly added element.
  7. Verify the Resul in InvoiceHeader/DisplayID.

Dependencies: None.

JT-1726811

Inventory Adjustment BOD

Program/Business class/Process affected:

  • Files Changed:
    • FSM_ION_SyncInventoryAdj_Outbound.lpd
    • FSM_ION_SyncInventoryAdjustment_Inbound.lpd
  • New Required Setup: Added new System Configuration Parameter "SyncInventoryAdjustment_Reference”. Default value for the flag is "N". When the Value is set to "Y", to consume and publish IPS reference.
  • New Variable Added in JSON: InvLineRef
  • New IPA Changes:
    • Changes in FSM_ION_SyncInventoryAdj_Outbound.lpd:
      • In Start node added new variables InvLineRef,InvAdjRef,PROPERTIES_XML_Line.
      • Added conditions in node Assign4990,InvAdj_Line.
    • Changes in FSM_ION_SyncInventoryAdjustment_Inbound.lpd:
    • In Start node added new variables InvLineRef,InvAdjRef.
    • Added conditions in node LineVariables,InventoryTranLine
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. Setup:
    1. Enable the service "InventoryAdjustmentService" for FSM_ION_SyncInventoryAdj_Outbound.lpd.
    2. Set the value of System Configuration Parameter "SyncInventoryAdjustment_Reference” to "Y".
    3. In Channel Administrator enable the receiver of FSM_ION_SyncInventoryAdjustment_Inbound.lpd.
  2. When BOD gets processed an InventoryTransaction of Adjustment is Created.
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncInventoryAdjustment_Inbound.lpd and FSM_ION_SyncInventoryAdj_Outbound.lpd BOD.
  4. Verify the Result:
    • If SyncInventoryAdjustment_Reference=N then IPS reference is not mapped to InventoryTransactionLine.Reference.
    • If SyncInventoryAdjustment_Reference=N then IPS reference is mapped to InventoryTransactionLine.Reference and sent in InventoryTransactionLine/UserArea of FSM_ION_SyncInventoryAdj_Outbound.

Dependencies: None.

JT-1703084