How to Debug GL FSG (Financial Statement Generator) Signal 10/Signal 11 Issues
(Doc ID 189275.1)
Last updated on AUGUST 08, 2024
Applies to:
Oracle General Ledger - Version 11.5 and laterInformation in this document applies to any platform.
Purpose
How to Debug FSG Signal10/Signal11 Issues ?
Scope
Technical and General Ledger functional users
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| 1. Set the profile 'FSG: Debug' to Y and run the FSG again |
| 2. Get on the Latest FSG Code . |
| 3. Are There Complex Structures For the Segment Value Relationships? |
| 4. Are There Multiple Row Assignments With Display Option 'E' or 'B' in the Same Row Assignment? |
| 5. Check the setting of the profile option "Maximum page length". |
| 6. A Signal 10/11 can also be caused by overlapping child values in a value set hierarchy. |
| 7. Eliminate excessive ranges being applied to a single row. |
| 8. Run Program - Optimizer with both parameters set to Yes (Gather Statistics and Maintain Indexes). Make sure this completes normally. |
| 9. Run Gather Schema Statistics for GL schema. |
| 10. If there are any warnings in the FSG log file, those must be resolved. |
| 11. When running the FSG for XML output: |
| 12. Additional causes in R12 for Signal 11 |
| 13. Additional cause on AIX for Signal 11 |
| 14. In Bug:14060143 FSG failed with signal 11 particular period and segment override value |
| 15. Check if text has been entered in the column heading which is outside any column in the report output. |
| References |