We use a UD table to store the vebiage of various requirements that could be placed upon components. Key1 becomes the code, ShortChar01 is the 'title' of the requirement and Character01 is the actual text.
Part Entry has been customized to store the codes in the ShortChar fields. These fields have been added to PartTracker, Receipt Entry, and where ever else they need to be displayed. Mouse over one of the fields and the entire text of the code is displayed like a tooltip.
PO Entry has been customized to display the info in a textbox, but the codes are concatenated into a tab delimited form. A BPM takes care of storing the codes in a Character field in the PODetail record.
PO Print crystal form collects the codes and prints a page containing the verbiage for each PO that has codes attached to a part.
This way the actual text is only entered once, and the code is used in the various places it needs to be attached - I am from the old school when a 400Mb disk and 1024K of memory ran 30 terminals and an entire organization....... :o)
So I think what you want to do is possible.
Part Entry has been customized to store the codes in the ShortChar fields. These fields have been added to PartTracker, Receipt Entry, and where ever else they need to be displayed. Mouse over one of the fields and the entire text of the code is displayed like a tooltip.
PO Entry has been customized to display the info in a textbox, but the codes are concatenated into a tab delimited form. A BPM takes care of storing the codes in a Character field in the PODetail record.
PO Print crystal form collects the codes and prints a page containing the verbiage for each PO that has codes attached to a part.
This way the actual text is only entered once, and the code is used in the various places it needs to be attached - I am from the old school when a 400Mb disk and 1024K of memory ran 30 terminals and an entire organization....... :o)
So I think what you want to do is possible.
--- In vantage@yahoogroups.com, Steven Gotschall <sgotschall@...> wrote:
>
> What about using eight of the ShortChar and eight of the Character user defined fields in the Part Master to store this information for each part? You could then bypass the whole FKV thing, which I never have gotten to work right with UD tables. Doing a FKV of the Part table in OE is easy and works great, I do that myself. Should be that way out of the can IMHO.
>
> Another option would be to link your UD table to the Matenance form via an embedded dashboard. I do this on the Customer Maintenance screen for Tax Exempt ID numbers which we need to have by state for all our customers. The OE part of this may be a little tricky.
>
>
>
> ________________________________
> From: nancy.leifheit <nleifheit@...>
> To: vantage@yahoogroups.com
> Sent: Fri, November 20, 2009 1:10:19 PM
> Subject: [Vantage] Need to Add a UD table to my part master using FKV or is there another way.
>
> ÂÂ
> I am trying to add a UD table (Material certs table contains Key1=Seq#,
> shortCahr01 = ID and Character02 = Description and shortChar02= Type)to my part master.
>
> These are material certs I need to attach to my part master and a part could contain up to 8 different cert based on the final product makeup.
> My UD table doesn't have any "part number" reference. Once I get them attached to the part master I need to be able to bring them into my order detail table - our customers need certs to bring with packing slips. Well select the appropriate cert during OE based on the customers requirements.
>
> I have looked at:
> 4163ESC - How to use FKV in UD table to bring in Part table -> wrong direction.
>
> I need to be in my part table and bring in the UD table information. Then I need to be able to select this information in OE.
>
> Any suggestions?
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>