GPv6-Inv Batch-Check Links appears in a blank batch comment 1

[markajem]

This is a first for us that we know of. When we call up Inventory Batch ID window we see the non=posted batches listed but also see a batch that has no batch ID. If we expand the batch to see detail under the column comments we see "Check Links". I tried searching for this in the help etc but don't see any reference to this. Anyone see this before.

Thanks

 

[jymm]

we had something similar happen a while back with another module

essentially what happens is that if you run the check links module and it determines that a parent record is missing for an orphaned child record (in our case it was a payroll record with a missing person) Check LInks creates a record with the needed key, BUT with 'Check Links' as the description/name. Took us some digging to find out who was re-inserted, but that is the problem - this help?

 

[markajem]

Thank you, that was very helpful and solved the mystery. What utility can we run to recoup the parent record?

 

[jymm]

ouch - that one is tougher --- I do not know of a good way to do that without (in my case I am on sql) doing a db restore to another place (in other words not over the prod data) and then looking through the database to find that key. of course this would mean that you need to have an idea of when the record disappeared and the only way to know that is to look at the dates on the batch.

 

[markajem]

Thanks for your reply again. We are on SQL also. I will have to discuss it with our IT Dir and see what he thinks and also suggest your method. Unfortunately we do not have any type of tech support for GPlains so that makes it even more difficult but we are both well versed in the database and both have programming backgrounds so that will also help.

We just had the same thing happen just a day before this one with our WMSystem. But that company is aware of the problem and is preparring a script for us to run periodically if it happens again.

Thanks again.

 

[markajem]

jymm
You mention specifically the word "KEY". What do you mean by key.
Thanks

 

[jymm]

we do not have inventory module here, so I am not going to be able to tell you what the key field is - let me give you an example though of our problem from Payroll.

In the UPR30300 table (pay history essentially) there is a field that is EMPLOYID (the key for the parent). In our situation there were records that were in the UPR30300 that were (unknown to the DBA - aka ME) not in the 'parent' table (UPR00100). The check links created the UPR00100 segment/row with the lastname of CHECKLINKS. SO --- I went back in the archives (actually it was easier since there were some printed reports with the employid & the lastname) and then went into the card and updated the LASTNAME to the employeee that had left and was deleted.

So - I think it is similar with you - there is a batch that had some detail 'below' it (if you can envision a hirearchical db tree). GP SHOULD either not allow you to delete the 'base' record without deleting the detail OR should delete the detail as well (my opinion) - BUT - that is what happens in some modules (my experience).

This help?

 

[markajem]

jymm
sorry for the delay in my "Thanks" to your post. Took a few days off.
Yes, your explanation is basically what we had thought after your first post but you did clarify the term "KEY". We just now were informed we had the same thing happen in the Inventory Master file. We have an item with a description of Added by check link. But seems strange that it would be created in the master file. This would mean that the item (which was non existant til GP created it) was used in another table and tried to cross ref to the master, did not find it so check link created it.

Thanks again, you have been very helpfull.

 

[jymm]

I often wish that there was a utility in GP that would clean out (delete) the orphans instead of re-creating the parent/root record.

darn accountants anyway...

are you running check links over & over or is this from a previous run? I do not run Check Links unless there is a problem - BUT - run a number of utilities against the SQL db to ensure integrity/shrinkage... more curious than anything.