Exploring FSC common applications

  • Release version: Yokohama
  • Updated February 5, 2025
  • 1 minute to read

    • Explore the FSC common application plugins and their dependencies.

    Table 1. FSC common application plugins
    Plugin name Description Dependencies Mandatory/Optional
    Finance Common Architecture [sn_fin]

    Maintains primary data such as Enterprise Resource Planning (ERP) sources, legal entities, accounting periods, and so on.

    For more information about the components installed with this plugin, see Components installed with Finance Common Architecture.
    • Finance Applications – Common Dependencies [com.snc.fin_dep]
    • Fiscal Calendar [com.snc.fiscal_calendar]
    • Scoped Application Restricted Caller Access [com.glide.scope.access.restricted_caller]
    • Insert Multiple Web Service [com.glide.web_service_insert_multiple]
    		 Mandatory for SPO, SLO, and APO
    ERP Integration Framework [sn_fcms_integrations] Provides integration support between the Platform and common ERP systems.

    For more information about the components installed with this plugin, see Components installed with ERP Integration Framework.
    • Scoped Application Restricted Caller Access [com.glide.scope.access.restricted_caller]
    • Insert Multiple Web Service [com.glide.web_service_insert_multiple]
    		 Mandatory only if you want to use a common integration framework to get the data from third-party ERP systems into Source-to-Pay applications: SPO, SLO, and APO
    Common Service Delivery [sn_spend_sdc] Contains Finance Case, Finance Case Line, Finance Task, and Playbook status tables, as well as other infrastructure that forms the basis of Finance and Supply Chain workflows products.
    • Process Automation Designer Core [com.glide.pad.core]
    • Process Automation Designer for App Engine [com.glide.pad.license]
    • Playbook Experience [com.playbook_experience]
    		 Mandatory for SPO, SLO, and APO
    Source-to-Pay Common Architecture [snc.sn_shop] Provides an architecture to store purchase orders, requisitions, sourcing requests, and other objects that are commonly used across the source-to-pay business processes.

    For more information about the components installed with this plugin, see Components installed with Source-to-Pay Common Architecture.
    • Finance Common Architecture [com.sn_fin]
    • Common Service Delivery [com.sn_spend_sdc]
    		 Mandatory for SPO, SLO, and APO
    Source-to-Pay Integration Framework [sn_spend_intg] Provides a set of staging tables, transform maps, and workflows to integrate Source-to-Pay Operations with third-party ERP system. For more information, see Source-to-Pay integration framework. Source-to-Pay Common Architecture

    [com.snc.sn_shop]

    		 Mandatory only if you want to use a framework to develop a set of API integrations with Source-to-Pay applications: SPO, SLO, and APO
    Supplier Common Architecture [snc.sn_slm] Provides a common architecture to track data objects related to a supplier used in both Supplier Lifecycle Operations andSupplier Collaboration Portal.

    For more information about the components installed with this plugin, see Components installed with Supplier Lifecycle Operations.
    • Finance Common Architecture [sn_fin]
    • External User Registration [snc.external_user_self_registration]
    • Common Service Delivery [sn_spend_sdc]
    • Common Vendor Core [snc.sn_vendor_core] and [com.snc.vendor_core]
    • Document Management [snc.platform_document_management]
    		 Mandatory for SLO