BOD Connectors

This section contains enhancements in Infor Financials and Supply Management.

Add New Elements and Map Accordingly for SyncAssetTransaction Outbound BOD for Local.ly

Local.ly changes required to Add New Elements and Map Accordingly for SyncAssetTransaction Outbound bod

Program/Business class/Process affected:
  • Files Changed: FSM_ION_SyncAssetTransaction_Out.lpd
  • IPD change:
    • Added new mappings to both header and line XMLs
    • Added javascript code in 'Assign' node
Use these steps to test the enhancement:
  1. Create Asset.
  2. Release Asset.
  3. Verify WorkUnit record.
  4. Verify these x-paths:
    • AssetTransactionHeader/LastModificationDateTime
    • AssetTransactionHeader/Status/EffectiveDateTime
    • AssetTransactionLine/AssetBookCode

Dependencies: None

JT-1677694

Add New Elements and Map Accordingly for SyncAssetMaster outbound BOD For Local.ly

Add New Elements and Map Accordingly for SyncAssetMaster outbound BOD For Local.ly

Program/Business class/Process affected:
  • Files Changed: FSM_ION_SyncAssetMaster_Out.lpd
  • IPA Changes:
    • Added these variables in 'start' node: AssetBook,AssetLife,AssetMethod,BookPostingBook,BookDescription,FirstandLastYear
    • Created 'AssetBook'node and Assign4770 nodes
    • Added following code in Assign4770
      AssetBook = AssetBook_Book;
AssetLife = AssetBook_Life;
AssetMethod =AssetBook_Method;
BookPostingBook = AssetBook_BookPostingBook;
BookDescription =AssetBook_BookDescription;
if(AssetBook_FirstAndLastYear=="M")
{
FirstandLastYear ="Middle";
}
else if(AssetBook_FirstAndLastYear=="F")
{
FirstandLastYear ="First";
}
else if(AssetBook_FirstAndLastYear=="L")
{
FirstandLastYear ="Last";
}
else if(AssetBook_FirstAndLastYear=="C")
{
FirstandLastYear ="CompletelyDepreciated";
}
else if(AssetBook_FirstAndLastYear=="P")
{
FirstandLastYear ="PostRecovery";
}
BookSeqNumber = BookSeqNumber+1;
if(IntegrationApplication == "Local.ly")
{
FixedAsset_XML +=
<AssetBook SeqNumber = {BookSeqNumber}>
<AssetBookCode accountingEntity={accountingEntity}>{AssetBook}@NoNullTag@</AssetBookCode>
<Description>{BookDescription}@NoNullTag@</Description>
<PostingBookIndicator>{BookPostingBook}@NoNullTag@</PostingBookIndicator>
<AssetLife>{AssetLife}@NoNullTag@</AssetLife>
<DepreciationMethodCode listID="LinearDepreciation">{AssetMethod}@NoNullTag@</DepreciationMethodCode>
<DepreciationStatusCode>{FirstandLastYear}</DepreciationStatusCode>
</AssetBook>
}
  • Added following in XML_Asset:
    <FixedAsset>{FixedAsset_XML}</FixedAsset>
Use these steps to test the enhancement:
  1. Create Asset.
  2. Release Asset.
  3. Verify generated workunit record.
  4. Verify this path: SyncAssetMaster/DataArea/AssetMaster/FixedAsset/AssetBook

Dependencies: None.

JT-1668053

Add New Elements and Map Accordingly for SyncAssetTransaction Outbound BOD for Local.ly

Add New Elements and Map Accordingly for SyncAssetTransaction Outbound BOD for Local.ly

Program/Business class/Process affected:
  • Files Changed: FSM_ION_SyncAssetTransaction_Out.lpd
  • IPA Change:
    • Added following variables in Start node : IntegrationApplication,documentDate,CurrDate
    • Added following code in Assign node:
      a.documentDate=CreationDate
substring(CreationDate, 0,4) + "-" + substring(CreationDate, 4,6) + "-" + substring(CreationDate, 6,8);
b.if (IntegrationApplication == "Local.ly" )
{
CurrDate = documentDate;
}
    • Added following node in header XML: <DocumentDateTime>{CurrDate}@NoNullTag@</DocumentDateTime>
Use these steps to test the enhancement:
  1. Create Asset.
  2. Release Asset.
  3. Verify WorkUnit record.
  4. Verify following x-path: AssetTransaction/AssetTransactionHeader/DocumentDateTime

Dependencies: None.

JT-1668032

Add SupplierParty Node to Sync Receive delivery outbound bod for Local.ly Integration

Added SupplierParty Node to Sync Receive delivery outbound bod for Local.ly Integration

Program/Business class/Process affected:
  • Files Changed: FSM_ION_SyncReceiveDelivery_Out lpd.
  • New Required Setup: None.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • In Start Node added following variables: SupplierpartyXML, VendorAddressLine1, VendorAddressLine2, VendorAddressLine3, VendorAddressLine4, VendorMunicipality, VendorStateProvince, VendorCountry, VendorPostalCode.
    • Added node Assign1820, Assign9590
    • Added Transaction nodes for Vendor, VendorAddress
  • Integration Specific: Yes, for "Local.ly".
Use these steps to test the enhancement:
  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. For Outbound BOD, Enable the Service Definition "PurchaseOrderReceiptService" for FSM_ION_SyncReceiveDelivery_Out.
  3. Ceate PurchaseOrder and Release it.
  4. Create and Release a PurchaseOrderReceipt for it and release.
  5. BOD will trigger and Work unit will generate successfully without any error.
  6. Verify the Result. SyncReceiveDelivery/DataArea/ReceiveDelivery/ReceiveDeliveryHeader/SupplierParty node added for Local.ly Integration.

Dependencies: None.

JT-1676823

Changes needs to be made on MASS BOD screen with respect to FSM-GRC_PI integration

Changes needs to be made on MASS BOD screen with respect to FSM-GRC_PI integration.

Program/Business class/Process affected:
  • bl/BODDataInitialLoad
  • ui/BODDataInitialLoad
Use these steps to test the enhancement:
  1. Go To Application Administrator > Financials > Shared Processes > BOD Integrations.
  2. Click Mass BOD Publish.
  3. Open Mass BOD Publish.
  4. Create record.
  5. Select Type as "Integration Wise" and Select Integration as "GRC-PI"
  6. Following list of BODs will display.
    • Sync.CustomerPartyMaster Outbound BOD
    • Sync.SupplierPartyMaster Outbound BOD
    • Sync.ChartOfAccount Outbound BOD
    • Sync.ItemMaster Outbound BOD
  7. Trigger list of BODs individually by selecting respective criteria.
  8. Define the service and attach the processes.

Dependencies: None.

JT-1670555

FSM Shipment Outbound to EAM WO

FSM Shipment Outbound to EAM WO. New SplitShipment changes and CleanDocumentID changes for FSM_ION_SyncShipment_Outbound

Program/Business class/Process affected:
  • Files Changed:
    • FSM_ION_SyncShipment_Outbound.ipd
    • PfiConfigurationProperty.xml
  • New Required Setup:
    • Added new parameters: SplitShipment,RequisitionShipment,RequiredCleanDocumentID,IsMultipleFEG.
    • Pass the value Y/N to enable or disable the above parameters.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • Added variables in Start Node: RequisitionShipmentFlag, SplitShipment, GLCCompany, ConfigDocID ,ConfigFEG, ShipmentLineXML, ShipmentLine_XML,ReqLineFlag, EAMWorkOrderActivityID, EAMWorkOrderID, RequisitionID, RequisitionNum, ReqLineNum
    • Added new branch condition and assign nodes for cleandocumentID changes:Branch6060,Assign8060,Branch7540,Assign1100
    • Branch5220 is added: When IntegratingApplication = "EAM", RequisitionShipment ="Y", SplitShipment = "Y", new flow is added for triggering one bod per line.
    • When SplitShipment = "Y", RequisitionLine.EAMWorkOrderActivity and RequisitionLine.EAMWorkOrder fields are passed in ShipmentHeader XML in following XPAths:
      • ShipmentHeader/UserArea/Property/NameValue/@name = "eam.WOActivityID" @type = "StringType" - EAMWorkOrderActivity
      • ShipmentHeader/DocumentReference/DocumentID/ID/@accountingEntity @location - EAMWorkOrder
    • Added Requisition value in XPath ShipmentHeader/DocumentReference/DocumentID/ID and ShipmentLine/DocumentReference/DocumentID/ID and Passed RequisitionLine number in ShipmentLine/DocumentReference/LineNumber.
  • Integration Specific: Yes. These changes are related to EAM integration.
Use these steps to test the enhancement:
  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. For Outbound BOD, Enable the Service Definition "ShipmentService" and Process "FSM_ION_SyncShipment_Outbound".
  3. Assign value "EAM" to "IntegratingApplication" parameter in System configuration.
  4. In System Configuration, pass parameter = Y/N for "SplitShipment" and "RequisitionShipment" parameters.
  5. Create Requisition with EAMWorkOrder values.
  6. Release Requisition.
  7. Run WarehousePickListPrint batch job.
  8. Navigate to WarehouseShipments and Finish>>Release the shipment record.
  9. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncShipment_Outbound BOD.
  10. Verify the Result:
    • ShipmentHeader/UserArea/Property/NameValue/@name = "eam.WOActivityID" @type = "StringType" - EAMWorkOrderActivity
    • hipmentHeader/DocumentReference/DocumentID/ID/@accountingEntity @location - EAMWorkOrder.
    • Requisition value in XPath ShipmentHeader/DocumentReference/DocumentID/ID and ShipmentLine/DocumentReference/DocumentID/ID and Passed RequisitionLine number in ShipmentLine/DocumentReference/LineNumber.
    • When IntegratingApplication = "EAM", RequisitionShipment ="Y", SplitShipment = "Y", new flow is added for triggering one bod per line.
    • When SplitShipment = "Y", RequisitionLine.EAMWorkOrderActivity and RequisitionLine.EAMWorkOrder fields are passed in ShipmentHeader XML in following XPAths:
      • ShipmentHeader/UserArea/Property/NameValue/@name = "eam.WOActivityID" @type = "StringType" - EAMWorkOrderActivity
      • ShipmentHeader/DocumentReference/DocumentID/ID/@accountingEntity @location - EAMWorkOrder
    • When SplitShipment = N, first RequisitionLine.EAMWorkOrder, and RequisitionLine.EAMWorkOrderActivity are added in ShipmentHeader XML.

Dependencies: None.

JT-1646999

FSM-Local.ly: Changes required in SyncCreditTransfer_Out BOD for Poland && Netherlands

FSM-Local.ly: Changes required in SyncCreditTransfer_Out BOD for Poland && Netherlands

Program/Business class/Process affected:
  • Files Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • IPA Change:Added following code in Assign5940 for both "PL" and "NL" countries.
    if(RemitTolocation!="" && VLoc_Country!="")
{
if((IntegrationApplication == "Local.ly" && AEAddressCountry == "PL") &&
(VLoc_Country=="PL"))
{
ChargeBearerCode = "Shared";
}
else if((IntegrationApplication == "Local.ly" && AEAddressCountry == "PL") &&
(VLoc_Country!="PL" ) && (GetPayablesInvoice_DerivedMemOfEu == "true") && (GetPayablesInvoice_DerivedVenLocMemOfEu=="true"))
{
ChargeBearerCode ="Service Level";
}
else if((IntegrationApplication == "Local.ly" && AEAddressCountry == "PL") && (VLoc_Country!="PL" ) &&
(GetPayablesInvoice_DerivedMemOfEu == "true") && (GetPayablesInvoice_DerivedVenLocMemOfEu!="true"))
{
ChargeBearerCode ="Debtor";
}
}
else if(VendorAddressCountry!="")
{
if((IntegrationApplication == "Local.ly" && AEAddressCountry == "PL") &&
(VendorAddressCountry=="PL"))
{
ChargeBearerCode = "Shared";
}
else if((IntegrationApplication == "Local.ly" && AEAddressCountry == "PL") && (VendorAddressCountry!="PL" ) && (GetPayablesInvoice_DerivedMemOfEu == "true") && (GetPayablesInvoice_DerivedVenMemofEu=="true"))
{
ChargeBearerCode ="Service Level";
}
else if((IntegrationApplication == "Local.ly" && AEAddressCountry == "PL") && (VendorAddressCountry!="PL" ) &&
(GetPayablesInvoice_DerivedMemOfEu == "true") && (GetPayablesInvoice_DerivedVenMemofEu!="true"))
{
ChargeBearerCode ="Debtor";
}
}
if(RemitTolocation!="" && VLoc_Country!="")
{
if((IntegrationApplication == "Local.ly" && AEAddressCountry == "NL") &&
(VLoc_Country=="NL"))
{
ChargeBearerCode = "Shared";
}
else if((IntegrationApplication == "Local.ly" && AEAddressCountry == "NL") && (VLoc_Country!="NL" ) &&
(GetPayablesInvoice_DerivedMemOfEu == "true") && (GetPayablesInvoice_DerivedVenLocMemOfEu=="true"))
{
ChargeBearerCode ="Service Level";
}
else if((IntegrationApplication == "Local.ly" && AEAddressCountry == "NL") && (VLoc_Country!="NL" ) &&
(GetPayablesInvoice_DerivedMemOfEu == "true") && (GetPayablesInvoice_DerivedVenLocMemOfEu!="true"))
{
ChargeBearerCode ="Debtor";
}
}
else if(VendorAddressCountry!="")
{
if((IntegrationApplication == "Local.ly" && AEAddressCountry == "NL") &&
(VendorAddressCountry=="NL"))
{
ChargeBearerCode = "Shared";
}
else if((IntegrationApplication == "Local.ly" && AEAddressCountry == "NL") && (VendorAddressCountry!="NL" ) && (GetPayablesInvoice_DerivedMemOfEu == "true") && (GetPayablesInvoice_DerivedVenMemofEu=="true"))
{
ChargeBearerCode ="Service Level";
}
else if((IntegrationApplication == "Local.ly" && AEAddressCountry == "NL") && (VendorAddressCountry!="NL" ) &&
(GetPayablesInvoice_DerivedMemOfEu == "true") && (GetPayablesInvoice_DerivedVenMemofEu!="true"))
{
ChargeBearerCode ="Debtor";
}
}
Use these steps to test the enhancement:
  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Do required setup for CreditTransfer flow.
  3. Create PayablesInvoice and release.
  4. Run'Perform Cash Application' job.
  5. Check CashRequiremnetsResults records.
  6. Run ElectronicPaymentCreation job/
  7. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCreditTransfer_Out BOD.
  8. Verify the Result :
    • X-path: SyncCreditTransfer/DataArea/CreditTransfer/CreditTransferPayment/PaymentTransaction/ChargeBearerCode

Dependencies: None.

JT-1667799

SM-Local.ly: Changes required in SyncCreditTransfer_Out BOD for Australia

Changes required for SyncCreditTransfer_Out BOD for local.ly and for Australia country

Program/Business class/Process affected:
  • Files Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • IPA Change:
    • Added javascript code in Assign5940,Assign6300 for both "AU" country.
    • New mapping added in line XML
Use these steps to test the enhancement:
  1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Do required setup for CreditTransfer flow.
  3. Create PayablesInvoice and release.
  4. Run'Perform Cash Application' job.
  5. Check CashRequiremnetsResults records.
  6. Run ElectronicPaymentCreation job.
  7. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCreditTransfer_Out BOD.
  8. Verify the Result: X-path:SyncCreditTransfer/DataArea/CreditTransfer/CreditTransferPayment/Description

Dependencies: None.

JT-1681302

ION Content and JSON Files Delivery

Latest IPA JSON files and FSM_ION_CONTENT* delivery
  • JSONFILES_ST record updtaed 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

Use these steps to test the enhancement:
  1. Go to Application > 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-1685501

Load supplier Invoice changes for Local.ly

Creating PayablesInvoiceAddOnChargeImport records for local.ly

Program/Business class/Process affected:
  • Files Changed: FSM_ION_LoadSupplierInvoice_Inbound
    • Added new variable in start Node.

    • Added "LocallyLineAOC" transaction node.

    • Added new Assign6230 node.
    • Added new Assign2290 node
  • New Required Setup: None.
Use these steps to test the enhancement:
  1. Create channels for Load.SupplierInvoice_Inbound BOD.
  2. Set value IntegrationApplication to "Local.ly" in System Configuration.
  3. Send InvoiceCharge details in line level.
  4. Send valid XML and record should create in PayablesInvoiceAddOnChargeImport.
  5. Verify the Result:
    1. Check record in MatchInvoiceImport.
    2. Workunit should create without any errors.

Dependencies: None.

JT-1580630

Remove Accounting Entity value Attribute for Item Id of ShipmentItem in Sync Shipment Outbound bod for Local.ly and country Poland

Removed AccountingEntity for Sync Shipment Outbound bod for Local.ly and country Poland.

Program/Business class/Process affected:
  • Files Changed: FSM_ION_SyncShipment_Outbound.lpd
  • New Required Setup: None.
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • Passed empty value for Accounting entity in the X-path SyncShipment/ShipmentItem/ItemID/ID --------> accountingEntity for Local.ly
  • Integration Specific: Yes. Local.ly.
Use these steps to test the enhancement:
  1. Enable the service "ShipmentService" for FSM_ION_SyncShipment_Outbound.lpd.
  2. Create Requisition and Release it.
  3. Run WarehousePickListPrint batch job.
  4. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncShipment_Out BOD.
  5. Verify the Result. Accounting entity element in the X-path SyncShipment/ShipmentItem/ItemID/ID.

Dependencies: None.

JT-1675072

Sync Invoice Outbound Bod Changes for Local.ly Integration

Sync Invoice Outbound Bod Changes for Local.ly Integration.

Program/Business class/Process affected:
  • 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 following changes made:
    • In Assign5720 : Javascript modified ,For IntegrationAppicationnLocal.ly LineQuantity mapped to BillingInvoiceLine.Quantity.
    • In Assign9990 : Javascript modified ,LineQuantity directly mapped to BillingInvoiceLine.Quantity.
  • Integration Specific: Yes. These changes are related to Local.ly Integration.
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" and "BillingInvoiceService" for "FSM_ION_SyncInvoice_Outbound.lpd" Processes.
  4. Create BillingInvoice Release it.
  5. Run InvoiceVerificationReport.
  6. Run InvoiceAndRegisterPrint.
  7. Run SubSystemUpdate.
  8. BOD will trigger and Work unit will generate With respective changes.

    InvoiceLine/Quantity

    For BillingInvoiceService: Create BillingInvoice and Release it.

Dependencies: None.

JT-1674709