BOD Connectors CU68

This section contains enhancements in Infor CloudSuite Financials for 11.0.68.0.

IOBOX and IMS ION content sample document templates

The CloudSuite Financials ION content packs are installed in the install directory LASRCDIR/plugins/iefinconnector/ion_content. For users who do not have access to the install directory, the ION content packs are now available in sample document templates.

Program/Business class/Process affected:

  • plugins/iefinconnector/ipa_content/SampleDocumentTemplate.csv

Use these steps to test the enhancement:

ION Content Pack Sample document templates

  1. Sample document templates are included with Infor CloudSuite Financials & Supply Management. For ION content setup and updates, select the content pack template files to use and save them to a shared drive or local drive.

Viewing ION Content sample document templates

You can view a full list of the sample document templates.

  1. Select Financials > Shared Processes > Sample Document Templates.
  2. To filter the list for ION content packs, specify search terms FSM_ION in the Sample Document Template field and click Search.
  3. These are the available ION content packs:
    1. FSM_ION_CONTENTPACK_ST
      • CloudSuite Financials FSMIOBOX ION 11 content pack
      • csfsm_ion11_contentpack.zip
      • FSMIOBOX logical ID is lid://infor.fsm.fsm
    2. FSM_ION_CONTENT_PACK_IONCE_ST
      • CloudSuite Financials FSMIOBOX ION 12 content pack
      • csfsm_ion12_contentpack.zip
      • FSMIOBOX logical ID is lid://infor.fsm.fsm
    3. FSM_ION_CONTENT_PACK_IONCE_IMS_ST
      • CloudSuite Financials IMS ION 12 content pack
      • csfsm_ion12_contentpack_ims.zip
      • IMS logical ID is lid://infor.fsm.fsm_ims
  4. Click the attachment link to view and download the ION content pack sample document template.
  5. Open the sample document template and review the instructions.

CloudSuite Financials ION content pack Instructions

The Infor CloudSuite Financials ION content pack provides configured sample templates for each ION-enabled application integrating with Infor CloudSuite Financials & Supply Management. The standard template connection points for the integrating applications are configured with that application's default IOBOX logical ID.

For Infor CloudSuite Financials FSMIOBOX ION connection, the logical ID is lid://infor.fsm.fsm.

For Infor CloudSuite Financials IMS ION connection, the logical ID is lid://infor.fsm.fsm_ims.

Always install the latest version of the ION content pack sample templates. Content packs can use new BODs and add new supported documents in the document flows. Download the package to a local server and import templates using ION desk or Infor Ming.le. If the ION content pack document flow name is the same as your installed content, you can skip the update.

See Infor ION Desk user guide for instructions to import and activate ION content.

To customize the ION content standard template, copy and rename the ION content template before making your changes.

JT-1388908

Purge action in BODDataInitialLoad

The PurgeInitialLoad action was added in BODDataInitialLoad.

Program/Business class/Process affected:

  • BODDataInitialLoad (busclass & UI)
  • 11.0_post_CU80.faf

Use these steps to test the enhancement:

  1. Open BODDataInitialLoad.
  2. Run PurgeInitialLoad from Actions.
  3. Specify Offset Days and run the action.
  4. Check the records in BODDataInitialLoad. All records should be deleted before OffSetDays.
  5. If OffsetDays are not specified, an error should occur.

JT-1395553

Changes for Sync_Invoice_Outbound--Localization Services (IPA Flow)

When TaxCode is Zero, the InvoiceLine/Tax/Calculation/RateNumeric x-path value should be 0.00 in the SyncInvoice_Out BOD for Localization Services.

Program/Business class/Process affected:

File changed:

  • FSM_ION_SyncInvoice_Outbound.lpd

IPA changes:

  • In FSM_ION_SyncInvoice_Outbound, these IPA flow changes have been made:
    • In Assign5720 node - BLLineTAX_XML javascript modified.

      if TaxRate1 is 0E-7, then TaxRate1 = 0.00. The logic when modified has been changed for TaxRate1 to TaxRate8.

      if BLLineTaxRate1 is 0E-7, then BLLineTaxRate1 = 0.00. Otherwise BLLineTaxRate1 = BLLineTaxRate1.

  • In Assign7380, the JavaScript was modified:
    • if BL_Tax_RateNumeric is 0E-7, then BL_Tax_RateNumeric = 0.00. Otherwise BL_Tax_RateNumeric = BL_Tax_RateNumeric.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, select the the BODtrigger check box.
  2. Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.
  3. Open the Service Definition and enable ReceivableInvoiceService for FSM_ION_SyncInvoice_Outbound.lpd Processes.
  4. Create a BillingInvoice with BillingInvoiceLine having a Zero TaxRate value. Release it.
  5. Run InvoiceAndVerificationReport.
  6. Run InvoiceAndRegisterPrint.
  7. Run SubSystemUpdate.
  8. A ReceivableInvoice record is created in a Released state.
  9. A BOD is triggered and a work unit is created.
  10. Verify the InvoiceLine/Tax/Calculation/RateNumeric x-path. If TaxCode is Zero, verify that the Rate Numeric is 0.00.

JT-1403334

Changes for Sync_Invoice_Outbound--IPA Flow

Changes were made for Sync_Invoice_Outbound for Localization Services. The Alternate Currency Rate and Alternate Currency Rate2 were displayed as 0E-15.

Program/Business class/Process affected:

File changed:

  • FSM_ION_SyncInvoice_Outbound.lpd

IPA Changes:

  • In FSM_ION_SyncInvoice_Outbound, these IPA flow changes were made:
    • In Assign4010, the JavaScript was modified.
    • If using Localization Services and 0E-15 were displayed for the AlternateCurrencyRate and AlternateCurrencyRate2, they are now displayed as 0.00.
    • If RIDAlternateCurrencyRate2 is 0E-15, then RIDAlternateCurrencyRate2 is set to 0.00. Otherwise RIDAlternateCurrencyRate2 = RIDAlternateCurrencyRate2.
    • if RIDAlternateCurrencyRate is 0E-15, then RIDAlternateCurrencyRate is set to 0.00. Otherwise RIDAlternateCurrencyRate = RIDAlternateCurrencyRate.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the BODtrigger check box is selected.
  2. Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.
  3. Open the Service Definition and enable ReceivableInvoiceService for FSM_ION_SyncInvoice_Outbound.lpd Processes.
  4. Create a BillingInvoice and release it.
  5. Run InvoiceAndVerificationReport.
  6. Run InvoiceAndRegisterPrint.
  7. Run SubSystemUpdate.
  8. A ReceivableInvoice record is created in a Released state.
  9. A BOD is triggered and a work unit is created.
  10. Verify that in InvoiceHeader, 0.00 is displayed instead of 0E-15 for fsm.AlternateCurrencyRate2 and fsm.AlternateCurrencyRate.

JT-1404845

SyncInvoice - Customer Purchase Order and BOL elements

The CustomerPurchaseOrder and BOL elements were added in SyncInvoice_Out BOD for Localization Services

Program/Business class/Process affected:

File Changed:

  • FSM_ION_SyncInvoice_Outbound.lpd

IPA changes:

  • In FSM_ION_SyncInvoice_Outbound, these IPA flow changes were made:
    • These variables were added in the start node: DocRefIDBOL, DocRefIDCustomerPO, DocRefBOL, DocRefCustomerPO, and BillingInvoiceLocation.
  • In the BLinvoice transaction node, the Location field was added.
  • In Assign8960, the BillingInvoiceLocation variable was mapped to BLinvoice_Location.
  • In Branch1660, verification of whether a WareHouseShipment record exists was added.
    • If the record exists, it is moved to the new Transaction node WShipmentBOL and Assign8610.
    • If the record exists and IntegrationApplication = Local.ly and Country = Mexico, DocRefBOLIDocRefBOL = BOL and DocRefIDBOL = WareHouseShipment.BillOfLading. If the record does not exist, the record is moved to the existing Continue flow to Branch1840.
  • In Assign430, the JavaScript was modified.
    • If IntegrationApplication = Local.ly and Country = Mexico, DocRefCustomerPO is mapped to CustomerPurchaseOrder and DocRefIDCustomerPO is mapped to BLinvoice_CustomerPurchaseOrder. Otherwise, the DocRefCustomerPO and DocRefIDCustomerPO values are blank.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the BODtrigger check box is selected.
  2. Enable the Service Definition and Processes for FSM_ION_SyncInvoice_Outbound IPA flow.
  3. Open the Service Definition and enable ReceivableInvoiceService for FSM_ION_SyncInvoice_Outbound.lpd Processes.
  4. Create a CustomerOrder and provide respective details. For example, CustomerPurchaseOrder and CertificationNumber. Release it.
  5. Run WarehousePickListPrint.
  6. Run WareHouseShipment. A record is created and a Bill Of Lading is provided.
  7. Release WareHouseShipment.
  8. Run Order Entry Daily Shipment Journal.
  9. A BillingInvoice record is created.
  10. Run InvoiceAndVerificationReport.
  11. Run InvoiceAndRegisterPrint.
  12. Run SubSystemUpdate.
  13. A ReceivableInvoice record is created in a Released state.
  14. A BOD is triggered and a work unit is created with the added element.
  15. Verify these new x-paths:
    • InvoiceLine/DocumentReference@type
    • InvoiceLine/DocumentReference/DocumentID/ID

JT-1399196

FSM_ION_SyncChartOfAccounts_Outbound - Native LPL

Missing elements were added in FSM_ION_SyncChartOfAccounts_Outbound-- Native LPL.

Program/Business class/Process affected:

  • SyncChartOfAccounts_Header_ST UserTemplate

Use these steps to test the enhancement:

  1. Enable FSMBODConfiguration enable BOD for ChartofAccounts.
  2. Create a ReportingChartAccount.
  3. Select the IONOutBoxQueue. A work unit is created.
  4. Select the User area. Missing elements are populated.
<Property>
<NameValue name="fsm.AccountType" type="StringType">Asset</NameValue>
</Property>
<Property>
<NameValue name="fsm.ParentChartAccount" type="StringType">2_JYO798</NameValue>
</Property>

JT-1345710

Testing Native LPL for LCL Tax Report BOD

Line level TaxID details are now populating correctly.

Program/Business class/Process affected:

Files that are changed:

  • TaxEntity.busclass

New IPA changes:

  • When vatReportingLine.Source is Not I or o, then taxID details are displayed.

Use these steps to test the enhancement:

  1. Create a Payables invoice with tax and release it.
  2. Run Cash Requirements.
  3. Run Electronic Payment Creations.
  4. Run Payment Close.
  5. Run Vat Return Report. A BOD is triggered and a work unit is created successfully.
  6. When vatReportingLine.Source is empty, then TaxReportLine/TaxID details are displayed.

JT-1389210

PendingNativeLPLConversion: Sync.Contract_Outbound

Changes were made in Sync.Contract_Outbound.

Program/Business class/Process affected:

  • Contract.busclass
  • ContractLine.busclass

Use these steps to test the enhancement:

  1. Enable the Sync.Contract_Outbound in FSMBODConfiguration.
  2. Create a contract with Inventory Item and Service Item. Check the XML for the value Populated in the x-path Contract/ContractSchedule/Item/ItemId/Id as FEG@@ItemGroup@@Item and Item respectively.
  3. For release and activate of Contract, check the XML for the value Populated in the x-path Contract/ContractSchedule/Status/Code as Pending and Open respectively.
  4. Release the contract, activate the contract, and check the x-paths.
  5. Create a contract with Inventory Item and check the XML for the value Populated in the x-path Contract/ContractSchedule/ContractPrice/ContractAmount and Contract/ContractSchedule/ContractPrice/ContractBaseAmount. The value is 0 if BaseCost is not specified.
  6. Release the contract and check the x-path.

JT-1391150

Real invoice numbers in SSJE BOD

Invoice details were added to the ListID attribute for Userarea x-path for Integration Local.ly and Country France.

Program/Business class/Process affected:

Files changed:

  • FSM_ION_SyncSourceSystemJournalEntry_Out.lpd

IPA changes:

  • The InvoiceArray variable was added in the start node.
  • Changed Node Assign7700: if System is BL, Invoice Details are stored in InvoiceArray Array Variable.
  • Changed Node Assign1430: if System is AP, Value of APGLTransDetail_DerivedAPInvoice is assigned to ListID Attribute of Userarea/Property.
  • Changed Node Assign8230: if System is AR, Value of RecGLDist_Invoice is Assigned to ListID Attribute of Userarea/Property
  • Changed NodeGLTRN_VAR: Billing Invoice details are assigned to ListID Attribute of Userarea/Property.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the BODtrigger check box is selected.
  2. Enable the Service Definition GLJournalControlService for FSM_ION_SyncSourceSystemJournalEntry_Out.lpd.

Billing scenario:

  1. Create a Billing invoice and release it.
  2. Run the Invoice Verification Report.
  3. Run Invoice and Register Print.
  4. Run Sub System Update.
  5. Journals are created in a Released state. Run Quick Post on them.
  6. The BOD is triggered.

Receivables scenario:

  1. Create ReceivableInvoiceBatch and release it.
  2. Journalize the distributions created. A journal is created in a Released state.
  3. Run Quick Post. The record is moved to a Posted state.
  4. The BOD is triggered.

Payables Scenario:

  1. Create and release a Payables invoice with distributions.
  2. Journalize the distributions. A journal is created in a Released state.
  3. Run Quick Post. The record is moved to the Posted tab.
  4. The BOD is triggered.

Verify the Result:

  1. Verify the ListID Attribute in Line level Userarea/Property.

JT-1393156

PendingNativeLPLConversion: TAX ID element in SyncInvoice/ShipFromParty

The TAX ID element was added in SyncInvoice/ShipFromParty.

Program/Business class/Process affected:

  • BillingInvoiceLine
  • UserTemplate

Use these steps to test the enhancement:

  1. In FSMBODConfiguration, enable the setup for NativeLPL - SyncInvoice Outbound.
  2. Trigger the SyncInvoice BOD for Local.ly, Country India.
  3. The BOD is triggered and IONOutboxQueue is generated. A new element is available in the respective x-path.

JT-1393174

PendingNativeLPLConversion: Sync Invoice Outbound BOD - Localization Services

Changes were made to Sync Invoice Outbound BOD - Localization Services.

Program/Business class/Process affected:

  • ReceivableInvoice

Use these steps to test the enhancement:

  1. In FSMBODConfiguration, enable the setup for NativeLPL - SyncInvoice Outbound.
  2. Trigger the SyncInvoice BOD for Local.ly.
  3. The BOD is triggered and IONOutboxQueue is generated. A new element is available in the respective x-path.

JT-1393175

PendingNativeLPLConversion: CountrySubDivisionCode node in Sync Invoice BOD

The CountrySubDivisionCode node is correctly mapped to the Customerparty node in the Sync Invoice BOD.

Program/Business class/Process affected:

  • UserTempate

Use these steps to test the enhancement:

  1. In FSMBODConfiguration, enable the setup for NativeLPL - SyncInvoice Outbound.
  2. Trigger the SyncInvoice BOD.
  3. The BOD is triggered and IONOutboxQueue is generated and element is mapped correctly.

    X-path: InvoiceHeader/CustomerParty/Location/Address/CountrySubDivisionCode is mapped to Customer.PostalAddress.StateProvince.

JT-1393177

PendingNativeLPLConversion: CountrySubDivisioncode in Shiptoparty node for SyncInvoice BOD

The CountrySubDivisioncode was added in the Shiptoparty node for the SyncInvoice BOD.

Program/Business class/Process affected:

  • ReceivableIvoice
  • BillingInvoiceLine
  • UserTemplate

Use these steps to test the enhancement:

  1. In FSMBODConfiguration, enable the setup for NativeLPL - SyncInvoice Outbound.
  2. Trigger the SyncInvoice BOD for Local.ly.
  3. The BOD is trigger and a work unit is generated. A new element is available in the respective x-path.

JT-1393181

PendingNativeLPLConversion: elements and map for Sync Invoice BOD - Localization Services

Elements were added and mapped for the Sync Invoice BOD for Localization Services.

Program/Business class/Process affected:

  • ReceivableIvoice
  • BillingInvoiceLine
  • UserTemplate

Use these steps to test the enhancement:

  1. In FSMBODConfiguration, enable the setup for NativeLPL - SyncInvoice Outbound.
  2. Trigger the SyncInvoice BOD for Local.ly.
  3. The BOD is triggered and a work unit is generated. A new element is available in the respective x-path.

JT-1393183

IPA configuration variable for Sync.CaptureDocument process flow

There is a new IPA configuration variable for the Sync.CaptureDocument process flow.

Program/Business class/Process affected:

  • modules/framework/bl/IEFINPostUpgradeAction.busclass
  • plugins/iefinconnector/ipa_content/PfiConfigurationProperty.xml
  • plugins/iefinconnector/pflows/inbound_process/FSM_ION_SyncCaptureDocument_Inbound.lpd

Use these steps to test the enhancement:

  1. Sign in as Process Server Administrator.
  2. Select Configuration > System Configuration.
  3. Open the FSM_ION_Connector configuration and select Properties.
  4. Specify a value for the SyncCaptureDocument_In_FinanceEnterpriseGroup variable.
  5. Send Sync.CaptureDocument BOD to CSF with or without finance enterprise group and company values from the BOD.
  6. Check the created work unit.
  7. Check the created record in Document Interface Invoices.

JT-1395856

Zero period to Localization Services in the Financial calendar BOD

Zero period values were added in the FSM_ION_SyncFinancialCalendar_Out BOD for Localization Services, specific to country France.

Program/Business class/Process affected:

Files changed:

  • FSM_ION_SyncFinancialCalendar_Out (GeneralLedgerClosePeriodService)
  • PfiConfigurationProperty.xml
  • IEFINPostUpgradeAction BusinessClass

Required setup:

  • The System Configuration parameter FinancialCalendar_With_BeginningBalance was added. Set the value to Y or Empty based on the scenario.
  • The System Configuration parameter IntegrationApplication was added. Set the value to Local.ly.

IPA changes:

  • In FSM_ION_SyncFinancialCalendar_Out, IPA flow changes were made by adding these variables to the start node:
    • PeriodXML
    • BeginningBalancePeriod
    • FinalXML
    • BeginningBalancePeriodName
    • BeginningBalanceFlag and assigned the FinancialCalendar_With_BeginningBalance parameter
    • IntegrationApplication
  • The Assign8230 node was added.
  • Assigned GLCYr_GeneralLedgerCloseYear to BeginningBalancePeriod with 000.
  • If IntegrationApplication = Local.ly and FinancialCalendar_With_BeginningBalance = Y, then PeriodXML is created with respective Zero Period changes.
  • Appended the PeriodXML in XML_CalYear XML.

Use these steps to test the enhancement:

  1. In FinanceEnterpriseGroup, verify that the BODtrigger check box is selected.
  2. For Outbound BOD, enable the Service Definition GeneralLedgerClosePeriodService for the FSM_ION_SyncFinancialCalendar_Out Processes.
  3. In System Configuration, specify Y for FinancialCalendar_With_BeginningBalance.
  4. In System Configuration, specify Local.ly for IntegrationApplication.
  5. Select Finance Enterprise Group > Calendar > Hierarchy > Create Calendar Year.
  6. Open CloseConfiguration and select Create a Year.
  7. Select the Year and open the Helper list. Select the GeneralLedgerCloseConfiguration Periods and select CreateClosePeriod.
  8. The BOD is triggered and a work unit is created for FSM_ION_SyncFinancialCalendar_Out BOD (GeneralLedgerClosePeriodService).
  9. Verify the results. If IntegrationApplication = Local.ly and FinancialCalendar_With_BeginningBalance = Y, then Period XML Zero Period values are appended to the existing CalendarYear/Period Xpaths.
    • FinancialCalendar/CalendarYear/Period/PeriodID is appended with BeginningBalancePeriod with 000.
    • FinancialCalendar/CalendarYear/Period/Name
    • FinancialCalendar/CalendarYear/Period/ShortName
    • FinancialCalendar/CalendarYear/Period/Status/Code
    • FinancialCalendar/CalendarYear/Period/EffectiveTimePeriod/StartDateTime
    • FinancialCalendar/CalendarYear/Period/EffectiveTimePeriod/EndDateTime
    • FinancialCalendar/CalendarYear/Period/PeriodTypeCode

JT-1399446

Updates to CSF replicate sets

Updates were made to the replication sets that were delivered with CSF to support the 11.0.8 Birst content release.

Program/Business class/Process affected:

These business classes have been added to the CSF replication sets:

  • FSM_AR_ST--SalesRepresentative
  • FSM_GL_ST--AddressCode
  • FSM_PO_ST--Buyer
  • FSM_PO_ST--Supplier

These fields have been added to existing replication set business classes:

FSM_AR_ST--CompanyCustomer--AdministrativeFee

FSM_AR_ST--CompanyCustomer--AdvancedDunningLetterFromAndReplyToEmail

FSM_AR_ST--CompanyCustomer--Affiliate

FSM_AR_ST--CompanyCustomer--AffiliateOwnership

FSM_AR_ST--CompanyCustomer--AgeDisputesRule

FSM_AR_ST--CompanyCustomer--AgingCode

FSM_AR_ST--CompanyCustomer--Agings

FSM_AR_ST--CompanyCustomer--AlternateEDINumber

FSM_AR_ST--CompanyCustomer--AlternateEDIType

FSM_AR_ST--CompanyCustomer--ApplicationCode

FSM_AR_ST--CompanyCustomer--ApplicationDiscountGraceDays

FSM_AR_ST--CompanyCustomer--ApplyMixedSignedLineItemsAutomatically

FSM_AR_ST--CompanyCustomer--AssessDunningFee

FSM_AR_ST--CompanyCustomer--AutomaticApplicationMethod

FSM_AR_ST--CompanyCustomer--AutomaticCashApplication

FSM_AR_ST--CompanyCustomer--AutomaticDunning

FSM_AR_ST--CompanyCustomer--AutomaticTransactionRemoval

FSM_AR_ST--CompanyCustomer--BalanceForwardStatementCycle

FSM_AR_ST--CompanyCustomer--BankTransactionCode

FSM_AR_ST--CompanyCustomer--BasicDunningLetterFromAndReplyToEmail

FSM_AR_ST--CompanyCustomer--BillingInvoiceFromAndReplyToEmail

FSM_AR_ST--CompanyCustomer--BillOfExchangeBalance

FSM_AR_ST--CompanyCustomer--BillOfExchangeProcessing

FSM_AR_ST--CompanyCustomer--CarrierFlag

FSM_AR_ST--CompanyCustomer--ChargeMinimumFinanceCharge

FSM_AR_ST--CompanyCustomer--CollectDayses

FSM_AR_ST--CompanyCustomer--Contact

FSM_AR_ST--CompanyCustomer--CreditAgencyPostalAddress

FSM_AR_ST--CompanyCustomer--CreditBalanceStatement

FSM_AR_ST--CompanyCustomer--CurrentCashDays

FSM_AR_ST--CompanyCustomer--CurrentCashPaid

FSM_AR_ST--CompanyCustomer--CustomerChangeAudit

FSM_AR_ST--CompanyCustomer--DaysBeyondTermsCash

FSM_AR_ST--CompanyCustomer--DaysBeyondTermsCashDays

FSM_AR_ST--CompanyCustomer--DaysBeyondTermsPriorYear

FSM_AR_ST--CompanyCustomer--DaysBeyondTermsRatio

FSM_AR_ST--CompanyCustomer--DaysBeyondTermsYearToDateCash

FSM_AR_ST--CompanyCustomer--DaysBeyondTermsYearToDateDays

FSM_AR_ST--CompanyCustomer--DebitCreditMemoTermsCode

FSM_AR_ST--CompanyCustomer--DetailChargebackDate

FSM_AR_ST--CompanyCustomer--DiscountAdjustmentReason

FSM_AR_ST--CompanyCustomer--DishonoredBillOfExchangeTotal

FSM_AR_ST--CompanyCustomer--DishonoredRenegotiatedBillOfExchange

FSM_AR_ST--CompanyCustomer--DisputedTransFinanceCharged

FSM_AR_ST--CompanyCustomer--DunningCycle

FSM_AR_ST--CompanyCustomer--DunningLetterIndicator

FSM_AR_ST--CompanyCustomer--DunningProcessCode

FSM_AR_ST--CompanyCustomer--EDINumber

FSM_AR_ST--CompanyCustomer--EmailAddress

FSM_AR_ST--CompanyCustomer--EmailAdvancedDunningLetter

FSM_AR_ST--CompanyCustomer--EmailBasicDunningLetter

FSM_AR_ST--CompanyCustomer--EmailBillingInvoice

FSM_AR_ST--CompanyCustomer--EmailPaymentRequestNotice

FSM_AR_ST--CompanyCustomer--EmailReceivablesStatement

FSM_AR_ST--CompanyCustomer--FaxNumber

FSM_AR_ST--CompanyCustomer--FinanceChargeCalculationMethod

FSM_AR_ST--CompanyCustomer--FinanceChargeCode

FSM_AR_ST--CompanyCustomer--FinanceChargeCycle

FSM_AR_ST--CompanyCustomer--FinanceChargeDueDateGraceDays

FSM_AR_ST--CompanyCustomer--ForeignEconomicRegulatoryCode

FSM_AR_ST--CompanyCustomer--HigHBalance

FSM_AR_ST--CompanyCustomer--IDMPaymentRequestNoticeSequenceNumber

FSM_AR_ST--CompanyCustomer--InterfaceInProcess

FSM_AR_ST--CompanyCustomer--InvoiceMinimumFinanceCharge

FSM_AR_ST--CompanyCustomer--InvPaids

FSM_AR_ST--CompanyCustomer--LanguageCode

FSM_AR_ST--CompanyCustomer--LastComment

FSM_AR_ST--CompanyCustomer--LastDunningLetter

FSM_AR_ST--CompanyCustomer--LastDunningLetterDate

FSM_AR_ST--CompanyCustomer--LastDunningLetterTextCode

FSM_AR_ST--CompanyCustomer--LastInvoiceAmount

FSM_AR_ST--CompanyCustomer--LastInvoiceDate

FSM_AR_ST--CompanyCustomer--LastLetterDate

FSM_AR_ST--CompanyCustomer--LastStatementBalance

FSM_AR_ST--CompanyCustomer--LastStatementDate

FSM_AR_ST--CompanyCustomer--LatePaymentAndFinanceCharges

FSM_AR_ST--CompanyCustomer--MaxAutoPcts

FSM_AR_ST--CompanyCustomer--MaximumAutoAdjustAmount

FSM_AR_ST--CompanyCustomer--MaximumOverageAmount

FSM_AR_ST--CompanyCustomer--MaximumOveragePercent

FSM_AR_ST--CompanyCustomer--MaximumOverageReasonCode

FSM_AR_ST--CompanyCustomer--MaximumShortReasonCode

FSM_AR_ST--CompanyCustomer--MinimumFinanceChargeAmount

FSM_AR_ST--CompanyCustomer--MultipleDunningLetters

FSM_AR_ST--CompanyCustomer--NumberOfDishonoredBillOfExchange

FSM_AR_ST--CompanyCustomer--ObjectID

FSM_AR_ST--CompanyCustomer--OpenItemStatementCycle

FSM_AR_ST--CompanyCustomer--OriginatingInterfaceRun

FSM_AR_ST--CompanyCustomer--OverCreditLimitStatement

FSM_AR_ST--CompanyCustomer--PaidPrmpts

FSM_AR_ST--CompanyCustomer--PastDueOnlyStatement

FSM_AR_ST--CompanyCustomer--PaymentRequestNoticeFromAndReplyToEmail

FSM_AR_ST--CompanyCustomer--PerRtmses

FSM_AR_ST--CompanyCustomer--PhoneNumber

FSM_AR_ST--CompanyCustomer--PrintAdvancedDunningLetter

FSM_AR_ST--CompanyCustomer--PrintBasicDunningLetter

FSM_AR_ST--CompanyCustomer--PrintBillingInvoice

FSM_AR_ST--CompanyCustomer--PrintChargebacks

FSM_AR_ST--CompanyCustomer--PrintFinanceChargeDocument

FSM_AR_ST--CompanyCustomer--PrintPaymentRequestNotice

FSM_AR_ST--CompanyCustomer--PrintReceivablesStatement

FSM_AR_ST--CompanyCustomer--ProcessLevelRestrictions

FSM_AR_ST--CompanyCustomer--ReceivableDefaultCode

FSM_AR_ST--CompanyCustomer--ReceivableGeneralLedgerCode

FSM_AR_ST--CompanyCustomer--ReceivableLockBox

FSM_AR_ST--CompanyCustomer--ReceivableProcessingMethod

FSM_AR_ST--CompanyCustomer--ReceivablesStatementFromAndReplyToEmail

FSM_AR_ST--CompanyCustomer--ReceivableStatementCycle

FSM_AR_ST--CompanyCustomer--ReconciledDishonoredBillOfExchange

FSM_AR_ST--CompanyCustomer--RevalueCurrencyTransactions

FSM_AR_ST--CompanyCustomer--ReviewCode

FSM_AR_ST--CompanyCustomer--ReviewDate

FSM_AR_ST--CompanyCustomer--SocialNetworkID2

FSM_AR_ST--CompanyCustomer--SocialNetworkID3

FSM_AR_ST--CompanyCustomer--SocialNetworkID4

FSM_AR_ST--CompanyCustomer--SocialNetworkID5

FSM_AR_ST--CompanyCustomer--StartDate

FSM_AR_ST--CompanyCustomer--StatementRequired

FSM_AR_ST--CompanyCustomer--StaticAgingCurrentPeriodAmount

FSM_AR_ST--CompanyCustomer--TaxCode

FSM_AR_ST--CompanyCustomer--TaxExempt

FSM_AR_ST--CompanyCustomer--TelexNbr

FSM_AR_ST--CompanyCustomer--TwitterID

FSM_AR_ST--CompanyCustomer--URLAddress

FSM_AR_ST--CompanyCustomer--VATValidation

FSM_AR_ST--CompanyCustomer--WriteOffDishonoredBillOfExchange

FSM_AR_ST--CompanyCustomer--Year2CollectionDays

FSM_AR_ST--CompanyCustomer--YearToDateCashDays

FSM_AR_ST--CompanyCustomer--ZeroBalanceStatement

FSM_AR_ST--CompanyCustomer--Customer cube dimension value

FSM_AR_ST--CompanyCustomer--SalesRepresentative cube dimension value

FSM_AR_ST--ReceivableInvoiceDetail--HSNSACCode

FSM_AR_ST--ReceivableInvoiceDetail--LineType

FSM_AR_ST--ReceivableInvoiceDetail--Customer cube dimension value

FSM_AR_ST--ReceivableInvoiceDetail--SalesRepresentative cube dimension value

FSM_AR_ST--ReceivablePayment--BackgroundProcessing

FSM_AR_ST--ReceivablePayment--Customer cube dimension value

FSM_AR_ST--ReceivablePayment--ReceivablePaymentHeader.DepositBankCode

FSM_AR_ST--ReceivableInvoice--Customer cube dimension value

FSM_AR_ST--ReceivableInvoice--SalesRepresentative cube dimension value

FSM_AR_ST--Customer--Customer cube dimension value

FSM_AR_ST--SalesRepresentative--Company

FSM_AR_ST--SalesRepresentative--SalesRepresentative

FSM_AR_ST--SalesRepresentative--Active

FSM_AR_ST--SalesRepresentative--CommisionPercent

FSM_AR_ST--SalesRepresentative--Name

FSM_AR_ST--SalesRepresentative--create stamp

FSM_AR_ST--SalesRepresentative--update stamp

FSM_AR_ST--SalesRepresentative--Territory

FSM_AR_ST--SalesRepresentative--UniqueID

FSM_AR_ST--SalesRepresentative--UsedByATransaction

FSM_AR_ST--SalesRepresentative--UsedFlag

FSM_AR_ST--SalesRepresentative--SalesRepresentative cube dimension value

FSM_BL_ST--BillingCompany--AcknowledgeCommentOptions

FSM_BL_ST--BillingCompany--AuditOrder

FSM_BL_ST--BillingCompany--AuditPrice

FSM_BL_ST--BillingCompany--BaseNumberOfDecimals

FSM_BL_ST--BillingCompany--BillingCompanySetupIncomplete

FSM_BL_ST--BillingCompany--BillingInvoiceDocument

FSM_BL_ST--BillingCompany--BillingInvoiceEmailSubject

FSM_BL_ST--BillingCompany--BillingInvoiceEmailTemplate

FSM_BL_ST--BillingCompany--BillingInvoiceTemplate

FSM_BL_ST--BillingCompany--BillingOperatorControl

FSM_BL_ST--BillingCompany--CompanyAddress

FSM_BL_ST--BillingCompany--DailyShipmentJournalCommentOptions

FSM_BL_ST--BillingCompany--DailyShipmentJournalIDMTemplate

FSM_BL_ST--BillingCompany--DefaultCurrencyOverride

FSM_BL_ST--BillingCompany--DiscountAccount

FSM_BL_ST--BillingCompany--EuropeanCommunityCountry

FSM_BL_ST--BillingCompany--ExpenseAccount

FSM_BL_ST--BillingCompany--IDMDocumentForInvoiceRegister

FSM_BL_ST--BillingCompany--IDMOrderEntryDailyShipmentJournalTemplate

FSM_BL_ST--BillingCompany--Incomplete

FSM_BL_ST--BillingCompany--InvoiceAndRegisterPrintIDMTemplate

FSM_BL_ST--BillingCompany--InvoiceCreation

FSM_BL_ST--BillingCompany--InvoiceEdit

FSM_BL_ST--BillingCompany--InvoiceEditOption

FSM_BL_ST--BillingCompany--InvoicePrint

FSM_BL_ST--BillingCompany--InvoiceRegisterCommentOptions

FSM_BL_ST--BillingCompany--InvoiceRegisterTemplate

FSM_BL_ST--BillingCompany--InvoiceUpdate

FSM_BL_ST--BillingCompany--ISOCountry

FSM_BL_ST--BillingCompany--ManualReturnNumbering

FSM_BL_ST--BillingCompany--MultipleSalesAccountEntry

FSM_BL_ST--BillingCompany--ProformaInvoiceDocument

FSM_BL_ST--BillingCompany--QuotationCommentOptions

FSM_BL_ST--BillingCompany--ReleaseCommentOptions

FSM_BL_ST--BillingCompany--RemitToAddress

FSM_BL_ST--BillingCompany--RemitToEuropeanCommunityCountry

FSM_BL_ST--BillingCompany--RemitToISOCountry

FSM_BL_ST--BillingCompany--RoundingAccount

FSM_BL_ST--BillingCompany--SalesAccount

FSM_BL_ST--BillingCompany--SpecialOrderCOGSAccount

FSM_BL_ST--BillingCompany--SpecialOrderSalesAccount

FSM_BL_ST--BillingCompany--TaxCalulationAndPrinting

FSM_BL_ST--BillingCompany--UnitOfMeasureRequired

FSM_BL_ST--BillingCompany--UseIDM

FSM_BL_ST--BillingCompany--UseIDMInInvoiceRegister

FSM_BL_ST--BillingCompany--VATOutputOffset

FSM_BL_ST--BillingInvoice--AuthorizationNumber

FSM_BL_ST--BillingInvoice--AutoApply

FSM_BL_ST--BillingInvoice--BankTransactionCode

FSM_BL_ST--BillingInvoice--BillingInvoice

FSM_BL_ST--BillingInvoice--BillTo

FSM_BL_ST--BillingInvoice--BillToEuropeanCommunityCountry

FSM_BL_ST--BillingInvoice--BillToISOCountry

FSM_BL_ST--BillingInvoice--BillToRegion

FSM_BL_ST--BillingInvoice--CashInAdvance

FSM_BL_ST--BillingInvoice--CashOnDeliveryPrint

FSM_BL_ST--BillingInvoice--CostProject

FSM_BL_ST--BillingInvoice--CurrencyMultiplicationOrDivision

FSM_BL_ST--BillingInvoice--CurrencyNumberOfDecimals

FSM_BL_ST--BillingInvoice--ElectronicPaymentExpirationDate

FSM_BL_ST--BillingInvoice--ElectronicPaymentSettlementAmount

FSM_BL_ST--BillingInvoice--ElectronicPaymentTransactionID

FSM_BL_ST--BillingInvoice--ElectronicPaymentTransactionID2

FSM_BL_ST--BillingInvoice--EnteredDiscount

FSM_BL_ST--BillingInvoice--EWayBillNumber

FSM_BL_ST--BillingInvoice--FreightCharge

FSM_BL_ST--BillingInvoice--GlobalDocumentType

FSM_BL_ST--BillingInvoice--HoldCode

FSM_BL_ST--BillingInvoice--IDMJob

FSM_BL_ST--BillingInvoice--IDMUniqueID

FSM_BL_ST--BillingInvoice--InterfaceInProcess

FSM_BL_ST--BillingInvoice--IntrastatNumber

FSM_BL_ST--BillingInvoice--LastAddOnChargeSequence

FSM_BL_ST--BillingInvoice--LastBottomCommentLine

FSM_BL_ST--BillingInvoice--LastTopCommentLine

FSM_BL_ST--BillingInvoice--LetterOfCredit

FSM_BL_ST--BillingInvoice--ListName

FSM_BL_ST--BillingInvoice--OrderDiscount

FSM_BL_ST--BillingInvoice--OrderReferenceNumberUser

FSM_BL_ST--BillingInvoice--OriginalBillingInvoice

FSM_BL_ST--BillingInvoice--OriginatingInterfaceRun

FSM_BL_ST--BillingInvoice--ParallelReference

FSM_BL_ST--BillingInvoice--ReasonCode

FSM_BL_ST--BillingInvoice--ReceivableDetailPosting

FSM_BL_ST--BillingInvoice--ReceivableGeneralLedgerCode

FSM_BL_ST--BillingInvoice--ReceivableLineLevelInterface

FSM_BL_ST--BillingInvoice--Reference

FSM_BL_ST--BillingInvoice--RegimeCode

FSM_BL_ST--BillingInvoice--RequireElectronicPaymentSettlement

FSM_BL_ST--BillingInvoice--SalesAnalysisInterface

FSM_BL_ST--BillingInvoice--ShipToEuropeanCommunityCountry

FSM_BL_ST--BillingInvoice--ShiptoISOCountry

FSM_BL_ST--BillingInvoice--TaxTotal

FSM_BL_ST--BillingInvoice--TermsDiscount

FSM_BL_ST--BillingInvoice--TotalAddOnAmount

FSM_BL_ST--BillingInvoice--TotalInventoryGoodsAmount

FSM_BL_ST--BillingInvoice--TotalNoninventoryGoodsAmount

FSM_BL_ST--BillingInvoice--UserDefinedField1

FSM_BL_ST--BillingInvoice--UserDefinedField2

FSM_BL_ST--BillingInvoice--UserDefinedField3

FSM_BL_ST--BillingInvoice--UserDefinedField4

FSM_BL_ST--BillingInvoice--UserDefinedField5

FSM_BL_ST--BillingInvoice--CustomerOrderRel.CustomerOrder cube dimension value

FSM_BL_ST--BillingInvoiceLine--BillingInvoice

FSM_BL_ST--BillingInvoiceLine--COGSAccount

FSM_BL_ST--BillingInvoiceLine--DiscountAccountArray

FSM_BL_ST--BillingInvoiceLine--HSNSACCode

FSM_BL_ST--BillingInvoiceLine--LastAddOnChargeSequence

FSM_BL_ST--BillingInvoiceLine--LastCommentSequence

FSM_BL_ST--BillingInvoiceLine--LineNetAmount

FSM_BL_ST--BillingInvoiceLine--OffsetAccount

FSM_BL_ST--BillingInvoiceLine--Promotion

FSM_BL_ST--BillingInvoiceLine--SalesAccount

FSM_BL_ST--BillingInvoiceLine--SecondaryUOM

FSM_BL_ST--BillingInvoiceLine--SecondaryUOMMultiplier

FSM_BL_ST--BillingInvoiceLine--TaxableAmount

FSM_BL_ST--BillingInvoiceLine--TaxableCurrencyAmount

FSM_BL_ST--BillingInvoiceLine--UserField1

FSM_BL_ST--BillingInvoiceLine--UserField2

FSM_BL_ST--BillingInvoiceLine--UserField3

FSM_FR_ST--FranchiseContract--BillingCreditMemoInvoiceType

FSM_FR_ST--FranchiseContract--BillingInvoiceType

FSM_FR_ST--FranchiseContract--CalculateInvoiceAmountOnGrossSales

FSM_FR_ST--FranchiseContract--CalculateTaxOnNetSales

FSM_FR_ST--FranchiseSales--CycleNumber

FSM_FR_ST--FranchiseSales--InvoicePrefix

FSM_FR_ST--FranchiseContractCharge--AccrualAccount

FSM_FR_ST--FranchiseContractCharge--AccrualOffsetAccount

FSM_FR_ST--FranchiseContractCharge--CalculationType

FSM_FR_ST--FranchiseContractCharge--Description

FSM_FR_ST--FranchiseContractCharge--InitializeSpecialCharges

FSM_FR_ST--FranchiseContractCharge--NoteAccrual

FSM_FR_ST--FranchiseContractCharge--NoteAccrualOffsetAccount

FSM_FR_ST--FranchiseContractCharge--NoteAssetAccount

FSM_FR_ST--FranchiseContractCharge--ProcessLevel

FSM_FR_ST--FranchiseContractCharge--RevenueAccount

FSM_FR_ST--FranchiseContractCharge--StepLimits

FSM_FR_ST--FranchiseContractCharge--StepPercents

FSM_FR_ST--FranchiseContractCharge--FranchiseStandardCharge.Currency

FSM_IC_ST--Item--CriticalItem

FSM_IC_ST--Item--PersonalProtectiveEquipment

FSM_IC_ST--ItemLocation--Buyer cube dimension value

FSM_MA_ST--MatchInvoiceMessage--PayablesInvoice cube dimension value

FSM_MA_ST--MatchInvoiceMessage--PayablesInvoiceDetail cube dimension value

FSM_MA_ST--MatchInvoiceMessage--ItemGTIN cube dimension value

FSM_MA_ST--MatchInvoiceMessage--Buyer cube dimension value

FSM_OE_ST--CustomerOrder--Acknowledgement

FSM_OE_ST--CustomerOrder--AcknowledgementPrinted

FSM_OE_ST--CustomerOrder--BankPaymentCode

FSM_OE_ST--CustomerOrder--BillECCountry

FSM_OE_ST--CustomerOrder--BillISOCountry

FSM_OE_ST--CustomerOrder--BillPostalAddress

FSM_OE_ST--CustomerOrder--BillingCustomerCreditCard

FSM_OE_ST--CustomerOrder--BillingFreightCode

FSM_OE_ST--CustomerOrder--Carrier

FSM_OE_ST--CustomerOrder--CheckNumber

FSM_OE_ST--CustomerOrder--CostProject

FSM_OE_ST--CustomerOrder--CreditWorkFlow

FSM_OE_ST--CustomerOrder--CurrencyMultiplicationOrDivision

FSM_OE_ST--CustomerOrder--CurrencyNumberOfDecimals

FSM_OE_ST--CustomerOrder--CurrencyOveride

FSM_OE_ST--CustomerOrder--CurrencyTable

FSM_OE_ST--CustomerOrder--CustomerOrder_BODId

FSM_OE_ST--CustomerOrder--CustomerOrder_CreateStamp

FSM_OE_ST--CustomerOrder--CustomerOrder_UpdateStamp

FSM_OE_ST--CustomerOrder--DiscountableAmount

FSM_OE_ST--CustomerOrder--EdiOeInterface

FSM_OE_ST--CustomerOrder--ElectronicPaymentAmount

FSM_OE_ST--CustomerOrder--ElectronicPaymentExpirationDate

FSM_OE_ST--CustomerOrder--ElectronicPaymentMinimumMargin

FSM_OE_ST--CustomerOrder--ElectronicPaymentMinimumMarginPercent

FSM_OE_ST--CustomerOrder--ElectronicPaymentSettlementAmount

FSM_OE_ST--CustomerOrder--ElectronicPaymentTransactionID

FSM_OE_ST--CustomerOrder--FreightTaxable

FSM_OE_ST--CustomerOrder--GlobalDocumentType

FSM_OE_ST--CustomerOrder--HoldCode

FSM_OE_ST--CustomerOrder--HoldCodeApprove

FSM_OE_ST--CustomerOrder--IntrastatNumber

FSM_OE_ST--CustomerOrder--InventoryGoodsAmount

FSM_OE_ST--CustomerOrder--LastAddOnChargeSequence

FSM_OE_ST--CustomerOrder--LastBottomCommentSequence

FSM_OE_ST--CustomerOrder--LastLineNumber

FSM_OE_ST--CustomerOrder--LastReferenceNumberForRequisition

FSM_OE_ST--CustomerOrder--LastTopCommentSequence

FSM_OE_ST--CustomerOrder--LetterOfCredit

FSM_OE_ST--CustomerOrder--ListName

FSM_OE_ST--CustomerOrder--NatureOfTransactionCode

FSM_OE_ST--CustomerOrder--NonInventoryGoodsAmount

FSM_OE_ST--CustomerOrder--OnProformaPaymentHold

FSM_OE_ST--CustomerOrder--OpenOrderAmount

FSM_OE_ST--CustomerOrder--OrderDiscountCode

FSM_OE_ST--CustomerOrder--OrderEntryCancelledOperator

FSM_OE_ST--CustomerOrder--OrderEntryChangeOperator

FSM_OE_ST--CustomerOrder--OrderEntryCreditOperator

FSM_OE_ST--CustomerOrder--OrderEntryOperator

FSM_OE_ST--CustomerOrder--OrderEntryOrderSource

FSM_OE_ST--CustomerOrder--OrderReferenceNumberUser

FSM_OE_ST--CustomerOrder--PaymentInvoiced

FSM_OE_ST--CustomerOrder--PickingListPrinted

FSM_OE_ST--CustomerOrder--ProofOfDeliveryGracePeriod

FSM_OE_ST--CustomerOrder--ProofOfDeliveryRequired

FSM_OE_ST--CustomerOrder--RateFreeze

FSM_OE_ST--CustomerOrder--RequireElectronicPaymentAuthorization

FSM_OE_ST--CustomerOrder--SalesAnalysisUpdate

FSM_OE_ST--CustomerOrder--ShipPostalAddress

FSM_OE_ST--CustomerOrder--ToECCountry

FSM_OE_ST--CustomerOrder--ToISOCountry

FSM_OE_ST--CustomerOrder--TotalOrderAmount

FSM_OE_ST--CustomerOrder--TransUser1

FSM_OE_ST--CustomerOrder--TransUser2

FSM_OE_ST--CustomerOrder--TransUser3

FSM_OE_ST--CustomerOrder--TransUser4

FSM_OE_ST--CustomerOrder--TransUser5

FSM_OE_ST--CustomerOrder--UserDate1

FSM_OE_ST--CustomerOrder--UserDate2

FSM_OE_ST--CustomerOrder--UserIdEntry

FSM_OE_ST--CustomerOrder--UserIdRelease

FSM_OE_ST--CustomerOrder--VATRegistrationNumber

FSM_OE_ST--CustomerOrder--WarehouseShipment

FSM_OE_ST--CustomerOrderReturn--AutomaticCashApplication

FSM_OE_ST--CustomerOrderReturn--BillingCustomerCreditCard

FSM_OE_ST--CustomerOrderReturn--CommentCount

FSM_OE_ST--CustomerOrderReturn--CreateCreditMemo

FSM_OE_ST--CustomerOrderReturn--CustomerOrderReturn_CreateStamp

FSM_OE_ST--CustomerOrderReturn--CustomerOrderReturn_UpdateStamp

FSM_OE_ST--CustomerOrderReturn--FreightCode

FSM_OE_ST--CustomerOrderReturn--GlobalDocumentType

FSM_OE_ST--CustomerOrderReturn--LastAddOnChargeSequence

FSM_OE_ST--CustomerOrderReturn--LastCommentSequence

FSM_OE_ST--CustomerOrderReturn--LastLineNumber

FSM_OE_ST--CustomerOrderReturn--LastSequence

FSM_OE_ST--CustomerOrderReturn--OriginalInvoice

FSM_OE_ST--CustomerOrderReturn--PhoneNumber

FSM_OE_ST--CustomerOrderReturn--UndecidedCommentCount

FSM_OE_ST--CustomerOrderReturn--UndecidedItemCount

FSM_OE_ST--CustomerOrderLine--AtnObjId

FSM_OE_ST--CustomerOrderLine--AtnObjIdC

FSM_OE_ST--CustomerOrderLine--BookedBySaleAnalysis

FSM_OE_ST--CustomerOrderLine--CostOfGoodsSoldAccount

FSM_OE_ST--CustomerOrderLine--CreatePurchaseOrder

FSM_OE_ST--CustomerOrderLine--CustomerOrderLine_CreateStamp

FSM_OE_ST--CustomerOrderLine--CustomerOrderLine_UpdateStamp

FSM_OE_ST--CustomerOrderLine--DiscountCode

FSM_OE_ST--CustomerOrderLine--ExpenseAccount

FSM_OE_ST--CustomerOrderLine--HSNSACCode

FSM_OE_ST--CustomerOrderLine--HoldCode

FSM_OE_ST--CustomerOrderLine--ICNCode

FSM_OE_ST--CustomerOrderLine--InterCompany

FSM_OE_ST--CustomerOrderLine--LastAddOnChargeSequence

FSM_OE_ST--CustomerOrderLine--LastCommentSequence

FSM_OE_ST--CustomerOrderLine--MaterialSafetyDataSheet

FSM_OE_ST--CustomerOrderLine--OriginalReplacementOrSubstitute

FSM_OE_ST--CustomerOrderLine--POCode

FSM_OE_ST--CustomerOrderLine--PortCode

FSM_OE_ST--CustomerOrderLine--ReferenceNumberForRequisition

FSM_OE_ST--CustomerOrderLine--RouteCreate

FSM_OE_ST--CustomerOrderLine--RouteHeader

FSM_OE_ST--CustomerOrderLine--RouteStop

FSM_OE_ST--CustomerOrderLine--SalesAccount

FSM_OE_ST--CustomerOrderLine--SecondaryToStock

FSM_OE_ST--CustomerOrderLine--SecondaryUOM

FSM_OE_ST--CustomerOrderLine--SellUOM

FSM_OE_ST--CustomerOrderLine--StatisticalProcedure

FSM_OE_ST--CustomerOrderLine--SupplementaryUOM

FSM_OE_ST--CustomerOrderLine--UserDate3

FSM_OE_ST--CustomerOrderLine--UserDate4

FSM_OE_ST--CustomerOrderLine--UserFld1

FSM_OE_ST--CustomerOrderLine--UserFld2

FSM_OE_ST--CustomerOrderLine--UserFld3

FSM_OE_ST--CustomerOrderLine--WorkOrderSuf

FSM_OE_ST--CustomerOrderReturnLine--AtnObjIdC

FSM_OE_ST--CustomerOrderReturnLine--CostOfGoodsSoldAccount

FSM_OE_ST--CustomerOrderReturnLine--CostVarianceAccount

FSM_OE_ST--CustomerOrderReturnLine--CustomerOrderReturnLine_CreateStamp

FSM_OE_ST--CustomerOrderReturnLine--CustomerOrderReturnLine_UpdateStamp

FSM_OE_ST--CustomerOrderReturnLine--HSNSACCode

FSM_OE_ST--CustomerOrderReturnLine--OffsetAccount

FSM_OE_ST--CustomerOrderReturnLine--RestockCharge

FSM_OE_ST--CustomerOrderReturnLine--SalesAccount

FSM_PO_ST--PurchaseOrderLine--ItemGTIN cube dimension value

FSM_PO_ST--Contract--Supplier cube dimension value

FSM_PO_ST--ContractLine--Contract.Supplier cube dimension value

FSM_PO_ST--ContractLine--GlobalTradeItemNumber cube dimension value

FSM_PO_ST--ContractLineMember--Contract.Supplier cube dimension value

FSM_PO_ST--PurchaseOrderBuyerMessage--PurchaseOrderReceipt cube dimension value

FSM_PO_ST--PurchaseOrderBuyerMessage--PurchaseOrderReceiptLine cube dimension value

FSM_PO_ST--PurchaseOrderBuyerMessage--PurchaseOrderBuyerMessage cube dimension value

FSM_PO_ST--PurchaseOrderBuyerMessage--Company.FinanceEnterpriseGroup

FSM_PO_ST--PurchaseOrderReceipt--Company.FinanceEnterpriseGroup

FSM_PO_ST--PurchaseOrderReceipt--Buyer cube dimension value

FSM_PO_ST--PurchaseOrderReceiptLine--Company.FinanceEnterpriseGroup

FSM_PO_ST--PurchaseOrderReceiptLine--ItemGTIN cube dimension value

FSM_PO_ST--PurchaseOrderReceiptLine--PurchaseOrderReceipt.Buyer cube dimension value

FSM_PO_ST--PurchaseOrderRevision--Company.FinanceEnterpriseGroup

FSM_RQ_ST--Requisition--Buyer cube dimension value

FSM_RQ_ST--RequisitionLine--ItemGTIN cube dimension value

FSM_RQ_ST--RequisitionLine--Buyer cube dimension value

FSM_TX_ST--TaxTransaction--TaxEntity cube dimension value

FSM_TX_ST--VatReportingLine--TaxEntity cube dimension value

These fields have been deleted:

FSM_BL_ST--BillingInvoice--RoundingLineRel.EnteredPrice

FSM_FR_ST--FranchiseContractCharge--FranchiseStandardCharge

Use these steps to test the enhancement:

  1. Verify that the changes listed are included in the CSF replication sets.
  2. Select all replication sets that begin with FSM_ and end with _ST. Right-click and select Validate Schemas.
  3. After about 30 seconds, a red exclamation point is displayed on the replication sets the have updates. Select each set with the red exclamation point and select Register Out Of Data Schemas.
  4. After registering out of date schemas, select ION Desk > Connection Points > FSM_IMS and click +. Select all tables that begin with FSM_ to the connection point and click Save.
  5. Add the new objects to the FSM DataLake document flow in ION Desk > Document Flows.

JT-1400518