VPD Profiles

This page is accessed via Configuration and Administration > VPD Profile. The VPD Manager enables administrators to use the Oracle Virtual Private Database (VPD) feature to view, modify, and create VPD Profiles. Only users with ADMIN user level privileges can access the VPD Manager. VPD works by adding a WHERE clause to every table in a SQL statement. VPD does not provide functional security; rather, it controls user access to data. For functional security, use the Function Groups option and Menu Manager. A VPD profile is a set of virtual private database rules. Virtual private databases provide fine-tuned access control to users, across or within domains. A number of preset VPD profiles can be selected and new profiles can be created for customized access control. Note: Only users with ADMIN user level privileges can access the VPD Manager. In addition, creating or editing VPD profiles requires a working knowledge of Oracle databases. For assistance, contact Technical Support. Note: To exclude a query from being cached for UI drop-down lists, add the glog property glog.droplistcache.exclude and the value of the full java class name that runs the query. For example, to exclude Shipment Refnum Qualifiers from the cache, set the property to: glog.droplistcache.exclude=glog.server.query.powerdata.ShipmentRefnumQualQuery Select Profile To use an existing VPD profile, select it from the drop-down list. The preset VPD profiles are: DATAENTRY - Limits a user to only updating those records which the user created. This, in effect, creates a personalized database for a user limited to the records they have created. DBA - Provides full access to Oracle Transportation Management schema tables. DEFAULT - Provides access to the entire domain, public data, and any other data to which they have been granted access. DISPLAY_HIDDEN_SHIPMENT_EVENTS - Displays a flag on the Add Shipment Event page that lets you hide/show specific events. Note: Do NOT use this profile. Instead, go to the User Preferences page (Configuration and Administration > Preferences > User Preferences) and select it there. FTI_DEFAULT : OTM users that will access FTI should have this profile rather than DEFAULT. Do not use the default profile to access FTI. FTI service providers should use the profile SERVPROV. INVOLVED_PARTY_DOMAIN_VIS - Limits access to only those order bases in a domain in which the user is an involved party.* INVOLVED_PARTY_USER_VIS - Limits access to only those order bases, order releases and shipments in which the user is an involved party.* SERVPROV - Limits access to only those shipments in which the user is associated with the service provider.

*The INVOLVED_PARTY external predicates do nothing when the user's domain is the same as the domain on the order or shipment.