ERP Integration Framework
Summarize
Summary of ERP Integration Framework
The Source-to-Pay (S2P) ERP Integration Framework enables seamless and bidirectional data exchange between ServiceNow and multiple third-party Enterprise Resource Planning (ERP) systems. It supports integration of primary data, transactional data (such as purchase orders, receipts, and invoices), fixed assets, and tax information across various ERP instances, providing a unified approach to managing procurement and financial workflows.
Show less
Key Features
- User-defined primary data: Customizable to meet organizational needs and mapped to legal entities for data governance.
- ERP Sources: Represents specific ERP instances mapped to legal entities, allowing multiple ERP sources per organization.
- Clear system of record roles: Third-party ERPs serve as the system of record for primary data, while Source-to-Pay manages purchase orders and receipts. Invoices can be created either manually in Source-to-Pay or via external portals.
- Integration abstraction layer: Decouples Source-to-Pay workflows from backend ERP-specific data structures, enhancing flexibility and maintainability.
Integration Architecture and Requirements
- The framework loads primary data into Source-to-Pay Operations, enabling ServiceNow workflows and importing inbound transactional data.
- Requires installation of the Finance – ERP Integration store application.
- MID Server is necessary for SOAP-based ERP integrations to connect securely with ERP servers; REST-based integrations do not require a MID Server.
- At least one ERP source must be configured per legal entity in each target instance, and multiple ERP sources can be created as needed.
User Roles and Permissions
- Administrator (snfcmsintg.admin): Full control over installation, configuration, and integration management.
- Procurement Specialist (snshop.procurementspecialist): Manages ERP sources and integration workflows.
- FCA Integration User (snfcmsintg.integrationuser): Handles ERP source settings, web service authorization, user/role mappings, and integration process execution.
- Additional granular roles for specialized operations like data transformation and SOAP web service integrations ensure secure and role-appropriate access.
This framework empowers ServiceNow customers to efficiently integrate their procurement processes with multiple ERP systems, ensuring consistent data management, clear governance, and streamlined operational workflows.
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
- 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 Sources
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
- 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.
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
Integration Architecture
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.
The integration requires the Finance – ERP Integration store application to be installed.
MID Server Requirement
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 for details.
User Roles and Permissions
| Role name | Capabilities |
|---|---|
| Administrator (sn_fcms_intg.admin) |
|
| Procurement Specialist (sn_shop.procurement_specialist) |
|
| FCA Integration user (sn_fcms_intg.integration_user) |
|
- Import_transformer: For data transformation operations
- SOAP: For SOAP-based web service integrations
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.| 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 |