Business plans

Multiple plans can be published to SCV Core by different SCP applications. These plans can contain production plans, purchase plans and transfer plans potentially with different horizons. Business plans are also used to prepare the published plans for export to the ERP. These plans are assembled from published plans for a selected group of items and locations within a category as well as across categories. The CloudSuite SCP platform, SCV, Supply Planning, Production Scheduling and M3 Integration have been updated to support business plans.

The changes related to the business plan for SCV are mainly to the outbound flow. New plan entities have been introduced to maintain the pu blished production/purchase/transfer plans. The new SCV configuration screens for business plans, export profiles and item/location data selections, have been introduced to assemble business plans for exporting to the ERP. The SCP cycle period calendars are synchronized with SCV; new SCV programs made available to log plan details and generate publish horizons for business plans. New publish views to move published plans from SCV Core to SCV Outbox are delivered along with functionality to regenerate/revert publish views based on enabled business plan definitions. Changes to the CloudSuite SCP Platform and SCV related to business plans are listed below.

New SCV configuration entities:

  • Business Plans: Assemble business plans from the plans published by SCP applications and prepare the Plans for exporting to the ERP.
  • Export Profiles: This is used in business plans to group plans that must be exported together.
  • Data Selection Rules: This is used in business plans to filter the available planning data in SCV, including items and locations.

New application variables:

  • scv_use_business_plans_for_outbound: This variable is used to trigger business plan-based inbound and outbound flows.
  • scv_export_profile: This is used in outbound macros to set the source value at runtime.

New SCV configuration parameters:

  • SCP_DEFAULT_EXPORT_PROFILE: This is used to indicate the default SCV Export Profile. The default export profile is used sequentially by the standard publish views between the new plan entities, as the source value. When no business plans exist or when all existing business plans are disabled, the generated publish views use the default export profile as the source value.

Updated column registry for plan entities. These common columns are now added to all tables created from SCV plan entities:

  • plan_id
  • plan_value_id: Defaults to an auto-generated numeric value, if no explicit value is specified during inserts/updates.
  • plan_value_status
  • plan_category
  • plan_type
  • plan_subtype
  • plan_description
  • plan_version
  • plan_version
  • plan_value_type
  • planner_id
  • remark

    Standard entity definitions containing one of these columns have been updated to remove the column from entity definition. To support successful loading of older templates that still contain any of these columns, template loader is updated to exclude the columns from the loaded entity definition.

New entity-specific properties are introduced to maintain SCP order details:

  • scp_order_number: A unique functional key for orders.
  • scp_order_sequence_number: This property is used when orders are split to meet maximum order quantity constraints.
  • scp_order_status: The status of supply orders. The status can be set to Planned, Firm Planned, New, Open, Released, In Progress, Completed or Cancelled.
  • scp_ordergroup_number: This is used by Supply Planning to indicate the planned orders that are committed together.
  • scp_ref: This property is used by Supply Planning to distinguish the planned orders with the same dimension values (that is reference), such as planned purchase orders with the same item, warehouse, supplier and date values. The existing column in SCV plan tables is repurposed.
  • erp_order_number: Order number displayed in ERP.
  • erp_line_number: If applicable, line number displayed in ERP.
  • erp_subline_number: If applicable, subline number displayed in ERP.
  • erp_schedule_line_number: If applicable, schedule line number displayed in ERP.

New SCV business plan:

  • BASE_SUPPLY_PLAN

New SCV export profiles:

  • BASE_EXPORT_PROFILE
  • BASE_EXPORT_PROFILE_ORDERS
  • BASE_EXPORT_PROFILE_PLANNED_ORDERS

New SCV data selection rules:

  • BASE_SUPPLY_ITEM_SELECTION
  • BASE_SUPPLY_LOCATION_SELECTION

New SCV internal tables:

  • SZ_SCP_CALENDAR: This maintains cycle period calendars published by CloudSuite SCP.
  • SZ_PLAN_PUBLISH_LOG: This maintains logged plan details such as plan calendar, plan start and end dates.
  • SZ_BUSINESS_PLAN_PUBLISH_HORIZON: This maintains generated horizon start and end dates for business plans.

New SCV programs:

  • LOG_PLAN
  • EXECUTE_GENERATE_BUSPLAN_HORIZON
Updated SCV program:
  • PURGE_PLAN: Now accepts plan_category, plan_name and scp_order_status as input parameters.

New SCV Plan entities and all related configuration such as table registry, constraints, and datasheets:

  • PRODUCTION_PLAN
  • PRODUCTION_PLAN_OP
  • PURCHASE_PLAN
  • TRANSFER_PLAN

New publish views between the SCV Core and SCV Outbox tables of the new plan entities:

  • SC_V_PUB_PRODUCTION_PLAN
  • SC_V_PUB_PRODUCTION_PLAN_OP
  • SC_V_PUB_PURCHASE_PLAN
  • SC_V_PUB_TRANSFER_PLAN
  • SC_V_BP_PRODUCTION_PLAN
  • SC_V_BP_PURCHASE_PLAN
  • SC_V_BP_TRANSFER_PLAN

New SCV mappings between SCV PUB views and SCV Outbox for the new plan entities:

  • BASE_SC_V_PUB_PRODUCTION_PLAN-SO_PRODUCTION_PLAN
  • BASE_SC_V_PUB_PRODUCTION_PLAN_OP-SO_PRODUCTION_PLAN_OP
  • BASE_SC_V_PUB_PURCHASE_PLAN-SO_PURCHASE_PLAN
  • BASE_SC_V_PUB_TRANSFER_PLAN-SO_TRANSFER_PLAN

New and updated macros to implement the outbound flow using business plans:

  • SCV - Generate Business Plans Publish Horizons: Generates business plan publish horizon start and end dates based on business plan definition and synchronized SCP cycle period calendars.
  • SCV - Outbound Supply Plan Full (updated macro): When scv_use_business_plans_for_outbound = 1, existing flow is disabled and only the new flow is enabled. The new flow first generates business plan publish horizons and later moves the plan data from SCV Core tables to SCV Outbox tables for the new plan entities. When moving plan data, the new flow uses the export profile as specified in scv_export_profile as source.
  • SCV - Outbound Supply Plan Full (Orders): This new macrosets scv_export_profile = BASE_EXPORT_PROFILE_ORDERS and executes macro SCV - Outbound Supply Plan Full.
  • SCV - Outbound Supply Plan Full (Planned Orders): This new macro sets scv_export_profile = BASE_EXPORT_PROFILE_PLANNED_ORDERS and executes macro SCV - Outbound Supply Plan Full.

SCV inbound flow is aligned with the outbound flow. Entities that maintains the imported supply orders have been extended with the new SCP order related properties. New LOV is defined to specify the allowed values for the new SCP Order Status property.

These SCV Plan entities are updated to add scp_order_status, ext_order_status and scp_order_number. Related configuration such as datasheets, Inbox->Core mappings, is also updated.

  • PROD_CNCL_TRX
  • PROD_HIST_TRX
  • PROD_OPEN_TRX
  • PROD_PLND_TRX
  • PURCHASE_CNCL_TRX
  • PURCHASE_HIST_TRX
  • PURCHASE_OPEN_TRX
  • PURCHASE_PLND_TRX
  • TRANSFER_CNCL_TRX
  • TRANSFER_HIST_TRX
  • TRANSFER_OPEN_TRX
  • TRANSFER_PLND_TRX

New Validation LOVs:

  • SCP Order Status
  • SCP Order Planned Status
  • SCP Order Open Status
  • SCP Order History Status
  • SCP Order Cancel Status

New validation rules - to validate scp_order_status against the newly created LOVs:

  • BASE PROCNCLTRX SCP Order Status
  • BASE PROHISTTRX SCP Order Status
  • BASE PROOPENTRX SCP Order Status
  • BASE PROPLNDTRX SCP Order Status
  • BASE PURCNCLTRX SCP Order Status
  • BASE PURHISTTRX SCP Order Status
  • BASE PUROPENTRX SCP Order Status
  • BASE PURPLNDTRX SCP Order Status
  • BASE TRACNCLTRX SCP Order Status
  • BASE TRAHISTTRX SCP Order Status
  • BASE TRAOPENTRX SCP Order Status
  • BASE TRAPLNDTRX SCP Order Status

This feature is available after appending the base template (base.zip) for the current version. New SCV Outbound Flow using Business Plans is enabled after setting the scv_use_business_plans_for_outbound application variable to 1. The default value for this application variable is 0, maintaining existing behavior.

New SCV Outbound Flow is executed by ’source’, which is controlled by the scv_export_profile application variable. The default value for this application variable is BASE_EXPORT_PROFILE. This default value is used when the standard delivered publish views are used; in this case, all plan data is published from SCV Core to SCV Outbox. When the publish views are generated from business plans, application variable must be set to one of the BASE_EXPORT_PROFILE_ORDERS or BASE_EXPORT_PROFILE_PLANNED_ORDERS values. Alternatively, executing macros SCV - Outbound Supply Plan Full (Orders) or SCV - Outbound Supply Plan Full (Planned Orders) can internally set the application variable only for the duration of macro execution. In this case, orders or (firm) planned orders are published from SCV Core to SCV Outbox.
Note: By default, this feature is enabled. No additional role or privilege is required to access this feature.