BeauG
Browser
Posts: 7
|
Good afternoon, Our shipping department has reported a problem when running PI-C, though I have noticed that the issue persists in all menus between PI-A and PI-E. The values for the Year field and the Physical Inventory Number field are defaulting to 2021 and 01, respectively as if there was a frozen inventory that needs attention. When tabbing through past the second field, an error pops up stating 'This is not an existing Physical Inventory number.' Based on my understanding, these ghost cycle counts have plagued us many times, and are usually resolved by ensuring that the BKPIPHYS and BKPIMSTR tables do not have any blank rows (generally via Maintain DB). Unfortunately, this time we have examined these two tables, along with BKICLOC, BKICLOCM, BKICMSTR, BKPIFROZ, BKPILCNT, ISBINLOC, ISBNMSTR and MTICMSTR since they were open in Pervasive when accessing this menu item. We found no blank entries to delete, and so the issue persists. Just to verify behavior, we checked our other company, and have verified that this behavior of defaulting those two fields is not occurring. Our operations director ran PI-A, C, G and H using these defaulted values, in the hopes that doing so would clear out whatever is responsible for setting the default field values. After running this, we did note an appropriate entry with those values in BKPIMSTR. We removed the row, but the issue has unfortunately not gone away. Using lookup in the year field shows an empty table, and any attempt to print or access this inventory number simple returns a "There is no such physical inventory" message. Generally, once this or the original error message are shown, the current PI application becomes unresponsive and shows the error again with any click. The only progress we have made, is that after the operations director attempted to PI-A, C, G and H, we gained access to the Add/Edit/Delete buttons (which previously were not clickable due to the error). Trying to delete resulted in the message "ERROR: BKPIFROZ record not found for this part/location!" At this point we are effectively stuck. Any suggestions? Thank you and best regards, Beau
|