Re: Missing Inventory Transactions

[Ata510@xxxxxxx]

In a message dated 9/28/99 8:07:38 PM Central Daylight Time, sueu@alltel.net 
writes:

> 
>  For those of you who may be experiencing a similar problem:
>  
>  Client is on BPCS version 6.02 (plf) AS/400 V4R2 and using DCServ.  We are 
>  using a user defined transaction to signal allocation of inventory from 
>  DCServ to BPCS.  When traffic is heavy between the server and the 400, we 
>  occasionally would have what appeared to be missing transactions filter 
>  through.
>  
>  For example, an adjustment transaction is sent through and its 
accompanying 
>  allocation transaction will follow within seconds (remember, 
user-defined). 
>   ORD720 grabs the YCI (without a lock), updates other inventory files for 
>  that allocation and then comes back and updates the YCI.  In the meantime, 
>  the adjustment transaction has processed, but the YCI's updated quantity 
>  fields are overlaid by ORD720.  This is proven out by using the 
transaction 
>  log on the DCServ engine.
>  
>  Now, I know that is a wordy explanation, but you have to understand how 
>  AS/Set works to see the problem.  The fields used to calculate on-hand are 
>  used in ORD720.  The file is read without a lock, calculations occur, and 
>  then the YCI is updated.  Internally, AS/Set reacquires the record and 
then 
>  compares the values in the fields from the original read with those from 
>  second.  If any of those are different (in this case adjustments), the 
>  fields from the original read are moved to record and the file is updated. 
>   Hence, wiping out the adjustment.
>  
>  This is a timing issue and we have spent a lot of time researching (and 
>  fixing) the errors being created.  I just wanted to save someone else the 
>  aggravation.  And yes, we will be reporting the issue to SSA.
As an FYI to anyone else using it, DCServ uses database triggers to affect 
updates to the outside application. Whenever a file is changed, it triggers 
the DCServ update to occur, regardless of BPCS processing which is occuring. 
It also happens to causes the July cumulative apply to crash on 6.0.04, so be 
sure to remove triggers before attempting the upgrade of BPCS to the July 
cume. 

+---
| 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
+---