ERP source validation on Sourcing and Procurement Operations objects

  • Release version: Yokohama
  • Updated January 30, 2025
  • 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 the use of different ERP systems across regions or business lines. It validates the ERP source from which primary data is fetched and ensures transaction data is routed correctly with appropriate attributes. This validation enhances data accuracy and prevents integration errors.

    Show full answer Show less

    Key Features

    • ERP Source Validation: Ensures that data such as purchase requisitions and purchase orders are linked to the correct ERP source based on the legal entity, supporting precise multi-ERP integration.
    • Foreign Currency Support: Supports foreign currency transactions where the contract currency differs from the legal entity’s local currency. Contract amounts are converted into local currency using exchange rates tied to the ERP source.
    • Currency Conversion: Uses conversion rates from the Finance Exchange Rates (snfinfxrate) table, which includes ERP source information, to convert amounts into local and reporting currencies. Converted values are stored in the PSM FX Currencies (snshopfxcurrencyinstance) table.
    • Cost Center and GL Account Restrictions: Displays only cost centers and GL accounts that match the ERP source tied to the legal entity, reducing data errors in the Source-to-Pay Workspace.
    • Error Handling: If records have inconsistent ERP sources, an integration error task is generated to alert fulfillers to correct data before processing.

    What This Enables for ServiceNow Customers

    With ERP source validation, customers can confidently manage procurement and sourcing processes across multiple ERP systems without risking data mismatches or routing errors. This capability ensures accurate currency conversions and financial data consistency tied to the correct ERP source, streamlining operations and minimizing integration issues. Customers benefit from improved data integrity, enhanced support for multi-currency transactions, and automated error detection, leading to smoother procurement workflows and more reliable financial reporting.

    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.