Event plan upload file structure include the following metadata information:

• Event Note
• Status of the event (Draft, Planned, Executed)
• Type of the event
• Name of the event
• ID of the event (blank for newly uploaded events)
• Event Include in History (1 or 0)
• Context where the event is applied (Customer, Item, Location level specific fields, defining a hierarchical context)
• Bucket type
• Period-Unit - event plan unit adjustment within each period
• Period-Price - event plan asp adjustment within each period

Upload workflow requirements:

• Multiple events may be created or amended with each upload
• If there is no ID provided, a new event will be created even if the event name is already used.
• Event plan adjustments to unit and price will strictly follow the same approach as for user defined forecast and budget.
• If an event is being created for new PCL's, then the item, customer, and location must be included so that the PCL is also created.

Constraints

• It is allowed to upload only unit edits per period for hierarchical context in a row.
• It is allowed to upload combined unit and asp edit per period for hierarchical context in a row. 
• It is not allowed to upload only asp edits per period for hierarchical context in a row.
  • If such an upload is attempted, the following error message will be presented: "Invalid price bucket edit for period {PeriodDate}, because a corresponding unit bucket edit is missing."

Make the change to units and/or price to one or more entities within the download file and then prepare to upload.

Change the name of the file to "eventplanningforecast" and then zip the file and upload as normal.

In the example below, the event values for the first line have been changed.

Following the upload process, you may review the error log for errors.

The uploaded changes are applied against the given context.

As noted above, adding a note to a single line will add a not against the event. Changing the status of a single line will not change Event Status.

For simplicity, we recommend starting with a previously downloaded Event Plan with the proper date periods and formatting.

Rules:

1. The event plan upload will upload a plan as new entry if the event plan id column is blank for that file row.
2. If there are multiple rows with a blank event plan id column, grouping will be applied based on the value of the event plan name column, so every group will be treated as unique new event plan and data will be merged.
3. If there is such a case described in 2), values for the event plan status, type name, note will be merged sequentially and based on row numbers in ascending order and only final result will saved and logged.

Validation

• Id (EventId***) - event plan must be blank for new events.
• Name (EventName***) - event plan name is a mandatory field.
  • "Event name must not be empty." - when is empty.
  • "Event name must not exceed 200 characters." - when name exceeds max length.
•  Type (EventType***) - event plan type name is mandatory field.
  • "Event type must be supplied." - when is empty.
  • "Event type must be eligible from existing event types." - when name doesn't exists in the system.
• Status (EventStatus***) - event plan status is mandatory field.
  • "Event status must be eligible from existing event statuses." - when event status is missing or cannot be mapped to an either of Draft/Planned/Executed.
• Note (EventNotes***) - event note is optional field.
  • "Event notes must not exceed 512 characters." - when note exceeds max length.
• Include into History (EventIncludeIntoHistory***) - optional, value is 1/0.

Errors are parsed per file upload row and added to the file error log as: "Line was: [row number]. [error message]."

The new events appear in the event list with an auto-generated Event ID.

Event plan download file structure include the following metadata information:

• EventNotes: Event specific notes
• EventStatus: Status of the event (Draft, Planned, Executed)
• EventType: Type of the event
• EventName: Name of the event
• EventID: ID of the event (blank for newly uploaded events)
• EventIncludeIntoHistory: 0 if included, 1 if excluded
• Context where the event is applied (Customer, Item, Location level specific fields, defining a hierarchical context)
• Bucket type: Month or Week
• Period-Unit - event plan unit adjustment within each period
• Period-Price - event plan asp adjustment within each period

Constraints

• In a bucket weekly/monthly within report range, where an event adjustment is being made will export the actual unit or price value in the report.
• In a bucket weekly/monthly within report range, where an event adjustment is not being present will be blank in the report.

Custom period range:

• From date is a date field based on calendar availability min/max range of the selected bucket type (weekly, monthly).
• Number of bucket forward is a number field, which be used to filter available buckets forward based on calendar min/max restrictions in bucket type selection.

Once an event plan is created, to download,

1. Click the download icon
2. Select event plan as the Report Type, the desired Bucket type, period, and which columns to include
3. Click "Run Report"

Once the report is prepared, it is made available in Reports Download Panel. The report will include a unique ID appended to the filename.

Click report name hyperlink to download

The data downloaded in the report will present the selected Event Plan at the lowest level of the given event plan hierarchy which in the example below is customer > item

If you do not wish to include the level below where the event is created, simply remove the level and re-download the Event Plan. Below is the excel of the same event as above without the item level included.

Below is an example of another event where the hierarchy is location > product category