Need PO Line Due Date feild for report

Yahoo Archive
1
Lynn,



I'm using ODBC to add it to a sub report.



I'm looking for PO Line Due Date not Sales Order Due Date...



Norman



[Non-text portions of this message have been removed]
2
Any know how I can get PO Line Due date for a crystal report? It shows up
in the system but it's a calculated field, so I can't use it in a report?
Any help would be great.



Thanks,



Norman Hutchins

Network Administrator

Howell Laboratories, Inc.



[Non-text portions of this message have been removed]
3
Are you writing a BAQ report or are you using a Vantage Form with
Report Data Definitions or are you using ODBC?

And is it the OrderDtl table from which you are pulling information?

If you are using Report Data Definitions for a Vantage Form, then you
can definitely add any calculated field to your Crystal Report.

If you are writing a BAQ report, then use one of 2 date fields in the
OrderDtl table: OrderDtl.NeedByDate or OrderDtl.RequestDate (The
NeedByDate is the date it needs to arrive at the customer's dock; the
RequestDate is the date on which you need to ship it from your dock.)


--- In vantage@yahoogroups.com, "Norman Hutchins" <nhutchins@...>
wrote:
>
> Any know how I can get PO Line Due date for a crystal report? It
shows up
> in the system but it's a calculated field, so I can't use it in a
report?
> Any help would be great.
>
>
>
> Thanks,
>
>
>
> Norman Hutchins
>
> Network Administrator
>
> Howell Laboratories, Inc.
>
>
>
> [Non-text portions of this message have been removed]
>
4
What about linking in the PORel table and using the DueDate field
from that? I think that's where the POLine date comes from.

Nigel.

--- In vantage@yahoogroups.com, "Norman Hutchins" <nhutchins@...>
wrote:
>
> Any know how I can get PO Line Due date for a crystal report? It
shows up
> in the system but it's a calculated field, so I can't use it in a
report?
> Any help would be great.
>
>
>
> Thanks,
>
>
>
> Norman Hutchins
>
> Network Administrator
>
> Howell Laboratories, Inc.
>
>
>
> [Non-text portions of this message have been removed]
>