User Session Limits Profiles
There are two user Session profiles specify the limits on user session.
1) ICX: Session Timeout
This profile option tnforce and Inactivity timeout.
If user is not perform any operation for a time period ,the user session is disable.
Profile option is 0 or NULL the session time will never time out.
2) ICX: Limit time
This profile specify the obsolute max lenght of time in hours for user.
There are two user Session profiles specify the limits on user session.
1) ICX: Session Timeout
This profile option tnforce and Inactivity timeout.
If user is not perform any operation for a time period ,the user session is disable.
Profile option is 0 or NULL the session time will never time out.
2) ICX: Limit time
This profile specify the obsolute max lenght of time in hours for user.
Key flexfields provide a flexible way for the Oracle Applications to represent objects such as accounting codes, part numbers, job descriptions, and more
Benefits
1)Customize data fields to your meet your business needs without programming.
2)Customize your applications to conform to your current business for accounting codes, product codes, and other codes.
3)Query intelligent fields for very specific information.
4)Customize your applications to capture data that would not otherwise be tracked by your application.
5)A flexfield qualifier identifies a particular segment of a key flexfield.
Oracle Recommended : Do Not Use Database Tools to Modify Oracle Applications Data
Oracle provides powerful tools you can use to insert, update, and delete information in an Oracle 9i,10g database. But, if you use Oracle tools like SQL*Plus or Oracle Data Browser to modify Oracle Applications data, you risk destroying the integrity of your data and you lose the ability to audit changes to your data.
Because Oracle Applications tables are interrelated, any change you make using an Oracle Applications form can update many tables at once. But when you modify Oracle Applications data using anything other than Oracle Applications forms, you may change a row in one table without making corresponding changes in related tables.
When you use Oracle Applications forms to modify your data, Oracle Applications automatically checks that your changes are valid. Oracle Applications also keeps track of who changes information. But, if you enter information into database tables using database tools, you may store invalid information
Warning: Oracle Applications does not support any customization of Oracle Application Object Library tables or modules, even by Oracle consultants. Oracle Application Object Library table names begin with "FND_". (Foundation)
Do not write data directly into or change data in FND_ tables through any custom program or using any tool, including SQL*Plus, Oracle Data Browser, database triggers or other programming tools. You risk corrupting your database and damaging all your applications
ORACLE STRONGLY RECOMMEND that you never use SQL*Plus, Oracle Data Browser, database triggers, or any other tool to modify Oracle Applications tables, unless we tell you to do so in our installation, implementation, or open interface guides.
Setting Character-Mode vs. Bitmap Printing
Character mode Oracle Reports programs take their page dimensions and orientation from the print style associated with the request to run the program. Some print styles are predefined, and a System Administrator can define additional styles, if necessary.
Running Bitmap Oracle Reports Concurrent Programs
To run an Oracle Reports program in bitmap mode, query the concurrent program's definition in the Concurrent Programs form, and enter"VERSION=2.0b" in the Execution Options field. This defines the program to use the bitmap version of Oracle Reports. Bitmap Oracle Reports programs take their page dimensions and orientation from the program's definition (note: when printing a bitmap report, a print style is still required). If you wish to override the program's definitions, you can enter values in the Execution Options field for ORIENTATION and PAGESIZE. When entering more than one execution option, each option should be separated by a single space. There should be no spaces before or after the options.
For example: VERSION=2.0b ORIENTATION=LANDSCAPE PAGESIZE=7.5x9
Notes about PAGESIZE in the Execution Options field
In Oracle Reports, when defining a report the units and size of the report are specified in the report settings.
For bitmapped reports, x for PAGESIZE is usually in inches; however, this depends on the particular report definition.
You can enter the PAGESIZE parameter in the Execution Options field of the Concurrent Programs form (for bitmapped reports only) when you want to override the values specified in the report definition.
For example: VERSION=2.0b PAGESIZE=7.5x9
If the dimensions specified with the PAGESIZE parameter are smaller than what the report was designed for, you will generate a "REP-1212" error.
Character mode Oracle Reports programs take their page dimensions and orientation from the print style associated with the request to run the program. Some print styles are predefined, and a System Administrator can define additional styles, if necessary.
Running Bitmap Oracle Reports Concurrent Programs
To run an Oracle Reports program in bitmap mode, query the concurrent program's definition in the Concurrent Programs form, and enter"VERSION=2.0b" in the Execution Options field. This defines the program to use the bitmap version of Oracle Reports. Bitmap Oracle Reports programs take their page dimensions and orientation from the program's definition (note: when printing a bitmap report, a print style is still required). If you wish to override the program's definitions, you can enter values in the Execution Options field for ORIENTATION and PAGESIZE. When entering more than one execution option, each option should be separated by a single space. There should be no spaces before or after the options.
For example: VERSION=2.0b ORIENTATION=LANDSCAPE PAGESIZE=7.5x9
Notes about PAGESIZE in the Execution Options field
In Oracle Reports, when defining a report the units and size of the report are specified in the report settings.
For bitmapped reports, x for PAGESIZE is usually in inches; however, this depends on the particular report definition.
You can enter the PAGESIZE parameter in the Execution Options field of the Concurrent Programs form (for bitmapped reports only) when you want to override the values specified in the report definition.
For example: VERSION=2.0b PAGESIZE=7.5x9
If the dimensions specified with the PAGESIZE parameter are smaller than what the report was designed for, you will generate a "REP-1212" error.
Managing Concurrent Processing Files
The database tables that are affected by running the Purge Concurrent Request and/or Manager Data program are:
FND_CONCURRENT_REQUESTS
This table contains a complete history of all concurrent requests.
FND_RUN_REQUESTS
When a user submits a report set, this table stores information about the reports in the report set and the parameter values for each report.
FND_CONC_REQUEST_ARGUMENTS
This table records arguments passed by the concurrent manager to each program it starts running.
FND_DUAL
This table records when requests do not update database tables.
FND_CONCURRENT_PROCESSES
This table records information about Oracle Applications and operating system processes.
FND_CONC_STAT_LIST
This table collects runtime performance statistics for concurrent requests.
FND_CONC_STAT_SUMMARY
This table contains the concurrent program performance statistics generated by the Purge Concurrent Request and/or Manager Data program. The Purge Concurrent Request and/or Manager Data program uses the data in FND_CONC_STAT_LIST to compute these statistics.
The database tables that are affected by running the Purge Concurrent Request and/or Manager Data program are:
FND_CONCURRENT_REQUESTS
This table contains a complete history of all concurrent requests.
FND_RUN_REQUESTS
When a user submits a report set, this table stores information about the reports in the report set and the parameter values for each report.
FND_CONC_REQUEST_ARGUMENTS
This table records arguments passed by the concurrent manager to each program it starts running.
FND_DUAL
This table records when requests do not update database tables.
FND_CONCURRENT_PROCESSES
This table records information about Oracle Applications and operating system processes.
FND_CONC_STAT_LIST
This table collects runtime performance statistics for concurrent requests.
FND_CONC_STAT_SUMMARY
This table contains the concurrent program performance statistics generated by the Purge Concurrent Request and/or Manager Data program. The Purge Concurrent Request and/or Manager Data program uses the data in FND_CONC_STAT_LIST to compute these statistics.
Example of $FLEX$ Syntax
Here is an example of using :$FLEX$.Value_Set_Name to set up value sets where one segment depends on a prior segment that itself depends on a prior segment ("cascading dependencies"). Assume you have a three-segment flexfield where the first segment is car manufacturer, the second segment is car model, and the third segment is car color. You could limit your third segment's values to only include car colors that are available for the car specified in the first two segments. Your three value sets might be defined as follows:
Segment Name Manufacturer
Value Set Name Car_Maker_Name_Value_Set
Validation Table CAR_MAKERS
Value Column MANUFACTURER_NAME
Description Column MANUFACTURER_DESCRIPTION
Hidden ID Column MANUFACTURER_ID
SQL Where Clause (none)
Segment Name Model
Value Set Name Car_Model_Name_Value_Set
Validation Table CAR_MODELS
Value Column MODEL_NAME
Description Column MODEL_DESCRIPTION
Hidden ID Column MODEL_ID
SQL Where Clause WHERE MANUFACTURER_ID =
:$FLEX$.Car_Maker_Name_Value_Set
Segment Name Color
Value Set Name Car_Color_Name_Value_Set
Validation Table CAR_COLORS
Value Column COLOR_NAME
Description Column COLOR_DESCRIPTION
Hidden ID Column COLOR_ID
SQL Where Clause WHERE MANUFACTURER_ID =
:$FLEX$.Car_Maker_Name_Value_Set
AND MODEL_ID =
:$FLEX$.Car_Model_Name_Value_Set
In this above example, MANUFACTURER_ID is the hidden ID column and MANUFACTURER_NAME is the value column of the Car_Maker_Name_Value_Set value set. The Model segment uses the hidden ID column of the previous value set, Car_Maker_Name_Value_Set, to compare against its WHERE clause. The end user never sees the hidden ID value for this example.
Here is an example of using :$FLEX$.Value_Set_Name to set up value sets where one segment depends on a prior segment that itself depends on a prior segment ("cascading dependencies"). Assume you have a three-segment flexfield where the first segment is car manufacturer, the second segment is car model, and the third segment is car color. You could limit your third segment's values to only include car colors that are available for the car specified in the first two segments. Your three value sets might be defined as follows:
Segment Name Manufacturer
Value Set Name Car_Maker_Name_Value_Set
Validation Table CAR_MAKERS
Value Column MANUFACTURER_NAME
Description Column MANUFACTURER_DESCRIPTION
Hidden ID Column MANUFACTURER_ID
SQL Where Clause (none)
Segment Name Model
Value Set Name Car_Model_Name_Value_Set
Validation Table CAR_MODELS
Value Column MODEL_NAME
Description Column MODEL_DESCRIPTION
Hidden ID Column MODEL_ID
SQL Where Clause WHERE MANUFACTURER_ID =
:$FLEX$.Car_Maker_Name_Value_Set
Segment Name Color
Value Set Name Car_Color_Name_Value_Set
Validation Table CAR_COLORS
Value Column COLOR_NAME
Description Column COLOR_DESCRIPTION
Hidden ID Column COLOR_ID
SQL Where Clause WHERE MANUFACTURER_ID =
:$FLEX$.Car_Maker_Name_Value_Set
AND MODEL_ID =
:$FLEX$.Car_Model_Name_Value_Set
In this above example, MANUFACTURER_ID is the hidden ID column and MANUFACTURER_NAME is the value column of the Car_Maker_Name_Value_Set value set. The Model segment uses the hidden ID column of the previous value set, Car_Maker_Name_Value_Set, to compare against its WHERE clause. The end user never sees the hidden ID value for this example.
Concurrent Request Phase and Status
The Concurrent Requests window displays a phase and status summary for each concurrent request listed
A concurrent request has a life cycle consisting of the following phases: pending, running, completed, and inactive.
During each phase, a concurrent request has a specific condition or status. lists each phase/status combination and describes its meaning in relation to a request.
If a request is pending, you can determine when it will start by using the Concurrent Managers For the Request window from the Requests window to review the request's position in the queues of current managers that can run that request.
The Concurrent Requests window displays a phase and status summary for each concurrent request listed
A concurrent request has a life cycle consisting of the following phases: pending, running, completed, and inactive.
During each phase, a concurrent request has a specific condition or status. lists each phase/status combination and describes its meaning in relation to a request.
If a request is pending, you can determine when it will start by using the Concurrent Managers For the Request window from the Requests window to review the request's position in the queues of current managers that can run that request.
| 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 request in a request set that runs sequentially must wait for a prior request to complete | |
| RUNNING | Normal | Request is running normally |
| Paused | Parent request pauses for all its child requests to finish running. For example, a request set pauses for all requests in the set to complete. | |
| Resuming | All requests submitted by the same parent request have completed running. The Parent request resumes running. | |
| Terminating | Request is terminated by choosing the Cancel Request button in Requests window | |
| COMPLETED | Normal | Request completed successfully. |
| Error | Request failed to complete successfully | |
| Warning | Request completed with warnings. For example, a request is generated successfully but fails to print | |
| Cancelled | Pending or Inactive request is cancelled by choosing the Cancel Request button in the Requests window. | |
| Terminated | Request is terminated by choosing the Cancel Request button in the Requests window. | |
| Inactive | Disabled | Program to run request is not enabled. Contact your system administrator. |
| On Hold | Pending request is placed on hold by choosing the Hold Request button in the Requests window. | |
| No Manager | No manager is defined to run the request. Check with your system administrator. A status of No Manager is also given when all managers are locked by run-alone requests. |
Locate Trace file and Enviroment files from Front End
After completing traceinge, You can find the Trace file location path by using following methods
Method 1) select value from v$parameter
where name ='user_dump_dest'
The above Query returns Trace file location Path.
Method 2) Login As sysadmin
Click at Goto ->OAM->OAM Setup->Site MAP->Monitoring->System Configuration-> Databse Init.ora Setting.
Here You can find out Parameter name as user_dump_dest , utl_file_dir and corresponding values.
After completing traceinge, You can find the Trace file location path by using following methods
Method 1) select value from v$parameter
where name ='user_dump_dest'
The above Query returns Trace file location Path.
Method 2) Login As sysadmin
Click at Goto ->OAM->OAM Setup->Site MAP->Monitoring->System Configuration-> Databse Init.ora Setting.
Here You can find out Parameter name as user_dump_dest , utl_file_dir and corresponding values.
1 comment:
SeconF, ask For case experiments, reFerrals, anF practical experience while in the locations that you will neeF aiF in. UnFer no circumstances rent a marketing anF aFvertising consultant FevoiF oF making contact with shopper reFerral[url=http://www.maggiesotterodresses2013.com/]maggie sottero wedding dresses 2013[/url]
We coulF possibly get extremely exciteF with regarF to the revenue presentation anF the brochure printing we have been hanFeF with when searching For a guiFe.
|
Post a Comment