BOD Connectors

This section contains enhancements in Infor Financials and Supply Management for 11.0.82.0.

Add new element for SyncCustomerReturn_Out

Add new element for SyncCustomerReturn_Out

Program/business class/process affected:
  • Files Changed: FSM_ION_SyncCustomerReturn_Out.lpd
  • New IPA Changes:
    • XML changes: Passed CustomerOrderReturn.OrderNumber value in following path: DataArea/CustomerReturn/CustomerReturnLine/DocumentReference type="SalesOrder"/DocumentID/ID
  • Integration Specific: Yes. These changes are related to CSF-GRC Integration.
Use these steps to test the enhancement:
  1. Setup: In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
  2. Setup: Enable the "CustomerReturnService" in Service Definition for FSM_ION_SyncCustomerReturn_Out Processes.
  3. Testing - Scenario 1:
    1. Create CustomerOrderReturn for the BillingInvoice.
    2. Create CustomerOrderReturnLine and release it.
  4. Testing - Scenario 2:
    1. Run "OrderEntryReturnsGlobalLedgerPosting" (When "OrderEntryReturnsGlobalLedgerPosting" is run , if CustomerOrderReturn status is "Released" then it will move to "Closed" and work unit will be triggered.)
    2. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCustomerReturn_Out BOD (CustomerReturnService).
  5. Check the following Xpath: CustomerReturn/CustomerReturnLine/DocumentReference type="SalesOrder"/DocumentID/ID

JT-1602701

Add the below elements to SyncItemMaster_Out

Adding Elements to SyncItemMaster_Out

Program/business class/process affected:
  • Files Changed: FSM_ION_SyncItemMaster_Out.lpd
  • New Variable Added in JSON: ItemDecQuantity, ItemDecPrice, ItemDecCost, ItemEffectiveDate, ItemExpirationDate.
  • New IPA Changes:
    • Added the below elements to SyncItemMaster_Out
      • ItemMaster/ItemMasterHeader/ItemStatus/TimePeriod/StartDateTime

        Item.EffectiveDate

      • ItemMaster/ItemMasterHeader/ItemStatus/TimePeriod/EndDateTime

        Item.ExpirationDate

    • Added below Xpaths in user areas
      • <NameValue type="StringType" name="Quantity in Decimals"/>

        Item.NumberOfDecimalsQuantity

      • <NameValue type="StringType" name="Price in Decimals"/>

        Item.NumberOfDecimalsPrice

      • <NameValue type="StringType" name="Cost in Decimals"/>

        Item.NumberOfDecimalsCost

Use these steps to test the enhancement:
  1. Setup: Enable the service "ItemService" for FSM_ION_SyncItemMaster_Out.lpd.
  2. Create,Update or Delete a Item and save it.
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncItemMaster_Out.lpd
  4. Verify the Result:
    1. Check the mappings of following XPath.
      • ItemMaster/ItemMasterHeader/ItemStatus/TimePeriod/StartDateTime --->Item.EffectiveDate
      • ItemMaster/ItemMasterHeader/ItemStatus/TimePeriod/EndDateTime ----->Item.ExpirationDate
    2. Check the X-paths in user areas.
      • <NameValue type="StringType" name="Quantity in Decimals"/>

        Item.NumberOfDecimalsQuantity

      • <NameValue type="StringType" name="Price in Decimals"/>

        Item.NumberOfDecimalsPrice

      • <NameValue type="StringType" name="Cost in Decimals"/>

        Item.NumberOfDecimalsCost

JT-1600095

GL: Add RunGroup to the SSJE Acknowledgement Bod

GL: Add RunGroup to the SSJE Acknowledgement Bod

Program/business class/process affected:
  • File changed: FSM_ION_ ProcessSourceSystemJournalEntry_Inbound
  • Changes in IPA:
    • Made changes in XML's of AcceptedBOD XML and RejectBOD XML.
    • Added UserArea->Property-> @RunGroup in both XMls
Use these steps to test the enhancement:
  1. Enable the service in Service Definitions.
  2. Change the Configuration Parameters.
  3. Publish the BOD through Generator Tool.
  4. Verify the Results in Canvas Work Units

JT-1589534

GLSSJE: Send the invoice number at the user area without any special characters SSJE Outbound Bod

GLSSJE: Send the invoice number at the user area without any special characters SSJE Outbound Bod

Program/business class/process affected:
  • File changed: FSM_ION_SyncSourceSystemJournalEntry_Out
  • Changes in IPA:
    • Added a code snippet<BLInvoice = BLInvoice.replace(/[\W_]/g, '');> in Java script of Assign2700 Node.
Use these steps to test the enhancement:
  1. Setup: Navigate to BillingCompany> and invoicing options. Enable the manual invoice numbering.
  2. Create and release a Billing Invoice.
  3. Run Invoice Verification Report.
  4. Run Invoice and Register Print.
  5. Run Sub System Update.
  6. Journals will be created in released state and Quick Post them.
  7. BOD will be triggered. Identify the Invoice number in UserArea that does not have any special characters.

JT-1598081

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

JT-1605778

Implement Clean Document ID solution for ProcessBillToPartyMaster_In - New BOD Development

Implemented Clean Document for Process.BillToPartyMaster_In - New BOD

Program/business class/process affected:
  • Files Changed:
    • FSM_ION_ProcessBillToPartyMaster_Inbound.ipd
    • PfiReceiver.xml
  • New Required Setup:
    • Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.
    • Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG.
  • New Variable Added in JSON: No new variables added
  • New IPA Changes:
    • BOD gets triggered based on the action code in Input XML and creates,updates or deletes records in CustomerBillTo
  • Integration Specific: No
Use these steps to test the enhancement:
  1. Setup:
    1. Enable the receiver for FSM_ION_ProcessBillToPartyMaster_Inbound.ipd.
    2. Pass the source AccountingEntity and destination GLCompany values in Cross Reference :DESTAEVSCSFGLC/
  2. Once the BOD gets processed CustomerBillTo gets Created or Updated or Deleted based on ActionCode.
  3. Verify that CustomerBillTo gets Created or Updated or Deleted based on ActionCode based for the RequiredCleanDocumentID = Y/N.

JT-1591783

Implement Clean Document ID solution for ProcessContactMaster_In

Implemented Clean Document ID solution for ProcessContactMaster_In

Program/business class/process affected:
  • Files Changed: FSM_ION_ProcessContactMaster_Inbound.lpd
  • New Required Setup:
    • Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.
    • Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • In Start node added new variables ConfigDocID,ConfigFEG.
    • Added Conditions in nodes Assign90.
  • Integration Specific: No.
Use these steps to test the enhancement:
  1. Setup:
    1. Enable the receiver for FSM_ION_ProcessContactMaster_Inbound.lpd.
    2. Pass the source AccountingEntity and destination GLCompany values in Cross Reference :DESTAEVSCSFGLC.
  2. Once the BOD gets processed CompanyCustomerContact gets Created or Updated or Deleted based on ActionCode.
  3. Verify that CompanyCustomerContact gets Created or Updated or Deleted based on ActionCode based for the RequiredCleanDocumentID = Y/N.

JT-1591786

Implement Clean Document ID solution for ProcessCustomerPartyMaster_In

Clean DOC ID Solution for ProcessCustomerPartyMaster_Inbound.

Note: This parameter is Only applicable for Beta customer and not existing customer using FSM-MSCRM Integration.

Program/business class/process affected:
  • Files Changed: FSM_ION_ProcessCustomerPartyMaster_Inbound
  • New Required Setup:
    • Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.
    • Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". When the Value is set to "Y", to enable IsMultipleFEG.
  • New IPA Changes:
    • In FSM_ION_ProcessCustomerPartyMaster_Inbound IPA flow below changes done:
      • New variables added in start node.
      • Modified javascript in "Assign3330" node.
  • Integration Specific: Yes. These changes are related to FSM-MSCRM Integration.
Use these steps to test the enhancement:
  1. Setup:
    • In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
    • In Channels Administrator, Activate the respective ION Inbox Receivers for FSM_ION_ProcessCustomerPartyMaster_Inbound.
    • Pass the source AccountingEntity and destination GLCompany values in Cross Reference :DESTAEVSCSFGLC
  2. When the bod is processed, Work Unit will be triggered.
  3. If RequiredCleanDocumentID = Y, Company value will be taken from cross reference and Customer is created.
  4. Verify the result:
    • If RequiredCleanDocumentID = Y, Company value will be taken from cross reference and Customer is created without any error.

JT-1588232

Implement Clean Document ID solution for ProcessShipToPartyMaster_In

Implemented Clean Document ID solution for ProcessShipToPartyMaster_In

Program/business class/process affected:
  • Files Changed: FSM_ION_ProcessShipToPartyMaster_Inbound.lpd
  • New Required Setup:
    • Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.
    • Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG.
  • New Variable Added in JSON: No
  • New IPA Changes:
    • In Start node added new variables ConfigDocID,ConfigFEG.
    • Added Conditions in nodes Assign1900,Assign1890,Assign3660,Assign1340.
  • Integration Specific: No.
Use these steps to test the enhancement:
  1. Enable the receiver for FSM_ION_ProcessShipToPartyMaster_Inbound.lpd.
  2. Pass the source AccountingEntity and destination GLCompany values in Cross Reference :DESTAEVSCSFGLC.
  3. Once the BOD gets processed CustomerShipTo gets Created or Updated or Deleted based on ActionCode.
  4. CustomerShipTo gets Created or Updated or Deleted based on ActionCode based for the RequiredCleanDocumentID = Y/N.

JT-1591784

Implement Clean Document ID solution for SynCustomerPartyMaster_Out

Implemented Clean Document ID solution for SynCustomerPartyMaster_Out

Program/business class/process affected:
  • Files Changed: FSM_ION_SynCustomerPartyMaster_Outbound.lpd
  • New Required Setup:
    • Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.
    • Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • In Start node added new variables ConfigDocID,ConfigFEG,CrossGLC.
    • Added new nodes Branch3670,Assign4660
  • Integration Specific: No.
Use these steps to test the enhancement:
  1. Enable the service "CompanyCustomerService" for FSM_ION_SynCustomerPartyMaster_Outbound.lpd.
  2. Pass the source GLCCompany and destination AccountingEntity values in Cross Reference :CSFGLCVSDESTAE.
  3. Create,Update or Delete a CompanyCustomer.
  4. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SynCustomerPartyMaster_Outbound.lpd BOD.
  5. Verify that:
    • If RequiredCleanDocumentID=N then DocID and Accountingentity in concatenation form.
    • If RequiredCleanDocumentID=Y then DocID is Customer and Accountingentity is CrossReference destination value.

JT-1588231

Implement Clean Document ID solution for SyncBillToPartyMaster_Out

Implemented Clean Document ID solution for SyncBillToPartyMaster_Out.

Program/business class/process affected:
  • Files Changed: FSM_ION_SyncBillToPartyMaster_Out.lpd
  • New Required Setup:
    • Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.
    • Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG.
    • Added new System Configuration Parameter "TriggerBODBasedOnCrossReference”. Default value for the flag is "N". The Value is set to "Y", to enable TriggerBODBasedOnCrossReference.
  • New Variable Added in JSON: No
  • New IPA Changes:
    • In Start node added new variables ConfigDocID,ConfigFEG,CrossGLC,GLCCompany.
    • Added new nodes Branch1150,Assign6550,GLC,Branch2860,XML4010,IONOutbox7270,Branch1060,Assign6650.
  • Integration Specific: No.
Use these steps to test the enhancement:
  1. Setup: Enable the service "CustomerBillToService","BillToInventoryService" for FSM_ION_SyncBillToPartyMaster_Out.lpd.
  2. Setup: Pass the source GLCCompany and destination AccountingEntity values in Cross Reference :CSFGLCVSDESTAE.
  3. Create,Update or Delete a CustomerBillTo.
  4. Create,Update or Delete an InventoryLocation.
  5. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncBillToPartyMaster_Out.lpd BOD.
  6. Verify the Result:
    • If RequiredCleanDocumentID=N then DocID and Accountingentity in concatenation form.
    • If RequiredCleanDocumentID=Y then DocID is customer + Delimiter + billto and Accountingentity is CrossReference destination value for CustomerBillToService.
    • If RequiredCleanDocumentID=Y then DocID is InventoryLocation and Accountingentity is CrossReference destination value for BillToInventoryService.

JT-1589564

Implement Clean Document ID solution for SyncCodeDefinition_Out

Implemented Clean Document ID solution for SyncCodeDefinition_Out(UOM,Territory)

Program/business class/process affected:
  • Files Changed: FSM_ION_SyncCodeDefinition_Outbound.lpd
  • New Required Setup:
    • Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.
    • Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG.
    • Added new System Configuration Parameter "TriggerBODBasedOnCrossReference”. Default value for the flag is "N". The Value is set to "Y", to enable TriggerBODBasedOnCrossReference.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • In Start node added new variables CrossGLC.
    • Added Conditions in node TerritoryVar.
    • Added new nodes Branch8150,Assign8700,Branch1770,XML9420,IONOutbox8730,GLC.
  • Integration Specific: No.
Use these steps to test the enhancement:
  1. Setup: Enable the service "UnitOfMeasureService","TerritoryService"Service for FSM_ION_SyncCodeDefinition_Outbound.lpd
  2. Setup: Pass the source CSFCompany and destination AccountingEntity values in Cross Reference :CSFGLCVSDESTAE.
  3. Create,Update or Delete an UOM.
  4. Create,Update or Delete a Territory.
  5. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCodeDefinition_Outbound.lpd BOD.
  6. Verify the Result:
    • If RequiredCleanDocumentID=N then DocID and Accountingentity in concatenation form.
    • If RequiredCleanDocumentID=Y then DocID is UOM and Territory ,Accountingentity is CrossReference destination value.

JT-1595863

Implement Clean Document ID solution for SyncSalesOrder_Out

Implemented Clean Document changes for Sync.SalesOrder_Out

Program/business class/process affected:
  • Files Changed: FSM_ION_SyncSalesOrder_Out.ipd
  • New Required Setup: No new setup is required.
  • New Variable Added in JSON: No new variable is added.
  • New IPA Changes:
    • Added ConfigDocID, IsMultipleFEG and CrossGLC in Start node.
    • Added branch condition if ConfigDocID = "Y" navigate to Assign 3240 node else navigate to XML_COR.
    • Added new Assign node for clean document changes.
    • Added new Assign node Assign3350 to define ItemID for clean document.
  • Integration Specific: No
Use these steps to test the enhancement:
  1. Setup:
    1. In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
    2. For Outbound BOD, Enable the Service Definition "CustomerOrderService" and Process "FSM_ION_SyncSalesOrder_Out".
    3. Pass the source GLCCompany and destination AccountingEntity values in Cross Reference :CSFGLCVSDESTAE
  2. Create CustomerOrder and CustomerOrderLine.
  3. Release CustomerOrder.
  4. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncShipment_Out BOD.
  5. Verify the Result:
    • If RequiredCleanDocumentID=N then DocID and Accountingentity in concatenation form.
    • If RequiredCleanDocumentID=Y then DocID and Accountingentity is CrossReference destination value for CustomerOrderService.

JT-1595449

Implement Clean Document ID solution for SyncShipToPartyMaster_Out

Implemented Clean Document ID solution for SyncShipToPartyMaster_Out

Program/business class/process affected:
  • Files Changed: FSM_ION_SyncShipToPartyMaster_Outbound.lpd
  • New Required Setup:
    • Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.
    • Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • In Start node added new variables ConfigDocID,ConfigFEG,CrossGLC.
    • Added new nodes Branch7000,Assign9880.
  • Integration Specific:No
Use these steps to test the enhancement:
  1. Setup:
    • Enable the service "CustomerShipToService" for FSM_ION_SyncShipToPartyMaster_Outbound.lpd.
    • Pass the source GLCCompany and destination AccountingEntity values in Cross Reference :CSFGLCVSDESTAE.
  2. Create,Update or Delete a CustomerShipTo.
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncShipToPartyMaster_Outbound.lpd BOD.
  4. Verify the Result:
    • If RequiredCleanDocumentID=N then DocID and Accountingentity in concatenation form.
    • If RequiredCleanDocumentID=Y then DocID is Customer@@CustomerShipTo and Accountingentity is CrossReference destination value.

JT-1589550

New element to be added to ItemMaster Outbound BOD

Added XPath for ItemMaster Outbound BOD SyncItemMaster/DataArea/ItemMaster/ItemMasterHeader/Classification/Codes/Code[@listID="lcl.CommodityCode"]---CommodityCode from Item.CommodityCode

Program/business class/process affected:
  • Files Changed: FSM_ION_SyncItemMaster_Out.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • Added Item.CommodityCode for the following Xpath SyncItemMaster/DataArea/ItemMaster/ItemMasterHeader/Classification/Codes/Code[@listID="lcl.CommodityCode"]
Use these steps to test the enhancement:
  1. Setup: Enable the service "ItemService" for FSM_ION_SyncItemMaster_Out.lpd.
  2. Create,Update or Delete a Item and save it.
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncItemMaster_Out.lpd.
  4. Verify the Result:
    • Check the mappings of following XPath: SyncItemMaster/DataArea/ItemMaster/ItemMasterHeader/Classification/Codes/Code[@listID="lcl.CommodityCode"]--->Item.CommodityCode

JT-1589579

New element to be added to Shipment Outbound BOD

Added new X-Paths for Sync.Shipment_Out BOD to Local.ly intergration

Program/business class/process affected:
  • Files Changed: FSM_ION_SyncShipment_Out.ipd
  • New Required Setup: No new setup is required
  • New Variable Added in JSON: No new variable is added
  • New IPA Changes:
    • Added new node Item to get CommoditiyCode within WHL node.
    • Added Assign7770 node for defining the CommoditiyCode.
  • Integration Specific: These changes are related to Local.ly integration.
Use these steps to test the enhancement:
  1. Setup:
    1. In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
    2. For Outbound BOD, Enable the Service Definition "ShipmentService" and Process "FSM_ION_SyncShipment_Out".
    3. Assign value "Local.ly" to "IntegratingApplication" parameter in System Configurations.
  2. Create CustomerOrder and CustomerOrderLine.
  3. Release CustomerOrder.
  4. Run WarehousePickListPrint batch job
  5. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncShipment_Out BOD.
  6. Verify the below X-Path values :
    • SyncShipment/DataArea/Shipment/ShipmentItem/Classification/Codes/Code [@listID="lcl.CommodityCode"] -- Item.CommoditiyCode

JT-1589992

Prefix change needed for PaymentOutputFileHeader attribute in Sync.CreditTransfer_Out BOD

Prefix change needed for PaymentOutputFileHeader attribute in Sync.CreditTransfer_Out BOD

Program/business class/process affected:
  • File Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • IPA Change :
    • Modified XML prefix in Assign1110 for below path
      • Old prefix: SyncCreditTransfer/DataArea/CreditTransfer/CreditTransferHeader/UserArea/Property/NameValue[@name="fsm.PaymentOutputFileHeader"]
      • New Prefix: SyncCreditTransfer/DataArea/CreditTransfer/CreditTransferHeader/UserArea/Property/NameValue[@name="lcl.PaymentOutputFileHeader"]
  • Integration Specific: Yes. These changes are related to Local.ly Integration for Argentina(AR) Country.
Use these steps to test the enhancement:
  1. In FinanceEnterpriseGroup, "BODtrigger" checkbox 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 this X-Path: SyncCreditTransfer/DataArea/CreditTransfer/CreditTransferHeader/UserArea/Property/NameValue[@name="lcl.PaymentOutputFileHeader"]

JT-1598293

LoadBankStatement - Enhancements for TextReference

Done ANZCSV - BankStatement LoadBankStatement - Enhancements for TextReference

Program/business class/process affected:
  • Files changed: FSM_ION_LoadBankStatement_Inbound.lpd
  • New IPA Changes:
    • Added new variables in start node TextRef,BankLineDesc,BankRef,RelatedRef.
    • Added conditions in node Assign470.
Use these steps to test the enhancement:
  1. Setup:
    • Enable the receiver for FSM_ION_LoadBankStatement_Inbound.lpd.
    • Pass the CashManagementGroup in system configuration parameter "LoadBankStatement_In_CashManagementGroup"
  2. When the BOD gets processed, BankStatement and BankStatementLines get created.
  3. Verify the result:
    • Concatenation of the Particulars, Analysis Code and Reference data from the Bank Statement BOD xpath BankStatement/BankStatementAccount/AccountEntry/EntryDetail/EntryTransaction/ExternalReferences into the FSM field BankStatementLine.TextReference

JT-1596907

Prefix change needed for PaymentOutputFileHeader attribute in Sync.CreditTransfer_Out BOD

Prefix change needed for PaymentOutputFileHeader attribute in Sync.CreditTransfer_Out BOD.

Program/Business class/Process affected:

  • File Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • New Required Setup : No
  • New Variable Added in JSON: No
  • IPA Change : Modified XML prefix in Assign1110 for below path
  • IPA Change : Modified XML prefix in Assign1110 for below path

    Old prefix::

    SyncCreditTransfer/DataArea/CreditTransfer/CreditTransferHeader/UserArea/Property/NameValue[@name="fsm.PaymentOutputFileHeader"]

  • New Prefix::

    SyncCreditTransfer/DataArea/CreditTransfer/CreditTransferHeader/UserArea/Property/NameValue[@name="lcl.PaymentOutputFileHeader"]

  • Integration Specific: Yes

    These changes are related to Local.ly Integration for Argentina(AR) Country.

Use these steps to test the enhancement:

  1. Setup:
    • In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    • Enable the Service Definition and Processes.
  2. How to Test:
    • Do required setup for CreditTransfer flow.
    • Create PayablesInvoice and release
    • Run'Perform Cash Application' job.
    • Check CashRequiremnetsResults records.
    • Run ElectronicPaymentCreation job
    • BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCreditTransfer_Out BOD.
  3. Verify the Result: Verify below X-Path:
    • SyncCreditTransfer/DataArea/CreditTransfer/CreditTransferHeader/UserArea/Property/NameValue[@name="lcl.PaymentOutputFileHeader"]

JT-1598293