The workaround for the second problem is to adjust the qty on the
line and save, and then adjust back to the correct qty saving again.
Use the button on the booking details tab to retrieve the records.
While this creates all the expected bookdtl records, it does so as of
the date of when you execute the workaround. So your bookings by
period could be off if the problem didn't get noticed/resolved in the
same period as the problem arose.
Jim Pratt
line and save, and then adjust back to the correct qty saving again.
Use the button on the booking details tab to retrieve the records.
While this creates all the expected bookdtl records, it does so as of
the date of when you execute the workaround. So your bookings by
period could be off if the problem didn't get noticed/resolved in the
same period as the problem arose.
Jim Pratt
--- In vantage@yahoogroups.com, "jmpratt7" <james.pratt@...> wrote:
>
> We experienced both of these problems with the last upgrade we
made.
> We went from 8.00.811B to 8.03.404B. The conversion created
> thousands of extra bookdtl records that negated dollar for dollar
the
> value on many orders. Epicor has supplied a fix for this problem
> that worked in our test account; we are deploying tonight in our
> production account.
>
> There is apparently a fix for the problem of copied orders not
> writing bookdtl records, but I would believe it is only a cleanup
> routine. I would not expect that it will prevent future errors.
The
> support person at Epicor I spoke with indicated there was a fix,
but
> that it had to come from the Minneapolis office.
>
> Jim Pratt
>
> --- In vantage@yahoogroups.com, "vantage" <vantage@> wrote:
> >
> > We used them also until we went to version 400. If you copy a
> sales order
> > to a new order it does not create any BookDtls. Sometimes you
can
> edit the
> > quantity and it will create the back dated logs, but not always.
> Most of
> > the time you will have to delete the line and re enter it to get
> the booking
> > details in. I have had a call in on this since 404 release and
it
> is still
> > in dev available cue.
> >
> >
> >
> > Steve
> >
> >
> >
> > -----Original Message-----
> > From: jstockard990 [mailto:jeff.stockard@]
> > Sent: August 25, 2008 7:42 AM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] 803.405 Book Details
> >
> >
> >
> > Is our company the only one using the BookDtls table to get
> information
> > about Sales order Releases? I have not seen anything on this
topic.
> > When our data was converted to 803.405, thousands of extra Book
> Detail
> > records of releases were added to our database. SCR 52918 has
been
> > assigned to this issue and we have been waiting for over 2 months
> for a
> > fix to this issue. The Sales Releases do not have their own date,
> so
> > we have been using the date from the BookDtls table to get
> information
> > about when a Release was created. Every time a conversion is run,
> we
> > get thousands of more Release details added to our data. Has
anyone
> > found a fix for this problem yet?
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>