Re: Folks --

["Chris Devous" <cdevous@xxxxxxxxxxx>]

On 6 Feb 2003 at 10:22, Tom Jedrzejewicz @ San Pedro wrote:

[snip]

> The previous analyst would manually (with DBU) correct such errors.  I
> wish to avoid such silliness; I am a huge fan of audit trails.  My
> initial response was to advise the user to reverse the erroneous
> transaction by entering it the same but with negative quantity.
> 
> a> Is this a good response?

If one is set up, you may actually have a transaction type that is specific to 
reversal.  
We have a "J" transaction for multiple issue components, which we reverse with 
an 
"I" transaction, established specifically for that purpose.  I may have them 
sdrawkcab, but you get the idea.

In my opinion, the previous analysts behavior was inappropriate.  You are 
absolutely 
dead on about keeping an audit trail.  If your firm is audited they can ding 
you on 
procedures, even to the point of putting a note of "concern" on financial 
statements.  
That would be undesirable.  In most companies, inventory is the largest asset 
and 
should be carefully kept track of.

Also, proper transaction records can help in areas like forecasting, where you 
want to 
be as accurate as possible about the actual movement of inventory.

> 
> b> Is there any way to limit the dates that can be entered into
> inventory transactions short of custom programming?
> 


Depending upon the nature of the screen, it can be fairly easy to insert a date 
validation routine, using a service program in RPG or a CVTDAT in CL, which has 
several monitorable messages you can use to do validation.  We've modified some 
things (like monthend close) to do date validation.  Move the date into another 
field 
with CVTDAT and monitor for a message, and react accordingly.

I've seen you on the other lists, so I know you are familiar with programming, 
but I 
don't know how familiar, so if I'm not being detailed enough just let me know.

--Chris