Attention: Some Oracle Applications products provide, in addition to the Standard Request Submission windows, product-specific windows to submit certain reports and programs. Such a window automatically runs a report or a program as a concurrent process when you choose a specific button or save your work in the form.
The Post Journals window in the Oracle General Ledger application is an example of a window that submits a concurrent program to post journal entries when you choose the Post button. You should refer to the user’s guide for your Oracle Applications product to learn if your product uses any product-specific windows to submit reports or programs.
- Provides standard interface for running and monitoring reports.
- Single form to submit any request, concurrent program. Another form to see report’s progress and to review report online.
- Submit Request form: easy-to-use interface.
- Automatic Resubmission.
- Request Sets: define sets of reports, Submit an entire set at same time.
- Request Set options: Run order, printer, no. of copies etc.
- Request Set Log File:Single log file containing the completion status of all reports in set.
- Viewing Requests: Monitor report’s progress using View Request form.
- Child Request: or a sub-request submitted by any other concurrent request(Parent Request)
- Parameter: A value you specify when you run a request.
* A request set is parent request and all reports in set are child requests
Value Set: A set of values against which AOL validates values, the end user enters when running a concurrent program.
Controlling Access to Reports:
- Create related group of reports and request sets.
- Define responsibility and assign a report security group to that responsibility.
Request Sets:
- A collection of reports/programs that are grouped together. Allow to submit reports or programs in a request set all at once using a single transaction.
- Request set can be defined to submit requests depending on the completion status of previously submitted requests in the set.
Stage:
- Component of a request set used to group requests within a set. All requests in a stage are executed in parallel. Request set executes one stage at a time., following links from stage to stage.
- Links that are followed depend on the completion status of the individual stages. A stage completes when all the requests contained in the stage have completed.
- PL/SQL functions calculate the completion status of a stage
- Three status of a stage:
- Success
- Warning
- Error
Stage Evaluation function:
- Provided by AOL, computes the stage completion status from the completion statuses of the specified requests in set.
- Function returns a
- Success: If all requests completed with a status of “Success”.
- Warning: If one or more requests in set completed with warning and no request completed with error.
- Error: If any request in set completed with error.
Important: If you use summary accounts in your recurring journals, General Ledger maintains references to those summary account templates, even if you delete then recreate the summary accounts.
Latest Posts
- R12 – How to Handle NULL for :$FLEX$.VALUE_SET_NAME In Oracle ERPAugust 25, 2023 - 1:20 pm
- R12 – How to Delete Oracle AR TransactionsMarch 22, 2019 - 8:37 pm
- How to Define Custom Key Flexfield (KFF) in R12January 19, 2018 - 5:43 pm
- AutoLock Box Concepts In R12November 10, 2017 - 8:30 am
- R12 – java.sql.SQLException: Invalid column type in OAFSeptember 15, 2017 - 9:39 am
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
29 | 30 | 31 |
Recent Comments