Multiple ECC client

My ECC Development has 3 client sitting on the same server:
Client 100, Client 150 and Client 200
What I understand is the table RSBASIDOC is client-independent.
Can I connect 2 BW to the same client 200?
OR
can I connect 2 BW to 2 different client - Client 200 and Client 150?

You Can connect 2 BW to the same client 200
and
You can connect 2 BW to 2 different client too- Client 200 and Client 150.
Both possible.

Similar Messages

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.

Connecting multiple ECC Clients on same ECC system to BW system(s)

Hello.
We are considering connecting our Dev BW system to multiple clients on the same Dev ECC system. This connection would be for a limited time. We are wondering what the effect would be on the ECC system after we 'disconnect' our BW system from one of the clients.
Another thing we are considering is to create a seperate BW sandbox system and to connect that to a client on our Dev ECC system. The Dev ECC system will, at the same time, have a connection to a client on our existing Dev BW system. For example, having DEVBWcnlt100 -> DEVECCclnt100 and SNDBWclnt200 -> DEVECCclnt200 where DEVECC is a system and DEVBW and SNDBW are systems of their own. Our Sandbox BW system will have a limited life and at some point be taken down and no longer be a valid source system for the DEVECC system. We are concerned about what the impact would be to the DEV ECC system's client independent data once the Sandbox BW system is disconnected and taken down permenantly. Is 'residual' client independent data something we need to be concerned about? Is having two different BW systems connected to ECC clients on the same ECC systems a 'bad practice'? Any and all comments are welcome as we have not yet acted on our ideas yet.
Thanks very much for whatever comments you might provide,
Geoff.

We are considering connecting our Dev BW system to multiple clients on the same Dev ECC system. This connection would be for a limited time. We are wondering what the effect would be on the ECC system after we 'disconnect' our BW system from one of the clients.
No impact on the BW system. The only thing that you will have to take care of is that any process chains which fetch data from this DEV ECC system should not be put on periodic cycle because after disconnecting the ECC system, these would start failing.
Another thing we are considering is to create a seperate BW sandbox system and to connect that to a client on our Dev ECC system. The Dev ECC system will, at the same time, have a connection to a client on our existing Dev BW system. For example, having DEVBWcnlt100 -> DEVECCclnt100 and SNDBWclnt200 -> DEVECCclnt200 where DEVECC is a system and DEVBW and SNDBW are systems of their own. Our Sandbox BW system will have a limited life and at some point be taken down and no longer be a valid source system for the DEVECC system. We are concerned about what the impact would be to the DEV ECC system's client independent data once the Sandbox BW system is disconnected and taken down permenantly. Is 'residual' client independent data something we need to be concerned about?
Again no impact on ECC system. As for the client connected earlier to sandbox system, just clear all the queues in RSA7, LBWQ
Is having two different BW systems connected to ECC clients on the same ECC systems a 'bad practice'?
No its not at all a bad practice

One PI for multiple ECC systems

Hi PI experts,
We have one PI instance per environment, but multiple ECC instances, so taking Dev we currently have a BAU ECC and a project ECC, although there are occasionally conflicting needs this is generally manageable. However a new project has introduced the need for two further ECC instances per environment, all requiring the same interfaces. We will still only have one PI. All of the interfaces receive files coming into the same folder structure.
Has anyone else experienced this scenario? How was it best to manage the competing projects trying to use one PI instance?
Thanks very much in advance
R_Macd

Hi R_Macd,
You need to register the ABAP Systems in SLD, use the transaction RZ70 to do this, please check the refer links:
http://help.sap.com/saphelp_nwpi71/helpdata/en/7c/1966ab384d42a78deaebc74d33c032/frameset.htm
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=213353417
After that, create the business systems with the client do you need to connect.
http://help.sap.com/saphelp_nwpi71/helpdata/en/ae/e3bd4f6b61e146ad1384954ecabb41/frameset.htm
Best Regards,
.Luis Bernal.

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

Multiple CRM clients (MCRM) pricing and lean order management

Hi CRM experts,
We have a scenario where two CRM CLIENTS (not different systems/boxes) (lets say 100 and 110) are connected to two different SAP ECC systems (NOT different clients but different ECC systems). Both CRM clients have interaction center sales with Lean order management. Now ECC systems have to me merged and the it is required to have one ECC client is connected to 2 different CRM clients.
As per the note 1143540 provided by SAP on this subject it seems that multiple CRM systems can be connected to one ECC. The note tells that conditions exchange in not supported.
1) I want to know if conditions can be exchanged atleast with one system.
2) We know that multiple CRM systems/boxes are supported but are MULTIPLE CLIENTS supported
3) Will Lean order be supported with multiple clients of CRM with one ECC backend
Your help on any of the above questions is highly appreciated and points will be given liberally.
Thanks
Satish

Hi Satish ,
Though I have no document which says this would happen or don't , yet I believe this is possible.
I would visualize the scenario likes this
OLD Scenario
CRM_CLNT1--RFC_1ECC1 CRM_CLNT2--RFC_2-ECC2 ( CRM_CLNT* connected through RFC_* to ECC*)
New Scenario
CRM_CLNT1 -
RFC_1------ ECC1----RFC_2--
CRM_CLNT2
In my opinion at the CRM side this should be possible. It would not lead any change at the CRM side because CRM_1 system and CRM_2 system would still connect to ECC1 through separate RFC connections. But at the ERP side you would have to replicate the data for ECC2 in ECC1.
The Lean order or LORD connects the SAP ERP & SAP CRM systems through a RFC connection using LORD framework on the CRM side. The ERP fields and CRM fields are mapped using mapping table and data is exchanged through communication structure. I don't see any reason why this would be affected.
Let me know your thoughts on this.
I would be interested to know if I you find any relevant documents on this which proves my hypothesis wrong.
Regards
Kavindra
P.S: award points if you find it useful.
Edited by: joshi_kavindra on Nov 15, 2011 8:29 AM

Connecting to Multiple ECC systems via one Gateway system(Dynamic System Selection)

Hi Experts,
We have multiple ECC systems and one Gateway server. We want to connect to these different ECC systems using one GW system.
I have created System Aliases for these ECC system in GW system. For a service, i added 2 system aliases.
Now we are looking for the solution where UI can provide the system alias (it wants to connect) as a parameter while calling oData Service.
Please help.
Regards,
Rohit

Hi Rohit,
we have a similar scenario where we have two system aliases for one service. Both aliases point to the same system, but different clients; it should not make a difference though, having different systems. The feature you are looking for is Multiple Origin Composition (MOC).
There are a couple of things you have to consider:
in the SEGW the entity to be called has to be marked as addressable
the URI of the service needs to include the tag for MOC (;mo) --> http://sapgw.domain.org:8000/sap/opu/odata/sap/ZSOME_SERVICE;mo/entityset
Without the ;mo the call will be routed to your default alias. The ;mo will route the call to both systems. Using MOC will generate an additional key property into your entities --> SAP__ORIGIN. The property is the alias. If you want to route to a specific system you have to provide the SAP__ORIGIN like providing normal key properties in your requests.
This will look like this:
<content type="application/xml">
<m:properties xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices">
    <d:SAP__Origin>SOME_ALIAS</d:SAP__Origin>
    <d:Identifier>SOME_IDENTIFIER</d:Identifier>
    <d:Doublet />
</m:properties>
</content>
The original Entity only consists of the key property "Identifier" and the property "Doublet". "SAP__ORIGN" is added via the ;mo.
Hope it helped...
Holger

Creation of sales order in CRM and replicating it to Multiple ECC system.

We have a requirement for creation of sales order in CRM and replicating it to Multiple ECC system.
We have checked the following standard Adapter objects in transaction R3AC1.
BUS_TRANS_MSG
The initial flow contexts does not support target site type as R/3(SMOF_ ERPSITE). So we are not able to replicate the sales order from CRM
to ECC.
2. SALESDOCUMENT
Here the initial flow contexts does not support flow from CRM -> R/3 as we don’t see the target site as CRM.
Please let us know if the standard sap middleware objects don’t support the sales order flow from CRM to multiple ECC or is there any
other adapter object we need to use for this.

Hey Vijay Duvvada,
I hope you are already referred below sap note and which explains scope & how to do -
1084315 - Consulting: Information about the multiple backend scenario
1763516 - How-to: Basic Setup of MEP
As explained by Rohit Sharma data should be start flowing to multiple sites.
please let me know if it does help.
Regards,
Arjun

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.

Impact on changing ECC client on the working of ESS business package in EP

Dear Experts,
We had ESS business package working fine in our EP 7.0 which connected to client 100 of ECC 6.0.
Now we changed to client 700 in ECC 6.0.
Now all is working OK except for the Personal Data piece (address,bank etc).
The first screen shows up OK but when we review it we get the error :
Access via NULL object reference not possible.,error Key:RFC_ERROR_SYSTEM_FAILURE
The user is setup the same way as that in ECC 100.
The JCO is working correctly.Get successful message when we click "TEST".
I have used USER/PWD in both meta data and application data (though it is said to use Ticket and User/Pwd. It worked with ECC Client 100.)
Appreciate any inputs
Thanks.
Ashish

hi ashish,
try to use only application data

Consideration during Multiple ECC systems with One APO system for PP/DS

Hi All,
We have a scneario that Multiple ECC systems and Third party ERP systems and Legacy systems .What are the points to be considered for this scenario when using with PP/DS?

Hi,
The factors to be considered will greatly depend how the multiple ERP systems are split, if they are split on geographical aspects only (all modules in all ERP systems then no major issues) - the problem will become a little challenging when Multiple ERP are split with different modules in different instances then major thought has to go in your CIF design (the IMs has to properly though of ).
It is not a detailed explanation but just the line of thought.
Regards,
Vineet

BW system connecting to multiple ECC systems

Hi,
I am new to BW world & has a question to Gurus
1. Can I connecte a single BW system to source from multiple ECC systems (activley) with out any technical issues ? I am assuming that the multiple ECC systems are pretty much mirror images.
2. If possible what are the areas ( at a high level) I need to double check to make this happen ?
Thanks
Hari

Hi Hari,
Yes, you can connect multiple ECC systems to one BI system in one of my project we had more than 20 ECC systems connected to BI Production system.
How this works is because source system and BI system has got different provisions for that,
1) For connecting different systems you simply need to create RFC connection between them. After the RFC is formed you can load data from any of the systems.
How BI system differentiate similar data coming from these systems?
There is a field called 0SOURCE SYSTEM which is used as Compounding field, or primary key field where ever you have data loading from multiple systems, this field basically contains the 3 char source system ID and is used to differentiate records coming from different source system.
How delta is managed in this scenario?
In source system for each data source, a new delta queue is maintained for each target system.
Regards,
Durgesh.

A hint if you use multiple mail clients to check one IMAP account

FYI:
Mail.app in leopard turns on an advanced "push" mail feature automatically, called IDLE. This can cause strange problems when you use multiple IMAP clients to access you IMAP server.
For instance, I have a computer in my office and one in my lab. Normally Mail.app is running on them both constantly. After installing Leopard I would sit in my office delete and move messages from my INBOX, and when I went down to the lab I would find those emails still in my INBOX and also in the mailboxes I had moved them to on my office machine. In very short order I ended up with multiple copies of emails in many places and no ability to actually delete mail.
Originally I thought this was a bug with Leopard Mail.app, or a problem with compatibility between Mail.app and the UW IMAP server that I use. I wasted significant time searching on the web for possible solutions.
It turns out that the IDLE feature (that is automatically turned on for you in Leopard) was the cause of my problems. Turning this feature off (in the Advanced pane of the accounts setting) on EACH machine caused me email to return to its previous functional state.
If you only use one IMAP mail client the IDLE feature is nice, it pushes new mail to you as soon as the IMAP server receives the new mail.
(note -- IDLE is also automatically turned on in Thunderbird)

Assuming you're on a NAT'd network, DNS services can cause all sorts of weird errors with the mail server, including spontaneous name changes.
To verify local DNS services, launch Terminal.app from Applications > Utilities and issue the following harmless diagnostic message:
sudo changeip -checkhostname
You'll need to enter an administrative password for the sudo, might see a one-time informational message around the usage of sudo, then you'll see some host and network configuration information, and finally an indication that either no changes are required, or that there are local DNS or the network has configuration issues. Also, make sure you're not using .local or .arpa as the top-level domain within the DNS services.
Public DNS for the mail server can also cause communications issues, if that's not configured correctly — that won't cause the issue you're seeing in the logs here, but it will cause inbound mail to not reach your server, and outbound mail from your server to be dropped by the remote server. To verify your public DNS, launch Terminal.app from Applications > Utilities and issue the commands discussed in this thread or this thread and confirm that your internal and external MX record and your internal and external forward and reverse DNS settings are all correct.

ECC Client switch to SCM 7.0

Hello,
We are planning to switch our ECC Development client from 120 to 130 which is already connected to SCM system and has data related to ECC 120.
When switch the ECC client from 120 to 130 and run the Integration Models again, what are possibilities of SCM system data to become junk or Inconsistent?
1). SCM data needs to be scrambled before we run the Integraion Models from New client?
2). SCM data gets appended with new Data from new client?
Kindly provide your views...
Thanks,
Arjun

Arjun
It depends on which modules of SCM you are using. If you are using DP integrated with a BI system, the Infocubes/ Time Series Data could be inconsistent after switching. If you are using GATP with Product Allocation (again due to DP/ BI linkage), you could have the same issue.
Other than that you might be ok if you simply do CIF initialize (RIMODINI) and also do a Transaction data reconciliation (/SAPAPO/CCR).
As far as possible, my opinion is that it is always better to rebuild the SCM system everytime the connected ECC client changes rather than attempt to clean it. The reason is that should anything look funny in Development (either due to an enhancement or while testing standard functionality), you will always be thinking in the back of your mind that it might be due to the client switching. The fewer wild cards you introduce in your development environment, the better off your testing.
Rishi Menon

Multiple Mobile Clients

Hi to all.
I want to use multiple mobile clients (up to 50) to send data (texts/numbers) to the same server wirelessly.
What is the best way to go? Bluetooth or WiFi? Is there any limitation in any of the protocols? Which one will quarantee that the data of all the clients will be received at the server?
Thanks, appreciate your concern...
Std.

The thing that causes the "-" half-slected buttons on the Account Creation tab is the absence of a value for the (new in 10.5?) attribute in the com.apple.MCX plist file. You can find this by using the Inspector in Workgroup Manager, getting the user account and editing the MCXSettings attrbute:
cachedaccounts.WarnOnCreate.allowNever
otherwise known as "Show Mobile Account Dialog's Never Option" if you look in the Details tab of Workgroup Manager,
otherwise known as "Show "Don't ask me again" checkbox" if you look in the Account Creation tab of Workgroup Manager.
Pet peeve -- three different terms for the same thing?

Multiple ECC client

Similar Messages

Maybe you are looking for