Sage 100

Have a client that had a mod which created P2 inventory transaction types. They are no longer using that mod and when we did their upgrade, those P2 transactions were not included in the quantity history calculations - likely because Sage did not recognize the transaction type. Thought I would just export the IM_TransactionHistory file, change the P2 to an accepted transaction type, wipe the file and then re-import. However, when I try to import into IM_TransactionHistory, VI tells me that I cannot import directly into that file. Didn't want to import into transaction entry and update. Anyone know if there is a way to trick VI into letting me import directly into IM_TransactionHistory? This is 5.30.2. Thanks!!

When our customer moved away from P2, they moved to SQL version, so we were able to use SQL Magic, as I call it, to update the table via SQL tools to something that Sage would recognize

Data dictionary hack??

You might be able to use a script to do the SQL magic using business objects. That would probably take a while to process though.

Ah. Transaction Code is part of the primary key. I'm not sure how well a script would work for that.

If you can make the table visible using the data dictionary alteration. Would there be a business object update the other desired summary files?

There was a similar post a few months back. I believe Alnoor Cassim provided the data dictionary hack. It might be just as easy to import into Transaction Entry and Update the batches

If you wanted it to hit the periods properly, would you not have to import by month?

You could ask an MD to create a small program to read the entire file, and replace the P2 with something acceptable & similar, like ""SO"" The MD can handle the fact of it being in the key.

Thanks everyone. We've reached out to the MD to see if they can help write something to replace the P2.

any MD can do it, if there are any issues.....

Any MDs interested in quoting this please contact me at dawnw@capitolcom.com. Thanks!