Rick,
Thanks for responding, Rick. I understand what you are saying, I'll talk it
over with our controller.
Our situation is this: We do not have parts in our part master. We have
some, but very few. None of the parts have a G/L account associated with
them in the part master. In our business, nearly every part we buy is
unique to a job, and we depend primarily on the purchaser selecting the
correct part class to direct the part to the correct G/L account with the
interface turned off. However, many of the part classes could be bought to
a job, or as an expense for one of the 3 departments. To get this to hit
the correct account, in some cases we would need 4 part classes for each
type of part, ex: Mold Components to a job (hitting Wip), Mold Components
for the Repair Department (hitting Repair Dept. Expense), Mold Components
for the Prototype Department (hitting Prototype Dept. Expense), Mold
Components for the Production Department (hitting Production Dept. Expense).
We were hoping that by turning on the interface, we could at least eliminate
the job part classes.
Any advice anybody may have would be appreciated...
Sarah
-------------------------------------------
You can turn the interface on and not post as you stated. However, I
believe that by not posting you will get an ever increasing large list of
exceptions when running the capture. Vantage will show an exception for
every transaction that has not been posted for dates prior to the dates the
capture in run for. You can ignore these transactions, but it could also
mean that it will take an increasingly longer time to run the capture. This
could get kinda ugly.
I am curious, however, as to why your G/L accounts are defined as they are.
Why would parts that are purchased for jobs be mapped to accounts other than
WIP either in the part or part class? Additionally, I always suggest that
you try to avoid using the G/L account in the part and rely on the part
class instead. This makes it much easier should a G/L mapping change need
to be made. It is much easier to change the G/L account on a few part
classes verses 1000's of parts.
Thanks for responding, Rick. I understand what you are saying, I'll talk it
over with our controller.
Our situation is this: We do not have parts in our part master. We have
some, but very few. None of the parts have a G/L account associated with
them in the part master. In our business, nearly every part we buy is
unique to a job, and we depend primarily on the purchaser selecting the
correct part class to direct the part to the correct G/L account with the
interface turned off. However, many of the part classes could be bought to
a job, or as an expense for one of the 3 departments. To get this to hit
the correct account, in some cases we would need 4 part classes for each
type of part, ex: Mold Components to a job (hitting Wip), Mold Components
for the Repair Department (hitting Repair Dept. Expense), Mold Components
for the Prototype Department (hitting Prototype Dept. Expense), Mold
Components for the Production Department (hitting Production Dept. Expense).
We were hoping that by turning on the interface, we could at least eliminate
the job part classes.
Any advice anybody may have would be appreciated...
Sarah
-------------------------------------------
You can turn the interface on and not post as you stated. However, I
believe that by not posting you will get an ever increasing large list of
exceptions when running the capture. Vantage will show an exception for
every transaction that has not been posted for dates prior to the dates the
capture in run for. You can ignore these transactions, but it could also
mean that it will take an increasingly longer time to run the capture. This
could get kinda ugly.
I am curious, however, as to why your G/L accounts are defined as they are.
Why would parts that are purchased for jobs be mapped to accounts other than
WIP either in the part or part class? Additionally, I always suggest that
you try to avoid using the G/L account in the part and rely on the part
class instead. This makes it much easier should a G/L mapping change need
to be made. It is much easier to change the G/L account on a few part
classes verses 1000's of parts.