SQL Query to find out Parameters and Value Sets associated with a Concurrent Program

SELECT
fcpl.user_concurrent_program_name "Concurrent Program Name",
fcp.concurrent_program_name "Short Name",
fdfcuv.column_seq_num "Column Seq Number",
fdfcuv.end_user_column_name "Parameter Name",
fdfcuv.form_left_prompt "Prompt",
fdfcuv.enabled_flag " Enabled Flag",
fdfcuv.required_flag "Required Flag",
fdfcuv.display_flag "Display Flag",
fdfcuv.flex_value_set_id "Value Set Id",
ffvs.flex_value_set_name "Value Set Name",
flv.meaning "Default Type",
fdfcuv.DEFAULT_VALUE "Default Value"
FROM
fnd_concurrent_programs fcp,
fnd_concurrent_programs_tl fcpl,
fnd_descr_flex_col_usage_vl fdfcuv,
fnd_flex_value_sets ffvs,
fnd_lookup_values flv
WHERE
fcp.concurrent_program_id = fcpl.concurrent_program_id
AND fcpl.user_concurrent_program_name like 'XX%'
AND fdfcuv.descriptive_flexfield_name = '$SRS$.'
|| fcp.concurrent_program_name
AND ffvs.flex_value_set_id = fdfcuv.flex_value_set_id
AND flv.lookup_type(+) = 'FLEX_DEFAULT_TYPE'
AND flv.lookup_code(+) = fdfcuv.default_type
AND fcpl.LANGUAGE = USERENV ('LANG')
AND flv.LANGUAGE(+) = USERENV ('LANG')
ORDER BY fdfcuv.column_seq_num;

Read More»

How to make a Oracle form 'Query Only'

There are many ways in which we can make a form Query only. We are going to discuss two
1) Using parameter QUERY_ONLY=YES
2) using Form Personalization
Method 1: Using parameter QUERY_ONLY=YES
Lets take an example of Purchase order enter form

Step 1) Using Sysadmin Responsibility find out the Menu attached to Purchasing Super User responsibility for which you want to make Purchase Order form as read only.

Step 2) Now Navigate to Application>Menu and query for this form and find out the form function associate with enter purchase order form. In our case it is "Purchase Orders"

Step 3) Create a new form function name having logically similar name as that of original function and in the form tab make QUERY_ONLY=YES

Step 4) Attach this new function in the place of old function to the same menu

Save and let Compile Security Request complete

Test ResultNavigate to Purchasing Super User> Purchase Order

See now this form is read only

Method 2 : Using Form Personalization

Step 1) Navigate to PO form>Help>Diagnostic>custom Code>Personalize

Step 2) Now here you can disable Update, Delete and Insert

Test Case : Check PO form now

Thanks

Mandeep

Read More»

Important WF tables

WF_USER_ROLE_ASSIGNMENTS stores information about the direct and inherited assignments of users to roles in Oracle .

WF_USER_ROLES stores associations of users with the roles of which they are members.

WF_ROLES stores Roles, which can have one or more users as members.

WF_LOCAL_ROLES stores role information, including a user flag to mark those roles that also represent individual users. This table contains columns similar to those required in the WF_USERS and WF_ROLES views.

WF_LOCAL_USER_ROLES stores information about the associations of users with roles. This table contains columns similar to those required in the WF_USER_ROLES view.

WF_ACTIVITIES table stores the definition of an activity. Activities can be processes, notifications, functions or folders. A process activity is a modeled workflow process, which can be included as an activity in other processes to represent a sub process. A notification activity sends a message to a performer. A functions activity performs an automated function that is written as a PL/SQL stored procedure. A folder activity is not part of a process, it provides a means of grouping activities.

WF_ACTIVITY_ATTRIBUTES table defines attributes which behave as parameters for an activity. Activity attributes are only used by function activities.Examples of valid attribute types are DATE, DOCUMENT, FORM, ITEMATTR, LOOKUP, and VARCHAR2.

WF_NOTIFICATIONS holds the runtime information about a specific instance of a sent message. A new row is created in the table each time a message is sent.

WF_NOTIFICATION_ATTRIBUTES holds rows created for attributes of a notification. When each new notification is created, a notification attribute row is created for each message attribute in the message definition. Initially, the values of the notification attributes are set to the default values specified in the message attribute definition.

WF_MESSAGES contains the definitions of messages which may be sent out as notifications.

WF_MESSAGE_ATTRIBUTES contains message attribute definitions.

WF_ITEMS is the runtime table for workflow processes. Each row defines one work item within the system.

WF_ITEM_TYPES: defines an item that is transitioning through a workflow process.

WF_ITEM_ATTRIBUTES table stores definitions of attributes associated with a process. Each row includes the sequence in which the attribute is used as well as the format of the attribute data.

WF_ITEM_ACTIVITY_STATUSES is the runtime table for a work item. Each row includes the start and end date, result code, and any error information an activity generates.

WF_ITEM_ACTIVITY_STATUSES_H  stores the history of the WF_ITEM_ACTIVITY_STATUSES table.

WF_PROCESS_ACTIVITIES stores the data for an activity within a specific process.

WF_ACTIVITY_TRANSITIONS defines the transitions from one activity to another in a process. Each row includes the activities at the beginning and end of the transition, as well as the result code and physical location of the transition in the process window.

WF_ACTIVITY_ATTR_VALUES contains the data for the activity attributes. Each row includes the process activity id and the associated value for the attribute.

Thanks
Mandeep

Read More»

R12 SQL Query to differentiate Customer and Suppliers Data

select * from (
select hp.party_number,hp.party_name,hp.status,decode(nvl(hpu.party_usage_code,hp.party_type),'ORGANIZATION','CUSTOMER',nvl(hpu.party_usage_code,hp.party_type)) party_type 
from  apps.HZ_PARTY_USG_ASSIGNMENTS hpu, hz_parties hp
where hp.party_id = hpu.party_id(+))
order by party_type

Read More»

Important HRMS Tables

• per_all_people_f 

This table is used to store employee related data.

• per_all_assignments_f

This table store employee assignment related information and connected to per_all_people_f with person_id and assignment number.

• per_addresses

This table store  information related to employee address form and  connected to per_all_people_f with person_id.

• per_pay_proposals

This table will store information related to employee salary form.

• per_person_types_tl

This table store type of the employee information and connected to per_all_people_f with the person_type_id.

• per_jobs_tl

This table is for JOBS in Oracle and can be linked to per_all_assignments_f.

• per_grades_tl

This table stores various types of GRADES and can be linked to per_all_assignments_f.

• hr_locations_all

Location table

• pay_all_payrolls_f

PAYROLLS Table and can be linked to per_all_assignments_f table

• per_pay_bases

Contain the PAY BASES can be linked to  per_all_assignments_f table.

• per_assignment_status_types_tl

Contain the assignment types and linked to per_all_assignments_f table

• per_person_type_usages_f

This table store the person type of the employee. 

Read More»

Responsibilites and their associated Menus

SELECT DISTINCT frt.responsibility_name, fmt.user_menu_name
  FROM apps.fnd_responsibility_tl frt,
       apps.fnd_responsibility fr,
       apps.fnd_menus_tl fmt,
       apps.fnd_menus fm,
       apps.fnd_application_tl fat,
       apps.fnd_application fa
 WHERE     frt.responsibility_id(+) = fr.responsibility_id
       AND fr.menu_id = fmt.menu_id
       AND fr.menu_id = fm.menu_id
       AND fat.application_id = fa.application_id
       AND fa.application_id = fr.application_id
       AND frt.LANGUAGE = 'US';

Read More»

Request Group assigned to Responsibilty

SELECT    responsibility_name responsibility,request_group_name,frg.description 
FROM       fnd_request_groups frg, fnd_responsibility_vl frv 
WHERE     frv.request_group_id = frg.request_group_id 
ORDER BY responsibility_name; 

Read More»