{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":50361,"path":"source-to-pay-operations/sourcing-and-procurement-operations/installed-with-FSC.md","title":"Components installed with Sourcing and Procurement Operations","bundle":null,"doc_type":null,"release":"australia","body":"\n# Components installed with Sourcing and Procurement Operations\n\nSeveral types of components are installed with the activation of Sourcing and Procurement Operations, including tables, user roles, and scheduled jobs.\n\nDemo data is available for this feature.\n\n## Roles installed\n\n<table id=\"table_y5t_xj1_2lb\"><thead><tr><th>\n\nRole title \\[name\\]\n\n</th><th>\n\nDescription\n\n</th><th>\n\nContains roles\n\n</th></tr></thead><tbody><tr><td>\n\nShopping Hub Administrator\n\n \\[sn\\_shop.shopping\\_hub\\_admin\\]\n\n</td><td>\n\nAccess to all modules of the Source-to-Pay Common Architecture application.\n\n</td><td>\n\n-   decision\\_table\\_admin\n-   sn\\_fin.procurement\\_user\n-   model\\_manager\n-   category\\_manager\n\n</td></tr><tr><td>\n\nShopper\n\n \\[sn\\_shop.shopper\\]\n\n</td><td>\n\nAccess to the Shopping Hub portal to make requests and purchases.\n\n</td><td>\n\nNone\n\n</td></tr><tr><td>\n\nProcurement Administrator\n\n \\[sn\\_shop.procurement\\_administrator\\]\n\n</td><td>\n\nAccess to the primary data and administration sections of the Purchase Automation module.\n\n</td><td>\n\n-   sn\\_fin.procurement\\_primary\\_data\\_admin\n-   sn\\_shop.procurement\\_specialist\n\n</td></tr><tr><td>\n\nProcurement Specialist\n\n \\[sn\\_shop.procurement\\_specialist\\]\n\n</td><td>\n\nAccess to all the data of the Sourcing and Purchasing Automation module, except the primary data.\n\n</td><td>\n\n-   sn\\_fin.procurement\\_user\n-   contract\\_manager\n\n</td></tr><tr><td>\n\nAccounts Payable Viewer\n\n \\[sn\\_shop.accounts\\_payable\\_viewer\\]\n\n</td><td>\n\nRead access to purchase orders, invoices, and other task-related objects that arise from purchase order creation.\n\n</td><td>\n\nNone\n\n</td></tr><tr><td>\n\nPurchasing Task Owner\n\n \\[sn\\_shop.purchasing\\_task\\_owner\\]\n\n</td><td>\n\nAccess to all purchase orders, requisitions, negotiations, sourcing requests, and purchasing tasks.\n\n</td><td>\n\nNone\n\n</td></tr><tr><td>\n\nAcknowledgment Task Owner\n\n \\[sn\\_shop.acknowledgment\\_task\\_owner\\]\n\n</td><td>\n\nAccess to all purchase orders and purchase requisitions. Read-only access to the main objects, but can update assigned tasks.\n\n</td><td>\n\nNone\n\n</td></tr><tr><td>\n\nProcurement Common Administrator\n\n \\[sn\\_shop.procurement\\_common\\_admin\\]\n\n</td><td>\n\nAccess to all tables, including deletion of records, in the Source-to-Pay Common Architecture application.\n\n</td><td>\n\nsn\\_shop.procurement\\_common\\_user\n\n</td></tr><tr><td>\n\nProcurement Common Reader\n\n \\[sn\\_shop.procurement\\_common\\_reader\\]\n\n</td><td>\n\nRead access to all tables available in the Source-to-Pay Common Architecture application.\n\n</td><td>\n\nsn\\_fin.procurement\\_user\n\n</td></tr><tr><td>\n\nProcurement Common User\n\n \\[sn\\_shop.procurement\\_common\\_user\\]\n\n</td><td>\n\nAccess to perform, create, and update operations on all tables in the Source-to-Pay Common Architecture application.\n\n</td><td>\n\nsn\\_shop.procurement\\_common\\_reader\n\n</td></tr><tr><td>\n\nsn\\_spend\\_mgmt.category\\_manager\\_admin\n\n</td><td>\n\nCan import the category taxonomy, update the Spend Category and Spend Category Stage tables and update the Spend category to Product category mappings.\n\n</td><td>\n\nNone\n\n</td></tr><tr><td>\n\nsn\\_spend\\_mgmt.sourcing\\_category\\_manager\n\n</td><td>\n\nCan view and access the Category management tab and the Savings dashboard in Spend and Savings Management.\n\n</td><td>\n\nsn\\_shop.procurement\\_specialist\n\n</td></tr><tr><td>\n\nsn\\_spend\\_pipeline.pipeline\\_management\\_admin\n\n</td><td>\n\nCan configure the Pipeline project creation rule decision table to automate the creation of pipeline projects.\n\n</td><td>\n\ndecision\\_table\\_admin\n\n</td></tr><tr><td>\n\nsn\\_spend\\_pipeline.sourcing\\_pipeline\\_user\n\n</td><td>\n\nCan view and access the Pipeline management tab.\n\n</td><td>\n\nNone\n\n</td></tr></tbody>\n</table>**Note:** An application-specific admin role enables a user to manage application-level configurations, roles, and access controls. Your system-level admin on the production instance must grant the application-specific admin role to the appropriate users, and then remove the application-specific admin role from all users with the system-level admin role to help prevent system-level admins from viewing sensitive application data via forms, lists, and the UI. For more information, see [Application administration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/application-development/application-administration.md).\n\n## Scheduled jobs installed\n\n|Scheduled job|Description|\n|-------------|-----------|\n|\\[PSM\\] Approval Due Date Breached|Creates a breached approvals review task if a due date for an approval is breached.|\n|\\[PSM\\] Clear Recently Viewed Data|Clears the recently viewed data in ShoppingHub. This data comprises entries that were created more than 90 days ago by the logged-in user.|\n|\\[PSM\\] Create Receiving Task|Creates receipt tasks against the purchase order, grouped by calendar month and recipient, on the first of every month.|\n|\\[PSM\\] Create Service Acknowledgment Task|Creates service acknowledgment tasks on a monthly basis. This job automatically picks all purchase order lines that have started and are yet to reach their end dates, and have some remaining amount or percentage or quantity to be delivered.|\n|\\[PSM\\] Execute Credit Allocation Rules|Runs the credit allocation rules that are set up. Employee credit records are created as per this rule.|\n|\\[PSM\\] Execute Shopping Controls|Runs the shopping controls that are set up. User control records are created as per the shopping controls, and the respective supplier products are updated as well.|\n|\\[PSM\\] Monitor Milestone Tasks|Fetches any active milestone whose completion date is today and updates the state of the milestone to Confirmation Required.|\n|\\[PSM\\] Populate Spend Task – Due Date Bucket|Calculates the due date bucket of purchasing tasks to determine the category to which they belong to. The categories are Others, Due within 7 Days, and Overdue.|\n|\\[PSM\\] Purchasing Data Aggregation|Populates the following aggregate tables: Product Purchases by Job Code, Supplier Use by Shopper, and Supplier Use by Department.|\n|\\[PSM\\] Retiring Supplier Products|Updates the Published flag on the supplier product to False when the current date is the same as the sales end date on the supplier product.|\n|\\[PSM\\] Revoke Expired Credits|Sets the credit status to Credit Expired after the expiration date on the credit is reached.|\n\n## Tables installed\n\n**Note:** The following tables are commonly available, within the Source-to-Pay Common Architecture application.\n\n<table id=\"table_sgq_s5k_flb\"><thead><tr><th>\n\nTable\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nAttribute\n\n \\[sn\\_shop\\_attribute\\]\n\n</td><td>\n\nStores specific attribute types and the values that are associated with a product model. For example, a laptop can have an attribute for the type of memory used, which can be SSD or Hard disk.\n\n</td></tr><tr><td>\n\nAttribute Set\n\n \\[sn\\_shop\\_attribute\\_set\\]\n\n</td><td>\n\nStores a group of attribute types that can later be associated with a supplier product. For example, Memory, Graphic card, and CPU can be an attribute set that can be associated with a product group.\n\n</td></tr><tr><td>\n\nAttribute Type\n\n \\[sn\\_shop\\_attribute\\_type\\]\n\n</td><td>\n\nStores the various types of attributes that are used when creating a product attribute.\n\n</td></tr><tr><td>\n\nDelivery Location\n\n \\[sn\\_shop\\_delivery\\_location\\]\n\n</td><td>\n\nStores the delivery location for a given shop line or cart line.\n\n</td></tr><tr><td>\n\nERP Address Mapping\n\n \\[sn\\_shop\\_erp\\_address\\_map\\]\n\n</td><td>\n\nStores the mapping between the ERP address and the location.\n\n</td></tr><tr><td>\n\nERP Asset Category Mapping\n\n \\[sn\\_shop\\_erp\\_asset\\_category\\_map\\]\n\n</td><td>\n\nStores the mapping between the ERP source and the capitalization policy.\n\n</td></tr><tr><td>\n\nERP Material Group Mapping\n\n \\[sn\\_shop\\_erp\\_material\\_group\\_map\\]\n\n</td><td>\n\nStores the mapping between the ERP source, model category, and material group.\n\n</td></tr><tr><td>\n\nIntegration Error\n\n \\[sn\\_shop\\_erp\\_error\\_task\\]\n\n</td><td>\n\nStores integration errors that might occur when communicating or processing a request with ERP.\n\n</td></tr><tr><td>\n\nInvoice\n\n \\[sn\\_shop\\_invoice\\]\n\n</td><td>\n\nStores the invoice that is associated with a purchase order.\n\n</td></tr><tr><td>\n\nInvoice Line\n\n \\[sn\\_shop\\_invoice\\_line\\]\n\n</td><td>\n\nStores the invoice lines for each corresponding purchase order line.\n\n</td></tr><tr><td>\n\nJob Code\n\n \\[sn\\_shop\\_job\\_code\\]\n\n</td><td>\n\nStores the job codes that are associated with business owners that primarily drive the approval hierarchy.\n\n</td></tr><tr><td>\n\nMilestone\n\n \\[sn\\_shop\\_milestone\\]\n\n</td><td>\n\nExtends the Acknowledgment Task table and stores the acknowledgment of services received.\n\n</td></tr><tr><td>\n\nOffice Location\n\n \\[sn\\_shop\\_office\\_location\\]\n\n</td><td>\n\nStores delivery locations marked as office.\n\n</td></tr><tr><td>\n\nOrder Line Template\n\n \\[sn\\_shop\\_order\\_line\\]\n\n</td><td>\n\nExtends the Shop Line table and stores the purchase order line for any purchase order.\n\n</td></tr><tr><td>\n\nOrder Template\n\n \\[sn\\_shop\\_order\\]\n\n</td><td>\n\nStores all purchase orders. This is a base table.\n\n</td></tr><tr><td>\n\nOrder to Contract Relationships\n\n \\[sn\\_shop\\_m2m\\_order\\_contract\\]\n\n</td><td>\n\nStores the mapping between the purchase order and contract.\n\n</td></tr><tr><td>\n\nPayment Terms\n\n \\[sn\\_shop\\_payment\\_term\\]\n\n</td><td>\n\nStores the term in which a payment would be made. For example, a term could be seven days after the invoice date.\n\n</td></tr><tr><td>\n\nPrice Break\n\n \\[sn\\_shop\\_price\\_break\\]\n\n</td><td>\n\nStores the price divided based on the number of quantities purchased for a given supplier product contract.\n\n</td></tr><tr><td>\n\nPricing\n\n \\[sn\\_shop\\_m2m\\_product\\_contract\\]\n\n</td><td>\n\nStores the mapping of a supplier product and its price that is based on the associated contract.\n\n</td></tr><tr><td>\n\nProduct Group\n\n \\[sn\\_shop\\_product\\_group\\]\n\n</td><td>\n\nStores the name that is associated with an attribute set that is then referenced by the supplier product and product model.\n\n</td></tr><tr><td>\n\nProduct Visuals\n\n \\[sn\\_shop\\_supplier\\_product\\_artifact\\]\n\n</td><td>\n\nStores the artifacts that are used to display product appearances on the user interface.\n\n</td></tr><tr><td>\n\nPurchase Order\n\n \\[sn\\_shop\\_purchase\\_order\\]\n\n</td><td>\n\nExtends the Order Template table and stores the purchase order for a given purchase.\n\n</td></tr><tr><td>\n\nPurchase Order Line\n\n \\[sn\\_shop\\_purchase\\_order\\_line\\]\n\n</td><td>\n\nExtends the Order Line Template table and stores the purchase order line for a purchase.\n\n</td></tr><tr><td>\n\nReceipt\n\n \\[sn\\_shop\\_receipt\\]\n\n</td><td>\n\nStores the receipt of a supplier product received as part of a purchase order line.\n\n</td></tr><tr><td>\n\nShipment Details\n\n \\[sn\\_shop\\_shipment\\_details\\]\n\n</td><td>\n\nStores the shipment details that are associated with a purchase order line.\n\n</td></tr><tr><td>\n\nShipment Product\n\n \\[sn\\_shop\\_shipment\\_product\\]\n\n</td><td>\n\nStores the shipment product details that are associated with a purchase order line.\n\n</td></tr><tr><td>\n\nShipping Method\n\n \\[sn\\_shop\\_shipping\\_method\\]\n\n</td><td>\n\nStores the shipping method details that are associated with a purchase order line.\n\n</td></tr></tbody>\n</table>**Note:** The following tables are installed as part of the Sourcing and Purchasing Automation application.\n\n<table id=\"table_yct_jwt_d5b\"><thead><tr><th>\n\nTable\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nAcknowledgment Task\n\n \\[sn\\_shop\\_acknowledgment\\_task\\]\n\n</td><td>\n\nStores acknowledgments such as the milestone and receipt task. This is a parent table within the Common Service Delivery \\(SDC\\) application.\n\n</td></tr><tr><td>\n\nApproval Plan\n\n \\[sn\\_shop\\_approval\\_plan\\]\n\n</td><td>\n\nStores the approval plan details for a purchase requisition such as the approval routing method and approval decision method.\n\n</td></tr><tr><td>\n\nApproval Plan Detail\n\n \\[sn\\_shop\\_approval\\_plan\\_detail\\]\n\n</td><td>\n\nStores an instance of the approval record for a purchase line that is created based on the approval plan.\n\n</td></tr><tr><td>\n\nApproval Rule\n\n \\[sn\\_shop\\_approval\\_rule\\]\n\n</td><td>\n\nStores the rule that triggers the creation of an approval record. It uses a condition builder to build the trigger condition for approvals.\n\n</td></tr><tr><td>\n\nCapitalization Policy\n\n \\[sn\\_shop\\_capitalization\\_policy\\]\n\n</td><td>\n\nStores the condition based on which an asset is capitalized, and a fixed asset record is created.\n\n</td></tr><tr><td>\n\nCart Line\n\n \\[sn\\_shop\\_cart\\_line\\]\n\n</td><td>\n\nStores the details of a purchase line that is added to a cart. It has various details such as the supplier product selected, checkout type, business owner, delivery location, and so on.\n\n</td></tr><tr><td>\n\nContract Task\n\n \\[sn\\_shop\\_contract\\_task\\]\n\n</td><td>\n\nExtends the Purchasing Task table and stores instances of various types of contract tasks that are associated with a purchase line.\n\n</td></tr><tr><td>\n\nPurchase Cost Allocation\n\n \\[sn\\_shop\\_cost\\_allocation\\]\n\n</td><td>\n\nStores the type of cost allocation, associated cost center, and the amount that is allocated for a shopper that can be used to buy a supplier product.\n\n</td></tr><tr><td>\n\nCredit Allocation Rules\n\n \\[sn\\_shop\\_credit\\_allocation\\_rules\\]\n\n</td><td>\n\nStores the credit allocation rules that are based on how a credit is allocated to an individual shopper. The allocation can be based on the inventory asset or user condition.\n\n</td></tr><tr><td>\n\nDelivery Address Task\n\n \\[sn\\_shop\\_delivery\\_address\\_task\\]\n\n</td><td>\n\nExtends the Purchasing Task table and stores the tasks that are associated with verifying and validating the delivery location for a purchase line.\n\n</td></tr><tr><td>\n\nEmployee Credit\n\n \\[sn\\_shop\\_employee\\_credit\\]\n\n</td><td>\n\nStores the credit amount that is allocated for a user with supporting information such as the responsible cost center and credit allocation rule.\n\n</td></tr><tr><td>\n\nLedger Assignment Rules\n\n \\[sn\\_shop\\_ledger\\_assignment\\_rule\\]\n\n</td><td>\n\nStores the rules that apply to the supplier products, product model or product category, and cost center. These rules are based on the accounting details, such as the capex and expense accounts, that are populated on a purchase line.\n\n</td></tr><tr><td>\n\nModel Map\n\n \\[sn\\_shop\\_m2m\\_model\\_map\\]\n\n</td><td>\n\nStores the mapping between a CMDB model and a third-party category.\n\n</td></tr><tr><td>\n\nNegotiation\n\n \\[sn\\_shop\\_negotiation\\]\n\n</td><td>\n\nStores the negotiation object that is created for a supplier product in a sourcing activity.\n\n</td></tr><tr><td>\n\nSourcing Event\n\n \\[sn\\_shop\\_negotiation\\_event\\]\n\n</td><td>\n\nStores the sourcing events that are created for a supplier product in a sourcing activity.\n\n</td></tr><tr><td>\n\nNon Catalog Intake\n\n \\[sn\\_shop\\_non\\_catalog\\_intake\\]\n\n</td><td>\n\nExtends the Import Set Row table and acts like a staging table for the non-catalog intake flow.\n\n</td></tr><tr><td>\n\nOrder Permission\n\n \\[sn\\_shop\\_m2m\\_order\\_users\\_covered\\]\n\n</td><td>\n\nStores the mapping between the purchasing permission and purchase order.\n\n</td></tr><tr><td>\n\nPaycheck Periods\n\n \\[sn\\_shop\\_paycheck\\_periods\\]\n\n</td><td>\n\nStores the number of paychecks through which a payment would be made.\n\n</td></tr><tr><td>\n\nPayment Methods\n\n \\[sn\\_shop\\_payment\\_method\\]\n\n</td><td>\n\nStores the payment method that is selected by the shopper and the cost center or person responsible for the payment.\n\n</td></tr><tr><td>\n\nPercent Complete Configuration\n\n \\[sn\\_shop\\_percent\\_complete\\_config\\]\n\n</td><td>\n\nStores the configurations to determine the percentage of payment that is completed for an order.\n\n</td></tr><tr><td>\n\nPre-Payment\n\n \\[sn\\_shop\\_pre\\_payment\\]\n\n</td><td>\n\nStores a record of prepayment done for a purchase line as per a contract.\n\n</td></tr><tr><td>\n\nProduct Purchases by Job Code\n\n \\[sn\\_shop\\_user\\_product\\_purchase\\]\n\n</td><td>\n\nStores the aggregation of products purchased by the job code.\n\n</td></tr><tr><td>\n\nProduct Stage\n\n \\[sn\\_shop\\_imp\\_product\\]\n\n</td><td>\n\nExtends the Import Set Row table. This staging table is used to import supplier products.\n\n</td></tr><tr><td>\n\nProperties\n\n \\[sn\\_shop\\_properties\\]\n\n</td><td>\n\nStores the Shopping Hub specific properties such as the requisition auto order.\n\n</td></tr><tr><td>\n\nPurchase\n\n \\[sn\\_shop\\_purchase\\]\n\n</td><td>\n\nStores the purchase record that is created for each purchasing or sourcing activity.\n\n</td></tr><tr><td>\n\nPurchase Line\n\n \\[sn\\_shop\\_purchase\\_line\\]\n\n</td><td>\n\nExtends the Request Line table and stores the purchase line that is associated with a purchasing or sourcing activity.\n\n</td></tr><tr><td>\n\nPurchase Order History\n\n \\[sn\\_shop\\_order\\_history\\]\n\n</td><td>\n\nExtends the Order Template table and stores the older purchase order record when an order is revised.\n\n</td></tr><tr><td>\n\nPurchase Order Line History\n\n \\[sn\\_shop\\_order\\_line\\_history\\]\n\n</td><td>\n\nExtends the Order Line Template table and stores the older purchase order line record when a purchase order line is revised.\n\n</td></tr><tr><td>\n\nPurchase Requisition\n\n \\[sn\\_shop\\_purchase\\_requisition\\]\n\n</td><td>\n\nStores the purchase requisition for a purchase or sourcing activity.\n\n</td></tr><tr><td>\n\nPurchases by Category\n\n \\[sn\\_shop\\_user\\_category\\_purchase\\]\n\n</td><td>\n\nStores the analytical data for purchases by product category.\n\n</td></tr><tr><td>\n\nPurchasing Permission\n\n \\[sn\\_shop\\_covered\\_user\\]\n\n</td><td>\n\nStores the purchasing permission for a user, group, cost center, or department.\n\n</td></tr><tr><td>\n\nPurchasing Task\n\n \\[sn\\_shop\\_task\\]\n\n</td><td>\n\nStores the various tasks that are associated with a purchase such as finance and contract tasks. This is a base table within the Common Service Delivery \\(SDC\\) application.\n\n</td></tr><tr><td>\n\nReceipt Task\n\n \\[sn\\_shop\\_receipt\\_task\\]\n\n</td><td>\n\nExtends the Acknowledgment Task table and stores the state of a receipt confirmation.\n\n</td></tr><tr><td>\n\nRequest Line Template\n\n \\[sn\\_shop\\_request\\_line\\]\n\n</td><td>\n\nExtends the Shop Line table and stores the purchase request line items.\n\n</td></tr><tr><td>\n\nRequisition Permission\n\n \\[sn\\_shop\\_m2m\\_purchasing\\_users\\_covered\\]\n\n</td><td>\n\nStores the mapping between the purchasing permission and purchase requisition.\n\n</td></tr><tr><td>\n\nRequisition to Contract Relationships\n\n \\[sn\\_shop\\_m2m\\_requisition\\_contract\\]\n\n</td><td>\n\nStores the mapping between the requisition and contract.\n\n</td></tr><tr><td>\n\nRevision Line\n\n \\[sn\\_shop\\_rev\\_request\\_line\\]\n\n</td><td>\n\nExtends the Request Line Template table and stores the revision line for a purchase.\n\n</td></tr><tr><td>\n\nRevision Request\n\n \\[sn\\_shop\\_revision\\_request\\]\n\n</td><td>\n\nExtends the Purchasing Task table and stores the state of a revision request for a purchase.\n\n</td></tr><tr><td>\n\nService Acknowledgment\n\n \\[sn\\_shop\\_service\\_acknowledgment\\]\n\n</td><td>\n\nStores the acknowledgment tasks of services received.\n\n</td></tr><tr><td>\n\nShop Line\n\n \\[sn\\_shop\\_line\\]\n\n</td><td>\n\nStores the order line template and request line template. This is a base table.\n\n</td></tr><tr><td>\n\nShopper's Top Suppliers\n\n \\[sn\\_shop\\_usr\\_preferred\\_supplier\\]\n\n</td><td>\n\nStores the mapping between the shopper and preferred supplier.\n\n</td></tr><tr><td>\n\nShopping Control\n\n \\[sn\\_shop\\_shopping\\_control\\]\n\n</td><td>\n\nStores the security rules that determine the access of supplier products for a given user.\n\n</td></tr><tr><td>\n\nShoppingHub API Cache\n\n \\[sn\\_shop\\_shopnow\\_api\\_cache\\]\n\n</td><td>\n\nStores the cached data for quicker access by APIs. An example is the CachedCagetoryMap.\n\n</td></tr><tr><td>\n\nShoppingHub Configuration\n\n \\[sn\\_shop\\_shopnow\\_content\\]\n\n</td><td>\n\nStores configurations that determine certain aspects of the application appearance and behavior. An example is the terms and conditions page URL.\n\n</td></tr><tr><td>\n\nSourcing Bid Stage\n\n \\[sn\\_shop\\_imp\\_sourcing\\_bid\\]\n\n</td><td>\n\nStores the bids that are received for a supplier product by the third-party providers. This is a staging table.\n\n</td></tr><tr><td>\n\nSourcing Line Outbound Queue\n\n \\[sn\\_shop\\_sourcing\\_line\\_out\\_queue\\]\n\n</td><td>\n\nStages the sourcing line for the third-party providers.\n\n</td></tr><tr><td>\n\nSourcing Outbound Queue\n\n \\[sn\\_shop\\_sourcing\\_out\\_queue\\]\n\n</td><td>\n\nStages the sourcing request for the third-party providers.\n\n</td></tr><tr><td>\n\nSourcing Request\n\n \\[sn\\_shop\\_sourcing\\_activity\\]\n\n</td><td>\n\nStores requests to source for supplier products.\n\n</td></tr><tr><td>\n\nSourcing Task\n\n \\[sn\\_shop\\_sourcing\\_task\\]\n\n</td><td>\n\nExtends the Purchasing Task table and stores the tasks that are related to a sourcing request.\n\n</td></tr><tr><td>\n\nSourcing Vendor\n\n \\[sn\\_shop\\_sourcing\\_vendor\\]\n\n</td><td>\n\nStores the mapping between the sourcing vendor code and sourcing vendor name.\n\n</td></tr><tr><td>\n\nSupplier Product\n\n \\[sn\\_shop\\_supplier\\_product\\]\n\n</td><td>\n\nStores the supplier products that represent goods or services that can be listed on the portal.\n\n</td></tr><tr><td>\n\nSupplier Product View\n\n \\[sn\\_shop\\_supplier\\_product\\_view\\]\n\n</td><td>\n\nStores the analytics of the number of views for a supplier product.\n\n</td></tr><tr><td>\n\nSupplier Use by Department\n\n \\[sn\\_shop\\_dept\\_supplier\\_purchase\\]\n\n</td><td>\n\nStores the analytics of suppliers that are used by departments.\n\n</td></tr><tr><td>\n\nSupplier Use by Shopper\n\n \\[sn\\_shop\\_user\\_supplier\\_purchase\\]\n\n</td><td>\n\nStores the analytics of suppliers that are used by shoppers.\n\n</td></tr><tr><td>\n\nThird-Party Category\n\n \\[sn\\_shop\\_third\\_party\\_category\\]\n\n</td><td>\n\nStores an external category that is provided by a supplier that maps to an existing model.\n\n</td></tr><tr><td>\n\nUser Controls\n\n \\[sn\\_shop\\_user\\_control\\]\n\n</td><td>\n\nStores the mapping of a user and a shopping control.\n\n</td></tr></tbody>\n</table>## Purchasing properties\n\nThe following list contains the purchasing properties that are used by Sourcing and Procurement Operations.\n\n<table id=\"table_g42_qmr_flb\"><thead><tr><th>\n\nProperty\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nsn\\_shop.atf.threshold.days\n\n</td><td>\n\nNumber of days before an expected delivery date for goods, or a start date for services and blankets, in which time a purchase requisition would be considered after the fact.\n\n</td></tr><tr><td>\n\nsn\\_shop.credit.allocation.batchsize\n\n</td><td>\n\nTotal number of employee records that are processed in a batch, during credit allocation.\n\n</td></tr><tr><td>\n\nsn\\_shop.default.contract.model.type\n\n</td><td>\n\nDefault contract model when creating contracts.\n\n</td></tr><tr><td>\n\nsn\\_shop.default.purchasing.time\n\n</td><td>\n\nInitial value of the purchasing time in days.\n\n</td></tr><tr><td>\n\nsn\\_shop.default.shipping.estimate\n\n</td><td>\n\nDefault shipping estimate, in percentage.\n\n</td></tr><tr><td>\n\nsn\\_shop.default.sourcing.time\n\n</td><td>\n\nInitial sourcing time in days.\n\n</td></tr><tr><td>\n\nsn\\_shop.default.supplier.onboard.time\n\n</td><td>\n\nInitial supplier onboarding time in days.\n\n</td></tr><tr><td>\n\nsn\\_shop.non.pricing.contract\n\n</td><td>\n\nList of non-pricing contracts. The default is NDA.\n\n</td></tr><tr><td>\n\nsn\\_shop.shipping.estimate.inclusion\n\n</td><td>\n\nShipping estimate included in purchase request approvals.\n\n</td></tr><tr><td>\n\nsn\\_shop.approval.reassessment.resend\n\n</td><td>\n\nApprovals that must be reassessed during a revision if the same approval rule is triggered. It applies to both purchase requisition and purchase order revisions.\n\n</td></tr><tr><td>\n\nsn\\_shop.log.property\n\n</td><td>\n\nLogging level for Sourcing and Purchasing Automation.\n\n</td></tr><tr><td>\n\nsn\\_shop.spend.requisition.autoorder\n\n</td><td>\n\nPurchase order that can be automatically created on completion of purchasing tasks without having to undergo a manual final review.For more information on how the auto-order properties affect purchase order creation, see [Purchase requisition auto-order](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/pr-auto-order.md).\n\n</td></tr><tr><td>\n\nsn\\_shop.spend.requisition.autoorder.threshold\n\n</td><td>\n\nDollar amount threshold above which a final review is required before a purchase order is created even when the automatic creation of purchase orders property is set to Yes.For more information on how the auto-order properties affect purchase order creation, see [Purchase requisition auto-order](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/pr-auto-order.md).\n\n</td></tr><tr><td>\n\nsn\\_shop.spend.sla.due.days\n\n</td><td>\n\nMinimum due date for SLA calculation.\n\n</td></tr><tr><td>\n\nsn\\_shop.supported.artifact.formats\n\n</td><td>\n\nFormats that are supported for supplier product artifacts.\n\n</td></tr><tr><td>\n\nsn\\_shop.tax.estimate.inclusion\n\n</td><td>\n\nIncludes generated tax estimate in purchase requests for the approval process.\n\n</td></tr></tbody>\n</table>## Watchlist properties\n\nSet the `sn_shop.watchlist.user.limit` system property to restrict the maximum number of users in the watchlist to 20.\n\nRole required:\n\n-   sn\\_shop.procurement\\_administrator, sn\\_shop.shopping\\_hub\\_admin - Edit and view.\n-   sn\\_shop.procurement\\_administrator, sn\\_shop.shopping\\_hub\\_admin, sn\\_shop.shopper, sn\\_shop.procurement\\_specialist, sn\\_spend\\_psd.agent - View \\(read-only\\).\n\nTo modify the user limit, do the following:\n\n1.  Navigate to **All**.\n2.  On the left navigation pane, enter `sys_properties_list.do`.\n\n    The entire list of properties in the System Properties \\[sys\\_properties\\] table appears.\n\n3.  In the Name search field, look for **sn\\_shop.watchlist.user.limit** and open the system property.\n\n    The system property **sn\\_shop.watchlist.user.limit** opens as a record. The **Value** field displays the default value as 20. You can edit the record in editing mode.\n\n4.  In the **Value** field, you can modify the value as per your requirement.\n\n    For example, 5.\n\n5.  Select **Update**.\n\n## Property to automate the edit receipt flow\n\nEnable the `sn_spend_cp.enable_automated_edit_receipt_flow` system property to automate the approval and processing of edit receipt requests without manual intervention. The automated process updates the purchase order \\(PO\\) and purchase order line \\(POL\\) quantities, while also automatically closing the associated procurement case in the Source-to-Pay Workspace.\n\nRole required: sn\\_shop.shopping\\_hub\\_admin and sn\\_shop.procurement\\_administrator\n\nThis property is enabled by default. However, if this property is disabled, do the following to enable it:\n\n1.  Navigate to **All**.\n2.  On the left navigation pane, enter `sys_properties_list.do`.\n\n    The entire list of properties in the System Properties \\[sys\\_properties\\] table appears.\n\n3.  In the Name search field, look for **sn\\_spend\\_cp.enable\\_automated\\_edit\\_receipt\\_flow** and open the system property.\n\n    The system property is enabled by default. The **Value** field displays the default value as **ON**.\n\n4.  If the **Value** field shows **OFF**, change it to **ON** to enable this property.\n5.  Select **Update**.\n\n**Parent Topic:**[Install Sourcing and Procurement Operations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/source-to-pay-operations/sourcing-and-procurement-operations/install-spo-ai.md)\n\n## Properties installed with Finance Common Architecture\n\nUse these properties to configure various settings in the Sourcing and Procurement Operations application.\n\n|Property|Description|\n|--------|-----------|\n|default\\_je\\_sheet\\_name|Default sheet name of a Microsoft Excel file used to import journal entries.|\n|number\\_of\\_future\\_periods|Number of future periods that are available in the Period filter list on the Finance Workspace.|\n|number\\_of\\_prior\\_periods|Number of prior periods that are available in the Period filter list on the Finance Workspace.|\n\n"}}