Hi experts,
We are on our way to create some interfaces between PI 7.1 and BI 7.0.
These interfaces will communicate each system by means of ABAP proxies.
In BI side, in order to operate with the most up-to-date information,
we are using APD (Analysis Process Designer). It consists of a query
execution that at last inserts data into a DSO. This DSO is a table the
system creates, its fields are named with the prefix /bic/ and that is
the problem. BI team tried not to use it but with no success, this
prefix seems to be mandatory when working this way. Currently, RFC
communication is used, that is Outbound RFCs come along with DSO tables
and thus, data acquisition and assigning is done inmediately. Problem
is that we want to move to proxies without losing this benefit. That is
the clue.
So, back again in PI, once we try to create all the necessary stuff for
ABAP proxies, the system prevents us from creating the Data Type for
fieldnames starting with '/' so we cannot create the Service Interface
and so the proxy.
Error message looks like:
Value "/" is not allowed for the attribute "name" of type "NCName" in
element
Besides, we have tried to use the RFC metadata as a service interface
but it didnt work out, because '/' characters in BI were represented
by '-_' once we imported this metadata.
Basically, this is the problem we are facing right now. We know that
ABAP proxy is one of the best practises in terms of communication
between WAS servers and due to this, we think we might be missing
something in between.
Is there a way to work with ABAP proxies and this BI internal
fieldnames without having to reassign fields before calling the Proxy
methods and classes in BI?
Could you please help us on this issue?
Thanks a lot in advance and best regards,
David