ERP Integration Framework
Summarize
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 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
- 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 |