Validation and execution

The selected measures are copied on successful validation and execution of the macro. These are the validation rules:

  • Matching of item, location, period and measure is based on the name of the element, as code lists, hierarchies or configuration versions can differ.
  • When copying between item, location and calendar hierarchies, it is only possible to match the elements within the level. For example, if the source cycle period's 'Item Hierarchy level for storing scenario Values' is at the SKU level, it is possible to copy data to a destination cycle period at the Brand level by aggregating the weekly periods to Brands and matching at this level. It is not possible to prorate as we do not have spreading factors for item, locations and calendar hierarchy types.
  • Source nodes or elements that are not matched (for item, location, period or measure) must be reported in a discard log, based on interface services.
  • Unmatched destinations are not necessarily reported as these are added after the source is created. Hence the received result is 0.
  • When copying a source level that is the level to store scenario values, without a node selection, the const element for that dimension is included and scenario values for included measures of these elements are copied.
  • If the source is a Transactional Data/Order measure and the destination is a standard measure, only the transactional Data/order measure values are copied.
  • If the source is a Transactional Data/Order measure and the destination is also a Transactional Data/Order measure or Null, the Transactional Data/Order is copied. This includes the measure values (for the source and destination) and the transactional data/Order record.
  • If the destination is a Transactional Data/Order Measure and the Source is of other measure types, the measure cannot be copied.
  • For Transactional Data:
    • The start date and end date of Period Label are matched with the ‘To Date’ (received/End Date) of the transactional data. The transactional data/orders with a ‘To Date’ within this period label are included.
    • The location node (and the children) is matched with the ‘To location’ of the transactional data. The Transactional data with a ‘To Location’ at the location node (if base node) or a child (if aggregate) is included.
  • If the source is a Market Intelligence measure and the destination is a standard measure, only the MI measure values are copied. The Event is not copied.
  • If the source is a Market Intelligence measure and the destination is also a Market Intelligence measure or Null, the Market Intelligence Event is copied and re-applied including the Notes created. Also:
    • The events which start and end within the specified period are considered.
    • The MI Event spreads the MI based on the Spreading options stored for the MI Event.
    • Events must be copied based on the creation date. This process assists in maintaining the integrity of the Events and the subsequently spreaded values.
    See the Advanced CopyMIEvent macro.