Switching ECC client in BI

Hi
currently our BI is connecting to ECC client 110, but ECC client 130 has better data, please let us know what is the procedure to switch BI from ECC client 110 to 130?
Do we need to run BDLS in ECC system, we don't want to impact ECC system, if we need to run BDLS, will it cause any problem? Also we'll change the BI connection back to ECC client 110 after we are done with client 130, is it doable ?
Thanks
Joey

Similar Messages

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

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

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

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.

How register the ECC Client to SLD automatically

Hi All,
I know the we could use RZ70 to register the ABAP system to SLD
but it seems RZ70 only could register it as the technical system in SLD
but i am wondering is it possible to register the client as the business system in SLD?
let's say: ECC host is erp, and the client is 100, how to register ERPCLNT100 into SLD automatically???
thanks a lot

Hi,
From PI7.0 onwards ECC client registered automatically in SLD.
Check more on PI installation guidelines.
Re: Installing PI 7.0
Thanks.
Boopathi
Edited by: Boopathi Thangavel on Jun 30, 2008 8:55 AM

ECC clients for Datasource Activation

Hi Gurus,
In my project we are using three ECC clients.One is ECC-Golden,ECC-Development,
ECC-Unit tesing.
To activate LO datasources, I am in confusion to use which client from above.
Can anyone brief about the clients in ECC.
Appreciate the speedy reply.
Regards
gkrr

Hi Ganesh,
Golden client is the one where nothing is modified to other than what SAP has given. This is like a template client.
Development is the one where all these things are done, in terms of activations, creations. So your case falls here.
Unit test client, is where some data is posted and developments are tested.
This is as per the nomenclature provided. Not sure, if this can be different in your case.
Naveen.A

ECC Client for BI7

Hello guys,
I have couple of questions/confusion regarding ECC (source system) connection for New BI7 system.
We used to BW3.5 system and the Source System/R3 Client we were using was lets say ABCLNT80.So that means there was no RFC connection issues between these systems. Now we have a new System also, BI7 , and it has been configured to connect with different Source Client/R3 ..XYZCLNT700.
So, does this mean that i can no longer use my previous Source Client ABCLNT80 to send replicate DS to new BI7. do I have to access this new Source Client XYZCLNT700 as a Source system which has a RFC connected established already? if so , would I supposed to have new Configuration/log in information for this Source Client or i can use old ones? because it seems Client # with new one seems to be changed. I am really confused with this , please give me some hints on how these work.
thanks
dk

Hi,
I think you'll have to create a new RFC connection for the new system. This is a basis job. So contact your basis team,they should help you with this.
Regards.

Changing the ECC Client in DEV affects Transformation?

Hi,
I have a Clarification here.
We have 2 clients for ECC Dev, 300 & 100. We completed all our developments in BID linking to 300 client. Now, Customer says that he has more data in 100 client, so he wants to do testing of that data.
We have activated all the MD & TD Datasources in 300 Client and all the Transformation mappings are also pointing to 300.
How can this be achieved? Now, if suppose, Basis changes the Logical system to 100, do i have to do all the Activations in ECC again for 100? Do I have to create Transformations for all the Targets again?
Thanks for your time.
Regards,
Murali

Hi Murali,
Transformations are not source system dependent, when you say that you can see the name of source system in your transformation, where actually you can see that name? In the description or do you have source system as field in the header informaiton of Transformation?
You can get the difference, when you double click on your Data source you will see the Source system as separate field in the header information, but in case of transformation you will have only source or transformation and Target as important fields along with other fields.
Or are you saying that in the transformation mapping of fields you have source system ID assigned to target field source system ID?
And during transport source system changes are taken care by using transport connection, go to your RSA1 transaciton in the target system and go to Transport Connection-----> "Conversion" button on the tool bar here you can do the mapping of your source client and target client.
Regards,
Durgesh.

BI connects to which ECC client?

Hi All, We have 4 clients in ECC,
1 u2013 ABAP Development
2 u2013 Variant Configuration
3 u2013 Unit Testing
4 u2013 Golden Master
So to which of these 4 clients in ECC should our Bi system connect to?
Thanks in Advance.
Priya.

Hi,
Looking at the client names it seems like useful for you would be
3 u2013 Unit Testing
4 u2013 Golden Master
In the current system you can check from RSA1 that which are all the clients already connected, and for loading data from ECC, the best thing would be to contact to Functional team.
Regards,
Durgesh.

Content Switch replacing Client IP in IIS Logs

Hello Guys,
I have been facing this problem ever since we configured our content switch infront of our web server. The IIS logs in the web server now show the content switch IP in the 'c-ip' column.
Below is configuration for the website:
service GlobalInv
port 80
protocol tcp
ip address 172.21.21.31
active
owner GlobalWebSite
content GlobalInv-http
    vip address 172.21.21.52
    add service GlobalInv
    port 80
    protocol tcp
    advanced-balance sticky-srcip
    active
group GlobalInv
vip address 172.21.21.52
add destination service GlobalInv
active
Can someone please help me tellin as to how I can have the actual client IP addresses shown in my IIS logs instead of the content switch IP.
Please this is very important to us.

Thanks Jim,
I am sorry but am not an export in CCS, it would be a great help to me if you can instruct me on how I can actually achieve this.
I have already set the default gateway of my web server to the Content switch.
My topology is quite simple, both the content switch & the web server are in the DMZ zone (same subnet) and are connected to the same switch. Users from outside & inside the company access our corporate website through the content switch
Below is the configuration of my content switch (with the related config marked in red):
CSS-GLOBAL# sh runn
!Generated on 10/26/2010 23:14:04
!Active version: sg0810106
configure
!*************************** GLOBAL ***************************
dns primary 172.21.1.13
dns secondary 192.168.0.50
ssl associate rsakey eglobal eglobal.pem
ssl associate cert eglobal-selfsigned eglobal.selfsigned.pem
ssl associate rsakey glopedia glopedia.pem
ssl associate cert glopedia glopedia.selfsigned.pem
ssl associate cert eglobal-versign e-global-verisign.pem
ssl associate cert glopedia-verisign glopedia-verisign.pem
ssl associate cert EGlobal-Web EGlobal-Web.pem
ssl associate cert EGlobal-Web-Chain EGlobal-Web.pem
ssl associate cert Glopedia-Web-Chain Glopedia-Web.pem
ftp-record conf 172.16.143.43 shahim des-password 1bnc2hnduhmgjend /
ip route 0.0.0.0 0.0.0.0 172.21.21.1 1
ip route 172.21.1.0 255.255.255.0 172.21.21.4 1
ip route 172.16.0.0 255.255.0.0 172.21.21.4 1
ip route 192.168.0.0 255.255.255.0 172.21.21.4 1
!************************* INTERFACE *************************
interface e1
description "To Global Switch Foundary"
!************************** CIRCUIT **************************
circuit VLAN1
ip address 172.21.21.49 255.255.255.0
!*********************** SSL PROXY LIST ***********************
ssl-proxy-list SSL-Proxy-List
ssl-server 51
ssl-server 51 rsakey eglobal
ssl-server 51 vip address 172.21.21.51
ssl-server 51 cipher rsa-with-rc4-128-md5 172.21.21.51 80 weight 10
ssl-server 51 cipher rsa-with-rc4-128-sha 172.21.21.51 80 weight 8
ssl-server 51 cipher rsa-export-with-rc4-40-md5 172.21.21.51 80 weight 5
ssl-server 50
ssl-server 50 rsakey glopedia
ssl-server 50 vip address 172.21.21.50
ssl-server 50 cipher rsa-with-rc4-128-md5 172.21.21.50 80 weight 10
ssl-server 50 cipher rsa-with-rc4-128-sha 172.21.21.50 80 weight 8
ssl-server 50 cipher rsa-export-with-rc4-40-md5 172.21.21.50 80 weight 5
ssl-server 50 urlrewrite 1 *
ssl-server 51 urlrewrite 1 *
ssl-server 51 rsacert EGlobal-Web-Chain
ssl-server 50 rsacert Glopedia-Web-Chain
active
!************************** SERVICE **************************
service E-Global-https
ip address 172.21.21.32
port 80
protocol tcp
active
service Ghalia
port 81
protocol tcp
ip address 172.21.21.31
active
service GlobalInv
port 80
protocol tcp
ip address 172.21.21.31
active
service dms
ip address 172.21.1.115
port 80
protocol tcp
keepalive type http
active
service eglobal-http
port 80
protocol tcp
ip address 172.21.21.32
keepalive type http
active
service email
ip address 172.21.1.122
port 80
protocol tcp
keepalive type http
active
service email123
ip address 172.21.1.123
port 80
protocol tcp
keepalive type http
active
service glopedia
ip address 192.168.2.32
port 80
protocol tcp
active
service glopedia-expapps
ip address 192.168.2.32
port 4028
protocol tcp
active
service secure-transfer
type redirect
no prepend-http
ip address 172.21.21.32
keepalive type none
domain https://www.e-global.com.kw
active
service ssl-eglobal
type ssl-accel
keepalive type none
slot 2
add ssl-proxy-list SSL-Proxy-List
active
service workflow
ip address 172.21.21.44
port 80
protocol tcp
keepalive type http
active
!*************************** OWNER ***************************
owner EGlobal
content eglobal-http
    vip address 172.21.21.51
    no persistent
    protocol tcp
    port 80
    url "/*"
    add service eglobal-http
    active
content eglobal-https
    vip address 172.21.21.51
    protocol tcp
    port 443
    add service ssl-eglobal
    active
owner GhaliaWebSite
content Ghalia-http
    vip address 172.21.21.53
    add service Ghalia
    protocol tcp
    port 80
    active
owner GlobalWebSite
content GlobalInv-http
    vip address 172.21.21.52
    add service GlobalInv
    port 80
    protocol tcp
    advanced-balance sticky-srcip
    active
owner Glopedia
content bpmweb
    vip address 172.21.21.50
    url "/workflow"
    protocol tcp
    port 80
    redirect "/bpmweb"
    active
content cyberdocs
    vip address 172.21.21.50
    add service dms
    protocol tcp
    port 80
    url "/CyberDocs*"
    active
content dms
    vip address 172.21.21.50
    url "/dms*"
    redirect "/CyberDocs"
    protocol tcp
    port 80
    active
content email
    vip address 172.21.21.50
    no persistent
    url "/email"
    protocol tcp
    port 80
    redirect "/owa"
    active
content glopedia-expapps
    vip address 172.21.21.50
    add service glopedia-expapps
    no persistent
    port 4028
    protocol tcp
    active
content glopedia-http
    vip address 172.21.21.50
    add service glopedia
    no persistent
    protocol tcp
    port 80
    url "/*"
    active
content glopedia-https
    vip address 172.21.21.50
    add service ssl-eglobal
    protocol tcp
    port 443
    active
content owa
    vip address 172.21.21.50
    add service email123
    protocol tcp
    port 80
    url "/owa*"
    active
content workflow
    vip address 172.21.21.50
    add service workflow
    no persistent
    protocol tcp
    port 80
    url "/bpmweb*"
    active
!*************************** GROUP ***************************
group Ghalia
vip address 172.21.21.53
add destination service Ghalia
active
group GlobalInv
vip address 172.21.21.52
add destination service GlobalInv
active
group dms
vip address 172.21.21.50
add destination service dms
add destination service email
add destination service workflow
add destination service glopedia
add destination service email123
add destination service glopedia-expapps
active
group eglobal
vip address 172.21.21.51
add destination service eglobal-http
active

Flexconnect AP(Local Switching) Wireless clients are not able communicate eachother

Hi,
Scenario : We are deployed the WLC in Corparate Office and Access Points are placed in Branch Office with FlexConnect Local Switching mode.
In this case, I am not able to Ping the Wireless clients eachother . Peer to Peer Block Option also Disabled.
Some time Wireless clients Ping eachother & some times not. Both Wireless clients are associated with Same AP & Same WLAN SSID.
Please help me urgent ..
Devices :
1)WLC 2500 series , Software 7.2
2)Cisco 1400 series APs
3)CISCO ACS server for AAA authentication
Regards,
Shanmugam Nachimuthu

Hi Shanmugam,
Please apply following steps to configure P2P setting for WLAN:
Step 1 Choose WLANs to open the WLANs page.
Step 2 Click the ID number of the WLAN for which you want to configure peer-to-peer blocking.
Step 3 Choose the Advanced tab to open the WLANs > Edit (Advanced) page.
Step 4 Choose one of the following options from the P2P Blocking drop-down list:
• Disabled — Disables peer-to-peer blocking and bridges traffic locally within the controller whenever possible. This is the default value.
NOTE: Traffic is never bridged across VLANs in the controller.
• Drop—Causes the controller to discard the packets.
• Forward - Upstream — causes the packets to be forwarded on the upstream VLAN. The device above the controller decides what action to take regarding the packets.
NOTE: To enable peer-to-peer blocking on a WLAN configured for FlexConnect local switching, select Drop from the P2P Blocking drop-down list and select the FlexConnect Local Switching check box.
Step 5 Click Apply to commit your changes.
Step 6 Click Save Configuration to save your changes.
Thanks,
Prashant Gondaliya

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.

ECC Client export and import with BW data model

Dear BW Expert,
We are now have BW QAS system which is connecting to ECC600QAS.
Now we are going to:
     First >> Export data ECC600QAS.
     Second Drop this client
     Third Create client with the same logical name as ECC600QAS and then import again with the same logical system name is ECC600QAS. Ofcourse we will re-establish again connection between ECC600QAS and BW QAS.
In this case, do we need to create all data model or mapping data in BW again. Please help on this.
Thanks and Regards,
Kim Cheo.

Hi Reddy,
All your notes do not mention anything about in case Client refresh with the same logical name.
Our case is that we do:
      Step 1:         Export client logical name is "ECC600QAS".
      Step 2:         Drop client "ECC600QAS"
      Step 3:         Import again and create the same client logical name "ECC600QAS".
      In this case do we need to create again all data model, mappying rule or transformation.
      Really, I can not found any idea there in all your note.
Thanks and regards,
Kim CheolYeon Lee.

Switching between clients - Integration builder

Hi,
I'm trying to set up specific business scenarios between different clients on our R/3 qas server. Using integration builder, each interface was defined as having either sender / receiver clnt100 and clnt401. Tests have been performed successfully on both clients vs. our legacy system.
Recently, it has become necessary to remove interface data coming from / going to client 100. I've removed the necessary definitions in the business scenario configurations. This has worked fine : tests outbound from client 100 are not being processed. However, I'm having trouble with the link between the IDoc interfaces and the processing of the messages for the remaining client. Each message type, such as (ZZ)CREMAS or (ZZ)MATMAS is defined correctly, and we have periodic jobs setup that run a specific program with an associated variant.
Ex : Job SEND_VENDOR_CP runs (successfully) every minute (with an associated message type). However, the data isn't being pulled. I have to manually start the job. This then results in a message being sent through (sxmb_moni - message with "checkered flag") and the legacy system receives the data from this client (401) normally. I'm just wondering why the interfaces don't run automatically in client 401 (as they still do in client 100). Is there a missing association in the message types ?
Any help would be greatly appreciated (I'm fairly new to XI). We are using XI 2.0. Our systems are defined as :
XIQAS000 (1 client) EQ1CLNT100 & EQ1CLNT401 (same for the RFC's).
Thank you,
Eric P.

Found the problem : the scheduled jobs on 401 were targeting client 100. Re-creating the background jobs has solved this problem.

Switching ECC client in BI

Similar Messages

Maybe you are looking for