Fiori Elements & file upload¶

Let a user (Fiori) or a system (API) send a spreadsheet file to your RAP BO and have its rows imported — with about two lines of your own code. The action runs parse → coerce → dynamic EML create with defer_commit (the RAP framework commits at the end of the OData request, so it's one synchronous call).

What the component ships¶

Wire it into your BO (3 steps)¶

1. Two action lines in your BO's behavior definition (the root entity's behavior):

   static action importExcel  parameter ZSSI_A_IMPORT            result [1] ZSSI_A_RESULT;
   static action importUpload deep parameter ZSSI_A_IMPORT_FILE  result [1] ZSSI_A_RESULT;
   

   Keep only importExcel for API‑only, or only importUpload for Fiori‑only.

2. One handler method per action in your behavior pool — generate it with zcl_ssi_adapter_gen=>generate_action( iv_entity = 'ZXX_R_BO' iv_alias = 'YourAlias' ), or write it by hand (each body is a single call):

   METHOD import_excel.   " FOR ACTION YourAlias~importExcel
     zcl_ssi_import_action=>execute( EXPORTING it_keys   = keys
                                               iv_entity = 'ZXX_R_BO'
                                     CHANGING  ct_result = result ).
   ENDMETHOD.
   

   (Pass an optional is_options to inject extension hooks or a mapping.)

3. Expose your BO via an OData V4 UI service (SRVD + SRVB). importExcel / importUpload surface as bound actions.

Calling it¶

POST .../YourEntity/<namespace>.importExcel
{ "FileContent":"<base64 of the xlsx/csv>", "IsCsv":true, "IsDraft":false,
  "ChunkSize":0, "DecimalSeparator":"", "HeaderRow":0 }

Option fields (on both parameters): IsCsv force CSV (else magic‑byte auto‑detect) · IsDraft create drafts · ChunkSize rows/LUW (0 = default 500) · DecimalSeparator '.'/',' · HeaderRow 1‑based header row. See Options & data types.

Surfacing the action in Fiori Elements (metadata extension)¶

In a Fiori Elements app the import action becomes a button in the table toolbar (and the upload parameter renders a file picker) via a CDS metadata extension (DDLX) on your projection view — no custom UI code. Conceptually:

@Metadata.layer: #CORE
annotate entity ZC_YourProjection with
{
  @UI.lineItem: [ { position: 10 } ]                       // a column …
  YourField;
}

// the action on the entity's toolbar:
@UI: { lineItem:        [ { type: #FOR_ACTION, dataAction: 'importUpload', label: 'Import Excel' } ],
       identification:  [ { type: #FOR_ACTION, dataAction: 'importUpload', label: 'Import Excel' } ] }

The 758 on‑prem Fiori upload caveat¶

On S/4HANA 2023 on‑prem, the base64 API channel is the universal, fully‑wired path. The Fiori importUpload control still renders a working Edm.Stream upload, but the mime‑type filter and file name are not auto‑bound in the dialog — a confirmed gateway framework‑version gap, not a modelling bug. The importer auto‑detects the file type from magic bytes regardless, so the import works either way.