3632177 - Export File from BC Scoping is not Fully Compatible with Downstream JavaScript Logic

Customers who are transitioning to SAP S/4 Hana public cloud can transition their BC scope in BYD to S4 Scope Items via DDA, for this to happen user will have to export the Business Configuration scope in Implementation Projects work center view by using the export button in the step 3.

You are unable to upload the export file because the exported file is corrupted and inconsistency in metadata. 

• The system exports an Excel file (XLSX) that is of smaller (eg: 50KB) in size in Step 3 of Implementation Project view in Edit Scope.
• This file fails during downstream processing in a JavaScript-based application. : DDA Toolset
• However, when you open and save the same file in Microsoft Excel without making any changes, the file size increases to 83KB, and the downstream process then works successfully. Opening the file in Excel will trigger Excel to correct all the missing metadata that should’ve been generated by ByD.

SAP Business ByDesign

1. Go to Business Configuration work center
2. Highlight the Project 
3. Edit Project Scope
4. Export in excel in Scoping / Questions step

The exported template is for the Excel plugin, so that user can fetch latest data from system directly using the excel Add-in, the template is designed accordingly. Few application logic maintain their specific custom template for export and for others the file is generated virtually based on the master template and its styles.

This behaviour can vary and is as per design. It will not be possible to do changes in the core export logic. Also the issue is not happening with the import/export functionality.

If the file is being used for other purpose(data processing/imports) by other tools, formatting must be taken care accordingly.

KBA , AP-RC-BCT , Business Config. Tools (SAP Business ByDesign , Problem