Validation and execution

These are the validation rules:

• The current Cycle period must include a previously completed Cycle period.
• Matching of periods, scenario and measures is based on the name of the element not on ID.
• The Period Label must exist for aggregate levels in:
  • The destination/current cycle period when ‘Use Destination Period Label’ = True. The base elements under this aggregate are matched with the corresponding base elements in the source cycle period and copied.
  • The source/previous cycle period when ‘Use Destination Period Label’ = False. The base elements under this aggregate are matched with the corresponding base elements in the source cycle period and copied
  If the period label is a base period, the period must exist in the destination/current and source/previous cycle period. Else, data is not copied and the unmatched nodes are reported in the discard log.
• 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 both 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 to 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. 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.
• Only the nodes within the item, location and period hierarchies that exist in the previous and current cycle period are copied. The nodes which do not exist in the previous cycle period are reported in the discard log.

See Advanced CopyMIEvent macros.