Collection and sorting of EBS preset files

Http://blog.csdn.net/rfb0204421/article/details/7589514

In EBS, there are many configuration options (profile ),System AdministratorYou only need to make some simple configurations for them to meet the control process switch, secure access, personal preferences, and other requirements.

Take HR: security profile as an example. This profile is controlled in the HR system and can be viewed by the logon user, such as organization, position, and payroll. After logging on to the system using system administrator, select profile-> system. You can see that a profile can be set with a corresponding value at many levels. The priority of these values increases from top to bottom, that is, the user-level value has the highest priority. The value of this layer will overwrite the values of all other layers. However, for a profile, you may need to restrict access to certain levels and assign values to them. In the EBS system, you can use the following implementation: application developer-> profile, you can control access and update permissions for each level (site, server, responsibility, etc. Note that when you modify the Profile Value of HR: security profile, you must submit a concurrent request through HRMS Manager-> processes and reports-> submit processes and reports, the name is security list maintenance, and the value of the "generate list for" parameter is one named security profile. The value of the "security profile" parameter is the name of the profile that has just been modified.

 

For more information about how to set and use preset files, see some common methods for component control (availability, visibility) in the development of the blog form.

 

The following are common preset files, all of which can be downloaded from my resources.

1. Hide diagnostics menu entry: used to control whether diagnostics under the Help menu is hidden. It is hidden by default.
2. Utilities: Diagnostics: used to control whether to use the apps password when entering the diagnostic mode. The default password is used.
3. Java color scheme (Java color design): Color configuration of form.
4. Java look and feel: Set the form style.
5. Currency: Positive format: positive display format
6. Currency: Negative format: the format in which a negative number is displayed.
7. Currency: Thousands separator: whether to display kilobytes (Note: The display accuracy is determined by the precision settings of each currency (set in the general ledger module ))
8. Self Service personal home page mode: defines the style of the responsibility and permission page displayed after a user logs on.
9. Icx: Date Format mask (icx: Date display style): defines the date display format of the system.
10. Icx: Session Timeout (icx: Session Timeout): defines the timeout interval for the system to maintain an inactive user session. The default value is 1800000 milliseconds (30 minutes ).
11. Icx: limit time (icx: limit time): defines the maximum logon time for the system to maintain a user session. The default value is 4 hours.
12. Icx: Limit connect (icx: restrict connections): defines the maximum number of active database connections. The default value is 1000.
13. MO: operating unit: ou business organization
14. MO: Default operating unit: default business organization
15. MO: security profile: Security preset file. -- Mo: security profile can be used to set multiple organizations. In this case, you can use MO: Default operating unit to specify the default organization, while MO: operating unit is used only for a single organization.
16. Signon password length: Minimum Password Length. The default value is 5. The maximum length is 30.
17. Signon password hard to guess: whether a "strong" password is required. The default value is "no ".
18. Signon password failure limit: number of failed password retries at logon. The default value is 3.
19. Signon password no reuse: the number of days after which the previously used password can be used. The default value is null, that is, no control is performed.
20. SystemAPIDebug level FND: debug log level level_unexpected: internal level ID is 6
    Level_error: internal level ID is 5
    Level_exception: internal level ID is 4
    Level_event: internal level ID is 3
    Level_procedure: internal level ID is 2
    Level_statement: internal level ID is 1 FND: debug log Enabled
    Set this profile to Yes
    
    FND: Debug Log Module
    Set this to %
21. General Ledger set GL legder name
22. Hide diagnostics menu hide diagnostics menu entry
23. Developer mode (R12) -- role to be studied FND: developer Mode
24. Data Control Set (R12) GL: Data Access set

 

The configuration file (profile) plays an important role in EBS system configuration. The function consultant must be familiar with many important configuration files. Otherwise, a problem may occur. after a long time of being depressed, it may be found that some inconspicuous configuration file is in disorder. The configuration file is equivalent to a parameter with permission Level Control. Its role area is restricted by its permission settings.

First, I learned about the configuration file from the background.

-- Query the configuration of configuration files in the system
Select op. profile_option_id,
TL. profile_option_name,
TL. user_profile_option_name,
LV. level_id,
LV. file security,
Va. level_value,
Case
When va. level_id = 10001 then 'location'
When va. level_id = 10002 then (select fav. application_name
From fnd_application_vl fav
Where fav. application_id = va. level_value)
When va. level_id = 10003 then (select/* $ header $ */
T. responsibility_name
From fnd_responsibility_tl t,
Fnd_responsibility B
Where T. responsibility_id = va. level_value
And T. responsibility_id = B. responsibility_id
And B. application_id = T. application_id
And nvl (B. end_date, sysdate + 1) & gt; sysdate
And nvl (B. start_date, sysdate-1) <sysdate
And T. Language = 'zhs ')
When va. level_id = 10004 then (select user_name
From fnd_user
Where user_name not in
('* Anonymos *',
'Version ',
'Initial ',
'Feeder system ',
'Current Manager ',
'Standalone batch Process ')
And user_id = va. level_value
And nvl (end_date, sysdate + 1)> sysdate
And nvl (start_date, sysdate-1) & lt; sysdate)
When va. level_id = 10005 then (select node_name from fnd_nodes where node_id = va. level_value)
When va. level_id = 10006 then (Select name
From hr_operating_units
Where organization_id = va. level_value)
Else
''
End as profile_level_value,
Va. profile_option_value
From fnd_profile_options_tl TL,
Fnd_profile_options op,
Fnd_profile_option_values va,
(Select 10001 level_id, 'location' file security
From dual
Union
Select 10002 level_id, 'application product' file security
From dual
Union
Select 10003 level_id, 'response' file security
From dual
Union
Select 10004 level_id, 'users' file security
From dual
Union
Select 10005 level_id, 'server' file security
From dual
Union
Select 10006 level_id, 'org 'file security
From dual) LV
Where tl. Language = 'zhs'
And tl. profile_option_name = op. profile_option_name
And va. profile_option_id = op. profile_option_id
And va. level_id = lv. level_id
-- And TL. profile_option_name like '%'
-- And TL. user_profile_option_name like '%'
Bytes ------------------------------------------------------------------------------------------------------------------------
-- Query System Configuration File Creation
Select profile_option_name configuration file name,
User_profile_option_name user configuration file name,
Description,
Hierarchy_type,
Site_enabled_flag location is visible,
Site_update_allowed_flag location can be updated,
App_enabled_flag application product visible,
App_update_allowed_flag application products can be updated,
Resp_enabled_flag responsibility is visible,
Resp_update_allowed_flag responsibility can be updated,
Server_enabled_flag server visible,
Server_update_allowed_flag server updatable,
Serverresp_enabled_flag server responsibilities are visible,
Serverresp_update_allowed_flag server responsibilities can be updated,
Org_enabled_flag tissue visibility,
Org_update_allowed_flag organizations can be updated,
User_enabled_flag visible to users,
User_update_allowed_flag users can update,
Start_date_active effective start date,
End_date_active effective end date,
User_visible_flag user access can be viewed,
User_changeable_flag user access is updatable,
Read_allowed_flag readable,
Write_allowed_flag writable,
SQL _validation SQL verification,
Profile_option_id configuration file configuration ID
From fnd_profile_options_vl
-- Where (profile_option_name like '% ')
Bytes -------------------------------------------------------------------------------------------------------------------------
-- "Edit"-"Preferences"-"configuration file" configurations available in the menu
If you set the configuration file
User Access-you can view and check the configuration file in the menu.
User Access-you can modify the configuration file in the menu after the update check is completed.

Collection and sorting of EBS preset files