An Oracle Fusion invoice descriptive flexfield query retrieves custom information attached to the invoice. A descriptive flexfield, commonly called a DFF, extends the standard business record. Its available segments and contexts depend on the configuration deployed in your Oracle environment.
Resolve one invoice using its number with the relevant supplier and business unit. Keep the returned item link and its resource key. The invoice investigation guide explains how to establish the intended invoice before reading its related records.
The header flexfield collection has the form GET /fscmRestApi/resources/11.13.18.05/invoices/{invoiceKey}/child/invoiceDff. Obtain the key from the selected invoice response. Oracle exposes invoiceDff within the invoice resource definition. Invoice header flexfields and line flexfields are separate resources.
Inspect the metadata for the deployed flexfield before naming a custom attribute in a request. A label displayed to an AP user may differ from the REST attribute name. An attribute from another customer's environment is not evidence that the same segment exists in yours.
This CLHAPI flexfield-metadata SQL selects the invoice header flexfield AP_INVOICES. It removes the original tenant-specific context filter so you can inspect the configured contexts. Oracle documents the columns in FND_DF_SEGMENTS_B.
SELECT application_id,
descriptive_flexfield_code,
context_code,
segment_code,
segment_identifier,
column_name,
sequence_number,
enabled_flag
FROM fnd_df_segments_b
WHERE descriptive_flexfield_code = 'AP_INVOICES'
ORDER BY application_id, context_code, sequence_number, segment_code;The result describes segment configuration rather than values stored on an invoice. COLUMN_NAME identifies a storage column; it does not by itself establish the REST attribute name. Confirm the enabled segment, context and deployed REST metadata before reading invoice values.
Check the returned context and determine which segments apply to it. Context-sensitive segments can have different meanings from global segments. Keep the context with the exported values so a consumer does not interpret an attribute using the wrong business definition.
For an empty or null result, verify the selected invoice and deployed configuration before diagnosing missing data. The field might be unused for that invoice or available under another context. Account permissions can also limit visibility. Compare the same record in Oracle under the same access scope.
When exporting, select only the confirmed attributes required by the consumer. Preserve dates and identifiers using the documented types. Do not silently turn a missing value into a business default. The absence of a payment reference, for example, needs an explicit rule in the downstream process.
Fusion Toolkit's invoice-full-investigation recipe includes the supported invoice flexfield read. Custom attributes require validated tenant metadata before they can be used in a governed change. A successful lookup does not authorize an update. Review the Swiss QR-bill mapping example for a workflow where that distinction matters.
The workflow was reviewed on 8 November 2026. Confirm one deployed segment and one test invoice before widening the export to a production population.
You can also use an LLM with the Fusion Toolkit AI Administrator skill and ask, "Show the descriptive flexfield values for invoice DEMO-INV-1042 and explain which context they use." It can inspect supported Oracle data in plain language without requiring you to write the query. Provide the supplier and business unit to identify the invoice.