UDCs

alan_watt

Member
Is there any way to set up UDCs by Company?

One of my customers has several companies in the same group - all using
OneWorld. Whilst most of the UDCs will apply group-wide, some need to be
different for each company. I notice that there's a field in F0004 called
UDCO. It doesn't appear to be used in the normal UDC Revisions applications,
so what's it used for? i.e. can I steal it to use as a filter, by tying a
company number to a UDCO letter.

The alternative (which I don't like) is to replicate the UDC functionality
in some F55 tables!!

Cheers...

... Alan =8^)
__________________________________
Alan Watt
Jade Enterprise Solutions Ltd.
"Making Good Ideas Happen"
__________________________________
Tel/Fax: +44 (0)161 428 1288
Mobile: +44 (0)7970 255073
Email: [email protected]
URL: http://www.jade.tm
__________________________________
 
Alan,
If your users are grouped by companies as OW users then create different data sources for the different sets of UDCs. Map the tables for the groups to the appropriate data source in OCM.
Hope, could work for you.
Zoltán

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
 
Alan, Zoltan,

Great idea, of course mapping different tables will mean that you have to
maintain a COMPLETE set of UDCs for each group of users not just the
different codes.

How many UDCs are you talking about?

Could you format them differently for each company for instance 'A*' is for
company A and 'B*' is for company B. Or, maybe place a prefix in the
description. Then you could use row security. Not sure how much row security
you would need though.

Are both companies in the same database? If they are, will they be able to
see each others data where these UDCs are used? If this is the case then
separate tables might raise issues when one company uses the others data.

David Helsley
[email protected]
http://www.guru.com/profile/view.jhtml?guruId=942464
 
Can't you have company a use all the codes that start with an a and company b use all
the codes that start with a b?

Marcel

alan watt wrote:

> Is there any way to set up UDCs by Company?
>
> One of my customers has several companies in the same group - all using
> OneWorld. Whilst most of the UDCs will apply group-wide, some need to be
> different for each company. I notice that there's a field in F0004 called
> UDCO. It doesn't appear to be used in the normal UDC Revisions applications,
> so what's it used for? i.e. can I steal it to use as a filter, by tying a
> company number to a UDCO letter.
>
> The alternative (which I don't like) is to replicate the UDC functionality
> in some F55 tables!!
>
> Cheers...
>
> ... Alan =8^)
> __________________________________
> Alan Watt
> Jade Enterprise Solutions Ltd.
> "Making Good Ideas Happen"
> __________________________________
> Tel/Fax: +44 (0)161 428 1288
> Mobile: +44 (0)7970 255073
> Email: [email protected]
> URL: http://www.jade.tm
> __________________________________
>
> --------------------------
> To view this thread, visit the JDEList forum at:
> http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OWDEV&Number=2380
> *************************************************************
> This is the JDEList One World / XE Developers Mailing List.
> Archives and information on how to SUBSCRIBE, and
> UNSUBSCRIBE can be found at http://www.JDELIST.com
> *************************************************************
 
Alan,
I agree with Zoltán (he's sitting next to me so i'd better :)) but have an
alternative option (programming) You have to set up UDCs disjunct in code so
the different company codes don't collide and override the search on the
forms where it is needed. It is only applicable if you have only a few UDCs
you want to use by company. You set up all the codes in the original UDC
table and replicate them in an F55* table (I know it is just what you wanted
to avoid but it's not too difficult) extended with a company code (filtered
on the form with the user's company). On the forms where it is needed you
either override the search form or use Suppress Default Visual Assist system
function. This way the codes are validated according to the original UDC
table and are searched by the company-dependent forms. I made a similar
modification when hierarchic search of UDC's was needed.
Regards:
Gergely Pongrácz
Synergon, Hungary

> ----------
> From: Zoltan_Gyimesi[SMTP:[email protected]]
> Reply To: [email protected]
> Sent: Friday, December 08, 2000 9:10 PM
> To: [email protected]
> Subject: Re: UDCs ~~2380:2391
>
> Alan,
> If your users are grouped by companies as OW users then create different
> data sources for the different sets of UDCs. Map the tables for the groups
> to the appropriate data source in OCM.
> Hope, could work for you.
> Zoltán
>
> B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
> (working with B7321, B7331, XE too)
> --------------------------
> Visit the forum to view this thread at:
> http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OWDEV&Num
> ber=2391
> *************************************************************
> This is the JDEList One World / XE Developers Mailing List.
> Archives and information on how to SUBSCRIBE, and
> UNSUBSCRIBE can be found at http://www.JDELIST.com
> *************************************************************
>
 
Re: RE: UDCs

Here is a bit addition to Gergely's idea:
The solution won't prevent the user to enter the UDC manually instead of using visual assist, so won't prevent to enter a UDC of other company.
Resolutions:
1.) You have to force somehow using visual assist for the entry (currently a I haven't idea, how you can do it)
2.) You have to override the Edit Rule of the UDC field on the Form with FDA.
Zoltán

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
 
Alan,

The UDCO field in F0004 and F0005 is a character (1 char) field not like company (CO) which is 5 char long string field.
You can know more abaout it's usage if you examine it in the data dictionary:

UDCO's long name is: UdcOwnerShipflag and it's glossary states: "This flag indicates whether this information is required for J.D. Edwards
software. If it is "J", the code MUST exist and will be loaded by JDE during
PTFs and re-installs."

I don't think that you can use it for company.
Zoltán

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
 
Alan,
If you have many company dependent UDCs and many affected field on many forms then here is an alternative and general solution. I describe it briefly.

1.) Create a custom table (e.g. F55xxyyyy) as a tag file. Include the the fields of the primary key of the UDC table, the company and as many field as you want (e.g. audit informations or a flag to determine that is it a common UDC or a company dependent one, etc.).
2.) Modify the UDC applications: the visual assist for UDC and the UDC Revision to handle the tag table (filtering, applying company data in the tag table).
3.) Fill your tag file for the existing UDCs with the appropriate informations (one time initialization).

Now, the visual assist will bring up only the UDCs of the company (and the common if you accomplished to handle it).
Maybe, it's enough for you.
If you want a strict validation (editing) on the entered information then you have to modify the UDC validation accordingly which is called when a data item's Edit Rule is "UDC". I suppose, it is a BSFN (instead of a built in function into the engine) but currently I don't know which is it amoung the many "Verify UDC...", Validate UDC..." BSFNS.

This solution can work for UDC Types and UDC Codes too.

LIMITATION:
Different companies can not use the same Type and/or Code with different attributes and/or meanings!

Please, let us know if it could work for you.
Zoltán



B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
 
Alan,

Do you have more than one language in your installation? If not, you may be able to take advantage of the language override functionality. In the UDC application, there is a row exit to allow you to enter alternate descriptions based on a language flag.

There are a couple of scenarios here:

1 - Instead of company A and company B using different UDC codes, they use the same code with two different descriptions (meanings). For example, if you wanted search type X to mean ex-employee for company A and ex-customer for company B. Unfortunately, this also means that there can be no functionality based on the UDC value since it has different meanings...unless you are going to program according to company as well.

If your installation has only English installed, I believe you can set all the users in company A to an alternate language in the user profile application, say FR for French. Then in the UDC application, set up company A's alternate descriptions for a given value as French translations. Because you don't actually have the French version of OneWorld installed, their screens will continue to show up in English. But any time they access the UDC table, it will first look to the F0004D and F0005D tables for any alternate descriptions coded to French.

2 - If you must have different UDC values for the two company's, you may still be able to use this solution. Simply decide which company (say Company B) gets the "primary" (English) version of the UDC tables (F0004/F0005). Then add company A's values as usual to the UDC table with a description of COMPANY A ONLY for all values added. Then set up the alternate descriptions for whatever language (FR as in previous paragraph) you've assigned for company A users. Company B will see the values for company A, but will easily be able to identify them as for company B only. This also allows you to set up for additional companies (C, D, etc.) by assigning them to their own alternate language.

3 - The only real alternative is to create separate UDC tables for each company. This is not too difficult, but can get a little messy in environment setup as well as UDC maintenance on-going and during upgrades. If you do decide to go this route, I would recommend simply creating a different environment for each company by copying your current production environment to PRDA for Company A and PRDB for Company B. Then you simply change the OCM mappings for PRDA for the F0004, F0004D, F0005, F0005D to the new datasource containing company A's UDCs and similar mappings for PRDB. The users in each company would then sign on using their company specific environment. Notice that they will still be running against all the same data as before except for the UDC tables. They will also be running the same code since these environments still run with the PRDB733 pathcode...so no extra package maintenance is involved. I recommend this over trying to separate the users in each company by group and then trying to have them run against the different UDC datasources by maintaining OCM records with in the PRD733 environment. Group-specific OCM maintenance is messier than separate environments.

I hope this helps. Please let the list know what you decide.

owguru (at least I'm trying :)
>all versions
>all platforms
 
A little bit addition to using alternate language preference.
It could be an unwanted sideeffect if your b7\system\bin32 folder containes translated RTT items (e.g. oexplorer) too. In this case, users with F language code will see a French OW Explorer and many other will French for them.
Workaround this problem, define notional language codes (UDC: 01/LP) for this method like Z1, Z2, etc. and use them.
Zoltán

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
 
Zoltan!

I knew someone would rescue me with the whole solution :)

Thanks

owguru (at least I'm trying :)
>all versions
>all platforms
 
Back
Top