{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":37875,"path":"order-management/sales-and-services-api-core.md","title":"Sales and Service API Core","bundle":null,"doc_type":null,"release":"australia","body":"\n# Sales and Service API Core\n\nEnables seamless tracking and management of Sales Customer Relationship Management workflows through structured inbound and outbound request handling, configurable flow processing, and integration with external systems.\n\n## Overview of Sales and Service API Core\n\nThe Sales and Service API Core \\(com.sn\\_tmt\\_core\\) plugin has three key components.\n\n<table id=\"table_t1y_j4g_xgc\"><thead><tr><th>\n\nTable\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\n[Inbound Request](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/som_request_tracker.md) \\(sn\\_tmt\\_core\\_inbound\\_queue\\)\n\n</td><td>\n\nTracks the status of both synchronous and asynchronous flows. It enables agents to monitor the progress of requests and also enables sequential processing of dependent records to maintain data accuracy and consistency.\n\n It captures detailed status information for each request. For example, when an order is created from a quote, it logs a confirmation message with the order header number.\n\n It also supports archival and cleanup policies enabling organizations to cleanup records by applying different durations for successful and failed requests to optimize data management.\n\n</td></tr><tr><td>\n\n[Inbound Request Configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/inbound-request-configuration-table.md) \\(sn\\_tmt\\_core\\_inbound\\_queue\\_config\\)\n\n</td><td>\n\nDefines how each flow is processed and tracked.\n\n It’s a metadata table that is referenced by the Request Configuration field in the Inbound Request Table.\n\n It enables administrators to:\n\n-   Configure synchronous vs asynchronous processing.\n-   Adapt the Request Tracker across CRM flows.\n-   Set notification types \\(default, custom, or none\\).\n\n</td></tr><tr><td>\n\n[Outbound Request](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/outbound-request-configuration-table.md) \\(sn\\_tmt\\_core\\_outbound\\_request\\)\n\n</td><td>\n\nFacilitates outbound interactions with external Service Order Management \\(SOM\\).\n\n It supports end-to-end order fulfillment via bi-directional REST API integration and requires specific roles.\n\n</td></tr></tbody>\n</table>|Role|Access|\n|----|------|\n|sn\\_tmt\\_core.admin|Create, read, update, delete, report\\_view, and report\\_on|\n|sn\\_tmt\\_core.viewer|report\\_view, report\\_on, and read|\n\n**Related topics**  \n\n\n[Using lead-to-cash foundation applications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/using-lead-cash-foundation.md)\n\n[Lead-to-cash foundation reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/order-management/reference-lead-cash-foundation.md)\n\n"}}