Document manger runs within the CONCURRENT manager in Oracle Applications. When an application uses a Document Manager, it sends a PIPE signal which is picked up by the document manager.

There are two mechanisms by which to trace the document manager

• Set the debugging on by USING profile option
• STEP 1. Set profile option “Concurrent:Debug Flags” to TCTM1

This profile should only generate DEBUGS when set at Site level(I THINK, as I have only tried site), because Document Manager runs in a different session.

• STEP 2. Bounce the Document Managers
• STEP 3. Retry the Workflow to generate debugs.
• STEP 4. Reset profile option “Concurrent:Debug Flags” to blank
• STEP 5. have a look at debug information in table fnd_concurrent_debug_info

• Enable tracing for the document managers

This can be done by setting profile option “Initialization SQL Statement – Custom” against your username before reproducing the issue. The value of this profile will be set so as to enable trace using event 10046, level 12.

Document manger runs within the concurrent manager in Oracle Applications. When an application uses a Document Manager, it sends a pipe signal which is picked up by the document manager.

There are two mechanisms by which to trace the document manager

This profile should only generate debugs when set at Site level(I think, as I have only tried site), because Document Manager runs in a different session.

This can be done by setting profile option “Initialization SQL Statement – Custom” against your username before reproducing the issue. The value of this profile will be set so as to enable trace using event 10046, level 12.