IEFINConnector CU72

This section contains enhancements in Infor CloudSuite Financials for 11.0.72.0.

MT ION Content automation for iefinconnector

ION Desk administrators have to manually import the delivered CSF ION Contents standard templates for data flows, connection points, monitors and mapping.

It does not install:

  • MingleViewsforFSM (in Ming.le) – is installed with Mingle
  • FSMDistributionGroup (in User Management) Distribution groups are manually imported. ION is working on automation.

Program/Business class/Process affected:

  • Installation of the FSM IEFINConnector Plugin
  • ION Content – iefinconnector.pm

Use these steps to test this enhancement:

  1. For system admins, verify the ION Content property on FSM tenant's property tab in CSP is populated with an s3 location to the FSM_IONContent.zip
  2. For ION Desk admins, verify if the standard template for data flows, connection points, monitors and mapping are loaded on ION Desk for newly created tenants.

Dependencies:

  • This automation will only occur on newly provisioned tenants on MT
  • This process is not applicable to ST/OP installs

JT-1325377

Native LPL- Mapping of Elements for Source System Journal Entry OUT BOD

Mapping of Elements for Native Sync.SourceSystemJournalEntry OUT BOD

Program/Business class/Process affected:

  • PayablesInvoicePayment.bussclass

Use these steps to test this enhancement:

Enable service for Process FSM_ION_SyncSourceSystemJournalEntry.lpd in FSMBODConfiguration.

Give IntegrationApplication = "GRC" in FSMBODConfigurationParameter.

For GRC Integration:

BL:

  1. Create a Billing Invoice and Release it
  2. Run Invoice Verification Report
  3. Run Invoice and Register Print
  4. Run Sub System Update
  5. Journals will be created in released state and Perform Quick Post them.
  6. BOD will be triggered. Verify the XML in ION Out Queue

AR:

  1. Create receivableinvoicebatch and release it.
  2. Journalize the distributions created then journal will be created in released state.
  3. Perform Quick Post, then record will be moved to Posted state.
  4. BOD will be triggered. Verify the xml in ION Out Queue.

AP:

  1. Create and release payabesinvoice with distributions.
  2. Journalize the distributions. When it is done, the journal will be created in released state.
  3. Perform Quick Post, then Record will be moved to Posted tab.
  4. Work unit will be created. Verify the xml in ION Out Queue.

JT-1427835

SyncInvoice - Dummyline to be populated when a direct AR Invoice is created

Program/Business class/Process affected:

File 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 below changes done:

Below new variable added in start node:

  • ReceivableGLDistCategory
  • ReceivableGLDistHSNSACCode
  • ReceivableGLDistHSNSACCode
  • ReceivableGLDistHSNSACCode
  • ReceivableGLDistAmount
  • ReceivableGLDistTaxCode
  • ReceivableGLDistTransactionTaxableAmount
  • ReceivableGLDistTaxRate
  • ReceivableGLDistTaxAmount
  • InvoiceLine_XML

In AMD1 transaction node, added ReceivableCompanyDataGroup.ReceivableDistributionCategory & HSNSACCode & OriginalCurrency field:

  • In Assign8580 - Mapped values and added javascript.
  • d.In Assign9750 - Mapped ReceivableGLDistTaxRate values.
  • e.Added Assign4190.
  • f.In Assign4010 and Assign1740 : Javascript modified.
  • Earlier SystemID == "BL" && IntegrationApplication == "Local.ly" && Country =="AR" now changed to IntegrationApplication == "Local.ly" && Country =="AR" .
  • g.In XML_INVHDR XML - added InvoiceLine_XML

Integration Specific: Yes

These changes are related to Local.ly Integration.

Use these steps to test this enhancement:

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.

How to Test:

  1. Create ReceivableInvoice and Release it.
  2. BOD will trigger and Work unit will generate. With respective newly added element.
  3. Verify that the InvoiceLine passes.

JT-1433656

Create ION Data flow in CSFM1 with GFC and CSF as IMS connection point

This update added new document flows for FSM to GFC integration.

Program/Business class/Process affected:

  • FSM_GFC_ims_documentflow_ST.xml
  • FSM_all_documentflows_ST.xml
  • FSM_ims_GFC_ims_documentflow_ST.xml
  • FSM_IMS_All_DataFlows_ST.xml

Use these steps to test this enhancement:

  1. Import FSM_GFC_ims_documentflow_ST.xml file in data flows(ION).
  2. FSM_ims_GFC_ims_documentflow_ST.xml file in data flows(ION).
  3. Verify that document flows should create successfully in data flows(ION).
  4. Verify FSM to GFC IMS document flow.
  5. Verify FSM IMS to GFC IMS document flow.

JT-1438825

Changes for Sync_Receivable Tracker_Outbound

This enhancement added Currency and Amounts changes for FSM_ION_SyncReceivabelTracker_Out

Amounts should be converted based on dates. For Argentina Country Amounts need to calculate based on InvoiceDate. For Mexico Country Amounts need to calculate based on PaymentDate.

Program/Business class/Process affected:

New IPA Changes:

In start node added these variables

  • CurrRateFun
  • CurrRateRep
  • AssignedBaseAmount
  • TotalBaseAmount
  • ARIncomeWithHoldCode

Added four new transaction nodes to get the Currency rates for Argentina and Mexico Country.

In Assign8450 and Assign3780 converted all the amounts based on currency rates for Mexico country.

In Assign260 and Assign3780 Converted all the amounts based on Currency rates for Argentina country.

Integration Specific: Yes

These changes are related to CSF-Local.ly Integration.

As ReceivableTracker as using for Local.ly

Use these steps to test this enhancement:

Setup:

  1. In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
  2. In Service Definition enable the service for "ReceivableTrackerService" and attach FSM_ION_SyncReceivableTracker_Out

How to test:

  1. In AccountingEntity Add CountryCode Mexico/Argentina.
  2. Create ReceivableReason code for Tax type.
  3. Create ReceivableInvoice release it, Create ReceivablePayment and release it.
  4. Apply Payment to the Invoice with entering Adjustment type as tax.
  5. Perform ProcessSelections.
  6. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_ReceivableTracker_Out BOD (ReceivableTrackerService).

Test appropriate scenarios by creating ReceivablePayment and release.

Verify the result: In the XML below paths should be populated with values.

  1. Verify all the amounts in normal scenario and AdjustmentScenario in both header and line.
  2. All the amounts should be populate based on Dates for Mexico and Argentina Country

JT-1443669

New BOD ProcessBillToPartyMaster_Outbound

We have added a new IPA flow Process.BillToPartyMaster_Out BOD.

Program/Business class/Process affected:

Files changed:

  • CustomerBillTo.busclass
  • PayablesService.field
  • PfiServiceDefinition.xml
  • PfiServiceflowDefinition.xml

Files added:

  • ProcessBillToPartyMaster.txt
  • FSM_ION_ProcessBillToPartyMaster_Out.ipd

New Required Setup: Enable newly added Service "ProcessCustomerBillTo" in Service Definitions.

New Variable Added in JSON: New ProcessBillToPartyMaster.txt JSON file is added.

New IPA Changes: FSM_ION_ProcessBillToPartyMaster_Out is triggered for Create, Update and Delete actions on CustomerBillTo

Integration Specific: The changes are related to CSF-M3 integration.

Use these steps to test this enhancement:

Setup:

  1. In FinanceEnterpriseGroup, BODtrigger check box should be selected.
  2. For Outbound BOD, Enable the Service Definition ProcessCustomerBillTo and Process FSM_ION_ProcessBillToPartyMaster_Out

How to test:

  1. Give values for FSMBODConfigurationParameters:BillToPartyMaster_Outbound_AccountingEntity_All and SyncBillToPartyMstr_Outbound_AccountingEntity.
  2. BOD gets triggered for Create, Update and Delete actions of CustomerBillTo.

Verify the result:BOD will trigger and Work unit will generate successfully with the values in the XPath mapped according to the provided mapping sheet.

JT-1447198

New BOD ProcessShipToPartyMaster_Outbound

This change added a new BOD ProcessShipToPartyMaster_Outbound.

Program/Business class/Process affected:

  • CustomerShipTo.busclass
  • FSM_ION_ProcessShipToPartyMaster_Out

Use these steps to test this enhancement:

  1. Enable "ProcessCustomerShipToService" in Service Definition.
  2. Create/Update/Delete CustomerShipTo.
  3. Check the generated workunits.

JT-1447203

Add new elements and Update mapping Sheet for SyncCustomerPartyMaster_out

This enhancement added new elements and Updated mapping Sheet for SyncCustomerPartyMaster_out.

Program/Business class/Process affected:

Files Changed: FSM_ION_SyncCustomerPartyMaster_Out.lpd

  1. New Required Setup: No
  2. New Variable Added in JSON: No
  3. New IPA Changes:
    • Added new elements Cdebitcrd,CBankTrcode,Ctermcode in start node.
    • Added new LMRK queries TCode,DCode for termscode description.
  4. Integration Specific: No

Use these steps to test this enhancement:

Setup: Enable the service "CompanyCustomerService" for FSM_ION_SyncCustomerPartyMaster_Out.lpd

How to test:

  1. Create a CompanyCustomer and save it.
  2. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCustomerPartyMaster_Out.lpd BOD (CompanyCustomerService).

Verify the Result:

  1. Mapped CompanyCustomer.BankTransactionCode to CustomerPartyMaster/PaymentMethodCode.
  2. Mapped CompanyCustomer.TermsCode to CustomerPartyMaster/CustomerAccount/Term/ID.
  3. Mapped CompanyCustomer.DebitCreditMemoTermsCode to CustomerPartyMaster/CustomerAccount/Term/ID.
  4. Mapped CompanyCustomer.TermsCode.Description.Desc[1] to CustomerPartyMaster/CustomerAccount/Term/Description.
  5. Mapped CompanyCustomer.DebitCreditMemoTermsCode.Description.Desc[1] to CustomerPartyMaster/CustomerAccount/Term/Description.

JT-1447297

Elements added to SyncSupplierPartyMaster_Out

Program/Business class/Process affected:

Files Changed: FSM_ION_SyncSupplierpartyMaster_Out.lpd

New Required Setup: No

New Variable Added in JSON:

  • VFExtension
  • VFIPrefix
  • VFNumber
  • VEmail
  • VPExtension
  • VPPrefix
  • VPNumber
  • VTaxCode
  • VMExtension
  • VMPrefix
  • VMNumber

New IPA Changes: In XML_VEN,XML_VENDOR_WITH_CONTACT nodes mapped Vendor.TaxCode to path SupplierPartyMaster/PartyIDs/TaxID.

Integration Specific: No

Use these steps to test this enhancement:

  1. Setup: Enable the service "VendorGroupService" for FSM_ION_SyncSupplierPartyMaster_Out.lpd
  2. How to test:
    • 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.
  3. Verify the result: Mapped Vendor.TaxCode to path SupplierPartyMaster/PartyIDs/TaxID.

JT-1447304

New elements added to SyncCustomerParty_Out

This change added new elements and Updated mapping Sheet for SyncCustomerPartyMaster_out.

Program/Business class/Process affected:

Files Changed:

  • FSM_ION_SyncCustomerPartyMaster_Out.lpd
  • CompanyCustomer.busclass

New required setup: No

New variable added in JSON: No

New IPA changes:

Added new elements

  • EFTBankAcc
  • CBankEntity
  • CustomerGroup
  • VatRegistrationCountryin start node

In Assign5830 node,EFTBankAccount is assigned to EFTBankAcc,CustomerBankEntity is assigned to CBankEntity.

Integration specific: No

Use these steps to test this enhancement:

  1. Setup: Enable the service "CompanyCustomerService" for FSM_ION_SyncCustomerPartyMaster_Out.lpd
  2. How to test:
    • Create a CompanyCustomer and save it.
    • BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCustomerPartyMaster_Out.lpd BOD (CompanyCustomerService).
  3. Verify the result:
    • Mapped CustomerDraftBank.BOEEFTBankAccount to FinancialParty/FinancialAccount/AccountIDs/ID.
    • Mapped CompanyCustomer.VatRegistrationCountry and CompanyCustomer.CustomerGroup to UserArea.

JT-1448406

Supplier Party Master - VAT/TaxID SchemeAgencyName Changes

Program/Business class/Process affected:

  • FSM_ION_SyncSupplierpartyMaster_Out.lpd.
  • schemeagencyname changes for VAT/TAxId

Integration Specific: Yes, changes are specific to Local.ly Argentina Country.

Use these steps to test this enhancement:

  1. Enable Service Definition for "VendorGroupService" and attach FSM_ION_SyncSupplierPartyMaster_Out lpd file.
  2. Create Vendor with Tax ID and Vendor Registration Number.
  3. Workunit will be created for "VendorGroupService"
  4. Verify the VAT/TaxID details in XML.

JT-1448579

PayableTracker - Addtion of Tax Regime Code

The TaxRegime code was added to PayableTransaction BOD.

Program/Business class/Process affected:

  • FSM_ION_SyncPayablesTracker_Out.lpd

Added user area node in PayablesTrackerLine/Tax/Userarea passing TaxRegime Code.

Use these steps to test this enhancement:

  1. Enable BODTrigger in FinanceEnterpriseGroup.
  2. Enable ServiceDEfinition for PayablesTrackerService and attach FSM_ION_SyncPayableTracker_out lpd.
  3. Create PayablsInvoice with tax and WithHolding details and release it.
  4. Perform CashRequirements.
  5. Run ElectronicPaymentCreation.
  6. Workunit will be created successfully for PayablesTrackerService.
  7. Verify the xml in Adjustment tax xml user area should be populated with tax regime.

JT-1449185

Changes for Sync_SupplierInvoice_Outbound-- Local.ly

For Local.ly Integration Tax Distributions should be populated on IsTaxDistribution condition.

Program/Business class/Process affected:

  • FSM_ION_SyncSupplierInvoice_Outbound.lpd

  • In start node added these variables: IsTaxDistribution

Added new Assign5320 node for Local.ly Integration.

In Tax Javascript derived Tax_XML based on IsTaxDistribution condition.

Integration Specific: Yes

These changes are related to CSF-Local.ly Integration.

Use these steps to test this enhancement:

  1. Setup:
    • In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    • In Service Definition enable the service for "PayablesInvoiceService" and attach FSM_ION_SyncSupplierInvoice_Outbound
  2. How to test:
    • Create PayablesInvoice type TaxInvoice
    • Add Linked Tax distribution to Invoice and release it.
    • BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SupplierInvoice_Outbound BOD (PayablesInvoiceService).
  3. Verify the result:Only ISTaxDistribution = "true" nodes should be passed in Tax node remaining distribution should be populate in Distribution nodes.

JT-1449297

New elements added to SyncSalesOrder_Out

There are new elements in Sync.SalesOrder_Out bod for CSF-GRC integration.

Program/Business class/Process affected:

Files changed: FSM_ION_SyncSalesOrder_Outbound.

New required setup: no

New variable added in JSON:

  • Added CustomerOrder.CancelledDate as CancelledDate
  • Added CustomerOrder.ShippingMethod as ShippingMethod

New IPA changes:

  • Added variables in Start Node: CancelledDateTime
  • Defined the CancelledDate as DateTime format in Java Script

Integration specific: Changes are related to CSF-GRC integration

Use these steps to test this enhancement:

  1. Setup:
    • In FinanceEnterpriseGroup, BODtrigger check box should be checked.
    • For Outbound BOD, Enable the Service Definition CustomerOrderService and Process FSM_ION_SyncSalesOrder_Outbound
  2. How to test:
    • Ceate CustomerOrder and release it.
    • BOD will trigger and work unit will generate successfully without any error for FSM_ION_SyncSalesOrder_Out BOD (CustomerOrderService).
  3. Verify the result:
    • Verify the X-Path values for all scenarios
    • SalesOrder/SalesOrderHeader/CancelShipByDateTime
    • SalesOrder/SalesOrderHeader/PaymentTerm/ID
    • SalesOrder/SalesOrderHeader/TransportationMethodCode

JT-1449915

New elements added to SyncShipment_Out

We added new elements in Sync.Shipment_Out bod for CSF-GRC integration.

Program/Business class/Process affected:

Files changed: FSM_ION_SyncShipment_Outbound.

New required setup: No new setup is required

New variable added in JSON:

  • Added WarehouseShipment.ShipmentMethod as ShipmentMethod
  • Added WarehouseShipment.WarehouseBatch as WarehouseBatch

New IPA changes:

  • Added variables in Start Node: CustPrtyID and CustShipName
  • Defined the CustPartyID and CustShipName in Java Script
  • Passed accountingEntity and CustPartyID in the header XML

Integration specific: Changes are related to CSF-GRC integration

Use these steps to test this enhancement:

  1. Setup:
    • In FinanceEnterpriseGroup, BODtrigger check box should be checked.
    • For Outbound BOD, Enable the Service Definition ShipmentService and Process FSM_ION_Shipment_Outbound
    • Assign value to Configuration Parameter : IntegratingApplication as GRC
  2. How to test:
    • Ceate CustomerOrder and Release it.
    • Run WarehousepickListPrint batch job.
    • BOD will trigger and Work unit will generate successfully without any error for FSM_ION_Shipment_Out BOD (ShipmentService).
  3. Verify the result:

    Verify the X-Path values for all scenarios

    • Shipment/ShipmentHeader/CustomerParty/PartysID/ID @AccountingEntity
    • Shipment/ShipmentHeader/CustomerParty/PartysID/ID
    • Shipment/ShipmentHeader/RequiredShipDateTime
    • Shipment/ShipmentHeader/TransportationMethodCode
    • Shipment/ShipmentHeader/ShipToParty/Name
    • UserArea/Property/fsm.BatchNumber/WarehouseShipment.WarehouseBatch

JT-1449912

New elements added to SyncInvoice_out

Program/Business class/Process affected:

File 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 below changes done:

  • These new variables added in start node:
    • BLInvHoldCode
    • BLInvBatchNumber
    • BLInvPostingDate
  • In BLinvoice transaction node, added HoldCode and GeneralLedgerDate field.
  • In Assign8960 - BLInvBatchNumber variable mapped to BLinvoice_BatchNumber and BLInvHoldCode mapped to BLinvoice_HoldCode.

  • In Assign1740 - Javascript changed - If IntegrationApplication "GRC" and SystemID "BL"

    BLInvBatchNumber, BLInvHoldCode, and BLInvPostingDate mapped value. If not - value will be blank.

Integration specific: Yes

These changes are related to CSF-GRC Integration.

Use these steps to test this enhancement:

  1. 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.
  2. How to test:
    • Create BillingInvoice and Release it.
    • Execute InvoiceAndVerificationReport.
    • Execute InvoiceAndRegisterPrint
    • Execute SubSystemUpdate
    • ReceivableInvoice Record will create in Released state.
    • BOD will trigger and Work unit will generate. With respective newly added element.
  3. Verify the result:

    Verify the newly added below x-path:

    • UserArea/Property/fsm.BatchNumber --BillingInvoice.BatchNumber
    • UserArea/Property/fsm.HoldCode --BillingInvoice.HoldCode
    • UserArea/Property/fsm.PostingDate --BillingInvoice.GeneralLedgerDate

JT-1449920

Mapping of elements in Sync.ReceivableTransactionOutBod for CSF-GRC PI

This change added new elements to SyncReceivableTransaction_Outbound for CSF-GRC.

Program/Business class/Process affected:

Files changed:

  • ReceivableInvoice.busclass
  • FSM_ION_SyncReceivableTransaction_Outbound
  • ReceivableTransactionJSON.txt

New required setup: No

New variable added in JSON: Yes

  • Added ReceivableInvoice.BatchNumber as RIBatchNumber

New changes:

  • In FSM_ION_SyncReceivableTransaction_Outbound IPA flow below changes done:
    • Added ReceivableInvoice.BatchNumber as RIBatchNumber.
    • Added ReceivableInvoice.BatchNumber as RIBatchNumber.
    • Added TermsCode.TermsDiscountArray.TermsDiscountGroup[1].DiscountPercent as TermsCodeDiscountPercent in ReceivableInvoice service variables.

Integration Specific: Yes

  • These changes are related to CSF_GRC Integration.

Use these steps to test this enhancement:

  1. Setup: Provide the setup to execute the flow/changes.
    • In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    • Enable "ReceivableTransactionService" service for FSM_ION_SyncReceivableTransaction_Outbound
  2. How to test:
    • Create a ReceivableInvoice with multiple details and release it.
    • Create a ReceivablePayment and apply payment to the invoice.
    • Perform ProcessSelections.
    • In CashApplication, perform ProcessSelections.
    • BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncReceivableTransaction_Outbound.
  3. Verify the result:
    • ReceivableTransactionHeader/PaymentTerm/Discount/DiscountPercent
    • ReceivableTransactionHeader/UserArea/Property/fsm.BatchNumber

JT-1450706

Element added to SyncItemMaster_Out

This update added element to SyncItemMaster_Out and Updated in mapping sheet.

Program/Business class/Process affected:

Files Changed: FSM_ION_SyncItemMaster_Out.lpd

New required setup: No

New variable added in JSON: Item.CommodityCode is mapped with CommodityCode.

New IPA Changes: In "UserAreaAssign" node CommodityCode is passed in headerUserArea XML.

Integration specific: No

Use these steps to test this enhancement:

  1. Setup:
    • Enable the service "ItemService" for FSM_ION_SyncItemMaster_Out.lpd
  2. How to test:
    • Create an Item and save it.
    • BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncItemMaster_Out.lpd BOD (ItemService).
  3. Verify the result:
    • Mapped Item.CommodityCode in UserArea.

JT-1450748

CustomerPartyMaster - VAT/TaxID changes

Program/Business class/Process affected:

File Changed: FSM_ION_SyncCustPrtyMstr_Outbound.lpd

New required setup: No

New variable added in JSON: No

New IPA Changes:

In FSM_ION_SyncCustPrtyMstr_Outbound IPA flow below changes done:

In XML_Customer XML - chnaged the order like below

  • <TaxID schemeName={SchemaValue} schemeAgencyName={SchemaAgencyValue}>
  • {VATRegistrationNumber}@NoNullTag@</TaxID>
  • <TaxID schemeName={SchemaValue1} schemeAgencyName={SchemaAgencyValue1}>
  • {Customer["TaxID"]}@NoNullTag@</TaxID>

Integration specific: Yes

  • These changes are related to Local.ly Integration, country specific to Argentina.

Use these steps to test this enhancement:

  1. Setup:
    • In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    • Enable the Service Definition and Processes for FSM_ION_SyncCustPrtyMstr_Outbound IPA flow.
    • Go to Service Definition and Enable "CompanyCustomerService" for "FSM_ION_SyncCustPrtyMstr_Outbound.lpd" Processes.
  2. How to test:
    • CustomerParty/TaxID@schemeAgencyName =AR:VAT -->CompanyCustomer.VATRegistrationNumber
    • CustomerParty/TaxID@schemeAgencyName = AR:IIBB --> Customer.TaxID AR:VAT should first then AR:IIBB

JT-1452058

New Enhancements required for Sync Lcl tax report for mexico.(Local.ly)

Program/Business class/Process affected:

Files changed: FSM_ION_SyncLCLTaxReport.lpd

New required setup: No

New variable added in JSON: No

New IPA Changes: Added new Branch Branch1510, VenRet Lmrk query.

Integration Specific: Local.ly Integration for MX Country

Use these steps to test this enhancement:

  1. Setup:
    • Enable the service "TaxReportService" for FSM_ION_SyncLCLTaxReport _Out.lpd.
    • In SystemConfiguration give the value of IntegrationApplication == "Local.ly"
  2. How to test:
    • Create a Payablesinvoice with tax and PayablesInvoice of type Credit memo and release it. Do the payment for the Invoice by performing actions:
      • Perform cash Requirements
      • Electronic Payment Creations
      • PaymentClose: Run Vat Return Report batch Job. BOD will trigger and work unit will generate successfully
  3. Verify the result:
    • Run Vat Return Report batch Job. BOD will trigger and work unit will generate successfully
    • In case of Normal Credit Memos consider it as Normal invoices and add those accordingly.

JT-1453063

Added certification number and date to ProcessInvoice BOD

This enhancement added two new fields to Process.Invoice BOD:
  • Certification Number
  • Certification Date

Program/Business class/Process affected:

Files changed: FSM_ION_ProcessInvoice_Inbound

  • Added new fields in StartNode
  • Added new fields AssignHdr node
  • Added new fields in CreateRecInv transaction Node

New required setup: No

Use these steps to test this enhancement:

  1. Setup: Create channels for Process.Invoice_Inbound BODs.
  2. How to test:
    • Send valid XML and record should create in ReceivableInvoice with CertificationNumber and CertificationDate fields.
    • Pass the CertificationNumber and CertificationDate values in Header UserArea.
  3. Verify the result:
    • Check record in ReceivableInvoice and it should be released state with CertificationNumber and CertificationDate fields.
    • Workunit should create without any errors.

JT-1453616

PayableTracker - Tax Regime Code truncation

Tax Regime Code truncation done in PayableTracker Out BOD.

Program/Business class/Process affected:

File Changed: FSM_ION_SyncPayableTracker_Out.lpd

New required setup: No

New variable added in JSON: No

IPA Change:

  • Added 'TaxWHC' variable with the type of String with "" value at start node.
  • Added change in JavaScript at Assign3140 node for TaxWHC as below.

    if(PIWH_IncomeWithholdingCode !="" )

    {

    TaxWHC = PIWH_IncomeWithholdingCode.substring(0,4);

    }

  • In Next JavaScript, replaced 'PIWH_IncomeWithholdingCode' with 'TaxWHC' @xpath PayableTracker/PayableTrackerLine/Tax/UserArea/Property/NameValue[@name='lcl.TaxRegime'].

Use these steps to test this 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 With Holding Tax of PayableTracker flow.
    • Create PayablesInvoice with Tax information 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.lpd BOD.
  3. Verify X-Paths:
    • PayableTracker/PayableTrackerLine/Tax/UserArea/Property/NameValue[@name='lcl.TaxRegime'].

JT-1453814

ION Content and JSON Files Delivery

This is the 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

Use these steps to test this enhancement:

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

JT-1454233

SyncInvoice - Dummyline AR Invoice to be Applicable for only India Country

SyncInvoice - Dummyline AR Invoice to be Applicable for only India Country Local.ly.

Program/Business class/Process affected:

File 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 below changes done:

Below new variable added in start node:

  • ARInvoiceLine_Sequence

In Assign4190: Modified javascript:

  • InvoiceLine_XML only for India Local.ly
  • Added ARInvoiceLine_Sequence incremented logic
  • Added x-path InvoiceLine/LineNumber

Integration specific: Yes

  • These changes are related to Local.ly Integration Specific to country India.

Use these steps to test this enhancement:

  1. Setup:
    • In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    • Go to Service Definition and Enable "ReceivableInvoiceService" for "FSM_ION_SyncInvoice_Outbound.lpd" Processes.
  2. How to test:
    • Create ReceivableInvoice and Release it.
    • BOD will trigger and Work unit will generate. With respective newly added element.
  3. Verify the result: InvoiceLine will pass for Local.ly India also added x-path InvoiceLine/LineNumberEnable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.

JT-1455371

SupplierPartyMaster - VAT/TaxID changes

Program/Business class/Process affected:

Files changed: FSM_ION_SyncSupplierpartyMaster_Out.lpd

New required setup: no

New variable added in JSON:
  • VFExtension
  • VFIPrefix
  • VFNumber
  • VEmail
  • VPExtension
  • VPPrefix
  • VPNumber
  • VTaxCode
  • VMExtension
  • VMPrefix
  • VMNumber

New IPA Changes:

  • Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPAIn Assign_1 node added a condition if(IntegrationApplication == "Local.ly" && VendorPostalAddressCountry == "AR" )

    {

    if(VATRegNumber == VendorTaxID)

    {

    SchemeAgencyName1 = "AR:VAT";

    SchemeAgencyName = "";

    VendorTaxID = "";

    SchemeValue = "";

    }

    }

  • In XML_VEN,XML_VENDOR_WITH_CONTACT nodes interchanged the Xpaths SupplierPartymaster/PartyIDs/TaxID mapped with VatregistrationNumber and VendorTaxID.

Use these steps to test this enhancement:

  1. Setup: Enable the service "VendorGroupService" for FSM_ION_SyncSupplierPartyMaster_Out.lpd
  2. How to test:
    • 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.
  3. Verify the result:If VatRegistrationNumber and TaxID are same then only TaxID mapped with VatRegistrationNumber Xpath will come.

JT-1456076

CustomerPartyMaster - VAT/TaxID changes

Program/Business class/Process affected:

Files changed: FSM_ION_SyncCustomerPartyMaster_Out.lpd

New required setup: No

New variable added in JSON: No

New IPA Changes:

  • Added new Variable CTaxID in start node.
  • In Assign5830 node, CTaxID is assigned to "Customer["TaxID"]"
  • In Assign5830 node, added a condition

    if (IntegrationApplication == "Local.ly" && AddressCountryCode == "AR")

    {

    if(VATRegistrationNumber==CTaxID)

    {

    SchemaAgencyValue = "AR:VAT";

    SchemaAgencyValue1 = "";

    CTaxID = "";

    SchemaValue1 = "";

    }

    else

    {

    SchemaAgencyValue = "AR:VAT";

    SchemaAgencyValue1 = "AR:IIBB";

    }

  • In "XML_Customer" node Customerpartymaster/partyids/taxid is mapped with CTaxID

Integration specific: No

Use these steps to test this enhancement:

  1. Setup: Enable the service "CompanyCustomerService" for FSM_ION_SyncCustomerPartyMaster_Out.lpd
  2. How to test:
    • Create a CompanyCustomer and save it.
    • BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCustomerPartyMaster_Out.lpd BOD (CompanyCustomerService).
  3. Verify the result: If VatRegistrationNumber and TaxID are same then only TaxID mapped with VatRegistrationNumber Xpath will come.

JT-1456081