ERP source configuration for Oracle Financial Cloud

  • Release version: Australia
  • 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 Financial Cloud

    This configuration guide helps ServiceNow customers integrate their Source-to-Pay (S2P) instance with Oracle Financial Cloud ERP. It supports seamless inbound and outbound data exchange, enabling automatic posting of purchase orders, receipts, invoices, and downloading of primary ERP data. The ERP source configuration allows mapping service logic specific to Oracle Financial Cloud or other ERP systems and supports multiple ERP instances within the same environment.

    Show full answer Show less

    Key Features

    • Multiple ERP Instances: Each Oracle Financial Cloud instance is configured as a distinct ERP source with a unique connection alias.
    • Service Mapping: Predefined service maps for key entities like Suppliers, Payment Terms, Legal Entities, Currencies, GL Accounts, Purchase Groups, Purchasing Organizations, Cost Centers, and Plant Addresses enable accurate data synchronization from Oracle Financial Cloud.
    • Authentication Profile: Basic authentication profiles are created using Oracle Financial Cloud integration credentials for secure web service communication.
    • Scheduled Data Synchronization: Scheduled jobs can be set up to periodically sync primary data updates from Oracle Financial Cloud, ensuring up-to-date information for posting and other services.
    • User Mapping: The ERP user mapping table links Source-to-Pay users to Oracle Financial Cloud procurement buyers, supporting requisition assignment and integration workflows.

    Prerequisites

    • Assign Importtransformer and SOAP roles to the Integration user in ServiceNow.
    • Obtain ERP integration user credentials and relevant SOAP or REST API details from your Oracle Financial Cloud ERP team.
    • For environments with multiple ERP instances, configure each Oracle Financial Cloud instance separately within Source-to-Pay.

    Configuration Steps

    • Define the ERP source for Oracle Financial Cloud integration in ServiceNow.
    • Create and register a basic authentication profile using Oracle Financial Cloud credentials.
    • Associate the authentication profile with service maps for key ERP entities to enable lookups.
    • Configure subflows within service maps for each entity to retrieve data from Oracle Financial Cloud.
    • Set up scheduled jobs to synchronize primary data updates from Oracle Financial Cloud, especially for cost centers and other entities.
    • Load and maintain user ID mappings between Source-to-Pay and Oracle Financial Cloud procurement buyers.

    Expected Outcomes

    After completing the ERP source configuration, ServiceNow customers can expect reliable and automated integration between Source-to-Pay and Oracle Financial Cloud ERP. This enables efficient data exchange for procurement processes, accurate user-role mappings for requisitions, and timely synchronization of master data, improving overall procurement operations and reducing manual data entry.

    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 Financial Cloud 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 Financial Cloud, follow these steps:
    1. Define the ERP source that you want to integrate with Oracle Financial Cloud integration.
    2. Create a basic authentication profile that can be used for web service integration with Oracle Financial Cloud.
    3. Register the Oracle Financial Cloud 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 Financial Cloud.
    5. Configure service maps for the following entities:
      • Suppliers

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

      • Payment Terms

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

      • Legal Entities

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

      • Currencies

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

      • GL Accounts

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

      • Purchase Groups

        Set up subflows for the source configuration to lookup purchase groups from Oracle Financial Cloud.

      • Purchasing Orgs

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

      • Cost Center

        Set up subflows for the source configuration to lookup purchasing cost center from Oracle Financial Cloud.

      • Plant Addresses

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

      Figure 1. ERP Source Configuration of Oracle Financial Cloud
      ERP Source Configuration of Oracle Financial Cloud
    6. Configure a scheduled job to synchronize primary data updates from Oracle Financial Cloud.
    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 Financial Cloud 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 Financial Cloud.