BOD Connectors CU69

This section contains enhancements in Inor CloudSuite Financials for 11.0.69.0.

Assigning Journal References to SSJE BODs

Added LPL code to trigger Sync.SourceSystemJournalEntry Outbound BOD when AssignJournalReferenceNumber batch job is performed and Added JournalReferenceNumber field in new XPath for Sync.SourceSystemJournalEntry

Program/Business class/Process affected:

  1. Files Changed:
    • FSM_ION_SyncSourceSystemJournalEntry_Out.lpd
    • GeneralLedgerJournalControl.busclass
    • GeneralLedgerJournalControlRef.busclass
  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:
    • Added Variable: JRNumber
    • Node GLTRN_VAR changed: if IntegrationApplication is "Local.ly" and CountryCode is France and AssignJournalReferenceNumber batch job is performed then JRNumber will be the JournalReferenceNumber value otherwise JRNumber will be empty
  5. Integration Specific: Yes

    These changes are related to Localization Services integration for France.

Use these steps to test the enhancement:

  1. Setup:
    • In FinanceEnterpriseGroup, select the BODtrigger check box.
    • Enable the GLJournalControlService service definition.
  2. How to Test:
    • Select Financials > Global Ledger > Processing > Reporting Basis > Reporting Basis then select ReportingBasis and Year.
  3. Verify the Result:
    1. Check this path for JournalReferenceNumber:Now Perform AssignJournalReferenceNumber batch job then Sync.SourceSystemJournalEntry outbound BOD will be triggered without any errors.
    2. SyncSourceSystemJournalEntry/DataArea/SourceSystemJournalEntry/JournalEntryHeader/BaseJournalEntryHeader/ProtocolNumberText
    3. Go to GeneralLedgerJournalControl screen and Posted tab

JT-1393064

Sync_ReceivableTransaction_Outbound has not been triggered when we do Payment Reversal-- Native LPL flow

Program/Business class/Process affected:

  • ReceivableApplicationAdjustmentSelect
  • ReceivablePaymentApplyReverseDetail

Use these steps to test the enhancement:

  1. Enable SyncReceivableTransaction BOD in FSMBODConfiguration business class.
  2. Create ReceivableInvoice and Release.
  3. Create ReceivablePaymentHeader and Release.
  4. Go to cash application and apply payment.
  5. Perform Application Close.
  6. Perform Journalize receivable distribution.
  7. Go to Payment Reversal in Additional Actions, perform CreateandReverseall and Release.
  8. Verify ION Out Queue.

JT-1395973

Facing an Issue While testing Native Lpl for LCL Tax Report Bod

Program/Business class/Process affected:

  • TaxEntity.busclass

Use these steps to test the enhancement:

  1. Create a Payablesinvoice with tax and release it. Do the payment for the Invoice by performing actions:
    1. Perform cash Requirements,
    2. Electronic Payment Creations
    3. PaymentClose
  2. Run Vat Return Report batch Job. BOD will trigger and Work unit will generate successfully
  3. When vatReportingLine.Source is empty then TaxReportLine/TaxID details will be displayed.

JT-1399373

Sync Personnel Inbound for vendor not populating the vendor name

In FSM_ION_SyncPersonnel_Inbound.lpd Vendor.VendorName is picked from the XPath Peronnel/Name.

Program/Business class/Process affected:

  1. Files Changed: SM_ION_SyncPersonnel_Inbound.lpd
  2. New Required Setup:No
  3. New Variable Added in JSON:No
  4. New IPA Changes:
  5. In FSM_ION_SyncPersonnel_Inbound.lpd flow below changes are done.
    1. In Initialvalues assign node,"IN_Personnel_Name" variable is configured to XPath Peronnel/Name.
    2. In "CreateVendor" and "UpdateVendor" LM query added fields LegalName and VendorSearchName configured to values "IN_Personnel_Name"
  6. Integration Specific: Yes

    These changes are related to CSF-XM Integration.

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. In Channels Administrator, Activate the Sync.Personnel ION Inbox Receiver.
  2. How to Test:

    After the BOD is processed:

    • When ActionCode= "Add" a Vendor gets Created

    • When ActionCode="Replace"

      1. If Vendor does not exist, create new Vendor Record
      2. If Vendor exists, update existing Vendor Record

    • When ActionCode="Delete"

      1. If Vendor does not exist, click End.
      2. If Vendor exists, delete existing Vendor Record.
  3. Verify the Result:

    Vendor.VendorName, Vendor.VendorSearchName, Vendor.LegalName will get value from XPath Personnel/Name for Create and Update actions of Vendor.

JT-1400576

Error generated when expense report is generated with Company Paid

"Already Exist" error occurred in FSM_ION_SyncExpenseReport_Inbound when expense report is generated.

Scenario: Company Paid

Integration: CSF-XM

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncExpenseReport_Inbound

  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    In FSM_ION_SyncExpenseReport_Inbound IPA flow below changes done:

    1. Added "InterfaceHeader" Query to get the record count of ExpenseManagementInterfaceHeader.
    2. Added Branch8660 to verify the condition ExpenseManagementInterfaceHeader record exist or not.

      • If record exist it will go to newly added Assign node - Assign1430

      • If record does not exist then it will go to existing flow - ReadExpenseHdr.

  5. Integration Specific: Yes

    These changes are related to CSF-XM Integration.

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger" check box.
    2. In Channels Administrator, select ION Channels. Activate the respective ION Inbox Receivers for FSM_ION_SyncExpenseReport_Inbound.
  2. How to Test:

    • When the ExpenseReport is processed form XM side, "ExpenseManagementStagingHeader" and "ExpenseManagementStagingDetail" are created and is moved to "ExpenseManagementInterfaceHeader" with line records in "ExpenseManagementInterfaceDetail".

    • BOD will trigger and Work unit will be generated successfully without any error for FSM_ION_SyncExpenseReport_Inbound BOD.

  3. Verify the Result:

    • When Expense Report is processed with already existing Document in "ExpenseManagementInterfaceHeader" then Confirm BOD is sent with error message "Expense Management Interface : Employee expense document already exists for this document number "

    • XPath for Document sent is ExpenseReport/ExpenseReportHeader/DocumentID/ID.

    • When BOD is processed with existing Document then Confirm BOD is sent else flow will be executed and ExpenseManagementStagingHeader and ExpenseManagementStagingDetail are interfaced to "ExpenseManagementInterfaceHeader" with line records in "ExpenseManagementInterfaceDetail".

There are no dependencies.

JT-1400762

Create Document Flow - GHR IMS to CSF IOBOX - For MT Env for CSF - XM integration

Delivered new document for GHR IMS to CSF IOBOX.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_all_documentflows_ST.xml

    • FSM_GHR_documentflow_ST.xml

  2. New Required Setup: No
  3. Integration Specific: Yes

    It is related to GHR-CSF integration

Use these steps to test the enhancement:

  1. How to Test:

    Import FSM_GHR_documentflow_ST.xml file in data flows(ION).

  2. Verify the Result:

    Document flow should create successfully in data flows(ION).

JT-1401992

Sync IEFIN ION Content to SampleDocumentTemplate.csv

Make ION Content information available in Sample Document Template

Program/Business class/Process affected:

  • Viewing information in Sample Document Template

Use these steps to test the enhancement:

  1. Open a sample document.
  2. In the All tab, search for FSMIONContent*
  3. Verify that there are three records for the above search with attachments.

JT-1402511

Create IMS Document Flow - CSF IMS to SCE - For MT Env

Delivered new document for CSF IMS to SCE for MT Environment.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ims_SCE_documentflow_ST.xml

    • FSM_IMS_All_DataFlows_ST.xml

  2. New Required Setup: No
  3. Integration Specific: Yes

    It is related to CSF-SCE integration

Use these steps to test the enhancement:

  1. How to Test:

    Import FSM_ims_SCE_documentflow_ST.xml file in data flows(ION).

  2. Verify the Result:
    1. Document flow should create successfully in data flows(ION).
    2. Verify CSF IMS to SCE document flow.

JT-1402513

Create IMS Document Flow - CSF IMS to XM - For MT Env

Delivered new document for CSF IMS to XM for MT Environment.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ims_XM_documentflow_ST.xml

    • FSM_IMS_All_DataFlows_ST.xml

  2. New Required Setup: No
  3. Integration Specific: Yes

    It is related to CSF-XM integration

Use these steps to test the enhancement:

  1. How to Test:

    Import FSM_ims_XM_documentflow_ST.xml file in data flows(ION).

  2. Verify the Result:
    1. Document flow should create successfully in data flows(ION).
    2. Verify CSF IMS to XM document flow.

JT-1402516

Create IMS Document Flow - CSF IMS to IPS - For MT Env

Delivered new document for CSF IMS to IPS for MT Environment.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ims_IPS_documentflow_ST.xml

    • FSM_IMS_All_DataFlows_ST.xml

  2. New Required Setup: No
  3. Integration Specific: Yes

    It is related to CSF-IPS integration

Use these steps to test the enhancement:

  1. How to Test:

    Import FSM_ims_IPS_documentflow_ST.xml file in data flows(ION).

  2. Verify the Result:
    1. Document flow should create successfully in data flows(ION).
    2. Verify CSF IMS to IPS document flow.

JT-1402517

Restrict Native LPL ACK Trigger by Default as Part of of GLTranasactionInterface process

Restricted Native LPL Acknowledge SourceSystemJournalEntry BOD Trigger by Default as Part of GLTranasactionInterface process.

Program/Business class/Process affected:

  1. Files Changed:

    • GLTransactionInterface

    • GLTransactionInterfaceResult

  2. New Required Setup: No
  3. Integration Specific: Yes

    It is related to HRCM-CSF integration

Use these steps to test the enhancement:

  1. Setup:

    In FSMBODConguration enable/disable Acknowledge.SourceSystemJournalEntry BOD.

  2. How to Test:
    1. Create GLTransactionInterface record using Process.SourceSystemJournalEntry BOD.
    2. Perform Interface Transactions action in GLTransactionInterface business class.
  3. Verify the Result:
    1. In FSMBODConguration Acknowledge.SourceSystemJournalEntry BOD enables BOD should trigger.
    2. In FSMBODConguration Acknowledge.SourceSystemJournalEntry BOD disable BOD should not trigger.

JT-1403290

PendingNativeLPLConversion: Assigning Journal References to SSJE BODs

Added Native LPL code to trigger Sync.SourceSystemJournalEntry Outbound BOD when AssignJournalReferenceNumber batch job is performed and Added JournalReferenceNumber field in new XPath for Sync.SourceSystemJournalEntry

Program/Business class/Process affected:

  • GeneralLedgerJournalControl.busclass

  • GeneralLedgerJournalControlRef.busclass

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. Select check box in FSMBODConfiguration for Sync.SourceSystemJournalEntry.
  2. How to Test:
    1. Go to Financials > Global Ledger > Processing > Reporting Basis > Reporting Basis then select ReportingBasis and Year.
    2. Now Perform AssignJournalReferenceNumber batch job then Sync.SourceSystemJournalEntry outbound BOD will be triggered without any errors and outbound XML xml will be generated in ION Out Queue.
  3. Verify the Result:
    1. Check this path for JournalReferenceNumber: SyncSourceSystemJournalEntry/DataArea/SourceSystemJournalEntry/JournalEntryHeader/BaseJournalEntryHeader/ProtocolNumberText
    2. Go to GeneralLedgerJournalControl screen and Posted Tab and check JournalReferenceNumber number generated for each Journal.

JT-1403868

Mapping of Elements in SyncSupplierInvoice_Out for CSF-GRC PI integration

Mapping of Elements in SyncSupplierInvoice_Out for CSF-GRC PI integration

Adding new elements in SupplierInvoice BOD as part of CSF-GRC Integration.

Program/Business class/Process affected:

  • FSM_ION_SyncSupplierInvoice_Outbound.lpd

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. In Service Definition enable the service for "PayablesInvoiceService" and attach FSM_ION_SyncSupplierInvoice_Outbound
  2. How to Test:
    1. Create PurchaseOrder and Release it.
    2. Create PurchaseOrderReceipt and Release it.
  3. Create PayablesInvoice for that PurchaseOrder(matchInvoice) and Release it.
  4. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SupplierInvoice_Out BOD.

    Verify these paths in XML:

    SupplierInvoiceHeader/ExtendedReportAmount

    SupplierInvoiceHeader/ExtendedReportAmount/CurrencyID

    SupplierInvoiceLine/ExtendedReportAmount

    SupplierInvoiceLine/ExtendedReportAmount/CurrencyID

    SupplierInvoiceLine/UnitPrice/ReportAmount

    SupplierInvoiceLine/UnitPrice/ReportAmount/CurrencyID

JT-1404877

SyncPayables Transaction_Out - Mapping Elements for GRC_PI Integration

Added new elements in Sync.PayablesTransaction_Out bod as part of CSF-GRC Integration.

Program/Business class/Process affected:

  1. Files Changed:

    • FSM_ION_SyncPayablesTransaction_Outbound.lpd

    • PayablesInvoicePayment. busclass

  2. New Required Setup: No
  3. New Variable Added in JSON: Yes

    Added new variables in JSON:

    • PayablesInvoice.Description as PInvDescription

    • VendorLocationRel.VendorName as VLVendorName

    • PayablesInvoice.DueDate as PInvDueDate

    • PayablesInvoice.DiscountDate as PInvDiscountDate

    • PayablesInvoice.TeramsCode.Description as TermsCodeDesc

  4. New IPA Changes:

    In FSM_ION_PayablesTransaction_Outbound IPA flow below changes done:

    1. These variables are added in start node:

      • RemitToPartyName

      • TermsDueDate

      • DiscountDate

      • TermsCode_Desc

      • ItemID

      • ExtendedReportAmount

      • Line_XML

    2. In VariablePrep Assign node added Java Script in the last to derive RemitToPartyName , TermsDueDate and DiscountDate
    3. Added "InvoiceDetail" Transaction node to get the PayablesInvoicedetail records if records exist added new Assign220 assign node to contruct the line xml
    4. In SyncPayableTransactionBOD XML node, these fields are added to the respective path:

      • PInvDescription to PayableTransaction/PayableTransactionHeader/Description

      • RemitToPartyName to PayableTransaction/PayableTransactionHeader/RemitToParty/Contact/Name

      • BankTransactionCode to PayableTransaction/PayableTransactionHeader/PaymentMethodCode

      • PI_TermsCode to PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/ID

      • TermsDueDate to PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/DueDateTime

      • DiscountDate to PayableTransaction/PayableTransactionHeader/PaymentTerm/Discount/EffectiveDateTime

      • TermsCodeDesc[0]["Desc"] to PayableTransaction/PayableTransactionHeader/PaymentTerm/Description

      • Added constructed {Line_XML} tag.

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. In Service Definition, enable the service for PayablesInvoicePaymentService and attach FSM_ION_SyncPayablesTransaction_Outbound
  2. How to Test:
    1. Create PurchaseOrder and Release it.
    2. Create PurchaseOrderReceipt and Release it.
    3. Create PayablesInvoice for that PurchaseOrder(matchInvoice) eneter the terms code and Release it.
    4. Run PerformCashRequirements
    5. Run ElectronicPaymentCreation Batch job
    6. Run PaymentClose, check the generated reports.
    7. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_PayablesTransaction_Out BOD (PayablesInvoicePaymentService).
  3. Verify the Result: In the XML below paths should be populated with values

    • Header XML

      • PayableTransaction/PayableTransactionHeader/Description

      • PayableTransaction/PayableTransactionHeader/RemitToParty/Contact/Name

      • PayableTransaction/PayableTransactionHeader/PaymentMethodCode

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/ID

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/DueDateTime

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Discount/EffectiveDateTime

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Description

    • Line XML

      • PayableTransaction/PayableTransactionLine/LineNumber

      • PayableTransaction/PayableTransactionLine/Item/ItemID/ID

      • PayableTransaction/PayableTransactionLine/Quantity

      • PayableTransaction/PayableTransactionLine/Quantity@unitcode

      • PayableTransaction/PayableTransactionLine/ExtendedAmount

      • PayableTransaction/PayableTransactionLine/ExtendedAmount@currencyID

      • PayableTransaction/PayableTransactionLine/ExtendedReportAmount

      • PayableTransaction/PayableTransactionLine/ExtendedReportAmount@currencyID

JT-1404884

Changes for FSM_ION_SyncInvoice_outbound-- IPA Flow

Changes for Sync_Invoice_Outbound -InvoiceLine/Item/Classification/Codes/Code must be without "-" for Mexico.

Program/Business class/Process affected:

  1. File Changed: FSM_ION_SyncInvoice_Outbound.lpd
  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    In FSM_ION_SyncInvoice_Outbound IPA flow below changes done:

    • Modified Assign4710 - Javascript

    • Changed the condition from Customer Country to AccountingEntity -->PostalAddress->Country.

    • If the Country is Mexico, then Commodity Code should come as without Dashes("-").

  5. Integration Specific: No

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    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.
  2. How to Test:
    1. Create BillingInvoice and Release it.
    2. Execute InvoiceAndVerificationReport.
    3. Execute InvoiceAndRegisterPrint
    4. Execute SubSystemUpdate
    5. ReceivableInvoice Record will create in Released state.
    6. BOD will trigger and Work unit will generate.
  3. Verify the Result:

    Verify the below x-path: InvoiceLine/Item/Classification/Codes/Code

JT-1405082

NativeLPL:SyncPayables Transaction_Out - Mapping Elements for GRC_PI Integration

Added new elements in Sync.PayablesTransaction_Out bod as part of CSF-GRC Integration.

Program/Business class/Process affected:

  • PayablesInvoicePayment.busclass

  • PayablesinvoiceDetail.busclass

Use these steps to test the enhancement:

  1. Setup:
    1. In FinanceEnterpriseGroup, select the BODtrigger check box.
    2. In FSMBODConfiguration, Sync.PayableTransaction BOD should be enabled
  2. How to Test:
    1. Ceate PurchaseOrder and Release it.
    2. Create PurchaseOrderReceipt and Release it.
    3. Create PayablesInvoice for that PurchaseOrder(matchInvoice), specify the terms code and Release it.
    4. Run PerformCashRequirements
    5. Run ElectronicPaymentCreation Batch job
    6. Run PaymentClose, check the generated reports.
    7. BOD will trigger.
  3. Verify the Result: In the XML below paths should be populated with values

    • Header XML

      • PayableTransaction/PayableTransactionHeader/Description

      • PayableTransaction/PayableTransactionHeader/RemitToParty/Contact/Name

      • PayableTransaction/PayableTransactionHeader/PaymentMethodCode

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/ID

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Term/DueDateTime

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Discount/EffectiveDateTime

      • PayableTransaction/PayableTransactionHeader/PaymentTerm/Description

    • Line XML

      • PayableTransaction/PayableTransactionLine/LineNumber

      • PayableTransaction/PayableTransactionLine/Item/ItemID/ID

      • PayableTransaction/PayableTransactionLine/Quantity

      • PayableTransaction/PayableTransactionLine/Quantity@unitcode

      • PayableTransaction/PayableTransactionLine/ExtendedAmount

      • PayableTransaction/PayableTransactionLine/ExtendedAmount@currencyID

      • PayableTransaction/PayableTransactionLine/ExtendedReportAmount

      • PayableTransaction/PayableTransactionLine/ExtendedReportAmount@currencyID

JT-1405089

changes needs to be done in SyncItemMaster_Out and Mapping sheet

Added new elements to Sync.ItemMaster_Out.lpd

Program/Business class/Process affected:

  1. Files Changed: FSM_ION_SyncItemMaster_Out.lpd
  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New IPA Changes:

    In "XML_ITL" node Mapped Variationid to ItemMaster/ItemMasterHeader/ItemId/RevisionID and ItemMaster/ItemMasterHeader/ServiceIndicator is set to false.

  5. Integration Specific: No

Use these steps to test the enhancement:

  1. Setup:

    Enable the service "ItemService" for FSM_ION_SyncItemMaster_Out.lpd

  2. How to Test:

    • Create an Item and save it.

    • BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncItemMaster_Out.lpd BOD (ItemService).

  3. Verify the Result:

    Mapped Variationid to ItemMaster/ItemMasterHeader/ItemId/RevisionID and ItemMaster/ItemMasterHeader/ServiceIndicator is set to false.

JT-1405092

Native LPL: changes needs to be done in SyncItemMaster_Out and Mapping sheet

Added new elements to Sync.ItemMaster_Out.lpd

Program/Business class/Process affected:

  1. Files Changed: UserTemplate.csv
  2. New Required Setup: No
  3. New Variable Added in JSON: No
  4. New Changes:

    In XML Template of ItemMaster Mapped Variationid to ItemMaster/ItemMasterHeader/ItemId/RevisionID and ItemMaster/ItemMasterHeader/ServiceIndicator is set to false.

  5. Integration Specific: No

Use these steps to test the enhancement:

  1. Setup: Enable Sync.ItemMaster in FSMBODConfiguration.
  2. How to test:
    1. Create an Item and save it.
    2. BOD will trigger and check the generated XML in IONOut.busclass
  3. Verify the Result:

    Mapped Variationid to ItemMaster/ItemMasterHeader/ItemId/RevisionID and ItemMaster/ItemMasterHeader/ServiceIndicator is set to false.

JT-1405093

Changes needs to be done in SyncPurchaseOrder_Out BOD and Mapping

Added new elements in FSM_ION_SyncPurchaseOrder_Outbound BOD for CSF-GRC PI Integration.

Program/Business class/Process affected:

  1. Files Changed:
    • FSM_ION_SyncPurchaseOrder_Outbound

    • PurchaseOrder Business Class

  2. New Required Setup:

    • No new Setup is required.

  3. New Variable Added in JSON:

    • No new variable is added in JSON.

  4. New IPA Changes:

    In FSM_ION_SyncPurchaseOrder_Outbound IPA flow below changes done:

    1. Passed Company.ProcurementGroup as variable in Trigger Code in PurchaseOrder BusinessClass.
    2. Below variables added in start node:

      • ContractLine

      • Contract

    3. Passed Contract and ContractLine in "LMTxn4560" query.
    4. Added respective code in PLI_FIELDS Assign node:

      • If LMTxn4560_Contract > 0 then ContractID = ProcurementGroup + Generic_Delimiter + LMTxn4560_Contract

      • If LMTxn4560_ContractLine > 0 then ContractLine = LMTxn4560_ContractLine

    5. Added new Xpaths :

      • PurchaseOrderHeader/ExtendedReportAmount

      • PurchaseOrderLine/ContractReference/DocumentID/ID

      • PurchaseOrderLine/ContractReference/LineNumber

  5. Integration Specific: Yes

    These changes are related to CSF-GRC Integration.

Use these steps to test the enhancement:

  1. Setup:

    • In FinanceEnterpriseGroup, select the BODtrigger check box.

    • For Outbound BOD, enable the PurchaseOrderService service definition for FSM_ION_SyncPurchaseOrder_Outbound.

  2. How to Test:

    • Create PurchaseOrder and PurchaseOrderLine, Pass Contract value in PurchaseOrderLine and release it.

    • BOD will trigger and work unit will generate successfully without any error for FSM_ION_SyncPurchaseOrder_Outbound BOD (PurchaseOrderService).

  3. Verify the Result:

    • PurchaseOrderHeader/ExtendedReportAmount

    • PurchaseOrderLine/ContractReference/DocumentID/ID

    • PurchaseOrderLine/ContractReference/LineNumber

There are no dependencies

JT-1405099

Mapping of Elements in SyncRequisition_Out BOD for CSF-GRC PI Integration

Added new elements in RequisitionHeader and RequisitionLine in SyncRequisition_Out BOD for CSF-GRC PI Integration.

Program/Business class/Process affected:

  1. Files Changed:
    1. FSM_ION_SyncRequisition_Outbound.
    2. Requisition Business Class
  2. New Required Setup: No new Setup is required.
  3. New Variable Added in JSON: No new variable is added in JSON.
  4. New IPA Changes: In FSM_ION_SyncRequisition_Outbound IPA flow below changes done:
    1. Passed ApprovalValue as variable in Trigger Code in Requisition BusinessClass.
    2. Below variables added in start node: TransactionCurrencyCode
    3. Passed TransactionCurrencyCode in "RequisitionLine" query. Assigned the value to TransactionCurrencyCode variable in LineVars Assign node.
  5. Integration Specific: Yes

    These changes are related to CSF-GRC Integration.

Use these steps to test the enhancement:

  1. Setup:
    • In FinanceEnterpriseGroup, select the BODtrigger check box.
    • For Outbound BOD, Enable the "RequisitionService" service definition for FSM_ION_SyncRequisition_Outbound.
  2. How to Test:
    • Create Requisition and RequisitionLine and release it.
    • BOD will trigger and work unit will generate successfully without any error for FSM_ION_SyncRequisition_Outbound BOD (RequisitionService).
  3. Verify the Result:
    • RequisitionHeader/ExtendedReportAmount
    • RequisitionLine/ExtendedReportAmount

There are no dependencies.

JT-1405101