BOD Connectors

This section contains enhancements in Infor Financials and Supply Management.

Add New Elements For Sync Payable Tracker Outbound Bod for Local.ly and for Country Australia

Add New Elements For Sync Payable Tracker Outbound Bod for Local.ly and for Country Australia

Program/Business class/Process affected:
  • Files changed: FSM_ION_SyncPayableTracker_Out.lpd
  • New Required Setup: No.
  • New Variable Added in JSON: No.
  • New IPA Changes:Yes.
    • Added the these new nodes :Assign6560,Branch2980,PayInvDistribution,Branch9040,TaxCode,Assign2750
    • Added Xml initialization and seqencenumber initialization in Assign6560
    • Added this code in Assign 2750
      if(IntegrationApplication == "Local.ly" && AE_DerivedAccountingEntityCountry == "AU" && PayInvDistribution_TaxCode!="")
{
TaxCode=PayInvDistribution_TaxCode;
TaxCodeDes = TaxCode_Description;
TaxRate = PayInvDistribution_TaxRate;
TaxInvoiceCurrency=PayablesInvoice_InvoiceCurrency;
TaxPayCurrency = PayablesInvoice_PayCurrency;
TaxReportCurrencyOne=PayablesInvoice_DerivedReportCurrencyOne;
TaxBasisAmount = PayInvDistribution_TaxableAmount;
TaxBasisBaseAmount =PayInvDistribution_TaxableAmount;
TaxBasisReportAmount = PayInvDistribution_TaxableAmount*PayInvDistribution_DistributionAmount_ReportAmount1_EnteredCurrencyRate;
TaxAmount =PayInvDistribution_DistributionAmount_CurrencyAmount;
TaxBasisEnteredAmount=PayInvDistribution_DistributionAmount_FunctionalAmount_EnteredCurrencyAmount;
TaxReportAmt = PayInvDistribution_DistributionAmount_ReportAmount1_EnteredCurrencyAmount;
}
TaxSeqNumber = TaxSeqNumber+1;
if(IntegrationApplication == "Local.ly" && AE_DerivedAccountingEntityCountry == "AU" && PayInvDistribution_TaxCode!="")
{
Tax_XML +=
 <Tax sequenceNumber={TaxSeqNumber}>
 <ID>{TaxCode}@NoNullTag@</ID>
 <BasisAmount currencyID={TaxInvoiceCurrency}>{TaxBasisAmount}@NoNullTag@</BasisAmount>
 <BasisBaseAmount currencyID={TaxPayCurrency}>{TaxBasisBaseAmount}@NoNullTag@</BasisBaseAmount>
 <BasisReportAmount currencyID={TaxReportCurrencyOne}>{TaxBasisReportAmount}@NoNullTag@</BasisReportAmount>
 <Calculation>
 <RateNumeric>{TaxRate}@NoNullTag@</RateNumeric>
 </Calculation>
 <Description>{TaxCodeDes}@NoNullTag@</Description>
 <Amount currencyID={TaxInvoiceCurrency}>{TaxAmount}@NoNullTag@</Amount>
 <BaseAmount currencyID={TaxPayCurrency}>{TaxBasisEnteredAmount}@NoNullTag@</BaseAmount>
 <ReportAmount currencyID={TaxReportCurrencyOne}>{TaxReportAmt}@NoNullTag@</ReportAmount>
 <WithheldIndicator>0</WithheldIndicator>
 </Tax>
}
    • Added {Tax_XML} in 'PayTrackerLine'
  • Integration Specific: Yes. These changes are related to Local.ly Integration and for Country Australia.
Use this information to test the enhancement:
  1. Setup: In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
  2. Setup: Enable Service Definition and processes for Sync.PayableTracker Out BOD.
  3. Testing goal: Supposed to trigger Sync.PayableTracker Outbound BOD For 'Payment void stop pay update' job.
  4. Create and release PayablesInvoice.
  5. Run 'Perform Cash Requirements' JOB.
  6. Run 'ElectronicPaymentCreation'
  7. Run 'Payment Close'
  8. Verify generated work unit record.
  9. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncPayableTracker_Out BOD.
  10. Goto 'CashLedgerTransaction' busclass and click 'void' on the record that is generated to change status.
  11. Run 'Payment void stop pay update' job with update 'yes'.
  12. Verify generated work unit record.
  13. Verify the Result: Verify Tax nodes added or not

Dependencies: None.

JT-1659951

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

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

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 below changes have been made:
      • In Start node: AUschemeID variable Added
      • Assign1740:Modified javascript."Local.ly" && AddressCode != "" && AddressCode_PostalAddress_Country =="AU" . AUschemeID = "AU:VAT";
      • XML_INVHDR:InvoiceHeader/CustomerParty/PartyIDs/EndPointID@schemeID={AUschemeID} added
  • Integration Specific: Yes. These changes are related to Local.ly Integration specific to Australia(AU).
Use this information to test the enhancement:
  1. Setup:
    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.
  2. Testing ReceivableInvoiceService:
    • Option 1:
      1. Create ReceivableInvoice and Release it.
      2. BOD will trigger and Work unit will generate With respective newly added element.
    • Option 2:
      1. Create BillingInvoice Release it.
      2. Perform InvoiceVerificationReport.
      3. Perform InvoiceAndRegisterPrint.
      4. Perform SubSystemUpdate.
      5. BOD will trigger and Work unit will generate With respective newly added element.
  3. Verify the Result: In InvoiceHeader/CustomerParty/PartyIDs/EndPointID@schemeID="AU:VAT" added

Dependencies: None.

JT-1658101

EAM Direct Material Requisition Inbound Sourced by Item Type

EAM Direct Material Requisition Inbound Sourced by Item Type: In FSM_ION_ProcessRequisition_In ,RequisitionLine/RequiredDeliveryDateTime populates FSM (RequisitionLine.RequestedDeliveryDate).

Program/Business class/Process affected:
  • Files Changed:
    • FSM_ION_ProcessRequisition_In
    • PfiConfigurationProperty.xml
  • New Required Setup:
    • Added new configuration parameter REQDATE. If REQDATE = Y, value from below xpath defaulting in Requisition line: BOD Element: EAM Requisition/RequisitionLine/RequiredDeliveryDateTime populates FSM (RequisitionLine.RequestedDeliveryDate).
  • New Variable Added in JSON: No.
  • New IPA Changes:
    • Added new configuration parameter REQDATE.
    • In Assign node "Ln_variables" added javascript code to read the RequestedDeliveryDate value.
  • Integration Specific: No.
Use this information to test the enhancement:
  1. Setup:
    1. In the Finance Enterprise Group, in Options, select the BOD Trigger check box.
    2. In the Channels Administrator, activate the respective ION Inbox Receivers for FSM_ION_ProcessRequisition_In.
  2. When FSM_ION_ProcessRequisition_In BOD is processed, Work Unit is triggered.
  3. A requisition is created and released.
  4. Verify the Result:
    1. Verify that a requisition is created and released without any errors.
    2. If Configuration parameter REQDATE == "Y", then the value from this xpath is the default in the Requisition line: BOD Element: EAM Requisition/RequisitionLine/RequiredDeliveryDateTime populates FSM (RequisitionLine.RequestedDeliveryDate).

Dependencies: None.

JT-1646997

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

Local.ly Changes required in SyncCreditTransfer_Out BOD for Netherlands

Program/Business class/Process affected:
  • Files Changed:
    • PayablesInvoice.busclass
    • FSM_ION_SyncCreditTransfer_Out.lpd
  • IPA Change: Added Javascript code in Assign5940 for "NL" country.
Use this information to test the enhancement:
  1. Setup: 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-1659925

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

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

Program/Business class/Process affected:
  • Files changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • IPA changed: Added javascript code in Assign5940 for both "PL" country.
Use this information to test the enhancement:
  1. Setup: 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-1666854

FSM_Local.ly: Changes required in SyncCreditTransfer_Outbound for Poland (PL)

FSM_Local.ly: Changes required in SyncCreditTransfer_Outbound for Poland (PL)

Program/Business class/Process affected:
  • Files Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • IPA Change:
    • Added following variables in 'start' node
      • FirstAgentPaymentMethodCode
      • CreditTransferType
    • Added below code in Assign5940
      if(IntegrationApplication == "Local.ly" && AEAddressCountry=="PL")
{
ID_scheme = "BankPartyIdentification";
FirstAgentPaymentMethodCode = BankTransactionCode;
}
if(IntegrationApplication == "Local.ly" && AEAddressCountry == "PL")
{
if((GetPayablesInvoice_DerivedMemOfEu == "true") && (GetPayablesInvoice_DerivedVenMemofEu=="true" || GetPayablesInvoice_DerivedVenLocMemOfEu=="true"))
{
CreditTransferType="SEPA";
}
else
{
CreditTransferType="URGP";
}
}
Use this information to test the enhancement:
  1. Setup: 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-paths:
      • CreditTransferHeader/InitiatingParty/PartyIDs/ID/@schemeName
      • CreditTransferPayment/DebtorParty/PartyIDs/ID/@schemeName
      • CreditTransferPayment/FirstAgentPaymentMethodCode
      • CreditTransferPayment/CreditTransferAgreement/CreditTransferType

Dependencies: None.

JT-1664745

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:
  • \iefin\wfdata\SampleDocumentTemplate.
  • \iefin\plugins\iefinconnector\ipa_content\SampleDocumentTemplate.
Use this information 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-1672033

Sync EAM BOD with FSM Maintenance Order Table

New Field mappings in EAMWorkOrder and EAMWOrkOrderActivity in FSM_ION_SyncMaintenanceOrder_Inbound.

Program/Business class/Process affected:
  • Files Changed:
    • EAMWorkOrder.busclass UI
    • EAMWorkOrderActivity.busclass UI
    • FSM_ION_SyncMaintenanceOrder_Inbound
  • New Required Setup: No.

  • New Variable Added in JSON: No

  • LPL Changes:
    • Added EAMCompany under Main is a Form in EAMWorkOrder.busclass UI
    • Added following fields under EAMWorkOrderActivityForm is a Form in EAMWorkOrderActivity.busclass UI : EAMScheduledStartDate, EAMUserDate1, EAMUserDate2, EAMUserDate3, EAMUserDate4, EAMUserDate5, EAMUserField01, EAMUserField02, EAMUserField03, EAMUserField04, EAMUserField05, EAMUserNum01, EAMUserNum02, EAMUserNum03, EAMUserNum04
  • IPA Changes:
    • Added new variables in start node: EAMScheduledStartDate, EAMUserDate1, EAMUserDate2, EAMUserDate3, EAMUserDate4, EAMUserDate5, EAMUserField01, EAMUserField02, EAMUserField03, EAMUserField04, EAMUserField05, EAMUserNum01, EAMUserNum02, EAMUserNum03, EAMUserNum04, idx6,UALineLen, textName6, textValue6, SplitCompany, EAMCompany.
    • Mapped MaintenanceOrder/MaintenanceOrderHeader/DocumentID/ID/@accountingEntity to EAMCompany in Assign870 and CleanDocID code for EAMCompany.
    • Passed EAMCompany value in "WOCreate" and "WOUpdate".
    • Mapped the variables form XPath MaintenanceOrder/MaintenanceOrderHeader/UserArea/Property/NameValue in "Assign7200" and "Assign3280".
    • Passed below values in "WOActivityUpdate" and "EAMWOActivity" EAMScheduledStartDate, EAMUserDate1, EAMUserDate2, EAMUserDate3, EAMUserDate4, EAMUserDate5, EAMUserField01, EAMUserField02, EAMUserField03, EAMUserField04, EAMUserField05, EAMUserNum01, EAMUserNum02, EAMUserNum03, EAMUserNum04.
  • Integration Specific: Yes. These changes are related to "PLL Integration - FSM/EAM".
Use this information to test the enhancement:
  1. Setup:
    1. In FinanceEnterpriseGroup, "BODtrigger" check box should be checked.
    2. In Channels Administrator, Activate the respective ION Inbox Receivers for FSM_ION_SyncMaintenanceOrder_Inbound.
  2. When the bod is processed, Work Unit will be triggered.
  3. EAMWorkOrder will be Created or Updated with EAMWorkOrder and EAMWOrkOrderActivity fields.
  4. Verify the below fields:
    1. EamWorkOrder.EAMCompany
    2. EAMWorkOrderActivity: EAMScheduledStartDate, EAMUserDate1, EAMUserDate2, EAMUserDate3, EAMUserDate4, EAMUserDate5, EAMUserField01, EAMUserField02, EAMUserField03, EAMUserField04, EAMUserField05, EAMUserNum01, EAMUserNum02, EAMUserNum03, EAMUserNum04

Dependencies: None.

JT-1652370

Sync.LCLTaxReport Outbound BOD - AGR Custom flow.

Updated the Standard Flow with GHR Custom Flow.

Program/Business class/Process affected:
  • Files Changed: FSM_ION_SyncLCLTaxReport.lpd
  • New Required Setup: No
  • New Variable Added in JSON: No
  • New IPA Changes:
    • In start node added new variable WHCode,HoldCode.
    • Added conditions in node Assign8910.
  • Integration Specific: Local.ly Integration.
Use this information to test the enhancement:
  1. Setup:
    1. Enable the service "TaxReportService" for FSM_ION_SyncLCLTaxReport _Out.lpd.
    2. In SystemConfiguration give the value of IntegrationApplication == "Local.ly"
  2. Create a Payablesinvoice with tax and PayablesInvoice of type Credit memo and release it. Do the payment for the Invoice by performing actions:
    1. Perform cash Requirements,
    2. Electronic Payment Creations
    3. PaymentClose
  3. Run Vat Return Report batch Job. BOD will trigger and Work unit will generate successfully.
  4. Verify the Result: TaxWithheld XML would generate if IncomeWithholdingCode starts with "IVA".

Dependencies: None.

JT-1661175