Connection of BI to Multiple SRM clients

Hi,
I am working on SRM/BW implementation. Now, in our project we are implementing multiple clients in SRM QA environment to support Testing and Training.
My question is,
Can this be done ?
If yes, What has to be done in BW system to extract data from multiple SRM clients in single environment and still segregate different client data in BW environment?
SRM QA System client 100 ->BW QA System -
>Query1 shows only SRM QA Client 100 data
SRM QA system client 110 -> BW QA System---> Query1 shows only SRM QA Client 110 Data
Thanks in advance.

hi Raj,
you can compound infoobject with 0LOGSYS ... or add it to your infoprovider,
and map 0logsys with the client logical name
take a look
http://help.sap.com/saphelp_nw70/helpdata/en/80/1a6399e07211d2acb80000e829fbfe/frameset.htm
hope this helps.

Similar Messages

Multiple Backend Connected to the same SRM client.

Hello All,
We have an interesting requirement.
We have an SRM 5.0 client with R/3 4.7 backend. Now we need to add another instance of ECC 5.0 to be connected to the same SRM client ( either on the same org stucture or a different org structure).
I am facing difficulty in doing the material replication.
I have the inbound queue in SRM blocked and I and getting the error message LOGSYS_FOR_GUID_CHANGED.
This lead me to the notes 588701 and 765018. But I am not sure this would actually solve the problem.
I have also seen the following thread which indicated that one CRM client should point to only one R/3 instance.
Downloading basic R/3 objects into CRM with brand new systems
Has any one so for integrated multiple backends to the same SRM client? What was your approch to the requirement? Inviting your views and opinions to this issue.
Thanks in advance.
Ajith

Hi
You can implement corrections in the note 765018 as you mentioned in your post.
We have done the same thing. In case of multiple backends and also if systems are refreshed with other instances (client copy), the logical system ID will be changed.
So we need to run the report mentioned in the said note and run the replication.
Rgds
Reddy

Multiple Backends Connected to the same SRM client.

Hello All,
We have an interesting requirement.
We have an SRM 5.0 client with R/3 4.7 backend. Now we need to add another instance of ECC 5.0 to be connected to the same SRM client ( either on the same org stucture or a different org structure).
I am facing difficulty in doing the material replication.
I have the inbound queue in SRM blocked and I and getting the error message LOGSYS_FOR_GUID_CHANGED.
This lead me to the notes 588701 and 765018. But I am not sure this would actually solve the problem.
I have also seen the following thread which indicated that one CRM client should point to only one R/3 instance.
Downloading basic R/3 objects into CRM with brand new systems
Has any one so for integrated multiple backends to the same SRM client? What was your approch to the requirement? Inviting your views and opinions to this issue.
Thanks in advance.
Ajith

Hi
You can implement corrections in the note 765018 as you mentioned in your post.
We have done the same thing. In case of multiple backends and also if systems are refreshed with other instances (client copy), the logical system ID will be changed.
So we need to run the report mentioned in the said note and run the replication.
Rgds
Reddy

Can two different SRM clients systems connect to one R/3 Back-end system?

Hello,
Trying to developing SRM Co-Exist/Global strategy, based on the following scenario:
1. Two different SRM client systems, each at DIFFERENT SRM Version/Release Level. SRM system "A" runs in Stand-Alone and Extend Classic Scenario mode. SRM system "B" runs in Classic Scenario mode
2. Two different R/3 back-end systems, each with SAME R/3 4.7 Version/Release Level.
Question 1: Can the two (2) different SRM client systems be connected to one (1) of the R/3 back-end systems?
Question 2: Are there any Basis Plug-In (PI_BASIS) issues/difficulties to consider from either the SRM client or R/3 back-end side?
Question 3: Does each SRM client need it own unique transaction document type(s) and number range(s) definitions?
Question 4: Are there any other difficulties, for example, with RFC and Partner Profile related definitions and what are the steps to address/resolve difficulties?
Please advise and thanks in advance for your feedback!
Regards,
Ed
Edited by: Ed Shigo on Mar 16, 2009 6:40 AM

Question 1: Can the two (2) different SRM client systems be connected to one (1) of the R/3 back-end systems?
They can be connected
Question 2: Are there any Basis Plug-In (PI_BASIS) issues/difficulties to consider from either the SRM client or R/3 back-end side?
Make sure that you have unique consumer entries for Middleware for Material replication, RFCs etc
Question 3: Does each SRM client need it own unique transaction document type(s) and number range(s) definitions?
Yes you need to have them.
Question 4: Are there any other difficulties, for example, with RFC and Partner Profile related definitions and what are the steps to address/resolve difficulties?
Don't see any difficulties as long as the a structured approach is followed.

Connection timeout depending on how many client JVMs (but as many requests)

Hello,
sorry for the cryptic title, I hit the length limit.
Here is my problem. I'm asking first for an explanation, or for ways to investigate it. Afterwards I'll need a solution but as I suspect the problem is involved, and involves several tiers, I will probably open dedicated topics instead.
Short Story*: a web service server and 10 test client JVMs work fine - but a single test client simulating 10 virtual users experiences ConnectException.
What can I log or probe to understand why?
Long Story*:
I have an application that I used to simulate load on a WebService server. The app simulates a variable number of clients of these WebServices, each virtual client running in its own thread, and sequentially calling the same set of WebServices in a fixed order, and looping.
I have, on some occasions, met various problems with the server product (under development and validation), or the test client (that may not have had the same level of attention and quality in the design as the product), some of you may remember some of my asking here and there. But we achieved a fair level of reliability.
However, today, after a few weeks' change to the server(1), we load-tested it using the test client simulating 10 concurrent clients. After a few minutes, we repeatedly witnessed a fair number (1% of the requests) of java.net.ConnectException "connection timed out" raised at the client's end. I immediately suspected the server to not honor connection requests timely, and went on monitoring the server's queues, listeners,etc.
As nothing seemed to highlight a problem on this side, a colleague suggested that we instead launch 10 client JVMs (on the same single test client machine), each one simulating one single client. I blatantly qualified his suggestion of "hopeless random try" but let him try his way.
Dang! He repeatedly demonstrated that the 10 client JVMs do not undergo the ConnectException, even though they simulate the same number of concurrent requests (well, 10 at most), at the same thoughput - and we observe the same level of server CPU, and same functional results.
I respectfully apologized for being a pretentious moron (2), but he hasn't proposed any satisfactory explanation so far, and I'm clueless too. So we haven't been able to make the "single JVM load-test client" work. We need to make this one work, for various reasons.
There may be some server-side tweaks (worker thread pools, waiting queues,... for the record it's a Glassfish server) that I may tune, but as the "regular" situation of 10 client VMs is handled appropriately, I deem the server-side setting are correct.
So I'm primarily interested in monitoring the client host and JVM(s) to spot the differences between the two scenarios. But there may be some server-side indicators as well (queue size, keep-alive pool) that may help the investigations - and if need be, I will happily tune the server for the benefit of the "test client investigating".
One track I'd like to investigate, is the way HTTP connections are reused: we're using a JAX-WS client querying a Glassfish server, and both seem to agree on using HTTP1.1 (I checked HTTP packets with tcpmon), which supposedly "reuses connections" (is that the same as "keeps TCP socket open and reuses them"?). Could it be that the 10 threads in the multi-client simulator have a bottleneck of using a shared HTTP connection(s)? I don't know how to log or monitor this:
- I did a couple of netstat dumps during the tests on the (Windows) client test machine, and it exhibits only a few hundreds of sockets in TIME_WAIT state, and a few dozens of ESTABLISHED ones.
- I don't have the numbers for the server, though.
I don't know how to investigate that further. Any clues?
I may exhibit a poor turnaround time in this thread, as the test platform is used for real tests, but I do care about the topic, so I attach shiny little dukes.
Thank you for your time (well if you've read this to the end you at least deserve a thanks!) (3)
J.
(1) and after switching test platform (room & network); lesson one: "Never mix test platform changes and other changes in the same iteration; regression-test the new test platform with the former software version"
(2) lesson two: "When you don't know, don't tell a colleague he doesn't know"
(3) lesson three: "Short posts get better attention, are better understood, and more happily replied to"... (sigh)

Hello ejp,
I not only missed your points, but missed your latest post as well :o)
I'm discovering it.
You've missed the point. Problems that only shows up with multiple clients in the same JVM but not with multiple JVMs don't correspond to real-world situations any more than the configuration does so there is little in even investigating them, and no point whatsoever in trying to fix them.
(...) It's not 'hopeless', but you have to be constantly aware that it can lead to false positives and false negatives.Fixing them woud enable me to continue load tests with a cheaper test platform. I cannot afford 10, 100 or 1000 client machines. I know you're talking about JVMs, but 10 or 100 client JVMs running on a single host is not a real-world situation either, no more than "all clients are on the same LAN". I have to do away with approximations, keeping aware as completely as possible of the differences it introduces.
This is not true for HTTP connection caching: this favors the server as much as the client, so I can't infer that it's a favorable case overall.Again you've missed the point. It can only happen inside a single JVM. So it may present you with false positives.I'm still not sure I got the point now:
-> For the server, wich are the differences between both client configurations (single-JVM vs 10 JVMs)?
- - Does a new TCP connection request from the same JVM involve less work if one is already established?
If not, and if each virtual client uses its own TCP connection, there is no cheating, and I don't need to worry about this level of bias.
- - Does an HTTP request that comes over an established TCP socket require less server work than an HTTP request that reqests a new TCP socket?
Probably (in the second case the server has to accept the TCP request and probably pool it, and assign a reader thread, etc...). So I do need to worry about this bias. One way to avoid it is to manage to have the virtual clients not using each other's HTTP connection.
And so on...
Is it possible to build a comprehensive list of the differences incurred by the single-JVM configuration?
Then for each of them, I can try to evaluate ways to alleviate the bias.
- If I managed to avoid or alleviate each and every bias, I would be back to a realistic simulation.
- If there remained only the biases that handicap the server (such as, the server crashes under a 15 clients load, whereas in reality it could sustain 25), then I could be conservative and announce "the server will handle 15 clients gracefully" to the salespeople that will establish the SLAs. I understand that I may never be able to prove that the server actually scales up to 25 concurrent clients, but as long as the conservative SLA matches the market target that will do.
- If I'm left with biases that do favor the server, then I can't rely on the test platform and I'll reluctantly but resignedly try to have a more realistic platform funded (the more likely outcome is to be asked to provide probabilities and disclaimers in the test reports).
Thanks for your help so far, and please bear with my stubborn but polite request to try to identify further the differences ad causes.
J.
Edited by: jduprez on Dec 14, 2009 5:56 PM
Edited by: jduprez on Dec 14, 2009 5:57 PM

Multiple SRM Systems One SRM-MDM Catalog?

Hi
I'm currently upgrading our SRM 5.0 to SRM 7.01 with SRM-MDM Catalog 7.01. Is it possible to use one SRM-MDM Catalog in our non-production environment and connect multiple SRM systems to it?
For example our sandbox, development and QA SRM 7.01 systems would all connect to the same SRM-MDM Catalog 7.01.
Thanks.
Neil

Hi,
for non-production use and if it is just a catalog without custom coding running I see no problem in using one MDM server for multiple SRM systems (especially sharing one for sandboxes and dev). It is a setup I have seen multiple times and it worked always without problems.
You should set up different repositories for each SRM system so that you don't interfere with each others data (i.e. suppliers or other lookups tied to SRM).
You have to keep in mind that you have to upgrade all systems together. But you can always use separate MDM servers during the upgrade process and then consolidate onto one server when the upgrade is done.
If you are running custom coding with your MDM catalog I would recommend having a separate MDM system for the QA SRM in order to be closer to the production set-up when testing your custom solution.
Regards,
Martin

Multiple SRM and single ECC in landscape

Hi all,
I have a requirement where we need to implement SRM 7 in one region (so that we are able use the new features) and continue with SRM 4 for the other regions. Both the SRM systems will connect to the single ECC 5 system in the landscape.
Has anyone implemented a similar scenario where multiple SRM systems are connected to one ECC system
What are the problems that one will encounter.
Self service procurement, Supplier self services and strategic sourcing are the scenarios that are currently configured.
Contract management may be used in the future
Any suggestion / idea will be greatful
Thanks
Venkat

Hi Venkat,
yes, it's possible to link the same ECC backend system to different SRM systems (with different releases). We have also a scenario like this.
The only problem what comes up to my mind is, that you need to take care about the number ranges (as the PO, RS... number ranges are from the point of view external numbers).
Regards,
Peter

Multiple ECC clients configured to APO

Folks,
If multiple ECC clients (001, 002, 003) are configured with a single APO client(001), how does APO system deal with this without causing data issues.
Say if I updated Material master in all these 3 ECC clients, which version will be refelected in APO system.
TIA

Hi Pat,
Need to maintain different BSG: Business System Group for each R/3 by tcode : /SAPAPO/C2.
"Maintain Business System Group
    Use
    In this IMG activity, you determine the assignment to a business system
    group of the APO System and the SAP R/3 System to be connected. By doing
    this, you create areas with the same naming conventions. These guarantee
    that the same names are used for master data, and also their
    synchronization in distributed system landscapes.
    Requirements
    As an independent logical system, the APO System must, in addition to
    the SAP R/3 Systems, be assigned to a business system group (BSG).
    Activities
    o   Choose New entries.
    o   On the New entries: Overview screen, specify the following
    o   information for the business system group:
        -   An alphanumerical key (maximum of 10 characters).
        -   A description.
    o   Save your entries.
Example 1
An APO System is to be linked with two SAP R/3 Systems (A and B), in
which two different materials (for example a hammer and a screw), have
the same material number (100). Both materials are to be represented as
two different products in the APO System.
Assign both SAP R/3 Systems to different BSGs. Assign the APO System to
one of the BSGs.
o   SAP R/3 System A (Material number 100 = Hammer) -> BSG A
o   SAP R/3 System A (Material number 100 = Screw) -> BSG B
o   APO System -> BSG A
In order to avoid having two identical names and to be able to uniquely
assign the material numbers, you need SAP extension APOCF005. This is an
inbound processing product (transaction SMOD or CMOD).
Material number 100 from BSG A receives, for example, product number 100
in the APO System and material number 100 from BSG B gets product number
100_B. This allows you to uniquely assign the materials.
For inbound processing in the APO System, the following SAP enhancements
are available as customer exits for master data:
o   APOCF001 : Inbound processing location
o   APOCF005 : Inbound processing product
Example 2
An APO System is to be linked with two SAP R/3 Systems (A and B). In SAP
R/3 System A, a particular screw has material number 110. In SAP R/3
System B, it has material number 120. Both material numbers are
represented in the APO System by one product, with product number 110.
Assign both SAP R/3 Systems to different BSGs. If possible, assign the
APO System to the BSG whose data does not have to be renamed.
o   SAP R/3 System A (material number 110 = screw) -> BSG A
o   SAP R/3 System B (material number 120 = screw) -> BSG B
o   APO System (product number 110 = screw) -> BSG A
You use SAP enhancement APOCF005 to convert the local SAP R/3 material
number 120, to the APO product number, 110.
Note
For the time being, this second scenario is only supported for material
masters and product masters. If, for example, the same customer is used
with different BSGs in R/3 Systems A & B, you must create two separate
customer locations in the APO System. This applies for the vendor,
plant, and other master data.

Support of multiple GUI clients

Hi,
Currently, we have an application which partially supports multiple
GUI clients. When a GUI first launches, it will pop up a dialog box
to select "Read" or "Read/Write" access mode. Once "Read/Write"
is selected, others can only select "Read" mode until "Read/Write" mode is released. There is a timer to automatically release the mode, if "Read/Write" is holding up for too long.
Now., we have to fully support multiple clients. The "Read" and "Read/
Write" modes have to be removed. That means, mutliple clients can
send update requests at the same time. Does anyone have ideas how
to support multiple clients? Is there any "models" out there where
I can based on to support it?
Thanks,
Pin

Mark, we came out with 8.1.7.4.0 precisely for the reasons you have stated. There is no longer a Windows NT Oracle Service For MTS per database. The logic to enlist Oracle connections in MTS transactions, and the logic to subsequently commit/abort these transactions is fully contained within the middle-tier dlls i.e. ORAMTS.DLL. This removes the single point-of-failure in pre 8.1.7.4.0 versions, and also makes the solution more scalable.

How to handle multiple DEV clients in CHARM

Experts:
We have many DEV clients in our ECC landscape.
Some customizing needs to be imported into all DEV clients.
In order to use CHARM to do above import into different DEV clients, I want to define some logical components with only
2 systems, i.e. source DEV client and target DEV client (e.g. DEV100->DEV200). Then link this logical component to a
project.
In this way we will define many projects (logical componets, maintenance cycles) depending on how path combinations existing on the STMS setup.
Could you help verify whether this will work as expected? Because I did not configure 2 system tp for CHARM before therefore I am not sure.
Thanks a lot!

Hi,
you should take a look to those 2 threads especially the second one IF those other clients are USED FOR CREATING TR:
Re: Multiple clients in DEV and QA for CHARM setup
Change Request Management for multiple production clients
IF the other clients should just be synchronized with custo done in the first one then the lines above will help you.
Important fact "A Solman Project can have more than a logical component."
So for example in your case if you are trying to update DEV 200 with DEV 100 when importing TR to quality system (200 must be a kind of reference client for you),
you ll simply have to declare a Solman Project containing the core logical component (for ex: DEV 100 -> QUAL 100 -> PRD 100) AND another one that ll let you import in DEV 200 (DEV 100 -> DEV 200).
In your generated tasklist you'll then find DEV 200 under Target Systems node; like if it was a QUAL system AND you ll find tasks as "Import Transport Requests" available for DEV 200.
As a prerequesite you MUST declare DEV 200 in your logical component as a Target Role System and not as a Source Role System (like DEV 100) (Transaction SMSY). Otherwise Solman will understand that DEV 200 will be used only for creating and releasing TR and it will be considered like DEV 100
Hope it helps
Keep me updated with how it goes
Regards
Khalil

Not able to connect Oracle DBXE from sql*plus client

Hi,
I have installed Oracle 10gXE from oracle site. i have updated the tnsnames.ora also
but when i try to connect the db through sql*plus client, i am redirected to .net debugger.
Pls help me in this,
Thanks in advance.
-- Raja

Hello,
Can you clarify what you are trying to connect from? If it's B1 ( one ) then post to the [B1 forum|http://forums.sdn.sap.com/index.jspa#44].
Otherwise need more info on the product you are using?
Typically the Oracle Path must be in the PATH statement as well it requires the correct platform ( 32 or 64 ) bit client installed.
Most BOE/CR products are 32 bit so you need to install the 32 bit client.
Don

Single file to multiple IDOC's (on Multiple R3 Clients):

Hi,
We have a complex Landscape with multiple (4) businesses (multiple R3) instances and most common R3 --> DEV 4 instances with 5 clients each, QAS 4 instances with 2 clients each with some additional clients, PRD 4 instances with a client each and Training 4 instances with 2 clients each in the Landscape along with BW systems.
We are trying to implement standard MDM - XI - R3 distribution scenario. Only difference being MDM Production will be the Master distribution client and have to be distributing to all the R3 clients. For those who doesn't know SAP MDM - is Master Data Management Engine and within this scenario the output from MDM is standard XML IDOC file.
To achieve this syndication is being planned as MDM production to distribute files to 4 businesses to 4 file share folders. These files will be picked up by XI production and will be distributing(Creating IDOCs) on multiple receivers (R3 --> DEV, QAS and PRD) clients of the respective instances.
The one to one scenario is very simple to build MDM XML file from file adapter to R3 IDOC of IDOC adapter, but for our business it becomes one file to multiple R3 clients (IDOCs) on multiple R3 instances;
My question is: Is there an easy way to configure single file to mutiple R3 client IDOC receivers scenario? Also there might be additions and deletions of the R3 clients based on business requirements. Is there any proposed or already implemented procedure to achieve this complex distribution?
We have planned on trying to define a business system for each R3 client (DEV/QAS/PRD) and to have the integration directories configuration built for all the 47 clients that the data needs to be distributed. With IDOC Adapter is this the only way to go? Also, in future if there are additions or deletions of clients it becomes maintenance intensive and there won't be a quick way to stop the distribution?
Your time and input is appreciated.
Thanks and Regards,
-Raj.

Michal,
Thanks for your answer and FAQ.
I think I am confusing everyone with my long messages!
We already have XI DEV, XI QAS, XI PRD.
But business requirement for the global harmonization MDM scenario is that MDM PRD should be able to distribute the XML files (IDOC fields in GLMAST01 - IDOC format) to all the DEV, QAS and PRD (R3) systems in the landscape. For this distribution XI is used as the integration partner (File adapter picks up the XML file from MDM file share location and IDOC adapter creates an IDOC on the respective R3).
For this specific scenario though XI-DEV and XI-QAS systems are present they are available only for testing phase. After the scenario is moved into production, XI-PRD should be able to pick up the XML file from MDM and distribute it to all the DEV, QAS, PRD R3 systems.
Same file needs to be distributed to 20 DEV clients across 4 DEV instances, 27 QAS clients across 4 QAS instances and 12 PRD/TRN(training clients).
Yes, as you said in your answer earlier deleting a client from the distribution is removing the client from the receiver determination (and removal of corresponding Interface determination, sender agreement and receiver agreement).
Addition of a client for distribution is adding the client (business system) in receiver determination (and addition of of corresponding Interface determination, sender agreement and receiver agreement).
Do I have to maintain all the 59 (Clients from different systems) sets of config within the ID and all the systems in SLD of XI - DEV/QAS/PRD? Even if I do so, Is this the right way to go, defining all the DEV/QAS/PRD clients within all the SLD's of XI - DEV/QAS/PRD?
I am not finding an easy way to architect this.
I appreciate your time and patience.
Thanks and regards,
Rajani Kanth Yalamanchili.

Connect 2 BW to the same client in R3?

Hi,
Is it possible to connect 2 BW to the same client of R/3 as a source system? Will this mess up the delta queue like in RSA7? Or, the R3 system has separate queue for each BW? Please advise.
Thanks,
Jeff

Hello Roberto,
Could you please give me the step to step procedure of doing it? I really appreciate your help and full points will be awarded
Experts,
I have two BW clients with same naming convention (BWP400).. Can I connect 2 BW systems with same logical name to one R/3 system. If not how can I change the logical name of one of the system with out affecting any data or settings it .
One of the prod box is new one and yet to load data.
All inputs are highly appreciated
Thanks and Regards,
Harish

External Requirements from One R/3 client to Multiple EBP clients

Hi
We have a scenario where in , the Purchase requisitions generated from R/3 has to be sent to two different EBP clients on the same server.
But, we are able to send the PR to one EBP client only, but not the other.
Is there any settings where we need to maintain, such a way that, at the time of transferring the PR, one need to maintain the EBP client..?
We are on SRM4.0 and R/3 4.7

Hi Muralidhar,
One R/3 PR can only create one SRM SC.
When defining a transfer profile in R/3, you define the target SRM RFC destination, where the client is defined uniquely.
If you "duplicate" this flow to create 2 separate SC in 2 SRL clients, which one will be leading ? I mean they will have 2 different lifecycle, and at the end, both you try to fullfill original PR (by creating 2 PO ??).
For your exotic need, you have to change standard R/3 code to send the same PR to 2 SRM clients.
After this, up to you to garanty the consistency of the process (no support from SAP).
Rgds
Christophe

JCo client connection Failed to create new JCO client connection

hi All
I am trying to create a new JCO destination ion CE7.1 webdynpro content Admin. but I am getting following error.
Exception while creating JCo client connection Failed to create new JCO client connection weter: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_ACCESS_DENIED: User is not in role LcrInstanceWriterLD at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120) at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.getIResult(SimpleResponseAnalyser.java:53) at com.sap.lcr.api.cimclient.CIMOMClient.sendImpl(CIMOMClient.java:220) at com.sap.lcr.api.cimclient.CIMOMClient.send(CIMOMClient.java:148) at com.sap.lcr.api.cimclient.CIMOMClient.createInstanceImpl(CIMOMClient.java:669) at ......
SLD is Up and running
CIM data is imported
Solution tried :
1) As no role wtih name LcrInstanceWriterLD was existing in the server ,hence created a new role with same name and assigned the LCR related action . Assigned the role to the user through which we are creating JCOs.
But we still getting the same error.
regards
Poonam

Hi Poonam!
Got to dig in the past a bit, I remember Users being able to create SLD object have to have certain permissions set in the J2EE UME. Simple Admin rights do not suffer, if I recall right.
Unfortunately I cannot go further in detail because this issue has been solved by a long gone collegue of mine.
Good luck anyway!
Jürgen

Connection of BI to Multiple SRM clients

Similar Messages

Maybe you are looking for