Document extraction

No core answer is documented.

Not covered: SAPUI5's own upload controls — UploadCollection, and its successor sap.m.plugins.UploadSetwithTable — move a file to the backend and list it as an attachment; neither reads what is inside one. Reaching SAP Document AISAP Document AIserviceExtracts 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 UI5 app is a manual sequence built on top of that: upload, poll the job, map the returned fields onto the screen.

Unmapped rather than core-only: SAP Document AISAP Document AIserviceExtracts 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 and lists cap, not ui5, in serves_ecosystems. Integrate Document Information Extraction into UI5 applicationIntegrate Document Information Extraction into UI5 applicationblogUploading an invoice from a UI5 application and getting the extracted fields back on screen, with a destination pointing at the Document Information Extraction API and a Refresh button polling until the job finishes. The polling is the honest part: extraction is asynchronous, and the post does not pretend otherwise. From 2022, so the service has since been renamed and the API moved, but the shape — upload, poll, map the result — is the shape it still is.published 2022-05-31, a 2022 post, documents the upload-poll-map sequence as something the app author wrote, not a control or plugin.