Does anyone have any tips for determining what specifically is causing the PL/SQL Beautifier to generate the following error:

"PL/SQL Beautifier could not parse text"

The code appears to be syntactically correct and creates the database view as intended in a valid state.

Thank you for your suggestions.

Can you send the code to me?

If you run beautifier on the above code you get the error mentioned by Todd_emo.
If you select the code from 'select' until the end of the code then beautifier does his magic without complaints. In the above case (and my custom settings) it becomes (omitting the create line):

Yes, this happens for me too, and has been painful in the past. However I don't believe this is a bug. It is a PL/SQL beautifier, not a SQL beautifier. A create or replace DDL isn't a part of PL/SQL.

I do the same as above, I highlight the SELECT part and beautify that.

It would be a nice change to have the beautifier work on SQL scripts too however I have no complaints. The beautifier is by far the best feature of PLSD.

Do we have any news on this subject? I'm not able to "beautify" my views because of this error. The last answer is not complete from my point of view because, in your website, the description of the beautifier includes both SQL and PL/SQL codes: "The PL/SQL Beautifier allows you to format your SQL and PL/SQL code through a user-defined set of rules [...]"

The PL/SQL Beautifier can only process PL/SQL, as the name suggests. This includes SQL that is valid within PL/SQL, but not DDL statements like "create view".