Something I'm not sure about here, it's clear from your example data a Batch can have multiple JobCreationDetail rows, but can a JobCreationDetail row belong to more than one Batch?  If so, then yes you would need the junction table, otherwise could this be simplified by just adding a column and foreign key in the JobCreationDetail table for the BatchID to reverence the Batch each row belongs to.