Extensions to SCV Data model

The entity has been extended to add the property together with all related configuration (such as Inbox->Core mappings, datasheets, currency conversion rules for amount columns):

  • LOCATION: subtype

Currently only used when location type is Warehouse. In this case, the only allowed subtype value is Store. The location_subtype property already exists in the LOCATION entity. The difference is that the location_subtype holds the subtype as in ERP without mapping the imported values to a pre-defined list of subtypes. On the other hand, subtype is validated against an LOV, a controlled list of values.

These entities have been extended to add these properties with all related configuration (such as Inbox->Core mappings, datasheets, currency conversion rules for amount columns) These new properties are used in SCV database view SP_V_CUSTOMER_ALLOCATIONS to support splitting lost sales into lost orders and lost forecast implemented in SCO:

  • ITEM_SALES: min_orders_service_level, xs_min_orders_service_level
  • ITEM_LOCATION: min_orders_service_level, xs_min_orders_service_level
  • ITEM_NPI: min_orders_service_level, xs_min_orders_service_level
  • ITEM_CUSTOMER: min_orders_service_level, xs_min_orders_service_level

These entities have been extended to add these properties with all related configuration (such as Inbox->Core mappings, datasheets, currency conversion rules for amount columns). These new properties are also used in SCV database view SP_V_CUSTOMER_ALLOCATIONS to allow moving forecast to back-orders in SCO:

  • ITEM_SALES: backorders_allowed_flag_orders, xs_backorders_allowed_flag_orders, backorders_allowed_flag_forecast, xs_backorders_allowed_flag_forecast
  • ITEM_LOCATION: backorders_allowed_flag_orders, xs_backorders_allowed_flag_orders, backorders_allowed_flag_forecast, xs_backorders_allowed_flag_forecast
  • ITEM_NPI: backorders_allowed_flag_orders, xs_backorders_allowed_flag_orders, backorders_allowed_flag_forecast, xs_backorders_allowed_flag_forecast
  • ITEM_CUSTOMER: backorders_allowed_flag_orders, xs_backorders_allowed_flag_orders, backorders_allowed_flag_forecast, xs_backorders_allowed_flag_forecast

These SCV entity properties have been deprecated:

  • ITEM_LOCATION: inv_use_order_freq_flag, xs_inv_use_order_freq_flag
  • INVENTORY: inv_use_order_freq_flag, xs_inv_use_order_freq_flag
  • INVENTORY_PLAN.inv_use_order_freq_flag

These entities have been extended to add these properties together with all related configuration (such as Inbox->Core mappings, datasheets, currency conversion rules for amount columns.):

  • ITEM_LOCATION: inv_preflot_or_replendays, xs_inv_preflot_or_replendays
  • INVENTORY: inv_preflot_or_replendays, xs_inv_preflot_or_replendays
  • INVENTORY_PLAN: inv_preflot_or_replendays

The new properties replace the corresponding deprecated SCV properties, namely inv_use_order_freq_flag. The new properties are used by Inventory Planning and can have an enumerated list of values instead of the boolean value (yes/no) that the deprecated properties can have. The new properties can have one of the following values:

  • 0: Manual Preferred Lot Qty is used to calculate the inv_order_freq_days.
  • 1: Manual Replenishment Days (days between orders) is used to calculate the inv_preferred_order_qty.
  • 2: EOQ Qty is used to calculate the inv_order_freq_days.
  • 3: Adjusted EOQ to the nearest increment of seven days is used to calculate the inv_order_freq_days.
  • 4: Adjusted EOQ to the nearest increment of batch (Units per Storage Unit) is used to calculate the inv_order_freq_days.

This new macro and corresponding new mappings and view have been added to migrate data from the inv_use_order_freq_flag deprecated property to the inv_preflot_or_replendays new property in the SC_INVENTORY_PLAN table:

  • SCV - Migrate Use Order Frequency Flag (SC_INVENTORY_PLAN)

Action required prior to activation:

Existing custom import mappings for the deprecated properties must be adjusted and existing data in the deprecated properties must be migrated to the new properties.

The INVENTORY_PLAN.inv_use_order_freq_flag deprecated property has been published by Inventory Planning. In order to migrate the existing data from the the inv_use_order_freq_flag deprecated property to the inv_preflot_or_replendays new property in the SC_INVENTORY_PLAN table, the following migrate macro must be executed:

  • SCV - Migrate Use Order Frequency Flag (SC_INVENTORY_PLAN)

The INVENTORY.inv_use_order_freq_flag and ITEM_LOCATION.inv_use_order_freq_flag deprecated properties have not been part of a standard ERP integration. If there are custom import mappings to populate these deprecated properties, the custom import mappings must be adjusted to populate the new properties instead.

If there are any manually specified values in the INVENTORY.xs_inv_use_order_freq_flag and ITEM_LOCATION.xs_inv_use_order_freq_flag deprecated extension properties, these are not migrated by the migration macro mentioned above. Values in the deprecated extension properties must be manually copied to the new extension properties.

For both, updating the custom import mappings and migrating the deprecated extension property values, the following data mappings must be used:

  • When inv_use_order_freq_flag = "N" then inv_preflot_or_replendays = 0
  • When inv_use_order_freq_flag = "Y" then inv_preflot_or_replendays = 1
  • When inv_use_order_freq_flag = <empty> then inv_preflot_or_replendays = <empty>
Note: This feature is enabled after loading the base template (base.zip) for this version. You are not required a new role or privilege access to use this feature.