Open Forum

Expand all | Collapse all

Check Links & Reconcile Created Batches

  • 1.  Check Links & Reconcile Created Batches

    Posted Jan 12, 2019 06:15 PM
    Hi, all. I'm going through Check Links & Reconcile for the first time in our environment and had a question about the batches these processes create. If we're satisfied that all of the transactions in the batches created have already been accounted for, is it okay to delete the batches or do they need to be posted. My concern is that if we don't post them, it cancels out the what all was just done by CL & Reconcile. Also, the process created a few batches that have blank batch numbers and can't be deleted via GP. If these are removed via SQL Server, do we need to do any additional CL or Reconcile series again. I hope this makes sense. Please let me know if I haven't provided enough info & thanks for all of the help.

    Jon Godwin
    Database Administrator
    Boulder CO

  • 2.  RE: Check Links & Reconcile Created Batches

    Posted Jan 13, 2019 02:49 PM
    Hi Jon,
    the fact a batch has been created does not mean it has something inside to be posted.

    These batches are probably created because of open transactions not necessarily to be posted, such as quotes or orders.  Probably old stuff.
    So probably these batches can be deleted.  A reconcile is good to execute since it fixes, for most of it, summary tables and recalculate summary numbers.  But a Checklinks should be executed only if really we are looking to recreate information that has only partially be created because of a bug.  After lots of history, it will probably do more unrelevant records creation than it will help.

    It may also create header records for orphans detail records you may have because of history bugs, that you probably just recreated over the time...

    Luc St-Yves
    Business Analyst
    Co-Leader GPUG - Montreal chapter
    Humanware Technologies
    Drummondville QC

  • 3.  RE: Check Links & Reconcile Created Batches

    Posted Jan 14, 2019 08:24 AM
    Hi @Jon Godwin

    @Luc St-Yves has a point.

    If CheckLinks has created a batch for you then at some point you have had data corruption - you have orphaned records in your tables - most likely in the Key Files for each module or you have orphaned detail lines.  Usually happens if someone manually deletes transactions from tables but does not delete them from every table they exist in, so GP recreates them at CheckLinks.

    If you have verified that the transactions do in fact exist correctly in GP then you can delete these, but I would note the transaction numbers and search the database for where they are so you can fix the database by deleting or removing the orphans.

    Otherwise, these transactions will haunt you every time you run CheckLinks.  There's also the possibility that orphaned records also impact GP's native processing so probably a good idea to clean them up.

    Kindest Regards,
    Jo deRuiter , MCP, DCP
    "That GP Red Head"
    GPUG Academy Instructor
    Dynamics GP Credentialing Council-Vice Chair
    770-906-4504 (Cell)


If you've found this thread useful, dive deeper into User Group community content by role