Profile Options for Concurrent Manager (CM) in Oracle Applications

This post provides a list of profile options available for Concurrent Manager (CM) in Oracle Applications and their respective functionalities.
1. Concurrent: Active Request Limit
Value: Numeric
Description: Limits the number of concurrent requests a user can run simultaneously. If left blank, there is no restriction.
2. Concurrent: Attach URL
Values: YES / NO
Description: Attaches a URL to request completion notifications, allowing users to access request results directly.
3. Concurrent: Collect Request Statistics
Values: YES / NO
Description: Enables runtime statistics collection for concurrent requests.
4. Concurrent: Conflicts Domain
Values: List of available domains
Description: Defines the domain where program incompatibilities must be resolved.
5. Concurrent: Debug Flags
Description: Enables debugging for transaction managers.
6. Concurrent: Directory for Copy
Description: Specifies a directory for storing report output or log file copies when a copy operation is requested.
7. Concurrent: Enable Request Submission in View Mode
Values: YES / NO
Description: Allows users to submit new requests from the Find Requests form (FNDRSRUN).
8. Concurrent: Hold Requests
Values: YES / NO
Description: Automatically places requests on hold after submission.
9. Concurrent: Multiple Time Zones
Values: YES / NO
Description: Ensures immediate request scheduling regardless of client session time zone.
10. Concurrent: PMON Method
Description: Internal profile option related to Process Monitor (PMON). Cannot be viewed or updated.
11. Concurrent: Report Access Level
Values: RESPONSIBILITY / USER
Description: Defines access permissions for concurrent program report outputs and logs.
12. Concurrent: Report Copies
Value: Numeric
Description: Specifies the default number of copies printed for each submitted request.
13. Concurrent: Request Priority
Value: Numeric
Description: Assigns priority to requests, overriding start time scheduling.
14. Concurrent: Request Start Time
Value: Date/Time
Description: Defines when requests should start running.
Example: 31-MAR-2025 13:00 (Starts at 1:00 PM on March 31, 2025).
15. Concurrent: Save Output
Values: YES / NO
Description: Determines whether concurrent request output is saved to a file.
16. Concurrent: Sequential Requests
Values: YES / NO
Description: Forces concurrent requests to execute in sequence.
17. Concurrent: Show Requests Set Stages
Values: YES / NO
Description: Displays request set stages in concurrent request screens.
18. Concurrent: Show Requests Summary After Each Request Submission
Values: YES / NO
Description: Displays the Request Summary (FNDRSRUN) form after submission. Set to NO if submitting multiple requests.
19. Concurrent: URL Lifetime
Value: Numeric
Description: Defines how long the request output URL remains active.
20. Concurrent: Use ICM (Internal Concurrent Manager)
Values: YES / NO
Description: Determines whether the Internal Concurrent Manager (ICM) should resolve request conflicts.
21. Concurrent: Wait for Available TM
Value: Numeric (Minutes)
Description: Specifies the time a client will wait for a Transaction Manager (TM) before trying another TM.