Sage 100

I am working on a proposal for a prospective customer. We will implement core accounting and job cost. They use job's to track costs incurred on various assets. The projects run for the life of the asset which can be 10 years or greater. There are about 250 assets they are currently tracking. After the first six to nine months, there is very little activity, maybe 5 to 10 expenses per year each. When setting them up, they need full history on all projects; about 10 years of detail. I don't know how many records but let's assume 10,000 to 20,000 rows. I've never loaded history on job cost but I see in VI that I can populate JC Detail History, JC Job history, and JC Transaction History. Has anyone loaded history into JC and are there any ""Gotcha's"" I need to be aware of?

I would think you might be better off running it through Job Posting Entry so it populates those files during an update, just because it's JC.

That's a lot of transactions to post. They hit all kinds of years / months so they would require a lot of batches.

But does that really matter? As long as history transaction detail has the right date, does it matter if the correct period bucket is hit? Maybe on a YTD basis, but period. And even with a year criteria, doesn't the bucket just show PTD, YTD and total job. Maybe import the history up through the current year, then start doing it by period. Your crystal reports will be based on date.....

Jeff, I don't know that it does matter. That's my challenge. What's the potential harm if I load through history. I'm going to try a small sub-set and see what shows up as compared to a second job where I post the transactions as Beth suggests. I was just hoping someone had gone here before to save me the journey.

I think what Beth is saying is that you only have to import once through job posting entry AND it imports things correctly. Since it is JC, the BF rules will not apply and that it is quite easy to become frustrated trying to get these multiple imports correct. OH, how I don't miss those days of imports not working or only half working and hours were wasted trying to figure WTF was not working. Go with what you are comfortable with. I like Beth's idea.

I agree with Beth and Jeff, JC doesn't track history for each period/year separately like the BF modules so that would limit the number of imports. If you can get the info in Job Posting Entry and updated you would be less likely to have an issue later on with data that was imported to the history files separately.