ERP source configuration for Oracle EBS

  • Release version: Zurich
  • Updated March 12, 2026
  • 3 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 configuration for Oracle EBS

    This guide explains how to configure Source-to-Pay (S2P) integration with Oracle E-Business Suite (EBS) ERP systems. The configuration supports automatic posting and downloading of purchase orders, receipts, invoices, and primary data between S2P and Oracle EBS. It enables defining multiple ERP sources and managing service mappings specific to each ERP instance, allowing organizations to integrate multiple Oracle EBS systems distinctly.

    Show full answer Show less

    Prerequisites

    • Assign Importtransformer and SOAP roles to the Integration user.
    • Obtain ERP integration user credentials and SOAP or REST API details from the ERP team, depending on the web services used.
    • Configure separate integrations in S2P for each Oracle EBS instance if multiple ERP instances exist.

    Key Configuration Steps

    • Define the ERP source in S2P that corresponds to the Oracle EBS instance.
    • Create and register a basic authentication profile using Oracle EBS integration credentials to enable web service connectivity.
    • Configure the source settings to identify the ERP system connection accurately.
    • Set up service maps with subflows for various Oracle EBS entities, including:
      • Cost Centers
      • Product Models
      • Payment Terms
      • Purchasing Organizations
      • Departments
      • GL Accounts
      • Currencies and FX Rates
      • Invoice Payment Details
      • Suppliers
      • Plant Addresses
      • Legal Entities
      • Invoices
    • Configure scheduled jobs to periodically synchronize primary data such as Cost Centers and other entities from Oracle EBS to ensure posting services function correctly.
    • Load and maintain the ERP user-mapping table (snfcmsintgerpusermap) linking S2P users to their corresponding ERP user IDs for procurement buyer roles, supporting requisition assignment rules.

    Benefits for ServiceNow Customers

    By setting up this ERP source configuration, ServiceNow customers can:

    • Seamlessly synchronize key procurement data between Source-to-Pay and Oracle EBS.
    • Support multiple Oracle EBS instances with unique authentication and service mappings.
    • Automate data lookups and updates for critical procurement entities, reducing manual effort and errors.
    • Ensure accurate user role mapping for procurement workflows across integrated systems.

    Next Steps

    • Define ERP source configurations and authentication profiles specific to your Oracle EBS instances.
    • Set up and customize service maps and subflows according to your organizational data structure.
    • Schedule synchronization jobs to keep primary data current.
    • Load and maintain user mappings to enable proper requisition routing.

    Configure your Source-to-Pay (S2P) instance to support inbound and outbound integration with your ERP system. This integration configuration enables you to automatically post purchase order, receipt, invoice, and download primary data from the ERP.

    ERP source configuration enables the implementation of specific logic to populate values pertinent to third-party ERP systems. It includes all service mappings defined between Source-to-Pay (S2P) and the third-party ERP system. In cases where multiple ERP sources exist, they’re stored as distinct ERP source entries with their corresponding service mappings.

    To meet specific requirements, you can modify the service-mapping logic by updating the relevant service element map entry within the service map record. For organizations using multiple ERP systems, an ERP Source field has been incorporated into the tables to ensure accurate identification of the respective integrated ERP system.

    The ERP source configuration for Oracle EBS enables customers to establish multiple Oracle instances. Each instance is identified by a distinct source, and the connection alias for each instance must be unique.

    Prerequisites

    Before you start the integration configuration, you must complete the following tasks.
    • Add the following roles to the Integration user:
      • Import_transformer
      • SOAP
    • Get the following details from the ERP team:
      • ERP integration user credentials.
      • SOAP or REST API details based on your ERP system and the type of web services you’re using for the integration.
    Note:
    If the application must support multiple ERP instances, configure Source-to-Pay to integrate with each ERP instance separately.

    ERP Source Configuration

    To perform the ERP Source configuration for Oracle EBS, follow these steps:
    1. Define the ERP source that you want to integrate with Oracle EBS integration.
    2. Create a basic authentication profile that can be used for web service integration with Oracle EBS.
    3. Register the Oracle EBS integration username and password to create the authentication profile and associate it to service maps.
    4. Define source configuration for ERP source. The ERP source configuration determines the ERP source to which your ERP system connects. For more information, see Define ERP source configuration for Oracle EBS.
    5. Configure service maps for the following entities:
      • Cost Centers

        Set up subflows for the source configuration to lookup cost centers from Oracle EBS.

      • Product Models

        Set up subflows for the source configuration to lookup product models from Oracle EBS.

      • Payment Terms

        Set up subflows for the source configuration to lookup payment terms from Oracle EBS.

      • Purchasing Orgs

        Set up subflows for the source configuration to lookup purchasing orgs from Oracle EBS.

      • Departments

        Set up subflows for the source configuration to lookup departments from Oracle EBS.

      • GL Accounts

        Set up subflows for the source configuration to lookup GL accounts from Oracle EBS.

      • Currencies

        Set up subflows for the source configuration to lookup currencies from Oracle EBS.

      • FX Currency Rates

        Set up subflows for the source configuration to lookup FX rates from Oracle EBS.

      • Invoice Payment Details

        Set up subflows for the source configuration to lookup invoice payment details from Oracle EBS.

      • Suppliers

        Set up subflows for the source configuration to lookup suppliers from Oracle EBS.

      • Plant Addresses

        Set up subflows for the source configuration to lookup plant addresses from Oracle EBS.

      • Legal Entities

        Set up subflows for the source configuration to lookup legal entities or company code details from Oracle EBS.

      • Invoices

        Set up subflows for the source configuration to lookup invoices from Oracle EBS.

      Figure 1. ERP Source Configuration of Oracle EBS
      ERP Source Configuration of Oracle EBS
    6. Configure a scheduled job to synchronize primary data updates from Oracle EBS.
    7. Set up the interval in the lookup Cost Center scheduled job to periodically synchronize primary data updates from the ERP, for posting services to work.
      Note:
      Similarly, you can configure schedule jobs for the other integrations services.
    8. Load data to the Oracle EBS user-mapping table.
    9. Set up Source-to-Pay and ERP User ID mapping (sn_fcms_intg_erp_user_map) for the integration to work.

      The mapping is maintained for all active users who have the procurement buyer role in ERP. These users should be used in the requisition assignment rule.

      You have configured the ERP source for Oracle EBS.