Document extraction
Getting structured data out of a document somebody sent you — an invoice, a purchase order, a scanned form — instead of having a person key it in. The mirror image of document output, and a different problem from reading a service: the input is a file, the shape is unknown until something reads it, and the answer arrives with a confidence rather than a guarantee.
Showing artifacts, examples and content with confirmed Web Components applicability. View All UI5
Overview
No core answer is documented.
Not covered: Web Components' own upload control, ui5-file-uploader, opens a file picker and exposes the selection through its read-only files property; it moves a file into the page and reads nothing inside it, the same boundary SAPUI5's UploadCollection draws for the door as a whole. Reaching SAP Document AISAP Document AIExtracts header fields and line items from invoices, payment advices, purchase orders and custom document types, as structured data over a REST API — the extraction is the service's, the schema can be yours.sap official, btp from a Web Components app is the same manual sequence as elsewhere on the door: upload, poll the job, map the returned fields onto the screen.
Unmapped rather than not-applicable: the concern is not excluded by the layer's architecture the way routing or OData binding are, it is simply unbuilt here too. SAP Document AISAP Document AIExtracts header fields and line items from invoices, payment advices, purchase orders and custom document types, as structured data over a REST API — the extraction is the service's, the schema can be yours.sap official, btp has ecosystem btp, serves cap and carries no flavors, so it states no web-components.
No artifact is documented here yet.
Artifacts
Nothing is mapped here yet.
Details
Coverage
For your agent
- Ref
capability:document-extraction- JSON
- /capabilities/document-extraction.json
- MCP
- Connecting an agent