BPC 7.5 - Data Manager filling tablespace

Question

We are installing a brand new BPC for NW 7.5 SP4 system.  When trying to import data from .txt files via the data manager, the system is generating /1CPMB/DM0000xxx (example /1CPMB/DM0000001) tables.  The problem is these tables are being generated with a size category of 9.  This defaults to a next extent of 320MB.  This is on an Oracle-based backend BI 701 system with Dictionary-based tablespace.
If you only upload 1-2 records, then it falls under the initial extent of 16KB.  But if you upload enough records to get past that initial extent, then it will blow up and take up 320MB of space, most of it being wasted.
We've engaged SAP Support and thus far they have not been able to provide a means to have these tables generated with a lower size category, such as 1, or any other work-around to this issue.
Initially, we were trying to load 60-100 smaller datafiles.  But seeing how BPC is dealing with them by wasting so much space, we are looking at combining the number of files to a smaller number.  If not, you could theoretically try to take up 32TB of space.
We can reorg the tables after the fact, but that doesn't help the newly generated tables every time we upload a file using data manager.
1) Login to BPC for Netweaver website
2) Go into the excel portion
3) log into the applicationset
4) click on edata at the top of the screen
5) select upload data file
6) enter source and target locations. the file is a .txt file (40KB in
size)
7) click OK to start the
upload
*error*
Any thoughts?

Answer 1

Further digging, the tables are hardcoded by SAP code to default to a size category of 9...
class:
CL_UJF_FILE_SERVICE_MGR
  METHOD upload_document_dm.
    TRY .
        lo_file_service_mgr->put_document_data_mgr(
                    EXPORTING i_docname     = lv_docname
                              i_append      = lv_append
                              i_doc_content = lt_content
                              i_content_delivery = im_is_cd ).
      CATCH cx_ujf_file_service_error INTO lo_exception.
        imess = convert_ex_to_message( lo_exception ).
        IF imess IS NOT INITIAL.
          READ TABLE imess INTO xmess INDEX 1.
          MESSAGE e001(00) WITH xmess-message.
        ENDIF.
    ENDTRY.
method:
PUT_DOCUMENT_DATA_MGR
If document is found, that means that there is probably
a database table already created,
  CASE me->is_document_found( ).
    WHEN abap_true.
      lv_tabname = me->ds_document-doc_content_db.
    WHEN abap_false.
Check if this call is for content delivery, if so, then generate the table using
a different name space, otherwise use the default naming  for data manager files.
      CASE i_content_delivery.
        WHEN abap_false.
          lv_tabname = do_file_service_dao->generate_doc_content_table( i_namespace = 'DM' ).
        WHEN abap_true.
          lv_tabname = do_file_service_dao->generate_doc_content_table( i_namespace = 'CD' ).
      ENDCASE.
  ENDCASE.
method:
generate_doc_content_table
Add header and technical settings
  CLEAR ls_dd02v.
  ls_dd02v-tabname    = lv_tabname.
  ls_dd02v-ddtext     = lv_ddtext.
  ls_dd02v-ddlanguage = sy-langu.
  ls_dd02v-tabclass   = 'TRANSP'.
  ls_dd02v-contflag   = 'A'.
  ls_dd02v-exclass    = '1'.
  CLEAR ls_dd09v.
  ls_dd09v-tabkat     = '9'.
  ls_dd09v-tabart     = 'APPL1'.
  ls_dd09v-pufferung  = space.
  ls_dd09v-bufallow   = space.