fusion_describe_table
Describe an Oracle Fusion table's columns, data types, and comments before querying to avoid column-name errors. Automatically resolves case-duplicate object names to return the accurate schema.
Instructions
Describe ONE Fusion object: ordered columns, data types, comments.
Call this before writing any query that names a column. Fusion column names rarely match the UI labels, and a wrong guess costs a full ORA-00904 round trip. Comments are populated on this pod and are genuinely informative.
The dual-object rule. This pod carries objects whose names differ only in
letter case -- FUSION.po_headers_all and FUSION.PO_HEADERS_ALL are two
distinct objects, and the dictionary lookup is case-insensitive, so a lookup
for one returns both. Presenting their union would show a 288-column table as
576 columns with every name duplicated: a wrong answer that looks like a right
one. So the rows are grouped by their exact (OWNER, TABLE_NAME) and exactly
one group is ever described:
If exactly one group spells its name the way you did (case-sensitive on the object, case-insensitive on the owner, since Oracle object names created with quotes really are case-sensitive), that group wins --
chosen_by: exact_name_match. Your spelling is the only unambiguous signal available.Otherwise the best-documented group wins --
chosen_by: most_documented: first a group that has a table comment, then the one with the most commented columns, then the most columns, then name order for determinism. On this pod the documented twin is the real transactional object; its namesake has no statistics and no comments. And it is decided from data the report already returned, so no extra round trip is needed.
Whenever more than one object matched, ambiguous is true, alternates
lists every object that was NOT described, and the summary leads with it. The
ambiguity is never resolved silently: if the choice is wrong, re-call with the
exact spelling you meant (table="po_headers_all").
Args:
table: Object name, optionally OWNER.OBJECT, e.g. AP_INVOICES_ALL.
Case is preserved and used for the tie-break above.
owner: Schema owner used when table is unqualified.
datasource: Legacy composed-SQL fallback only; ignored on the report path.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| owner | No | FUSION | |
| table | Yes | ||
| datasource | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||