Re: Invoicing State

ED_DAY@csiltd.co.uk writes:

>  Al,
>       you might want to check whether the PO's for the resupply-orders have
>  a costed qty = receipted qty & ordered qty, do a PO inquiry. 

I checked that & if there ever was a PO on them they are long gone now.  The 
ITH history only goes back 365 days - not far enough to see what PO activity 
was on the problem orders.  

The "problem orders" I had been struggling with were completed for all items 
as far as anyone could see, and were for activity over a year old that no one 
is interested in anymore.  They were identified through ORD300 when we were 
trying to delete obsolete items, but ORD500 could not get into them to delete 
them because they in "invoicing state."

I do not know the cycle that everyone in the company does to fulfill their 
duties but I suspect we are missing some steps, or have some settings wrong.

Our histories in SYS800 are set at 365 days - I suspect we may want to lower 
some, but I do not know what end-fiscal step is supposed to make old 
completed customer orders go away - none seem plain from their naming, or the 
documentation I looked at so far.  I spent much of weekend on OSG to no avail.

On a hunch, I created a query to list ECH records coded CZ which is my 
understanding of done completed ready for purge.  We have approx 5,000 dating 
back several years.  Only 75 of them are resupply orders.  The following 
chart is type - status - how many of that combination.

1 8 4344
1 E 399
9 8 59
9 E 15
1 4 2
7 1 2
7 8 2
1 F 1
1 7 1
9 4 1

I will probably hit these upside the head with SQL followed by ORD990 but I 
sure would like to know what we are doing wrong to get into this kind of mess 
in the first place.  Obviously our problem is bigger than the resupply orders 
that cannot be maintained because of the state they are in.

We do have intermittent problems with tasks aborted & users in conflict with 
each other, but not on this scale.

On another hunch, I compared the INV documentation of transaction effects 
with INV355 options we now have, then RUNQRY *N ITH F4 selecting one effect 
at a time from the ones not in SSA documentation.  I found an "H" for 
resupply orders, but we are using "IU" intercompany resupply purchase orders 
which updates a PO# but not an RO#.  The "H" which we are not using updates 
RO but not PO.  I suspect we should be using something that updates both at 
the same time, assuming they are sufficiently linked that the receiving clerk 
only needs to know the item #.

Al Macintyre  ©¿©
http://www.cen-elec.com MIS Manager Programmer & Computer Janitor
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com
+---