FRM-18122: Forms Builder Debugger failed to initialize

FRM-18122: Forms Builder Debugger failed to initialize

• When you opening the Oracle Database 10g Forms Builder, suppose if you got an error like the following screenshot,
• The Error is “FRM-18122: Forms Builder Debugger failed to initialize”

 

Solution:

 

• First, Select My Computer then click Properties by the time you will see System Properties window like the following Screenshot,

 

• In that Properties window click the option “Advanced “. When you click that option then you will see like the following ,

• In the Advanced tag, click Environment Variables button and you will see one new window like the following screenshot,

 

 

• In that Environment Variables window, click the New button and you will see New User Variable window like the following,

 

• In that New User Variable then add the appropriate Variable name and Variable value.
• In Variable name box of the New User Variable window then type FORMS_BUILDER_CLASSPATH.
• In Variable value box of the New User Variable window then add the appropriate Oracle Database 10g Forms Class path like the following,

F:\DevSuiteHome_1\forms\java\frmwebutil.jar;F:\DevSuiteHome_1\forms\java\frmall.jar;F:\DevSuiteHome_1\forms\java\frmall_jinit.jar( This path is Based on  where you Installed Forms In your System)

• And again click New button, add one more Forms path like the following, in Variable name box type FORMS_PATH.

• And in Variable value box then add the respective jar files of the forms path like the following ,

F:\DevSuiteHome_1\forms\java\frmall.jar;F:\DevSuiteHome_1\forms\java\frmall_jinit.jar( This path is Based on where you Installed Forms In your System)

• Once finished these steps then click Apply and Ok.
• After that again add these jar file paths into default.env file. Then go to respective Forms builder of the default.env file. Example like the following,

F:\DevSuiteHome_1\forms\server, and also refer the following screen shot

 

• Click the default.env file.
• Add the appropriate jar files path in FORMS_PATH, like the following screenshot,

 

• Add the appropriate jar files path in CLASSPATH, like the following,

 

• Once You finished all these steps, and then opens the Forms Builder that error will not occur.

Form Personalization with Examples

Form Personalization:

 

1. Form Personalization is a feature in Oracle Apps that allows us to change the behavior of form based screens.
2. It can be moved easily through FNDLOAD from one instance to another, It can be restricted at   Site/User/Responsibility Level.

What can be done through Form Personalization?

1.        Zoom from One form to another.

2.        Pass data from one form to another through global variables.

3.        Enable/Disable/Hide fields dynamically.

4.        Launch URL directly from oracle form.

5.        Call PL/SQL procedure.

Components of Form Personalization:

 

 

How To make a Field Mandatory in the Form:

 

Go for Any Perticular Form If you want to personalize, Open that form

 

 

 

Go as specified Navigation in Help ->Diagnostics-> Custom Code -> Personalize

 

 

 

Once Open That let we create 10.1 Seq For Make Field Mandatory (Make sure that This should be Enabled). 

 

Condition->Trigger Event we are selection as WHEN-NEW-FORM-INSTANCE.

 

 

 

Object_type:Item(Column)

Target_Object :MTL_SYSTEM_ITEMS.LIST_PRICE_PER_UNIT_MIP(Which field you want to make it mandatory select that column as target Object).

Property_Name:Required

 

 

 

 

 How to perform calculations in the field:

 

 

 

 

Calculations will be done through per each Record so we selected as WHEN-NEW-RECORD-INSTANCE

 

Let we calculate this in attirbute_13 in PO_LINES

 

 

 

Meaning of Special fields in Form Personalization:

•      Menu(1-15) will be in tools

•       Populate tools menu (SPECIAL 1-15)

•       Populate reports menu (SPECIAL 16-30)

•       Populate actions menu (SPECIAL 31-45)

•       It is recommended to use Menu before Tools

Various components used In Form Personalization:

Trigger Event  - These are predefined event. Based on the value chosen the function will execute only when that particular event triggers on the form.

Processing Mode - Query mode or Not in Query mode or   Both

Context   - At what level like user or Responsibility level

Menu      -    this is used to call one form from another. it is used to implement the zoom functionality. There are 45 menu entries which are used to call                      one form from current form.

Built In    -   It allows you to call Oracle standard built-in and Functions

 

Launch a URL

 

 

How to hide a field

 

 

 

 

 

 

  

Create User In Oracle Apps Through Back End

Create User In Oracle Apps Through Back End


declare
l_user_name varchar2(30):='TESTUSER';
l_owner varchar2(30):='xxxxx'; -- Any existing user
l_unencrypted_password varchar2(240) :='welcome123';
l_session_number number :=userenv('sessionid');
l_start_date date :=sysdate-1;
l_end_date date := null;
l_last_logon_date date := null;
l_description varchar2(240) := 'FirstName, Lastname';
l_password_date date := SYSDATE;
l_password_accesses_left number := null;
l_password_lifespan_accesses number := null;
l_password_lifespan_days number := 90;
l_employee_id number := null;
l_email_address varchar2(240) := 'existing@email.com';
l_fax varchar2(30) := null;
l_customer_id number := null;
l_supplier_id number := null;


begin

fnd_user_pkg.CreateUser(
x_user_name => l_user_name,
x_owner => l_owner,
x_unencrypted_password => l_unencrypted_password,
x_session_number => l_session_number,
x_start_date => l_start_date,
x_end_date => l_end_date,
x_last_logon_date => l_last_logon_date,
x_description => l_description,
x_password_date => l_password_date,
x_password_accesses_left => l_password_accesses_left,
x_password_lifespan_accesses => l_password_lifespan_accesses,
x_password_lifespan_days => l_password_lifespan_days,
x_employee_id => l_employee_id,
x_email_address => l_email_address,
x_fax => l_fax,
x_customer_id => l_customer_id,
x_supplier_id => l_supplier_id);



fnd_user_pkg.addresp(l_user_name,'SYSADMIN','SYSTEM_ADMINISTRATOR','STANDARD',null,sysdate-1,sysdate+90);

DBMS_OUTPUT.PUT_LINE('User Created SuccessFully');

COMMIT;
end;

Query to find the Request Group Or a Concurrent Program Information

Query to find the Request Group Or a Concurrent Program Information

 
 SELECT DECODE(frgu.request_unit_type,
              'P','Program',
              'S','SET',
              'A','Application',
              'F','Set Function',
              NULL) REQUEST_TYPE,
      frg.request_group_name,
      fat.application_name,
      decode(frgu.request_unit_type,
      'P', fcpv.user_concurrent_program_name,
      'S',FRSV.user_request_set_name,
      'A', fat2.application_name,
      NULL)  CONC_PROGRAM_NAME         ,
      fatt.application_name CONC_APPLICATION_NAME
FROM FND_REQUEST_GROUP_UNITS frgu,
  fnd_application_tl fat            ,
  FND_REQUEST_GROUPS frg            ,
  FND_CONCURRENT_PROGRAMS_VL fcpv   ,
  fnd_application_tl fatt,
  FND_REQUEST_SETS_VL FRSV,
  fnd_application_tl fat2
  WHERE  frgu.application_id    =   fat.application_id(+)
AND frgu.request_group_id       =   frg.request_group_id(+)
AND frgu.request_unit_id        =   fcpv.concurrent_program_id(+)
AND frgu.unit_application_id    =   fatt.application_id(+)
AND frgu.request_unit_id        =   frsv.request_set_id(+)
and frgu.request_unit_id        =   fat2.application_id(+)
--and frg.request_group_name ='All Reports'
--and fat.application_name ='Payables'
and fcpv.user_concurrent_program_name='XX AP Supplier Site Conversion Loader Program'