---
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


---

# ERP Integration Framework

# ERP Integration Framework {#ariaid-title1}

* Release version: Yokohama
* 
* Updated December 8, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Integration Framework

The Source-to-Pay (S2P) ERP Integration Framework facilitates seamless data exchange between ServiceNow and various third-party ERP systems, enabling organizations to manage primary data, transactional data (purchase orders, receipts, invoices), fixed assets, and tax information efficiently across multiple ERP instances.
Show full answer Show less  

## Key Features

* Customizable primary data to fit organizational needs.
* Mapping of data to legal entities for improved governance.
* Bidirectional data flow between ServiceNow and target ERP systems.
* Flexibility to configure multiple sources tailored to organizational structures.

## Integration Requirements

To utilize the ERP Integration Framework, at least one ERP source must be configured for each legal entity within the target instance. Each ERP source should align with a designated target ERP system, and organizations can establish multiple ERP sources as necessary.

## Integration Architecture

The framework supports loading primary data into Source-to-Pay Operations and facilitates the import of inbound transactional data. An abstraction layer between Source-to-Pay applications and backend systems ensures that workflows remain insulated from specific backend integrations.

## Required Applications

The Finance -- ERP Integration store application is essential for the integration. Additionally, a MID Server is required for ERP integrations using SOAP services, and it must be configured to connect with the ERP system server.

## User Roles and Permissions

The ERP Integration Framework includes several user roles with specific capabilities:

* **Administrator:** Manages integration applications and settings.
* **Procurement Specialist:** Defines and manages ERP sources and workflows.
* **FCA Integration User:** Configures ERP source settings and manages integration processes.

Granular roles provide read and write permissions for system properties, ensuring appropriate access control aligned with organizational directives.  
The Source-to-Pay (S2P) ERP Integration Framework enables seamless data exchange between ServiceNow and third-party Enterprise Resource Planning (ERP) systems. This framework supports comprehensive integration of primary data,
transactional data (purchase orders, receipts, invoices), fixed assets, and tax information across multiple ERP instances.

## Key Features {#erp-integration-framework__section_alk_2v3_4hc}

* User-defined primary data that can be customized to organizational needs.
* Mapped to organizational legal entities for clear data governance.
* Associated with target ERP systems for bidirectional data flow.
* Flexible configuration enabling multiple sources for an organization.
{#erp-integration-framework__ul_njn_gv3_4hc}

## ERP Sources {#erp-integration-framework__section_x4j_ykk_4hc}

An ERP Source represents a specific ERP instance from which data is imported and to which data is exported. Organizations typically maintain multiple ERP instances as systems of record, with each ERP source mapped to a legal entity
within the organization.

## ERP Integration Requirements {#erp-integration-framework__section_yfp_zkk_4hc}

* At least one ERP source must be configured for each legal entity within every target instance.
* Each ERP source should be associated with a specific target ERP system.
* Organizations can create as many ERP sources as needed to support their structure.
{#erp-integration-framework__ul_n2d_nkk_4hc}

The integration framework clearly defines the system of record responsibilities:

* Third-party ERP: System of record for primary data entities
* Source-to-Pay: System of record for purchase orders and receipts
* Either system: Invoices can be created manually in Source-to-Pay or through external supplier portals
{#erp-integration-framework__ul_bfc_qkk_4hc}

## Integration Architecture {#erp-integration-framework__section_eh2_kkk_4hc}

The ERP Integration Framework application loads primary data into Source-to-Pay Operations, enabling various ServiceNow workflows. It also imports selected inbound transactional data objects such as purchase order data that are shared
across all Source-to-Pay Operations products.

Both the ERP Integration Framework and Source-to-Pay Integration Framework applications provide an abstraction layer between the Source-to-Pay application and backend systems. This design shields Source-to-Pay workflows and data
models from backend-specific integration components and data structures.  
Figure 1. Source-to-Pay Operations Integration Architecture  
Required Applications

The integration requires the Finance -- ERP Integration store application to be installed.

## MID Server Requirement {#erp-integration-framework__section_ypl_1lk_4hc}

A MID Server is required for ERP integrations using SOAP services. The MID Server must be installed and configured to connect to the ERP system server. See [Installing the MID Server](https://www.servicenow.com/docs/access?context=mid-server-installation&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) for details.  
Note:  
MID Server integration is only required for SOAP-based integrations, not for REST-based integrations.

## User Roles and Permissions {#erp-integration-framework__section_gbs_clk_4hc}

The ERP Integration Framework supports the following roles and permissions:{#erp-integration-framework__table_d5y_ylk_4hc__entry__2}

| Role name | Capabilities |
|-|-|
| Administrator (sn_fcms_intg.admin) | * Install integration applications * Configure system-wide settings * Manage all aspects of the integration infrastructure {#erp-integration-framework__ul_ygs_4mk_4hc} |
| Procurement Specialist (sn_shop.procurement_specialist) | * Define and manage ERP sources * Configure ERP source parameters * Manage integration workflows {#erp-integration-framework__ul_a1q_pmk_4hc} |
| FCA Integration user (sn_fcms_intg.integration_user) | * Configure ERP source settings including web service authorization * Set up web services for Park and Post, Reverse operations * Manage user and role mappings * Access inbound and outbound staging tables * Configure and execute integration processes {#erp-integration-framework__ul_ttn_qmk_4hc} |
[ ]

{#erp-integration-framework__table_d5y_ylk_4hc}  
Additional roles for the FCA Integration user (sn_fcms_intg.integration_user):

* Import_transformer: For data transformation operations
* SOAP: For SOAP-based web service integrations
{#erp-integration-framework__ul_jr3_zmk_4hc}  
Granular roles  
Users assigned the integration admin role (`sn_fcms_intg.admin`) are granted read and write permissions for these system properties. This access aligns with the granular role modifications as per the new directives.{#erp-integration-framework__table_fdq_x1p_4hc__entry__3}

| Property Name | Read role | Write role |
|-|-|-|
| sn_fcms_intg.status_for_purchase_order | sn_shop.shopper, sn_shop.procurement_common_reader, sn_fcms_intg.admin | sn_fcms_intg.admin |
| sn_fcms_intg.status_for_invoice_creation | sn_fcms_intg.admin, sn_ap_apm.accounts_payable_specialist | sn_fcms_intg.admin |
| sn_fcms_intg.status_for_goods_receipt | sn_shop.shopper, sn_shop.procurement_common_reader, sn_fcms_intg.admin | sn_fcms_intg.admin |
[ ]

{#erp-integration-framework__table_fdq_x1p_4hc}