Transaction by Item inquiry shows first ending balance negative?

lpl

New Member
I did run 5.22/23 (closed PO/receipt PO delete/archive) until 01/07/07

I don't know if it's related, but for some reason the first ending balance of a lot of items is negative now? Any ideas where this can come from, and more important: how to solve it?

3.21.2 Transactions by Item Inquiry 26/07/10
┌──────────────────────────────────────────────────────────────────────────────┐
│Date TT Loc Qty Change T Ending Balance Order ID Tran Nbr│
│──────── ──────── ────────────── ─ ────────────── ────────── │

...
│15/07/10 WO-CLOSE 0,0 M 04130023 1310882 3056782│
│15/07/10 RCT-WO 1,0 0,0 04130023 1310882 3056684│
│22/06/10 CST-ADJ 0,0 -1,0 3049763│
│25/05/10 CST-ADJ 0,0 -1,0 3039361│
│20/05/10 RCT-PO 1,0 s MA155165 J1002672 3036830│
│20/04/10 CST-ADJ 0,0 -1,0 3029664│
│12/04/10 CST-ADJ 0,0 -1,0 3025940│

Thanks a lot
 
Is the item Purchased or Manufactured? cause your screen shot shows both RCT-PO & WO-CLOSE. In any case the issue is unrelated as 3.21.2 uses tr_hist.
 

lpl

New Member
It's an M item, but it appears that whe baught the item in the past, and now make it ourselves?
 

lpl

New Member
Here it is:

│ Item Number: L0271618501 Date: 12/04/10
│Performance Da: Trans Type: CST-ADJ
│ Loc: Begin Loc Bal: 0,0
│ Begin Balance: 0,0 Qty Required: 0,0
│ Qty Change: 0,0 Qty Short: 0,0
│ UM: st Last Activity:
│ Order: Sales/Job:
│ Ship Type: Address:
│ Remarks: Not used. Dr :
│Not Used. Cr : Material: 958,59
│ Labor: 457,11727 Burden: 52,3345
│ Price: 1.468,04177 Trans: 3025940
│ Amount: 0,00 Not used. Dr :
│Not Used. Cr : ID:
│ Subcontract: 0,00 GL Date:
│Loc Qty Change: 0,0 User ID: pdr
│ Lot/Serial: Effective: 12/04/10
│ Product Line: 3i14 Salesperson 1:
│ Salesperson 2: Not used. Cr :
│Not used. Dr : Line: 0
│ Ufld1: Ufld2:
│ Currency: EUR Exch Rate: 1,0
│ Rev: Time: 31.453
│ Overhead: 0,00 Site: MCW
│Inventory Stat: Grade:
│ Expire Date: Assay %: 0,00%
│Not used. GL : tr__chr01:
│ tr__chr02: tr__chr03:
│ tr__chr04: tr__chr05:
│ tr__chr06: tr__chr07:
│ tr__chr08: tr__chr09:
│ tr__chr10: tr__chr11:
│ tr__chr12: tr__chr13:
│ tr__chr14: tr__chr15:
│ tr__dte01: tr__dte02:
│ tr__dte03: tr__dte04:
│ tr__dte05: tr__dec01: 0,00
│ tr__dec02: 0,00 tr__dec03: 0,00
│ tr__dec04: 0,00 tr__dec05: 0,00
│ tr__log01: no tr__log02: no
│ Ref: Message Number: 0
│ Program: ppptcp.p Revision: 0
│Reference Site: MCW Reason:
│ Supplier Lot: Supplier Produ:
│ Day Code: Service Part:
│Salesperson[1]: Salesperson[2]:
│Salesperson[3]: Salesperson[4]:
│ FSM Type: tr_upd_isb: no
│Auto Installed: no Work Code:
│Covered Amount: 0,00 Charge Code:
│ Batch: Service Catego:
│ Contract: Contract Type:
│ Service Area: System Product:
│ tr_svc_type: tr_ca_opn_date:
│ Price: 0,00 Engineer Code:
│ Operation: End User:
│Inventory Move: Ship Date:
│Shipper Number: Exch Rate 2: 1,0
│ Rate Type: Sequence: 0
│ Promise Date: Comment: 0
 

lpl

New Member
It appears like the inventory in_mstr (in_qty_oh) changed from 1 to 0 causing the ending balance to be negative (-1 in this case)? And this appears to have happend for a lot of items? What can cause this (probably an automated process/batch, since nobody was around last week or during the weekend)?
 

lpl

New Member
from a tabanalys output, I also a lot of ld_det records "dissapeared" since the week before (from 15.682 to 1648), what could explain the reason why in_mstr has 0 qty's, but what is cleaning the ld_det records?
 
What ver are you on?
Which batch process are you suspecting?
I dont understand the number range you have mentioned for ld_det.
I can dial in & fix it if there is a issue.
 

lpl

New Member
Progress 9.1D, eb2 SP5

The number is the amount of ld_det records that shrinked from 15682 to 1648 records for unknown reason.
In the meanwhile I restored the MFG/PRO database, and will reschedule the dump/load.
 

lpl

New Member
Records don't shrink by themselves of course, but I could not wait any longer to figure out what went wrong, so I just restored the mfg db from last backup, and we are back online (that's why we take backups, don't we?).
Thanks anyway.
 
Top