Has anyone been able to add the PrimBin to both the Materials and Primary part on a Job Router. The issue is you cannot make a dual relationship to the same table in the RDD. We have a need to have the BIN for the materials and the upper-level part. Just curious if anyone has found a solution to this.
1 Like
Can you get to it through the linked tables of the existing data sources?
I do not see a way to get the primary part to the PlantWhse where the PrimBin is stored. I currently have the relationship going from the JobMtl to PlantWhse. Maybe that is the incorrect relationship to get the linked table to show up. Thoughts?
I don’t know if it’s a great option, but you could set the PlantWhse relationship to be Company to Company and then you’d return all your PlantWhse records. Then you could use the query in the RDL to join the same table twice, once from JobHead and the second time from JobMtl. Not sure how well that performs. Or you could write the Job part Primary bin to a UserChar field on JobHead. Those are already available and you could write that using a BPM maybe even when the Job Traveler is printed. Just a couple of ideas.
Wouldn’t it make sense if you could add the same table twice and just alias it differently like you can in SQL? It’s like they gave you the option to name your data source but then still don’t let you use the same table twice. Seems silly to me.
1 Like
Yes, totally agree. I will explore those couple of options. If you have any other thoughts, please let me know. I appreciate your insight.
Some other questions we might want to consider:
What is the purpose of identifying the primary bin on the Job Traveler? I can guess that the material primary bin is shown to help in locating the materials needed for the job. But why the job part primary bin?
Could the bin you’re looking to identify actually be identified in a different way? For instance, does the resource that will be used to complete the job have an output bin that might match what you’re looking for?
Along those lines, the PrimBin is not necessarily where the part is actually being held in inventory. It could be received, transferred, etc. into any bin. Whenever I reference bin information on a form, I pull in the PartBin table. This is where inventory is ACTUALLY on hand.
1 Like
We have the primary bin on our job traveler and I tied the job head to the part plant (both part and plant are on the job head) and then part plant to plant warehouse (Company to Company, Plant to Plant, PartNum to PartNum, and PrimWhse to WarehouseCode) but it’s pretty easy for us because we only have one warehouse per plant.
As for why we have it on the job traveler I believe it’s to make it easier to put it in the primary bin once the job is completed and not a random bin. I’ll be honest though I just completed the request and didn’t dig into it as much as I likely should have.
1 Like
That works fine, unless you want to add Bins to the Materials also. The previous idea of adding it to the company may work. Still testing out how it performs etc.