Getting Started with UD Tables and Foreign-Key Views

I'm reading the docs and scratching my head a bit on how to get
started using a UD table.



Here's what I want to accomplish: We need to implement a
CommercialInvoice as a variant of the PackSlip. My shipping folks would
ideally like to have the tariff code selected based on the destination
country and product group. We can maintain this data in a UD table.



So I bound one Epicor.Mfg.UI.UD02Entry.dll to the menu and I'm
starting to poke around. Basically I want to say "UD02.Key1 is the same
as Country.ISOCode" and "UD02.Key2 is the same as ProdGrup.ProdCode" and
get the lookups on the UD02Entry form for creating new records. My UD
table will look like this:



Company Key1 (CountryCode) Key2 (ProductGroup)
Key3 (TariffCode) Character01(Description)



Then I need to modify Customer Shipment Entry to look this stuff up.
Probably the simplest way to do this would be to assume the data is
there and just have a BPM populate some custom fields in ShipHead or
ShipDtl with the looked up values and warn if the lookups fail and the
user can enter them by hand if they're missing.



This is somewhat simplistic for international customs stuff, but
should meet our needs. I just need to understand how to manipulate
these UD tables, entry forms, and the underlying data relationships.



I'm also wondering about how to manipulate the search option that
comes up in the UD02Entry form as it shows the raw column names (all of
them) in its search results. Can I modify this to use my column names
(from a BAQ) and show my own search fields? This is probably overkill
for this application, but it would be good to know how to do all of
this.



Anyone have an "explainer" that's better than what's in the embedded
docs?



Thanks as always!



-bws



--

Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix

bspolarich@...
<mailto:bspolarich@...> ~ 734-864-5618 ~
www.advancedphotonix.com <http://www.advancedphotonix.com>





[Non-text portions of this message have been removed]