2014.

From time to time it happens that the source system delivers special characters and the Business Warehouse system can not handle it. So the loading process may be crashed.

One solution is the following ABAP code:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19

DATA:
  zeichen(1) TYPE c,
  muster(2) TYPE c,
  field TYPE c LENGTH 000060.
  field = SOURCE_FIELDS-YYSTREET.

DO.
  IF field CO ' !"%&()*+,-./:;<=>?_0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZÄÖÜßabcdefg' && 'hijklmnopqrstuvwxyzäöü '.
    EXIT.
  ELSE.
    zeichen = field+sy-fdpos(1).
    muster+0(1) = zeichen.
    muster+1(1) = space.
    TRANSLATE field USING muster.
  ENDIF.

ENDDO.

RESULT = field.

While checking or activation of an InfoSet the BW System generates the following Dump:

"UNCAUGHT_EXCEPTION" CX_RS_INPUT_INVALID

"CL_RSQ_ISET_APPEND ============ CP"

"SPLIT_APPENDNM_FALIAS"

Solution: This is a program error and by installing the SAP Note 1970282 resolve this issue.

Unfortunately, SAP export negative numbers like "Number-":

There is a SAP Note which was released 2009. This Note shows how to change key figures of an InfoProvider, even though they are used. The Note is 579342.

1. Transaction rsa1 or rsdcube
2. Menu >> Extras
   
3. Select "Unlock InfoObjects"
   

The following source code allows you to connect your DataSource to a BW system. The workbook must contain a DataSource (DS_1). At this moment you can't open a workbook like BEx 3.5 or 7.0. In Analysis for Office 2.3 you have now the option to open a workbook with the function SAPOpenWorkbook.

When the BEx Query Designer crashes while you are creating or modify a query, the user lock this query in the database. You can remove the lock with the Transaction sm12 and erase the entry.

1. Open TA sm12
2. Click list
3. Select the required entry
4. Click delete

From time to time it is necessary to replicate DataSources from other SAP systems, eg if the DataSource has changed in the source system. To replicate a DataSource, use the transaction rsa1.

1. Open the TA rsa1
2. Search for your InfoSource
3. Right-click on the InfoSource and replicate DataSource
4. Change and activate DataSource
5. Replicate DataSource again

Now the DataSource can be used.

Query to Read All Data at Once

Advantages:

• query navigation after first call very quickly as data completely present in OLAP cache

Disadvantages:

• Initial call slow
• Using characteristics aggregates greatly restricted
• Large memory requirement in the OLAP cache

Recommendation:

• Using the read mode only for small InfoCubes
• Using the read mode only in queries with a few free characteristics

Query to Read Data During Navigation

Advantages:

• Good hit rate in characteristic aggregates
• Quick response times for small hierarchies

Disadvantages:

• Waiting period required in successive runs when selection is not identical to Initial call

Recommendation:

• Using the read mode for small hierarchies
• Using the read mode for large result sets

Query to Read When You Navigate or Expaned Hierarchies

Advantages:

• Initial call of the query quickly because only the necessary data is selected

Disadvantages:

• Selects the least amount of data in the Initial call, so read access to database with modified navigation required

Recommendation:

• Using the read mode when hierarchy aggregates required

In 7.0 and 3.5 you can open workbooks via VBA. This is useful if you want to automate reporting. The command for BEx Analyzer is:

If you want to import source code from a text file, you can use the following code.

If you want to start a Process Chain and you maybe haven't got the rights in the BW, you can start a Process Chain by VBA. Use the following source code:

If you have created your own SAP function module, you can use this with the following VBA code.

Sub FunctionModule()

'Variables Definition

Dim MyFunc As Object

Dim E_INSERTED As Object

Dim E_MODIFIED As Object

Dim DATA As Object

Set MyFunc = R3.Add("Z_RSDRI_UPDATE_LCP") 'FunctionModule Name in SAP BW

Set E_INSERTED = MyFunc.imports("E_INSERTED") 'InsertFunction in SAP BW

Set E_MODIFIED = MyFunc.imports("E_MODIFIED") 'ModifyFunction in SAP BW

Set DATA = MyFunc.tables("I_T_DATA") 'Table to store data and write to BW.

'Add data

DATA.Rows.Add 'add new data

rowDATA.Value(1, 1) = Sheet1.Cells(1, 10).Value 'First Cell of the data table is filled with the value from Sheet1.Cells(1,10)

'Call Insert or Modify

Result = MyFunc.CALL

'Message to the User

If Result = True Then

MsgBox "Insert Rows: " & E_INSERTED.Value & " Modify Rows: " & E_MODIFIED.Value, vbInformation

Else

MsgBox MyFunc.EXCEPTION 'Exception

End If

End Sub

Sometimes you want to know which users are created on a Business Warehouse system and if these have access or have been blocked from by incorrect logon. For this you can use the transaction rsusr200. In the transaction you can see the last login, the users validity, etc.

1. Call transaction rsusr200
2. Run
3. List of all users appears

Sometimes you have to check the rights of users. For this you can use the transaction su53.

If you adjusts many objects in the Business Warehouse, a lot of transformations are automatically inactive. So you don't have to activate each transformation by hand, there is a ABAP program named RSDG_TRFN_ACTIVATE.

1. Call transaction se38
2. Run program RSDG_TRFN_ACTIVATE

If you want to create automated reports with data from an SAP ERP or Business Warehouse system, you first need to connect to a SAP system. The connection can be used later to access system tables in the ERP or Business Warehouse or to trigger various other action.