Thursday, 13 September 2012

Scheduling the Concurrent program

Scheduling the Concurrent program
We can submit the Concurrent program future date or date by using 
the schedule button in SRS window
As soon as possible: This is default option whenever we submit the
 request it will submit the as soon as possible
Once: It will submit the rest only once for future date.
Periodically: WE can specify the from_date and to_date to submit 
program periodically no of. Days months, hours, minutes and so on.
Specific Days: If we want submit concurrent program in the specific 
days we write select this option
Save this Schedule: This check box will be used to save the schedule 
and apply same schedule to other concurrent programs 
by selecting the button called 'Apply save schedule'
NOTE: After schedule the Concurrent program we can also 
cancel by selecting the cancel button.

--


Monday, 10 September 2012

HOW TO COMPILE AND OPEN ORACLE FORMS IN UNIX:


HOW TO COMPILE AND OPEN ORACLE FORMS IN UNIX:

Below are the commands to open and compile Oracle Forms in UNIX.

FORMS6I:
to open- f60desm
to compile/generate - f60genm



FORMS 9I:
to open - frmbld
to compile/generate – frmcmp



f90genm userid=scott/tiger@bs817 batch=yes module=$i module_type=form

compile_all=yes window_state=minimize

For 10gR1 = forms 9.0.4.x, you can use f90gen also

For 10gR2 = forms 10.x, you can use frmcmp.sh or frmcmp_batch.sh


Demo script (Linux) – Compiling forms application


frmcmp_batch.sh Module_type=LIBRARY Module=$ff userid=username/password@database upgrade=yes batch=yes window_state=minimize compile_all=yes

--


Value Sets

Dependent value Set:  ====================  This is another LOV which will be used to displays the   list of values which are depending on the previous parameter value.    Before going to create Dependent first we have to create Independent  then we have to create Dependent  First parameter will be Independent  Second parameter will be Dependent.    Note:Without Independent we can not create Dependent Value set.    Country	IND  	        US  	        UK  City   Banglore	Chennai 	Delhi	 Mumbai  Pune         Chikago  California      Anderson         London   Hungrant    1)We have to create Independent value set and enter the values.  2)Create Dependent value set attach independent and then enter values.      Job	  Manager  	  Developer  	  Programmer    Position   Delivery Manager   Project manager Financce manager  	   Software Developer Test Developer  	   Trainee  Fresher    Table Value set :    Table value set will be used to displays the list of values from the  oracle apps base tables.  we have to give the table name and column name which will automatically  displays the values.    Note: If values are not stored in the database table then we have to         go for Independent  value set.        If values are there in the table then we will create table value        set.    1.Open the value set form Select  validation type as table select the     button called Edit Information enter table name and column name     in the value field   2.Use where/Order By clause to implement Where/Order By clause.  3.Use Additional Columns field to displays extra columns for reference    purpose.  4.Use the ID column to pass the ineternally other columns data     for ex displaying username to the user and pass userID internally.  5.If multiple tables are required then enter the table names in the     table name field with alias name and enter the Join Condition in the    Where clause field.    6.If we know the table name we can find the Table application name from    Application Developer responsibility   Application Developer => Application => Database => table   Query the records based on the table Name.      Translated Independent and Translated Dependent:  ================================================  Both  value sets will work like Independent and Dependent value sets  will be used to displays the transalation values which will be enabled  if there is multilanguage implementation.    Special and Pair:  =================  Both Value sets will be used to displays the Flexfield data as LOV to  the User.  


--


Tuesday, 4 September 2012

R12 SLA Tables join conditions to AP, AR, INV,Payments and Receiving

R12 SLA Tables connection to AP, AR, INV,Payments, Receiving


R12 SLA (Sub ledger Accounting)


1) All accounting performed before transfer to the GL. Accounting data generated and stored in "Accounting Events" tables prior to transfer to GL


2) Run "Create Accounting" to populate accounting events (SLA) tables. User can "View Accounting" only after "Create Accounting" is run. Create Accounting process

Applies accounting rules

Loads SLA tables, GL tables

Creates detailed data per accounting rules, stores in SLA "distribution links" table


3) Below are the key tables for SLA in R12


XLA_AE_HEADERS xah

XLA_AE_LINES xal

XLA_TRANSACTION_ENTITIES xte

XLA_DISTRIBUTION_LINKS xdl

GL_IMPORT_REFERENCES gir


Below are the possible joins between these XLA Tables


xah.ae_header_id = xal.ae_header_id

xah.application_id = xal.application_id

xal.application_id = xte.application_id

xte.application_id = xdl.application_id

xah.entity_id = xte.entity_id

xah.ae_header_id = xdl.ae_header_id

xah.event_id = xdl.event_id

xal.gl_sl_link_id = gir.gl_sl_link_id

xal.gl_sl_link_table = gir.gl_sl_link_table

xah.application_id = (Different value based on Module)


xte.entity_code =

'TRANSACTIONS' or

'RECEIPTS' or

'ADJUSTMENTS' or

'PURCHASE_ORDER' or

'AP_INVOICES' or

'AP_PAYMENTS' or

'MTL_ACCOUNTING_EVENTS' or

'WIP_ACCOUNTING_EVENTS'


xte.source_id_int_1 =

'INVOICE_ID' or

'CHECK_ID' or

'TRX_NUMBER'


XLA_DISTRIBUTION_LINKS table join based on Source Distribution Types


xdl.source_distribution_type = 'AP_PMT_DIST'

and xdl.source_distribution_id_num_1 = AP_PAYMENT_HIST_DISTS.payment_hist_dist_id

---------------

xdl.source_distribution_type = 'AP_INV_DIST'

and xdl.source_distribution_id_num_1 = AP_INVOICE_DISTRIBUTIONS_ALL.invoice_distribution_id

---------------

xdl.source_distribution_type = 'AR_DISTRIBUTIONS_ALL'

and xdl.source_distribution_id_num_1 = AR_DISTRIBUTIONS_ALL.line_id

and AR_DISTRIBUTIONS_ALL.source_id = AR_RECEIVABLE_APPLICATIONS_ALL.receivable_application_id

---------------

xdl.source_distribution_type = 'RA_CUST_TRX_LINE_GL_DIST_ALL'

and xdl.source_distribution_id_num_1 = RA_CUST_TRX_LINE_GL_DIST_ALL.cust_trx_line_gl_dist_id

---------------

xdl.source_distribution_type = 'MTL_TRANSACTION_ACCOUNTS'

and xdl.source_distribution_id_num_1 = MTL_TRANSACTION_ACCOUNTS.inv_sub_ledger_id

---------------

xdl.source_distribution_type = 'WIP_TRANSACTION_ACCOUNTS'

and xdl.source_distribution_id_num_1 = WIP_TRANSACTION_ACCOUNTS.wip_sub_ledger_id

---------------

xdl.source_distribution_type = 'RCV_RECEIVING_SUB_LEDGER'

and xdl.source_distribution_id_num_1 = RCV_RECEIVING_SUB_LEDGER.rcv_sub_ledger_id



--


Friday, 13 July 2012

Query to get alerts information

SELECT
alv . *
FROM ALR_ALERTS al ,
ALR_ACTION_HISTORY aah ,
ALR_OUTPUT_HISTORY aoh ,
ALR_ACTIONS_V alv ,
alr_alert_historY_view aahv
WHERE al . alert_name = <name of alert > ---------'XX_ALERTS_SAMPLE'
AND al . alert_id = aah . alert_id
AND aah . check_id = aoh . check_id
AND alv . ALERT_ID = aah . alert_id
AND aahv . alert_name = al . alert_name;


--


Wednesday, 25 April 2012

QUERY FOR FINDING REQUEST GROUP

QUERY FOR FINDING REQUEST GROUP

SELECT fa.application_short_name,
       frg.request_group_name,
       fe.execution_file_name,
       fe.executable_name
  FROM fnd_request_group_units frgu,
       fnd_concurrent_programs fcp,
       fnd_request_groups frg,
       fnd_executables fe,
       fnd_application fa
 WHERE     frgu.request_unit_id = fcp.concurrent_program_id
       AND frgu.request_group_id = frg.request_group_id
       AND fe.executable_id = fcp.executable_id
       AND FRG.application_id = fa.application_id
       AND fe.executable_name = 'XX_PC_PURCHASE';
--


Create directory in Oracle


Create directory in Oracle
       

create or replace directory foo_dir as '/tmp';

Directories must be created if external tables are used.
Created directories are shown in either dba_directories or all_directories. There is no user_directories.

Privileges

When a «directory» has been created, the read and write object privileges can be granted on it:

create directory some_dir;
grant read, write on directory some_dir to micky_mouse;

An example

The following example shows how create directory and utl_file can be used to write text into a file:

create or replace directory dir_temp as 'c:\temp';

declare
  f utl_file.file_type;
begin
  f := utl_file.fopen('DIR_TEMP', 'something.txt', 'w');
  utl_file.put_line(f, 'line one: some text');
  utl_file.put_line(f, 'line two: more text');
  utl_file.fclose(f);
end;
/