I'm happy to put my hand up for discussing / presenting some PL/SQL stuff and/or performance from a developer's perspective.
I've been chugging through Steven F.'s book and picked up some good stuff.

Connor McDonald would be Australia's Mr PL/SQL (despite a website of www.oracledba.co.uk), but he's in Perth and there's a big gap between east and west coasts.

I saw him present in Melbourne a few years back and it is....breath-taking. You can get his slides from last year's talk at Melbourne. All 700 of them, presented over a single morning. Click-click-click. Its a unique style, but works well.

There's a lot of PL/SQL that is simply control structures (loops, if/then.. etc) around SQL statements (possibly the more complicated stuff like multi-table inserts) or chopping around variables with functions that are pretty similar to SQL functions, mostly using SQL datatypes. Connor's book and Steven Feuerstein's both consider SQL as the foundation for PL/SQL.

I'd guess the main complications particular to PL/SQL are
1. Exception handling and propagation
2. Record types and collections.
3. Dynamic SQL
4. Triggers (and why not to use them)
5. Built-in packages like DBMS_JOB, UTL_FILE, UTL_HTTP etc.

What sort of problems does EBS throw up in PL/SQL ? Is it performance related, session-state, something else
And do they wrap their PL/SQL ?

  Gary