IEFINConnector CU71

This section contains enhancements in Infor CloudSuite Financials for 11.0.71.0.

Replace existing elements with new elements in SSJE Bod (FEC for France)

This update added supplier and customer details in line level user area for AP,AR and BL for Sync.SSJE outbound BOD for Local.ly integreation.

Program/Business class/Process affected:

  1. Files Changed:

    FSM_ION_SyncSourceSystemJournalEntry_Outbound.lpd

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:
    • In node Start,added SingleBLInvoice,BLMultiDetails variables
    • Removed country dependency condition for AP and AR in node Branch1710
    • In node Assign2700, added BLMultiDetails is true when GLTransactionDetails count is greater than 1.
    • In node Assign1430, line level userarea property is added with Create BillingInvoice and release it. name="lcl.SourceIdentifier" and name="lcl.SupplierID" for GLTransactionDetails count is greater than 1.
    • In node GLTRN_VAR,removed "FR" country dependent code for Local.ly
  5. Integration Specific: Yes

    This changes should applicable only for Local.ly Inegration.

Use these steps to test this enhancement:

Enable service definition GLJournalControlService for Process FSM_ION_SyncSourceSystemJournalEntry.lpd

For Local.ly:

a) 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 Line level user area for Customer details

b) 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 line level user area for customer details.

b) AP:

  1. Create and release payabes invoice with distributions.
  2. Journalize the distributions. once it is done 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 header and line level user area for Supplier Details.

JT-1414634

NativeLPL:Add new elements and update mapping sheet for SyncInvoice_Out

Added new elements for SyncInvoice_Out NativeLPL BOD for CSF-GRC.

Program/Business class/Process affected:

  • ReceivableInvoice
  • BillingInvoiceLine
  • wfdata/UserTemplate

Use these steps to test this enhancement:

In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.

In FSMBODConfigurtaion, Enable SyncInvoice NativeLPL.

In FSMBODConfigurationParameter define the IntegartinApplication value as GRC

  2. Execute InvoiceAndVerificationReport.
  3. Execute InvoiceAndRegisterPrint
  4. Execute SubSystemUpdate
  5. ReceivableInvoice Record will create in Released state
  6. BOD will trigger and ION OutQueue will create

Verify the respective x-path.

Invoice/InvoiceHeader/LastModificationPerson/IDs/ID

Invoice/InvoiceHeader/PaymentTerm/Term/ID

Invoice/InvoiceHeader/PaymentTerm/Description

Invoice/InvoiceLine/ShipToParty/PartyIDs/ID

Invoice/InvoiceLine/ExtendedReportAmount

Invoice/InvoiceLine/ExtendedReportAmount@CurrencyID

Invoice/InvoiceLine/ExtendedAmount

Invoice/InvoiceLine/ExtendedAmount@CurrencyID

Invoice/InvoiceLine/SalesOrderReference/DocumentID/ID

Invoice/InvoiceLine/SalesOrderReference/LineNumber

JT-1421234

Sync.CustomerReturn Outbound BOD Development - IPA

A new SyncCustomerReturn_Out bod was developed for CustomerOrderReturn.

Program/Business class/Process affected:

  1. Files Changed:
    • CustomerOrderReturn.busclass
    • OrderEntryReturnsGlobalLedgerPosting_OrderEntryReturnsGlobalLedgerPosting.java
    • PfiServiceDefinition.xml
    • PfiServiceFlowDefinition.xml
    Files Added:
    • SyncCustomerReturnJSON.txt
    • FSM_ION_SyncCustomerReturn_Out.lpd
  2. Create New Required Setup: Enable newly added service CustomerReturnService for FSM_ION_SyncCustomerReturn_Out in Service Definitions.
  3. New Variable Added in JSON: New SyncCustomerReturnJSON is added
  4. New IPA Changes: FSM_ION_SyncCustomerReturn_Out is developed for CustomerOrderReturn. The BOD will be triggered when the CustomerOrderReturns are made.
  5. Integration Specific: These changes are related to CSF-GRC Integration.

Use these steps to test this enhancement:

Setup:

In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.

Enable the "CustomerReturnService" in Service Definition for FSM_ION_SyncCustomerReturn_Out Processes.

Scenario 1:

  1. Create CustomerOrderReturn for the BillingInvoice.
  2. Create CustomerOrderReturnLine.
  3. Select InventoryDisposition value in the CustomerOrderReturnLine. (If CustomerOrderReturnLine.InventoryDisposition = "ReturnToStock" or "Scrap" then Status will be "Released" else Status will be "Closed".)
  4. Release the CustomerOrderReturn.
  5. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCustomerReturn_Out BOD (CustomerReturnService).

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).

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-1424322

Changes to SyncSalesOrder_Out

Changes were made in some XML fields for Sync.SalesOrder_Out BOD.

Program/Business class/Process affected:

Files Changed:

FSM_ION_SyncSalesOrder_Outbound

New Required Setup:

Added new System Configuration Parameter "IntegratingApplication": Set the value according to the integration used (GRC)

New Variable Added in JSON:

No new variables added in JSON

New IPA Changes:

In FSM_ION_SyncSalesOrder_Outbound IPA flow below changes done:

Added variables in Start node :

  • IntegrationApp
  • BillToPartyID
  • PayFromPartyID
  • ShipToPartyID

Added JavaScript to define the variables based on IntegrationApp

if (IntegrationApp == "GRC")

BillToPartyID = Customer + GenericDelimiter + CustomerOrder.CustomerBillTo

PayFromPartyID = CustomerOrder.Company + GenericDelimiter + Customer

ShipToPartyID = CustomerOrder.Company + GenericDelimiter + Customer + GenericDelimiter + CustomerOrder.CustomerShipTo

else

BillToPartyID = CustomerOrder.CustomerBillTo

PayFromPartyID = Customer

ShipToPartyID = CustomerOrder.CustomerShipTo

Integration Specific:

These are changes are related to GRC integration.

Use these steps to test this enhancement:

Setup:

  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. For Outbound BOD, Enable the Service Definition "CustomerOrderService" and Process "FSM_ION_SyncSalesOrder_Outbound".

How to Test:

  1. Ceate CustomerOrder and Release it.
  2. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncSalesOrder_Out BOD.

Verify the Result:

Verify the X-Path values for all scenarios

SalesOrder/SalesOrderHeader/BillToParty/PartyIDs/ID

SalesOrder/SalesOrderHeader/BillToParty/Name

SalesOrder/SalesOrderHeader/PayFromParty/PartyIDs/ID

SalesOrder/SalesOrderLine/ShipToParty/PartyIDs/ID

SalesOrder/SalesOrderLine/ShipToParty/Name

JT-1424890

Local.ly: Populate PartyID in Shipment BOD (Sales transport Document)

Populated PartyID and some other fields in Shipment_Out BOD (Sales transport Document)

Program/Business class/Process affected:

Files Changed:

FSM_ION_SyncShipment_Outbound.

New Required Setup:

No new setup is required.

New Variable Added in JSON:

New JSON object is added. Added the fields from InventoryLocation.

New IPA Changes:

Added new fields in JSON Parser from InventoryLocation

InventoryLocation.PostalAddress.DeliveryAddress.AddressLine1 as ShipFromPartAdr1

InventoryLocation.PostalAddress.DeliveryAddress.AddressLine2 as ShipFromPartAdr2

InventoryLocation.PostalAddress.DeliveryAddress.AddressLine3 as ShipFromPartAdr3

InventoryLocation.PostalAddress.DeliveryAddress.AddressLine4 as ShipFromPartAdr4

InventoryLocation.PostalAddress.Municipality as ShipFromPartyCity

InventoryLocation.PostalAddress.StateProvinc

InventoryLocation.PostalAddress.PostalCode as ShipFromPartyPostalCode

InventoryLocation.PostalAddress.Country as ShipFromPartyCountry

Integration Specific:

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. For Outbound BOD, Enable the Service Definition "ShipmentService" and Process "FSM_ION_SyncShipment_Outbound".

How to Test:

  1. Create Requisition and Release it.
  2. Run WarehousePickListPrint.WarehousePickListPrint batch Job.
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncShipment_Out BOD.

Verify the Result:

  1. Verify the below X-Path values.
  2. SyncShipment/ShipmentHeader/ShipToParty/PartyIDs/ID
  3. SyncShipment/ShipmentHeader/ShipFromParty/PartyIDs/ID
  4. SyncShipment/ShipmentHeader/ShipFromParty/Location/Address/AddressLine
  5. SyncShipment/ShipmentHeader/ShipFromParty/Location/Address/CityName
  6. SyncShipment/ShipmentHeader/ShipFromParty/Location/Address/CountrySubDivisionCode
  7. SyncShipment/ShipmentHeader/ShipFromParty/Location/Address/CountryCode
  8. SyncShipment/ShipmentHeader/ShipFromParty/Location/Address/PostalCode

JT-1425408

Add Auto-Reverse flag checking in the Journal Entry line (CSF-GFC-Payroll Integration)

Add Auto-Reverse flag in Journal Entry line (CSF-GFC-Payroll Integration)

Program/Business class/Process affected:

Files Changed:

FSM_ION_ProcessSourceSystemJournalEntry_Inbound

New Required Setup: No

New Variable Added in JSON: No

New IPA Changes:

In FSM_ION_ProcessSourceSystemJournalEntry_Inbound IPA flow below changes done:

  • Below variable added in start node:

    lineLevelAutoReverse

    HeaderAutoReverse

  • Changes done in ExtractHeader node:

    Assigned AutoReverse flag to HeaderAutoReverse

  • Changes done in ExtractLine node:

    if line level AutoReverse flag is 'true/false' then AutoReverse field in GLTransactionInterface will be 'true/false' otherwise it will take from header AutoReverse flag. if both Header and line level AutoReverse flag is empty then will take 'false'

Use these steps to test this enhancement:

Setup: Provide the setup to execute the flow/changes.

  1. In FinanceEnterpriseGroup, BODtrigger check box should be checked.
  2. For Inbound BOD, In Channels Administrator, Activate FSM_ION_ProcessSourceSystemJournalEntry_Inbound ION Inbox Receivers.

How to Test:

  1. If line level AutoReverse flag is 'true/false' then AutoReverse field in GLTransactionInterface will be 'true/false' otherwise it will take from header AutoReverse flag.
  2. If line level AutoReverse flag is 'true/false' then AutoReverse field in GLTransactionInterface will be 'true/false' otherwise it will take from header AutoReverse.
  3. Once data is processed and saved to GLTransactionInterface businessclass.
  4. Check AutoReverse field flag is assigning correctly or not.

JT-1425823

Mapping of Elements for Source System Journal Entry OUT BOD

Mapping of Elements In Sync.SSJE Outbound BOD for GRC Integration.

Program/Business class/Process affected:

Files Changed:

FSM_ION_SyncSourceSystemJournalEntry_Outbound.lpd

New Required Setup: No

New Variable Added in JSON: Yes

ResourceOperator

New IPA Changes:

  • In node Start,added FunctionalDebitAmt, GRCReleaseOperator, CurrentDate, PostingDate ,PostingOperator, GRC_JournalType variables
  • In GLGLC_VAR node, FunctionalDebitAmt, GRCReleaseOperator, CurrentDate, PostingDate, PostingOperator, GRC_JournalType variables are assigned with values only when integration type is GRC.

Integration Specific: Yes

this changes should applicable only for GRC Inegration.

Use these steps to test this enhancement:

Enable service definition GLJournalControlService for Process FSM_ION_SyncSourceSystemJournalEntry.lpd

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 on them.
  6. BOD will be triggered. Verify the XML.

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.

JT-1425911

Changes for SyncInvoice_Outbound-- Local.ly

SyncInvoice_out Discount/ReportAmount mapping changes specific to Local.ly for AR flow.

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:

In Assign4010 - Modified javascript condition.

Integration Specific: Yes

These changes are specific 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.
  2. BOD will trigger and Work unit will create.

Verify the Result:

Verify below x-path:

  • InvoiceHeader/PaymentTerm/Discount/ReportAmount@CurrencyID
  • InvoiceHeader/PaymentTerm/Discount/ReportAmount

JT-1428837

Add new trigger logic: BOD should be triggered when shipment is created from Customer Order.

Added new trigger logic for FSM_ION_SyncShipment_Out for CSF-GRC Integration: BOD should be triggered when shipment is created from Customer Order.

Program/Business class/Process affected:

Files Changed:

  • FSM_ION_SyncShipment_Outbound.
  • SyncShipmentJSON.txt
  • OrderEntryDailyShipmentJournal_OrderEntryDailyShipmentJournal.java
  • WHSHP70PD.java
  • WarehouseShipment.busclass

New Required Setup: Use these steps to test this enhancement: System Configuration Parameter "IntegratingApplication”: Set the Value to GRC.

New Variable Added in JSON:

  • Added CustomerShipTo.ShipToAddress.DeliveryAddress.AddressLine1 as "CustomerShipToAddr1"
  • Added CustomerShipTo.ShipToAddress.DeliveryAddress.AddressLine2 as "CustomerShipToAddr2"
  • Added CustomerShipTo.ShipToAddress.DeliveryAddress.AddressLine3 as "CustomerShipToAddr3"
  • Added CustomerShipTo.ShipToAddress.DeliveryAddress.AddressLine4 as "CustomerShipToAddr4"
  • Added CustomerShipTo.ShipToAddress.Municipality as "CustomerShipToCityAddr5"
  • Added CustomerShipTo.ShipToAddress.StateProvince as "CustomerShipToState"
  • Added CustomerShipTo.ShipToAddress.Country as "CustomerShipToCountry"
  • Added CustomerShipTo.ShipToAddress.PostalCode as "CustomerShipToPostalCode"
  • Added WarehouseShipment.CustomerShipTo as "WSCustomerShipTo"
  • Added CustomerShipTo.Name as "CustomerShipToName"

New IPA Changes:

In FSM_ION_SyncShipment_Outbound IPA flow below changes done:

  • ShipToPartyID
  • WSCustomerShipTo

Branch7830 newly added to verify the condition:

  • If IntegratingApplication = "GRC" and WHShipment.WarehouseDemand.DemandSystemCode="OE" go to "AssignUserArea"
  • If WHShipment.WarehouseDemand.DemandSystemCode="RQ" go to "REQ"- else go to "End"

For If IntegratingApplication = "GRC" and WHShipment.WarehouseDemand.DemandSystemCode="OE" mapped following values to the below XPaths :

  • ShipmentHeader/ShipToParty/ PartyIDs /ID: WarehouseShipment.Company @@ Customer@@ CustomerShipTo
  • ShipmentHeader/ShipToParty/ Location/ Name : CustomerShipTo.Name
  • ShipmentHeader/ShipToParty/ Location/ Address/ AddressLine1 : CustomerShipTo.ShipToAddress.DeliveryAddress.AddressLine1
  • ShipmentHeader/ShipToParty/ Location/ Address/ AddressLine2 : CustomerShipTo.ShipToAddress.DeliveryAddress.AddressLine2
  • ShipmentHeader/ShipToParty/ Location/ Address/ AddressLine3 : CustomerShipTo.ShipToAddress.DeliveryAddress.AddressLine3
  • ShipmentHeader/ShipToParty/ Location/ Address/ AddressLine : CustomerShipTo.ShipToAddress.DeliveryAddress.AddressLine4
  • ShipmentHeader/ShipToParty/ Location/ Address/ CityName : CustomerShipTo.ShipToAddress.Municipality
  • ShipmentHeader/ShipToParty/ Location/ Address/ CountrySubDivisionCode : CustomerShipTo.ShipToAddress.StateProvince
  • ShipmentItem/SalesOrderReference/DocumentID/ID : WarehouseShipment.Company @@ WHShipment.WarehouseDemand.DemandDocument
  • ShipmentHeader/ShipToParty/ Location/ Address/ CountryCode : CustomerShipTo.ShipToAddress.Country
  • ShipmentHeader/ShipToParty/ Location/ Address/ PostalCode: CustomerShipTo.ShipToAddress.PostalCode

Integration Specific: These changes are related to CSF-GRC Integration

Use these steps to test this enhancement:

Setup:

  1. In FinanceEnterpriseGroup, BODtrigger check box should be checked.
  2. For Outbound BOD, Enable the Service Definition ShipmentService for FSM_ION_SyncShipment_Outbound.
  3. System Configuration Parameter IntegratingApplication: Set the Value to GRC.

Scenario 1:

  1. Create CustomerOrder with CustomerOrderLines and release the CustomerOrder.
  2. Run WarehousePickListPrint
  3. BOD will be triggered and Work Unit will be generated.

Scenario 2:

  1. After WarehousePickListPrint is run go to WarehouseShipment
  2. Right click the record and select Finish, then again right click and select Release.
  3. Run OrderEntryDailyShipmentJournal
  4. BOD will be triggered and Work Unit will be generated.

Verify the Result:

  • When IntegratingApplication = "GRC", the above scenarios are executed, SyncShipment_Out bod should be triggered for CustomerOrder.

JT-1428931

Add New Elements for Lcl Tax Report Bod for Country Mexico

Changes done for SyncLCLTaxReport bod for Mexico.

Program/Business class/Process affected:

Files Changed: FSM_ION_SyncLCLTaxReport.lpd

New Required Setup: No

New Variable Added in JSON: No

New IPA Changes:

  • In start node added new variables: VStateProvinance, TaxSummaryCXML, TaxCodeArray, TaxTransCTaxAmt, TaxTransCTaxAmtTotal, ReturnsCount, TaxTransCTaxableAmt, TaxTransCTaxableAmtTotal, InvoiceReportableAmtTotal, InvoiceReportableAmt.
  • Added conditions for tax type and Invoice type credit in Assign8300.
  • Added code for InvoiceReportableAmtTotal in Assign8910.
  • Constructed Credit Invoice type XML in Assign6130 node.

Integration Specific: Local.ly Integration for MX Country

Use these steps to test this enhancement:

Setup:

  1. Enable the service TaxReportService for FSM_ION_SyncLCLTaxReport _Out.lpd
  2. In SystemConfiguration give the value of IntegrationApplication == "Local.ly"

How to Test:

  1. 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.
  2. Run Vat Return Report batch Job. BOD will trigger and Work unit will generate successfully

Verify the result:

  1. SyncLCLTaxReport/DataArea/LCLTaxReport/TaxReportLine/TransactionSummary/Tax/BasisAmount is mapped to TaxTransaction.TransactionTaxableAmount
  2. SyncLCLTaxReport/DataArea/LCLTaxReport/TaxReportLine/TransactionSummary/Tax/TaxAuthorityAmountis mapped to TaxTransaction.TransactionTaxAmount

For withheld:

  1. SyncLCLTaxReport/DataArea/LCLTaxReport/TaxReportLine/TransactionSummary/Tax/BasisAmount is mapped to PayablesInvoiceWithholding. InvoiceReportableAmount
  2. SyncLCLTaxReport/DataArea/LCLTaxReport/TaxReportLine/TransactionSummary/Tax/TaxAuthorityAmountis mapped to PayablesInvoiceWithholding.WithholdingAmount

JT-1429043

Changes for Sync_Invoice_Outbound--Local.ly

SyncInvoice ReceivableInvoice.CertificationNumber changes specific to Local.ly - Argentina.

Program/Business class/Process affected:

File Changed:

  • FSM_ION_SyncInvoice_Outbound.lpd
  • ReceivableInvoiceJSON.txt

New Required Setup: No

New Variable Added in JSON: Yes

ReceivableInvoice.CertificationNumber -->RICertificationNumber

New IPA Changes:

In FSM_ION_SyncInvoice_Outbound IPA flow below changes done:

  • In Startnode: Added one variable. RICertificationNumber_AR
  • In Assign1620 - Added Javascript condition.
  • if ReceivableInvoice.CertificationNumber value with hyphen it should come without hyphen.
  • In Assign4010 and Assign1740: Javascript modified for AlternateDocumentID (BL_CertificationNumber_AR) and DisplayID

Integration Specific: Yes

These changes are specific to Local.ly Integration and Specific to Argentina.

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. ReceivableInvoice create and release.
  2. BOD will trigger and work unit will create.

Verify the Result:

Verify below x-path:

  • InvoiceHeade/AlternateDocumentID-- ReceivableInvoice.CertificationNumber
  • InvoiceHeade/DisplayID-- ReceivableInvoice.CertificationNumber

JT-1429447

SyncInvoice - Addtion of Original BillingInvoice

This enhancement added SyncInvoice OriginalBLInvoice changes specific to Local.ly.

Program/Business class/Process affected:

File Changed: FSM_ION_SyncInvoice_Outbound.lpd

New Required Setup: No

New Variable Added in JSON: No

In FSM_ION_SyncInvoice_Outbound IPA flow below changes done:

  • In Startnode: Added variable. OriginalBLInvoiceNumber,OriginalBLInvoicePrefix,OrigBLInvoiceNumber and OrigBLInvoice
  • In BLinvoice Tranasction Node added OriginalBillingInvoice.InvoiceNumber & OriginalBillingInvoice.InvoicePrefix fields.
  • In Assign8960: Assigned OrigBLInvoiceNumber and OriginalBLInvoicePrefix value.

    Added Javascript, if IntegrationApplication Local.ly and OriginalBillingInvoice.InvoiceNumber >0

    OrigBLInvoice = lawsonCompany + Generic_Delimiter +OriginalBLInvoicePrefix;

    OriginalBLInvoiceNumber =OrigBLInvoice+"0000000"+OrigBLInvoiceNumber;(Zeros based upon condition)

  • In XML_INVHDR added orrection/OriginalDocumentID/ID - x-path

Integration Specific: These changes are specific to Local.ly Integration

Use these steps to test this enhancement:

Create BillingInvoice Record from Invoice or Provide OriginalBillingInvoice.InvoiceNumber OriginalBillingInvoice.InvoicePrefix.

  1. Execute InvoiceAndVerificationReport.
  2. Execute InvoiceAndRegisterPrint
  3. Execute SubSystemUpdate
  4. ReceivableInvoice Record will create in Released state.
  5. BOD will trigger and Work unit will create.

JT-1432864

BillingInvoice - Addtional Fields mapping

This was an enhancement to SyncInvoice CertificationNumber changes specific to Local.ly - Mexico.

Program/Business class/Process affected:

File Changed: FSM_ION_SyncInvoice_Outbound.lpd

New Variable Added in JSON: Yes

ReceivableInvoice.CertificationDate -->RICertificationDate

New IPA Changes:

In FSM_ION_SyncInvoice_Outbound IPA flow below changes done:

  • In Assign4010 and Assign1740: Javascript modified for AlternateDocumentID (BL_CertificationNumber_AR) and DisplayID for Mexico specific to IntegrationApplication Local.ly and Bl Flow and AR Flow.

    BL_CertificationDate_AR (BL Flow : specific to Local.ly and for all countries )

    RICertificationDate (In AR Flow: specific to Local.ly and only for Mexico country)

CertificationNumber will come as it is provided.

Integration Specific:These changes are specific to Local.ly Integration Mexico Country.

Use these steps to test this enhancement:

Setup:

  1. In FinanceEnterpriseGroup, "BODtrigger" checkbox 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 BillingInvoice Record and provide CertificationNumber and CertificationDate release it.
  2. Execute InvoiceAndVerificationReport.

    5.ReceivableInvoice Record will create in Released state.

  3. Execute InvoiceAndRegisterPrint
  4. Execute SubSystemUpdate
  5. BOD will trigger and Work unit will create.

OR

  1. Create ReceivableInvoiceBatch and provide CertificationNumber and CertificationDate release it.
  2. BOD will trigger and Work unit will create.
  3. Verify the Result:

    Verify below x-path:

    • InvoiceHeade/AlternateDocumentID-- CertificationNumber
    • InvoiceHeade/DisplayID-- CertificationNumber
    • Header UserArea properties CertificationDate will come as lcl.StatusDate
    • <Property><NameValue name="lcl.StatusDate" type="DateTimeType">2020-01-31T07:40:12</NameValue></Property>
    • In UserArea

For Billling Flow:BillingInvoice.CertificationNumber

BillingInvoice.CertificationDate

For Receivables Flow:ReceivableInvoice.CertificationNumber

ReceivableInvoice.CertificationDate

JT-1433184

SyncSupplierInvoice - Dummyline to be populated when an Expense is created in AP

This enhancement added InvoiceLine for the BasicInvoice as part of Local.ly Integration.

Program/Business class/Process affected:

  • FSM_ION_SyncSupplierInvoice_Outbound.lpd

New IPA Changes:

In start node added these variables:

  • Line_XML
  • UOM
  • Quantity
  • DHSNCode

Added LineXMl for BasicInvoice passing Distribution and Tax details in that xml.

In Assign4810 node constructed the LineXML for Local.ly integration.

Added HSNSAC Code for India Specific Country.

Use these steps to test this enhancement:

Setup:

In FinanceEnterpriseGroup, select the BODtrigger check box.

Enable ServiceDefinition for .PayablesInvoiceService. Attach FSM_ION_SyncSupplierInvoice_Outbound.lpd

In SystemConfiguration, add Configuration parameter IntegrationType = Local.ly.

Test:

  1. Create PayablesInvoice and release it.
  2. Workunit should be successfully triggered for PayablesInvoiceService
  3. Verify the XMLl ine node should be populate with Tax and distribution details..

JT-1433653

Changes for Sync_SupplierInvoice_Outbound--Local.ly

HSNSAC code needs to be send in DUmmy SupplierInvoice line when the CountryCode is "IN"

Program/Business class/Process affected:

New IPA Changes:

In start node added these variables

DHSNCode

Added LineXMl for BasicInvoice passing Distribution and Tax details in that xml.

In Assign4810 node constructed the LineXML for Local.ly integration.

Adding HSNSAC Code for India Specific Country

Integration Specific: Yes. These changes are as part of Local.ly Integration.

Use these steps to test this enhancement:

Setup:

In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.

Enable ServiceDefinition for "PayablesInvoiceService" attach FSM_ION_SyncSupplierInvoice_Outbound.lpd

In SystemConfiguration add Configuration parameter IntegrationType = "Local.ly"

How to test:

  1. Create PayablesInvoice
  2. Add HSNSAC code in Distribution level and release the Invoice.
  3. Workunit should be successfully triggered for "PayablesInvoiceService"
  4. Verify the XML. BOD will trigger and work unit will generate successfully for FSM_ION_SyncSupplierInvoice_Outbound.
  5. Verify the XML Line node should be populate HSNSAC code.

JT-1437573

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

Use these steps to test this enhancement:

  1. Select Supply Management > Shared Processes > Sample Document Template.
  2. Open the 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*.
  5. Three records updated with attachment:
    • FSM_ION_CONTENTPACK_ST
    • FSM_ION_CONTENT_PACK_IONCE_IMS_ST
    • FSM_ION_CONTENT_PACK_IONCE_ST

JT-1438601

SyncInvoice - Display ID changes for MX and Other countries

SyncInvoice - Display ID changes for Mexico and other countries.

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 changes done: In Assign 4010 : Modified Javascript for DisplayId chnages.

Integration Specific: Yes

These changes are specific to Local.ly Integration Mexico.

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 BillingInvoice and Release.
  2. Execute InvoiceAndVerificationReport.
  3. Execute InvoiceAndRegisterPrint
  4. Execute SubSystemUpdate
  5. ReceivableInvoice Record will create in Released state.
  6. BOD will trigger and Work unit will create.

Verify the Result:

  1. Verify the x-path Invoice/InvoiceHeader/DisplayID for Local.ly Mexico or other countries--> DisplayID value should be ReceivableInvoice.

JT-1440433