Foreword: Sometimes, due to certain needs, we must know the case of Oracle's form being used, in terms of which we make decisions, for example, if a form is used very often, then the relevant SQL code of this form should be prioritized to reduce the server load, thus providing the system to run faster. Or, (especially) when the system is going to be upgraded, this data is very important: decide which form should be left and which form should be taken away. Of course, this information is only the reference data for making decisions. 1. Technical approach to form tracking on Oracle EBS: A profile of Oracle EBS provides this capability: User_profile_option_name = login: Audit layer (Sign-on:audit level) View_ Name = Fnd_signon_audit_view This profile has 4 optional values: ' None ': Do Not track--a ' users ': only track which user logged ' duty ': only track which user is logged in with which function Form ': After which user is logged, which form--d is running, which of the following is enabled, the Fnd_signon_audit_view can be queried for relevant data through PID or Process_spid and v$process/v$ Session Association 2. System profile settings: Login: The audit layer Login: Audit layer allows you to select an audit layer to log on to Oracle application product users and adds four audit layer capabilities: None, users, responsibilities, and forms. None is the default value, which means that no users logged on to the Oracle app product are audited. Audit trail at the "user" level: Users logged in to your system and logged in and exited at the end of the "responsibility" layer audit performed the "User" layer audit function and lead: the responsible user chooses the amount of time each responsibility is used by the user to perform the audit function and lead on the "responsibility" layer in the "form" layer audit The time the user uses each form can be viewed and updated by the system administrator at all levels. Users cannot view or change this preset file option. This preset file option can be viewed and updated in all four tiers. Whether the layer can see if the update site is allowed is whether the app is the responsibility or the user is the internal name of this preset file option is signonaudit:level. Reference connection: http://www.onejava.com/article/oracle/fnd/adupapp.htm System Configuration Example: (see document) 3. How to monitor the customized form: The standard function of the form, will be set as long asThe profile value is monitored; however, the custom-developed Form, if it wants to be recorded by the system of its usage and usage times, must write code: Pre-form (or when-new-form-instance) correctly enter the following statement, You can record the information of each user login form (login time, number of times, etc.): Fnd_standard. Form_info (' $Revision: 120.0 $ ', ' from_name ', ' application_short_name ', ' $Date: 2010/11/02 23:25 $ ', ' $Author: sam.t $ '); For example, the form name is: XYG_WIP_MOVE_SCH_QY registered module abbreviation is: Xyg fnd_standard. Form_info (' $Revision: 120.0 $ ', ' xyg_wip_move_sch_qy ', ' xyg ', ' $Date: 2010/11/02 23:25 $ ', ' $Author: sam.t $ '); As long as user login form, it will be recorded, convenient to later statistics form the number of times used and other information. The logic is that once a form is logged in the same permission, it is logged once. At the same time, the DB tool can also be used to easily view the current user's use of form information. For example, I open a form under this form: (see document) Form information: (see document) 4. Related script files:---Record the number of times a FORM is used: SELECT a.*, B.form_name, b.description from Fnd_login_resp_forms A, fnd_form_vl B WHERE a.form_id = b.form_id---View the user's usage form in real time: SELECT * from Fnd_signon_audit_view---record related information pkg:fnd_signon-table plug record for form usage:/* INSERT into Fnd_login_resp_forms (login_id, login_resp_id, form_appl_id, form_id, start_time) SELECT audit_form. login_id, Audit_form. login_resp_id, a.application_id, f.form_id, sysdate from Fnd_form F, fnd_application A WHERE f.form_name = audit_form. Form_name and f.application_id = a.application_id and A.application_short_name = Audit_form. Form_application; */
