Unable to use Periodic as a View frequency in EPMA

Question

Setup: we have recently configured an EPM 11.1.2.1 environment and have migrated over two HFM applications from current production system. Both applications are accessible from within EPM Workspace. I have "Transformed" the classic applications to EPMA models and can view/modify them within Application/Dimension Library.
Issue: When attempting to Validate the consolidation applications within EPMA, I keep getting the following error in the validation report:
Error : Member 'ACTUAL' in dimension 'Scenario' failed validation 'DefaultFreqCantBeNullOrPeriodic' for the following reason(s): Default Frequency cannot be empty or Periodic.
EPMA is not liking that my View dimension has the "Periodic" frequency and having it set on the "Default Frequency" for scenarios. Is there a reason why "Periodic" cannot be used?
Periodic is commonly used and described within HFM documentation and I have yet to see any documentation stating that EPMA cannot use Periodic as the base month frequency.
The other user defined view frequencies that I use are QTD and YTD. They are aligned with quarters and [Year] within the Period dimension.
I'm looking for a solution that does not require a full rebuild of the HFM applications where I would then define the base frequency as "MTD" instead of Periodic.
Any insight or solution is greatly appreciated!!

Answer 1

I will do my best on your comments and may be repetitive (I am also getting tried and am sleepy). I get the impression that the result looks fine in Acrobat OR Reader. I an not sure reader can e-mail the PDF, but if it can the results often depend on the client e-mail setup (typically requiring MAPI to be active. Many folks (even my on some machines) just can't get the e-mail option to work. I would suggest that they simply attach the PDF to an e-mail directly, though I think you are trying to streamline the process. At least that may give a working process as you are trying to find out what is happening.
Howver, you also seem to suggest that the e-mail works (that would mean that the PDF was attached to the e-mail). In that case, my guess is that the e-mail package on the client machine is not set to encode attachments properly. I would suggest that encoding (typically MIME) be activated in the client for all attachments. Outlook has problems in that it often reads a PDF as a text file and does not encode it unless you force the encoding. When that happens the PDF gets corrupted.
If that is not the problem, then it may simply be that the fonts are not in the PDF or present on the receiving systems, causing a messed up font substitution, particularly if something like the MAC PDF viewer is being used rather than Reader.
I may still not understand the problem, but that is my best guess at this point.