cancel
Showing results for 
Search instead for 
Did you mean: 

Comments in a Query in WAD often get SID instead of Comments

Former Member
0 Kudos

Hi,

a made a pilot using comments as keyfigures.

Datamodel:

Aggregationlevel, Multiprovider with one Cube and DSO (directwriting) for planning and comments.

There is a planning query use a hierarchy (0COSTELMNT) on the rows of the query. The webtemplate is created with the WAD.

The ZCOMNT 250 Bytes long, no metadata, no texts.

The  planning and save is on the DSO.

With listcube on DSO or Mutliprovider, we see the correct comments.

The comments ary physically saved on the DSO.

I testet with short and long entries, special characters, and on different Tabs.

It starts fine. But after a time of testing i see digit-numbers instead of the comment.

The numbers are the SIDs in table /BIC/ZCOMNT

The translation to the ZCOMNT-text does not work for all, but for several comments.

This wrong looks on the WAD and on performing the planning-query.

Is there a tip, how to get permanent comments as result and no SIDs?

How does the translation between ZCOMNT and 1KY_ZCOMNT work in the query?

Additional question: the 1KYF_ZCOMNT is INT4 lenght 4. So the count of comnts is delimeted by 9999 entries ?

Thanks

Ernst

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Gregor,

thanks, i will order this by our SAP-BASIS. Unfortunally - christmas time - they need a bit of time to do this.

We have SAP-BWonHANA 7.4 SP12 and BI JAVA is not the actual one. So we have the possibility to update the BI JAVA in 2016.

Some of the release-notes - you list - are more difficult to develop. At his time, we don't have the PAK or BPC-license. So it is not recommended to insert these release notes.

Regards

Ernst

Addon at 8.2.2016:

The JavaPatch is implemented, it works: No SID representation fo comments at this time, Thanks

Answers (1)

Answers (1)

0 Kudos

Hi Ernst,

'characteristics as key figures' allow to expose characteristics as key figures in a query, thus one internally needs a number type to process this data type in the analytical engine (OLAP). The system use the SID of the characteristic to do this, thus the type INT4 is used. As a result one can have as many 'comments' as SIDs of master data value (something like 2 147 483 647).

To the problem:

Check collective note 2215368 to fix the issue. Some clients tools have problems with the characteristic value to SID conversion, so please use PL20 or higher for BI Java 740 with SP 11 and implement at least notes 2096560, 2155279.

Regards,

Gregor