How to select value of profile through query

=================================
select fnd_profile.VALUE ( 'XXX_BPEL_TEST_SERVER_URL' )
into v_var
from dual;

or use this in plsql block :

v_var1 := fnd_profile.VALUE ( 'XXX_BPEL_TEST_SERVER_URL' );
=================================

API for creation or updation an Item

==============================================
ego_item_pub.process_item (p_api_version => 1.0, p_init_msg_list => fnd_api.g_true, p_commit => fnd_api.g_false, p_transaction_type => p_transaction_type, p_template_id => l_template_id, p_organization_id => p_organization_id, p_master_organization_id => g_organization_id, p_inventory_item_id => p_inventory_item_id, p_description => p_description, p_item_number => p_item_name, p_primary_uom_code => v_primary_uom, p_attribute15 => 'RETAIL', p_inventory_item_status_code => v_inventory_item_status_code, p_serial_number_control_code => v_serial_number_control_code, p_tax_code => v_tax_code, p_attribute1 => v_attribute1, p_buyer_id => v_buyer_id, p_full_lead_time => v_full_lead_time, x_inventory_item_id => v_inventory_item_id, x_organization_id => v_organization_id, x_return_status => v_return_status, x_msg_count => v_msg_count, x_msg_data => v_msg_data );
==============================================

API for Organization assignment to an Item

====================================================
apps.ego_item_pub.assign_item_to_org
(p_api_version => 1.0,
p_init_msg_list => fnd_api.g_true,
p_commit => fnd_api.g_false,
p_inventory_item_id => v_inventory_item_id,
p_item_number => fnd_api.g_miss_char,
p_organization_id => rec_cur_org.organization_id,
p_organization_code => NULL,
x_return_status => v_return_status,
x_msg_count => v_msg_count
);
====================================================

How to attach organization to a responsibility

================================================================
"Organization Access" Form of inventory responsibilty in setup options is used to attach organization to an particular responsibility.

So that switching of Organization in that responsibility would have that particular organization.
================================================================

To get all the users which have all the responsibilities given as parameter

================================================================
SELECT SUM (num), user_name, tot_num
FROM (SELECT 1 num, frgd.user_id, fu.user_name, frgd.responsibility_id,
tot.tot_num
FROM fnd_user_resp_groups_direct frgd,
fnd_user fu,
fnd_responsibility_tl frt,
(SELECT COUNT (1) tot_num
FROM fnd_responsibility_tl
WHERE responsibility_name IN
('Application Developer', 'Purchasing')
AND LANGUAGE = 'US') tot
WHERE 1 = 1
AND frgd.user_id = fu.user_id
AND frgd.responsibility_id = frt.responsibility_id
AND frgd.responsibility_application_id = frt.application_id
--AND FRGD.USER_ID = 15732
--AND fu.user_name like 'PGARG'
AND LANGUAGE = 'US'
AND frt.responsibility_name IN
('Application Developer', 'Purchasing'))
GROUP BY user_name, tot_num
HAVING SUM (num) = tot_num
================================================================

Implementation Steps for oracle apps

=====================================================================
Implementation Steps for oracle apps
There are 269 steps suggested by Oracle that needs to be followed to implement Oracle HRMS.
Broadly they are grouped into 47 steps
1. Define Key Flexfields
2. Define Descriptive Flexfields
3. Define Extra Information Types (EITs)
4. Administration
5. Application Data Exchange (ADE) and Hierarchy Diagrammers
6. Define Organization Structures
7. Define Roles
8. Define Grade Related Information
9. Define Payroll Information
10. Define Input Value Validation
11. Define Compensation and Benefits
12. Define Earnings and Deductions for Payroll Processing
13. Customize the Generated Definitions
14. Salary Administration
15. Absence Management and Accruals of Paid Time Off (PTO)
16. Define Element Sets
17. Basic Benefits
18. Total Compensation - Administration
19. Benefits Eligibility
20. Derived Eligibility Factors
21. Eligibility Profiles
22. Define Life Events (Advanced Benefits)
23. Program Setup
24. Enrollment Requirements
25. Activity Rates and Coverage Calculations
26. Reporting Groups
27. Flex Credit Calculations (Advanced Benefits)
28. Define Benefit Balances
29. Define Online Benefits Services
30. Person Types and Assignment Statuses
31. Special Personal Information (Personal Analysis Key Flexfield Structures)
32. New Hire Reporting
33. Workers Compensation
34. Human Resource Budgets
35. Evaluation Systems
36. Requirements Matching
37. Recruitment
38. Career Management
39. Evaluations and Appraisals
40. Career and Succession Planning
41. Define Reports
42. Standard Letter Generation
43. Customize Oracle HRMS
44. Create Task Flows
45. Define Menus
46. Define User Security
47. Define Audit Requirements
Oracle HRMS Data Pum
=====================================================================

Icons to Show in Oracle apps Forms

================================================
We can use any .gif file placed in $OA_MEDIA top as an icon image.
================================================

API for BOM Creation

===============================================================
bom_bo_pub.process_bom
(p_bo_identifier => 'BOM',
-- This parameter is required. It is used by the API to compare the version number of
-- incoming calls to its current version number.
p_api_version_number => 1.0 ,
-- This parameter is set to TRUE, allows callers to request that the API do the
--initialization of message list on their behalf.
p_init_msg_list => TRUE,
-- This is a set of data structures that represent the incoming business objects. This is a
--record that holds the Bill of Materials header for the BOM
p_bom_header_rec => v_bom_header_rec,
-- All the p*_tbl parameters are data structure that represent incoming business objects
-- They are PL/SQL tables of records that hold for each of the other entities.
p_bom_revision_tbl => v_bom_revision_tbl , p_bom_component_tbl => v_bom_component_tbl, p_bom_ref_designator_tbl => v_bom_ref_designator_tbl, p_bom_sub_component_tbl => v_bom_sub_component_tbl,
-- All the x*_tbl parameters are data structure that represent outgoing business objects
-- They are PL/SQL tables of records that hold records for each of the other entities except
-- now they have all the changes that the import program made to it through all the
-- steps.
x_bom_header_rec => v_bom_hdr_rec , x_bom_revision_tbl => v_bom_rev_tbl,
x_bom_component_tbl => v_bom_comp_tbl,
x_bom_ref_designator_tbl => v_bom_ref_desig_tbl, x_bom_sub_component_tbl => v_bom_sub_comp_tbl,
-- This is a flag that indicates the state of the whole business object after the
-- import. 'S' - Success, 'E' - Error, 'F' - Fatal Error, 'U' - Unexpected Error ,
x_return_status => v_return_status ,
-- This holds the number of messages in the API message stack after
--the import.
x_msg_count => v_msg_count
p_debug => 'N',
p_output_dir => '',
p_debug_filename => '' );
=========================================================

Oracke Apps Item Category Conversion APIs

=====================================
inv_item_category_pub.create_category
(p_api_version => v_api_version,
p_init_msg_list => fnd_api.g_true,
p_commit => fnd_api.g_true,
x_return_status => v_return_status,
x_errorcode => v_err_code,
x_msg_count => v_msg_count,
x_msg_data => v_msg_data,
p_category_rec => v_category_rec,
x_category_id => v_category_id );
======================================

inv_item_category_pub.create_category_assignment
(p_api_version => v_api_version,
p_init_msg_list => fnd_api.g_true,
p_commit => fnd_api.g_true,
x_return_status => v_return_status,
x_errorcode => v_err_code,
x_msg_count => v_msg_count,
x_msg_data => v_msg_data,
p_category_set_id => rec_get_valid_assign_load.category_set_id, p_category_id => rec_get_valid_assign_load.category_id, p_inventory_item_id => rec_get_valid_assign_load.inventory_item_id, p_organization_id => rec_get_valid_assign_load.organization_id );

============================================================

Oracle Forms Tips

===============================================================

To Make record status - "QUERY" if it somehow changing in "INSERT" or "CHANGED"

Write the below code in POST QUERY trigger after all the processing.

app_record.set_status('QUERY');

===============================================================