Start of Content Area

Procedure documentation Generating Master and Transaction Data

Use

You generate master and transaction data as follows: The sample data tables delivered by SAP in client 000 are read and written into the data tables of the SAP Business Information Warehouse (SAP BW) belonging to the characteristics that you enter in the data transfer described later. Which specific SAP BW System is concerned here, results from the assignment of InfoCubes to the planning area, which you enter during the data transfer. Since the import for several planning areas can be started simultaneously, it can also occur here that data is imported into different BW Systems in one single operation.

Note

It is important that you transfer the planning objects into the production client first, and then generate master and transaction data afterwards. When transferring sample data, you must enter for which planning area data should be generated. Therefore, the planning areas of the planning applications must already be available before you can generate data for them. For more information, see Transferring Planning Objects into the Production Clients.

Prerequisites

You have transferred the delivered planning objects into the production client of your system.

Procedure

...

       1.      Log onto the system in which you operate SEM-BPS in the production client.

       2.      In the SAP menu, choose Tools ® ABAP Workbench ® Development ® ABAP Editor.

       3.      Enter UPB_DATA_IMPORT in the Program field and choose This graphic is explained in the accompanying text Execute.

You get to the Planning Applications: Import of Delivered Data screen. Client 000 is predetermined as the source client, since the sample data delivered by SAP is stored there in the system structure.

You can recognize which type of data was delivered in the context of a planning area by the way the entries are presented in the hierarchical list:

·         If transaction data was delivered on a planning area, then the row with the name of the planning area is highlighted in the list, and the number of available data records is entered in the Data Records column.

·         If master data was delivered on a characteristic of a planning area, then the row with the name of the characteristic is highlighted in the list, and the number of available characteristic values is entered in the Data Records column.

·         If no data is available on a list entry (planning area or characteristic) then the corresponding row is not highlighted and nothing is entered in the Data Records column.

       4.      For every planning area displayed in the list, enter which data you want to import into your SAP BW System:

To import transaction data, select the checkbox next to the name of the planning area.

To import master data, select the checkbox next to the name of the characteristic. You can choose whether only those values should be transferred, which are not yet available in your SAP BW System, or whether you want to transfer all characteristic values delivered as master data.  In the second case select the checkbox in the Overwrite column.

Note

If you only want to import transaction data and no master data, but the characteristic values contained in the transaction data are not yet available in your BW System, then the missing master data is automatically generated. Though the system cannot create any texts for characteristic values generated in this way.

Note

You can find out which planning areas belong to which planning application in the table in the section Generating Sample Data.

       5.      Choose This graphic is explained in the accompanying text Program ® Execute to start importing data.

The system imports the data you specified from the source client and posts the data in the Business Information Warehouse. You receive a log with the results.

Result

The master and transaction data that you generated is available in the SAP BW System and can be used by the planning applications for demonstration purposes in the production client.

The generated transaction data concerns the actual data for fiscal year 2000 and fiscal year variant K4.

 

 

End of Content Area