BAQ for unposted costing journals

Hi everyone,

We recently went live and realized we had several unposted journals hung up after the Capture routine. I have since fixed the primary cause. I now realize the Inventory/WIP Reconcilation is a great start but I’m hoping to create a summary BAQ to put on a Dashboard so that our Controller will be alerted that there is a problem. Can any one point me to the correct table? Any other advice? It appears that GLJrnDtl only shows posted journals unless I’m missing something.

Thanks in advance!

Go into the Review Journal and select a primary field. Then use the Field Help to show details about the field. There will be a table/pane with technical information. This will show the table and field name.

This might not work in the Kinetic interface. If not, use the modern shell interface just to find the field details.

Thanks - that is helpful; the table is RvJrnTr. However that table doesn’t show unposted activity journals. Journals that will eventually post when the Capture runs. That is the activity I am most interested in. In other words, I’m interested in the source of the data on the Inventory/WIP Reconcilation Report when you select “Only Unposted to the GL”

@nanvdand I believe those are in PartTran with the PostedToGL flag as false and GLTrans flag as true.
You may have to also use the COSPostingReqd flag.

1 Like

Thanks @gpayne ! These look like the place to start. Appreciate the guidance.

Note that if you want the related accounts, you’ll have to use table TranGLC. It’s one of those tables that have the key fields that vary in their use based on the RelatedTable field.

For example, a PUR-STK parttran record gets its accounts to use from TranGLC where:
TranGLC.RelatedTable = ‘RcvDtl’
TranGLC.Key1 = PONum
TranGLC.Key2 = POLine
TranGLC.Key3 = PORelNum

You’ll get two(or more) records for each parttran record that makes GL transactions. Most often one for the debit account and one for the credit account.


The above is from memory, so some of the field or table names might not be exactly right.

1 Like

Thank you @ckrusen - great guidance and I understand the direction. This is awesome.

The data dictionary menu item is also your friend when working these tables that involve these Key and Related columns.

1 Like