BOD Connectors
Add Accounting entity element - UOM- and only for Clean Document ID
Added Accounting entity element in the X-path SyncCodeDefinition\DataArea\Sync\AccountingEntityID for UOM in Sync.CodeDefinition_Outbound.
- Files Changed: FSM_ION_SyncCodeDefinition_Outbound.lpd
- New Required Setup: None.
- New Variable Added in JSON: No.
- New IPA Changes: Added Accounting entity element in the X-path SyncCodeDefinition\DataArea\Sync\AccountingEntityID.
- Integration Specific: No.
- Enable the service "UnitOfMeasureService" for FSM_ION_SyncCodeDefinition_Outbound.lpd.
- Create or update UnitOfMeasure.
- BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCodeDefinition_Outbound.lpd BOD.
- Verify the Result. Accounting entity element in the X-path SyncCodeDefinition\DataArea\Sync\AccountingEntityID when CleanDoc is enabled.
Dependencies: None.
JT-1630489
Add New Elements for SyncInventoryAdjustment Outbound bod for Local.ly
Add New Elements for SyncInventoryAdjustment Outbound bod for Local.ly.
- File Changed: FSM_ION_SyncInventoryAdj_Outbound.lpd
- IPD Changes:
- Startnode: Added 'TransactionDateTime'
- Added below code in Javascript of 'Assign ICT Line'
node
if(IntegrationApplication == "Local.ly") { TransactionDateTime = ict_trans_date; }
- Added following path in Line XM: <TransactionDateTime>{TransactionDateTime}</TransactionDateTime>
- Setup:
- In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
- Enable the Sync.InventoryAdjustment in FSMBODConfiguration
- Create InventoryTransaction Header with document type as 'Adjustment'.
- Go to Lines tab and create Inventory Transaction Line
- Go to Actions and Release Inventory Transaction.
- Inventory Transaction gets released.
- Check the generated XML in Work unit.
- Verify Results. Verify following path: <TransactionDateTime>{TransactionDateTime}</TransactionDateTime>
Dependencies: None.
JT-1628337
Add New Elements for SyncPayableTracker outbound for the country Mexico and Local.ly
Add New Elements for SyncPayableTracker outbound for the country mexico and Local.ly.
- File Changed: FSM_ION_SyncPayableTracker_Out.lpd
- IPA Change:
- Added following variable in 'start' node: reasoncode
- Added 'ReasonCode' in 'PInvoice' and 'PayablesInvoice' landmark nodes.
- Added following code in Assign3280 javascript:
if(IntegrationApplication == "Local.ly" && AE_DerivedAccountingEntityCountry == "MX" && PayablesInvoice_ReasonCode!="") { reasoncode = PayablesInvoice_ReasonCode; }
- Added following code in Assign8290
node:
if(IntegrationApplication == "Local.ly" && AE_DerivedAccountingEntityCountry == "MX" && PInvoice_ReasonCode!="") { reasoncode = PInvoice_ReasonCode; }
- Added below path in 'PayableTrackerAdjL' XM:
<Property>
<NameValue name="lcl.StatusReason" type="StringType">{reasoncode}</NameValue>
</Property>
- Added below path in 'PayTrackerLine'
XM:
<UserArea>
<Property>
<NameValue name="lcl.StatusReason" type="StringType">{reasoncode}</NameValue>
</Property>
</UserArea>
- Integration Specific: Yes. These changes are related to Local.ly Integration for Mexico Country.
- Setup. In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
- Setup. In Service Definition enable the service for "PayableTrackerService" and attach FSM_ION_SyncPayablesTracker_Out.
- Add WithHolding details in Vendor.
- Create PayablesInvoice(One by giving tax amount another by not giving any tax amount) , using above vendor and release Invoice.
- Run PerformCashRequirements.
- Run ElectronicPaymentCreation Batch job.
- BOD will trigger and Work unit will generate successfully without any error for FSM_ION_PayablesTracker_Out BOD (PayablesTrackerService).
- Verify following X Path in generated XML: SyncPayableTracker/DataArea/PayableTracker/PayableTrackerLine/UserArea/Property/NameValue [@name='lcl.StatusReason']-----> PayablesInvoice.ReasonCode
Dependencies: None.
JT-1628758
ION Content and JSON Files Delivery - IEFIN2021.10
- JSONFILES_ST record updtaed in \iefin\wfdata\SampleDocumentTemplate.
- FSM_ION_CONTENT* record updated in \iefin\plugins\iefinconnector\ipa_content.
- \iefin\wfdata\SampleDocumentTemplate
- \iefin\plugins\iefinconnector\ipa_content\SampleDocumentTemplate
- Go to Application -->Application Administrator -->Supply Management -->Shared Processes -->Sample Document Template.
- Open Sample Document.
- In the All tab, search for JSONFILES_ST, the record updated with attachment.
- In Fact Sheets tab, search for FSM_ION_CONTENT*, three records updated with
attachment:
- FSM_ION_CONTENTPACK_ST
- FSM_ION_CONTENT_PACK_IONCE_IMS_ST
- FSM_ION_CONTENT_PACK_IONCE_ST
Dependencies: None.
JT-1633243
New feature Changes development for SyncSupplierInvoice Outbound bod for Local.ly India
New feature Changes development for SyncSupplierInvoice Outbound bod for Local.ly India.
- File Changed: FSM_ION_SyncSupplierInvoice_Outbound.lpd
- New Required Setup: No
- New Variable Added in JSON: No
- New IPA Changes:
-
In FSM_ION_SyncSupplierInvoice_Outbound.lpd IPA flow below changes have been made:
- Start node : Added PInvVendorLocation,DummyLineTaxTotalAmount,DummyTaxTotalAmount,DummyTaxAmount and PIDDesc variable.
- In Assign6360: Added In Javascript logic for PInvVendorLocation.
- In VendorLoc Transaction node query PInvVendorLocation value passed instead of PVendorLocation
- In Assign5320:Commented Line_XML in Javascript.
- Newly added Branch20 ,PID Transaction node,Branch2310,Assign7370,PIDTax Transaction node,Assign3190,Assign6550,Assign5790,PIDTax1 Transaction node and Assign5510
-
- Integration Specific: Yes. These changes are related to Local.ly Integration specific to India country.
- Setup:
- In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
- Enable the Service Definition and Processes for FSM_ION_SyncSupplierInvoice_Outbound IPA flow.
- Go to Service Definition and Enable "PayableInvoiceService" for "FSM_ION_SyncSupplierInvoice_Outbound.lpd" Processes.
- Create PayableInvoice and Release it.
- BOD will trigger and Work unit will generate With respective changes.
Dependencies: None.
JT-1629426
ProcessRequisition_Inbound BOD Source by Item Type Option
ProcessRequisition_Inbound BOD Source by Item Type Option based on configuration parameter "RequisitionShipment".
- Files Changed: FSM_ION_ProcessRequisition_In
- New Required Setup: No
- New Variable Added in JSON: No
- New IPA Changes:
- Added new queries: LMTxnLineItemIorN,LMTxnReqLineItemIorN. Added new assign nodes: Assign2500,Assign9680,Assign2900,Assign6290.
- Added new condition in branch "Type_I_or_N",Branch5410.
- If Configuration parameter "RequisitionShipment == "Y"" then then RequisitionLine>ItemType is passed empty. Core application decide if RequisitionLine.ItemType is Inventoried or non stock item based on Item setup.
- Integration Specific: No
- Setup:
- In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
- In Channels Administrator, Activate the respective ION Inbox Receivers for FSM_ION_ProcessRequisition_In.
- When FSM_ION_ProcessRequisition_In BOD is processed, Work Unit will be triggered.
- Requisition is created and released.
- Verify the result:
- Requisition is created and released without any errors.
- If Configuration parameter "RequisitionShipment == "Y"" then then RequisitionLine.ItemType is passed empty. Core application decide if RequisitionLine.ItemType is Inventoried or non stock item based on Item setup.
Dependencies: None.
JT-1625588
Remove Code definition territory from the MSCRM list
Remove Code definition territory from the MSCRM list.
- bl/BODDataInitialLoad
- ui/BODDataInitialLoad
- Go To Application Administrator-->Financials -->Shared Processes ->BOD Integrations.Click on Mass BOD Publish.
- Open Mass BOD Publish.
- Create record.
- Select Type as "Integration Wise" and Select Integration as "MSCRM".
- Removed Code Definition Territory BOD from the MSCRM list.
Dependencies: None.
JT-1630483
Remove the Fiscal year and Fiscal period Nodes in the SyncInvoice outbound bod for Local.ly
Remove the Fiscal year and Fiscal period Nodes in the SyncInvoice outbound bod for Local.ly.
- 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 were made:
- In Assign20: In Javascript , for PROPERTIES_XML, lcl.FiscalYear and lcl.FiscalPeriod property commented.For Local.ly Integration.
- In Assign260: In Javascript , for PROPERTIES_XML, lcl.FiscalYear and lcl.FiscalPeriod property commented.
- In FSM_ION_SyncInvoice_Outbound IPA flow below changes were made:
- Integration Specific: Yes. These changes are related to Local.ly Integration all Countries.
- 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.
- Go to Service Definition and Enable "BillingInvoiceService" for "FSM_ION_SyncInvoice_Outbound.lpd" Processes.
- Testing ReceivableInvoiceService:.
- Test scenario 1::
- Create ReceivableInvoice and Release it.
- BOD will trigger and Work unit will generate With respective newly added element.
- Test scenario 2:
- Create BillingInvoice Release it.
- Execute InvoiceVerificationRepor.
- Execute InvoiceAndRegisterPrint
- Execute SubSystemUpdate.
- OD will trigger and Work unit will generate With respective newly added element.
- Test scenario 3:
- Do the required Setup for creating ProjectContract.
- Goto ProjectContract and add 'Billing Milestones'.
- Goto 'Actions' and click on 'Generate Invoices'.
- Verify Invoices have been generated in Invoice Details tab.
- Goto 'Actions' and click on 'Journalize Invoice'.
- ReceivableInvoice record should generate.
- Verify generated work unit record.
- Test scenario 1::
- BOD will trigger and Work unit will generate successfully with newly added element.
- Verify the Result: SyncInvoice/DataArea/Invoice/ InvoiceHeader/UserArea @lcl.FiscalYear and lcl.FiscalPeriod properties -removed
- In BillingCompany , Enable Process Invoice BOD flag.
- Create BillingInvoice and Release it.
- BOD will trigger and Work unit will generate successfully with newly added element.
- Verify the Result: SyncInvoice/DataArea/Invoice/ InvoiceHeader/UserArea @fsm.FiscalYear and fsm.FiscalPeriod properties- removed .
Dependencies: None.
JT-1625527
Add New Elements for SyncInventorycount Outbound bod for Local.ly
Added new elements: SyncInventoryCount Outbound
Program/Business class/Process affected:
- Files Changed:
- FSM_ION_SyncInventoryCount_Out.lpd
- New Required Setup: No
- New Variable Added in JSON: No
- New IPA Changes:
- Updated node Header
- Integration Specific: No
Use these steps to test the enhancement:
- Setup: Enable the service "InventoryCountService" for FSM_ION_SyncInventoryCount_Out.lpd
- How to Test:
- Trigger MassBOD for InventoryCount.
- BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncInventoryCount_Out.lpd BOD
- Verify the Result: Passed CurrentDateTimeStamp in Xpath InventoryCount/InventoryCountLine/TransactionDateTime:
JT-1628340