BOD Connectors

This section contains enhancements in Infor Financials and Supply Management.

Add New Elements For Sync Payable Tracker Outbound BOD for Local.ly

Program/Business class/Process affected:

  • Files changed: FSM_ION_SyncPayableTracker_Out.lpd
  • Variable Added in JSON: No.
  • IPA Changes:
    • Added this code in Assign:4060:
       if(IntegrationApplication=="Local.ly" )
 {
 location = appsCriteria1+Generic_Delimiter +CLPP_Company;
 }
    • Added location element in PayableTrackerXML.
  • Integration Specific: Yes. These changes are related to Local.ly Integration.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, the BODtrigger check box should be checked.
  2. Enable the Service Definition and Processes.
  3. Do required setup for PayableTracker flow.
  4. Create PayablesInvoice and release it.
  5. Run'Perform Cash Application' job.
  6. Check CashRequiremnetsResults records.
  7. Run ElectronicPaymentCreation job.
  8. BOD triggers and Work unit generates successfully without any error for FSM_ION_SyncPayableTracker_Out BOD.
  9. Verify the Result. Verify this x-Path, PayableTrackerHeader/DocumentID/ID/location.

Dependencies: None.

JT-1706796

Add new elements and map for Sync Supplier party master outbound BOD for Local.ly and country Australia (TPAR)

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncSupplierpartyMaster_Out.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: BankAccountValidationType
  • New IPA Changes:
    • In Start node added variables VIBBankAccountNumber and BankAccountValidationType.
    • Added Conditions in node Assign_1.
  • Integration Specific:Yes. Local.ly and country Australia.

Use these steps to test the enhancement:

  1. Enable the service "VendorGroupService" for FSM_ION_SyncSupplierPartyMaster_Out.lpd.
  2. Create,Update or Delete a Vendor and save it.
  3. BOD triggers and Work unit generates successfully without any error for FSM_ION_SyncSupplierPartyMaster_Out.lpd BOD.
  4. Verify the Result:

    • Mapped VendorAddress.AddressLine1 in XPath SupplierPartyMaster/Location/Address/StreetName.

    • Mapped SupplierPartyMaster/Location/Address/CountrySubDivisionCode------>VendorAddress.StateProvince

      SupplierPartyMaster/Location/Address/CountrySubDivisionCode------>VendorAddress.StateProvince

      SupplierPartyMaster/Location/Address/CountrySubDivisionCode------>VendorAddress.StateProvince

    • Mapped Vendor.BankAccountNumber in XPath FinancialParty/FinancialAccount/IBANID if Vendor.BankAccountValidationType is IBAN or IBAN and Bic.

Dependencies: None.

JT-1714721

Change the Scheme ID for Endpointid of customer in SyncInvoice Outbound bod for Local.ly and Country Australia

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncInvoice_Outbound.lpd
  • Variable Added in JSON: No.
  • IPA Changes:
    • FSM_ION_SyncInvoice_Outbound IPA flow, changes made in Assign1740. Modified javascript:
      "Local.ly" && AddressCode != "" && AddressCode_PostalAddress_Country =="AU" . AUschemeID = "AU:ABN";

  • Integration Specific: Yes. These changes are related to Local.ly Integration specific to Austalia (AU).

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.
  3. Go to Service Definition and Enable "ReceivableInvoiceService" for "FSM_ION_SyncInvoice_Outbound.lpd" Processes.
  4. Create ReceivableInvoice and Release it.
  5. BOD triggers and Work unit generates with respective newly added element.
  6. Create BillingInvoice Release it.
  7. Run InvoiceVerificationReport.
  8. Run InvoiceAndRegisterPrint.
  9. Run SubSystemUpdate.
  10. BOD triggers and Work unit generates with respective newly added element.
  11. Verify the Result. In InvoiceHeader/CustomerParty/PartyIDs/EndPointID@schemeID="AU:ABN" added.

Dependencies: None.

JT-1706031

Changes for CreditTransfer_Outbound changes-- Local.ly

Program/Business class/Process affected:

  • Files Changed:
    • ElectronicPaymentCreation_ElectronicPaymentCreation.java
    • FSM_ION_SyncCreditTransfer_Out.lpd
  • Variable Added in JSON: No.
  • .IPA Changes:
    • 'CountryCheck', 'Branch3120',and 'Branch4890' nodes are modified to check local.ly validation.
    • Added "Locall.ly" validation for nodes 'Assign6240', 'Assign7400', and 'Assign4940'.
  • .Integration Specific: Yes.

Use these steps to test the enhancement:

  1. Setup. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Setup. Enable the Service Definition and Processes.
  3. Do required setup for CreditTransfer flow.
  4. Create PayablesInvoice and release.
  5. Run'Perform Cash Application' job.
  6. Check CashRequiremnetsResults records.
  7. Run ElectronicPaymentCreation job.
  8. BOD triggers and Work unit generates successfully without any error for FSM_ION_SyncPayableTracker_Out BOD.
  9. Verify the Result.

    X-Path:: CreditTransferPayment/PaymentTransaction/CreditTransferAgreement/CategoryPurposeCode.

Dependencies: None.

JT-1713131

Changes for FSM_ION_SyncCreditTransfer_Outbound-- Local.ly, Australia

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • Variable Added in JSON: No.
  • IPA Changes: Changes made In Javascript 'Assign6780'.
  • Integration Specific: Yes. These changes are related to Local.ly Integration for Australia (AU).

Use these steps to test the enhancement:

  1. Setup: In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Setup :Enable the Service Definition and Processes.
  3. Do required setup for CreditTransfer flow.
  4. Create PayablesInvoice and release.
  5. Run'Perform Cash Application' job.
  6. Check CashRequiremnetsResults records.
  7. Run ElectronicPaymentCreation job.
  8. BOD triggers and Work unit generates successfully without any error for FSM_ION_SyncPayableTracker_Out BOD.
  9. Verify the Result: X-Path:: CreditTransferPayment/PaymentTransaction/CreditTransferAgreement/CategoryPurposeCode.

Dependencies: None.

JT-1714205

Changes for Load Bank Statement_Inbound-- .NAI Format for Australia

Program/Business class/Process affected:

  • Files Changed: FSM_ION_LoadBankStatement_Inbound
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes: Added conditions in Assign470.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. Setup. In ChannelAdministrator enable the receiver FSM_ION_LoadBankStatement_Inbound.
  2. Setup. In ConfigutationParameter set value for LoadBankStatement_In_CashManagementGroup.
  3. After the BOD gets processed, BankStatement is Created Successfully.
  4. Workunit triggers without errors.
  5. Verify the Result:
    • BankStatement and BankStatementLine should be successfully created for .NAI format.
    • Mapped BankStatementLine. RelatedReference from XPath LoadBankStatement/BankStatement/BankStatementAccount/AccountEntry/Entrynote
    • Mapped BankStatementline.Description from XPath LoadBankStatement/BankStatement/BankStatementAccount/AccountEntry/EntryDetail/EntryTransaction/RemittanceInformation/UnstructuredRemittanceText

Dependencies: None.

JT-1712429

Changes for Sync_CreditTransfer_Outbound for New Zealand

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • Variable Added in JSON: No.
  • .IPA Changes: Added Javascript code in Assign6780 node.
  • Integration Specific: Yes. These changes are related to Local.ly Integration for NZ country.

Use these steps to test the enhancement:

  1. Setup: In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Setup: Enable the Service Definition and Processes.
  3. Do required setup for CreditTransfer flow.
  4. Create PayablesInvoice and release.
  5. Run'Perform Cash Application' job.
  6. Check CashRequiremnetsResults records.
  7. Run ElectronicPaymentCreation job.
  8. BOD triggers and Work unit generates successfully without any error for FSM_ION_SyncPayableTracker_Out BOD
  9. Verify the Result. Verify the below x-Path
    • CreditTransfer/CreditTransferPayment/RequestedExecutionDateTime. Cash ledger Payables Payment. PaymentDate
    • CreditTransfer/CreditTransferPayment/PaymentTransaction/ChargeBearerCode. Pass the value as "Shared" if the Country in AccountingEntity and Vendor/Remitto Location is Different and Pass the value as "Debtor" if the countries are same.
    • Pass only two decimal values for the amounts in the below nodes:
      • CreditTransfer/CreditTransferPayment/PaymentTransaction/InstructedAmount
      • CreditTransfer/CreditTransferPayment/PaymentTransaction/EquivalentAmount

Dependencies: None.

JT-1709121

Changes required in SyncCreditTransfer_Out BOD for Netherlands

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • Variable Added in JSON: No.
  • IPA Changes: Yes. Modified changes in Javascript.
  • Integration Specific: Yes. These changes are related to Local.ly Integration for Netherlands (NL) country.

Use these steps to test the enhancement:

  1. Setup: In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Setup: Enable the Service Definition and Processes.
  3. Do required setup for CreditTransfer flow.
  4. Create PayablesInvoice and release.
  5. Run'Perform Cash Application' job.
  6. Check CashRequiremnetsResults records.
  7. Run ElectronicPaymentCreation job.
  8. BOD triggers and Work unit generates successfully without any error for FSM_ION_SyncPayableTracker_Out BOD.
  9. Verify Result in below X-Path: SyncCreditTransfer/DataArea/CreditTransfer/CreditTransferPayment/PaymentTransaction/ChargeBearerCode

Dependencies: None.

JT-1713691

Create new document flows and connection points with the new logical ID after the IOBOX to IMS conversion

Modified EAM connection point name in FSM-EAM document flows.

Program/Business class/Process affected:

  • Files Changed:
    • FSM_EAM_documentflow_ST.xml
    • FSM_ims_EAM_documentflow_ST.xml
    • FSM_all_documentflows_ST.xml
    • FSM_IMS_All_DataFlows_ST.xml

Use these steps to test the enhancement:

  1. Import FSM_EAM_documentflow_ST.xml and FSM_ims_EAM_documentflow_ST.xml files in data flows(ION).
  2. Verify the Result:
    • Document flows should create successfully in data flows (ION).
    • Verify FSM-GFC document flows.

Dependencies: None.

JT-1699744

Deliver new GFC IMS LogicalID in FSM Data flows

Modified GFC connection point name in FSM-GFC document flows.

Program/Business class/Process affected:

  • Files Changed:
    • FSM_GFC_ims_documentflow_ST.xml
    • FSM_ims_GFC_ims_documentflow_ST.xml
    • FSM_all_documentflows_ST.xml
    • FSM_IMS_All_DataFlows_ST.xml
  • New Required Setup: No.

Use these steps to test the enhancement:

  1. Import FSM_GFC_ims_documentflow_ST.xml and FSM_ims_GFC_ims_documentflow_ST.xml files in data flows (ION).
  2. Verify the Result:
    • Document flows should create successfully in data flows (ION).
    • Verify FSM-GFC document flows.

Dependencies: None.

JT-1709687

ION Content and JSON Files Delivery

Latest IPA JSON files and FSM_ION_CONTENT* delivery.

  • JSONFILES_ST record updated in \iefin\wfdata\SampleDocumentTemplate.
  • FSM_ION_CONTENT* record updated in \iefin\plugins\iefinconnector\ipa_content.

Program/Business class/Process affected:

  • Files Updated:
    • \iefin\wfdata\SampleDocumentTemplate
    • \iefin\plugins\iefinconnector\ipa_content\SampleDocumentTemplate

Use these steps to test the enhancement:

  1. Go to Application Administrator > Supply Management > Shared Processes > Sample Document Template.
  2. Open Sample Document.
  3. In the All tab, search for JSONFILES_ST, the record updated with attachment.
  4. 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-1721172

Implement Clean Document ID solution for SyncInventoryAdj_Outbound

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncInventoryAdj_Outbound.lpd.
  • New Required Setup:
    • Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID
    • Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • In Start node added new variables ConfigDocID,ConfigFEG,ITSXML,CrossGLC.
    • Added conditions in node Assign4990,InvAdj_Line.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. Setup. Enable the service "InventoryAdjustmentService" for FSM_ION_SyncInventoryAdj_Outbound.lpd.
  2. Setup. Pass the source GLCCompany and destination AccountingEntity values in Cross Reference :CSFGLCVSDESTAE.
  3. Create and release an Inventory Transaction of type Adjustment.
  4. BOD triggers and Work unit generates successfully without any error for FSM_ION_SyncInventoryAdj_Outbound.lpd BOD.
  5. Verify the Result:
    • If RequiredCleanDocumentID=N then DocID and Accountingentity in concatenation form.
    • If RequiredCleanDocumentID=Y then DocID is InventoryTransaction and Accountingentity is CrossReference destination value.

Dependencies: None.

JT-1710739

Implement Clean Document ID solution for SyncRemitToPartyMaster_Outbound

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncRemitToPartyMaster_Out.lpd
  • New Required Setup:
    • Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.
    • Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG
    • Added new System Configuration Parameter "TriggerBODBasedOnCrossReference”. Default value for the flag is "N". The Value is set to "Y", to enable TriggerBODBasedOnCrossReference
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • In Start node added new variables ConfigDocID,ConfigFEG,TriggerCrossReference,CrossGLC,GLCCompany.
    • Added new nodes Branranch4200,Assign9110,GLC,Branch6780,XML1200,IONOutbox1590.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. Setup: Enable the service "RemitToLocationService" for FSM_ION_SyncRemitToPartyMaster_Out.lpd
  2. Setup: Pass the source GLCCompany and destination AccountingEntity values in Cross Reference :CSFGLCVSDESTAE
  3. Create,Update,Delete a VendorLocation with type remitto.
  4. BOD triggers and Work unit generates successfully without any error for FSM_ION_SyncRemitToPartyMaster_Out.lpd BOD.
  5. Verify the Result:
    • If RequiredCleanDocumentID=N then DocID and Accountingentity in concatenation form.
    • If RequiredCleanDocumentID=Y then DocID is Vendor@@VendorLocation and Accountingentity is CrossReference destination value.

Dependencies: None.

JT-1711595

Implement Clean Document ID solution for SyncRemitToPartyMaster_Out

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncRemitToPartyMaster_Out.lpd
  • New Required Setup:
    • Added new System Configuration Parameter "RequiredCleanDocumentID”. Default value for the flag is "N". When the Value is set to "Y", to enable RequiredCleanDocumentID.

    • Added new System Configuration Parameter "IsMultipleFEG”. Default value for the flag is "N". The Value is set to "Y", to enable IsMultipleFEG.

    • Added new System Configuration Parameter "TriggerBODBasedOnCrossReference”. Default value for the flag is "N". The Value is set to "Y", to enable TriggerBODBasedOnCrossReference
  • New IPA Changes:
    • In Start node added new variables ConfigDocID,ConfigFEG,TriggerCrossReference,CrossGLC,GLCCompany.
    • Added new nodes Branch4200,Assign9110,GLC,Branch6780,XML1200,IONOutbox1590.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. Setup. Enable the service "RemitToLocationService" for FSM_ION_SyncRemitToPartyMaster_Out.lpd.
  2. Setup. Pass the source GLCCompany and destination AccountingEntity values in Cross Reference :CSFGLCVSDESTAE
  3. Create,Update,Delete a VendorLocation with type remitto.
  4. BOD triggers and Work unit generates successfully without any error for FSM_ION_SyncRemitToPartyMaster_Out.lpd BOD.
  5. Verify the Result:
    • If RequiredCleanDocumentID=N then DocID and Accountingentity in concatenation form.
    • If RequiredCleanDocumentID=Y then DocID is Vendor@@VendorLocation and Accountingentity is CrossReference destination value.

Dependencies: None.

JT-1711595

New elements to be added to Sync.Shipment Outbound BOD

Added new elements in Sync.Shipment outbound BOD for Scenario- Local.ly specific to Chile country and customer order flow

Program/Business class/Process affected:

  • Files Changed:
    • FSM_ION_SyncShipment_Outbound
    • WarehouseShipment.busclass
  • Variables Added in JSON: No.
  • IPA Changes:
    • In FSM_ION_SyncShipment_Outbound IPA flow below changes made:
      • Below variables added in start node:
        • CarrierGroup
        • CarrierName
        • CarrierVendor
        • CarrierID
      • Added below javascript in AssignVars node
         if(IntegrationApplication == "Local.ly" && WHShipment["WarehouseDemand"]["DemandSystemCode"] == "OE" && ShipFromPartyCountry == "CL")
 {
 CarrierGroup=VendorGroup
 CarrierName=VendorName
 CarrierVendor=Vendor
 CarrierID=trimLeadingZeros(FinanceEnterpriseGroup)+
 Generic_Delimiter + CarrierGroup + Generic_Delimiter + CarrierVendor
 }
 else
 {
 CarrierGroup=""
 CarrierName=""
 CarrierVendor=""
 CarrierID=""
 }
    • In ShipmentXML node below Xpaths added:
      • SyncShipment/DataArea/Shipment/ShipmentHeader/CarrierParty/PartyIDs/ID<ID accountingEntity={accountingEntity}>{CarrierID}@NoNullTag@</ID>
      • SyncShipment/DataArea/Shipment/ShipmentHeader/CarrierParty/Name <Name>{CarrierName}@NoNullTag@</Name>
  • Integration specific: Yes. These changes are related to Local.ly Integration for Chile country.

Use these steps to test the enhancement:

  1. Setup. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Setup. Enable the service "ShipmentService" for FSM_ION_SyncShipment_Outbound.lpd
  3. Testing Scenario 1:
    1. Create CustomerOrder and release it.
    2. Run the WarehousePickListPrint batch job.
    3. BOD triggers and Work Unit generates without error.
  4. Testing Scenario 2:
    1. After "WarehousePickListPrint" is run go to "WarehouseShipment"
    2. right-click the record and select "Finish", then again right-click and select "Release".
    3. Run "OrderEntryDailyShipmentJournal".
    4. BOD triggers and Work Unit generates.
  5. Verify the result:
    • SyncShipment/DataArea/Shipment/ShipmentHeader/CarrierParty/PartyIDs/ID <ID accountingEntity="A100@@101">A100@@GRP1@@1</ID>
    • SyncShipment/DataArea/Shipment/ShipmentHeader/CarrierParty/Name <Name>Vendor1</Name>

Dependencies: None.

JT-1711510

Scheme ID for Endpointid of customer in SyncInvoice Outbound bod for Local.ly and Country New Zealand

Program/Business class/Process affected:

  • File Changed: FSM_ION_SyncInvoice_Outbound.lpd
  • Variable Added in JSON: No.
  • IPA Changes: In FSM_ION_SyncInvoice_Outbound IPA flow below changes made:

    • Assign1740:Modified javascript."Local.ly" && AddressCode != "" && AddressCode_PostalAddress_Country =="NZ" . AUschemeID = "GLN";

  • Integration Specific: Yes. These changes are related to Local.ly Integration specific to New Zealand (NZ).

Use these steps to test the enhancement:

  1. Setup. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked
  2. Setup. Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.
  3. Setup. Go to Service Definition and Enable "ReceivableInvoiceService" for "FSM_ION_SyncInvoice_Outbound.lpd" Processes.
  4. Testing Scenario 1:
    1. Create ReceivableInvoice and Release it.
    2. BOD triggers and Work unit generates with respective newly added element.
  5. Testing Scenario 2:
    1. Create BillingInvoice Release it.
    2. Run InvoiceVerificationReport.
    3. Run InvoiceAndRegisterPrint.
    4. Run SubSystemUpdate.
    5. BOD triggers and Work unit generates with respective newly added element.
  6. Verify the Result. In InvoiceHeader/CustomerParty/PartyIDs/EndPointID@schemeID="GLN" added.

Dependencies: None.

JT-1715614

Scheme ID for Endpointid of customer in SyncInvoice Outbound bod for Local.ly and Country Netherlands

Program/Business class/Process affected:

  • File Changed: FSM_ION_SyncInvoice_Outbound.lpd
  • Variable Added in JSON: No
  • IPA Changes: In FSM_ION_SyncInvoice_Outbound IPA flow below changes made:
    • Assign1740: Modified javascript. 
      "Local.ly" && AddressCode != "" && AddressCode_PostalAddress_Country =="NL" . AUschemeID = "NL:KVK";
  • Integration Specific: Yes. These changes are related to Local.ly Integration specific to Netherlands (NL).

Use these steps to test the enhancement:

  1. Setup. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.
  3. Go to Service Definition and Enable "ReceivableInvoiceService" for "FSM_ION_SyncInvoice_Outbound.lpd" Processes
  4. Testing Scenario 1:
    1. Create ReceivableInvoice and Release it.
    2. BOD triggers and Work unit generates with respective newly added element.
  5. Testing Scenario 2:
    1. Create BillingInvoice Release it.
    2. Run InvoiceVerificationReport
    3. Run InvoiceAndRegisterPrint
    4. Run SubSystemUpdate
    5. BOD triggers and Work unit generates with respective newly added element.
  6. Verify the Result. In InvoiceHeader/CustomerParty/PartyIDs/EndPointID@schemeID="NL:KVK" added.

Dependencies: None.

JT-1712142

Use EAM Work Order and Work order Activity on Inv Transaction Line for Performance

Program/Business class/Process affected:

  • Files Changed:
    • FSM_ION_SyncMaintenanceOrder_Inbound
    • Added new fields in LMTxnWDLine
    • Added new fields in UpdateWDLine

Use these steps to test the enhancement:

  1. Testing configuration:
    • In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    • In Channels Administrator, Activate the respective ION Inbox Receivers for FSM_ION_SyncMaintenanceOrder_Inbound.
    • Set value "Y" in System Configuration Parameter "UpdateShipDateTimeFromWO"
    • Set value "N" in System Configuration Parameter "UpdateShipDateTimeFromWO"
  2. When the bod is processed, Work Unit is triggered.
  3. EAMWorkOrder is Updated.
  4. When the UpdateShipDateTimeFromWO parameter flag set to N EstimatedTransactionDate should not update.

Dependencies: None.

JT-1676382

FSM_ION_SyncInventoryAdj_Outbound work unit fails with error ‘"ICC_ITEM_GROUP" is not defined.’

Program/Business class/Process affected:

  • Files Changed: FSM_ION_SyncInventoryAdj_Outbound.lpd
  • New Required Setup : No.
  • New Variable Added in JSON: No.
  • IPA Change: Added condition in AssignVars,Assign_ICT_Line,InvAdj_Line.
  • Integration Specific: No.

Use these steps to test the enhancement:

  1. Setup In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Setup Enable the service "InventoryAdjustmentService" for FSM_ION_SyncInventoryAdj_Outbound.lpd
  3. Create and release an InventoryTransaction of type InventoryAdjustment.
  4. BOD triggers and Work unit generates successfully without any error for FSM_ION_SyncInventoryAdj_Outbound.lpd BOD.
  5. Verify the Result :
    • When InventoryLocation.EAMLocation is EAMLocation then workunit should be generated without errors.
    • Undefined value should not come in XPath SyncInventoryAdjustment/DataArea/InventoryAdjustment/InventoryAdjustmentLine/TransactionDateTime when IntegrationApplication is Locally.
    • Passed InventoryTransaction.TransactionUOM in XPath SyncInventoryAdjustment/DataArea/InventoryAdjustment/InventoryAdjustmentLine/Quantity

Dependencies: None.

JT-1698564