Hope you haven't selected Report parameter as "No Report".

Create Accounting has mainly two templates.

Subledger Accounting Program Report - Standard inturn calls Subledger Accounting Program Report - Sub Template.
Subledger Accounting Program Report - Sub Template is a sub template and shouldn't be used while submiting the Create Accounting.

If the output is blank, the template needs to be crosschecked, which is available in the Options Button of the SRS window.

For Packages:

   SELECT text
   FROM   all_source
   WHERE  name = Upper('&package_name')
   AND line = 2;

   SELECT af.subdir, 
          af.filename, 
          afv.version 
   FROM   ad_files af, 
          ad_file_versions afv 
   WHERE  af.file_id = afv.file_id 
   AND af.filename = '&file_name';

Are you using MO view like ap_invoices?
  For all org_ids' data      -> Use ap_invoices_all
  For specific org_id's data -> 11i -> dbms_application_info.set_client_info(&org_id);
                                R12 -> mo_global.set_policy_context('S',&org_id);

gl_je_lines (je_header_id, je_line_num)                -> gl_import_references (je_header_id, je_line_num)

gl_import_references (gl_sl_link_table, gl_sl_link_id) -> xla_ae_lines (gl_sl_link_table, gl_sl_link_id)

xla_ae_lines (applicaiton_id, ae_header_id)            -> xla_ae_headers (application_id, ae_header_id)

xla_ae_headers (application_id, event_id)              -> xla_events (application_id, event_id)

xla_events (application_id, entity_id)                 -> xla.xla_transaction_entities (application_id, entity_id)

Create Accounting (with Transfer to GL parameter as Yes) will transfer only the journal entries to GL, which have been created by this Create Accounting run.
To transfer the jounral entries to GL, which have been accounted by other Create Accounting (with Transfer to GL parameter as No) run, Transfer Journal Entries to GL concurrent program needs to be run.

Online Accounting:
------------------
Draft will create journal entries, which are not final, which means they are not ready to be transferred to GL.
You can see the accounting in xla_ae_headers and xla_ae_lines.

When importing table that contained custom type, you will encounter an oracle error as shown below:
Import of table containing object type(s) fails with IMP-00061 IMP-00063

cause:
When you import a table that references a type, but a type of that name
already exists in the database. Import attempts to verify that the pre-existing
type is in fact the type used by the table(rather than a different type that
just happens to have the same name).

RMAN is recommended for backups/restore of oracle databases.It is a very powerful tool and has variety of useful features.There is 'checksyntax' feature in RMAN which allows one to check RMAN scripts syntactically without executing it.This feature is available from 10G release 2.It proves to be useful for checking scriptsfor live databases where one doesnt have leisure to execute scripts any time and any times!!

bash-3.00$ vi rman_bkp.rman

RUN {
ALLOCATE CHANNEL c1 TYPE DISK FORMAT '/data/backup/Hotbkp_Full_%D_%d_%s_%p'; BACKUP database; RELEASE CHANNEL c1;
allocate channel c2 type dis

Here’s an alternative to the union statement for creating a collection of values using the Oracle SQL Model construct in 10g.

[code]--Using SQL Model clause to return a list of items.

SELECT col_1 Product, col_2 Price, col_3 Description
FROM (SELECT -1 col_id,
RPAD ('X', 30) col_1,
TO_NUMBER(RPAD ('1', 3)) col_2,
RPAD ('X', 40) col_3
--Change RPAD number to reflect length of column value.
FROM DUAL)
WHERE col_id <> -1
MODEL
DI

Make Your SQL Statements Readable

Even though readability doesn't affect the actual performance of SQL statements, good programming practice calls for readable code. Readability is especially important if you have multiple conditions in the WHERE clause.