There are instances where a company has different business units (BU), and each BU has its own set of values to be defined. Say for e.g. a company has different business units spread across countries for their operations. Won’t it be great if each country could see their own list of states/provinces instead of having separate instances? Another example – a company’s customer service department may provide support for appliances, consumer electronics, and sporting goods. Typically, a representative would choose from an extensive list of values to specify the repair code for a particular type of product. These cases can be dealt using UDC Sharing (I reckon its an old feature!). With UDC sharing, JD Edwards EnterpriseOne provides the ability to control, or regulate, how organizational data among different business units is shared. UDC sharing enables you to define a subset of UDC values for a business unit. You can share multiple UDC values among multiple business units. So for the above example, with UDC sharing, the company can associate a subset of the repair code UDC values, such as for appliances, to a business unit. As a result, the representatives associated with the business unit would only have to choose from a list of repair codes relevant to appliances. UDC Sharing is a functionality that is available beginning with EnterpriseOne 8.11. The set-up needs to be done on the Windows client, but the actual security only applies to applications that are run on the web client.
UDC sharing can impact system performance because of the time it takes the system to determine the UDC values that are associated with each business unit.
Now, UDC sharing is defined using the UDC Sharing application P95310. It can be accessed under the EnterpriseOne Life Cycle Tools task view by selecting System Administration Tools/System Administration Tools/Security Maintenance/Business Unit Security. Learn more about/Implement UDC sharing at Oracle Documentation NB: Issues with UDC Sharing
- Only works on the Web client. Not something that functions or can be tested on a Windows client.
- UDC sharing does not work when calling the UDC application directly (P0004A or UDC – P0005 in Fast Path). It only works when using a Visual Assist within an application that calls the UDC table (P0005S – Search & Select Form).
- No F00950 security records are created when defining UDC Sharing. Although the Business Unit security portion of the application is utilized, no transaction security is defined.
- When you set up UDC Sharing, the records are stored in the F95310 Table Sharing – Table Group Definition, F95311 – Table Sharing – Table Group Detail and F95320 – Table Sharing – Set ID Definition tables. These tables are mapped to the System data source. Therefore, any UDC sharing defined will be applied across all environments within EnterpriseOne.
Download the whitepaper here –
Please register to download the attachments in UDC Sharing [Whitepaper]