I am glad that my suggested places to look bore you some fruit, but what you are now saying is a puzzlement to me. There can be multiple unusual things happening, such that when we first examine some files in detail, we don't know what is unusual.

Our version not have IPP file so someone else needs to tell you significance of it.

Stuff often goes haywire. If the situation is a single one time inexplicable event, sometimes it is more productive to get the records correct than figure out what caused ti to go haywire.

Various actions update different files.
This can include modifications to BPCS software, and practices.
Also, we can have too many cooks ... other people updating stuff that is not obvious.

I advise NOT to reorganize orders until everything in an order is resolved.

The RMAs are contained in separate members of ECH ECL etc. file structures.

In all probability there are several different ECL lines on the item in question.
There are probably several different SIL billing installments.

Some place in SIL or SIH layout there is a document # which ties back to the ESH ESL shipping detail records. They don't have item or quantity there, but you can see how many shipments occurred.

The extra 46,000 invoiced in ECL that did not get shipped, that could have been via Billing Adjustments.
In our version, BIL500 creates SIL etc. records detailing what got shipped & the flow updates ECL in concert with aggregate SIL, while BIL600 does billing adjustments that usually create a dummy order that can never be seen in ECL.


I have checked the file ITH, ECL and IPP.

There is a additional record of 34000 QTY in the IPP
file.

But the when I see the SIL file
Line qty = 34000
pick qty =-12000


The ECL is saying the total ord qty as 80000. It is
qty shipped is 80000. But the qty invoice(LQTIN) is
126000.


Thanks

> date: Fri, 09 Nov 2007 11:20:03 -0600
> from: Al Mac Wheel <macwheel99@xxxxxxxxxx>
> subject: Re: [BPCS-L] Negative quantiy and amount in
> invoice
>
> I am on 405 CD, have not had that exact problem
> occur, but have had
> multiple problems with negatives, and math not
> coming out with logical
> expectations.
>
> There are many places in BPCS where a person can
> enter a negative # on
> purpose, or by accident, which can drive unexpected
> other places negative.
>
> You might check your company's policies for how you
> proceed when trying to
> ship something which has not yet been reported as
> having been made
> (transaction float).
>
> You might check the ITH "B" transaction which is
> generated by the actual
> shipping.
> That should be a negative 34000 because it is a
> deduction from inventory.
>
> You might check the ECL customer order item line
> detail.
> There are fields for quantity originally ordered,
> picked for shipping,
> shipped, invoiced.
>
> You might check the work files and job step tracking
> associated with the
> shipping and billing, to see if anyone had a crash
> that was not properly
> resolved.
>
> Al Mac
> In the midst of changing my e-mail address
>
>
> > Hi ,
> >
> > We are running bpcsv6.
> >
> > we got a case where we are getting the negative
> >invoice quantity and so the negative invoice
> amount.
> >But the inventory is fine with positive quantity,
> only
> >during the invoice print in BBH file it is
> becooming
> >negative quqantity.It is partial shipment which is
> >already shipped 46000 out of total 80000. The
> remaning
> >34000 while printing has become -12000 instead of
> >34000.
> >
> > Is it possible due to any error it will happen
> in
> >the pick release or confirmation data error it will
> be
> >negative.
> >
> >
> > If anybody experienced the similar error please
> let
> >me know.
> >
> >Regards,



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].