BOD Connectors CU76

This section contains enhancements in Infor Financials and Supply Management for 11.0.76.0

Local.ly(FR): System code description need to send to LSP - Sync.CodeDefinition Outbound

Program/Business class/Process affected:

  1. Files changed:
    • FSM_ION_SyncCodeDefinition_Outbound.lpd
    • GeneralLedgerSystemCode.busclass
    • GeneralLedgerSystemCode.busclass
    • PfiServiceDefinition,PfiServiceFlowDefinition Business class
  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:
    • In Start node added new variables FEG,SystemCode,RType,RecType,Desc_XML.
    • Added Conditions in node Assign7000,Branch7190.
    • Added new nodes JSONParser6140,Assign8170,Assign9810,AT,SysCode_XML,SysCode_BOD.
  5. Integration Specific: No

Use these steps to test the enhancement:

  1. Setup: Enable the service "GeneralLedgerSystemCodeService" for FSM_ION_SyncCodeDefinition_Outbound.lpd
  2. How to Test: Create,Update or Delete a GeneralLedgerSystemCode.
  3. Verify the Result: BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCodeDefinition_Outbound.lpd BOD.

JT-1479394

Local.ly(FR): Financial calendar bod should carry the Period Status to LSP

Local.ly(FR): Financial calendar bod should carry the Period Status to LSP: it should carry the Period status either Final Close or Limited close based on user action perform for the period.

Program/Business class/Process affected:

  1. Files Changed:
    • EntityLedgerPeriod.busclass
    • EntityLedgerPeriod.busclass
    • SyncFinancialCalendarPeriodJSON.txt
    • FSM_ION_SyncFinancialCalendar_Out.lpd
  2. New Required Setup: No
  3. New Variable Added in JSON: FinanceEnterpriseGroup.CoreLedger value assigned to FEGLedger variable.
  4. New Changes:

    LPL Changes:

    • Added Local Field "LocalAccountingEntity" in GeneralLedgerClosePeriod
    • Added "TriggerFinancialCalendarRules" instance action in GeneralLedgerClosePeriod
    • Added "TriggerFinancialCalendarRules" instance action in GeneralLedgerClosePeriod

      if (Ledger = FinanceEnterpriseGroup.CoreLedger)

      invoke TriggerFinancialCalendarRules BODGeneralLedgerClosePeriodRe

      invoked.PrmAccountingEntity = AccountingEntity

    IPA Changes:

    • Added EntityLedgerPeriodStatus,PeriodStatus, addressCode variables in start node.
    • New Variable Added in JSON: FinanceEnterpriseGroup.CoreLedger value assigned to FEGLedger variable.
    • Added new branch "Branch5300". if _service == "GeneralLedgerClosePeriodService" && IntegrationApplication == "Local.ly" then go to "LMTxnEntityLedgerP" query else go to "XML_CalPeriod"
    • Added new Landmark query nodes:LMTxnEntityLedgerP, LMTxnAE, Assign3010.
    • In "GLCCf_VAR" added "PeridStatus = Open".
    • In XML_CalPeriod, passed "PeriodStatus" in Period/Status/Code.
  5. Integration Specific: Yes

    These changes are related to Local.ly Integration.

Use these steps to test the enhancement:

  1. Setup:
    • In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
    • Enable "GeneralLedgerClosePeriodService" service for FSM_ION_SyncFinancialCalendar_Out.
    • Set IntegrationApplication = "Local.ly" in System Configuration.
    • AccountingEntity AddressCode should be set to FR(France).
  2. How to Test:

    Scenario 1:

    • ApplicationAdministrator->Financials->GlobalLedger->Processing->PeriodClose->Period List-> Select the record with status = "Limited" and in Actions perform "FinalClose"
    • Work Unit will trigger and "PeriodStatus" in Period/Status/Code will be sent as "Closed".

    Scenario 2:

    • ApplicationAdministrator->Financials->GlobalLedger->Processing->PeriodClose->PeriodForLedger->ActionOption : FinalClose.
    • Work Unit will trigger and "PeriodStatus" in Period/Status/Code will be sent as "Closed".
  3. Verify the Result:
    • Application Administrator > Financials > Processing > Period Close > Period List. Select the record with a Limited status and in the Actions perform Final Close.

      Or

    • Application Administrator > Financials > Processing > Period Close > Period For Ledger. Select the record with a Limited status and in the Actions perform Final Close.

    if AccountingEntity AddressCode = FR and IntegrationApplication = "Local.ly" then Period/Status/Code will be "Closed" else "Open"

JT-1481436

Local.ly(FR): Financial calendar bod should carry the Period Status to LSP

Local.ly(FR): Financial calendar bod should carry the Period Status to LSP: it should carry the Period status either Final Close or Limited close based on user action perform for the period.

Program/Business class/Process affected:

  1. Files Changed:
    • EntityLedgerPeriod.busclass
    • GeneralLedgerClosePeriod.busclass
    • SyncFinancialCalendarPeriodJSON.txt
    • FSM_ION_SyncFinancialCalendar_Out.lpd
  2. New Required Setup: No
  3. New Variable Added in JSON: FinanceEnterpriseGroup.CoreLedger value assigned to FEGLedger variable.
  4. New Changes:
    LPL Changes:
    • Added Local Field "LocalAccountingEntity" in GeneralLedgerClosePeriod
    • Added "TriggerFinancialCalendarRules" instance action in GeneralLedgerClosePeriod
    • Added the below code in "FinalClose" and "SetActionFinalClose" instance actions in EntityLedgerPeriod.

      if (Ledger = FinanceEnterpriseGroup.CoreLedger)

      invoke TriggerFinancialCalendarRules BODGeneralLedgerClosePeriodRe

      invoked.PrmAccountingEntity = AccountingEntity

  5. IPA Changes:
    • Added EntityLedgerPeriodStatus,PeriodStatus, addressCode variables in start node.
    • New Variable Added in JSON: FinanceEnterpriseGroup.CoreLedger value assigned to FEGLedger variable.
    • Added new branch "Branch5300". if _service == "GeneralLedgerClosePeriodService" && IntegrationApplication == "Local.ly" then go to "LMTxnEntityLedgerP" query else go to "XML_CalPeriod"
    • Added new Landmark query nodes:LMTxnEntityLedgerP, LMTxnAE, Assign3010.
    • In "GLCCf_VAR" added "PeridStatus = Open".
    • In XML_CalPeriod, passed "PeriodStatus" in Period/Status/Code.
  6. Integration Specific: Yes, these changes are related to Local.ly Integration

Use these steps to test the enhancement:

  1. Setup:
    • In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    • Enable "GeneralLedgerClosePeriodService" service for FSM_ION_SyncFinancialCalendar_Out.
    • Set IntegrationApplication = "Local.ly" in System Configuration.
    • AccountingEntity AddressCode should be set to FR(France).
  2. Scenario 1: Select Application Administrator > Financials > Global Ledger > Processing > Period Close > Period List
    • Select the record with status = "Limited" and in Actions perform "FinalClose"
    • Work Unit will trigger and "PeriodStatus" in Period/Status/Code will be sent as "Closed."
  3. Scenario 2: Select Application Administrator > Financials > Global Ledger > Processing > Period Close > Period For Ledger. Select Action> Final Close.
    • Work Unit will trigger and "PeriodStatus" in Period/Status/Code will be sent as Closed.
  4. Verify the Result: Application Administrator > Financials > Global Ledger > Processing > Period Close > Period List Select the record with status = "Limited" and in Actions perform "FinalClose" (Or)

    Select Application Administrator > Financials > Global Ledger > Processing > Period Close > Period For LedgerActionOption : FinalClose.

    • ApplicationAdministrator->Financials->GlobalLedger->Processing->PeriodClose->PeriodForLedger->ActionOption : FinalClose.

      If AccountingEntity AddressCode = FR and IntegrationApplication = "Local.ly" then Period/Status/Code will be "Closed" else "Open"

JT-1481436

Additional EAM User Fields need to be added to FSM - MaintanenceOrder Inbound BOD

Additional EAM User Fields need to be added in EAMWorkOrderUserfields busclass and map that fields to FSM_ION_SyncMaintenanceOrder_Inbound BOD

Program/Business class/Process affected:

  1. Files Changed:
    • EAMAlpha80X30 Field.
    • EAMCheckBoxX5 Field.
    • EAMNumericX5 Field.
    • EAMWorkOrder.busclass UI
    • EAMWorkOrderUserFields.busclass UI
    • FSM_ION_SyncMaintenanceOrder_Inbound
  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New Changes:
    • LPL changes:
      1. In EAMAlpha80X30 field: Changed "Value is Alpha 80" to "Value is Alpha up to 80" and occurs value from 30 to 45.
      2. In EAMCheckBoxX5 field: Changed occurs value from 05 to 10
      3. In EAMNumericX5 field: Changed occurs value from 05 to 10
      4. Added new fields in EAMWorkOrder UI and EAMWorkOrderUserFields UI for UserFields and UserFieldsAdditional.
    • IPA changes:
      1. In Start node added new variables "UDFCHKBOX06 to UDFCHKBOX10","UDFNUM05 to UDFNUM10","UDFDATE06 to UDFDATE10" and "UDFCHAR31 to UDFCHAR45
      2. Mapped the variables form XPath MaintenanceOrder/MaintenanceOrderHeader/UserArea/Property/NameValue in "Assign870"
      3. Passed the values UserFieldAlpha.Value[31] to UserFieldAlpha.Value[45],UserFieldNumeric.Value[6] to UserFieldNumeric.Value[10] ,UserFieldCheckBox.Value[6] to UserFieldCheckBox.Value[10] and UserFieldDate.Value[6] to UserFieldDate.Value[10] in "EAMWOUserFields" and "WOUserFieldsUpdate" queries.
  5. Integration Specific: Yes

These changes are related to CSF-EAM Integration.

To test this enhancement:

  1. Setup:
    • In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
    • In Channels Administrator, Activate the respective ION Inbox Receivers for FSM_ION_SyncMaintenanceOrder_Inbound.
  2. Test:
    • When the bod is processed, Work Unit will be triggered.
    • EAMWorkOrder will be Created or Updated with EAMWOrkOrderUserFeilds.
  3. Verify the result:
    • MaintenanceOrder/MaintenanceOrderHeader/UserArea/Property/NameValue values are passed to UserFieldAlpha.Value[31] to UserFieldAlpha.Value[45],UserFieldNumeric.Value[6] to UserFieldNumeric.Value[10] ,UserFieldCheckBox.Value[6] to UserFieldCheckBox.Value[10] and UserFieldDate.Value[6] to UserFieldDate.Value[10]

JT-1484132

SyncInvoice - Changes related to new Trigger and LSP Response BODs

SyncInvoice - Changes related to new Trigger and LSP Response BODs.

Program/Business class/Process affected:

File Changed:

1.BillingInvoice

2.ARLL.Java

3.IEFINPostUpgradeAction BL

4.BillingInvoiceJSON.txt

5.FSM_ION_SyncInvoice_Outbound.lpd

6.PfiServiceDefinition.xml

7.PfiServiceFlowDefinition.xml

2.New Required Setup: Service Definition Added BillingInvoiceService

3.New Variable Added in JSON: Added new JSON

4.New IPA Changes:

a.Added new flow in FSM_ION_SyncInvoice_Outbound.lpd - Branch2550 onwards.

5.Integration Specific: Yes

These changes are specific to Local.ly Integration.

To test this enhancement:

1. Setup:

1.In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.

2.Enable the Service Definition BillingInvoiceService and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.

3.BillingCompany enable Process Invoice BOD flag.

Execution:

1.Create BIllingInvoice and Release.

2.BOD will trigger and Work unit will generate successfully with required changes.

BOD triggered for BillingInvoiceService.

JT-1492203

ProcessInvoice Inbound - Changes related to new Trigger and LSP Response BODs

ProcessInvoice Inbound - Changes related to new Trigger and LSP Response BODs.

Program/Business class/Process affected:

1.Files Changed:

FSM_ION_ProcessInvoice_Inbound

Modified java script code in Assign6370 node.

Added new branch condition in "Branch6360" node.

Added new transaction nodes "UBI", "ReleaseBI".

Added new Assign node "Assign5400".

2.New Required Setup:

No

To test this enhancement:

1. Setup:

-> Create channels for Process.Invoice_Inbound BOD.

2. How to Test:

-> Country code should be "MX" and IntegrationApplication as "Local.ly".

-> Send valid XML with scheme name as "LCL.MX.UUID" or "lcl.MX.UUID" and CertificationNumber.

3. Verify the Result:

-> Check record in BillingInvoice and it should be update CertificationNumber and billing invoice should be release state.

-> Workunit should create without any errors.

JT-1492702

Locall.ly :Populate fields in ItemMaster bod

Locall.ly :Populate fields in ItemMaster_Out bod

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:

->Passed Item.IssueAccount.GeneralLedgerChartOfAccount in the Xpath of ItemMaster/ItemMasterHeader/GLAccount/GLNominalAccount in the nodes XML_ITL,XML2250,XML9450.

5.Integration Specific:No

To test this enhancement:

1. Setup:

->Enable the service "ItemService" for FSM_ION_SyncItemMaster_Out.lpd

2. How to Test:

->Create,Update or Delete an Item with Item.IssueAccount.GeneralLedgerChartOfAccount field is passed.

->Create,Update or Delete an ItemLocation.

->BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncItemMaster_Out.lpd BOD (ItemService).

3. Verify the Result:

->Item.IssueAccount.GeneralLedgerChartOfAccount in the Xpath of ItemMaster/ItemMasterHeader/GLAccount/GLNominalAccount

JT-1497281

Request New Document flow for CSF IMS-GHR IMS

Added New Document flow for CSF IMS-GHR IMS.

Program/Business class/Process affected:

1.Files Changed:

FSM_ims_GHR_ims_documentflow_ST.xml

FSM_IMS_All_DataFlows_ST.xml

2.New Required Setup:

No

To test this enhancement:

1. How to Test:

Import FSM_ims_GHR_ims_documentflow_ST.xml file in data flows(ION).

2. Verify the Result:

1. Document flows should create successfully in data flows(ION).

2. Verify FSM IMS to GHR IMS document flow.

JT-1497371

Add New elements and Map accordingly for SyncSupplierInvoice Outbound bod For india

Add New elements and Map accordingly for SyncSupplierInvoice Outbound bod For india in Line level user area.

Program/Business class/Process affected:

1.Files Changed:

FSM_ION_SyncSupplierInvoice_Outbound

2.New Required Setup:No

3.New Variable Added in JSON: No

4.New IPA Changes:

Added new variables in start node.

Modified javascript in Assign8700 node and new javascript added in Assign8700.

5.Integration Specific: Yes

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

To test this enhancement:

1. Setup:

In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.

For SyncSupplierInvoice BOD, Enable the Service Definition "PayablesInvoiceService".

In System Configuration Integration Applicati0on value should be "Loca.ly" and Country code India(IN).

2. How to Test:

Create PurchaseOrder and Release it.

Create PurchaseOrderReceipt and Release it.

Create PayablesInvoice with Invoice type match and match it.

BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncSupplierInvoice_Out BOD.

3. Verify the Result: Check the Line level level user area and it should be the value "1" and UserArea/Property/NameValue/name - "LCL.IN.ITCApplies".

JT-1506545

ChartofAccount DocumentID Transformation in ION

Program/Business class/Process affected:

1.Files Changed:

FSM_LPS_documentflow_ST.xml

FSM_all_documentflows_ST.xml

2.New Required Setup:

No

To test this enhancement:

1. How to Test:

Import FSM_LPS_documentflow_ST.xml file in data flows(ION).

2. Verify the Result:

1. Document flows should create successfully in data flows(ION).

>> What are the dependencies?

None.

JT-1507089

SyncShipment BOD - Mapping changes

Added element in Sync.Shipment_Out BOD for Local.ly

Program/Business class/Process affected:

1.Files Changed:

WarehouseShipment.busclass

FSM_ION_SyncShipment_Outbound.ipd

Shipment_Out.xlsx

FSM_Shipment_Outbound_Template.xlsx

2.New Required Setup: No new setup is required

3.New Variables Added in JSON: No new variable is added

4.New IPA Changes: Added variable CustomerTaxID defined as CustomerOrderRel.Customer.TaxID and VendorTaxID defined as Carrier.TaxID in the Service in WarehouseShipment.buscless

5.Integration Specific: Changes are related to Local.ly integration

To test this enhancement:

1. Setup:

a.In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.

b.Enable the ServiceDefinition "ShipmentService" and ProcessDefinition "FSM_ION_SyncShipment_Out"

c.Set Value to "IntegrationApplication" = "Local.ly" in System Configuration

2. How to Test:

a.Create Requisition and Release it.

b.Run WarehousePickListPrint batch job.

c.Release the WarehouseShipment.

d.Run OrderEntryDailyShipmentJournal batch job.

e.BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncShipment_Out BOD.

3. Verify the Result:

Verify the below X-Paths values.

ShipmentHeader/CarrierParty/PartyIDs/TaxID

ShipmentHeader/SupplierParty/PartyIDs/TaxID

ShipmentHeader/CustomerParty/PartyIDs/TaxID

JT-1509025

Add New Elements and Map accordingly for Sync Invoice Bod dummy lines (Local.ly)

Added Line level ShipFromparty/Location/TaxID x-path for Sync Invoice (DummyLine)

Program/Business class/Process affected:

File Changed:

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

a.In Assign4190 : Added ShipFromparty/Location/TaxID X-path in InvoiceLine Xml.

5.Integration Specific: Yes

These changes are related to Local.ly Integration specific to India.

To test this enhancement:

1. Setup:

1.In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.

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

1.Create ReceivableInvoice Batch and Release it.

4.BOD will trigger and Work unit will generate successfully for FSM_ION_SyncInvoice_Out BOD (ReceivableInvoiceService).

for dummy line

InvoiceLine/ShipFromparty/Location/TaxID X-path populating now.

InvoiceLine/ShipFromparty/Location/TaxID -->TaxEntity.VATRegistrationNumber

JT-1511105

Add New Elements and Map accordingly for Sync Invoice (Project Invoice)

Added Line level ShipFromparty/Location/TaxID x-path for Sync Invoice (Project Invoice)

Program/Business class/Process affected:

File Changed:

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

a. In XML9570: Added ShipFromparty/Location/TaxID X-path in InvoiceLine Xml..

5.Integration Specific: Yes

These changes are related to Local.ly Integration specific to India.

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.

Go to Service Definition and Enable "ReceivableInvoiceService" for "FSM_ION_SyncInvoice_Outbound.lpd" Processes.

2. How to Test:

1.Do the required Setup for creating ProjectContract.

2.Goto ProjectContract and add 'Billing Milestones'

3.Goto 'Actions' and click on 'Generate Invoices'.

4.Verify Invoices have been generated in Invoice Details tab.

5.Goto 'Actions' and click on 'Journalize Invoice'.

6.ReceivableInvoice record should generate.

7.Verify generated work unit record.

4.BOD will trigger and Work unit will generate successfully for FSM_ION_SyncInvoice_Out BOD (ReceivableInvoiceService).

InvoiceLine/ShipFromparty/Location/TaxID X-path populating now.

InvoiceLine/ShipFromparty/Location/TaxID -->TaxEntity.VATRegistrationNumber

JT-1511142

Add New Elements and Map accordingly for Sync Invoice Bod dummy lines (Local.ly)

Added ShipFromParty Node in InvoiceHeader- Sync Invoice Bod dummy lines (Local.ly)

Program/Business class/Process affected:

File Changed:

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

a.Added ShipFromParty_Hdr_XML in Start node

b.In Assign4010 - Added javascript for ShipFromParty.

c.In XML_INVHDR:Mapped ShipFromParty_Hdr_XML

5.Integration Specific: Yes

These changes are related to Local.ly Integration specific to India.

To test this enhancement:

1. Setup:

1.In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.

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

Execution:

1.Create ReceivableInvoice Batch and Release it.

4.BOD will trigger and Work unit will generate successfully for FSM_ION_SyncInvoice_Out BOD (ReceivableInvoiceService).

for dummy line

SyncInvoice/DataArea/Invoice/InvoiceHeader/ShipFromParty x-paths are populating now.

JT-1516390

Add New Elements and Map accordingly for Sync Invoice Outbound Bod (Project Invoice)

Added ShipFromParty Node in InvoiceHeader - Sync Invoice Outbound Bod (Project Invoice)

Program/Business class/Process affected:

File Changed:

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

a.Added ShipFromParty_Hdr_XML in Start node

b.In Assign4010 - Added javascript for ShipFromParty.

c.In XML_INVHDR:Mapped ShipFromParty_Hdr_XML

5.Integration Specific: Yes

These changes are related to Local.ly Integration specific to India.

To test this enhancement:

1. Setup:

1.In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.

2.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:

1.Do the required Setup for creating ProjectContract.

2.Goto ProjectContract and add 'Billing Milestones'

3.Goto 'Actions' and click on 'Generate Invoices'.

4.Verify Invoices have been generated in Invoice Details tab.

5.Goto 'Actions' and click on 'Journalize Invoice'.

6.ReceivableInvoice record should generate.

7.Verify generated work unit record.

4.BOD will trigger and Work unit will generate successfully for FSM_ION_SyncInvoice_Out BOD (ReceivableInvoiceService).

SyncInvoice/DataArea/Invoice/InvoiceHeader/ShipFromParty x-paths are populating now

JT-1516394

ION Content and JSON Files Delivery -CU76

Latest IPA JSON files and FSM_ION_CONTENT* delivery -

JSONFILES_ST record updated in \iefin\wfdata\SampleDocumentTemplate.

FSM_ION_CONTENT* record updated in \iefin\plugins\iefinconnector\ipa_content.

Program/Business class/Process affected:

\iefin\wfdata\SampleDocumentTemplate.

\iefin\plugins\iefinconnector\ipa_content\SampleDocumentTemplate.

To test this enhancement:

Go to Application -->Application Administrator -->Supply Management -->Shared Processes -->Sample Document Template.

Open Sample Document

In the All tab, search for JSONFILES_ST, the record updated with attachment.

In Fact Sheets tab, search for FSM_ION_CONTENT*, three records updated with attachment.

FSM_ION_CONTENTPACK_ST,FSM_ION_CONTENT_PACK_IONCE_IMS_ST and FSM_ION_CONTENT_PACK_IONCE_ST.

JT-1516911

Map DocumentDateTime Field with Invoice date in SyncSupplierInvoice Outbound bod for Local.ly

Map DocumentDateTime Field with Invoice date in SyncSupplierInvoice Outbound bod for Local.ly

Program/Business class/Process affected:

1. Files Changed:

FSM_ION_SyncSupplierInvoice_Outbound

2. New Required Setup:No

3. New Variable Added in JSON: No

4. New IPA Changes:

-Added new variables in start node.

Modified javascript in Assign5320 node.

5.Integration Specific: Yes

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

To test this enhancement:

1. Setup:

In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.

For SyncSupplierInvoice BOD, Enable the Service Definition "PayablesInvoiceService".

In System Configuration Integration Application value should be "Loca.ly".

2. How to Test:

Create PayablesInvoice and Release it.

BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncSupplierInvoice_Out BOD.

3. Verify the Result: Check the SupplierInvoiceHeader/DocumentDateTime xpath that should be Invoice date for Local.ly.

JT-1519339