What is best practice to reload History for ASR/VMR?

Full year(s)

• Send records in history file E3SXHS52 for the entire current year (excluding current week Period)

• The types of history that can be sent in the E3SXHST52/XHTYPE:
  • G = Regular Demand (Sales)
  • H = Lost Sales
  • F = Promo Sales

• History values will be replaced
• If processing records for new SKUs, send current week values on the E3SXF01 file
• If processing records for SKUs with existing history, send current week values on the weekly bucket field corresponding of the current week
• Before sending records on the E3SXHS52 History file, any SKUs in Super Type relation must be broken before reloading history
• File will be processed during the night job
• Processed SKU will be reforecast automatically

• 
  One week:

• Send records in the Fix Week file E3SFXWK for a single week
• The types of history that can be sent in FXTYPE field are:
  • G = Regular Demand (Sales)
  • H = Lost Sales
  • F = Promo Sales
• History values will be replaced
• File will be processed manually by calling program E3TFIXWEEK with year and week number corresponding to values in E3SFXWK.

• example: CALL E3TFIXWEEK ('E3T' '2020' '16')

• Super type relationship doesn't have to be broken.

Summary:

	Fixed Week	History Reload ASR All versions
File Name	E3SFXWK	E3SXHST52
What history is needed	A specific week	The entire year
Type of Demand History	Regular Promo Lost	Regular Promo Lost
Action to be taken	Replaced	Replace existing (ONLY)
Supersede impact	Relationships can remain intact	Relationships need to be broken prior and recreated after
Reforecast	Manual	reforecast automatically
Additional Considerations	Requires some technical/operational skills to run	Part of standard interface processing

NOTE: It is recommended to process the history file during the Daily job and not the Weekly, so the Weekly job will not be delayed
NOTE: Do not reload history when in the new E3 year, but still in the old calendar year. The recommendation is to wait until the first history period closes (weekly period or 4 weekly period) of the new calendar year. (not the new E3 year)
NOTE: History reload for SKUs in swap relationships replaces history. If history quantity reloaded for the Replacement SKU does not include the superseded item's history, then the SKUs demand history will not reflect the superseded SKU
NOTE: Blue Yonder recommends not to exceed interfacing 3 years + current year