ERP Source Configuration for Oracle EBS

  • Release version: Xanadu
  • Updated March 9, 2025
  • 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 configuration enables ServiceNow Source-to-Pay (S2P) instances to integrate seamlessly with Oracle EBS ERP systems for inbound and outbound data exchange. It automates posting of purchase orders, receipts, and invoices, as well as downloading primary data from Oracle EBS. The setup supports multiple ERP instances by managing distinct ERP source entries and corresponding service mappings, ensuring accurate identification and connectivity for each integrated Oracle instance.

    Show full answer Show less

    Key Features

    • Multiple ERP Instances: Allows configuration of multiple Oracle EBS instances, each with a unique source and connection alias.
    • Service Mappings: Defines and customizes service maps to align S2P data flows with Oracle EBS entities such as cost centers, product models, payment terms, purchasing organizations, suppliers, and invoices.
    • Authentication Profiles: Supports creation of basic authentication profiles using Oracle EBS integration credentials for secure web service communication.
    • Subflows for Data Lookup: Configurable subflows for retrieving master data (e.g., GL accounts, currencies, departments, legal entities) from Oracle EBS to ensure data consistency.
    • Scheduled Synchronization: Enables scheduled jobs to periodically synchronize primary data updates such as cost centers, ensuring up-to-date information for posting services.
    • User Mapping: Maintains mappings between S2P users and Oracle EBS procurement buyers to support requisition assignment and transaction processing.

    Prerequisites

    • Assign Integration user roles: Importtransformer and SOAP.
    • Obtain ERP integration user credentials and SOAP/REST API details from the ERP team.
    • If integrating multiple ERP instances, configure each instance separately within S2P.

    Configuration Steps

    • Define the ERP source within S2P to identify the Oracle EBS instance.
    • Create and register basic authentication profiles for Oracle EBS web service integration.
    • Configure service maps and subflows for key Oracle EBS entities (cost centers, product models, payment terms, purchasing orgs, departments, GL accounts, currencies, FX rates, invoice payments, suppliers, plant addresses, legal entities, and invoices).
    • Set up scheduled jobs to synchronize primary data updates, particularly for cost centers.
    • Load and maintain the ERP user mapping table linking S2P users with Oracle EBS procurement buyers.

    Expected Outcomes

    By completing this configuration, ServiceNow customers can expect reliable, automated integration between their Source-to-Pay system and Oracle EBS ERP. This ensures timely and accurate exchange of procurement and financial data, consistent master data synchronization, and efficient requisition assignment aligned with ERP user roles. The integration supports multiple Oracle EBS instances, enhancing flexibility for organizations with complex ERP landscapes.

    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 are using for the integration.
    Note:
    If the application needs to 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 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.
    8. Load data to 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.