{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":49975,"path":"source-to-pay-operations/source-to-pay-integration-framework/erp-integration-framework.md","title":"ERP Integration Framework","bundle":null,"doc_type":null,"release":"australia","body":"\n# ERP Integration Framework\n\nThe 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.\n\n## Key Features\n\n-   User-defined primary data that can be customized to organizational needs.\n-   Mapped to organizational legal entities for clear data governance.\n-   Associated with target ERP systems for bidirectional data flow.\n-   Flexible configuration enabling multiple sources for an organization.\n\n## ERP Sources\n\nAn 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.\n\n## ERP Integration Requirements\n\n-   At least one ERP source must be configured for each legal entity within every target instance.\n-   Each ERP source should be associated with a specific target ERP system.\n-   Organizations can create as many ERP sources as needed to support their structure.\n\nThe integration framework clearly defines the system of record responsibilities:\n\n-   Third-party ERP: System of record for primary data entities\n-   Source-to-Pay: System of record for purchase orders and receipts\n-   Either system: Invoices can be created manually in Source-to-Pay or through external supplier portals\n\n## Integration Architecture\n\nThe 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.\n\nBoth 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.\n\n\\[Omitted image \"s2p-data-architecture.png\"\\] Alt text: Source-to-Pay Operations Integration Architecture\n\n**Required Applications**\n\nThe integration requires the Finance – ERP Integration store application to be installed.\n\n## MID Server Requirement\n\nA 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/mid-server-installation.md) for details.\n\n**Note:** MID Server integration is only required for SOAP-based integrations, not for REST-based integrations.\n\n## User Roles and Permissions\n\nThe ERP Integration Framework supports the following roles and permissions:\n\n<table id=\"table_d5y_ylk_4hc\"><thead><tr><th>\n\nRole name\n\n</th><th>\n\nCapabilities\n\n</th></tr></thead><tbody><tr><td>\n\nAdministrator \\(sn\\_fcms\\_intg.admin\\)\n\n</td><td>\n\n-   Install integration applications\n-   Configure system-wide settings\n-   Manage all aspects of the integration infrastructure\n\n</td></tr><tr><td>\n\nProcurement Specialist \\(sn\\_shop.procurement\\_specialist\\)\n\n</td><td>\n\n-   Define and manage ERP sources\n-   Configure ERP source parameters\n-   Manage integration workflows\n\n</td></tr><tr><td>\n\nFCA Integration user \\(sn\\_fcms\\_intg.integration\\_user\\)\n\n</td><td>\n\n-   Configure ERP source settings including web service authorization\n-   Set up web services for Park and Post, Reverse operations\n-   Manage user and role mappings\n-   Access inbound and outbound staging tables\n-   Configure and execute integration processes\n\n</td></tr></tbody>\n</table>**Additional roles for the FCA Integration user \\(sn\\_fcms\\_intg.integration\\_user\\)**:\n\n-   Import\\_transformer: For data transformation operations\n-   SOAP: For SOAP-based web service integrations\n\n**Granular roles**\n\nUsers 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.\n\n|Property Name|Read role|Write role|\n|-------------|---------|----------|\n|sn\\_fcms\\_intg.status\\_for\\_purchase\\_order|sn\\_shop.shopper, sn\\_shop.procurement\\_common\\_reader, sn\\_fcms\\_intg.admin|sn\\_fcms\\_intg.admin|\n|sn\\_fcms\\_intg.status\\_for\\_invoice\\_creation|sn\\_fcms\\_intg.admin, sn\\_ap\\_apm.accounts\\_payable\\_specialist|sn\\_fcms\\_intg.admin|\n|sn\\_fcms\\_intg.status\\_for\\_goods\\_receipt|sn\\_shop.shopper, sn\\_shop.procurement\\_common\\_reader, sn\\_fcms\\_intg.admin|sn\\_fcms\\_intg.admin|\n\n"}}