ERP source validation on Sourcing and Procurement Operations objects

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of ERP source validation on Sourcing and Procurement Operations objects

    Sourcing and Procurement Operations supports multi-ERP integration, allowing different ERP systems to be used across various regions or business lines. This functionality validates the ERP source of primary data and ensures transaction data is correctly routed with appropriate attributes. These validations help maintain data accuracy and prevent integration errors across multiple ERP systems.

    Show full answer Show less

    Key Features

    • ERP Source Validation: Ensures that data fetched and transactions processed correspond to the correct ERP source based on the legal entity associated with the record.
    • Foreign Currency Handling: Supports foreign currency transactions by converting contract currency amounts into the local and reporting currencies of the legal entity using exchange rates from the Finance Exchange Rates (snfinfxrate) table, which is tied to ERP sources.
    • Currency Conversion Storage: Converted currency values are stored in the PSM FX Currencies (snshopfxcurrencyinstance) table for accurate financial processing.
    • Purchase Requisition Management: Purchase requisitions are split by currency of the purchase requisition lines, with conversions applied during checkout in the legal entity’s local currency.
    • Cost Center and GL Account Restrictions: Cost centers and GL accounts shown during record updates are filtered based on matching ERP sources, ensuring data consistency aligned with the legal entity’s ERP integration.
    • Error Handling: If records have mismatched ERP sources, integration error tasks are generated to prompt correction before further processing, reducing downstream integration failures.

    Practical Benefits for ServiceNow Customers

    • Enables reliable multi-ERP operations by ensuring accurate ERP source association for all procurement and sourcing objects.
    • Improves financial accuracy by handling currency conversions specific to each legal entity’s ERP system.
    • Prevents costly integration errors by detecting and flagging ERP source mismatches early in the process.
    • Enhances user experience in the Source-to-Pay Workspace by filtering relevant cost centers and GL accounts according to the ERP source.
    • Supports compliance with regional and business line-specific ERP requirements, facilitating smoother procurement operations across a global enterprise.

    Sourcing and Procurement Operations supports multi-ERP integration that enables you to use different ERP systems for different regions or lines of business, as required.

    Whenever Sourcing and Procurement Operations integrates with multiple ERPs, it validates the ERP from where the primary data is being fetched. It also ensures that the transaction data is routed to the right ERP with the right set of attributes. To validate ERP source to select correct attributes for Sourcing and Procurement Operations objects, and to support multi-ERP integration, these updates are enabled.

    Fx currency and conversion rates

    Conversion rates from the Finance Exchange Rates (sn_fin_fx_rate) table are used. This table has an ERP Source column, and records like purchase requisition and purchase order are also tied to the ERP Source column. By taking the legal entity and getting an ERP source from the legal entity, the right conversion rate is derived.

    Fx2 currency amount is converted into your legal entity local currency amount and legal entity reporting currency amount by using the conversion rate from the Finance Exchange Rates table. All these converted values are stored in the PSM FX Currencies (sn_shop_fx_currency_instance)​ table.

    Shopping Hub

    Foreign currency transactions are supported. A foreign currency transaction is one where the contract currency, also known as the transaction currency, is different from the local currency of the legal entity. For example, if an employee whose legal entity has a local currency of USD, purchases something which is in the contract currency of EUR, then it becomes a foreign currency transaction. In such cases,the contract amount is converted into the legal entity local currency in the shopping cart by using the exchange rate from the Finance Exchange Rates (sn_fin_fx_rate) table, where the ERP source in the Finance Exchange Rates table matches with the ERP source or legal entity of the employee.

    Also, purchase requisitions are split based on currency of the purchase requisition lines. Legal entity local currency is used to do the conversions during checkout.

    Cost center and GL account

    Cost center and GL account values are restricted by the ERP source on the object. The legal entity from the object is considered, and the ERP source is fetched. When a user updates the record, only those cost centers that have matching ERP sources are displayed in the Source-to-Pay Workspace.

    Note:
    These validations are enforced only when a legal entity has been set up for integration with ERPs. If you've set up integration with an ERP, then you’ll see the data having the same ERP source, thereby preventing downstream errors during integration.

    If there’s any record with different ERP sources, then an integration error task is raised. This is an indicator for your fulfiller to correct the record before processing it further.