Use start date when publishing (firm) planned production orders to SCV

In M3, only the end date is accepted when creating planned and firm planned production orders. Hence, (firm) planned production orders must be published on the end date. The routing specified for the order is validated against the end date and the start date is calculated based on the production lead time in M3. The reason for publishing on start date instead of end date is the processing and validation of (firm) planned production orders in M3. M3 accepts only end date when creating planned and firm planned production orders. The specified routing on the order is validated against the end date and the start date is calculated based on the production lead time in M3.

In SCP, start date is used to validate routings/processes that are used for production (as the moment when materials are allocated). When routings have effective dates in M3, and a production order starts during one routing’s effective period and completes in another alternative routing’s effective period, this causes validation issues either in M3 or in SCP. Validation issues occur either in M3 or in SCP if:

• Routings have effective dates in M3.
• A production order starts during one routing’s effective period.
• Completes the production order in the effective period of another routing.

To synchronize, SCP is now publishing planned and firm planned production orders to SCV using start dates. In SCV, as a post-publish step, the order end dates are calculated using production lead times.

Production lead times in turn are determined in SCV using the user-defined lead times. If not available, the production lead times are determined or, if that is not available, using imported lead times. The planned and firm planned production orders are then exported to M3 using these calculated end dates.

When importing planned and firm planned production orders from M3, the routing specified on the order is matched with the alternative routings imported from M3. Mismatches can occur when importing the orders to SCV as M3 uses end date to validate routings at order creation time. Therefore, the matching logic in SCV is modified to stretch the effective from date of imported routings with the same production lead time used when calculating the end dates of the published orders. Then order’s start dates are used to match the imported routings.

The BASE_SC_V_UPD_PRODUCTION_PLAN_LEAD_TIME-SC_PRODUCTION_SCV mapping is updated.

These interface services are updated:

• SPLS - SCV - Export Planned Production Plan buckets

  Removed mapping: planned_end_time = CalendarPeriod.EndDate

  Added mapping: planned_start_time = CalendarPeriod

• SPLS - SCV - Export Planned Production Plan orders

  Removed TD mapping: planned_end_time = Date

• SPLS - SCV - Export Firm Planned Production Plan orders

  Removed TD mapping: planned_end_time = Date

These macros are updated:

• Supply - Publish Plan to SCV

  Added macro step: RunSCV("EXECUTE_TRANSFER","-SOURCE=%app_var_scv_spls_profile%","-REFRESH_MODE=Full","-TARGET_DELETE_MODE=None","-TARGET_UPDATE_MODE=Merge","-MAPPING_NAME=BASE_SC_V_UPD_PRODUCTION_PLAN_LEAD_TIME-SC_PRODUCTION_PLAN") with condition '%app_var_scv_use_business_plans_for_outbound%' == '1'

• Supply - Export Fixed Orders

  REFRESH_MODE=Full","-TARGET_DELETE_MODE=None","-TARGET_UPDATE_MODE=Merge","-MAPPING_NAME=BASE_SC_V_UPD_PRODUCTION_PLAN_LEAD_TIME-SC_PRODUCTION_PLAN") with condition '%app_var_scv_use_business_plans_for_outbound%' == '1'

• SP - SCV - SCO - Publish Plan

  Added macro step: RunSCV("EXECUTE_TRANSFER","-SOURCE=%app_var_scv_apsco_profile%","-REFRESH_MODE=Full","-TARGET_DELETE_MODE=None","-TARGET_UPDATE_MODE=Merge","-MAPPING_NAME=BASE_SC_V_UPD_PRODUCTION_PLAN_LEAD_TIME-SC_PRODUCTION_PLAN")

This feature is enabled in Supply Planning after appending the supply planning template (spls.zip) and available in Planning Engine after appending the planning engine template (apsco.zip) for this version.