Localization Services CU69

This section contains enhancements in Infor CloudSuite Financials for 11.0.69.0.

SyncInvoice BOD PaymentForm and USO-CFDI fields mapping

Changes for Sync_Invoice_Outbound -PaymentForm and USO-CFDI fields mapping- for Local.ly - Mexico.

Program/Business class/Process affected:

Files changed:

  • FSM_ION_SyncInvoice_Outbound.lpd

IPA changes:

  • In FSM_ION_SyncInvoice_Outbound, IPA flow changes:
    • Start node added new variables: BLLetterOfCredit, BLMXSATUseCode, BL_LetterOfCredit, and BL_LetterOfCreditValue
    • In BLinvoice Transaction node, added LetterOfCredit field.
    • In Assign8960 node, assigned BLinvoice_LetterOfCredit value to LetterOfCredit.
    • In Assign4010, if SystemID = BL, IntegrationApplication = Local.ly, and Country = Mexico: If LetterOfCredit is blank, then BLLetterOfCredit,BLMXSATUseCode is blank. If LetterOfCredit has a value, then BLLetterOfCredit is Billinginvoice.LetterOfCredit value before the "-" and BLMXSATUseCode is Billinginvoice.LetterOfCredit value after the "-".
      Note: Specify the BillingInvoice.LetterOfCredit value by using a hyphen. For example, 101-AAA.
    • In Assign1740, if BillingInvoice.certificationDate is not specified, the value will be blank. If BillingInvoice.certificationDate is specified, the value will be BillingInvoice.certificationDate with a Timestamp format. If BL_CertificationDate_AR = 00000000, then BL_CertificationDate_AR = "". Otherwise, BL_CertificationDate_AR = (convertDateTime(BL_CertificationDate_AR)) +"T" + Hours+":"+Minutes+":"+Seconds+"Z".

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the BODtrigger check box is selected.
  2. Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.
  3. Select the Service Definition and enable ReceivableInvoiceService for FSM_ION_SyncInvoice_Outbound.lpd Processes.
  4. Create a BillingInvoice and Release it.
  5. Run InvoiceAndVerificationReport.
  6. Run InvoiceAndRegisterPrint.
  7. Run SubSystemUpdate.
  8. A ReceivableInvoice record will be created in a Released state.
  9. A BOD will be triggered and a work unit will be generated.
  10. Verify this x-path:

    Invoiceheader/Paymentmethodcode = Billinginvoice.LetterOfCredit before the "-" details.

    InvoiceHeader/UserArea/Property/NameValue('lcl.MX.SATUseCode') = Billinginvoice.LetterOfCredit(After the "-" details)

    For example, BillingInvoice.LetterOfCredit is "101-AAA"

    Invoiceheader/Paymentmethodcode --> 101 InvoiceHeader/UserArea/Property/NameValue('lcl.MX.SATUseCode') = AAA

    InvoiceHeader/UserArea/Property/NameValue('lcl.StatusDate') = BillingInvoice.CertificationDate value with timestamp

    If the BillingInvoice.CertificationDate value is specified, an x-path will be generated with the value. Otherwise, there is no x-path for the Localization Services integration.

JT-1407800

Add new elements at user area in SSJE BOD for FEC

Added Systemcode to userarea in Sync.SSJE Outbound BOD for FEC for Local.ly Integration.

Program/Business class/Process affected:

Files changed:

  • FSM_ION_SyncPayablesTransaction_Outbound.lpd

IPA changes:

  • In the GLGLC_VAR node, added SystemCode to Header Userarea.

  • In the GLTRN_VAR node, added SystemCode to Line level UserArea.

Use these steps to test the enhancement:

  1. Enable service definition GLJournalControlService for Process FSM_ION_SyncSourceSystemJournalEntry.lpd.
  2. For 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 a released state. Quick Post them.
    6. A BOD will be triggered. Verify the XML Line level Userarea for Customer details.
  3. For AR:
    1. Create receivableinvoicebatch and release it.
    2. Journalize the distributions created. A journal will be created in released state.
    3. Run Quick Post. A record will be moved to a Posted state.
    4. A BOD will be triggered. Verify the XML line level userarea for Customer details.
  4. For AP:
    1. Create and release a PayablesInvoice with distributions.
    2. Journalize the distributions. A journal will be created in a Released state.
    3. Run Quick Post. The record will be moved to the Posted tab.
    4. A work unit will be created. Verify the XML in the header and line level userarea for SystemCode Details.

JT-1407101

Source Document Date mapping to the General Ledger Transaction Date enhanced

Changed element SourceDocumentDate mapping to the GeneralledgerTransaction.TransactionDate

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncSourceSystemJournalEntry_Out

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    • GLTRN_VAR

    • If IntegrationType is "Local.ly" then GeneralLedgerTransaction.TransactionDate is populated otherwise GeneralLedgerJournalControl.LastUpdateDateTime

  5. Integration Specific: Yes

    • Local.ly

Use these steps to test the enhancement:

  1. Setup: Provide the setup to execute the flow/changes.
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. For Outbound BOD, Enable the Service Definition "GLJournalControlService" for Process FSM_ION_SyncSourceSystemJournalEntry_Out.
  2. How to Test:
    1. When a Journal is Posted then FSM_ION_SyncSourceSystemJournalEntry_Out will be triggered.
    2. If Integration type is "Local.ly" then GeneralLedgerTransaction.TransactionDate will be populated otherwise GeneralLedgerJournalControl.LastUpdateDateTime will be populated in Path JournalEntryLine/SourceDocumentReference/DocumentDateTime

JT-1404514

Changes for Sync_ReceivableTracker_Outbound

Changes for Sync_ReceivableTracker_Outbound

Adding ReportingAmount fields in ReceivableTracker.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncReceivableTracker_Outbound.lpd

  2. Changes:

    • Add two variables in start node:

      • TotalReportAmount

      • AssignedReportAmount.

    • Added two new transaction nodes to get ReportCurrency from FEG and to get ReportCurrencyrate from ReceivableGLDistribution.

    • Derived the values for both AssignedReport Amount and passed in line xml

JT-1418336

Changes for Sync_PayableTracker_Outbound

Added PayableTrackerHeader/TotalReportAmount and PayableTrackerLine/AssignedReportAmount nodes to SyncPayableTracker outbound BOD.

Program/Business class/Process affected:

  1. Files Changed:

    FSM_ION_SyncPayableTracker_Out.lpd

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes in Nodes:

    • PayablesInvoice

    • Assign3280

    • Assign4060

    • PayTrackerLine

    • PayableTracker

    • PayableTrackerAdjL

    • PayableTrackerAdj

    • Assign3140

  5. Integration Specific: No

Use these steps to test the enhancement:

  1. Setup: Provide the setup to execute the flow/changes.
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. Enable the Service Definition "PayableTrackerService" for Processes "FSM_ION_SyncPayableTracker_Out".
  2. How to Test:

    Scenario1:

    1. Create a PayablesInvoice and Release it, then perform Manual payment.
    2. Work unit will be triggered.
  3. Verify the Result:

    • Check these Xpaths:

      • PayableTrackerHeader/TotalReportAmount

      • PayableTrackerHeader/TotalReportAmount/@currencyID

      • PayableTrackerLine/AssignedReportAmount

      • PayableTrackerLine/AssignedReportAmount/@currencyID

JT-1417197

Changes for Sync_SupplierInvoice_Outbound-- Local.ly

Changes for Sync_SupplierInvoice_Outbound-- Local.ly

Changed the existing path as part of local.ly integration

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncSupplierInvoice_Outbound.lpd

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. IPA Changes:
    1. Two new variables added in start node

      • Locally_DocID_schemeName_CU

      • LocallyCertificationNumber_CU

    2. In Assign4810 node derived the fields for Locally_DocID_schemeName_CU, LocallyCertificationNumber_CU based on Integration Application Local.ly and country is "AR" or "MX".

      Derived Display ID based on integration and derived values for ExtendedPreTaxAmount when the integration application is "Local.ly"

    3. In Main XML added one more series of AlternateDocumentID and added DisplayID in the DisplayID path.
  5. Integration Specific: Yes

    • These changes are related to Local.ly integration

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. In Service Definition enable the service for "PayablesInvoiceService" and attach FSM_ION_SyncSupplierInvoice_Outbound
    3. In SystemConfiguration add IntegrationApplication = "Local.ly"
    4. In AccountingEntity add the Country code as "AR" or "MX"
  2. How to test:
    1. Create PurchaseOrder and Release it.
    2. Create PurchaseOrderReceipt and Release it.
    3. Create PayablesInvoice for that PurchaseOrder(matchInvoice) enter the certification number and release it.
    4. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SupplierInvoive_Out BOD (PayablesInvoiceService).
  3. Verify Result:
    1. In XML, this path should be populated with values

      • Header XML:

        • <AlternateDocumentID>

        • <ID accountingEntity="A100@@101" schemeName="Supplier" variationID="1">MINV_8</ID>

        • </AlternateDocumentID>

        • <AlternateDocumentID>

        • <ID accountingEntity="A100@@101" schemeName="lcl.Government" variationID="1">78</ID>

        • </AlternateDocumentID>

        • <DisplayID>8</DisplayID>

        • <ExtendedPretaxAmount currencyID="USD">1000.000</ExtendedPretaxAmount>

        • <SubTotalAmount currencyID="USD">1000.000</SubTotalAmount>

    2. Test with disabling Local.ly flag the display ID should be Invoice and ExtendedPreTaxAmount and SubTotalAmount should not be populated.

JT-1416336

ProcessInvoice Inbound BOD Enhancement for Local.ly Integration

Added new scenario in ProcessInvoice_Inbound BOD for Local.ly to update the CertificationNumber in BillingInvoice.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_ProcessInvoice_Inbound.lpd

  2. New Required Setup: Yes

    • IntegrationApplication should be "Local.ly" in System Configuration.

Use these steps to test the enhancement:

  1. Setup:

    • Create channels for Process.Invoice_Inbound BOD.

  2. How to Test:
    1. Create Billing Invoice with Unreleased state and Country code should be "MX".
    2. Send valid XML and work unit should create with out any errors.
  3. Verify the Result:
    1. Billing Invoice record should update with CertificationNumber.
    2. Workunit should create without any errors.

JT-1415231

Added new elements and mapped accordingly for Lcl Tax Report BOD for country Mexico

Added new elements in Sync.LCLTaxReport bod - Local.ly specific to Mexico Country.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncLCLTaxReport _Out.lpd

  2. New Required Setup:No
  3. New Variable Added in JSON:No
  4. New IPA Changes:

    • In "start" node added new variables TaxRateArray,TransTypeArray.

    • In "Vendor" LMRK query added new fields VendorAddress.Country,VendorAddress.CountryName.

    • Added new LMRK query "PayInv" to get PaidInvoices after "MX_TaxTrans" query.

    • In "Assign8300" node added a condition for taxrate and taxtype based on vendor country.

    • In "Assign6130" changed the SupplierpartyXML changed vendorcountry from vendorContact.VendorAddess.Country to Vendor.VendorAddress.Country and VendorCountryname from Vendorcontact.VendorAddress.CountryName to Vendor.VendorAddress.CountryName.

    • In TaxTransactionSummary XML replaced the value in XPath TransactionSummary/Type from Import to TransTypeArray and in Xpath TransactionSummary/Tax/Calculation/RateNumeric to TaxRateArray.

  5. Integration Specific:Local.ly Integration for Mexico Country

Use these steps to test the enhancement:

  1. Setup:
    1. Enable the service "TaxReportService" for FSM_ION_SyncLCLTaxReport _Out.lpd.
    2. In SystemConfiguration give the value of IntegrationApplication == "Local.ly"
  2. How to Test:
    1. Create a Payablesinvoice with tax and release it. Do the payment for the Invoice by performing actions:
      • Cash Requirements
      • Electronic Payment Creations
      • PaymentClose
    2. Run Vat Return Report batch Job. BOD will trigger and Work unit will generate successfully
  3. Verify the Result:

    • Xpath LCLTaxReport/TaxReportLine/TransactionSummary.

JT-1414864

Handled Certification Date not entered scenario in SyncSupplierInvoice Out BOD for Local.ly

Handled Certification Date not entered scenario in SyncSupplierInvoice Out BOD for Local.ly.

Program/Business class/Process affected:

  1. File Changed:

    • FSM_ION_SyncSupplierInvoice_Outbound.lpd

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    • In FSM_ION_SyncSupplierInvoice_Outbound, IPA flow changes:

      • In Assign4810 node, the java script code is modified.

      • If PayablesInvoice.certificationDate is not specified, value will come as blank.

      • If PayablesInvoice.certificationDate is specified, value will come as PayablesInvoice.certificationDate with Timestamp format.

      • If (CertificationDate == "00000000")-->Locally_StatusDate = "";

      • Locally_StatusDate = (convertDateTime(CertificationDate)) +"T" + Hours+":"+Minutes+":"+Seconds+"Z";

  5. Integration Specific:

    These changes specific to Local.ly Integration

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. Enable the Service Definition and Processes for FSM_ION_SyncSupplierInvoice_Outbound IPA flow.

      Go to Service Definition and Enable "PayablesInvoiceService" for "FSM_ION_SyncSupplierInvoice_Outbound.lpd" Processes.

  2. How to Test:
    1. Create PayablesInvoice and Release it. .
    2. BOD will trigger and Work unit will generate.
  3. Verify the Result:
    1. Verify this x-path:

      SupplierInvoiceHeader/UserArea/Property/NameValue('lcl.StatusDate')-->PayablesInvoice.CertificationDate value with timestamp

    2. If PayablesInvoice.CertificationDate value entered - x-path will come with value otherwise no x-path.(For Local.ly Integration)

JT-1409538

New triggers for Receivable Tracker BOD

New triggers for Receivable Tracker BOD

Added new Trigger when Invoice is Apply to the payment thru CashPayment

Program/Business class/Process affected:

  • ReceivablePayment.busclass

  • ReceivableApplication.busclass

  • NationalAccountTransaction.busclass

Use these steps to test the enhancement:

  1. Setup:
    1. Enable BOD trigger in FEG
    2. Enable Service Definition for "ReceivableTrackerService" and attach FSM_ION_SyncReceivableTracker BOD
  2. How to test:
    1. Create a ReceivableInvoice and release it
    2. Create ReceivablePayment and release it.
    3. Apply Payment to the Invoice thru CashPayment.
    4. Workunit should be created successfully for ReceivableTrackerService.
    5. Go to ReviewApplications and delete the Application.
    6. Workunit should be created for ReceivableTracker service.

JT-1409524

Receivable Tracker BOD - PaymentForm addition

Receivable Tracker BOD - PaymentForm addition

Add PaymentMethodCode in ReceivableTracker BOD for Local.ly Integration Mexico country.

Program/Business class/Process affected:

  • FSM_ION_SyncReceivableTracker_Outbound.lpd

    • Added "PaymentMethodCode" Variable in Start Node.

    • Added ReceivablePaymentHeader Transaction to get Reference value.

    • In Assign9560 chnaged to the java script for Country mexico added PaymentMethodCode.

Use these steps to test the enhancement:

  1. Enable the ServiceDefinition for "ReceivableTrackerService" and attach FSM_ION_SyncReceivableTracker.lpd.
  2. Create ReceivablePaymentHeader with passing reference value.
  3. Release ReceivablePaymentHeader.
  4. Bod will Trigger Workunit will be created successfully for ReceivableTracker_Outbound BOD.
  5. Verify Result:

    In XML verify this path: ReceivableTrackerHeader/PaymentMethodCode

JT-1407805

NativeLPL: Added elements to X-Path and changed mapping sheet SyncCustomerPartyMaster_Out

Added new elements to Sync.CustomerPartyMaster_Out.lpd

Program/Business class/Process affected:

  1. Files Changed:

    • UserTemplate.csv

    • CompanyCustomer.busclass

  2. New Required Setup:No
  3. New Variable Added in JSON:No
  4. New Changes:

    • In CompanyCustomer.buclass added derivedfields DerivedLastupdateBy,DerivedCCustomerUpdateTimeStamp,DerivedCCustomerUpdateTimeStamp.

    • In XML Template of CompanyCustomer Mapped DerivedCCustomerUpdateTimeStamp to CustomerPartyMaster/LastModificationDateTime and DerivedLastupdateBy to CustomerPartyMaster/LastModificationPerson/IDs/ID.

  5. Integration Specific:No

Use these steps to test the enhancement:

  1. Setup:

    • Enable the Sync.CustomerPartyMaster in FSMBODConfiguration.

  2. How to Test:
    1. Update a CompanyCustomer and save it.
    2. BOD will trigger and check the generated XML in IONOut.busclass
  3. Verify the Result:

    • Mapped DerivedCCustomerUpdateTimeStamp to CustomerPartyMaster/LastModificationDateTime and DerivedLastupdateBy to CustomerPartyMaster/LastModificationPerson/IDs/ID.

JT-1409207

Added elements to X-Path and changed mapping sheet SyncCustomerPartyMaster_Out

Added new elements to Sync.CustomerPartyMaster_Out.lpd

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncCustomerPartyMaster_Out.lpd

  2. New Required Setup: No
  3. New Variable Added in JSON: Yes

    • Added CompanyCustomer.UpdateStamp.Actor to LastUpdateActor.

    • Added CompanyCustomer.UpdateStamp.TimeStamp to LastUpdateStamp.

  4. New IPA Changes:

    • In "Assign5830" added javascript to covert LastUpdateStamp to YearMonthDate format with separator.

    • In "XML_Customer" node Mapped CCUpdateStamp to CustomerPartyMaster/LastModificationDateTime and LastUpdateActor to CustomerPartyMaster/LastModificationPerson/IDs/ID.

  5. Integration Specific:No

Use these steps to test the enhancement:

  1. Setup:

    • Enable the service "CompanyCustomerService" for FSM_ION_SyncCustomerPartyMaster_Out.lpd

  2. How to Test:
    1. Update 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).
  3. Verify the Result:

    • Mapped CCUpdateStamp to CustomerPartyMaster/LastModificationDateTime and LastUpdateActor to CustomerPartyMaster/LastModificationPerson/IDs/ID.

JT-1409205

Added fields in SyncContract BOD and modified mapping

Added new fields in XML and Updated mapping sheet.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncContract_Outbound

    • Contract_Out.xlsx

    • FSM_Contract_Outbound_Template.xls

  2. New Required Setup: No
  3. New Variable Added in JSON:

    • Two variables are added in JSON

      • Contract_UpdateStamp

      • Contract_CreateStamp

  4. New IPA Changes:

    • Added new variable "ContractLineNumber" in Start node

    • Added new Javascript for converting Contract_UpdateStamp and Contract_CreateStamp into Date Formats

    • Fetched 3 varibles "ItemDescription & LifetimeMaximumQuantity & ContractLine" from Landmark Transaction node "ContractLine"

    • Passed Contract_CreateStamp value to Contract/ContractHeader/DocumentDateTime in Header XML

    • Passed Contract_UpdateStamp value to Contract/ContractHeader/LastModificationDateTime in Header XML

    • Passed ItemDescription value to Contract/ContractSchedule/ContractPrice/Item/Description in Line XML

    • Passed service_item value to Contract/ContractSchedule/ContractPrice/Item/ServiceIndicator in Line XML

    • Passed LifetimeMaximumQuantity value to Contract/ContractSchedule/ContractPrice/TargetQuantity in Line XML

    • Passed ContractLineNumber value to Contract/ContractSchedule@Sequence in Line XML

  5. Integration Specific:

    • These changes are related to CSF-GRC Integration.

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. For Outbound BOD, Enable the "ContractService" Service Definition and "FSM_ION_SyncContract_Outbound" Process.
  2. How to Test:
    1. Create Contract and Release it or Activate Contract or Close Contract
    2. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncContract_Outbound BOD.
  3. Verify the Result:
    1. FSM_ION_SyncContract_Outbound BOD should be triggered in the Work Units without errors.
    2. Check the X-Paths in the generated XML:

      • Contract/ContractHeader/DocumentDateTime

      • Contract/ContractHeader/LastModificationDateTime

      • Contract/ContractHeader/Description

      • Contract/ContractSchedule/ContractPrice/Item/Description

      • Contract/ContractSchedule/ContractPrice/Item/ServiceIndicator

      • Contract/ContractSchedule/ContractPrice/TargetQuantity

      • Contract/ContractSchedule@Sequence

    3. Check the X-Paths in the MappingSheet Contract_Out.xlsx

      • Contract header:

        • Contract/ContractHeader/LastModificationDateTime row no: 19

        • Contract/ContractHeader/DocumentDateTime row no: 27

        • Contract/ContractHeader/SupplierParty/PartyIDs/ID row no: 642

      • Contract schedule:

        • Contract/ContractSchedule row no: 2

        • Contract/ContractSchedule/ContractPrice/Item/ServiceIndicator row no: 24

        • Contract/ContractSchedule/ContractPrice/Item/Description row no: 25

        • Contract/ContractSchedule/ContractPrice/TargetQuantity row no: 227

JT-1409182

NativeLPL: Added fields in SyncContract BOD and modified mapping

Add new fields in SyncContract BOD and modify mapping.

Program/Business class/Process affected:

  • Contract.busclass,

  • ContractLine.busclass

Use these steps to test the enhancement:

  1. Setup:

    • Enable the Sync.Contract_Outbound in FSMBODConfiguration

  2. How to test:
    1. Create Contract and Release it or Activate Contract or Close Contract
    2. Check the XML generated in IONOutboxQueue
  3. Verify the result:

    • Check the X-Paths in the generated XML:

      • Contract/ContractHeader/DocumentDateTime

      • Contract/ContractHeader/LastModificationDateTime

      • Contract/ContractHeader/Description

      • Contract/ContractSchedule/ContractPrice/Item/Description

      • Contract/ContractSchedule/ContractPrice/Item/ServiceIndicator

      • Contract/ContractSchedule/ContractPrice/TargetQuantity

      • Contract/ContractSchedule@Sequence

JT-1409181

Mapping of elements in Sync.RequisitionOut BOD for CSF-GRC PI(2)

Added new element in RequisitionHeader in SyncRequisition_Out BOD for CSF-GRC PI Integration.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncRequisition_Outbound.

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    • In FSM_ION_SyncRequisition_Outbound IPA flow changes:

      • Passed Requisition.Requester value in Approvers/SequencedApprover/ApproverPersonReference/IDs/ID in the XML.

  5. Integration Specific:

    • These changes are related to CSF-GRC Integration.

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. For Outbound BOD, Enable the "RequisitionService" service definition for FSM_ION_SyncRequisition_Outbound.
  2. How to Test:
    1. Create Requisition and RequisitionLine and release it.
    2. BOD will trigger and work unit will generate successfully without any error for FSM_ION_SyncRequisition_Outbound BOD (RequisitionService).
  3. Verify the Result:

    • Approvers/SequencedApprover/ApproverPersonReference/IDs/ID

JT-1409177

Assigning Journal References to SSJE BODs, Protocol Context Number data is missing in native lpl BOD of SSJE

Assigning Journal References to SSJE BODs,Protocol Context Number data is missing in Native lpl Bod of SSJE.

Program/Business class/Process affected:

  • GeneralLedgerJournalControlRef.busclass

Use these steps to test the enhancement:

  1. Select Financials > Global Ledger > Processing > Reporting Basis > Reporting Basis then select ReportingBasis and Year.
  2. Now Perform AssignJournalReferenceNumber batch job then Sync.SourceSystemJournalEntry outbound BOD will be triggered without any errors.
  3. Verify the Result:

    • Check this path for JournalReferenceNumber:: SyncSourceSystemJournalEntry/DataArea/SourceSystemJournalEntry/JournalEntryHeader/BaseJournalEntryHeader/ProtocolNumberText

JT-1409175

NativeLPL: Added fields in XML and updated mapping sheet

Adding new fields in XML and Updating the mapping sheet

Program/Business class/Process affected:

  • PurchaseOrderReceiptLine.busclass

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. For Outbound BOD, Enable the Sync.ReceiveDelivery_Outbound BOD trigger in FSMBODConfiguration.
  2. How to Test:
    1. Create PurchaseOrder and Release it.
    2. Create PurchaseOrderReceipt and Release it.
    3. BOD will trigger and IONOutboxQueue will generate successfully without any error for FSM_ION_SyncReceiveDelivery_Out BOD.
  3. Verify the Result:
    1. FSM_ION_SyncReceiveDelivery_Outbound BOD should be triggered without errors.
    2. Check these X-Paths:

      • ReceiveDelivery/ReceiveDeliveryHeader/ReturnFromShipToParty/PartyIDs/ID

      • ReceiveDelivery/ReceiveDeliveryItem/ServiceIndicator

      • ReceiveDelivery/ReceiveDeliveryItem/ShippedQuantity

JT-1408084

Added fields in XML and updated mapping sheet

Added new fields in XML and Updated mapping sheet.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncReceiveDelivery_Outbound

    • ReceiveDelivery_Out.xlsx

    • FSM_ReceiveDelivery_Outbound_Template.xls

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    • Added new variable "ServiceIndicator" in Start node

    • Added new Javascript for defining the ServiceIndicator variable

      • If (PurchaseOrderReceiptLine.ItemType == "Service"), then ServiceIndicator = "true" If not, ServiceIndicator = "false"

    • Parsed PurchaseFromLocation value in ReceiveDelivery/ReceiveDeliveryHeader/ReturnFromShipToParty/PartyIDs/ID in Header XML

    • Parsed ServiceIndicator value in ReceiveDelivery/ReceiveDeliveryItem/ServiceIndicator in Line XML

    • Parsed PurchaseOrderReceiptLine.EnteredReceivedQuantity value in ReceiveDelivery/ReceiveDeliveryItem/ShippedQuantity in Line XML

  5. Integration Specific:

    • These changes are related to CSF-GRC Integration.

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. For Outbound BOD, Enable the "PurchaseOrderReceiptService" Service Definition and "FSM_ION_SyncReceiveDelivery_Outbound" Process.
  2. How to Test:
    1. Create PurchaseOrder and Release it.
    2. Create PurchaseOrderReceipt and Release it.
    3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncReceiveDelivery_Out BOD.
  3. Verify the Result: FSM_ION_SyncReceiveDelivery_Outbound BOD should be triggered in the Work Units without errors.
    1. Check these X-Paths:

      • ReceiveDelivery/ReceiveDeliveryHeader/ReturnFromShipToParty/PartyIDs/ID

      • ReceiveDelivery/ReceiveDeliveryItem/ServiceIndicator

      • ReceiveDelivery/ReceiveDeliveryItem/ShippedQuantity

JT-1408083

Updated Sync.CaptureDocument process flow to store vendor name in DII

Store the vendor name from Sync.CaptureDocument BOD to DocumentInterafaceInvoice.VendorName

Program/Business class/Process affected:

  • FSM_ION_SyncCaptureDocument_Inbound.lpd

Use these steps to test the enhancement:

  1. Send a Sync.CaptureDocument BOD with vendor name and no vendor number to CSF.
  2. Check the created record in document interface invoice in Payables menu.

JT-1405290

Mapping of Elements in SyncRequisition_Out BOD for CSF-GRC PI Integration

Added new elements in RequisitionHeader and RequisitionLine in SyncRequisition_Out BOD for CSF-GRC PI Integration.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncRequisition_Outbound.

    • Requisition Business Class

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    • - In FSM_ION_SyncRequisition_Outbound IPA flow changes:

      • Passed ApprovalValue as variable in Trigger Code in Requisition BusinessClass.

      • This variable is added in start node: TransactionCurrencyCode

      • Passed TransactionCurrencyCode in "RequisitionLine" query. Assigned the value to TransactionCurrencyCode variable in LineVars Assign node.

  5. Integration Specific:

    • These changes are related to CSF-GRC Integration.

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. For Outbound BOD, Enable the "RequisitionService" service definition for FSM_ION_SyncRequisition_Outbound.
  2. How to Test:
    1. Create Requisition and RequisitionLine and release it.
    2. BOD will trigger and work unit will generate successfully without any error for FSM_ION_SyncRequisition_Outbound BOD (RequisitionService).
  3. Verify the Result:

    • RequisitionHeader/ExtendedReportAmount

    • RequisitionLine/ExtendedReportAmount

JT-1405101

Changes to SyncPurchaseOrder_Out BOD and Mapping

Added new elements in FSM_ION_SyncPurchaseOrder_Outbound BOD for CSF-GRC PI Integration.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncPurchaseOrder_Outbound.

    • PurchaseOrder Business Class

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    • In FSM_ION_SyncPurchaseOrder_Outbound IPA flow changes:

      • Passed Company.ProcurementGroup as variable in Trigger Code in PurchaseOrder BusinessClass.

      • These variables added in start node:

        • ContractLine

        • Contract

      • Passed Contract and ContractLine in "LMTxn4560" query.

      • Added respective code in PLI_FIELDS Assign node:

        • If LMTxn4560_Contract > 0 then ContractID = ProcurementGroup + Generic_Delimiter + LMTxn4560_Contract

        • If LMTxn4560_ContractLine > 0 then ContractLine = LMTxn4560_ContractLine

      • e. Added new Xpaths :

        • PurchaseOrderHeader/ExtendedReportAmount

        • PurchaseOrderLine/ContractReference/DocumentID/ID

        • PurchaseOrderLine/ContractReference/LineNumber

  5. Integration Specific:

    • These changes are related to CSF-GRC Integration.

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. For Outbound BOD, enable the "PurchaseOrderService" service definition for FSM_ION_SyncPurchaseOrder_Outbound.
  2. How to Test:
    1. Create PurchaseOrder and PurchaseOrderLine, Pass Contract value in PurchaseOrderLine and release it.
    2. BOD will trigger and work unit will generate successfully without any error for FSM_ION_SyncPurchaseOrder_Outbound BOD (PurchaseOrderService).
  3. Verify the Result:

    • PurchaseOrderHeader/ExtendedReportAmount

    • PurchaseOrderLine/ContractReference/DocumentID/ID

    • PurchaseOrderLine/ContractReference/LineNumber

JT-1405099

Native LPL: changes to SyncItemMaster_Out and Mapping sheet

Added new elements to Sync.ItemMaster_Out.lpd

Program/Business class/Process affected:

  1. Files Changed:

    • UserTemplate.csv

  2. New Required Setup:No
  3. New Variable Added in JSON:No
  4. New Changes:

    • In XML Template of ItemMaster Mapped Variationid to ItemMaster/ItemMasterHeader/ItemId/RevisionID and ItemMaster/ItemMasterHeader/ServiceIndicator is set to false.

  5. Integration Specific: No

Use these steps to test the enhancement:

  1. Setup:

    • Enable Sync.ItemMaster in FSMBODConfiguration.

  2. How to Test:
    1. Create an Item and save it.
    2. BOD will trigger and check the generated XML in IONOut.busclass
  3. Verify the Result:

    • Mapped Variationid to ItemMaster/ItemMasterHeader/ItemId/RevisionID and ItemMaster/ItemMasterHeader/ServiceIndicator is set to false.

JT-1405093

Changes to SyncItemMaster_Out and Mapping sheet

Added new elements to Sync.ItemMaster_Out.lpd

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncItemMaster_Out.lpd

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    • In "XML_ITL" node Mapped Variationid to ItemMaster/ItemMasterHeader/ItemId/RevisionID and ItemMaster/ItemMasterHeader/ServiceIndicator is set to false.

  5. Integration Specific: No

Use these steps to test the enhancement:

  1. Setup:

    • Enable the service "ItemService" for FSM_ION_SyncItemMaster_Out.lpd

  2. How to Test:
    1. Create an Item and save it.
    2. 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 Variationid to ItemMaster/ItemMasterHeader/ItemId/RevisionID and ItemMaster/ItemMasterHeader/ServiceIndicator is set to false.

JT-1405092

NativeLPL: SyncPayables Transaction_Out - Mapping Elements for GRC_PI Integration

Added new elements in Sync.PayablesTransaction_Out bod as part of CSF-GRC Integration.

Program/Business class/Process affected:

  • PayablesInvoicePayment.busclass

  • PayablesinvoiceDetail.busclass

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. In FSMBODConfiguration, Sync.PayableTransaction BOD must be enabled
  2. How to Test:
    1. Create PurchaseOrder and Release it.
    2. Create PurchaseOrderReceipt and Release it.
    3. Create PayablesInvoice for that PurchaseOrder(matchInvoice) eneter the terms code and Release it.
    4. Run PerformCashRequirements
    5. Run ElectronicPaymentCreation Batch job
    6. Run PaymentClose, check the generated reports.
    7. BOD will trigger.
  3. Verify the Result. These XML paths should be populated with values:

    • Header XML

      • PayableTransaction/PayableTransactionHeader/Description

      • PayableTransaction/PayableTransactionHeader/RemitToParty/Contact/Name

      • PayableTransaction/PayableTransactionHeader/PaymentMethodCode

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/ID

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/DueDateTime

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Discount/EffectiveDateTime

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Description

    • Line XML

      • PayableTransaction/PayableTransactionLine/LineNumber

      • PayableTransaction/PayableTransactionLine/Item/ItemID/ID

      • PayableTransaction/PayableTransactionLine/Quantity

      • PayableTransaction/PayableTransactionLine/Quantity@unitcode

      • PayableTransaction/PayableTransactionLine/ExtendedAmount

      • PayableTransaction/PayableTransactionLine/ExtendedAmount@currencyID

      • PayableTransaction/PayableTransactionLine/ExtendedReportAmount

      • PayableTransaction/PayableTransactionLine/ExtendedReportAmount@currencyID

JT-1405089

Changes for FSM_ION_SyncInvoice_outbound-- IPA Flow

Changes for Sync_Invoice_Outbound -InvoiceLine/Item/Classification/Codes/Code must be without "-" for Mexico.

Program/Business class/Process affected:

  1. File Changed:

    • FSM_ION_SyncInvoice_Outbound.lpd

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    • In FSM_ION_SyncInvoice_Outbound IPA flow changes:

      • Assign4710 - Javasript modified.

      • Here Changed the condition from Customer Country to AccountingEntity -->PostalAddress->Country.

      • If the Country is Mexico , then Commodity Code should come as without Dashes("-").

  5. Integration Specific: No

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.
    3. Go to Service Definition and Enable "ReceivableInvoiceService" for "FSM_ION_SyncInvoice_Outbound.lpd" Processes.
  2. How to Test:
    1. Create BillingInvoice and Release it. .
    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 generate.
  3. Verify the Result:

    • Verify this x-path: InvoiceLine/Item/Classification/Codes/Code

JT-1405082

SyncPayables Transaction_Out - Mapping Elements for GRC_PI Integration

Added new elements in Sync.PayablesTransaction_Out bod as part of CSF-GRC Integration.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncPayablesTransaction_Outbound.lpd

    • PayablesInvoicePayment. busclass

  2. New Required Setup: No
  3. New Variable Added in JSON: Yes

    • PayablesInvoice.Description as PInvDescription

    • VendorLocationRel.VendorName as VLVendorName

    • PayablesInvoice.DueDate as PInvDueDate

    • PayablesInvoice.DiscountDate as PInvDiscountDate

    • PayablesInvoice.TeramsCode.Description as TermsCodeDesc

  4. New IPA Changes:

    • In FSM_ION_PayablesTransaction_Outbound IPA flow below changes done:

      • a. Below variable added in start node:

        1.RemitToPartyName

        2.TermsDueDate

        3.DiscountDate

        4.TermsCode_Desc

        5.ItemID

        6.ExtendedReportAmount

        7.Line_XML

      • In VariablePrep Assign node added Java Script in the last to derive RemitToPartyName , TermsDueDate and DiscountDate

      • Added "InvoiceDetail" Transaction node to get the PayablesInvoicedetail records if records exist added new Assign220 assign node to construct the line xml

      • In SyncPayableTransactionBOD XML node added below fields to the respective path:

        • PInvDescription to PayableTransaction/PayableTransactionHeader/Description

        • RemitToPartyName to PayableTransaction/PayableTransactionHeader/RemitToParty/Contact/Name

        • BankTransactionCode to PayableTransaction/PayableTransactionHeader/PaymentMethodCode

        • PI_TermsCode to PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/ID

        • TermsDueDate to PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/DueDateTime

        • DiscountDate to PayableTransaction/PayableTransactionHeader/PaymentTerm/Discount/EffectiveDateTime

        • TermsCodeDesc[0]["Desc"] to PayableTransaction/PayableTransactionHeader/PaymentTerm/Description

        • Added constructed {Line_XML} tag.

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. In Service Definition enable the service for "PayablesInvoicePaymentService" and attach FSM_ION_SyncPayablesTransaction_Outbound
  2. How to Test:
    1. Create PurchaseOrder and Release it.
    2. Create PurchaseOrderReceipt and Release it.
    3. Create PayablesInvoice for that PurchaseOrder(matchInvoice) eneter the terms code and Release it.
    4. Run PerformCashRequirements
    5. Run ElectronicPaymentCreation Batch job
    6. Run PaymentClose, check the generated reports.
    7. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_PayablesTransaction_Out BOD (PayablesInvoicePaymentService).
  3. Verify the Result. In the XML below paths should be populated with values:

    • Header XML

      • PayableTransaction/PayableTransactionHeader/Description

      • PayableTransaction/PayableTransactionHeader/RemitToParty/Contact/Name

      • PayableTransaction/PayableTransactionHeader/PaymentMethodCode

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/ID

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/DueDateTime

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Discount/EffectiveDateTime

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Description

    • Line XML

      • PayableTransaction/PayableTransactionLine/LineNumber

      • PayableTransaction/PayableTransactionLine/Item/ItemID/ID

      • PayableTransaction/PayableTransactionLine/Quantity

      • PayableTransaction/PayableTransactionLine/Quantity@unitcode

      • PayableTransaction/PayableTransactionLine/ExtendedAmount

      • PayableTransaction/PayableTransactionLine/ExtendedAmount@currencyID

      • PayableTransaction/PayableTransactionLine/ExtendedReportAmount

      • PayableTransaction/PayableTransactionLine/ExtendedReportAmount@currencyID

JT-1404884

Mapping of Elements in SyncSupplierInvoice_Out for CSF-GRC PI integration

Mapping of Elements in SyncSupplierInvoice_Out for CSF-GRC PI integration

Adding new elements in SupplierInvoice BOD as part of CSF-GRC Integration.

Program/Business class/Process affected:

  • FSM_ION_SyncSupplierInvoice_Outbound.lpd

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
    2. In Service Definition enable the service for "PayablesInvoiceService" and attach FSM_ION_SyncSupplierInvoice_Outbound
  2. How to Test:
    1. Create PurchaseOrder and Release it.
    2. Create PurchaseOrderReceipt and Release it.
    3. Create PayablesInvoice for that PurchaseOrder(matchInvoice) and Release it.
    4. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SupplierInvoice_Out BOD.
  3. Verify these paths in XML:

    • SupplierInvoiceHeader/ExtendedReportAmount

    • SupplierInvoiceHeader/ExtendedReportAmount/CurrencyID

    • SupplierInvoiceLine/ExtendedReportAmount

    • SupplierInvoiceLine/ExtendedReportAmount/CurrencyID

    • SupplierInvoiceLine/UnitPrice/ReportAmount

    • SupplierInvoiceLine/UnitPrice/ReportAmount/CurrencyID

JT-1404877

PendingNativeLPLConversion: Assigning Journal References to SSJE BODs

Added Native LPL code to trigger Sync.SourceSystemJournalEntry Outbound BOD when AssignJournalReferenceNumber batch job is performed and Added JournalReferenceNumber field in new XPath for Sync.SourceSystemJournalEntry

Program/Business class/Process affected:

  • GeneralLedgerJournalControl.busclass

  • GeneralLedgerJournalControlRef.busclass

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
    2. Enable checkbox in FSMBODConfiguration for Sync.SourceSystemJournalEntry.
  2. How to Test:
    1. Select Financials > Global Ledger > Processing > Reporting Basis > Reporting Basis then select ReportingBasis and Year.
    2. Now Perform AssignJournalReferenceNumber batch job then Sync.SourceSystemJournalEntry outbound BOD will be triggered without any errors and outbound XML xml will be generated in ION Out Queue.
  3. Verify the Result:
    1. Check this path for JournalReferenceNumber:

      SyncSourceSystemJournalEntry/DataArea/SourceSystemJournalEntry/JournalEntryHeader/BaseJournalEntryHeader/ProtocolNumberText

    2. Go to GeneralLedgerJournalControl screen and Posted Tab and check JournalReferenceNumber number generated for each Journal

JT-1403868

Createed IMS Document Flow - CSF IMS to IPS - For MT Env

Delivered new document for CSF IMS to IPS for MT Environment.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ims_IPS_documentflow_ST.xml

    • FSM_IMS_All_DataFlows_ST.xml

  2. New Required Setup: No
  3. Integration Specific: Yes

    • It is related to CSF-IPS integration

Use these steps to test the enhancement:

  1. How to Test:

    • Import FSM_ims_IPS_documentflow_ST.xml file in data flows(ION).

  2. Verify the Result:
    1. Document flow should create successfully in data flows(ION).
    2. Verify CSF IMS to IPS document flow.

JT-1402517

Create IMS Document Flow - CSF IMS to XM - For MT Env

Delivered new document for CSF IMS to XM for MT Environment.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ims_XM_documentflow_ST.xml

    • FSM_IMS_All_DataFlows_ST.xml

  2. New Required Setup: No
  3. Integration Specific: Yes

    It is related to CSF-XM integration

Use these steps to test the enhancement:

  1. How to Test:

    • Import FSM_ims_XM_documentflow_ST.xml file in data flows(ION).

  2. Verify the Result:
    1. Document flow should create successfully in data flows(ION).
    2. Verify CSF IMS to XM document flow.

JT-1402516

Created IMS Document Flow - CSF IMS to SCE - For MT Env

Delivered new document for CSF IMS to SCE for MT Environment.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ims_SCE_documentflow_ST.xml

    • FSM_IMS_All_DataFlows_ST.xml

  2. New Required Setup: No
  3. Integration Specific: Yes

    It is related to CSF-SCE integration

Use these steps to test the enhancement:

  1. How to Test:

    • Import FSM_ims_SCE_documentflow_ST.xml file in data flows(ION).

  2. Verify the Result:
    1. Document flow should create successfully in data flows(ION).
    2. Verify CSF IMS to SCE document flow.

JT-1402513

Sync IEFIN ION Content to SampleDocumentTemplate.csv

Make ION Content information available in Sample Document Template

Program/Business class/Process affected:

Viewing information in Sample Document Template

Use these steps to test the enhancement:

  1. Search for and open Sample Document
  2. In the All tab, search for FSMIONContent*
  3. Verify that there are three records for the above search with attachments.

JT-1402511

Created Document Flow - GHR IMS to CSF IOBOX - For MT Env for CSF - XM integration

Delivered new document for GHR IMS to CSF IOBOX.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_all_documentflows_ST.xml

    • FSM_GHR_documentflow_ST.xml

  2. New Required Setup: No
  3. Integration Specific: Yes

    It is related to GHR-CSF integration

Use these steps to test the enhancement:

  1. How to Test:

    • Import FSM_GHR_documentflow_ST.xml file in data flows(ION).

  2. Verify the Result:

    • Document flow should create successfully in data flows(ION).

JT-1401992

Facing an Issue While testing Native Lpl for LCL Tax Report BOD

Facing an Issue While testing Native Lpl for LCL Tax Report Bod

Program/Business class/Process affected:

  • TaxEntity.busclass

Use these steps to test the enhancement:

  1. Create a Payablesinvoice with tax and release it. Do the payment for the Invoice by performing actions:
    1. Perform cash Requirements
    2. Electronic Payment Creations
    3. PaymentClose
  2. Run Vat Return Report batch Job. BOD will trigger and Work unit will generate successfully
  3. When vatReportingLine.Source is empty then TaxReportLine/TaxID details will be displayed.

JT-1399373

Assigning Journal References to SSJE BODs

Added LPL code to trigger Sync.SourceSystemJournalEntry Outbound BOD when AssignJournalReferenceNumber batch job is performed and Added JournalReferenceNumber field in new XPath for Sync.SourceSystemJournalEntry

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncSourceSystemJournalEntry_Out.lpd

    • GeneralLedgerJournalControl.busclass

    • GeneralLedgerJournalControlRef.busclass

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    • Added Variable: JRNumber

    • Node GLTRN_VAR changed: if IntegrationApplication is "Local.ly" and CountryCode is France and AssignJournalReferenceNumber batch job is performed then JRNumber will be the JournalReferenceNumber value otherwise JRNumber will be empty
  5. Integration Specific:

    These changes are related to Local.ly Integration for France Country.

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. Enable GLJournalControlService service definition.
  2. How to Test:
    1. Select Financials > Global Ledger > Processing > Reporting Basis > Reporting Basis then select ReportingBasis and Year.
    2. Now Perform AssignJournalReferenceNumber batch job then Sync.SourceSystemJournalEntry outbound BOD will be triggered without any errors.
  3. Verify the Result:
    1. Check the below path for JournalReferenceNumber:

      SyncSourceSystemJournalEntry/DataArea/SourceSystemJournalEntry/JournalEntryHeader/BaseJournalEntryHeader/ProtocolNumberText

    2. Go to GeneralLedgerJournalControl screen and Posted Tab.

JT-1393064