BOD Connectors

This section contains enhancements in Infor Financials and Supply Management for 11.0.78.0.

Add new elements to Sync.ReceivableTransaction_ out BOD for FSM-GRC PI

Add new elements to Sync.ReceivableTransaction_ out BOD for FSM-GRC PI.

Program/business class/process affected:

  • Files Changed: FSM_ION_SyncReceivableTransaction_Outbound
  • New Required Setup:No
  • New Variable Added in JSON: No. Reading field from existing JSON.
  • New IPA Changes:
    • Added new field from existing JSON.
    • Modified javascript in Assign4270 node.
    • Modified javascript in Assign5400 node.
  • Integration Specific: Yes. These changes are related to FSM-GRC PI Integration.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the "BODtrigger" checkbox is checked.
  2. For SyncReceivableTransaction BOD, enable the Service Definition "ReceivableTransactionService".
  3. Create Receivable Invoice and Release it.
  4. Create Receivable Payment Header and Release it.
  5. Go to Cash application and apply the payment.
  6. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncReceivableTransaction_Out BOD
  7. Verify the Result: Check the Header user area and fsm.PostingDate value should be GeneralLedgerDate of ReceivablePayment..

JT-1547673

Expense Report BOD - Consuming Dimensions of FSM as Segments.

Consuming Dimensions of FSM as Segments based on Classfication type = "CostCenterSegments" in FSM_ION_SyncExpenseReport_In BOD

Program/business class/process affected:

  • Files Changed: FSM_ION_SyncExpenseReport_Inbound
  • New Required Setup: No.
  • New IPA Changes:

    In Start node, added variables "CostCenterClassificationType","CostCenterClassificationlen","idx4","textName4","textValue4"

    In "Assign7160" and "Assign3680" nodes added JavaScript code for getting Cost Center value.

    • if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is "CostCenterSegments", reading the value from ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/Codes/Code listID = "Cost Center"

      Else,if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is not available then reading the value from ExpenseReport/ExpenseReportLine/ExpenseAllocation/CostCenterCode

    • if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is "CostCenterSegments", reading the FinanceDimension values from ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/Codes/Code listID = "Finance 1 Dimensions" to "Finance 10 Dimensions".

      Else,if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is not available then reading the values from ExpenseReport/ExpenseReportLine/Classification/Codes/Code listID = "Finance 1 Dimensions" to "Finance 10 Dimensions".

  • Integration Specific: Yes These changes are related to FSM-XM Integration.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, "BODtrigger" checkbox should be checked.
  2. In Channels Administrator, Activate the respective ION Inbox Receivers for FSM_ION_SyncExpenseReport_Inbound.
  3. When the ExpenseReport is processed form XM side, "ExpenseManagementStagingHeader" and "ExpenseManagementStagingDetail" are created and is moved to "ExpenseManagementInterfaceHeader" with line records in "ExpenseManagementInterfaceDetail".
  4. BOD will trigger and Work unit will be generated successfully without any error for FSM_ION_SyncExpenseReport_Inbound BOD.
  5. Verify the result:
    1. For "FinanceStructure.AccountingUnit" field: if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is "CostCenterSegments", reading the value from ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/Codes/Code listID = "Cost Center"

      Else,if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is not available then reading the value from ExpenseReport/ExpenseReportLine/ExpenseAllocation/CostCenterCode

    2. For "FinanceStructure.FinanceDimension1 to FinanceDimension10" fields : if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is "CostCenterSegments", reading the FinanceDimension values from ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/Codes/Code listID = "Finance 1 Dimensions" to "Finance 10 Dimensions".

      Else,if ExpenseReport/ExpenseReportLine/ExpenseAllocation/Classification/type is not available then reading the values from ExpenseReport/ExpenseReportLine/Classification/Codes/Code listID = "Finance 1 Dimensions" to "Finance 10 Dimensions".

JT-1544238

FSM BOD Shipment to EAM - SyncShipment_Out

Added new X-Paths for Sync.Shipment_Out BOD to EAM intergration

Program/business class/process affected:

Files Changed:

  • FSM_ION_SyncShipment_Outbound.ipd
  • SyncShipmentJSON.txt

New Required Setup: Assign value "EAM" to "IntegratingApplication" parameter in System Configurations

New Variable Added in JSON:

  • Added RequisitionRel.Requisition.EAMWorkOrder as EAMWorkOrder
  • Added RequisitionRel.Requisition.EAMWorkOrderActivity as EAMWorkOrderActivity

New IPA Changes:

  • Added two variables in Start Node : DocID, ShipmentPurposeCode
  • New JavaScript is added in AssignUserArea node;
  • If (WarehouseShipment.WarehouseDemand.DemandSystemCode == "RQ" && IntegrationApp == "EAM" && status == "Closed")
  • ShipmentPurposeCode = "IssueItems"
  • UserAreaXML += <Property><NameValue name="eam.WOActivityID" type="StringType">{EAMWorkOrderActivity}@NoNullTag@</NameValue></Property>
  • OrderType = "MaintenanceOrder"
  • DocID = EAMWorkOrder

Integration Specific: These changes are related to EAM integration

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the "BODtrigger" checkbox is 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 Configurations.
  4. Create Requisition with EAMWorkOrder values.
  5. Release Requisition.
  6. Run WarehousePickListPrint batch job.
  7. Navigate to WarehouseShipments and Finish>>Release the shipment record.
  8. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncShipment_Outbound BOD.
  9. Verify the results:
    • ShipmentHeader/DocumentReference/DocumentID/ID/@accountingEntity @location - EAMWorkOrder ShipmentHeader/UserArea/Property/NameValue/@name = "eam.WOActivityID" @type = "StringType" - EAMWorkOrderActivity
    • ShipmentHeader/ShipmentPurposeCode/@listID = "Shipment Purposes" - "IssueItems"

JT-1541514

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. Select 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.
  5. FSM_ION_CONTENTPACK_ST,FSM_ION_CONTENT_PACK_IONCE_IMS_ST and FSM_ION_CONTENT_PACK_IONCE_ST.

JT-1549249

Add new X-paths to SyncItemMaster_Out

New X-paths added for Sync.ItemMaster_Out

Program/business class/process affected:

  • Files Changed: FSM_ION_SyncItemMaster_Out.lpd
  • New Required Setup:No
  • New Variable Added in JSON:No
  • New IPA Changes:
    • ShipmentHeader/UserArea/Property/NameValue/@name = "eam.WOActivityID" @type =Added new variables in start node RPolicy,ReorderPolicy,MinOrderQuantity,MaxOrderQuantity,ReorderPoint,SafetyStock.
    • Added conditions in nodes DetailVar,XML_DTL,Assign9960,XML2250,Assign7250,XML9450,ITLOC1,ITLOC.
  • Integration Specific:No

Use these steps to test the enhancement:

  1. Enable the service "ItemService" for FSM_ION_SyncItemMaster_Out.lpd
  2. Create,Update or Delete an Item with an ItemLocation both for RequiredCleanDocumentID = "N" and "Y".
  3. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncItemMaster_Out.lpd BOD (ItemService).
  4. Verify the result: X-paths and its respective values.

    ItemMaster/ItemLocation/ProcurementParameters/OrderMethodCode ----ItemLocation.ReorderPolicy

    ItemMaster/ItemLocation/ProcurementParameters/MinOrderQuantity -- ItemLocation.MinimumOrderQuantity

    ItemMaster/ItemLocation/ProcurementParameters/MinOrderBaseUOMQuantity --ItemLocation.MinimumOrderQuantity

    ItemMaster/ItemLocation/ProcurementParameters/MaxOrderQuantity --- ItemLocation.MaximumOrderQuantity

    ItemMaster/ItemLocation/ProcurementParameters/MaxOrderBaseUOMQuantity --ItemLocation.MaximumOrderQuantity

    ItemMaster/ItemLocation/ProcurementParameters/OrderPointQuantity -- ItemLocation.ReorderPoint

    ItemMaster/ItemLocation/ProcurementParameters/OrderPointBaseUOMQuantity--ItemLocation.ReorderPoint

    ItemMaster/ItemLocation/ProcurementParameters/SafetyStockQuantity ---ItemLocation.SafetyStock

    ItemMaster/ItemLocation/ProcurementParameters/SafetyStockBaseUOMQuantity--ItemLocation.SafetyStock

JT-1539701

FSM Localization: Changes required in CreditTransfer BOD for Mexico

Changes done in Sync.CreditTransfer BOD (Country Code: MX). Localization specific to Mexico Country.

Program/business class/process affected:

  • File Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • New Required Setup : No
  • New Variable Added in JSON: Yes. MXBankAccountNumber added.
  • IPA Change:
    • Added "MXBankAccountNumber","transactionDes","paymentPurposeCode","BODBankEntityBranchName " variables in 'start' node
    • Added below code in one javascript of Assign6300,Assign5940 nodes
      if ( DebtorAddressCountry == "MX") 
{ 
transactionDes = "AT&T Mexico"; 
} 
else 
{ 
transactionDes = GetPayablesInvoicePayment_ProcurementCardStatement; 
} 


if ( DebtorAddressCountry == "MX") 
{ 
paymentPurposeCode= "AT&T Mexico"; 
BODBankEntityBranchName = BankE_BranchName; 
} 
c)Added below code in XML file 
<BranchParty> 
<PartyIDs> 
<ID schemeName="BankPartyIdentification">{MXBankAccountNumber}@NoNullTag@</ID> 
</PartyIDs> 
</BranchParty> 

<BranchParty> 
<PartyIDs> 
<ID schemeName="BankPartyIdentification">{BODBankEntityBranchName}@NoNullTag@</ID> 
</PartyIDs> 
</BranchParty> 

<PaymentPurposeCode>{paymentPurposeCode}@NoNullTag@</PaymentPurposeCode>
  • Integration Specific: Yes. These changes are related to Localization Integration for Mexico Country.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the "BODtrigger" checkbox is checked.
  2. 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 will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCreditTransfer_Out BOD.
  9. Verify these X-Paths:
    • CreditTransferPayment/FirstAgentParty/BranchParty/PartyIDs/ID
    • CreditTransferPayment/PaymentTransaction/FinalAgentFinancialParty/BranchParty/PartyIDs/ID
    • CreditTransferPayment/PaymentTransaction/Description
    • CreditTransferPayment/PaymentTransaction/PaymentPurposeCode

JT-1541422

Change Mapping In Sync Invoice Outbound BOD for Country India

Change Mapping In Sync Invoice Outbound BOD for Country India.

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 done:
    • In Assign4010: Modified Javascript for localization for India
    • SupplierPartyTaxID_AR_VAT = SupplierPartyTaxID_AR_VAT (TaxEntity.VATRegistrationNumber);
    • SupplierPartyTaxID = ";
  • Integration Specific: Yes

These changes are related to localization Integration , Country India.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the "BODtrigger" checkbox is 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 will trigger and Work unit will generate successfully for FSM_ION_SyncInvoice_Out BOD (ReceivableInvoiceService).
  6. Verify that mapped Below x-path's for localization India:

    InvoiceHeader/SupplierParty/PartyIDs/TaxID-------> map this to TaxEntity.VATRegistrationNumber

JT-1539204

Effective time period values are coming improper for SyncLCLTax Report Outbound BOD

Effective time period values are coming proper for sync.LCLTaxReport_Out

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 variables PeriodEndDateArray,formattedDate,PeriodStartDateArray,Fin_EndTimePeriod,x,y,year,month,day.
    • Added new nodes Period,Assign4480,Assign6930.
  • Integration Specific:localization Integration.

Use these steps to test the enhancement:

  1. Enable the service "TaxReportService" for FSM_ION_SyncLCLTaxReport _Out.lpd.
  2. In SystemConfiguration give the value of IntegrationApplication == "Local.ly"
  3. 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.
  4. Run Vat Return Report batch Job. BOD will trigger and Work unit will generate successfully.
  5. Verify that Period StartDate and EndDates are passed in Xpaths TaxReportHeader/EffectiveTimePeriod/StartDateTime and TaxReportHeader/EffectiveTimePeriod/EndDateTime respectively.

JT-1545926

Localization (Chile): Send Journal Referance number in SSJE BOD

Localization (Chile): Send Journal Reference number in SSJE BOD

Program/business class/process affected:

  • Files Changed: GeneralLedgerJournalControlRef.bussclass

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the "BODtrigger" checkbox is checked.
  2. Enable Service Definition "GLJournalControlService".
  3. Go to Financials->Global Ledger->Processing->Reporting Basis->Reporting Basis then select ReportingBasis and Year.
  4. Now Perform AssignJournalReferenceNumber batch job then Sync.SourceSystemJournalEntry outbound BOD will be triggered without any errors.
  5. Verify the below path for JournalReferenceNumber:

    SyncSourceSystemJournalEntry/DataArea/SourceSystemJournalEntry/JournalEntryHeader/BaseJournalEntryHeader/ProtocolNumberText

  6. Go to GeneralLedgerJournalControl screen and Posted Tab.

JT-1535991

New Elements required for Sync Invoice Outbound BOD for the country Great Britain E-invoicing

New Elements required for Sync Invoice Outbound BOD for country Great Britain.

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 done:
    • In Assign4010: Modified Javascript for Great Bretain(GB) PaymentMethodCode--BillingInvoice.BankTransactionCode;
    • Assign7380 :Commented the Javascript and In Assign100:Added Javascript for InvoiceCharge information.
    • In Assign5720 :Modified javascript , for InvoiceAllowance - added CurrencyID for Amount, For TotalDiscount ID added - missed.
  • Integration Specific: Yes

These changes are related to Localization Integration , Great Britain Country.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the "BODtrigger" checkbox is 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 BillingInvoice Release it.
  5. Execute InvoiceVerificationReport
  6. Execute InvoiceAndRegisterPrint
  7. Execute SubSystemUpdate
  8. BOD will trigger and Work unit will generate successfully for FSM_ION_SyncInvoice_Out BOD (ReceivableInvoiceService).
  9. Verify that:

    Added new Elements required for Sync Invoice Outbound BOD for the country Great Britain E-invoicing

    /SyncInvoice/DataArea/Invoice/InvoiceHeader/PaymentMethodCode

    Invoice charge /Type and sequence

    InvoiceAllowance/ID

    InvoiceAllowance/Amount@CurrencyID

JT-1531243

New Elements required for Sync Invoice Outbound BOD (Billing Flow) for the country India

New Elements required (ShipFromParty x-paths added) for Sync Invoice Outbound BOD (Billing Flow) for the country India.

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 done:
    • Start node: Added below variables:

      BLInvShipFromPartyLocation,BLInvShipFromPartyAddressLine1,BLInvShipFromPartyAddressLine2,BLInvShipFromPartyAddressLine3,BLInvShipFromPartyAddressLine4,

      BLInvShipFromPartyMunicipality,BLInvCountrySubDivisionCode,BLInvShipFromPartyCountry,BLInvShipFromPartyPostalCode and BLLineShipFromPartyLocationIN

    • Assign8960 : Mapped the values in jvascript
    • Assign5720: Modified the Javascript for Localization India: mapped the value

      BLLineShipFromPartyLocation ="";

      BLLineShipFromPartyLocationIN = lawsonCompany + Generic_Delimiter +BLInvoiceline_Location;

    • In BLinvoice Transaction node Added Location.PostalAddress.DeliveryAddress.AddressLine1 & &Location.PostalAddress.DeliveryAddress.AddressLine2 & Location.PostalAddress.DeliveryAddress.AddressLine3 & Location.PostalAddress.DeliveryAddress.AddressLine4 & Location.PostalAddress.Municipality & Location.PostalAddress.Country & Location.PostalAddress.PostalCode & Location.PostalAddress.StateProvince fields.
    • In Assign4010: Modified Javascript for Localization India- Added ShipFromparty x-path for Billing flow.
  • Integration Specific: Yes

These changes are related to Localization Integration, Country India.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the "BODtrigger" checkbox is 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 BillingInvoice Release it.
  5. Execute InvoiceVerificationReport
  6. Execute InvoiceAndRegisterPrint
  7. Execute SubSystemUpdate
  8. BOD will trigger and Work unit will generate successfully for FSM_ION_SyncInvoice_Out BOD (ReceivableInvoiceService).
  9. Verify that the mapped below x-path's for Localization India:

    /SyncInvoice/DataArea/Invoice/InvoiceHeader/ShipFromParty.

    In InvoiceLine ShipFromParty/PartyIDs/ID and InvoiceLine ShipFromParty/PartyIDs/TaxID

JT-1541335

New Elements to be added for Sync Location outbound BOD for the country Brazil

Added new elements for Sync.Location_Out BOD for Country Brazil

Program/business class/process affected:

  • Files Changed: Sync.Location_Out BOD
  • New Required Setup: No new setup is required
  • New Variables Added in JSON: No new variable is added in JSON
  • New IPA Changes: Added new X-Paths in Address XML
    If (IntegrationApplication == "Local.ly and CountryCode == "BR")Address type="Discrete" 
BuildingNumber = InventoryLocation.PostalAddress.AddressLine2 
AttentionOfName = InventoryLocation.Name 
StreetName = InventoryLocation.PostalAddress.AddressLine1 
Unit = InventoryLocation.PostalAddress.AddressLine3 
CityName = InventoryLocation.PostalAddress.Municipality 
CountrySubDivisionCode = InventoryLocation.PostalAddress.StateProvince(listID="Country Sub-divisions") 
CountryCode = InventoryLocation.PostalAddress.Country (listID="Countries") 
PostalCode = InventoryLocation.PostalAddress.PostalCode (listID="Postal/ZIP Codes")
  • Integration Specific: Changes are related to Localization integration

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the "BODtrigger" checkbox is checked.
  2. Enable the ServiceDefinition "InventoryLocationService" and ProcessDefinition "FSM_ION_SyncLocation_Out"
  3. Assign GeneralLedgerCompany.AccountingEntity.AddressCode.PostalAddress.Country = "BR"
  4. Create, Update and Delete a record in InventoryLocation.
  5. Verify the below X-Paths:

    Location/Address type="Discrete"

    Location/Address/BuildingNumber

    Location/Address/AttentionOfName

    Location/Address/StreetName

    Location/Address/Unit

    Location/Address/CityName

    Location/Address/CountrySubDivisionCode(listID="Country Sub-divisions")

    Location/Address/CountryCode(listID="Countries")

    Location/Address/PostalCode(listID="Postal/ZIP Codes")

JT-1531440

Sync.CreditTransfer BOD - Addition of new element for PaymentOutputFileHeader(Payment Run Number)

Sync.CreditTransfer BOD - Addition of new element for PaymentOutputFileHeader(Payment Run Number)

Program/business class/process affected:

  • File Changed: FSM_ION_SyncCreditTransfer_Out.lpd
  • New Required Setup : No
  • New Variable Added in JSON: No
  • IPA Change: Added below code in Javascript of Assign1110 node 
    <Property> 
<NameValue name="fsm.PaymentOutputFileHeader" type="StringType">{CLPP_TransactionNumber}@NoNullTag@</NameValue> 
</Property>
  • Integration Specific: Yes

These changes are related to localization.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the "BODtrigger" checkbox is checked.
  2. Enable the Service Definition and Processes.
  3. Do required setup for CreditTransfer flow.
  4. Select to Payables > Payables Processing > Process Paymens > Payment Output Files.
  5. Add New Element for Payment Run Number in Sync.CreditTransfer BOD and publish the data from PaymentOutputFileHeader.
  6. BOD will trigger and Work unit will generate successfully without any error for FSM_ION_SyncCreditTransfer_Out BOD.
  7. Verify the X-Path: SyncCreditTransfer/DataArea/CreditTransfer/CreditTransferHeader/UserArea/Property/NameValue[@name="fsm.PaymentOutputFileHeader"]
  8. Expected Result:
    <UserArea> 
<Property> 
<NameValue name="fsm.PaymentOutputFileHeader" type="StringType">5</NameValue> 
</Property> 
<UserArea>

JT-1525538