Using Debug mode (GMF_CONC_DEBUG) to analyze OPM Financial Processes
(Doc ID 230743.1)
Last updated on DECEMBER 09, 2020
Applies to:Oracle Process Manufacturing Financials - Version 11.5.9 to 12.2 [Release 11.5 to 12.2]
Information in this document applies to any platform.
Executable:GMCACOST - OPM Actual Cost Process (Rel 11i)
Executable:GMCROLL - OPM Cost Rollup Process (Rel 11i)
Executable:GMGUPD - OPM Subledger Update
Executable:GMFACOST - OPM Actual Cost Process (Rel 12)
Executable:GMFROLL - OPM Cost Rollup Process (Rel 12)
Executable:GMFXUPD - OPM Accounting Pre-Processor
The purpose of this document is to summarise the use of the GMF_CONC_DEBUG Profile Option in relation to the Oracle Process Manufacturing Financials (GMF) concurrent processes, for example :
Cost Rollup - GMCROLL / GMFROLL
Actual Costing - GMCACOST / GMFACOST
Subledger Update (Rel 11i) - GMGUPD
Accounting Pre-Processor (Rel 12) - GMFXUPD
Please note that for convenience we will refer to the Profile Option throughout this article by its internal name ('GMF_CONC_DEBUG') because the seeded values of the external name can vary :
Rel 11i : "GMF: Debug Log Level"
Rel 12 : "GMF: Concurrent Debug Flag"
Indeed, if the Profile Option was created manually in your system in the past, the external name may have been set to some other value completely. In any version of Applications Release 11 or 12
you can use the following SQL*Plus statement to show :
- if the Profile Option exists, and if it does
- what external name has been given to it
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!