The problem is not that you can not import the data per se, there is no
technical reason why you can not import such data into your Axapta tables as
you have been informed before your purchase - but the problem is rather
managing the complexity and it get it to work correctly when you as you state
wish to import history - which is why it is not recommened. For example, in
your example you are getting errors which are caused by missing records in
the inventtrans table. The inventtranstable needs these records to link to
your saleslines, and at least these records needs to be inserted and linked
correctly before you can begin to do the invoice.
Keep in mind everytime you create a new salesline, a record is
simultaneously inserted in the inventtrans table. In order at least not to
get these errormessages you therefore need to run a script that creates these
inventtrans records with a link to your sales/purchase lines - but, even this
might not be sufficient, because when you work with sales/purchase orders,
you create a lot of transactions in a lot of tables which you got to keep in
mind are created correctly - think of all the relations there. I agree in
principle with Your approach about invoicing the orders after the import
basically is right, because at least that will address creating records in
for example ledger and custtrans, but as you have already noticed here, even
when invoicing certain updates can in principle go wrong, as you can see here
with inventtrans. Then as already mentioned, what about movements, status on
the orders, delivered, picked?, reserved etc, etc, how is this going to be
addressed ?.
Eg. a lot of tables really need to be correctly updated to make this
feasible and also consider the potential problematic implications if you had
a mix of 'imported' orders and orders which have been created 'normally'. I
would not recommed to have this mixture, and definantly not if you have not
closed all your financial years - and even then I am not so sure it is a good
idea, at least due to performance reasons. But, if you still wish to go ahead
with this, perhaps it would be an idea that you create a new company just for
historical transactions and then the user can for example switch to these via
an icon on the desktop which opens up the right company, they can then
inquire for the orders histories through this.
"Allan Wallis" wrote:
> When you refer to sales and purchase history, what do you actually mean?
>
> We have produced a number of solutions for importing history - let me know
> what you want to achieve and I will try and help
>
> "Stranta" wrote:
>
> > When evaluating this software purchase I was told that everything could be
> > imported.
> >
> > After purchase, my vendor claims that sales and purchase history canâ??t be
> > done or is extremely costly if I could even find someone that could do it. I
> > have tried everyway to import my sales and purchase history with no success.
> >
> > Finally, I decided to import all the orders headers and lines (83,000, which
> > took forever) as open orders and invoice them all at the appropriate dates in
> > AX.
> >
> > My problem now is that some will invoice and others will not. I get the
> > error message â??Insufficient inventory transactions with status 'Sales on
> > order', 'Reserved ordered' and 'Reserved physical'.â?.
> >
> > Also, when I look at item master then â??Inquiry/Lotsâ? I donâ??t see all the
> > lotâ??s that should be displayed for an item. But the â??Inquiry/Open sales order
> > lineâ? shows all the records.
> >
> > Is there a class that I can run to correct these issues? Or could someone
> > help me to create one?
> >
> > Thanks,
> > Stranta