Field APInvDtl.RcptReceiptDate not available in BAQ

Kinetic ERP
,
1

The APinvDtl form in AP Invoice Tracker shows in field help that the receiptdate field is called RcptReceiptDate and the EpiBinding is APinvDtl.RcptReceiptDate.

However, loading APInvDtl into BAQ Designer, that table does not have a field called RcptReceiptDate.
I tried adding a calculated field and manually entering “APinvDtl.RcptReceiptDate”, but got an “Invalid column name” error.
In Data Dictionary Viewer, the field also does not exist in APinvDtl.

However, in Application Studio for AP Invoice Tracker, under Data Views, the field RcptReceiptDate is listed. As far as I can tell the source for this view is the Data Table APInvDtl.

Why this discrepancy?

image
image1879×756 42.1 KB

2

I don’t know about this field in particular. Sometimes, Epicor has calculated fields on their data views on forms. If that is the case here, then it wouldn’t be in the table and therefore not available via a BAQ.

1 Like
3

Definitely a calculated field

image

For the baq you are going to have to join the invoice details with the receipt details on company, invoice number and invoice line.

2 Likes
4

“Data Views” are exactly that, programmed queries that lookup and pull data into a tracker or entry forms from other tables.

As others have mentioned , DB Field is what tells you if the value is populating directly from the database table.field

5

Wouldn’t you join on either

APInvDtl to RcvDtl > Left Outer
or
APInvHed to RcvHed > Left Outer

You’ve got the date of the whole receipt in your header table and receipt date for each line.

Left outer because you can invoice half of the PO and may not of received everything…

6

This is what I ended up doing, since RcvDtl has InvoiceNum and InvoiceLine fields.

1 Like