In a BAQ the option to show Connected Only Tables for PORel only lists the JobAsmbl table as a direct connector to a job, even though in Purchase Order Entry the operation sequence is filled out when linked to a job. However, the Operation sequence field is does exist and but is called JobSeq in the PORel table. Connecting the PORel.JobSeq field to the JobOper.OpSeq works great and returns same number of rows in my tests. If there is an issue im not aware of by linking these two tables together then let me know, otherwise this is just notes for a future me.
1 Like
There’s nothing wrong with using JobOper.
BUT… depending on what you’re doing… you may want to consider JobOpDtl.
1 Like
Yes that is the correct relationship. You should also filter the PORel table to JobSeqType=“S” or you could run into issues with pulling in purchase direct materials.
3 Likes
This.
2 Likes