AnsweredAssumed Answered

Anyone "converted" to the v13 cost type for capitalization?

Question asked by vtleogal2 on May 6, 2014
Latest reply on May 4, 2015 by BradGibson

We have a group that is considering using the new cost type options for SW cap (available as of 13.2).  We are in the test stages of our upgrade.  My initial testing of the conversion jobs and usage look good. I was wondering if anyone else switched over and if there is anything that you discovered that was not documented?  I understand how it works, just curious of the migration from charge codes to using cost type from a business standpoint.

Examples:

1. We have an oracle integration that depends on charge code. Could the business use "both" charge code and cost type? charge codes reserved for the integration and cost type for the OOTB reporting/portlets/portfolio module, etc. (v13.3)  They are aware that they would manually map this with new v13 projects. I don't see any issues, but still double checking.

2. Did you encounter any unexpected issues?

3. Any best practices to consider with using cost type/capitalization %/cost plans?

4. From what I read, they could "convert" the cost plans and task charge codes from v12 at any time correct?

 

Thanks

Lynn

Outcomes