×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
ECL and SIL reflect each other. Some times there will be two SIL if
you make two shipments off the same order.
RAR is the invoice total. The Seq# only tracks what order payments "RP"
records and Credits "RC" or "RD". The RI Invoice record is the first
deq and has the remaining due.
Do you use cross reference items? Then check ECL Lprod vs LItem.
I don't think ECH gets purged.
Roger Henady
Thorco Industries
(417) 682-1340
From:
Al Mac Wheel <macwheel99@xxxxxxxxxx>
To:
"BPCS ERP Discussion List" <bpcs-l@xxxxxxxxxxxx>
Date:
05/30/2008 10:33 AM
Subject:
[BPCS-L] Line #s Order Invoice
I'm working on a modification in 405 CD which involves a report generated
off of invoices hitting RAR in which I need to get at line #s in SIL
invoice and original ECL order.
Am I correct that SIL.ILSEQ points at ECL.LLINE?
What does RAR.RSEQ point at?
Regardless of the # of lines on SIL invoice, does the whole invoice end up
being a single record of RAR?
As orders get satisfied, the order lines & orders get coded complete,
ready
to purge.
When does this purge normally occur ... during end fiscal month, or as
soon
as an order has been completely filled shipped billed?
Orders have a description which defaults to item description from item
master, but for some customers, we substitute info, specific to the line
#s
of the customer purchase order, which shows up on billing invoice, and I
need to go back to the ECL to access in later reports, so I'm interested
in
how long the customer order remains in the system.
-
Al Mac
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.