BOD Connectors CU67
FSMInboundBODTracker to track all Inbound BOD processing status
As part of native LPL adoption, a FSMInboundBODTracker screen was created to track all inbound BOD processing statuses.
Program/Business class/Process affected:
New classes:
- FSMInboundBODTracker
- FSMAPInboundBODImport
- FSMARInboundBODImport
- FSMGLInboundBODImport
- FSMCDInboundBODImport
- FSMPOInboundBODImport
- FSMRQInboundBODImport
- FSMICInboundBODImport
Updated files:
- 11.0_post_CU80.faf
- FSMBODConfigurationDetail
- AllBODMenu
Security class changes:
- IEFINCommonViewInformation_ST
- IEFINBODProcessing_ST
Use these steps to test this enhancement:
As part of security changes, these codes were added in their respective security classes:
- IEFINBODProcessing_ST security classes (all classes are accessible for all actions
unconditionally):
- FSMInboundBODTracker BusinessClass
- FSMAPInboundBODImport BusinessClass
- FSMARInboundBODImport BusinessClass
- FSMGLInboundBODImport BusinessClass
- FSMCDInboundBODImport BusinessClass
- FSMPOInboundBODImport BusinessClass
- FSMRQInboundBODImport BusinessClass
- FSMICInboundBODImport BusinessClass
- In IEFINCommonViewInformation_ST security classes (all classes are
accessible for all inquiries and audit views unconditionally):
- FSMInboundBODTracker BusinessClass
- FSMAPInboundBODImport BusinessClass
- FSMARInboundBODImport BusinessClass
- FSMGLInboundBODImport BusinessClass
- FSMCDInboundBODImport BusinessClass
- FSMPOInboundBODImport BusinessClass
- FSMRQInboundBODImport BusinessClass
- FSMICInboundBODImport BusinessClass
JT-1243185
ION Content for IMS Connection LPL BOD integrations
Document flows were added in ION Content as part of IMS BODs. These flows are delivered with existing templates. In IEFINCommonViewInformation_ST security classes (all classes are accessible for all inquiries and all audit views unconditionally):
Program/Business class/Process affected:
- FSM_EAM_dataflow_ims_STxx.xml
- FSM_GFC_dataflow_ims_STxx.xml
- FSM_HRCM_dataflow_ims_STxx.xml
- FSM_MINGLE_dataflow_ims_STxx.xml
- FSM_ALL_dataflow_ims_STxx.xml
Use these steps to test this enhancement:
Load the document flows as part of LPL based BODs testing with respect to different applications.
JT-1339951
Update JE sequence number for GFC BODs
In the FSM_ION_ProcessSSJE_Inbound BOD, the JE sequence number for GFC BODs was update with the user area property gfc.sourceJeLineSequence.
Program/Business class/Process affected:
- FSM_ION_ProcessSourceSystemJournalEntry_Inbound
Use these steps to test this enhancement:
In IEFINCommonViewInformation_ST security classes (all classes are accessible for allFor the sequence of GlTransactionInterface, priority should be given to line user area gfc.sourceJeLineSequence. If the value of gfc.sourceJeLineSequence is empty or null, then priority should be given to sequence attribute of JournalEntryLine. In ReferenceID, the sequence number should be based on these conditions.
JT-1371291
SyncInventoryCount from Mass BOD
An option was added to select Item of SyncInventoryCount from Mass BOD.
Program/Business class/Process affected:
- ItemLocation.busclass
- BODDataInitialLoad. busclass(bl & UI)
- CU80.faf
Use these steps to test this enhancement:
- Enable a service definition for InventoryCountService. Attach FSM_ION_SyncInventoryCount.lpd.
- On the BODDataInitialLoad screen, create a record for Transactiontype or For Integration EAM.
- On the InventoryCount panel, specify the criteria related to Item.
- Enable the Trigger option and run the TriggerNow action.
- A work unit will be created for Item.
JT-1373231
Item location using SyncItemMaster_inbound BOD
In PendingNativeLPLConversion, an error while trying to create an item location using SyncItemMaster_inbound BOD was fixed.
Program/Business class/Process affected:
- FSMICInboundBODImport.busclass
Use these steps to test this enhancement:
- Enable Sync.ItemMaster in FSMBODConfiguration.
- In FSMBODConfigurationParameter, set IntegratingApplication to EAM.
- Once the BOD is processed, an Item and ItemLocation are created and updated.
- For creating or updating ItemLocation, the value for Company and ItemLocation will be from XPath ItemMaster/ItemLocation/WarehouseLocation/ID. The value is concatenated as Company@@ItemLocation.
JT-1387005
OutputFileHeader data for all payment formats
The WireTransferBOD trigger can handle OutputFileHeader data for all payment formats.
Program/Business class/Process affected:
- WireTransferOutput
Use these steps to test this enhancement:
- In FinanceEnterpriseGroup, the BOD Trigger check box should be selected.
- In Service Definition, specify the Service Name as WireTransferService and the Process Name as FSM_ION_SyncCreditTransfer_Out.lpd.
- Create WireTransferBatch and WireTransferBatchDetail. Release WireTransferBatch. The BOD will trigger and a work unit will be created.
JT-1378576
Changes for LCLTaxReport_Outbound Mexico
Changes were made for LCLTaxReport_Outbound Mexico.
Program/Business class/Process affected:
- FSM_ION_SyncLCLTaxReport_Outbound BOD
Use these steps to test this enhancement:
- Enable the service definition with the Service Name of TaxReportService for processing FSM_ION_SyncLCLTaxReport_OutBound.lpd.
- For Mexico, create a Payablesinvoice with tax and release it. Do the payment for the
invoice by performing these actions:
- Perform Cash Requirements
- Electronic Payment Creations
- PaymentClose
- Run the Vat Return Report to trigger the BOD. When it is triggered, check XML for the Supplier details and summaryTransaction (TaxTransaction details) to verify it.
JT-1381752
LoadSupplierInvoice_Inbound IPA flow PayImmediately field
A new field PayImmediately field was added to the MatchInvoiceImport transaction node.
Program/Business class/Process affected:
- FSM_ION_LoadSupplierInvoice_Inbound
Use these steps to test this enhancement:
- Create channels for FSM_ION_LoadSupplierInvoice_Inbound.
- Send XML with the PayImmediately field in HeaderUserArea.
- A work unit should be created without any errors.
- Check the PayImmediately field in the MatchInvoiceImport businessClass.
JT-1384136
LoadSupplierInvoice_Inbound IPA flow add on charges
For PendingNativeLPLConversion, the LoadSupplierInvoice_Inbound IPA flow had an add on charges field added.
Program/Business class/Process affected:
- FAMAPInboundBODImport business class
Use these steps to test this enhancement:
- Enable the Load.SupplierInvoice BOD in FSMBODConfiguration.
- Create PurchaseOrder and release it.
- Create PurchaseOrderReceipt and release it.
- Send the XML with AddOnCharge details in the header level and line level.
- An Inbound Tracker record should be created with a Complete status.
- Check the record in MatchInvoiceImport and AddOnCharge details.
JT-1386431
SerialControlIndicator
For PendingNativeLPLConversion, SerialControlIndicator should be send a True or False value.
Program/Business class/Process affected:
- Item.busclass
Use these steps to test this enhancement:
- Enable the ItemMaster Outbound BOD in FSMBODConfiguration.
- Specify the integration value as Local.ly in the FSMBODConfigurationParameter IntegrationApplication field.
- Create, update, or delete the field.
- For the Local.ly integration, when an item is tracked as serial tracked and sent as NotSerialTracked, then the value is passed as False. Otherwise, True is passed in the ItemMaster/ItemMasterHeader/SerialControlIndicator Xpath.
JT-1386941
New elements and map for discount related fields in SyncInvoice BOD
New elements and a map were added for discount related fields in the SyncInvoice BOD.
Program/Business class/Process affected:
- FSM_ION_SyncInvoice_Outbound.lpd
- FSM_Invoice_Outbound_Template.xls
- Invoice_Out.xlsx
Use these steps to test this enhancement:
- In FinanceEnterpriseGroup, select the BODTrigger check box.
- Specify the Service Definition as ReceivableInvoiceService and Process as FSM_ION_SyncInvoice_Outbound.lpd.
- Trigger the SyncInvoice BOD for Localization Services. The BOD will be triggered and a work unit will be created with the specified elements.
JT-1387906
New elements for SyncInvoice BOD for Mexico
New elements were added for the SyncInvoice BOD for Mexico.
Program/Business class/Process affected:
- FSM_ION_SyncInvoice_Outbound.lpd
- FSM_Invoice_Outbound_Template.xls
- Invoice_Out.xlsx
Use these steps to test this enhancement:
- In FinanceEnterpriseGroup, select the BODTrigger check box.
- Specify the Service Definition as ReceivableInvoiceService and Process as FSM_ION_SyncInvoice_Outbound.lpd.
- Trigger the SyncInvoice BOD for Localization Services. The BOD will be triggered and a work unit will be created.
These xpath elements specific to Mexico were added:
- InvoiceLine/Item/ItemID/ID[@schemeName='Customer']
- InvoiceLine/Item/ItemID/ID -->CustomerItemCrossReference
JT-1388690
SyncSupplierInvoice BOD Amount field
An issue where NaN was displayed the Amount field in the SyncSupplierInvoice BOD has been fixed.
Program/Business class/Process affected:
- FSM_ION_SyncInvoice_Outbound.lpd
Use these steps to test this enhancement:
- In FinanceEnterpriseGroup, select the BODTrigger check box.
- Specify the Service Definition as PayablesInvoiceService and Process as FSM_ION_SyncSupplierInvoice_Outbound.lpd.
- Trigger the SyncInvoice BOD for Localization Services. The BOD will be triggered and a work unit will be created.
These xpath elements were updated so NaN is not displayed:
- SupplierInvoiceHeader/ExtendedPretaxAmount
- SupplierInvoiceHeader/SubTotalAmount
JT-1388811
SyncSupplierInvoice BOD mapping changes
SyncSupplierInvoice BOD mapping changes were made for AlternateDocumentID.
Program/Business class/Process affected:
- FSM_ION_SyncSupplierInvoice_Outbound.lpd
- SupplierInvoice_Out.xlsx
- FSM_SupplierInvoice_Outbound_template.xls
Use these steps to test this enhancement:
- In FinanceEnterpriseGroup, select the BODTrigger check box.
- Specify the Service Definition as PayablesInvoiceService and Process as FSM_ION_SyncSupplierInvoice_Outbound.lpd.
- Trigger the SupplierInvoice BOD for Localization Services. The BOD will be triggered and a work unit will be created.
The xpath element AlternateDocumentID/ID should be mapped correctly.
JT-1391216