Question:
Hello,
we have 2 BW Systems (One dev. System; One prod. System. NO BW Q-Box) and 3 R/3 Systems (Dev., Q and Prod. System).
What is your proposal to connect?
BW Dev. to R3 Q-System or BW Dev. to R/3 Prod. System?
(Data Quality in R/3 Q-System is very bad).
Thanks in advance.
Answer:
You HAVE to connect you BW DEV to R3 DEV,
because you will create objects in R3DEV that will have to be transported.
This means that if you only connect BW DEV to R3 Q, you will have a problem transports-wise.
Now, one BW can be connected to several R3, so you may consider connecting BW DEV to R3 Q as well, to have data to test ;
I would avoid it if you are a beginner, since it is sometimes a little bit tricky, and as you stated that the data quality is bad in R3 Q anyway.
Ch
Answer:
Hello CHC,
why do I have to connect my BW DEV to R3 DEV?
You mentioned that I will have problems in my transport-wise.
That's not clear for me.
Pls correct me if I am wrong:
I can do my R3 delelopments in Dev. and transport them to R3 Q-System (which is connected to BW Dev.) - menas: no connection between the two Dev. Systems. Where is the problem?
(A collegue told me the following system landscape: 3 BW Systems. 3 R3 Systems. Connection: BW Dev. to R3 Quality. BW Quality to R3 Prod. And BW prod. to R3 prod. - but we only have two BW Boxes...
Thanks in advance.
Answer:
Listen, if you know the answers, then don't ask the question.
Want to have an example ?
Do this :
BW Quality to R3 Prod. And BW prod. to R3 prod.
then, you create a delta load for CO, it will work fine for months in BW prod, then you will decide "let's do a delta in BW Quality"
I know a guy that has nearly been fired and his whole consultancy team as well because they did this type of error...
Because as the delta queue is Target system dependent, but because the timestamp is not, it did screw up the delta in production, and nobody noticed it until the figures were proved to be wrong.
Ch
Answer:
Hello,
I am thinking loud of a problem which I have currently. I don't know the answer. I only want a discussion. Not more.
What I have learnt - thanks! - is:
BW Dev. System to R3 Quality System
BW Prod. System to R3 Prod. System
What is up to now not clear for me is the connection from BW Dev. System to R3 Dev. System:
CHC. You wrote:
"You HAVE to connect you BW DEV to R3 DEV".
If s.b. can answer that question, of me this topic is perfectly solved.
[/quote]
Answer:
[quote="starwars2001"]Hello,
I am thinking loud of a problem which I have currently. I don't know the answer. I only want a discussion. Not more.
What I have learnt - thanks! - is:
BW Dev. System to R3 Quality System
BW Prod. System to R3 Prod. System
What is up to now not clear for me is the connection from BW Dev. System to R3 Dev. System:
CHC. You wrote:
"You HAVE to connect you BW DEV to R3 DEV".
If s.b. can answer that question, of me this topic is perfectly solved.
Answer:
Hi starwars,
no it is not a must to connect BWDEV with R3DEV. I have a view system landscapes with 2 BW systems and most times the data in R3DEV is so poor that we decided to connect the R3Q. Then you have to know that every source you develop must first be transported than replicated and than can deliver test data to you BWDEV. And you should plan to refresh 1 or 2 times a year the R3Q data from R3Prod if it is possible. That should be enough testdata.
Regards,
Jochen