Importing and exporting table data

XCO_CP_XLSX reads and writes XLSX content held as an xstring, and CL_CSV_FACTORY creates writers that turn internal table content into CSV; both are among SAP's released ABAP classes.

Not covered: At converting content. Getting the file from a user, mapping its columns onto a target structure and checking values before they are written are left to the application; SAP's own example uploads through a generated Fiori elements preview.

SAP-samples repositories demonstrate the concern, a JSON uploader for SAP BTP ABAP Environment and an ALV export to Google Sheets; samples are not counted as providers. The community tools differ in where the file is handled: ABAP Spreadsheet ImporterABAP Spreadsheet ImporterpackageA server-side ABAP component that parses an uploaded XLSX or CSV file and creates instances of a named RAP business object through dynamic EML, so its validations and authorizations run on every row.community org, abap parses an uploaded XLSX or CSV file in the backend and creates its rows on a RAP business object, and abap2UI5 for Excelabap2UI5 for ExcelappAn Office add-in that runs an abap2UI5 app in Excel's task pane, where the app reads and writes the workbook through the z2ui5.cc.ExcelBridge control.community org, abap moves table data between an abap2UI5 app and the open workbook without a file. How these tools relate to the XCO classes has not been assessed.