Tutorials Oracle Apps Oracle Apps Concurrent Processing Oracle Apps Concurrent Processing - Page 2 Oracle Apps Concurrent Processing - Page 3 Oracle Apps Concurrent Processing - Page 4
The 3rd step in defining concurrent program is to define the parameters. To do this, click on the Parameters button as shown at the bottom the form in figure 4. The following screen (figure 5) is displayed when you click on parameters button. This screen is used to define the parameters in the concurrent program.
Figure 5. Parameter Window
i) Program – will be defaulted from Concurrent Program
ii) Application – will be defaulted from Concurrent Program
iii) Conflicts Domain - Enter the parameter which will hold the value of the conflict domain of the program.
iv) Security Group - This field is for HRMS security only.
v) Seq – Enter sequence number for the parameter
vi) Parameter – name of the parameter, will be displayed in parameter entry screen
vii) Description – description about the usage of the parameter
viii) Enabled – check box to enable or disable the parameter. Disable a parameter when you don’t want to use it.
ix) Value set – enter the name of the value set which you want to use to validate the value enter in the parameter field.
x) Description – will be defaulted from value set definition
xi) Default Type – choose the default type for the default value of the parameter. Possible default types are
xii) Display size – Enter the field length in characters for this parameter. The user sees and fills in the field in the Parameters window of the Submit Requests window.
xiii) Token - For a parameter in an Oracle Reports program, the keyword or parameter appears here. The value is case insensitive. For other types of programs, you can skip this field.
To navigate to this form, click on the Incompatibilities button on the bottom of the form shown in figure 4. This window is used for defining the incompatibilities of the concurrent program. Identify concurrent programs that should not run with your concurrent program as they might interfere with its execution.
Figure 6. Incompatibilities Form
i) Program – Defaulted from Concurrent Programs Window
ii) Application – Defaulted from Concurrent Programs Window
iii) Application – Application of the concurrent program which is incompatible to the defined concurrent program.
iv) Name – Name of the concurrent program which is incompatible to the defined concurrent program.
v) Scope – Used to identify if concurrent program is incompatible if the program or also with its child requests.
vi) Type - Enter Domain or Global. If you choose Domain, the incompatibility is resolved at a domain-specific level. If you choose Global, then this concurrent program will be considered globally incompatible with your concurrent program, regardless of which domain it is running in.
To navigate to this form, click on the Session Control button on the bottom of the form shown in figure 4. This is a new functionality given in 11.5.10 to control the database session while executing concurrent program using following three parameters. The form would look like as shown in figure 7.
Figure 7. Session Control Form
i) Consumer Group – resource consumer group of the concurrent program can be specified. A resource consumer group defines a set of users who have similar resource usage requirements. An overall resource plan specifies how resources are distributed among the different resource consumer groups. Resource consumer groups and resource plans provide a method for specifying how to partition processing resources among different users.
ii) Rollback Segment – Rollback segment specified here would be used instead of the default rollback segment. If you specify a rollback segment here, your concurrent program must use the APIs FND_CONCURRENT.AF_COMMIT and FND_CONCURRENT.AF_ROLLBACK to use the specified rollback segment.
iii) Optimizer mode - Optionally specify an optimizer mode. You can choose ALL_ROWS, FIRST_ROWS, Rules, or Choose. You would specify an optimizer mode only for a custom program that may not perform well with the default cost-based optimizer (CBO) and needs tuning. You can use a different optimizer mode until your program is tuned for CBO.
Next Page: Oracle Apps Concurrent Processing - Page 4
| Nice one |
| Good One |
| Very Informative.... Keep up the good work..... |
| A very good article for oracle developers those who work on development environment |
| your are excellent..... ;) |
| Very neatly explained step by step |
| Excellent Article very Good |
|
This material is gud, But give detailed description of each field Its better to learn more for beginners |
| Very Good site. Well laid out with good examples. Much easier to use than the official documentation. |
| Way the explanation is given, really useful for beginners and whoever wants to refresh their knowledge. |
| Good information. If will be even better if it includes how to set email notification should the concurrent process fails. |
| u can add the complete slide shots upto the report or forms execution in apps . thank you |
| Good informationm,can u give some more information like if a concurrent program is running from a long time,what may be the problem.Actually it has to complete the same in the minutes.So please can u clear me what may be the issue,and where we can have a look ... |
|
Hi, I am using java concurrent Program to call shell script. In Shell Scrip i want APPS user name and Password,to exucute SQLLoader Command. IF we use Host Conncurrent program, we getUSer name and password directly. any idea how i can get this in java concureent program. Thanks, Prashant |
