BOD Connectors
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:
- Setup:
- In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
- For Outbound BOD, Enable the service "CompanyCustomerService" for FSM_ION_SyncCustomerPartyMaster_Out.lpd.
- Create,Update and Delete a CompanyCustomer for Local.ly (Brazil.
- BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCustomerPartyMaster_Out BOD.
- Verify the Result:
- CustomerPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IM"-- CompanyCustomer.PostalAddress.LocaleIDNumber.
- CustomerPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IE"-- CompanyCustomer.PostalAddress.StateProvinceIDNumber.
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:
- Setup:
- In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
- For Outbound BOD, Enable the Service Definition "VendorLocationService" and Process "FSM_ION_SyncShipFromPartyMaster_Out".
- Create, Update and Delete VendorLocation
- BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncShipFromPartyMaster_Out BOD.
- Verify the Result:
- ShipFromPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IE"-- VendorAddress.StateProvinceIDNumber
- ShipFromPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IM"-- VendorAddress.LocaleIDNumber
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:
- Setup:
- In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
- For Outbound BOD, Enable the Service Definition "RemitToLocationService" and Process "FSM_ION_SyncRemitToPartyMaster_Out".
- Create/ Update VendorLocation of Location Type of RemitTo
- BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncRemitToPartyMaster_Out BOD.
- Verify the Result:
- RemitToPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_CNPJ"-- VendorAddress.NationalIDNumber
- RemitToPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IE"-- VendorAddress.StateProvinceIDNumber
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;
- AssignVars:Modified javascript.for IntegrationApplication == "Local.ly" &&
CustomerCountry == "BR" .
- Integration Specific: Yes. These changes are related to Local.ly Integration specific to Brazil (BR).
Use these steps to test the enhancement:
- Setup:
- In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
- For Outbound BOD, Enable the Service Definition "CustomerBillToService" and Process "FSM_ION_SyncBillToPartyMaster_Out".
- Create, Update and Delete CustomerBillTo
- BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncBillToPartyMaster_Out BOD.
- Verify the Result:
- CustomerPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IM"-- CustomerBillTo.PostalAddress.LocaleIDNumber
- CustomerPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IE"-- CustomerBillTo.PostalAddress.StateProvinceIDNumber
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:
- Setup:
- In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
- Enable the service "VendorGroupService" for FSM_ION_SyncSupplierPartyMaster_Out.lpd
- Create,Update or Delete a Vendor and save it.
- BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncSupplierPartyMaster_Out.lpd BOD.
- Verify the Result:
- SupplierPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IE"-- VendorAddress.StateProvinceIDNumber
- SupplierPartyMaster/PartyIDs/TaxID @schemeAgencyName="BR_IM"-- VendorAddress.LocaleIDNumber
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:
- Go to Application -->Application Administrator -->Supply Management -->Shared Processes -->Sample Document Template.
- Open Sample Document.
- In the All tab, search for JSONFILES_ST, the record updated with attachment.
- 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-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:
- Setup:
- In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
- Enable the Service Definition and Processes.
- 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_SyncPayableTracker_Out BOD.
- 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; }
- In Assign_1 node modified javascript for Address XML- Added below line for Local.ly
and Country
AU:
- Integration specific: Yes. These changes are related to Local.ly Integration for Australia (AU).
Use these steps to test the enhancement:
- Setup:
- Enable the service "VendorGroupService" for FSM_ION_SyncSupplierPartyMaster_Out.lpd.
- Create, Update or Delete a Vendor and save it.
- BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncSupplierPartyMaster_Out.lpd BOD.
- Verify the Result:
- Mapped VendorAddress.PostalAddress.DeliveryAddress.AddressLine4 in Xpath SupplierPartyMaster/Location/Address/CitySubDivisionName
- 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).
- Setup:
- In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
- 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.
- Create BillingInvoice Release it.
- Perform InvoiceVerificationReport
- Perform InvoiceAndRegisterPrint
- Perform SubSystemUpdate
- BOD will trigger and Work unit will generate With respective newly added element.
- 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;
- Changes in FSM_ION_SyncInvoice_Outbound IPA flow::
- Integration Specific: Yes. These changes are related to Local.ly Integration specific to Chile (CL).
- Setup:
- In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
- 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.
- Create BillingInvoice Release it.
- Perform InvoiceVerificationReport.
- Perform InvoiceAndRegisterPrint.
- Perform SubSystemUpdate.
- BOD will trigger and Work unit will generate With respective newly added element.
- 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
- Changes in FSM_ION_SyncInventoryAdj_Outbound.lpd:
- Integration Specific: No.
Use these steps to test the enhancement:
- Setup:
- Enable the service "InventoryAdjustmentService" for FSM_ION_SyncInventoryAdj_Outbound.lpd.
- Set the value of System Configuration Parameter "SyncInventoryAdjustment_Reference” to "Y".
- In Channel Administrator enable the receiver of FSM_ION_SyncInventoryAdjustment_Inbound.lpd.
- When BOD gets processed an InventoryTransaction of Adjustment is Created.
- 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.
- 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