o Open System Administrator resp. Navigate to Security->Responsibility->Define
o Query responsibility name(Ex: Payables, HG Operations) you want to use that will have the Supplier page as Read Only.
o Under Menu Exclusions select Type as 'Function' and Name as 'Supplier Full Access : Buyer View'
o Save changes.
Navigation Path: System Administrator->Security->Responsibility->Define
o Now open Suppliers page and check changes.
Navigation Path: Payables Resp(Payables, HG Operations)->Suppliers->Entry
Supplier page looks like this in read only mode
Showing posts with label SystemAdmin. Show all posts
Showing posts with label SystemAdmin. Show all posts
Wednesday, January 20, 2010
Wednesday, January 6, 2010
Explain Request Groups and Request Sets in Concurrent Programs?
Grouping concurrent programs and other requests together allows you to control access and streamline processing. In Oracle Applications, you group programs and requests into request groups and request sets.
Request Groups
A request group is a collection of reports and other concurrent programs. You use request groups to implement security at the responsibility level. Request groups are normally associated with a responsibility, in which case they are referred to as request security groups. Any user of a responsibility has access to the reports in that responsibility’s request security group. Additionally, you can define a request group to have an access code. You can then define the form so that it allows users to select only those reports or concurrent programs belonging to a request group with an assigned code.
Request Sets
A request set is a collection of concurrent programs set up to run in a specified sequence from a single transaction. Request sets can also have run and/or print options, which apply to everymember of the set. Programs in a request set can share parameters; therefore a parameter value needs to be entered only once for multiple programs. Any user can create a request set.
Request Groups
A request group is a collection of reports and other concurrent programs. You use request groups to implement security at the responsibility level. Request groups are normally associated with a responsibility, in which case they are referred to as request security groups. Any user of a responsibility has access to the reports in that responsibility’s request security group. Additionally, you can define a request group to have an access code. You can then define the form so that it allows users to select only those reports or concurrent programs belonging to a request group with an assigned code.
Request Sets
A request set is a collection of concurrent programs set up to run in a specified sequence from a single transaction. Request sets can also have run and/or print options, which apply to everymember of the set. Programs in a request set can share parameters; therefore a parameter value needs to be entered only once for multiple programs. Any user can create a request set.
Monday, November 30, 2009
Types of Value Sets
You can define several types of value sets depending on how you need your values to be checked. All value sets perform minimal checking; some value sets also check against the actual values, if you have provided any.
Navigation Path: System Administrator->Application->Validation->Set/Values
None - A value set of the type None has no list of approved values associated with it. A None value set performs only minimal checking of, for example, data type and length. Examples of such values include credit card numbers, street addresses, and phone numbers.
Independent - Use the validation type Independent when you know the allowable values ahead of time. Independent type value sets perform basic checking but also check a value entered against the list of approved values you define.
Dependent - A Dependent value set is also associated with a list of approved values. In this case however, the values on the list can be grouped into subsets of values. Each subset of values is then associated with a value from an Independent value set. Once a value from the Independent value set has been specified, the list of values for the Dependent value set displays only the values that are approved for the value selected from the Independent value set.
In below picture, once a value from the Category value set has been specified, only the appropriate values from the Item value set are displayed.
Table - Table value sets obtain their lists of approved values from existing application tables. When defining your table value set, you specify a SQL query to retrieve all the approved values from the table.
Special - This specialized value set provides another flexfield as a value set for a single segment. Special value sets can accept an entire key flexfield as a segment value in a descriptive flexfield or report parameter.
Pair - This specialized value set provides a range flexfield as a value set for a pair of segments.
Translatable Independent - Translatable Independent value sets are similar to Independent value sets except that translated values can be displayed to the user. Translatable Independent value sets enable you to use hidden values and displayed (translated) values in your value sets. In this way your users can see a value in their preferred languages, yet the values will be validated against a hidden value that is not translated. A Translatable Independent value set can have only Translatable Dependent value sets dependent on it.
See Example: Appliances and Furniture can be displayed in two languages (Gerate and Mobel) or (Appareils and Meubles).
Translatable Dependent -Translatable Dependent value sets are similar to Dependent value sets except that translated values can be displayed to the user. Translatable Dependent value sets enable you to use hidden values and displayed (translated) values in your value sets. In this way your users can see a value in their preferred languages, yet the values will be validated against a hidden value that is not translated. Translatable Dependent value sets must be dependent on a Translatable Independent value set.
See Example: Appliances and Furniture can be displayed in two languages (Gerate and Mobel) or (Appareils and Meubles). Microwave can be displayed in Mikrowellenherd or Four a micro-ondes.
Navigation Path: System Administrator->Application->Validation->Set/Values
None - A value set of the type None has no list of approved values associated with it. A None value set performs only minimal checking of, for example, data type and length. Examples of such values include credit card numbers, street addresses, and phone numbers.
Independent - Use the validation type Independent when you know the allowable values ahead of time. Independent type value sets perform basic checking but also check a value entered against the list of approved values you define.
Dependent - A Dependent value set is also associated with a list of approved values. In this case however, the values on the list can be grouped into subsets of values. Each subset of values is then associated with a value from an Independent value set. Once a value from the Independent value set has been specified, the list of values for the Dependent value set displays only the values that are approved for the value selected from the Independent value set.
In below picture, once a value from the Category value set has been specified, only the appropriate values from the Item value set are displayed.
Table - Table value sets obtain their lists of approved values from existing application tables. When defining your table value set, you specify a SQL query to retrieve all the approved values from the table.
Special - This specialized value set provides another flexfield as a value set for a single segment. Special value sets can accept an entire key flexfield as a segment value in a descriptive flexfield or report parameter.
Pair - This specialized value set provides a range flexfield as a value set for a pair of segments.
Translatable Independent - Translatable Independent value sets are similar to Independent value sets except that translated values can be displayed to the user. Translatable Independent value sets enable you to use hidden values and displayed (translated) values in your value sets. In this way your users can see a value in their preferred languages, yet the values will be validated against a hidden value that is not translated. A Translatable Independent value set can have only Translatable Dependent value sets dependent on it.
See Example: Appliances and Furniture can be displayed in two languages (Gerate and Mobel) or (Appareils and Meubles).
Translatable Dependent -Translatable Dependent value sets are similar to Dependent value sets except that translated values can be displayed to the user. Translatable Dependent value sets enable you to use hidden values and displayed (translated) values in your value sets. In this way your users can see a value in their preferred languages, yet the values will be validated against a hidden value that is not translated. Translatable Dependent value sets must be dependent on a Translatable Independent value set.
See Example: Appliances and Furniture can be displayed in two languages (Gerate and Mobel) or (Appareils and Meubles). Microwave can be displayed in Mikrowellenherd or Four a micro-ondes.
Subscribe to:
Posts (Atom)



