Where do concurrent request logfiles and output files go?
The concurrent manager first looks for the environment variable $APPLCSF. If this is set, it creates a path using two other environment variables: $APPLLOG and $APPLOUT
It places log files in $APPLCSF/$APPLLOG
Output files go in $APPLCSF/$APPLOUT
So for example, if you have this environment set:
$APPLCSF = /u01/appl/common
$APPLLOG = log
$APPLOUT = out
The concurrent manager will place log files in /u01/appl/common/log, and output files in /u01/appl/ common/out
Note that $APPLCSF must be a full, absolute path, and the other two aredirectory names.
If $APPLCSF is not set, it places the files under the product top of the application associated with the request.
So for example, a PO report would go under $PO_TOP/$APPLLOG and $PO_TOP/$APPLOUT
Logfiles go to: /u01/appl/po/9.0/log
Output files to: /u01/appl/po/9.0/out
Of course, all these directories must exist and have the correct permissions. Note that all concurrent requests produce a log file, but not necessarily an output file.
What are the logfile and output file naming conventions?
Logfiles: l<request id>.req
Output files: If $APPCPNAM is not set: <username>.<request id>
If $APPCPNAM = REQID: o<request id>.out
If $APPCPNAM = USER: <username>.out
Where: <request id> = The request id of the concurrent request
And: <username> = The id of the user that submitted the request
How do I check if Multi-org is installed?
SELECT multi_org_flag FROM fnd_product_groups;
How do I find out what the currently installed release of Applications is?
SELECT release_name FROM fnd_product_groups
How do I find the name of a form?
GUI: Use Help->About Oracle Applications
Scroll down to find the form name
Character: Use \Help->Version
How do I lookup ORA errors? (and TNS errors)
Use: oerr ora XXXX
or: oerr tns XXXX
where XXXX is the error number (This also supports a number of other error types. Use the 3-letter error prefix in place of 'ora')
How do I generate a message file (usaeng.msb)?
Use: FNDMDCMF applsys/pwd 0 Y APP usaeng
where: applsys/pwd is the APPLSYS user and password and APP is the short name of the application (like PO or INV)
PACKAGE AD_DD
package ad_dd as
/* $Header: addds.pls 110.3 98/09/18 18:24:23 porting ship $ */
procedure register_table (p_appl_short_name in varchar2, p_tab_name in varchar2,
p_tab_type in varchar2, p_next_extent in number default 512, p_pct_free in number default 10, p_pct_used in number default 70);
procedure register_column (p_appl_short_name in varchar2, p_tab_name in varchar2,
p_col_name in varchar2, p_col_seq in number, p_col_type in varchar2, p_col_width in number,
p_nullable in varchar2, p_translate in varchar2, p_precision in number default null, p_scale in number default null);
procedure register_primary_key(p_appl_short_name in varchar2, p_key_name in varchar2, p_tab_name in varchar2, p_description in varchar2, p_key_type in varchar2 default 'S',p_audit_flag in varchar2 default 'N', p_enabled_flag in varchar2 default 'Y');
procedure update_primary_key(p_appl_short_name in varchar2, p_key_name in varchar2, p_tab_name in varchar2, p_description in varchar2, p_key_type in varchar2 default null,p_audit_flag in varchar2 default null, p_enabled_flag in varchar2 default null);
procedure register_primary_key_column(p_appl_short_name in varchar2, p_key_name in varchar2, p_tab_name in varchar2, p_col_name in varchar2, p_col_sequence in number);
procedure delete_primary_key_column(p_appl_short_name in varchar2, p_key_name in varchar2, p_tab_name in varchar2, p_col_name in varchar2 default null);
procedure delete_table (p_appl_short_name in varchar2, p_tab_name in varchar2);
procedure delete_column (p_appl_short_name in varchar2, p_tab_name in varchar2, p_col_name in varchar2);
end ad_dd;
CONCURRENT PROCESSING IN ORACLE APPS.
Definitions
What is a Concurrent Program ?
An instance of an execution file, along with parameter definitions and incompatibilities. Several concurrent programs may use the same execution file to perform their specific tasks, each having different parameter defaults and incompatibilites.
What is a Concurrent Program Executable ?
An executable file that performs a specific task. The file may be a program written in a standard language, a reporting tool or an operating system language.
What is a Concurrent Request ?
request to run a concurrent program as a concurrent process.
What is a Concurrent Process ?
n instance of a running concurrent program that runs simultaneously with other concurrent processes.
What is a Concurrent Manager ?
program that processes user’s requests and runs concurrent programs. System Administrators define concurrent managers to run different kinds of requests.
What is a Concurrent Queue ?
ist of concurrent requests awaiting processing by a concurrent manager.
What is a Spawned Concurrent program ?
Concurrent program that runs in a separate process than that of the concurrent manager that starts it. L/SQL stored procedures run in the same process as the concurrent manager; use them when spawned concurrent programs are not feasible.
LIFE CYCLE OF CONCURRENT REQUESTS
What are the phases and statuses through which a concurrent prequest runs through?
A concurrent request proceeds through three, possibly four, life cycle stages or phases:
Pending Request is waiting to be run
Running Request is running
Completed Request has finished
Inactive Request cannot be run
Within each phase, a request's condition or status may change. Below appears a listing of each phase and the various states that a concurrent request can go through.
Concurrent Request Phase and Status
Phase Status Description
PENDING Normal Request is waiting for the next available manager.
Standby Program to run request is incompatible with other program(s) currently running.
Scheduled Request is scheduled to start at a future time or date.
Waiting A child request is waiting for its Parent request to mark it ready to run. For example, a report in a report set that runs sequentially must wait for a prior report to complete.
RUNNING Normal Request is running normally.
Paused Parent request pauses for all its child requests to complete. For example, a report set pauses for all reports in the set to complete.
Resuming All requests submitted by the same parent request have completed running. The Parent request is waiting to be restarted.
Terminating Running request is terminated, by selecting Terminate in the Status field of the Request Details zone.
COMPLETED Normal Request completes normally.
Error Request failed to complete successfully.
Warning Request completes with warnings. For example, a report is generated successfully but fails to print.
Cancelled Pending or Inactive request is cancelled, by selecting Cancel in the Status field of the Request Details zone.
Terminated Running request is terminated, by selecting Terminate in the Status field of the Request Details zone.
INACTIVE Disabled Program to run request is not enabled. Contact your system administrator.
On Hold Pending request is placed on hold, by selecting Hold in the Status field of the Request Details zone.
No Manager No manager is defined to run the request. Check with your system administrator.
What is the difference between Request group and request set ?
REQUESTS GROUPS AND REQUEST SETS
Reports and concurrent programs can be assembled into request groups and request sets.
1. A request group is a collection of reports or concurrent programs. A System Administrator defines report groups in order to control user access to reports and concurrent programs. Only a System Administrator can create a request group.
2. Request sets define run and print options, and possibly, parameter values, for a collection of reports or concurrent program. End users and System Administrators can define request sets. A System Administrator has request set privileges beyond those of an end user.
Standard Request Submission and Request Groups
Standard Request Submission is an Oracle Applications feature that allows you to select and run all your reports and other concurrent programs from a single, standard form. The standard submission form is called Submit Requests, although it can be customized to display a different title.
3. The reports and concurrent programs that may be selected from the Submit Requests form belong to a request security group, which is a request group assigned to a responsibility.
4. The reports and concurrent programs that may be selected from a customized Submit Requests form belong to a request group that uses a code.
In summary, request groups can be used to control access to reports and concurrent programs in two ways; according to a user's responsibility, or according to a customized standard submission (Run Requests) form.
This time too the focus of R12.1 is again some of existing product enhancements across human resources, supply chain management, procurement, projects, master data management, customer relationship management and financials.