cancel
Showing results for 
Search instead for 
Did you mean: 

Different type of BICS Connectivity?

former_member186358
Active Contributor
0 Kudos

I did not know that BICS connectivity is different for different tools. Does anyone know the difference?

BICS (Dimensional Transient Universe)

BICS (Direct to BEx)

BICS (NW BI Java)

View Entire Topic
IngoH
Active Contributor
0 Kudos

Hi,

- BICS (NW BI JAVA) means that the connectivity uses the BICS interface from the BI Java component from BW without the need to have a BI4 server environment

- BICS Direct means that the tool connects to the BEx query directly without any Universe

- BICS (transient Universe) means that the tool leverages a BEx query and a "transient" universe is being generated

regards

Ingo Hilgefort

Former Member
0 Kudos

HI Ingo,

Thanks a lot for your clarification. I have however something that is not cleared in my mind. When you're using multisource-enabled foundation with different data sources including SAP BW, you also use a java component to return data. My question does this also uses BICS technology?

IngoH
Active Contributor
0 Kudos

Hello Jean,

the relational Universe for BW is not a BICS connection.

regards

Ingo Hilgefort


Former Member
0 Kudos

I have a quick question with regards to synchronization universes within IDT.  When you synchronize local project with the one published on the repository and you make changes locally; the system shows you that there have been changes locally. However, it does not show you the specific changes (tables added/removed for instance) after the changes have been locally saved. My question is there anyway someone to tell the difference between the local projects vs. project that has already published on the repository?

IngoH
Active Contributor
0 Kudos

Hello Jean,

you are asking questions on IDT and Universe on a discussion about the BICS connection - which does not require a universe at all and is a direct connectivity.

I would suggest you post your questions into the correct forums.

regards

Ingo Hilgefort, SAP