Showing results for 
Search instead for 
Did you mean: 

Dealing with compounding in customer exits

Former Member
0 Kudos

Hello there,

When creating a customer exit variable for an InfoObject do I have to allow for compounding and, if so how?

I don't know how I would use E_T_RANGE for this.

Thanks and regards


Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Siggi,

Thanks for your answer.

I also thought that I wouldn't have to worry about compounding but I have the following scenario:

When executing the query that contains the customer exit I get the following error message (appearing multiple times) when executing a report.

BRAIN 070: "No SID found for value...."

This error seems to occur under the following conditions only:

1. The query is based on a Basic InfoCube.

2. The query uses a customer exit variable which is is intended to prefilter one of the characteristic Infoobjects in the report by reading it from a DSO.

3. This characteristic InfoObject is compounded to two superior InfoObjects.

4. Specifically, the two superior InfoObjects are restricted using a normal characteristic value restriction in the query.

When we click on the long text of the error message we get:

"Characteristic value NAG [superior object 1] UOC [superior object 2]0000005675 [basic, compounded objet] does not exist in the master data table of characteristic MWONUM. Therefore, this value could not be transformed into the internal SID."

The reason why this error message is unexpected is because the characteristic values for which it is producing the error message do not even exist.

The coding itself in the customer exit works fine according to the debugger and returns the correct values to the query.

So the OLAP processor seems to be checking in master data for the existence of values that do not exist and are not (specifically) being requested.

Any help with this issue would be much appreciated.

Thanks and regards


Former Member
0 Kudos


you don't need to take care about the compounding in this case.