---
sourceDocument: Yokohama Finance and Supply Chain
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/source-to-pay-operations

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Finance and Supply Chain

ft:clusterId :

    - stpop

bundleId :

    - stpop

workflow :

    - Employee


---

# Scheduled jobs to look up primary data in Oracle EBS

# Scheduled jobs to look up primary data in Oracle EBS {#ariaid-title1}

* Release version: Yokohama
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

You can schedule on-demand jobs to be run at specific intervals of time to fetch primary data from different Oracle EBS ERP sources into ServiceNow.

Before you start the Oracle EBS ERP integration, you must configure the integration services record for target ERP source using the `sn_fcms_intg_service` table. The `sn_fcms_intg_service` table is a
mapping table between sub flows and target ERP source. For more information on creating an integration service record, see [Create Integration Service record](https://servicenow-prod.fluidtopics.net/gcMl94qzHYy5r1Yp8QPjXQ "Create Integration Service records for entities using the sn_fcms_intg_service table.").

Scheduled jobs are configured for entities using scripts. Example: Fetch cost center from ERP systems. For more information on configuring scheduled jobs using scripts, see [Automatically run a script of your choosing](https://www.servicenow.com/docs/access?context=t_ScheduleAScriptExecution&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US). The script invokes a subflow, which is associated with an entity as shown in the following figure. The subflow queries the active entities or ERP source configuration (optional)
listed in the integration service table.
* **[Run scheduled jobs in Oracle EBS](https://servicenow-prod.fluidtopics.net/Nz6k2pk93RLEOwAFWcPPQQ)**   
  Run adhoc scheduled jobs to look up entity primary data from the target Oracle EBS ERP source.

**Related concepts**   

* [ERP source configuration for Oracle EBS](https://servicenow-prod.fluidtopics.net/RupRAGsUYcIJcisquQNang "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.")
* [Look up primary data in Oracle EBS](https://servicenow-prod.fluidtopics.net/zmv~eExxeDyl5srKvyzl0A "You can run a job to look up primary data from different ERP sources into ServiceNow.")  
**Related tasks**   

* [Define ERP source configuration for Oracle EBS](https://servicenow-prod.fluidtopics.net/kZomh47YksEZ8QZIr8U7uA "ERP source configuration determines the ERP source to which your ERP system connects. Map the integration payload with the Oracle EBS tables.")
* [Configure integration services for Oracle EBS](https://servicenow-prod.fluidtopics.net/UCDjuE3nZRwqMtATr0QHVA "For configuring integration services, provide the connection end point and the Oracle EBS ERP credentials that you set up for your authentication profile. Also, create a separate web service record for each service request that you want to customize.")
* [Load data to ERP user-mapping table for Oracle EBS](https://servicenow-prod.fluidtopics.net/aBWjnG3DFwosAu7mazeWXQ "Set up Oracle EBS and ERP User ID mapping 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.")