Selecting event year when importing a PCE

I am running a tourism spending analysis. I created one activity to include lodging,gasoline, restaurants, etc. The spending data are in 2009 dollars, and I set all the event years to 2009. I imported NIPA1111 as an activity for expenditures on groceries. The event year for each of the sectors in NIPA1111 is 2007. My spending data for groceries is in 2009 dollars. I would like to run both of these activities in one scenario. I plan to report the results in 2014 dollars. What adjustments, if any, do I need to make to reconcile my 2009 dollars with the 2007 event years in the NIPA1111 PCE? Thank you for your time.
Was this post helpful?
0 out of 0 found this helpful

Comments

1 comment

  • Hi James. What adjustments, if any, do I need to make to reconcile my 2009 dollars with the 2007 event years in the NIPA1111 PCE? Thank you for your time. As regards to the Event Year, you will want the Event Year to reflect the year of your dollar's value (which sounds like 2004). You can then use the Dollar Year for View field to adjust the results to which ever dollar year you wish to see the results in. Deflators are applied before the value is applied to the multipliers by simply dividing the deflator value by the industry sales value. The same process adjusts the Dollar Year for View. You can view this with the Final Demand Preview Screen. In regards to what adjustments, if any, should you make to reconcile my 2009 dollars with the 2007 event years in the NIPA1111 PCE? Well, first your 2007 PCEs, we presume you're just using a coefficient breakdown of spending between these categories that is based on 2007 data. If so, then the only concern would be if that breakdown is no longer applicable. Once the values are converted to relative coefficients, the fact that the original data was in 2007 dollars should not affect your use of deflators (assuming again that your actual expenditure values are from 2009). Please let us know if this does not address your question or if you have additional concerns.
    0

Please sign in to leave a comment.