Re: Folks --

[Cfgwizard@xxxxxxx]

Ted,

A.  You are correct. The preferred solution is a reversal. But there is a 
severe restriction on reversals of backflushed components prior to version 8. 
The M transaction will probably have to be reversed with an M or an R for the 
finished goods item and an I or CI for each backflushed component issue. This 
option may be available if the order is still open and and hasn't been purged 
in the monthend process. If that is the case in your example, sorry. The 
reversal should attempt to return the components to the original warehouse,  
location, lot number, and container. Caution - may have to reactivate the lot 
or container first. You also need to ensure that the reversal 
transaction/reasoncode combo hits the same GL account and period as the 
original. Also realize the allocation has been consumed and may have to be 
manually re-established depending on your M trans procedure. 
B.  I'm not aware of any standard means or option to protect the default 
transaction date. Agree with Mac - get them out of the habit. One other 
possibility exists in some of the data collection solutions discussed here 
recently. I know that some if not all allow scripting that eliminates 
visibility/access to fields you declare off limits. In most cases you can 
fill the contents with a constant of your choice such as today's date.

Good Luck
Larry
630.561.0062




In a message dated 2/6/2003 12:35:01 PM Central Standard Time, 
TJedrzejewicz@contessa.com writes:


> X-INFO: INVALID TO LINE
> Folks --
> 
> We are BPCS 4.0.03 with customer Y2K mods.  The email below was sent to
> me asking for help.
> 
> ==User error email ==============
> As you know, Lupe is currently training me in the process of
> "reporting" shop orders.  This transaction is under "INV", "1" Inventory
> transactions, "M" Multiple Issue with Receipt. 
> 
> When I reported this SO #19377 (JC Pasta Ole), I entered the incorrect
> date of "10/29/03" when it actually should be "01/29/03". Please make
> the necessary transactions to reflect the correct date.  
> ==END user email ==============
> 
> 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?
> 
> b> Is there any way to limit the dates that can be entered into
> inventory transactions short of custom programming?
> 
> Thanks for any advise you may have.
> _______________________________________________