Change SCV interface to use SCO mapping views

Several Supply Planning interface services importing data from SCV are updated to use SCO mapping views (SP_V_*). This reduces overall maintenance and synchronizes data mappings between SCV and other applications, related to supply, for example, the direct SCV – SCO integration from the apsco template.

These interface services are updated:

  • SPLS - SCV -Import Product Measures: SP_V_PRODUCTS
  • SPLS - SCV -Import Product at Location Measures: SP_V_PRODUCTS_AT_LOCATIONS
  • SPLS - SCV -Import Location Measures: SP_V_LOCATIONS
  • SPLS - SCV -Import Product at Location Stock on Hand: SP_V_QTY_ON_HAND
  • SPLS - SCV -Import Product at Location Start Stock Expiring Plan: SP_V_EXPIRING_QTY_ON_HAND
  • SPLS - SCV -Import Resources Measures: SP_V_RESOURCES
  • SPLS - SCV -Import Production Measures: SP_V_RESOURCE_ALLOCATIONS
  • SPLS - SCV -Import Customer Measures: SP_V_CUSTOMER_ALLOCATIONS
  • SPLS - SCV -Import Forecast: SP_V_FORECASTS_PLAN_AGGR
  • SPLS - SCV -Import Customer Bucket Measures: SP_V_FORECASTS_PLAN_AGGR
  • SPLS - SCV -Import Forecast SC_DEMAND: SP_V_FORECASTS
  • SPLS - SCV -Import Customer Bucket Measures SC_DEMAND: SP_V_FORECASTS
  • SPLS - SCV -Import Supplier Locations: SP_V_SUPPLIERS
  • SPLS - SCV -Import Base Suppliers: SP_V_SUPPLIERS
  • SPLS - SCV -Import Supplier Measures: SP_V_SUPPLIER_ALLOCATIONS
  • SPLS - SCV -Import Item Supplier Measures: SP_V_SUPPLIER_ALLOCATIONS
  • SPLS - SCV -Import Item Supplier Calendar: SP_V_MAX_PURCHASE_QTY
  • SPLS - SCV -Import Process Groups Calendar: SP_V_PROCESS_GROUP_CALENDAR
  • SPLS - SCV -Import Processes: SP_V_PROCESSES
  • SPLS - SCV -Import Routings Outflow: SP_V_FORMULAS
  • SPLS - SCV -Import Routings Inflow: SP_V_FORMULAS
  • SPLS - SCV -Import Current WIP on hand: SP_V_QTY_ON_HAND_WIP

For these interfaces user overrides to SCV Database Views are possible without having to duplicate or customize Supply content.