Fonction SAP API_SEMBPS_SETDATA - Write Plan Data into the Buffer

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
I_AREA UPC_AREA-AREA C 8 Planning Area
I_LAYOUT UPP_PARAM-PARAM C 8 Parameter Group
I_PACKAGE UPC_PACKAGE-PPACKAGE C 8 Planning Package
I_PLEVEL UPC_PLEVEL-PLEVEL C 8 Planning Level

Paramètre Reférence Type Long. Description
E_SUBRC SYST-SUBRC I 4 Return Value, Return Value After ABAP Statements

Paramètre Reférence Long. Facultatif Description
ETK_RETURN BAPIRET2 548 X Return Parameter
ITK_DATA UPC_YS_API_DATA 79 Data
ITK_ROW UPC_YS_API_ROW 164 Description of Lines

Functionality
Data can be transferred to BW-BPS in a tabular prepared format. Notehere that with this module the data is only written in a data buffer,but is not yet updated in the database. However, all other modules ofAPI already 'see' this changed data. The module API_SEMBPS_POST is usedto update the data in the database.
As a rule, you read the data with the API module API_SEMBPS_GETDATA andchange it in a client application. However, it is not necessary to callup the module API_SEMBPS_GETDATA before. Data can also be directlytransferred to SEM-BPS with the module API_SEMBPS_SETDATA. Since inthis module, the tables on the header combination and the columncharacteristics are missing, this information is defined from theplanning package and the planning layout. For this reason, the clientapplication can only change data within existing rows or add new rows(compare here the execution for the import parameter itk_row).

Parameters

  • I_AREA: Planning area

  • I_PLEVEL: Planning level

  • I_LAYOUT: Planning layout

  • E_SUBRC: This return parameter contains the value 0, when the module
    • was processed withut errors, otherwise the value of the returnparameter is greater than 0.
    • ITK_ROW: The table contains the physical rows (itk_row-row) with their
      • characteristic values in external format and the appropriate texts onthe characteristic value. This table corresponds to the area of thelead columns in manual planning. The table can also contain new phyicalrows; then itk_data must be filled appropriately. These new rows aretaken into account by the system, as long as they are in the selectionof the planning package. Otherwise there is an error (e_subrc > 0). Newphysical rows are only taken into account when new rows could also becreated in manual planning. Compare here also the indicatores_info-insert in module API_SEMBPS_GETDATA. If phyiscal rows aremissing in the table itk_row, which were still delivered in the moduleAPI_SEMBPS_GETDATA, then the values in these rows are set to zero inall data columns. The texts on characteristic values in the itk_row areignored, this means no texts on characteristic values can be changedwith this module. Every characteristic value delivered in the itk_rowmust exist as valid master record.
      • ITK_DATA: The table contains per physical row and data column, the cell
        • value in external format. In addition in field itk_data-input it isdefined, whether the data cell is ready for input ( etk_data-input ='1' ) or not (etk_data-input = '0'). This indicator cannot be changed,since the system administers the ready for input status of a cell. Onlyready for input cells are taken into account in the retransfer ofvalues.
        • ETK_RETURN: This structure can contain a message. In the case E_SUBRC
          • <> 0 it contains an error message, in the case E_SUBRC = 0 aninformation message can be in this structure.
          The technical descriptions on characteristics in the tables above arethose, which are used in SAP BW. The 'dimension values', therefore thekey figure dimension, is an exception. This 'dimension' is treated as anormal 'characteristic' within the API modules API_SEMBPS_GETDATA,API_SEMBPS_SETDATA and API_SEMBPS_LAYOUT_GETDETAIL, although it doesnot exist as a characteristic in SAP BW. The string '_BKENNZAHL' isused as technical description for the dimension values within themodules API_SEMBPS_GETDATA and API_SEMBPS_SETDATA.