[BW] Activating authorization objects and creating InfoProviders - 746811

Symptom

If an InfoProvider is recreated and then activated, all of the relevant reporting authorization objects are automatically activated for this InfoProvider.

Other terms

Authorization object, create, activate, InfoProviders, InfoCubes, RSSM RSSTOBJDIR

Reason and Prerequisites

This is due to strict security guidelines, which prohibit data from being displayed until it is explicitly permitted.

Solution

The security guidelines cannot be altered.

If you do not require an authorization check, you must once again deselect the reporting authorization objects that were made; make this deselection in transaction RSSM under "Check for InfoProviders" --> "Change".

[BCS] Replication in BW system

[BW][BEX] Currency translation in report result

Only Currency translation type whose time ref. = fix date or query key date can be select in the query result.

[BW] Exception and scaling factor

[BW] Select variable table for different system

CASE SY-HOST.
WHEN 'ABIW3'.
I_TABNAME = '/1FB/MD___2S003L'.
WHEN 'ABIW2'.
I_TABNAME = '/1FB/MD___2S003J'.
WHEN 'ABIW1'.
ENDCASE.
......
SELECT * INTO CORRESPONDING FIELDS OF TABLE I_CS_ITEM
FROM (I_TABNAME) WHERE AREA = 'L1'.

[BW] System change option and BW - 184586

Symptom

You receive error messages when you connect the source system or activate transfer rules, stating that repository changes or client-independent Customizing is not allowed, or that the namespace is protected against changes.

Other terms

System change option, source system connection, transfer structures, production system, transport, namespace roles,

Dump 'DYNPRO_SEND_IN_BACKGROUND' in the source system, RSAR502

Reason and Prerequisites

It is very common in productive systems not to allow any changes.However, the connection of a system as a source system to a BW, or connection of a BW to a new source system, are considered to be system change options.

Furthermore, the namespace roles of the BW generating namespaces must be correctly maintained.

Solution

Therefore, the following changes must be valid in the affected client under these conditions:

1. during source system connection because of local generation of Idoc types in customer namespace ZS*

a) in BW before Basis 4.6A Hot Package 3 and

b) in the source system in all releases

2. during activation of transfer structures for transmission method Idoc because of local generation of Idoc segments in the namespaces /BIC/* and /BI0/*

a) before Basis 4.6C HotPackage 3 on both systems involved

• Client-independent Customizing and repository changes.

Implement this in transaction sm30, table T000.

• Changes in the customer namespace

• Changes in the local namespace

• Changes in BW namespaces /BIC/ and /BI0/.

Maintain these settings in transaction SE03, Administration, Set system change option

• Namespace role of namespaces /BIC/ and /BI0/:C (recipient) with valid repair license.

Maintain these settings in transaction se03, Administration, Display/change namespaces

These changes must also be permitted when BW objects are imported as otherwise the after-import methods fail.

Since the import of transfer structures / transfer rules also creates objects in the affected source system, the above-mentioned changes during the import must also be allowed.

[BW] Transport DataSource Hierarchy in R/3

1. Change Object package - SE03
2. Object Type = R3TR-DSAA : Name = APCO_MERGED

[BW] Start data transfer into BW from OLTP -- 135637

SWELS --> switch event log
SWEL --> show event log
SM62 --> define event
FM BP_EVENT_RAISE --> raise event
raise event from os level --> sapevt


========================================================================
BW:
You can use the function module SWE_EVENT_CREATE to raise the event. This function module is RFC enabled.
OR create ur own FM
FUNCTION Z_BW_EVENT_RAISE. ( must be RFC enable )
*"----------------------------------------------------------------------
*"*"Interface local:
*" IMPORTING
*" VALUE(EVENTID) LIKE TBTCO-EVENTID
*"----------------------------------------------------------------------

call function 'BP_EVENT_RAISE'
exporting
eventid = eventid
exceptions
bad_eventid = 1
eventid_does_not_exist = 2
eventid_missing = 3
raise_failed = 4
others = 5.

ENDFUNCTION.

R3:

REPORT ZBW_EVENT_RAISE .

call function 'Z_BW_EVENT_RAISE'
destination 'BW1001'
exporting
eventid = 'SAP_BW_TRIGGER_HR'.