--- sourceDocument: Xanadu Finance and Supply Chain sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/source-to-pay-operations Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu Finance and Supply Chain ft:clusterId : - stpop bundleId : - stpop workflow : - Creator --- # Integration settings on Source-to-Pay side # Integration settings on Source-to-Pay side {#ariaid-title1} * Release version: Xanadu * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read 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. Before you start the integration configuration, you must complete the following tasks. * Add the following roles to the Integration user: * Import_transformer * Soap {#integration-settings-psm-side__ul_fn3_g2p_j3b} * Get the following information from the ERP team: * ERP integration user credentials. * SOAP or REST API details based on your ERP system and the type of web services you are using for the integration. {#integration-settings-psm-side__ul_f15_r2p_j3b} {#integration-settings-psm-side__ul_ift_d2p_j3b} Note: If the application needs to support multiple ERP instances, configure S2P to integrate with each ERP instance separately. 1. Define an ERP source.Define the ERP source that you want to integrate with Procurement Service Management. This information is required for any primary data. For more information, see [ERP source](https://servicenow-prod.fluidtopics.net/zrZNGmgEXZsYYQ7i01auEg "An ERP Source [sn_fin_erp_source] table is available in Source-to-Pay (S2P) as part of the Finance Common Architecture application.") and [Primary data integration](https://servicenow-prod.fluidtopics.net/gjhO3WM82xI6jmikyuaS~Q "All primary data are synchronized based on the configurable scheduled job Fetch Spend Primary Data. For supplier primary data, if an update is made in the ERP, it is synchronized with Source-to-Pay (S2P) even if the scheduled job has not been triggered."). 2. Set up the authentication profile.Create a basic authentication profile that can be used for web service integration with ERP. Register the ERP integration username and password to create the authentication profile and associate it to service maps. For more information, see [Set up the authentication profile](https://servicenow-prod.fluidtopics.net/y5OF3CadMm84W4w5s_5kog "Create a basic authentication profile that can be used for web service integration with ERP. Register the ERP integration user name and password to create the authentication profile and associate it to service maps."). 3. Define source configuration for ERP.ERP source configuration determines the ERP source to which your ERP system connects. For more information, see [ERP source configuration](https://servicenow-prod.fluidtopics.net/mC8wp_7~CGSLqbgOH45uFg "ERP source configuration allows specific customer logic to be implemented to populate values specific to third-party ERP systems. It contains all the service mappings defined between Source-to-Pay (S2P) and the third-party ERP system.") and [Define ERP source configuration for Source-to-Pay](https://servicenow-prod.fluidtopics.net/RiuqKyQm7C~ZDamgJHh4fQ "ERP source configuration determines the ERP source to which your ERP system connects. Map the integration payload with the Source-to-Pay (S2P) tables."). 4. Configure service maps for the following entities: * Post purchase order.Set up web services for the source configuration to post purchase orders to ERP. * Post receipt.Set up web services for the source configuration to post receipts to ERP. * Post invoice.Set up web services for the source configuration to post invoices to ERP. * Fetch supplier.Set up web services for the source configuration to fetch supplier updates from ERP. * Fetch cost center.Set up web services for the source configuration to fetch cost center updates from ERP. * Fetch purchasing entity.Set up web services for the source configuration to fetch purchasing entity updates from ERP. * Fetch general ledger account.Set up web services for the source configuration to fetch general ledger account updates from ERP. * Fetch asset category.Set up web services for the source configuration to fetch asset category updates from ERP. * Fetch material group.Set up web services for the source configuration to fetch material group updates from ERP. {#integration-settings-psm-side__ul_n4b_fkh_3lb} Note: For configuring each of these service maps, provide the connection end point and the 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. For more information, see [Configure service maps for Source-to-Pay](https://servicenow-prod.fluidtopics.net/v9aEKFBhBihTOy5hTCOa_w "For configuring service maps, provide the connection end point and the 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."). 5. Configure scheduled job to synchronize primary data updates from ERP.Set up the interval in the Fetch Spend Primary Data scheduled job to periodically synchronize primary data updates from the ERP, for posting services to work. 6. Load data to ERP user mapping table.Set up S2P 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. For more information, see [Load data to ERP user mapping table for Source-to-Pay](https://servicenow-prod.fluidtopics.net/6XPN0UpRJMyCsQ3TsH2Fpw "Set up Source-to-Pay (S2P) 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."). 7. Map the following entities: * Purchasing entity.Map legal entity to the downloaded purchasing entity in the purchasing entity table. * Asset category.Map capitalization policy to the downloaded asset category in the asset category mapping table. * Material group.Map model category to the downloaded material group in the material group mapping table. * Delivery address.Map location reference in the delivery location table to ERP address code in the address mapping table. * ERP plant.Map ERP plant id to the corresponding ERP location in the address mapping table. Use the ERP address identifier 1 field for this mapping. {#integration-settings-psm-side__ul_k1r_mlh_3lb} {#integration-settings-psm-side__ol_jnb_sjh_3lb}